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

Technical Safety Management System

Demonstrate tolerability and retain the evidence behind the demonstration.

TSM is a governed engineering system for demonstrating major-hazard design risk against an approved tolerability basis, covering hazard registers, barriers, safety-critical elements, performance standards, verification schemes and safety-case evidence.

0Governed registers
0Controlled reports
0Functional areas
0Roles
TSM home view showing the current technical-safety position, overdue work, hazard-study currency, recommendation closure, ageing actions and governance-document status, with required management attention expressed as specific work rather than an opaque summary score.
The demonstration

Safety-case claims remain only as strong as their supporting evidence

A safety case is a structured argument supported by governed claims, arguments, evidence and conditions that could invalidate the demonstration.

The safety case
Claim
Risk is tolerable
Claim
Safeguards are effective
Claim
Current technical-safety basis
Argument
Hazard identification
Argument
Barrier analysis
Argument
Verification scheme
Evidence
Technical safety studies
Evidence
Performance standards
Evidence
Verification findings
Calculation governance

Passing software tests alone does not constitute engineering certification

Numerical methods remain unavailable for production use until required technical review, benchmark reproduction and technical-authority approval are complete. Passing software tests alone is not treated as engineering certification.

TSM calculation-engine register showing method, version, assurance state, referenced standards, equation set, benchmark cases and production-use admission status

Each calculation engine records chain position, version, referenced standards, equation set and benchmark cases used for assurance.

  • Methods and deterministic calculation engines are governed through registration, version control, benchmarking and formal admission before production use.
    A method that has not completed that assurance path remains unavailable for production execution.
  • Reference cases are explicit
    Where a result is derived rather than independently validated, the engine records the benchmark or reference case used.
  • Restricted at the assurance gate
    Methods not admitted for production use are blocked by runtime controls rather than policy alone.
When design inputs change

Approved engineering records are superseded rather than edited

Approved technical-safety records are superseded rather than edited, with dependent records identified for reassessment where required.

Engineering record
Draft
Approved
Superseded
Reassessed
Dependent records reassessed and re-approved
Capability architecture

Establish basis, identify hazards, analyse risk, define safeguards, demonstrate tolerability and verify performance

TSM navigation follows the safety-demonstration lifecycle from basis and hazard identification through analysis, safeguards, verification and evidence.

  • The safety basis

    The technical-safety basis retains risk-acceptance criteria, cost-of-averting-a-fatality inputs, governance documents and relevant regulatory frameworks.

    • Technical-safety basis
    • Risk-acceptance criteria
    • ICAF and VPF values
    • Governance documents
    • Regulatory frameworks
  • Identify

    The hazard register, major accident hazard designation, technical safety studies, workshops and the design intent that each hazard is assessed against.

    • Hazard register
    • Major-accident hazards
    • Technical-safety studies
    • Workshops
    • Design intent
  • Analyse

    Barrier models, layer-of-protection analysis, consequence analysis, quantitative risk assessment and escalation studies are retained as governed engineering records.

    • Bow-tie analysis
    • Layer-of-protection analysis
    • Independent-protection-layer library
    • Consequence
    • Quantitative risk assessment
    • Escalation analysis
    • Risk analysis
  • Safeguard

    Safety-critical elements, performance standards, fire and gas, fire protection, hazardous-area classification, escape, evacuation and rescue, and temporary-refuge assessment are governed as technical-safety design records.

    • Safety-critical elements and performance standards
    • Fire and gas
    • Fire protection
    • Hazardous-area classification
    • Escape, evacuation, rescue and temporary refuge
    • OBRA
  • Demonstrate and verify

    The safety case retains claims, arguments, evidence and defeaters together with tolerability demonstration and verification findings.

    • Safety case
    • ALARP
    • Verification schemes
    • Independent verification body findings
  • Engineering governance

    Calculation governance covers engines, methods, executions, references, engineering knowledge, mappings, technical-safety actions, assumptions and decisions.

    • Calculation governance
    • Engines and calculations
    • Engineering methods
    • Method executions
    • Controlled references
    • Technical-safety actions
    • Engineering assumptions
    • Engineering decisions
Design and operation

TSM governs safeguard definitions in design; PSM governs operational assurance

TSM governs the design definitions for barriers, safety-critical elements, safety instrumented functions, integrity targets, safety requirements specifications, performance standards and proof-test intervals, and publishes the approved definitions for operational use.

  • Offshore and onshore major-hazard regimes supported in one application
  • Occupational safety, incidents and permit-to-work processes are outside TSM scope
  • Enterprise risk remains governed in RMS rather than duplicated in TSM
Correct source data, not governed records

Rejected import rows are returned with stated reasons

Rejected rows are reported explicitly with validation reasons. Controlled import templates use organisation-approved values, and corrections are made in the source file before revalidation.

  • Comprehensive organisation extract packages
  • Dataset catalogue stating supported operations and governing rationale
  • Every load and extract is retained with its recorded outcome
  • Passing software tests alone does not constitute engineering certification is not certification

    Current calculation engines remain restricted from production use until required technical review, benchmark reproduction and technical-authority approval are complete.

  • No inferred compliance position

    TSM does not infer facility compliance or produce safety-integrity-level or quantitative-risk results without approved calculation methods. Where a supportable result is unavailable, the application reports that limitation.

  • Restricted records are reported as not visible rather than zero

    Where authorised users cannot access restricted records, the application reports them as not visible rather than as zero.

  • Approved records are superseded

    Approved engineering records are not edited in place. Supersession identifies dependent records requiring reassessment so approved demonstrations remain traceable.

Also in TSM

More of what the application covers

  • Safety case with claims, arguments, evidence and defeaters
  • Major-accident-hazard designation linked to the hazard register
  • Independent protection layer library behind layer-of-protection analysis
  • Performance standards retained against the safety-critical elements they govern
  • Verification schemes and independent verification body findings
  • Escape, evacuation and rescue with temporary refuge assessment
  • Read-only versioned access to governed engineering registers
  • Identity-based segregation of duties with append-only audit history
TSM

Review TSM using one of your safety cases.

Bring one major-accident hazard and its claimed safeguards. The demonstration will show resulting registers, verification requirements and any calculations that remain unavailable without approved methods.