Municipal Fleet & Asset IoT Monitor

Principal workflows

• Track: Location, engine and equipment data from your telematics devices arrive in one map and vehicle list, whatever vendor each device comes from.
• Maintain: Odometer and engine-hour readings drive preventive maintenance schedules, and fault codes are reviewed before they become breakdowns.
• Analyze: Fuel, use and maintenance costs are brought together per vehicle, so fleet managers can see which vehicles are underused, costly or due for replacement.
• Publish: For route services such as snow plowing and street sweeping, the Monitor publishes a public map of where service has been done, using rules your city sets.

Who uses it

• Fleet managers and fleet services divisions
• Public works and streets operations supervisors
• Fleet maintenance shops and mechanics
• Public information officers and 311 teams
• Finance and asset management staff responsible for capital planning

Reporting

• Vehicle utilization, idle time and cost by department and class
• Preventive maintenance due, overdue and completed
• Fault codes by severity and vehicle
• Fuel use and fuel exceptions by vehicle
• Streets serviced during an event by service and zone
• Telematics devices not reporting

Features

• Multi-vendor telematics: Data from more than one telematics provider and from vehicle manufacturers' connected-vehicle feeds shown in one place.
• Operations map: Vehicles and equipment on a live map by department, class and status, with route history for a chosen time window.
• Equipment sensors: Plow blade, spreader, sweeper broom and power take-off status recorded where your vehicles are equipped to report it.
• Asset register: Every vehicle and tracked asset with its department, class, funding source, acquisition date and assigned device.
• Preventive maintenance: Service intervals by vehicle class, with due and overdue maintenance calculated from actual mileage and engine hours.
• Fault code review: Engine fault codes listed by severity, with history per vehicle, for a shop supervisor to decide on action.
• Work orders: Open work orders from fault codes, schedules or driver reports, or pass them to your existing maintenance system.
• Fuel matching: Fuel card transactions matched to vehicles, with exceptions such as fills larger than the tank or fills while the vehicle was elsewhere.
• Utilization and cost: Hours in use, idle time, distance, fuel and maintenance cost per vehicle, compared within its class.
• Proof of Service map: A public map of serviced streets for the services and vehicle classes you choose, with a publication delay and sensitive vehicles excluded.
• Geofences and alerts: Alerts when vehicles enter or leave areas you define, run out of hours, or stop reporting.
• Complete audit trail: Every view of location history, export, configuration change and public map setting recorded with the person and time.

Integrations

• Telematics providers: Location, engine and sensor data from your telematics vendors and manufacturers' connected-vehicle services, connected during implementation.
• Fuel cards: Transactions from your fuel card provider or city fuel sites matched to vehicles.
• Fleet maintenance system: Work orders passed to the maintenance or enterprise asset management system your shop already uses, with completion returned.
• Finance and ERP: Asset register and cost data exchanged with your finance system for capital planning.
• GIS: Street centerlines and service routes from your GIS, including Esri ArcGIS, used to mark serviced segments.
• 311 and service requests: Service status shared with your 311 system, including Moraph's 311 Omni-Channel Citizen Intake, so agents can answer resident questions.
• Single sign-on: Staff sign in through your identity provider (SAML or OpenID Connect).
• Work API: Vehicle, maintenance and utilization data available to your reporting tools through the Moraph Work API.

Deployment

• Moraph cloud (US): Hosted and operated by Moraph in the United States region.
• Dedicated environment: A single-tenant environment for cities whose policies require isolation, for example where police vehicle data is included, scoped in the proposal.
• With a managed service: Optionally run alongside a Moraph managed service for telematics integration support and platform administration.

Security and privacy

• Single sign-on: Staff sign in through your identity provider, so your password and multi-factor policies apply.
• Role-based access: What each person can see follows their role and department; police and other sensitive vehicles can be hidden from everyone outside the owning department.
• Public map safeguards: Only the services and vehicle classes you choose appear publicly, after a delay you set, and never with driver names.
• Encryption and keys: Client data is encrypted, with keys Moraph staff cannot use without explicit, time-bound authorization.
• Complete audit trail: Every view of location history, export and change is logged with the person and time, and cannot be edited.
• US-only hosting: Data for US government clients is hosted in the United States region only, and every release passes security testing gates with a software bill of materials kept for the product.

Limitations

• It does not supply telematics hardware or connectivity. Devices and data plans come from your telematics providers, and data quality depends on them.
• Equipment sensor data such as plow and spreader status is only available where vehicles are fitted to report it.
• The public map shows where vehicles have passed with equipment active; it is not a guarantee of road condition or that a street is clear.
• What appears on the public map, and when, is your city's decision. The Monitor applies those settings.
• It is not a full fleet maintenance or parts inventory system. It works with your existing maintenance system or handles basic work orders only.
• It is not a computer-aided dispatch system and does not dispatch police, fire or EMS vehicles.
• Driver behavior data may be subject to labor agreements and records laws; how it is used is your city's decision.
• Location history is kept for the retention period you set, and is subject to your state's public records law.

Next steps

Book a demonstration or a technical briefing at www.moraph.com/solutions/municipal-fleet-and-asset-iot-monitor. Purchasing routes and company information: www.moraph.com/how-to-buy.