Connect fiber maintenance to stable physical asset identities and preserve the relationship between the reported location, inspected infrastructure and completed intervention. A cabinet repair and a customer service outage describe different things and should not share an ambiguous completion meaning.
Fiber is a documented Cityworks asset group. This supports evaluating asset maintenance, not an assumption that Unity Maintain performs network design, splice management or service provisioning. Official asset groups.
Define the physical work boundary
| Object | Example maintenance question |
|---|---|
| Chamber | Which opening or structure was inspected? |
| Cabinet | Which enclosure has the recorded defect? |
| Duct or route segment | What physical extent does the intervention cover? |
| Equipment relationship | Which separately managed item is affected? |
| Service reference | Which external operational record, if any, needs a link? |
Agree which system owns each identity. A maintenance record can reference another system without copying its entire data model.
Worked example: repaired enclosure, separate service question
In a synthetic case, a damaged cabinet enclosure is repaired. The work record identifies cabinet FC-08, the approved scope, completed action and acceptance evidence. A linked service issue remains under another team’s investigation.
Closing the enclosure repair must not automatically imply restoration of every service passing through the cabinet. Record the handoff and let the responsible operational system establish service status. This protects both teams from a misleading common “resolved” label.
If the cabinet is replaced, retain the previous enclosure identity where history matters and record the new relationship. Do not overwrite a physical identifier merely to keep the map label familiar.
What should a GIS update include?
A field correction should state whether it changes location, asset identity or a relationship. These are different decisions. A technician moving a point to improve its position should not unintentionally redefine the network topology.
Use a review queue for uncertain changes and define who can accept them. The required editing controls and integrations must be tested in the actual environment; this is a planning recommendation.
Test the boundary between systems
Give reviewers the cabinet repair reference and ask for its physical outcome and any linked unresolved service issue. Then change the location in a synthetic test and confirm that the identity remains consistent. Document manual reconciliation where no verified integration exists.
Start with GIS asset readiness before expanding into more detailed network requirements.
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.
