Critical infrastructure runs on millwright.
Agents and tools for self-healing factories, plants and machine fleets.
- Cardinal Energy
- Ridgeway
- Torvik
- Northwind
- Evolution
- Aldren
Observability shouldn't be split across 5 tabs.
Support articles
RCP seal degradation
SOP-114 · Rev 6
Telemetry
CCW supply header
1CC-TE-0341
130.4°F
Tickets + work orders
Seal leak-off rising
MNT-4412 · CCW Pump 1B
Asset management
CCW Pump 1B
S/N 88-4471 · Unit 1
millwright.
01The platform
All you need to keep machine fleets running.
The digital twin, the telemetry, the ticket, and the support manuals, finally unified.
Real-time telemetry, historical archives and diagnostic data in one place. Measure, observe, and act on your assets with confidence.
Modern asset management, enriched with AI. A single source of truth for your assets, their relationships and their history, augmented with accurate metadata.
Tag resolution · Cardinal PI
11,904 of 12,480
- 1CC_TE_0341.PVEnriching…
- CCW.P1B.VIB_OBEnriching…
- PMP1B_RUNSTSEnriching…
- 1CC_FIC_0142.SPEnriching…
- CCW.P1A.VIB_OBEnriching…
- 1CC_PDI_0118Enriching…
- EDGB_FUEL_LVLEnriching…
- TT_0355_OLDEnriching…
Diagnose and troubleshoot with confidence. Investigate, analyze and act on your assets with AI-powered insights.
Investigating MNT-4412
Read the local gauge at the 1CC-TE-0341 test connection.
The gauge agrees, about 104 °F
The gauge reads normal
Visualize plant assets in 3D or 2D, and create site layouts and maps.
Manage work and maintenance with confidence. Track incidents, corrective orders and planned fixes, and ensure your assets keep running smoothly.
Triage
2In progress
2Done
2
Support manuals and servicing guides for every piece of equipment. Searchable in plain language by your engineers, customers or AI agents.
Knowledge
7 documents
ER-AA-330Fault guide
Reactor coolant pump No. 1 seal degradation
ARP 1-MB4 E-6Procedure
Annunciator response — RCP seal leak-off high
TS 3.4.13Reference
RCS operational leakage — limits and required actions
TS 3.8.1Reference
AC sources — operating
MA-AA-212Procedure
Validating a suspect RTD or thermocouple
SY-AA-118Reference
Condenser performance and circulating water fouling
HU-AA-104Safety
Clearance and tagging — safety-related equipment
ER-AA-330Fault guide
Reactor coolant pump No. 1 seal degradation
Applies toWestinghouse 93A-1Westinghouse 93AByron-Jackson N-9000
Limits — Westinghouse 93A-1 seal package
- Seal injection flow, per pump
- 6–10 gpm
- Injection filter ΔP
- < 20 psid
- No. 1 leak-off, normal
- 1.5–3.5 gpm
- No. 1 leak-off, annunciator
- 4.5 gpm
- No. 1 leak-off, Tech Spec limit
- 6.0 gpm
- Seal water outlet temperature
- < 175 °F
- Frame vibration, alarm
- 8.0 mils
- Package replacement, lead time
- 11 days
Integrate all your systems and data into one unified workspace. See your assets in context, and plan your work in one place.
- Overview
- Assets
- Alerts2
- Tickets5
- Telemetry
- Knowledge
Overview
Northwind Energy
Battery data link
Battery Bank A
BESS-A
- Manufacturer
- Fluence
- Model
- Gridstack 2.4
- Capacity
- 4.2 MWh
- Commissioned
- June 2023
HOW-BAT-002Procedure
Restarting the battery's modem
Applies toBattery StorageSierra Wireless AirLink RV55
Check the network light first
Hold the recessed reset for three seconds, then leave it alone: the lights cycle twice before the tunnel comes back. If the readings have not resumed in five minutes, the SIM has lost its provisioning — that is HOW-BAT-006, not a second reboot.
02Close the loop
From alarm to
fix in seconds.
Enrich your tag namespace, bring in telemetry and manuals from every vendor, then diagnose.
01
Name· Atlas
Atlas organizes tags, assets, and topologies into a single source of truth that everything else reads from.
Atlas02
Plot telemetry· Trace
Trace puts live and recorded signals on one timeline you can zoom.
Trace03
Diagnose· Diag
Diag lays out the case with an AI diagnostician that shows its work.
Diag04
Close· Docket
Docket turns the answer into work orders linked to the evidence.
Docket
Anywhere with machines that can break.
Data Centers
Chillers, CRAH units, UPS strings, generator sets
CH-01-CHWS-TT
Power & Energy
Coolant pumps, inverters and battery energy storage (BESS)
1CC-TE-0341
Oil and Gas
Pumps, compressors, valves, flow meters, process mimics
1CC-TE-0341
Water and Wastewater
Lift-station pumps, blowers, UV trains, chemical dosing
LS04-P-2A-VIB
Manufacturing
Presses, compressors, conveyors, spindles, downtime codes
LN3-PRS-01-PT
Vehicle Servicing
Fleet inspections, trouble codes, bay throughput, parts and warranty
DTC-P0420
03Integrations
Your data already exists. Millwright aggregates it.
The historian, the EAM, the procedures library, the shift channel. Millwright connects them into one picture, writes back where you allow it, and leaves every closure to a person.
A marketplace of connectors, and an SDK for the systems only your plant has.
Connected sources
Where this organization's readings, jobs and documents come from.
- Cardinal PIAVEVA PI SystemBackfilling 90 days of history for the 2R19 review12,480 tagsSyncing
- Cardinal EAMWrite-backIBM MaximoWork orders both ways, closures held for a personConnected
- Station proceduresSharePoint3 of 11 libraries returned 403Degraded
- Chemistry LIMS bridgePrivateConnector SDKBuilt in-house, v1.4.2Connected
35 more in the marketplace.
42 connectors, and an SDK for the rest
04Security
Security is the product.
Scoped access, a complete audit trail, encryption throughout, and your choice of where it runs. Check any of them in a demo.
Role-based access
Operator, engineer, planner, contractor, stakeholder. Roles come from your identity provider over SSO.
Fine-grained scoping
Permissions follow the asset hierarchy, down to a single unit, system or point.
Read-only by default
Every connector starts read-only. Write-back is per system, per field, and off until you turn it on.
Audit logging
Every action, access and approval is recorded, queryable and exportable.
Encryption
TLS on every hop, including to the historian. At rest with keys you can bring and rotate.
Cloud or on-premises
Hosted, in a single-tenant VPC in your own account, or on the plant floor next to the historian.
Never trained on your data. Nothing you is used for training.
Always approved by a human. Approving and closing stay human-controlled.
05One picture, one purchase
Everyone on the same page.
Four tools means four rollouts, four sets of credentials and four versions of what happened last Tuesday. The fault you are chasing usually lives in the gap between two of them.
Field engineers
Work the fault on a shared board with the agent. It brings the evidence, you bring the judgment.
Plant operators
Start the shift on the overview: output, capability, active alarms and open work.
Customers and stakeholders
Follow a site without standing in the control room, scoped to what they are allowed to see.
06Questions
Let's get you some answers.
Our historian has twelve thousand points and three naming conventions. What actually happens?
A resolution pass reads point names, descriptors, units, ranges and whatever hierarchy exists, and proposes an asset for each point with a confidence you can see. Expect roughly one point in six to come back ambiguous, undescribed or long dead. Those go to an engineer rather than being guessed at, and each correction applies to the rest of the site. This is the part with real hours in it, and we would rather you budget for it than be surprised.
Does our data leave the plant?
We offer both cloud and on-premises options. Data is only transferred if you decide it should be. Run it hosted, in your own cloud account, or on-premises next to the historian. Model inference is the one step that can cross the boundary, and where it runs is a setting rather than an assumption. Nothing you connect trains anything.
What happens when the agent is wrong?
Every claim carries its evidence: the telemetry, the ticket, and the support article behind it, so a conclusion you disagree with is one you can see the working for and delete. It cannot close a ticket, write back a closure or sign anything. And where the telemetry does not decide, the run stops and asks rather than picking.
Does this add to our alarm load?
It should reduce it. Related alarms group into one investigation, so a flood arrives as one row rather than nine, and Millwright raises no alarms of its own. It does not replace your alarm management system or write to the DCS.
Who has to sign off to run a pilot?
For the first one: whoever can approve read-only access to the historian, plus an engineer with a few afternoons for tag review. We keep the opening scope inside one person's authority on purpose. A rollout that needs the historian, the CMMS, the procedures library and the control room to all agree first is not a pilot, it is a program, and programs are how the last ten years went.
How long does a first deployment take, and what do we need to have ready?
Weeks rather than quarters for one system, read-only. The long pole is tag review. What it needs from you: read access to the historian, somebody who knows the plant well enough to correct a mapping, and somewhere to run. What it does not need: a data migration, a change to your CMMS, or anything touching the control system.
See it running on your own plant.
We are onboarding a small number of operations teams. Three questions, and we will be in touch.