What this group does
Compliance & Safety (HSE) is the closing loop of the Energy add-on: workplace incidents get investigated, emissions get tracked against regulatory limits, formal submissions go out to EPDK/OSHA/Environment authorities, and internal audit plans keep every asset and process independently verified. Several other groups feed into this one — a critical Anomaly Detection alert or a failed Inspection Checklist item both land here as compliance records, not just internal tickets.
Safety Incidents
→
Emissions Tracking
→
Regulatory Reports
→
Audit Plans
Each screen persists to its own store (energySafetyIncidentService.ts, emissionsTrackingService.ts, regulatoryReportsService.ts, auditPlansService.ts) under energy-setup/. This is also the landing point for compliance-triggering actions from Grid Monitoring & Control (Anomaly Detection) and Asset Maintenance Operations (Inspection Checklists) — both write real RegulatoryReport or AuditPlan records here, not just a notification.
1. Safety Incidents
Purpose: Log and investigate workplace accidents, near-misses and emergency reports from the field, with a structured root-cause and corrective-action workflow.
Key features
- Incident classification —
near_miss, lost_time_injury, first_aid, equipment_damage, environmental, security_breach, each with a low–critical severity.
- 5 Whys root-cause analysis — a structured question/answer chain (
SafetyIncidentWhy[]) attached to each incident, guiding the investigator to the underlying cause rather than the surface symptom.
- CAPA tracking — Corrective and Preventive Action items (
SafetyIncidentCapa[]), each with its own status (open/in_progress/closed), assigned employee, and due date.
- Grid Node / Asset linkage — incidents can be tied to the specific substation node or physical asset involved, connecting the safety record to the same equipment tracked in Asset Maintenance Operations.
Integration triggers
| Action | What it does |
| Assign investigator | Moves the incident to under_investigation and records assignedInvestigatorId/assignedInvestigatorName. |
| Close all CAPA items | Once every SafetyIncidentCapa reaches closed, the incident itself can move to resolved and then closed. |
2. Emissions Tracking
Purpose: Records environmental emissions data per asset or site against regulatory thresholds, so the Emissions/Environmental team can spot a breach before it becomes a formal violation.
Key features
- Per-asset emissions log — recorded readings tied to the same
EnergyAssetItem registry used across Asset Maintenance Operations, keeping environmental data and maintenance history on the same physical equipment.
- Threshold comparison — each reading is evaluated against a regulatory limit, surfacing over-threshold entries for immediate follow-up.
- Historical trend view — readings accumulate over time per asset/site, giving the environmental team a trend line rather than a single snapshot.
Integration triggers
| Action | What it does |
| Flag over-threshold reading | An emissions reading that breaches its regulatory limit is a natural candidate for a new submission in Regulatory Reports, keeping the environmental filing trail attached to the underlying measurement. |
3. Regulatory Reports
Purpose: Tracks formal submissions to regulatory bodies (EPDK, Ministry of Environment, OSHA) against a reporting period and due date, with a penalty-risk amount surfaced for overdue filings.
Key features
- Regulatory body & period —
EPDK / Ministry_Environment / OSHA, against a fixed ReportingPeriod (Q1_2026 … Annual_2026).
- Status lifecycle —
draft → under_review → submitted → approved, or overdue once the due date passes unsubmitted.
- Penalty risk amount — a monetary field surfaced per report so compliance leadership can prioritize by financial exposure, not just deadline proximity.
- Grid Node / Asset linkage — a report can be scoped to the specific node or asset it concerns, matching the linkage pattern used by Safety Incidents.
Integration triggers
| Action | What it does |
| Auto-archived from Inspection Checklists | Exporting a signed inspection certificate automatically writes a submitted compliance report when an inspection checklist passes (see Asset Maintenance Operations). |
| Submit report | Submitting moves the report to submitted and stamps today's date as the submission date. |
4. Audit Plans
Purpose: Schedules and tracks internal quality/compliance audits (ISO 55001 asset, ISO 14001 environmental, ISO 45001 safety, EPDK technical) with a compliance score and per-finding severity.
Key features
- Audit type —
iso_55001_asset, iso_14001_env, iso_45001_safety, epdk_technical, each scheduled with a lead auditor and target date.
- Compliance score & open findings count — a numeric score plus a live count of unresolved findings, each carrying its own
minor/major/critical severity.
- Status lifecycle —
planned → in_progress → completed, or action_required when findings remain open past the audit date.
- Target asset & grid node linkage — an audit plan can target a specific physical asset or an entire grid node, matching the linkage convention used across this group.
Integration triggers
| Action | What it does |
| Auto-created from Anomaly Detection | Flagging a meter for regulatory audit automatically opens a new epdk_technical audit plan with a pre-filled major-severity finding when an AI anomaly alert is flagged for regulatory review (see Grid Monitoring & Control). |
| Resolve finding | Marking every finding as resolved clears the open findings count to zero, allowing the plan to move to completed. |
End-to-end data flow
| Source screen | Action | Target screen / record |
| Anomaly Detection (Grid Monitoring & Control) | Flag Meter for Regulatory Audit | → new record in Audit Plans |
| Inspection Checklists (Asset Maintenance Operations) | Export Signed Inspection Certificate | → new record in Regulatory Reports |
| Emissions Tracking | Threshold breach identified | Feeds a new filing candidate into Regulatory Reports |
| Safety Incidents | All CAPA items closed | Incident moves to resolved/closed |