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.
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.
| Lane | Does |
|---|---|
| Reporter | reports the incident or near miss on the mobile screen |
| Safety officer | classifies, sets the regulator deadline, leads the investigation |
| Investigation team | records events, causes and corrective actions; from operations, maintenance and HR |
| Site manager | approves actions, signs the regulator report, closes the incident |
Every screen renders for desktop and mobile; portal screens are the same screens delivered to an outside login.
| Screen | What is on it |
|---|---|
| S01 Report | mobile screen: type, location from the phone, equipment scan, people affected, contractor company, description, photos; submit |
| S02 Classification | severity, category, lost time, regulator report required; assign the investigation team; the clocks that start |
| S03 Investigation | timeline of events, causes by method, contributing factors, witness notes, documents; corrective actions with owner and date |
| S04 Actions | actions by owner and date with status and evidence; create maintenance order; take equipment out of service |
| S05 Regulator report | form pre-filled from the incident; site manager review; submit and store the acknowledgement |
| S06 HSE board | incidents and near misses by site, month and category; lost-time rate; open actions by age; regulator reports due |
The first object is the main one; each system page shows the real table or resource behind every handler.
| Object | Why the app reads it | See it on |
|---|---|---|
| Employee | the reporter, the people affected, their manager and org unit | S/4HANA · Oracle Fusion · Snowflake · Databricks |
| Equipment | the machine or installation involved and its location | S/4HANA · Oracle Fusion · Snowflake · Databricks |
| Maintenance order | the repair or modification order a corrective action creates | S/4HANA · Oracle Fusion · Snowflake · Databricks |
| Cost center | the site and department that own the incident | S/4HANA · Oracle Fusion · Snowflake · Databricks |
| Supplier master | the contractor company when a contractor is involved | S/4HANA · Oracle Fusion · Snowflake · Databricks |
| Object | What changes |
|---|---|
| Maintenance order | maintenance order created for a corrective action on the equipment, with the incident number as reference |
| Equipment | equipment set to out of service when the site manager takes it off line |
Start: Anyone on site submits S01 on the mobile screen, for an incident or a near miss.
| Step | Moves when |
|---|---|
| Reported | incident created with photos and location; safety officer notified within seconds |
| Classified | severity and category set within 1 hour; regulator clock started when required |
| Investigated | events, causes and corrective actions recorded; actions approved by the site manager |
| Actions complete | each action closed with evidence; maintenance orders confirmed in the ERP |
| Closed | effectiveness check passed after 30 days; site manager signs; the regulator's acknowledgement stored |
| Component | Trigger → action → outcome |
|---|---|
| btn_submit_report | on 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_severity | on change → apply the classification rules → start the investigation and regulator clocks, show the required team |
| btn_create_maint_order | on click → call the maintenance order interface with the equipment and the action text → store the order number on the action |
| btn_close_incident | on click → check that every action is closed and the effectiveness check is recorded → close the incident, update S06 |
| Step | Time limit and escalation |
|---|---|
| Classification | 1 hour, then the site manager is told |
| Regulator report | the 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 action | its due date, then the owner is reminded and the site manager is copied |
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.
The objects with their real names, the criteria in that system's fields, the write interface and what to set up first.
Employee read from PA0001 · PA0002 (SAP HCM) or SuccessFactors; also on SAP ECC.
Open the S/4HANA page →Employee read from HCM REST: workers · assignments; also on Oracle E-Business Suite.
Open the Oracle Fusion page →Employee read from CONFORMED.EMPLOYEE; lakehouse.
Open the Snowflake page →Employee read from silver.employee; lakehouse.
Open the Databricks page →Other systems connect through the same handlers; see how SmartApps connect.
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.
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.
Every role in this app is inside the company; an outside role can be added as a lane with a portal screen.
Every step, value, decision, notification and write-back acknowledgement of every instance, with the version of the app, append-only.
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.