Prepare a small, trustworthy asset register before a Unity Maintain pilot: stable identifiers, usable locations, meaningful asset types and clear ownership matter more than filling every optional attribute. The worksheet below is a proposed readiness test, not an official minimum schema.
Why check identity before adding more fields?
Legacy Cityworks integration guidance requires asset configuration and describes the need to reconcile layer names and aliases for inspection templates. This illustrates why a layer that looks correct to a map reader still needs application-level validation. Verify the equivalent requirements for your version. Trimble asset configuration guidance.
A compact data dictionary
| Proposed field | Meaning | Readiness check |
|---|---|---|
| Asset ID | Stable business identity | Unique within its agreed scope; never recycled casually |
| Asset type | What the crew maintains | Uses agreed codes, not inconsistent free text |
| Geometry | Where the asset is represented | Correct layer and coordinate reference; confidence recorded |
| Owner / custodian | Who resolves discrepancies | Named role or team, not an empty department label |
| Lifecycle state | Existing, retired or proposed | Retired equipment is not assigned new routine work |
| Verification record | Who checked which fact and when | Unknown values remain distinguishable from verified values |
This is a planning dictionary. Do not rename production fields to match it without analysing integrations and existing identifiers.
Worked review: three valve records
In a synthetic sample, V-201 appears twice with different coordinates, V-202 has no verified location and V-203 is retired but still included in the proposed inspection list. Record three different decisions: resolve the duplicate identity with the data steward, arrange location verification for V-202, and remove V-203 from routine assignment while retaining its history.
Do not delete one V-201 row simply because the ID repeats. It may be a duplicate record, an incorrectly labelled second valve, or a replacement whose history was not separated. The correct action depends on evidence. Keep a reconciliation log with the source records, decision and reviewer.
How do Arabic and English labels affect the register?
Keep a stable stored code for a type or status and agree on its Arabic and English display meanings. For example, “location unverified” must not be translated into “asset missing.” These states imply different field actions. Test the labels with someone who will assign work and someone who will locate the asset.
What constitutes a pass?
A pilot subset passes when the team can select the intended asset, recognise uncertainty, assign its correction and retrieve linked work without ambiguous identity. Missing optional attributes can have a completion plan; unresolved identity is a reason to narrow the subset.
Review Survey123 versus Field Maps for inspections when choosing how to collect corrections. A successful upload alone does not establish that the register is ready for maintenance decisions.
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.
