Explore the comprehensive ArcGIS Asset Management Template, designed for efficient data collection, analysis, and reporting, enhancing asset visibility and planning.
1
Define asset change scope
2
Confirm data model requirements
3
Prepare field collection environment
4
Capture asset identity details
5
Record location and geometry
6
Inspect condition and evidence
7
Validate attributes and classifications
8
Check spatial data quality
9
Reconcile duplicates and lineage
10
Resolve data quality exceptions
11
Publish or update ArcGIS record
12
Verify access and audit controls
13
Confirm operational usability
14
Approval: GIS data steward
15
Close change and schedule review
Define asset change scope
Establish the exact asset record and decision owner before any GIS edit. Confirm whether this run creates, updates, inspects, or retires an asset, and tie it to an accountable data steward. Use the authoritative work request or asset register; do not infer identifiers from labels or map symbols.
1
New asset record
2
Attribute update
3
Geometry update
4
Inspection update
5
Retirement or disposal
1
Building or facility
2
Linear infrastructure
3
Equipment or device
4
Vehicle or mobile asset
5
Land or grounds
6
Utility network asset
Confirm data model requirements
Identify the authoritative ArcGIS layer, schema, spatial reference, and identifier policy before collection begins. Compare the requested change with the current data dictionary and coded-value domains. Escalate schema changes instead of inserting free-form values that bypass governance.
Prepare field collection environment
Prepare the map and device for reliable field work. Confirm editing, offline use, GlobalIDs where offline workflows require them, the relevant map area, and the location profile or datum transformation. Set the accuracy threshold from the project specification, not from a generic default.
1
Continuous online
2
Intermittent online
3
Offline map area
4
Air-gapped transfer
5
Office-based editing
1
Ready and tested
2
Ready with limitations
3
Not ready
4
Not required
5
Blocked pending configuration
Capture asset identity details
Capture the minimum identity and lifecycle attributes that make the asset traceable across operational and financial systems. Reuse the governed identifier and classification; never create a second identifier because a record is difficult to locate. Record the lifecycle state that is true at the time of this change.
1
Planned
2
Acquired or constructed
3
Active service
4
Temporarily inactive
5
Under renewal
6
Retired or disposed
1
Critical
2
High
3
Moderate
4
Low
5
Not yet assessed
Record location and geometry
Capture or update geometry using the approved spatial reference and location method. For GNSS collection, wait for the project accuracy threshold and use the configured location profile when a datum transformation is required. If the threshold cannot be met, preserve the measured accuracy and document the exception rather than presenting the position as verified.
1
Point
2
Line
3
Polygon
4
Nonspatial table record
5
Mixed geometry collection
1
Integrated device GNSS
2
External high-accuracy GNSS
3
Survey control measurement
4
Digitized from authoritative source
5
Existing geometry retained
Inspect condition and evidence
Inspect the asset at the effective date of this run and capture evidence proportionate to its criticality. Use the organization’s condition scale where one exists and note safety or service issues separately from cosmetic observations. Attach clear photos or documents without personal or sensitive data.
1
Excellent
2
Good
3
Fair
4
Poor
5
Failed or unusable
6
Not inspected
1
Safety hazard
2
Service interruption risk
3
Structural damage
4
Corrosion or wear
5
Access obstruction
6
Label or identity mismatch
7
No issue observed
Validate attributes and classifications
Validate required values, coded domains, relationships, and business rules before publication. Use immediate constraint rules for invalid edits and deferred validation rules for broader quality checks where the platform supports them. Review every reported error and record whether it was corrected or accepted as a governed exception.
1
Passed
2
Passed with notes
3
Failed
4
Not applicable
5
Blocked pending source data
1
Passed
2
Passed with approved exception
3
Failed
4
Not configured
5
Not applicable
Check spatial data quality
Check geometry against project accuracy, topology, network connectivity, and surrounding authoritative features. Inspect errors at an appropriate scale and distinguish a true defect from an approved real-world exception. Re-run validation after corrections so resolved errors are cleared.
1
Passed
2
Passed with notes
3
Failed
4
Not applicable
5
Blocked pending reference data
1
Passed
2
Passed with approved exception
3
Failed
4
Not configured
5
Not applicable
Reconcile duplicates and lineage
Search the authoritative layer and related systems for duplicate identifiers, coincident features, or parallel records. Confirm the source and transformation history so the record can be traced back to its origin. Merge or retire duplicates only under the organization’s retention and stewardship rules.
1
No duplicate found
2
Potential duplicate
3
Confirmed duplicate
4
Duplicate resolved
5
Not applicable
Resolve data quality exceptions
Resolve failures from attribute, spatial, duplicate, or synchronization checks before approval. Correct the source record where possible, re-run the affected validation, and preserve evidence of the correction. If an exception must remain, name the accountable approver, risk, and time-bound follow-up.
1
Attribute validation
2
Spatial accuracy
3
Topology or connectivity
4
Duplicate identity
5
Offline synchronization
6
Access or audit control
1
Corrected and revalidated
2
Accepted temporarily
3
Accepted permanently
4
Rejected for rework
5
Escalated for decision
Publish or update ArcGIS record
Apply the approved edit to the authoritative feature layer using an account with only the required privileges. Preserve GlobalID and relationship integrity, avoid direct SQL changes that bypass geodatabase behavior, and confirm offline edits are synchronized. Record the final feature identity and edit result.
1
Created new feature
2
Updated attributes
3
Updated geometry
4
Added inspection record
5
Retired existing feature
1
Synchronized successfully
2
Synchronized with warnings
3
Failed
4
Not required
5
Pending controlled retry
Verify access and audit controls
Verify that editing, viewing, attachments, and audit history match the intended audience. Prefer editable hosted feature layer views when different groups need different access, and confirm editor tracking records authenticated creators and editors. Do not expose sensitive attributes through a broadly shared view.
1
Enabled and verified
2
Enabled not verified
3
Disabled
4
Not permitted
5
Not applicable
1
Named editors only
2
Regional editable views
3
Organization read access
4
Public read-only view
5
Restricted administrator access
1
Enabled and tested
2
Enabled not tested
3
Disabled by policy
4
Not supported
5
Not required
Confirm operational usability
Test the updated record in the map and workflow used by field and office teams. Confirm symbols, forms, searches, related records, and offline synchronization behave as intended. Capture a rollback or correction route before handing the change to the data steward.
1
Passed
2
Passed with notes
3
Failed
4
Not applicable
5
Blocked by environment
1
Passed
2
Passed with notes
3
Failed
4
Not applicable
5
Blocked by environment
1
Accepted
2
Accepted with notes
3
Rejected
4
Not required
5
Pending stakeholder review
Approval: GIS data steward
Will be submitted for approval:
Define asset change scope
Will be submitted
Confirm data model requirements
Will be submitted
Prepare field collection environment
Will be submitted
Capture asset identity details
Will be submitted
Record location and geometry
Will be submitted
Inspect condition and evidence
Will be submitted
Validate attributes and classifications
Will be submitted
Check spatial data quality
Will be submitted
Reconcile duplicates and lineage
Will be submitted
Resolve data quality exceptions
Will be submitted
Publish or update ArcGIS record
Will be submitted
Verify access and audit controls
Will be submitted
Confirm operational usability
Will be submitted
Close change and schedule review
Close the change only after steward approval. Summarize what changed, retain the evidence reference, and set a review date based on asset criticality, condition, and organizational policy. Record any follow-up work as a separate controlled request rather than leaving the GIS record in an ambiguous state.
Optional cookies and similar technologies support analytics, advertising and visitor identification, and embedded content. Change or withdraw consent in Cookie settings. Cookie policy.