VRt.Monitor
Monitor is the execution control service: it accepts already calculated trips, hands them out to performers in the mobile application and matches the plan against the fact in real time.
Planning answers the question "how it should be", Monitor answers "how it is actually going": where the performer is, which stops have already been passed, what has been cancelled, which payment has been accepted and when arrival at the remaining stops is now expected.
Key concepts
- Wave — the unit of work in Monitor: a set of source data and calculated trips that is launched into execution. Waves are stored in folders, and you define the folder structure yourself (for example, region → month → day → time).
- Crew — an account with limited permissions that a performer uses to work in the mobile application. It is created once and reused across different waves.
- Deal — the assignment of a crew to a specific trip of a wave.
- Fact — an event recorded by the performer or by the application: for example, arrival, completion or cancellation of a demand, payment acceptance, GPS coordinates.
Where to start
- Integration — the complete basic scenario: authorization, crews, wave import, launching trips, collecting facts and retrieving results.
- Examples — ready-made wave datasets, each one showing a single capability of the service. They can be opened both in Monitor and in Studio — the data format is common.