The data cockpit for electrical commissioning
MC · Punch · PAT · FAT · AI Weekly Report — one closed loop.
From TagMaster master data to subsystem RFCC READY, every step in the electrical discipline is digital and traceable.
Five sub-modules, one commissioning spine
All five sub-modules orbit a single spine — subsystem RFCC READY. They stay decoupled in implementation but their data is fully unified.
MC Inspection
Covers MC inspection for every electrical equipment & cable; subsystem RFCC aggregated live, punch categories synced automatically.
Punch Tracking
Every Punch item bound to an owner + due date, AgingDays color-graded, closure state feeds back into MC instantly.
PAT Inspection
17-field patrol inspection record, independent of MC, open/close opinion tracking — the standard intake for defects found on patrol.
FAT Acceptance
18-field vendor acceptance record with vendor info and conclusion. Standalone loop that does not affect RFCC.
AI Weekly Report
Drafts the weekly progress report, with week-over-week trends, from the platform's own figures using an AI model from Anthropic. AI output can be incomplete or wrong, so the team reviews and edits it before it goes out.
Four-layer data architecture
TagMaster → Equipment/Cable → MC/Punch/PAT/FAT → Subsystem RFCC. Every layer is an independently verifiable source of truth.
Layer 1 · TagMaster
Unique tag codes for all equipment & cables; TagNo is the mutable business key, internal tag_id is immutable
Layer 2 · Equipment / Cable
Instance records of equipment & cable lists, bound to TagNo and subsystem
Layer 3 · MC / Punch / PAT / FAT
Four independent process records, decoupled but linked through TagNo
Layer 4 · Subsystem RFCC
Ready For Commissioning Certificate status — aggregated automatically, never hand-filled
Real product screenshot · live production build, ship identifiers redacted
Key numbers
Real product screenshot · live production build, ship identifiers redacted