From the depths, to your fingertips.
Most offshore operators sit on a decade of incident, risk and progress records they can't actually use — every question takes ten minutes to answer, so the questions stop getting asked. Pear MS surfaces what you need to your hand in a heartbeat, every shift, every time.
Engineered around a single iron rule, written into the name itself.
Request a BriefingThe acronym is the operating procedure.
Every event the IMS captures is tagged and actioned in the order written above — an order that is fixed in the name, immune to whoever owns the company this quarter, and outranks any executive's preference for a different priority on a difficult day. People are first. They stay first.
We have watched too many organisations chase the fourth letter directly. It never works. Take care of the first three in their order — the fourth follows along behind, like the tail of a cat.
One source. One touch. Total trace.
Every variable lives in exactly one place — defined once, touched once, referenced everywhere. Every change is logged with who, when, and why; if a value moves, every downstream form that depended on it is alerted before the change can be saved. No version 2 of the truth. Only the truth, and the trail of how it got that way.
One platform. One event. Three views.
Every hazard, every shift, every incident is the same object in different states — planned, actual, deviated. The IMS stops treating them as separate forms in separate folders and starts treating them as one register the contract drives end-to-end.
Risk Register & RA
Phased risk assessment with hazard taxonomy, hierarchy of controls (Eliminate / Reduce / Isolate / Admin / PPE) and mandatory residual-risk capture at sign-off.
Daily Progress
Per-team, per-shift progress and downtime logged against contract-defined codes. Vessel-offline-capable. The end-of-project overview you used to compile manually — now live, every day.
Incident Investigation
Tripod Beta causal analysis with three-state risk (Actual / Potential / After-action). Layered cause walk enforced — investigators cannot skip Immediate or Underlying to land on a generic management label.
CAPA Closure
Corrective and preventive actions tracked from sign-off through independent verification. Closure rate is a first-class KPI on every project dashboard.
Contract-Driven Codes
The contract is the schema. Progress codes, downtime codes, locations, org roles and signatories all derive from the contract record — no fork per project, no re-deploy per scope change.
Live Project Dashboard
Hours-by-code rollups, downtime cause-of-day, per-foundation timeline, CAPA closure rate. The artefacts auditors and clients ask for — generated, not assembled.
From steady state into the worst day.
Twelve years of evidence on the prevention side is one half of the story. The other half is what happens when prevention runs out — when the spill, the man overboard, the collision, the blowout actually arrives. Pear EM picks up there: same data model, same org catalogue, same locations, every shred of context the Incident Commander needs already on the screen. The first hour stops being information-starved.
The daily heartbeat
Risk register, daily progress, incident log, CAPA. Knows who's where, doing what, with which controls in place, against which contract, every shift, every day.
pearmanagementsystems.comICS & Oil Spill Response
An NIMS-aligned Incident Command System for offshore emergencies. Pre-populated from Pear MS the moment the IC opens an incident:
- ICS 201 (Incident Briefing) auto-filled with location, activity, personnel and known hazards from the live RA register
- ICS 203 / 207 (Org Assignment) seeded from the IMS org catalogue and on-shift roster
- Spill modelling and Area Contingency Plan integration for OPA 90 / NCP compliance
- Action timeline writes back to Pear MS as a closed-loop AINM with full ICS evidence trail
Built from 2,000 turbines.
This system isn't speculative. It's calibrated against twelve years of structured incident, risk and progress data from major UK, Continental European and US East Coast offshore wind installations — the same projects that built the industry. Every design rule the IMS enforces is grounded in something the historical data showed us, not in a feature checklist.
Read the full methodology & corpus composition → The Calibration Corpus
Module-by-clause map for auditors → ISO Alignment Detail
Ready to put your safety data to work?
Whether you're a contractor with a decade of forms in folders or a client asking for an audit-ready record from day one, we'd like to hear what your current system can't tell you.
Tell us your sector and the question your current system can't answer.
[email protected]