App catalogue People and compliance

Health, safety and environment incident

Takes a safety or environmental incident from a report on a phone through classification, investigation and corrective actions to closure, with the regulator report where the rules require one.

SCREENSDATA HANDLERSSOURCE OBJECTS, READ IN PLACES01 ReportscreenS02 ClassificationscreenS03 InvestigationscreenS04 ActionsscreenS05 Regulator reportscreendh_employeeEmployeedh_equipmentEquipmentdh_maint_orderMaintenance orderdh_cost_centerCost centerdh_vendorSupplier masterS/4HANAPA0001 · PA0002S/4HANAEQUI · EQKT · ILOAS/4HANAAUFK · AFIH · AFVCS/4HANACSKS · CSKTS/4HANALFA1 · LFB1 · LFM1rows stay in the source · access rules apply at read time · writes go through the source's released interface and are confirmed
The screens, the data handlers behind them and the objects each handler reads in place on S/4HANA. Other systems have their own page.
6 days
of configuration to a production-grade version
estimate
6
screens, desktop and mobile
catalogue
5
data handlers, read in place
catalogue
4
systems with a page for this app
catalogue
3
clocks with escalation
catalogue
What it does

Today, and with the app

Today an incident is written on a paper form at the end of the shift, typed into a register the next day and investigated when the safety officer visits the site. Corrective actions are agreed in the meeting and tracked in a spreadsheet, and the regulator's deadline is counted by hand.

Anyone on site reports an incident or a near miss on the mobile screen in under 2 minutes, with photos, the location, the equipment involved and the people affected, whether employees or contractors. The safety officer classifies it within the hour, and the app starts the clocks the classification requires, including the regulator's reporting deadline for a lost-time injury or a spill. The investigation team records the sequence of events, the causes and the corrective actions; an action on a machine becomes a maintenance order in the ERP, and the equipment can be taken out of service from the screen. Actions are tracked to their dates, the site manager closes the incident once the effectiveness check passes, and the board shows every site's incident rate and open actions.

Who takes part

Process app: lanes and boxes first, then screens per box, then roles, then the criteria on each arrow

LaneDoes
Reporterreports the incident or near miss on the mobile screen
Safety officerclassifies, sets the regulator deadline, leads the investigation
Investigation teamrecords events, causes and corrective actions; from operations, maintenance and HR
Site managerapproves actions, signs the regulator report, closes the incident
Screens

6 screens, composed from the handlers

Every screen renders for desktop and mobile; portal screens are the same screens delivered to an outside login.

ScreenWhat is on it
S01 Reportmobile screen: type, location from the phone, equipment scan, people affected, contractor company, description, photos; submit
S02 Classificationseverity, category, lost time, regulator report required; assign the investigation team; the clocks that start
S03 Investigationtimeline of events, causes by method, contributing factors, witness notes, documents; corrective actions with owner and date
S04 Actionsactions by owner and date with status and evidence; create maintenance order; take equipment out of service
S05 Regulator reportform pre-filled from the incident; site manager review; submit and store the acknowledgement
S06 HSE boardincidents and near misses by site, month and category; lost-time rate; open actions by age; regulator reports due
Data handlers

5 objects, read where they live

The first object is the main one; each system page shows the real table or resource behind every handler.

ObjectWhy the app reads itSee it on
Employeethe reporter, the people affected, their manager and org unitS/4HANA · Oracle Fusion · Snowflake · Databricks
Equipmentthe machine or installation involved and its locationS/4HANA · Oracle Fusion · Snowflake · Databricks
Maintenance orderthe repair or modification order a corrective action createsS/4HANA · Oracle Fusion · Snowflake · Databricks
Cost centerthe site and department that own the incidentS/4HANA · Oracle Fusion · Snowflake · Databricks
Supplier masterthe contractor company when a contractor is involvedS/4HANA · Oracle Fusion · Snowflake · Databricks

Written back

