Skip to main content
Zemerc
Protect · Safety, Risk & Assurance

Traceable enterprise risk. Barrier assurance supported by governed records.

Hazards, barriers, controls and effectiveness governed through connected records spanning design and operation.

4
Applications
5
Stages in the flow
Why this area

Effectiveness derived from governed evidence

Hazards, barriers, controls and effectiveness governed through connected records spanning design and operation.

  • Effectiveness derived from governed evidence

    Barrier effectiveness is derived from governed control findings, such as overdue assurance activities or exceeded survey intervals.

  • Design and operational assurance kept distinct

    Technical safety in design (TSM) and process safety in operation (PSM) are separate applications with their own records.

  • Field safety records connected to enterprise risk

    Permits, incidents and observations from the field sit beside the enterprise risk register.

How the work moves

5 stages, each owned by an application.

Each stage shown here is supported by a Zemerc application, and every application remains independently operable. Operating areas are a way to understand related work, not a mandatory commercial bundle.

Hazard
Preventive barrier
Top event
Recovery barrier
Consequence
Stage 1 of 5TSM
Hazard

1 Hazard. Identified and registered. TSM

How the record moves

Four disciplines, connected through a common control model

Occupational safety, process safety in operation, technical safety in design and enterprise risk are distinct disciplines. Their common concern is the effectiveness of barriers between causes and consequences, supported by evidence that those barriers have been verified.

  1. Technical safety
    Process safety

    Design definitions, barriers, safety-critical elements and performance standards are published as governed requirements for operation.

  2. Process safety
    Occupational safety

    Operating envelopes and permits govern frontline work within defined limits

  3. Enterprise and specialist risk views
    Enterprise risk

    Control-effectiveness reporting is aggregated without duplicating the underlying technical registers.

Inside the application

RMS: Risk Management System

One enterprise risk register with facilitated workshops, bow-tie analysis and control-effectiveness records.

RMS enterprise risk dashboard showing current risks, high and extreme exposures, overdue treatment actions and reviews, and control-assurance states including ineffective, partially effective, unassessed and open-deficiency conditions.

Unrated risks remain included in exposure reporting so the visualisation represents the complete risk register rather than only assessed risks.

  • Unrated is not low
    risk. A risk without an approved assessment is reported as unrated rather than defaulted to low and remains visible in the register.
  • Design effectiveness is separate from operating effectiveness
    Design effectiveness and operating effectiveness are recorded separately so weakness in either remains visible.
  • A stated limitation rather than an unsupported score
    Where no approved engineering method exists, the process-safety application reports that limitation rather than producing an index.
Operations · safety assurance

Bring one risk and its barriers.

The key question is whether a control has been verified and whether required independence has been maintained between implementation and verification.

  • Bow-tie analysis linked to the risk register; RMS draws threats, barriers and consequences from the enterprise risk register.
  • Findings derived from governed records; Control findings are derived from the governed control record rather than entered as unsupported conclusions.
  • Safety case in design; TSM holds the hazard register, ALARP and safety-critical element assurance.
Occupational safety

Every reported figure derived through a governed calculation from recorded source data.

Recordable and lost-time rates are calculated from recorded hours worked. Where the required basis is absent, the application reports that the rate cannot be determined rather than substituting an estimated value.

  • Authorised users can report from the field, including offline where supported, with each report receiving a permanent document number.
  • Only valid next actions are available for incidents and permits
  • Status is not communicated by colour alone
Plant · barrier in service

Where this operating area is managed in practice

A degraded barrier record includes compensating measures and restoration actions so impairment remains visible until resolved.

  • Mobile incident reporting; HSE supports mobile capture of field reports and incidents.
Questions we are asked

Before the first working session

  • Which applications belong here?

    RMS, TSM, PSM and HSE.

  • Does TSM compute SIL or QRA?

    No. TSM records hazards, ALARP demonstrations and safety-critical element assurance. It does not claim to calculate SIL or QRA where no approved method is implemented.

  • Where should I start?

    Start with RMS where the enterprise risk register is the primary requirement, or HSE where the immediate need is field reporting and incident management.

  • Bow-tie analysis linked to the risk register

    RMS draws threats, barriers and consequences from the enterprise risk register.

  • Findings derived from governed records

    Control findings are derived from the governed control record rather than entered as unsupported conclusions.

  • Safety case in design

    TSM holds the hazard register, ALARP and safety-critical element assurance.

  • Mobile incident reporting

    HSE supports mobile capture of field reports and incidents.

RMS

Bring one risk and its barriers

The demonstration will generate a bow-tie view from the selected risk register.