Skip to main content
All CollectionsGetting started with Mooven
Start monitoring routes on your Site
Start monitoring routes on your Site
Updated over a week ago

At any time you can start and stop monitoring of the routes you have just created. By monitoring these routes, you can leverage the wide variety of data sources Mooven pulls together.

Using AI technology to distil hundreds of millions of data points into actionable operational decisions, once monitoring is live each route will now have the context of rich traffic, transit and environmental data; data from job and asset systems; integrations with industry sources like count records; or contextual data such as weather and upcoming events.

Start Live Monitoring


  1. Once you have created a set of routes, you don't have to start live monitoring immediately. However, once you have the ideal route layout, by entering the 'View' panel you will see a prompt to start live monitoring.

  1. Click β€˜start monitoring and the routes you have previously set up will start collecting data immediately.

  2. Alternatively, you can access the monitoring features in the 'Edit' panel under 'Monitoring Schedules'

Here you can review the option to edit your monitoring and create a schedule where you could have a fixed window or fixed end date for the data collection.

At any time you can start and stop monitoring. Mooven is a self-service platform for you to adapt and initiate whenever you need - because projects and the delivery environments they operate in are dynamic and your project workspace should be too.

How can I tell which Sites have live monitoring on?


  1. An immediate flag as to whether you are collecting live data on this site is the top left of your map, within either the view, Plan or Edit panels. You will see a green signal denoting live monitoring like this 'monitoring active'.

  2. Another way is from the main dashboard area (you can return there at any time by pressing the Mooven logo in the top left).

    The Sites in grey are not currently being monitored:

Did this answer your question?