Asset management

How Should Municipalities Link Lighting and Traffic Faults to the Right Asset?

Separate pole, lamp and controller identities when planning municipal maintenance, and avoid treating several reports as several confirmed failures.

Streetlight and traffic signal equipment at a municipal junction.

Identify the maintainable equipment behind a lighting or traffic report before treating the report as a confirmed component failure. A location such as “the junction” can contain several assets with different owners, functions and maintenance teams.

Electric and Traffic are documented Cityworks asset groups. They establish relevant asset categories, not a guarantee of signal-control functions or an electrical operating procedure. Official asset groups.

Build an identity worksheet

Record levelExample question
LocationWhich junction, road side or crossing?
Supporting structureWhich pole or cabinet?
Maintainable equipmentWhich lamp, signal head or other component?
Reported symptomWhat was observed, without assuming the cause?
Confirmed findingWhat did an authorised assessment establish?
ResponsibilityWhich team owns the next action and acceptance?

Use this sheet to define requirements for Unity Maintain. The selected asset model and work templates need validation in the actual deployment.

Worked example: a cluster of dark lamps

In a hypothetical case, three lamps on nearby poles are reported dark. The initial records identify three symptoms, but do not establish three failed lamps. An authorised investigation may find a shared cause or separate issues.

Preserve each location and link the eventual findings to the equipment actually assessed. If one intervention addresses all three reports, retain the links instead of inventing three independent repairs for reporting convenience. If one lamp remains unresolved, keep its follow-up visible when the shared task closes.

Traffic assets add a scope boundary: an asset-maintenance record is not an instruction to alter signal timing or operate electrical equipment. Route specialist decisions through the municipality’s approved responsibilities and procedures.

Prevent location ambiguity

A photo may show the intersection without distinguishing the pole. Agree which reference, direction and location evidence are sufficient. In bilingual records, preserve asset codes while translating descriptions such as road side and symptom. “Lamp dark” and “pole damaged” should remain separate observations.

Acceptance test

Ask a reviewer to start with one caller report and find the confirmed equipment, decision, completed work and remaining issues. Then start from a pole and distinguish its components’ histories. If the model only supports a general junction note, narrow the claims the resulting report can make.

The request and work-order guide provides a compatible record model for this test.

Plan your next step

Review InfoGraph’s Trimble offering and GIS implementation services. Contact our team with a sample asset record and the decision you need the workflow to support. For GIS data and field-collection skills, explore the training catalogue and confirm the relevant course scope; a dedicated Maintain course is not assumed.