Asset Operations
Asset Operations Center
Track hydrants, manage sewer assets, and coordinate field work from one shared operations workspace.
Current Focus
No asset selectedSelect a hydrant or sewer line from the map or registry to inspect details and route follow-up work.
Search & filter
Asset Explorer
Page 1
Use search or saved view to narrow operational focus.
Live inventory
Assets List
The table mirrors the current saved view, sort order, and operational filter.
| Asset ID | Type | Status | Open WOs |
|---|
No assets match current filters.
0 critical faults
Live map workspace
Needs Service
In Service
Sewer Lines
Manholes
Field posture
Operations Dashboard
Watch backlog, urgency, and completion health before crews fan out.
- 0 Open Work Orders
- 0 In Progress
- 0 Overdue
Immediate actions
Today’s Priorities
No urgent items right now. Use the shortcuts above to move from overview to action.
Shift playbook
Supervisor Rhythm
- Start with backlog risk Review overdue work orders first, then confirm today’s crews, vehicles, and call coverage.
- Validate inspection spillover Failed inspections should either create a follow-up work order or be explicitly deferred with notes.
- Watch cross-team pressure Water, sewer, and hydrant work share field capacity. Keep the mix balanced before the afternoon dispatch push.
Coverage model
Operational Guardrails
Dispatch lanes
Work Orders Board
Operational board view for dispatch and completion tracking.
Open
Unassigned backlogNew requests appear here until a crew or owner picks them up.
In Progress
Field work underwayActive repairs and site visits move into this lane once crews begin work.
Completed
Ready for closeout reviewFinished work lands here before reporting and handoff.
No work orders yet. Create one from the asset workspace to start dispatching.
Dispatch defaults
Routing Guardrails
- Open Needs assignment, scope confirmation, or triage.
- In progress Field crew acknowledged and work is active.
- Completed Repair done, awaiting reporting or quality review.
Crew cadence
Assignment Rhythm
Template workflow
Inspection Templates
Capture standardized field evidence, validate checklist completion, and push follow-up work without re-entering asset context.
Quality controls
Inspection QA Snapshot
- 0% Average Quality
- 0% Fail Rate
- 0 Auto Follow-ups
No QA flags detected.
Trend watch
Inspection Compliance Trends
No inspection trend data yet.
Template adherence
Template Compliance
No template compliance data yet.
Field history
Recent Inspections
No inspections recorded yet.
Operational Analytics
- 0 Active Backlog
- 0 Completed (7d)
- 0% Overdue Rate
Backlog Aging
No active backlog aging data.
Crew Throughput
No crew throughput data yet.
Asset Type Load
No asset-type workload data yet.
SLA Risk Buckets
No SLA risk data yet.
4-Week Closure Trend
No recent closure trend data yet.
Admin ingest
Data Imports (Admin)
MVP rule: import Hydrants.geojson into Supabase if
you need editable/searchable hydrants. Keep sewer mains,
manholes, valves, and the other large GIS layers as hosted
GeoJSON files.
No import runs logged yet.
Import rules
Recommended Source Handling
- Hydrants Import into Supabase when the layer needs editing, search, or field updates.
- Large GIS layers Keep mains, valves, and boundaries as hosted GeoJSON unless crews need direct write access.
- Validation notes Record transforms, source dates, and QA assumptions inside each import run.
Operational model
Layer Strategy
Access matrix
Role Matrix (Admin)
| Capability | Viewer | Editor | Admin |
|---|---|---|---|
| View assets and maps | Yes | Yes | Yes |
| Update status and notes | No | Yes | Yes |
| Create assets and configure layers | No | No | Yes |
| Access imports and admin settings | No | No | Yes |
Workflow controls
Operational Settings
No settings updates yet.
Governance
Control Notes
- Viewer devices stay read-only Shared tablets and supervisor kiosks should never expose edit or import paths.
- Editors own field truth Asset status, notes, and inspection evidence should map to a named operator for accountability.
- Admin changes need context Imports, SLA changes, and automation rules should include a written rationale before rollout.