MRA in a large organisation

[Herman Veldhuizen]

Just a tip.

I see great potential for MRA in organisations with many drivers. The main requirement for using MRA in such an organisation will be a better separation of the route management from the route navigation : central, organisation internal, repository for the routes to which only a few people in the organisation have WRITE & CREATE access to. Others have only READ access to the repository.
.

[Con Hennekens]

@Herman-Veldhuizen, Although MRA is always open to suggestions, I think your specific use fits better to some kind of fleet-owner software to be honest. That is a completely different kind of game.

[Herman Veldhuizen]

@Con-Hennekens Fleet management systems like those from TraffiTech or Tenix are designed to help the people in the office, not the driver who needs to navigate from A to C via B. They lack something like MRA. It's just a comment and feel free to ignore it.

[Corjan Meijerink]

Thanks for sharing your thoughts

[Con Hennekens]

@Herman-Veldhuizen said in MRA in a large organisation:

only a few people in the organisation have WRITE & CREATE access to. Others have only READ access to the repository

Rethinking this, I think it is almost completely possible as it is...
A manager can add drivers-accounts to his as friends. Friends can look into the library of their manager-friend, and open or start all his routes without being able to change them. They can start navigation of those routes directly from their "friend's" library.

Maybe not exactly what you would like, but maybe usable?

feel free to ignore it.

No one is here to ignore anything

[Herman Veldhuizen]

@Con-Hennekens Thanks, that's good to know. Inside an organisation I think that the RX Library is the logical place to have the routes of the organisation, and only those routes. Preferably with a tree/list view (instead of a map view). Employee's login for example via single sign on. MRA has all the components needed (and more) but might need repackaging to get acceptance.