--- title: "Independent measurement of chartered routes and trips | Merus Tracker" description: "How GPS positions, virtual fences and boardings form your own reading of the contracted trip, without depending only on the carrier's report." url: https://merustracker.com.br/en/plataforma/auditoria/medicao-independente/ language: en updated: 2026-10-22 --- # Independent measurement: how to know what really happened on each trip How GPS positions, virtual fences and boardings form your own reading of the contracted trip, without depending only on the carrier's report. **Published** Oct 22, 2026 **Updated** Oct 22, 2026 **Reading time** 4 min read **Byline** Merus Tracker team ## Quick answer Independent measurement is the construction of your own reading of how transport was executed, built from sources the company defines, such as GPS positions, virtual fence crossings, observed times and boarding records. In Merus Tracker, these events are tied to the planned trip, which makes it possible to check route, schedules and service without depending only on the carrier's report. ## In short - Independent measurement gives the company a second source about the trip, besides the supplier's report. - Raw events (positions, times, boardings) only make sense when tied to the right trip. - Merus integrates the telemetry the carrier already uses or supplies equipment with installation included. - Missing data is not proof of failure: inconclusive cases stay visible for human analysis. - Measurement is the foundation of planned × actual and invoice reconciliation. ## Why the company needs its own measurement In many charter contracts, everything the company knows about execution comes from the carrier: the trip report, the mileage and the incidents. It is like checking a bill using only the statement of the party charging you. The **independent measurement** changes that. The company gets its own reading of each trip, built from sources it knows and controls. This reading does not replace dialogue with the supplier. It gives that dialogue a common basis. ## From raw data to the measured trip A single GPS point says little: a vehicle was at a certain coordinate at a certain time. To become useful information, that point needs to be tied to a trip, a line, a direction and a contract obligation. That is what Merus does, in four layers: | Layer | What happens | Example | | --- | --- | --- | | Raw event | The data arrives with its origin and time preserved | Position of vehicle ABC at 05:42:10 | | Association | The event is tied to the most coherent trip | Line 07, direction to the site, 05:40 trip | | Measurement | Events form route, times and service | Departure at 05:43, 11 of 12 stops served | | Review | People confirm, adjust or keep the discrepancy | Stop 9 closed for roadwork, authorized detour | Keeping the four layers separate is what makes measurement trustworthy. The original data is never overwritten, and every conclusion shows where it came from. ## Which sources form independent measurement? ### GPS positions They are the basis of route measurement. They show where the vehicle went and at what time. They can come from the tracker the carrier already uses, through native integration with the main telemetry hardware, or from Merus telemetry, sold with installation included in the vehicles. ### Virtual fences Areas drawn on the map at stops, garages and sites. They record the vehicle entering and leaving and make it possible to know whether each stop was served and when. ### Observed times Departure, passage and arrival, derived from the positions and the fences. They feed the punctuality analysis. ### Boardings When the operation uses [identified boarding](https://merustracker.com.br/en/plataforma/funcionarios/embarque-identificado/), each boarding is tied to the passenger, the stop and the trip. This makes it possible to measure not only whether the vehicle passed, but whether people were served. ## How measurement is used day to day ### Monitor the operation in real time The team sees trips in progress, delays and deviations as they happen and handles incidents the same day, instead of finding out at month-end closing. ### Investigate a possible route deviation 1. Open the trip and overlay the planned route on the recorded positions. 2. Check which stops were served, at what time and with how many boardings. 3. Consult related incidents and communications. 4. Classify the case: unauthorized deviation, agreed change, source failure or incorrect association. 5. Record the explanation or send the open item to the carrier. ### Support invoice checking Measurement is the basis of the [operational reconciliation](https://merustracker.com.br/en/plataforma/auditoria/conciliacao-operacional/): measured trips and kilometers are compared with what the carrier charges. ## Data gaps: how to handle them responsibly No source is perfect. Equipment fails, mobile coverage varies and drivers swap vehicles. A responsible measurement: - **Does not treat missing data as missing service.** A trip with no positions is marked inconclusive, not as not completed. - **Shows the quality of the source.** The team knows when the reading is complete and when there are holes. - **Combines evidence.** Boardings, incidents and supplier records help close cases without GPS. - **Preserves the review history.** Who decided, when and why. ## Equipment: reuse, integrate or install | Fleet situation | Path in Merus | | --- | --- | | The carrier already has a tracker | Native integration with the main hardware, after technical assessment | | The fleet has no equipment | Sale of Merus telemetry with installation included | | Specific case or unusual source | Integration or tailored solution | | Loan or rental | Coming soon | The Merus team supports installation, data loading and validation until the system is 100% functional. ## Independent measurement and planned × actual Measurement answers “what happened”. The [planned versus actual](https://merustracker.com.br/en/plataforma/auditoria/previsto-vs-realizado/) answers “is what happened what should have happened?”. Both analyses use the same trip in Merus and, together, form the basis of [contracted transport auditing](https://merustracker.com.br/en/plataforma/auditoria/). In public transport, the same logic supports [public transport oversight: trips, kilometres and subsidy](https://merustracker.com.br/en/blog/fiscalizacao-do-transporte-coletivo/). ## Want to see this in your operation? The Merus team shows how this flow looks with your data, routes and contract, and supports the implementation until the system is 100% functional. [Talk to the Merus team](mailto:vendas@rioservice.com) FAQ ## Frequently asked questions **Which sources can be used for independent measurement?** GPS positions, virtual fence crossings, observed times and boarding records. They can come from trackers already installed, natively integrated with Merus, or from equipment sold and installed by Merus. **Does independent measurement replace the carrier's report?** No. It coexists with it. The supplier's report remains a source; independent measurement is the company's reference for checking that report. **Is a trip with no GPS signal considered not completed?** Not automatically. A missing position can have a technical cause, such as coverage or equipment failure. Merus flags the gap and keeps the trip available for analysis with other evidence, such as boardings and incidents. **Do I need to replace the fleet's trackers?** Not necessarily. Merus has native integrations with the main telemetry hardware on the market and assesses what already exists. When there is no equipment, Merus sells telemetry with installation; loan and rental options are coming soon. **How often do positions need to be sent?** It depends on the equipment and the goal. To verify the route and passage through stops, short intervals give a more faithful reading. The right frequency is defined in the technical diagnosis of each operation. **What is a virtual fence?** It is an area drawn on the map, such as a stop, a garage or a company site. When the vehicle enters or leaves that area, the system records the event and the time. ## Talk about your operation. [Talk to Merus](mailto:vendas@rioservice.com)