Asset Management & Operations

Asset Management & Operations

Winter, on one map. Work orders, assets and the crew share one history.

The problem

Roads, fleet and facilities generate work that finance never sees until month-end, and the map in the truck does not match the desk.

The workflow

A service request opens a work order. Completing the work order posts labour and writes the asset history. The incident map shows open requests, work orders and road defects together. Colour is the division. The deadline shows when it is overdue.

Road class, patrols and winter events follow the province's maintenance rules. In Ontario, a defect past Ontario Regulation 239/02 opens a work order with that regulation's repair-by time.

On screen

Work orders in OneCity Canada.
Incident map in OneCity Canada, with open requests and work orders on the municipal map.

Capabilities

Work orders

The job, and the cost.

Job plans and preventive maintenance for the division. Completing a work order posts labour.

Asset history

What this asset has already seen.

Work orders and maintenance stay on the asset, so the next crew can read the record.

Fleet

Fuel, hours and the reservation.

Plate, class, odometer and engine hours live on the asset. Fuel transactions record litres and cost. Pool vehicles are reserved, then checked out and back in.

Public works

Winter, on one map.

During a winter event the map can show plows moving, a water-main break, and the 311 calls that came in with the storm.

Integrations

Completed work posts to the ledger. A project task can sync with Jira. Email notices follow the workflow the division configures.

Demo

Incident map. Open work across divisions, with the deadline on each record. Silent screen recording. Captions describe the picture.