CoreSynaptics Coresynaptics
DEMO ORG—
L0RED TAG
Design Basis / Submittals
L2YELLOW TAG
Receipt Inspection / SIP
L3GREEN TAG
Energization and Startup
L4BLUE TAG
Functional Testing
L5WHITE TAG
IST & Acceptance
L6SLATE TAG
Clean walk + handover

Demo Control Room

Run the sales demo in twenty minutes

Run this in twenty minutes

Six beats, in order. Each one opens a live page of the demo workspace with seeded records behind it — the asset register, checklists, findings, gates and team companies all reference the same project, so nothing has to be hand-waved.

The data is sample data on a fictional campus. Demo workspaces are removed after a few days.

0–2 min

1. Open on the one screen that says what to do today

Open →

“This is what the project lead sees first thing — not a wall of charts, a list of what is owed and by whom.”

  • What needs attention now — each row names the owner and the page that clears it
  • Hard gates — what is physically blocked right now and why
  • The stage ladder and the audit trail behind every number
Why it lands: The system takes a position on priority instead of leaving it to whoever shouts loudest.
2–5 min

2. One asset register, every asset on its own rung

Open →

“Twelve assets on a live build — some still on order, some received, some set and terminated, one ready to energize.”

  • Procurement and readiness status per asset (OFCI vs CFCI)
  • The checklists each asset carries for the stages it has reached
  • Owner-furnished generators and who installs them
Why it lands: Procurement, install and commissioning are one record, not three spreadsheets.
5–8 min

3. Checklists that know whose line it is

Open →

“Every line names its responsible party — GC, EC, the vendor, NETA, the CxA — so a checklist is a hand-off, not a form.”

  • L1 factory tests, L2A receiving, L2B installation and RTE walk-downs
  • Lines owned by another company are theirs to answer
  • Evidence and readings where the line demands them
Why it lands: A checkmark cannot exist without the party that owns it.
8–12 min

4. Findings that hold the stage they belong to

Open →

“A UPS battery string out of tolerance is not a note in a meeting — it is a finding on that asset, and it holds that asset.”

  • Open findings by severity, each on its asset
  • Who it is assigned to and what clears it
  • The punch item next to the high-severity one — same register
Why it lands: Quality issues surface where the work is, before it is covered or energized.
12–16 min

5. Readiness that refuses to lie

Open →

“Ready-to-energize is derived from the record — nobody can declare it.”

  • Gate status per asset and what is still missing
  • The finding from beat 4 holding its asset
  • Turnover as accepted evidence, not a folder of PDFs
Why it lands: The answer to “can we energize Saturday?” is computed, and it is auditable.
16–20 min

6. Every company on one project, in separate lanes

Open →

“Log in as the CxA, the electrical contractor, the OEM or the owner with the passwords below — each company sees the project through its own seat.”

  • Team companies with their trade scope, each accepted by its own admin
  • Switch seats and watch page access change
  • A refusal: a member company cannot change another company's scope
Why it lands: Separation of duties is enforced by the server, which is what makes the record defensible later.
Demo logins
How to close
  • Point at the open high-severity finding and ask what it costs them today when it is found at IST instead of at installation.
  • Ask what their current answer is to “is this ready to energize” and how long it takes to assemble.
  • Offer to set up their own company and first project — registration takes minutes and the demo becomes their job.