Commissioning Management Software | CxSTAT GO

The problem

The record is scattered.

Checklists in one tool, test sheets in spreadsheets, photos in chat, signatures on paper. Nobody holds the whole picture, so nobody can prove it.

scatter_plot

Fragments everywhere

Every trade and vendor keeps its own version of progress. Reconciling them is a full-time job that still misses things.

percent

Percent complete lies

Counting signed sheets says 92%. It cannot say whether the next test will hold, because the evidence behind the number is unstructured.

history

Evidence arrives too late

The turnover package gets assembled at the end, when it is too late to fix what is missing. Gaps surface in front of the client.

Inside CxSTAT GO

Everything captured once, structured forever.

Six modules write one record. Every entry lands on the Turii ontology, so CxSTAT IQ can read it and CxSTAT Vault can prove it.

inventory_2

Equipment Registry

Every tagged asset with its level ladder from L1 to IST, locations, systems and dependencies. The spine the rest of the record hangs on.

checklist

Checklists & Templates

Template-driven checklists deployed across hundreds of assets at once, scored line by line, with photos and readings attached where the work happened.

verified

Functional Tests & Witnessing

Structured test execution with performer and witness signoff. Who tested, who witnessed and what the readings were, recorded as data, not scans.

bug_report

Issue Log

The full issue lifecycle with evidence-based closure. Every issue is linked to its equipment and system, and feeds Issue Intelligence in CxSTAT IQ.

photo_camera

Field Capture

Guided execution on site. Readings, photos and signoffs stream back as structured evidence, including site conversations via Field Intelligence.

smart_toy

AI Operations

39 commissioning-shaped tools over MCP. AI agents raise issues, find blockers, deploy checklists and draft reports. People keep signoff authority.

Platform depth

The mechanics that make it a system of record.

Under the six modules sits production software built for real programs. These are the details commissioning teams feel every day.

Sign-off gates on every status change

An equipment item cannot advance to its next status until the gate for that status clears: every checklist tagged to it closed, the latest test attempt passed with performer and witness signoff, and every mandatory document approved. A blocked attempt does not fail silently, it lists exactly what is outstanding, and the gate clears itself as requirements close.

EquipmentNG1 · CRAH-02-01

CRAH-02-01 L3 · Functionalarrow_forwardL4 · Loaded

blockCannot change status. Requirements not met.

closeL3 functional checklist · 2 of 44 lines still open

closeTest FT-CRAH-021 · awaiting witness signoff

checkCalibration certificate · approved

The gate is enforced in the database transaction, not in the UI.

Configurable equipment statuses

Every project defines its own equipment lifecycle in settings: status names, colors and workflow order, with closed states marked explicitly. Run the classic L1 to IST ladder or the owner’s own gate structure. The same configurability covers checklist, test and issue statuses, so the platform adapts to the program, not the other way round.

Project SettingsEquipment statuses · workflow order

⋮⋮1Delivered

⋮⋮2Pre-functional · L2

⋮⋮3Functional · L3

⋮⋮4Loaded · L4

⋮⋮5IST readyClosed

addAdd status

@ mentions in issue comments

Type @ in any issue comment and pick from the project’s members. The mention is stored against the person, not just the text: they are notified instantly with a deep link to the issue, and their name renders as a live reference in the thread. Chasing happens inside the record, where the evidence already is.

Issue NG1-03Comments (4)

DWD. Whelan· Cx Manager · 2h ago

Replacement actuator fitted and stroking full range. @P. Nair can your team re-verify the panel before the witness slot on Thursday?

Confirmed for Thursday. Looping in @M

MBM. Bianchi · BMS Engineer · Apex Controls

MRM. Rossi · QA Lead · Meridian Mechanical

Live in-app notifications

Notifications are pushed over a persistent live stream, no refresh needed: mentions, assignments, sign-off requests and changes to items you watch. The bell updates in real time across every open tab, and each entry deep-links to the exact issue, test or equipment item it refers to.

Northgate DC1NG1notifications3

Notifications3Mark all read

alternate_email

D. Whelan mentioned you in a comment on NG1-03 · damper actuator

5m ago

assignment_ind

You were assigned witness on FT-CRAH-021 · functional test

32m ago

inventory_2

Watched item CRAH-02-01 advanced to Loaded · L4, gate cleared

1h ago

How it fits

GO writes. IQ reads. Vault proves.

CxSTAT GO is the execution layer of one platform. What it records, the rest of CxSTAT understands.

edit_square

CxSTAT GO writes the record

Checks, tests, signoffs, issues and evidence land once, structured against the Turii ontology, never retyped.

insights

CxSTAT IQ reads it

The readiness intelligence layer answers what is ready, what is at risk and when the program will finish, from GO or from incumbent tools.

home_storage

CxSTAT Vault proves it

The document intelligence engine reads drawings, certificates and reports, and links every claim to its source.

hub

Turii underneath

One ontology spans all three, so a tag in the field means the same thing in the forecast and in the turnover package.

Common questions

Frequently asked.

What is CxSTAT GO? add

CxSTAT GO is commissioning management software for data centers and critical infrastructure. It is the execution platform and system of record: equipment, template-driven checklists, functional tests with performer and witness signoff, the issue lifecycle and field evidence live as one structured record, from L1 checks to integrated systems testing.

Does CxSTAT GO replace CxAlloy TQ or Facility Grid? add

Only if you want it to. CxSTAT GO is ODUM AI's own execution platform for teams that want an AI-native record end to end. Teams already running CxAlloy TQ or Facility Grid can keep them: CxSTAT IQ connects to those tools and adds the readiness intelligence layer on top, no migration required.

How does CxSTAT GO work with CxSTAT IQ and CxSTAT Vault? add

CxSTAT GO executes and writes the commissioning record. CxSTAT IQ reads that record and answers what is ready, what is at risk and when the program will finish. CxSTAT Vault reads the document trail and proves it, linking every fact to its source. All three speak the same Turii ontology, so nothing drifts between them.

Can AI agents operate CxSTAT GO? add

Yes. CxSTAT GO exposes 39 commissioning-shaped tools over MCP, so AI agents can raise issues, find blockers, deploy checklists and generate reports directly. Authority stays with people: witnesses and commissioning authorities keep signoff, the system keeps the evidence.

Still have questions? We’re here to help.

Book a Demo arrow_forward