As mentioned in the Setting Up Your Locations training, RPS Tracker has the concept of Projects, Locations and Routes. The three elements are not tightly bonded with each other i.e. a location is independent of a project and a Route can incorporate any location but is tied to a project. However a Project in a city or county area can be combined into a single overarching project that covers the city or county area and all projects ongoing within the city or county limits.
Think about your operations and reporting requirements before defining how you use the RPS Tracker System. The reporting is extremely flexible and can be filtered by driver, asset, date, time, route, location, material, project etc. Also think about who you want to access what information within the RPS Tracker platform - this will often be what dictates how you set up the system.
Here are some guidelines
If you are running a single large project over an extended period of time, that will likely be the definition of the project. The project can leverage your corporate Waste and Borrow Sites as well as your maintenance yards and fuel locations, however only route “legs” that are defined in your project will report using the Project filter.
If you are working in a city or county and are running multiple small sites with limited duration within a larger area along with multiple borrow, waste, maintenance and fuel etc. locations, you may be better off defining your project at the city or county limit and then define each project using single or multiple locations. In this way you can still report by Location to segregate your data by “project” but your equipment fleet will have common routes allowing them full flexibility to serve all of your projects in the defined area as well as work with all of your other corporate locations for waste, borrow, maintenance etc.
In the video below we will show you how to setup and define a Project and Project Routes as well as setting up ownership and project data visibility and access controls to different users.