← ChimmaniHome / 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.

Incident pyramid · events per band · one synthetic year

Synthetic demo data. Near misses to recordables ≈ 9:1.

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 days above 75% of the year's peak. 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 count per KPI
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
-

Synthetic demo data, generated per KPI; dates run back from today. Brightest, glowing cells = days above 75% of the year's peak.

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

Synthetic demo data. Observation velocity bars show % of plan on a 0–130% scale.

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 · scores 1–5

Synthetic demo data. Higher = more impact / more effort.

Recommended sequence

E2 → E1 → E3 → E4 → E5 → E6

The RPT series · five reportsAll reports on the home page →
  1. RPT-001D365 Data StrategyRaw objects to revenue moves · Synthetic demo data
  2. RPT-002EHS Metrics CommandLeading signal over lagging autopsy · Synthetic demo data
  3. RPT-003Value-Chain TwinOntology, links and unstructured data · Synthetic demo data
  4. RPT-004Verifiable AnswersArchitecture for AI you can sign off · Synthetic demo data
  5. RPT-005EHS BenchmarksReal OSHA data, and what it gets wrong · Real public OSHA data