CoreSynaptics Coresynaptics
DEMO ORG
L1RED TAG
FAT
L1
L2YELLOW TAG
Receipt Inspection / SIP
L2AL2BL2CL2D
L3GREEN TAG
Energization and Startup
L3
L4BLUE TAG
Functional Testing
L4
L5WHITE TAG
IST & Acceptance
L5
L6SLATE TAG
Clean walk + handover
L6

CX FLOW GUIDE

How to read the spine — the rules that govern it, not the diagram.

THE RULES · ENFORCED, NOT DOCUMENTED

Gates are order-free. Energizing is not.
Clear L1–L2D on any asset in any sequence. L3 is the exception: an asset only energizes once everything upstream of it on the one-line is live.
Evidence enables, authority executes.
Documents and readings open a gate; a named role signs it. Collapsing the two is how a gate becomes a rubber stamp.
The verifier is never the fixer.
Whoever did the work cannot be whoever proves it was done. The same rule governs LOTO release and every rung of the checklist ladder.
A failed line is not bypassable.
Bypass covers the ABSENCE of a document, never a failure. A failed line must be fixed and re-verified.
Nothing auditable is deletable.
Findings, completed checklists and test attempts are voided with a reason, never removed. Voided records stay queryable.
The checkmark is created last.
Evidence first, verdict after. That ordering is what makes the turnover package a byproduct rather than an assembly job.

WHAT EACH RUNG ASKS FOR · L1 → L6

GATEMEANSREQUIRES
L1FATGear received and inspected against the submittal.
L2AReceipt Inspection / SIPAnchored, aligned, Ready-to-Receive cleared.
L2BInstallation VerificationTerminations, torque, pressure and megger results filed.
L2CPre-Energization InspectionIndependent walk by the commissioning authority.
L2DAuthorizedFOD walk, tamper seal, NTE issued, briefing held.
L3Energization and StartupUpstream live, authorization signed, sequence respected.
L4Functional TestingLoad bank, failure modes, system-level behaviour.
L5IST & AcceptanceIST across systems, with the customer present.
L6Clean walk + handoverPackage accepted — findings disclosed, not hidden.
A gate is not a date. It opens when the record says it is ready, which is why a schedule and a readiness position can disagree — and why that disagreement is the most useful number on the job.