Industrial software is defined as much by the outcomes it prevents as by the capabilities it enables.
Producing a number is straightforward; declining to produce one when method, evidence or authority is insufficient requires deliberate engineering governance.

6 steps, each with a defined output.
A step is complete only when its required artefact exists and the next decision can be made from it.
- 01
Start from the record
The first design artefact is the operational register, sheet or log the responsible team already maintains, together with the rules governing validity, ownership, change and retention.
Produces: The record model the application is built around - 02
Build one independently operable application
Each application is developed, released and operated independently. It must provide complete value on its own before any integration with another application is considered.
Produces: An independently operable application - 03
Enforce the rules in the system
Segregation of duties, immutability and effective dating are implemented as application controls rather than left only to procedure.
Produces: Controls enforced by the application and data layer - 04
Derive from records rather than declare manually
Where status can be derived from governed records, the application derives it rather than relying on manually entered summary totals.
Produces: Figures with a traceable and supportable basis - 05
Decide what not to compute
Where no approved engineering method exists, the application reports that limitation rather than generating an unsupported figure.
Produces: A stated boundary on every public claim - 06
Prove it on real work
An application is tested on representative project or asset records with the team responsible for the underlying process before wider release. Derived positions are checked against supporting operational evidence.
Produces: Evidence supporting every public claim
Each principle is visible in delivered application behaviour.
These are implemented behaviours rather than design intentions, and each can be demonstrated in the relevant application.
- PSMDoes not generate process-safety indices where no approved engineering method exists and reports the underlying components insteadPSM: Process Safety Management System
- AIRMSDoes not calculate generic integrity, health or readiness indices without an approved method; thickness readings and approved assessment revisions remain governed recordsAIRMS: Asset Integrity & Reliability Management System
- FAMSKeeps a draft invisible downstream, and refuses to let the author of an engineering record approve itFAMS: Flow Assurance Management System
- HAMSPreserves raw readings, governs substitution and supports historical recalculation using the method effective for the original periodHAMS: Hydrocarbon Accounting Management System
- EAMSSeparates work completion from closure, with independent verification applied where configuredEAMS: Enterprise Asset Management System
- LGMSPrevents conflicting resource allocation through database controls and reports missing required limits as not checkableLGMS: Logistics Management System
- OPEPReports unsupported measures as unavailable and keeps ‘cannot be determined’ distinct from ‘not ready’OPEP: Offshore Projects Execution Platform
- OMSTreats unknown as an explicit lifecycle state rather than active, and counts only verified eventsOMS: Obsolescence Management System
PSM: Process Safety Management System
Process-safety indices make the principle explicit: where no approved engineering method is configured, the application does not generate a composite score.
Where a composite result is not supportable, contributing measures are presented individually so the recorded position remains transparent and technically defensible.

Controls that preserve the record throughout its lifecycle.
Long-term defensibility depends on how the record is controlled after creation: who may change it, how revisions are approved, how supersession is handled and how the audit trail is preserved.
- Office and field teams working from the same governed record; Office and field teams work from the same governed record. Field capture is designed for supported devices and the connectivity conditions in which the work is performed.
- Identity is the control surface; Roles, organisation scope and approval rights are enforced against authorised identities so segregation of duties does not depend on informal practice.
- Approved records are superseded rather than edited in place; An approved engineering record remains preserved. Supersession identifies dependent records that require reassessment rather than changing them automatically.
- Append-only audit history; Controlled changes retain who changed what and when so historical decisions can be reconstructed later.
Why the portfolio is structured this way.
Developing applications independently is an engineering and commercial design decision. The philosophy page explains the consequences of that model for clients and for the portfolio.
Ask what the application is designed to prevent or refuse.
For industrial software, controls around invalid, unsupported or unauthorised outcomes are as important as the functions themselves. Demonstrations show both the capability and the controls.
