01 · Why This Matters
Building on Ching Luh's existing IMS foundation. This module strengthens how data flows to three audiences — workers on the floor, facility GMs, and customers — each getting the right view at the right time.
Extends the current reporting flow with predictive signals — risks surface earlier, feedback closes the loop with workers.
Real-time visibility for Facility GMs and OHS leads, complementing the periodic reports already in place. Predictive indicators flag rising risk; investigations and CAPA tracked end-to-end in one place.
Building on audit-ready results already trusted by customers and regulators — adding real-time dashboards and continuous evidence visibility for customers and other stakeholders.
02 · Module Capabilities — Fit-for-Use IMS
Mobile-first and audit-ready by design. Every capability earns its place in this module — built to extend the existing IMS with predictive insight.
Frontline reports incidents at the facility with photos & voice — no laptop, no delay, no spreadsheet.
Classifies events into standard categories — all safety events (hazard, near-miss, incident…) — so data is comparable like-for-like across all facilities.
Incident trends are analyzed to surface leading metrics that warn of rising risk before an incident occurs. Threshold alerts are pushed automatically to the right owner.
Encrypted at rest and in transit. Personal data of workers protected by strict access controls. Built to comply with data protection laws in Vietnam and Indonesia.
Every action is logged, with role-based access. Audit-ready by design — for customers, ISO 45001, and regulators.
Operational views at facility level, regional strategy, and customer-facing audit. % action tracking — every CAPA visible from open to close. A single source of data for all.
03 · Incident Lifecycle
Five steps. From report to lessons learned. Discipline at every step.
04 · Deployment approach
A focused module, not a heavy enterprise build. Lightweight web/QR capture for frontline reporting at scale; a richer interface for the OHS team. Backend and security on Ching Luh's existing infrastructure. Dev work absorbed into the Group OHS role.
Right tool for the right user. Frontline workers → lightweight web/QR capture, no install needed. OHS team → interactive workflow & dashboard. Customer/auditor → read-only view. Backend → API + database on Ching Luh server.
AI-assisted development by the Group OHS role. No external dev team, no vendor lock-in. Same approach proven in production at AkzoNobel.
All code reviewed and approved by Ching Luh IT before deployment. Security audit, data residency check, integration sign-off — IT owns the gate. No code reaches production without IT clearance.
IT owns the code repo from day one. Documentation auto-generated during build. Knowledge transfer plan baked into the build cycle — continuity does not depend on a single person.
05 · Roadmap
Plan → Do → Check → Act, aligned to ISO 45001. Discovery first — no assumptions made before field verification. Then build, pilot, validate. Roll-out only after the playbook is signed off.
06 · Success Criteria
Clear, measurable, agreed from the start. Roll-out does not happen until every criterion is met.
07 · Demo
Not a slide-deck idea. A live application demonstrating the core capabilities — frontline capture, OHS workflow, and dashboard view — already built and running.
Note: This is a working proof-of-concept. Final stack, integrations, and security review will be confirmed during Discovery (Month 1).
08 · Proposed for Future Phases
A modular approach: validate the IMS module first. The modules below are proposed for future phases — to be scoped only after the IMS module delivers evidence. No big-bang rollout, no broad commitment without proof.
Fit-for-Use IMS — incidents, severity, predictive insights, lessons learned
JSA, HIRA, internal & external audits, CoSMA progression — to align later
Permit-to-work, management of change, isolation control — to align later
Competency matrix, retraining, contractor scoring — to align later
ESG reporting, environmental impact, customer disclosures — to align later
This proposal focuses on the IMS module only. Modules 2–5 could share the same data foundation — taxonomy, master data, audit trail, mobile capture, role-based access — and will be scoped and aligned in subsequent phases once the IMS module is validated.