MU·01 Technology
A system of record is the primary place the state of an operation is entered, verified and kept — not a dashboard drawn over someone else’s data. We build them for industries where the record still lives in six places at once.
Most operational software is a view. It reads from somewhere else, presents a chart, and disclaims responsibility for whether the underlying number is true. A system of record is the opposite: it is where the number is created, and it carries the obligation to be right.
The distinction matters because reporting layers multiply cheaply and records do not. An operator can buy five dashboards in a year. What it cannot buy easily is a single place where a produced volume, a crew certification or a contract milestone is entered once, by the person closest to it, and survives every handover afterwards.
Operations rarely fail for want of effort. They fail because the truth is distributed: a rota in a spreadsheet, certifications in an inbox, a manifest on paper, an invoice line in an accounting package. Each is individually defensible. Together they disagree, and the disagreement surfaces at the worst possible moment — an audit, a mobilisation, a dispute over an invoice.
Consolidation is unglamorous work and it is where most of the value sits. A verified headcount on a platform is a safety artefact before it is a data point. A certification that expires mid-hitch was visible weeks earlier to anyone looking at the right screen — if such a screen existed.
Every system of record we run began as an internal answer to a problem one of the group’s own platforms had. SubseaCore exists because our oil and gas platform needed to run offshore crew, assets and contracts against real duty-holder obligations. That origin shows in the assumptions it makes — rotations rather than calendars, certifications that gate mobilisation — and it is why none of these products are demonstrations.
What this covers
Questions
The primary system where the state of an operation is entered, verified and kept. It differs from a dashboard or reporting layer, which reads data created elsewhere and does not carry responsibility for its accuracy.
An ERP is usually a system of record for finance and procurement. The gap we address is operational: crew, assets, certifications, rotations and contracts, where a general ERP either has no model or assumes an office-based calendar.
Usually alongside at first. Rollout runs module by module with the old process operating in parallel until it is genuinely redundant, because switching a record system in one step is how operations lose history.
Anywhere shift work, certification and contract reconciliation meet. It was proven offshore, but the pattern is not specific to oil and gas.
Set per engagement. A bespoke build is normally owned by the client; an existing group product such as SubseaCore is licensed.
Continue
We start with a diagnostic, not a proposal.