Every transaction is a sensor reading.
The atom everything is built from. One record, written at the point of work, that every report, replenishment and compliance artefact is derived from — and that your ERP was never built to capture.
Under your ERP, not beside it.
acuitystore® is operational technology. It lives on the floor, at the point of work, below the systems that plan and account for the work. It does not hold your financials, it does not run your purchasing, and it is not trying to become your system of record. It writes the event — and then feeds it upward.
| Layer | What it holds | What it takes from the layer below |
|---|---|---|
| Plan & account ERP / MRP | Purchase orders, valuation, general ledger, planned demand, supplier terms. | Attributed consumption, reorder signals, cost-centre and job allocation — as movements, not as a monthly reconciliation. |
| Execute CMMS / MES / work management | Work orders, permits, maintenance plans, competency matrices. | Confirmation that the item actually reached the job, issued to a qualified person, in date. |
| Control at the point of work acuitystore® — OT | The transaction record. Issue, return, restock, gate, hold, override. | The raw observation, resolved into an event with a person, a job and a condition against it. |
| Sense the point itself | Card reader, load cell, coil motor and vend sensor, scanner, camera, date and calibration status. | — |
Your ERP holds a balance. acuitystore holds an event. An ERP can tell you that 240 cut-off discs were consumed last month against a cost centre. It cannot tell you that four of them left Crib B at 06:04:11 against WO 44182, issued to T. Kowalski, or that a gas monitor was held at issue eight minutes later and released under a named override. That granularity is the difference between a number you can defend and a number you can only assert.
The two layers fail differently, and that is the clearest test of which one you are looking at. An ERP that is unavailable delays a transaction. An OT system that is unavailable stops the work. That is why every point and peripheral holds its own copy and reconciles rather than queuing on a server, why Severity-1 cover is 24×7×365 on every service tier including the smallest, and why a life-safety gate fails closed rather than open.
We are not an ERP and we are not a CMMS, and we are not going to become either. If you want one system to hold valuation, run purchasing and be the record of stock on your balance sheet, we are the wrong tool, and you will hear that from us in the first conversation rather than the third. What we do well is give that system better inputs than it has had before.
One consequence worth naming early: because this is operational technology bought by operations but running on your network and holding personal information, it lands in the gap between the two governance regimes. That is deliberate on our part — it is why there is a security and data page written in the language your reviewer uses, rather than a logo.
What the platform actually does.
| Capability | What it means in practice |
|---|---|
| The transaction record | Every issue, return and restock — who, what, where, quantity, against which job, in what condition, with the running balance. Exactly as logged, exportable at any time. |
| Item master | Built with you from whatever you have. Unit weights, pack quantities, regimes, criticality. Machine-readable and yours. |
| People & credentials | Who may take what, verified at issue. Standard reader families — HID, Gallagher, barcode, PIN — or a customer-supplied reader integrated to the point. |
| Additional capture | Capture more than the standard fields without programming — work order, cost centre, permit, asset number, whatever the site actually needs to attribute against. |
| In-date control | Regimes against serialised items, gating issue, with a logged named override. |
| Replenishment | Reorder off the transaction rather than off a count. The signal goes to your distributor, not through us — we track and distribute items, we do not supply them. |
| Reporting | Consumption by person, crew, job, cost centre and period. Exceptions, overrides and out-of-date events on the same report as the successes. |
| Offline | Points and mobile peripherals cache locally and reconcile when the link returns — issue does not stop because the network did. Marginal coverage is a build specification, settled at scoping rather than discovered at commissioning. |
| Integration | Standard connectors to ERP and CMMS. Deeper integration is scoped, not assumed — no system operates entirely alone, and we would rather size that honestly. |
Because everything derives from one record, adding a location or a format does not add a system. The reporting, the replenishment logic and the compliance evidence are the same on day one and at twelve points.
The platform is only as good as the master data underneath it. Poor unit weights, duplicate SKUs and stale credentials will produce confident, wrong answers. Building that master is real work, we do it with you, and we would rather quote it than discover it.
The layer below is where the useful data is made.
Everything an analytics or AI programme can eventually do with your consumption depends on whether the underlying record was true at the moment it happened. Aggregated monthly movements cannot be un-aggregated afterwards. What the record makes possible →
We integrate with most systems.
Standard connectors cover the common ERP and CMMS platforms. If you have a special circumstance, or a business process that really matters to how the site runs, tell us early and we will scope it properly.