USE CASE · UTILITY CORRIDOR

Utility corridor: write inspection as a retrievable asset event

Corridors are a natural evidential scene for PipeGuardian. Multi-trade coexistence requires evidence, not overrule. Repeat inspection requires a stable segment key. Target capability remains unverified.

A utility corridor looks like a hallway. Operations are subcontracted by trade. A hot electrical joint, a water leak, a deformed comms tray, a corroded fire main — interpretation does not sit with one crew. If the product outputs a single “AI says there is a problem” score, the field cannot act. Correct output is: which segment, which asset class, which evidence, what confidence, who reviewed.

Shenzhen underground-utility data standards give a public mapping target. PG-Atlas should map codes and spatial fields from the first edition, even before flight scores exist. Data work can precede the prototype. That is a Hong Kong-side job in the HK–SZ split.

01

Before entry

Gas background, work permit, recovery path, Ex zones that stay forbidden.

02

In-gallery scout

Low-speed wall-follow on supports, leaks, temperature rise; weak-link map; interruptible.

03

Work order

Suspect clips enter a trade queue. Repair-before/after contrast returns to the same segment object.

If a cable sandwich or Ex zone inside the gallery has not been evaluated, the job must degrade or cancel. Flight capability does not override zoning rules.