# Waste Management Fleet Tracking Software | Open VTS

Canonical: https://openvts.io/industries/waste-management-and-sanitation

Open VTS is self-hosted GPS fleet software for compatible garbage trucks, street sweepers, recycling vehicles and sanitation fleets. Review latest reported locations, trips, stops, routes, geofences, notifications and reports. GPS movement evidence alone cannot confirm an individual bin pickup, container weight or active sweeping; those outcomes need suitable machine, crew or service records and validated integrations.

## Waste collection tracking. Every round in view.

Follow garbage trucks, street sweepers, recycling vehicles, and sanitation fleets from depot to service area. See the latest reported location, review collection routes, investigate exceptions, and operate the tracking platform on infrastructure you control. [Explore collection visibility](/industries/waste-management-and-sanitation#visibility) or [discuss your fleet](/company/contact-us).

GPS provides movement evidence. Confirming an individual pickup may require additional equipment or service records. The hero is concept imagery of municipal collection operations, not a live customer deployment.

## A collection route is more than a line on a map.

Waste collection is a high-stop, time-sensitive operation. Trucks move between streets, transfer stations, customer sites, depots and disposal facilities. Supervisors need to distinguish a delayed route from a stopped vehicle, a completed visit from an assumed pickup, and fresh GPS data from a position reported hours ago.

Open VTS provides the vehicle-tracking layer: location reports, movement history, geofences, routes, notifications and reporting. Add verified collection records through appropriate hardware, workflow tools or external integrations when contracts require bin-level proof.

- **Keep collection rounds visible:** Review where assigned vehicles last reported, how routes are progressing and where intervention may be needed.
- **Investigate, don't assume:** Connect route history with service evidence before treating an address visit as a completed collection.
- **Run tracking on your terms:** Keep the deployment, operational data, roles and integrations under your organization's administration.

## Across the city. One view of the fleet.

The interactive example switches between a central municipal ward, a riverside collection run and an industrial waste route. Select a vehicle to inspect its last reported state. The conceptual map shows location context, not a live municipal fleet. The sample positions and times are fictional; a deployment displays actual device reports according to permissions and connectivity.

1. **Latest reported location:** Find the last received position and timestamp, not an assumed live position.
2. **Stops and time on route:** Review trip and stoppage history to understand a delay.
3. **Dispatch with a clear question:** Contact a crew about a deviation, long stop or stale update rather than relying on location alone.

## Plan the round. Review the journey.

Collection days move from depot departure through residential streets, commercial stops, transfer stations and back again. Route planning, recorded movement and operational assignments are related, but they are different records.

### Follow the round. Investigate the exception.

The interactive four-stage sequence follows a hypothetical collection vehicle from depot to service zone and transfer station. Its stages are leaving the depot, entering the collection area, arriving at the transfer station, and reviewing the round. GPS positions, boundaries and history can help a supervisor reconstruct the day. The example is conceptual, not live collection telemetry. Arriving near a bin does not establish that it was emptied.

### From route planning to route history.

Actual Open VTS map, trip-history, geofence and reporting screenshots illustrate general product functionality. A route can be planned and saved from stop locations, but assigning a vehicle and recording proof of service require appropriate separate workflows. [Read the route optimization guide](/resources/documentation/user-guide/route-optimization).

## A truck visited the street. Was the bin actually emptied?

This distinction matters when a resident reports a missed pickup or a commercial customer disputes an invoice. GPS location can support an investigation. Specific service confirmation generally needs a collection event or crew record joined to that location.

### Build a service record you can explain.

The interactive evidence levels distinguish vehicle movement data, machine activity and confirmed container identity. Each added layer answers a different question and should only be presented as available when its hardware and integration are in place.

1. **GPS track:** Location and timestamp show a truck reported near a service location. A visit can be investigated through route history and dwell; it does not prove that a specific container was lifted, weighed or collected.
2. **Lift signal:** Suitable PTO, hydraulic or arm instrumentation may support a machine activity record, subject to compatible hardware, configuration and interpretation.
3. **Bin identity:** RFID, crew records or an equivalent service event can identify a specific container when linked to the truck, location and time.

A municipal report may combine Open VTS history with separately captured RFID, lift, weighing, crew or customer-service data through suitable integrations. The contract determines what counts as acceptable proof. [Explore the REST API reference](/resources/api-reference).

## Notice what changed. Know what to check next.

Collection operations face blocked streets, delayed vehicles, long stops and equipment gaps. A useful alert gives the supervisor context to investigate. The interactive examples cover route deviation, a delayed GPS update and a depot exit after hours. Each illustrates the device report, configured condition and human response; none is a live alarm feed or automated missed-service certification.

### Turn the round into an operational review.

Review recorded movement, trip history, distance, stoppage periods, geofence activity and available device signals. These records can help analyze recurring delays, depot waiting time, vehicle activity and route exceptions. For municipal contract acceptance, verify the required reporting format and service evidence separately. Weight tickets, bin service confirmation, driver sign-off and route coverage percentages may require integrations or contract-specific processing. [Explore reports and documentation](/resources/documentation).

## One tracking platform. Different collection vehicles.

Dense urban rounds and industrial container transport involve different vehicles, schedules and data needs. Tracker compatibility and sensor availability determine what the platform receives.

- **Rear and side loaders:** Review neighborhood collection rounds, stops, progress between areas and unexpected departures.
- **Front-load compactors:** Review commercial dumpster routes, visits and travel between yards and transfer facilities.
- **Roll-off and hook-lift trucks:** Review movement among customer locations, container sites, industrial facilities and disposal destinations.
- **Street sweepers and service units:** Inspect sweep routes and site visits; brush operation and road coverage need machine-state or task records.
- **Recycling collection fleets:** Keep vehicle positions visible while verifying stream, load and tonnage records in the appropriate system.
- **Supervisor and workshop vehicles:** Coordinate response, maintenance visits, transfers and fleet support.

### GPS shows movement. Other signals show the job.

A GPS track cannot create an engine-hour meter, hydraulic lift event or bin-level record that the equipment never sent. [Check device compatibility](/product/supported-devices).

| Question | Typical data needed | Important distinction |
| --- | --- | --- |
| Where was the truck? | GPS reports and time | Latest received position; freshness varies by device and network. |
| Did it visit the service area? | GPS history and a geofence | Area entry does not verify that a particular bin was serviced. |
| Was a container lifted? | PTO, arm or hydraulic signal | Requires compatible instrumentation and suitable interpretation. |
| Which bin was emptied? | RFID scan, crew record or equivalent | Container identity and service event must be captured separately. |
| What was the load weight? | Weighbridge ticket or calibrated weighing system | GPS does not measure material mass. |
| Did a sweeper's brushes operate? | Machine or PTO state | Travel along a road is not proof of active sweeping. |
| How much fuel was used? | Compatible fuel/CAN sensor or validated method | Data and calculations depend on hardware, calibration and conditions. |

## Own the tracking environment. Keep your service data connected.

Run Open VTS on infrastructure administered by your municipality, fleet business or service provider. Organize customer access and keep GPS history available for integrations and reporting processes. [Compare self-hosted and SaaS](/product/self-hosted-vs-saas).

- **Your infrastructure:** Choose supported customer-controlled hosting and take responsibility for access, backups, maintenance and monitoring.
- **Your fleet and users:** Manage roles, assigned vehicles, fleet groups, operations and history for departments, contractors or customer accounts.
- **Your reporting workflow:** Use documented APIs to connect suitable municipal systems, waste-management ERP, service-evidence records or reporting tools.

The published Free software tier supports up to 50 vehicles with full software features. Hosting, trackers, SIMs and third-party services are separate. [Download Open VTS](/download).

### Pilot one round. Prove the data before scaling.

Start with a representative vehicle and real route. Validate location quality and integration requirements before rollout. [Read deployment documentation](/resources/documentation).

1. Choose a route with depot, collection area, transfer station and expected interruptions.
2. Test stop-start operation, low-signal areas, device power, geofences and timestamp accuracy.
3. Agree whether GPS, RFID, PTO/lift, photos or weighbridge records are required for each service-evidence use case.
4. Verify access, exports, exceptions, alert quality and operational responsibilities before expanding.

## What waste fleet operators need to know.

### What is waste management fleet tracking software?

It combines GPS vehicle locations, travel history, geofences, alerts and fleet reports to help supervisors understand garbage collection and sanitation vehicle activity. It does not, by itself, certify an individual bin pickup or measure waste quantity.

### Can Open VTS track garbage trucks and municipal sanitation vehicles?

Yes, when the vehicle has a supported GPS tracker and working connectivity. Applicable vehicle types include collection compactors, tippers, roll-off haulers, sweepers, recycling trucks and support vehicles. Data fields depend on the hardware.

### Can the system prove that every bin was collected?

Not from GPS alone. GPS can show that a truck reported near a location. Confirmation for a specific bin usually requires RFID, a lift/PTO signal, an operator record, image evidence, or another service event tied to that stop.

### Does Open VTS optimize garbage collection routes?

Its route optimization workspace can arrange multi-stop journeys and save planned routes. Specialized waste-routing constraints such as curb-side approach, truck capacity, landfill windows, one-way access and hundreds of assigned containers should be validated separately. Route planning does not automatically assign a vehicle or verify service completion.

### How can I investigate a missed collection complaint?

Review the vehicle's relevant history, last reported location, stops and visits around the time in question. If a pickup-specific decision is required, combine the GPS evidence with crew notes, RFID/bin scans, lifting events or other agreed service records.

### Can I monitor vehicle entry and exit at transfer stations?

Yes. Configure an appropriate geofence and review GPS reports associated with that area. A geofence records a vehicle's reported movement; it does not replace weighbridge or disposal acceptance documentation.

### Can I monitor compactors' PTO or hydraulic operation?

Only when compatible vehicle hardware supplies those signals and the protocol/integration correctly interprets them. Standard GPS location alone cannot establish a compaction or lift cycle.

### Does this support street sweeping verification?

GPS history can show the streets traveled. Proof that brushes or spray systems were operating requires corresponding machine-state data or an operator/service record.

### Can a municipal authority prepare contract reports?

Open VTS offers vehicle trip, distance, stop, geofence, notification and available sensor data. Exact contract templates, bin-level completion, ward-specific KPIs and statutory submissions depend on requirements and may need configured reports or additional integrations.

### Can dispatchers receive route deviation or delayed-report alerts?

Open VTS supports configurable notifications including route deviations, geofence events and other operational conditions. Alert accuracy depends on route definitions, rule configuration and incoming device data. Review last-update age before treating a device position as current.

### What happens in areas with poor network connectivity?

The last received position remains available. Some trackers buffer messages and upload them after reconnecting, but recovery depends on model and configuration. Live status should never be inferred from a stale report.

### Can I track CNG, diesel and electric garbage trucks together?

Location tracking depends primarily on a compatible installed device, rather than the powertrain. Engine, fuel, battery and diagnostic data vary and should be verified for each vehicle type.

### Can Open VTS connect to a municipal waste-management ERP?

Documented REST APIs and supported events can be used for integrations. Specific citizen complaint portals, RFID readers, weighbridges and municipal MIS platforms require assessment of the available source data, permissions and interface contracts.

### Is Open VTS a self-hosted GPS tracking platform?

Yes. The platform can run in a customer-controlled environment. The organization remains responsible for hosting, backups, software maintenance and appropriate access/security controls unless separately managed by an agreed service provider.

### Is there a free plan for a small sanitation fleet?

Open VTS currently provides a Free tier for up to 50 vehicles without a time limit. Trackers, SIM connectivity, server hosting and external integrations may involve separate costs. See the official pricing page for current terms.

## Make every round easier to understand.

Start with dependable vehicle tracking. Add route, event and service-evidence integrations where your waste collection business needs more. Run the platform on infrastructure you control. [Get started free](/download) or [discuss your waste fleet](/company/contact-us).
