OTOF

Command, not chaos.

An NIMS-aligned Incident Command System and oil spill response platform for offshore emergencies. Pre-populated with the operational context the Incident Commander needs the moment the call comes in — so the first hour of a response is coordinated, not improvised.

Request a Briefing
The mission

The first hour is the whole game.

Most offshore incidents are lost or won in the first sixty minutes — not because the response is wrong, but because the Incident Commander is forced to spend that hour asking who, where and what. Pear EM removes the question. Every form is pre-filled, every responder is pre-assigned, every regulator is pre-addressed. The IC starts at minute zero with the page already turned.

What it does

A complete command room, not a form library.

Pear EM is not a PDF of ICS forms. It is the running command room — every section chief, every status board, every notification path, every map overlay — orchestrated against a single live event record that writes back to your IMS at every step.

01

Incident Command (NIMS)

Full ICS structure: Incident Commander, Operations, Planning, Logistics, Finance/Admin. Forms 201, 202, 203, 204, 205, 206, 207, 208, 209 generated and version-controlled live. Section chiefs assigned by competence and proximity, not by who's nearest the phone.

02

Oil Spill Response

OPA 90 / NCP / Area Contingency Plan workflows for US waters. SOSREP / MCA / OSPAR for UK and European. Tier 1, 2, 3 escalation paths pre-mapped. Equipment requests routed to the nearest pre-staged stockpile.

03

Spill Trajectory & Fate

Trajectory forecast and fate-and-effects modelling against current met-ocean data, overlaid on environmental sensitivity maps. Updates as the wind and tide turn. Outputs feed directly into ICS 209 (Status Summary) and the regulator notification.

04

Notification Cascade

Pre-templated regulator messages: USCG sector, NRC, BSEE, NOAA, state agencies, port authorities, insurance, client. UK / EU equivalents on demand. Each notification timestamped, acknowledged, and audit-trailed.

05

Operational Context

During onboarding we work with you to populate Pear MS Lite — a context system tuned for emergency response — with the operational landscape Pear EM needs to know: org, locations, active contracts, equipment register, standing RAs, common scenarios. By the time an incident opens, all of it is already there. The IC stops asking and starts deciding.

06

After-Action Loop

The full timeline — every command, every resource request, every notification, every status update — bound into a single AINM record at incident close. Exported in a format your existing IMS can ingest, so CAPA actions enter your standard closure pipeline and lessons-learned reach your next RA review. If you also run Pear MS, the loop is automatic.

The doctrine

The Planning P, built into the product.

Every NIMS-aligned incident response runs on the same ritual — eight meetings around one cycle, repeated every operational period. Pear EM doesn't ask you to remember the cycle. It runs the cycle.

The Pear EM Planning P — eight planning-cycle steps in the canonical ICS pattern, drawn as the letter P with the Pear at its centre A diagram in the shape of the letter P. The vertical stem on the left contains two initial-response steps run once per incident: 1 Incident Brief (ICS 201) at the bottom, 2 Initial Unified Command Meeting in the middle. The bowl on the upper right contains six planning-cycle steps that repeat every operational period, traversed clockwise from the entry: 3 IC and Unified Command Objectives Meeting (ICS 202), 4 Command and General Staff Meeting, 5 Tactics Meeting (ICS 215), 6 Planning Meeting, 7 IAP Approval, 8 Operations Briefing. The bowl is divided into four quadrants labelled Plan, Do, Assess, Review. A subtle bird's-eye pear photograph sits at the centre of the bowl as a brand mark. new period → initial response — once per incident operational period — repeats every cycle 1 INCIDENT BRIEF ICS 201 2 INITIAL UC MEETING 3 IC/UC OBJECTIVES ICS 202 · opens each cycle 4 COMMAND & GENERAL STAFF 5 TACTICS MEETING ICS 215 · 234 6 PLANNING MEETING 7 IAP APPROVAL the plan, blessed 8 OPERATIONS BRIEFING execute & assess →

The leg — once per incident

The first hour. Notification arrives. An Incident Brief (ICS 201) captures what happened, where, who's involved, and what's already been done. The Initial Unified Command Meeting brings the principals together to align before the wider organisation activates.

The loop — every operational period

Six meetings, in order, every cycle (typically 12 to 24 hours). The IC/UC Objectives Meeting (ICS 202) opens the cycle. The Command & General Staff Meeting cascades direction. The Tactics and Planning meetings work the plan. The IAP Approval seals it. The Operations Briefing hands it to the field. Then the cycle begins again — at meeting 3, with updated objectives.

The four quadrants

Plan
Steps 4–6 — strategy and tactics formed.
Do
Steps 7–8 — IAP approved, briefed, executed.
Assess
Field execution, with continuous progress assessment.
Review
Re-entry to the next cycle with what was learned.

Why we draw this

Every Incident Commander we've worked with knows the Planning P. What they don't have is software that runs it — that opens an ICS 201 the moment the call comes in, schedules the next meeting automatically, prefills ICS 215 with active tactics, drafts the IAP at the Planning Meeting, and hands the Operations Briefing to the oncoming shift with one click. Pear EM is built around this diagram, not around a feature checklist.

Pear EM with context, day one

Pear EM never operates in the dark.

An ICS platform without operational context is an empty form. Pear EM ships with Pear MS Lite — a context system we populate together with you during onboarding by mapping your operational landscape: org, locations, active contracts, equipment register, standing RAs, common scenarios. The work happens before any incident, so when one arrives, everything clicks into place. The full Pear MS IMS is a separate product — a complete operational management suite for teams who want one; skip it if Pear EM is enough.

Pear EM — incident mode

The command room

NIMS-aligned ICS, oil spill response, notification cascade, after-action loop. Activates the moment the IC declares an incident.

pear-em.com
←
Pear MS Lite — included with Pear EM

The context Pear EM lives in

The context system we populate together during onboarding by mapping your operational landscape — org, locations, contracts, equipment, standing RAs, common scenarios — into a structure tuned for emergency response. When an incident hits, the IC has every shred of context already on screen, ready to act. No improvisation, no chasing.

Want the full IMS? → pearmanagementsystems.com
9
ICS forms supported & version-controlled live
≤60starget
Time to pre-fill ICS 201 from Pear MS
4
Regulatory regimes (US, UK, EU, IMO)
7,315
Events in shared calibration corpus
The approach

Calibrated against real incidents.

Pear EM inherits the same twelve-year offshore-wind incident corpus that calibrates Pear MS — 7,315 events across 31 named projects, two contractors, and six countries. Every workflow the platform runs has been pressure-tested against scenarios that actually happened.

The first hour of an offshore incident is information-starved chaos. Pear EM exists to remove the chaos and leave only the decisions.
Aligned with the regimes that matter
NIMS / ICS US Incident Command OPA 90 / NCP US Oil Pollution SOSREP / MCA UK Maritime OSPAR / IMO MARPOL International
Talk to us

Ready to compress your worst hour?

Tabletop-exercise demonstrations available for offshore operators, response contractors, and regulator liaisons. Tell us your tier and your jurisdiction; we'll bring the rest.

Briefings run ~45 minutes. We come prepared with an ICS 201 prefilled from a redacted historical event in your sector — so the conversation starts where it matters.

hello@pear-em.com