Module tour

Every module says whether you can open it today.

This page used to sort the product into three build phases, and the phases collapsed faster than the copy did — nine of seventeen markers were describing something that no longer existed. A marker maintained by hand against a moving build always ends up behind it, so there are two states now and no third: live means a routed screen and a running service, and spec means designed and not built.

Live — you can open itSpec — designed, not builtNothing in between

22 you can open. One that is honest about not existing.

Each one is a service with its own boundary, publishing into the same event bus and the same dimension spine. Nothing here is a tab on something else.

live01Machine ledgerThe standard OMS sheet itself, populated from live records — every component, every week, the plan and what landed on it — and printable as an A2 audit document.

live02Breakdowns & EWOA ten-tab workbook in the order the plant already knows it: six MTTR phases, 5W1H, five parallel 5-Why chains, a three-level cause, countermeasures with owners.

live03Work order engineOne execution model for every work type, with four independent P/D/C/A flags and a mandated standardization output.

live04Machine health boardPlant → shop → line → machine, worst first. Green has to be earned by a measurement; everything unmeasured is grey and says “not monitored”, never “fine”.

live05CBM adoption registerWhich machines should stop being time-based, ranked by what their breakdowns actually cost — and it will not accept a condition parameter with no numeric limit.

live06Spares & requisitionsAn append-only stock ledger under the spares master, with min/max policies that raise work instead of emails.

live07Sensors & condition monitoringReadings arrive over MQTT on a tenant-keyed topic; a threshold breach raises a work order carrying its readings. The trend scopes to one machine from the board.

live08Technician & operator surfacesThe line incharge’s own screen, the shift inbox and the capture flow — scan, checklist, photo, sign-off — in English, Hindi and Marathi.

live09KPIs, reports & the libraryMTTR, MTBF, availability and PM adherence materialised at leaf grain from events; every rollup sums its children, and the report library holds what was run.

live10The WCM agentSuggest-only checks on the event bus, each rendering the inputs, the threshold and the citation it used. Ten deterministic rules and one LLM judgment check.

live11Excel and PDF, both waysWorkbooks in as validated imports with a per-row report; thirteen registers back out as real Excel — typed cells, frozen headers, and provenance in row one.

live12Reliability & step roadmapsPQCDSM criticality to an AA/A/B/C class, seven-step pillar roadmaps audited against evidence, and TBM frequency argued from MTBF − 2σ.

live13DC tools & calibrationSerialized torque tools, e-signed parameter changes, capability-gated swaps, and a calibration gate that closes overdue certificates in the same transaction.

live14EnergyVectors metered on the org tree, virtual meters with a reconciled residual, and EnPI baselines locked per CD-year.

live15Quality — QA, X, QMThe three matrices as data rather than images, with Q-points scheduled and PDCA-tracked like maintenance work, and audit runs that score and export.

live16SafetyS-EWO on the breakdown pipeline, S-Tags and observations with an SLA, JSRA and HERCA as versioned records.

live17Cost deployment & the rate masterFour named cost terms that reconcile to the paisa, over rates finance sets by effective date and nobody edits — superseding is an insert, enforced by a trigger.

live18Blue room & kaizenPillar boards built from live records, kaizen raised against a valorised loss, and savings that have to reconcile before they count.

live19People, ladders & competencyA twelve-rung shopfloor ladder beside a management one, rosters before sessions, OJT observation, and a level a classroom is not allowed to grant.

live20Early equipment managementStep-gates, design reviews that must consult MP-Info, and a handover no asset passes half-ready.

live21Controlled documentsThe register an auditor asks for second: what is controlled, at which revision, approved by whom, and what it is attached to.

live22Plant setup & provisioningNine administration screens, including a setup checklist read from the plant’s own data rather than a wizard — so it stays honest long after the first week.

spec23ERP adaptersA separate deployable next to your ERP owning mapping, retries and reconciliation, so connector complexity never reaches the domain. SAP codes already validate as reference fields; the adapter itself is not built.

Counted from the list above rather than typed underneath it — the hardcoded count is the thing that went stale last time. Verified against the running application on 11 August 2026.

The record everything hangs on

The machine ledger is the system of record, not a report you generate.

And it is the sheet your auditor already reads — the standard OMS layout, populated from live records, printable at A2.

When a WCM assessor asks how the plan evolved, the answer is one screen.

The plan comes from it: Fifty-two week cells per component — TBM, CBM, hour-based, AM and QM check points — where marking a week executed or missed, or moving a plan with a reason, happens in the cell itself.
The breakdown lands on it: The stoppage is recorded on the row that owns the component, next to the plan it interrupted.
The frequency change is logged against it: Old → new with its evidence, and the approval spawns the horizontal-deployment task automatically.
The cost sheet is derived from it: Not maintained beside it in a workbook that disagrees by the end of the quarter.
It says when it cannot be drawn: On a small phone the sheet does not pretend: it hands back a plain grid and a sentence asking for a larger screen, rather than a broken document an auditor would have to argue with.

Deliberately out of scope

Things we are not going to pretend to be.

More on the residency model and how support access actually works on the company page.

Not a WMS: The logistics pillar carries material-flow losses and step claims on the loss and programme registers. Warehouse management and advanced planning stay where they are.
Not an ERP connector inside the core: No service reaches into another’s tables, mirrors are read-only, and SAP codes validate as reference fields on the ledger today. The adapter that would speak to SAP is designed and not built — it is on the pricing page as an add-on that says so.
Not a PLC driver vendor: A hundred and fifty PLC drivers are a solved problem. The edge boundary is JSON over MQTT on a tenant-keyed topic; we own the data model, not the fieldbus.
Not a god-mode admin console: Customers self-serve users, org tree, masters, roles, career ladders and approval chains across nine admin screens. The gateway strips a vendor operator token off every inbound request exactly as it strips a tenant id, so vendor authority cannot reach a cell from outside it at all.

See it against your plant

Bring one machine and one bad month.

Book a plant walkthrough Pricing & tiers

Bring the ledger for a machine you argue about, and the breakdown history behind it — we will walk the EWO loop and the frequency logic against your own data, and you can judge whether the method holds.