← Chimmani / RPT-002
Synthetic demo data
Report 002 · EHS Metrics Command · Benchmark ESG / Gensuite

Lagging tells you what happened.
Leading lets you act.

Most safety reporting is an autopsy: TRIR arrives weeks after the injuries it describes. Command means instrumenting the indicators that still have time on the clock — observation velocity, closure discipline, reporting culture — and wiring 40 alerting KPIs so the right owner hears about drift while it is still cheap to fix. Built on the same governed spine as RPT-001; every number traces to a record.

S1

Signal physics

One synthetic year, stacked the way risk actually works. The strategy is not to stare at the top of the pyramid — it is to instrument the base so aggressively that the top starves. Click a band.

Band Select a band Every layer you instrument at the bottom removes events at the top. Move
S2

Indicator board

Fourteen indicators, split by when they let you act. The quiet scandal of EHS reporting: leadership attention goes to the lagging six because they are easy to rank. The board exists to invert that ratio.

Attention mix · leading share
42% today → 70% target
IndicatorSelect an indicator above
Reading (synthetic)
Alert rule
Owner action
S3

The alert wall

Forty KPI alerts in five classes. The class that matters most is the one nobody builds: silence alarms — because a site that stops reporting hasn't become safe, it has become invisible.

Doctrine

An alert that doesn't name an owner and an SLA is a notification. All forty route to a person, with a clock.

AlertSelect an alert above
Trigger
Routes to
Response SLA
S4

Cadence grid

A year of EHS activity, one cell per day, filtered by KPI. Intensity is volume; the glow marks top-decile days. What you are looking for is not the bright cells — it is the cold stretches, because those are the weeks nobody was looking.

Trailing 12 months · daily volume
Mon WedFri
Less More
Hover any day for its reading · switch KPI to re-scan the same year
Active days
Longest streak
Cold gap
Peak day
S5

Site command grid

Ten synthetic sites, ranked by what leading signal says is coming — not by whose last incident was most recent. Hover a row for the command action already in motion.

SiteRegionObservation velocity vs planAction closureDays since recordableStatus
Status is computed from leading drift, never from luck-of-the-draw incident timing
S6

Regulatory clock

Filing season is not an event, it is a countdown that never stops. Every filing below assembles itself from the governed layer — the deadline play is review, not archaeology.

S7

Action plan

Six plays. Same doctrine as RPT-001: cheapest signal first — silence alarms cost almost nothing and change site behavior overnight.

Impact vs effort
Recommended sequence

E2 → E1 → E3 → E4 → E5 → E6