ObjectWhat changes
Maintenance ordermaintenance order created for a corrective action on the equipment, with the incident number as reference
Equipmentequipment set to out of service when the site manager takes it off line
The flow

From the trigger to the last write

THE FLOW · HEALTH, SAFETY AND ENVIRONMENT INCIDENT1Reportedincident created withphotos and location; safetyofficer notified withinseconds2Classifiedseverity and category setwithin 1 hour; regulatorclock started when required3Investigatedevents, causes andcorrective actionsrecorded; actions approvedby the site manager4Actions completeeach action closed withevidence; maintenanceorders confirmed in the ERP5Closedeffectiveness check passedafter 30 days; site managersigns; the regulator'sacknowledgement stored
Each step and the criterion that moves it.

Start: Anyone on site submits S01 on the mobile screen, for an incident or a near miss.

StepMoves when
Reportedincident created with photos and location; safety officer notified within seconds
Classifiedseverity and category set within 1 hour; regulator clock started when required
Investigatedevents, causes and corrective actions recorded; actions approved by the site manager
Actions completeeach action closed with evidence; maintenance orders confirmed in the ERP
Closedeffectiveness check passed after 30 days; site manager signs; the regulator's acknowledgement stored
Actions, clocks and measures

What the components do, what the clocks enforce, what the board shows

ComponentTrigger → action → outcome
btn_submit_reporton tap → save the report with location, photos and the scanned equipment → notify the safety officer of the site, start the 1-hour classification clock
dd_severityon change → apply the classification rules → start the investigation and regulator clocks, show the required team
btn_create_maint_orderon click → call the maintenance order interface with the equipment and the action text → store the order number on the action
btn_close_incidenton click → check that every action is closed and the effectiveness check is recorded → close the incident, update S06

Clocks

StepTime limit and escalation
Classification1 hour, then the site manager is told
Regulator reportthe legal deadline by country and severity, for example 24 hours for a fatality or 10 days for a lost-time injury, then the head of HSE is told
Corrective actionits due date, then the owner is reminded and the site manager is copied

Measures

incidents and near misses per 200,000 hourshours from report to classificationactions closed on timeregulator reports submitted within the deadlineincidents by cause
A day with the app

Illustrative

Names, places and figures are illustrative; the pattern is the catalogue's.

At 22:40 on a night shift in Gliwice, a forklift driver, Marek, reported a near miss at a blind corner in 90 seconds from his phone, with a photo and the scanned equipment number of the rack that was hit. The safety officer classified it at 07:10, the investigation the next afternoon found a mirror missing since a rack change in March, and the corrective action created a maintenance order at 15:30 with the mirror fitted 2 days later. The board showed the plant manager 3 near misses at the same corner in 4 months, and a second action added floor markings; the site manager closed the incident after the 30-day check.

illustrative scenario · Health, safety and environment incident
On your systems

One page per system

The objects with their real names, the criteria in that system's fields, the write interface and what to set up first.

Other systems connect through the same handlers; see how SmartApps connect.

Terms on this page

Near missAn event that could have caused injury or damage; reported and investigated like an incident.
Lost-time injuryAn injury that keeps the person away from work for at least 1 full shift; it usually requires a regulator report.
Corrective actionA change made so the cause of the incident is removed, with an owner, a date and evidence.
Questions

How long does it take to have this running?

About 30 minutes to a first running screen on your live rows, and 6 working days to the production-grade version described here, most of it spent agreeing screens and criteria with the process owner.

Which system does it run on?

Any of SAP S/4HANA, Oracle Fusion Cloud, Snowflake, Databricks, with the objects read in place; the pages above show the objects and the write path for each. Two systems at once is one handler per object per system.

Who takes part from outside the company?

Every role in this app is inside the company; an outside role can be added as a lane with a portal screen.

What does the audit record hold?

Every step, value, decision, notification and write-back acknowledgement of every instance, with the version of the app, append-only.

See this app on your data

Bring the process and the systems it touches. In the first session we register the data handlers, draw the levels or the lanes and run the first screen on your live rows.