Safety Compliance Repository

Definition

Safety Compliance Repository

the safety work product that is a repository for all safety information

Classification

As illustrated in the preceding figure, Safety Compliance Repository is part of the following inheritance hierarchy:

• Type: Concrete
• Superclass: Repository
• Subclasses:
  • None

Responsibilities

The typical responsibilities of a Safety Compliance Repository are to:

• Ensure that all safety information is properly and securely stored.
• Ensure that all safety information is available to its stakeholders.
• Act as the central repository for all safety information.
• Act as the primary input to the safety compliance assessment task.
• Provide a historical record of safety information for future endeavors.

Contents

The typical contents of a safety compliance repository are:

• Safety Planning Information
  • The information from the safety program plan.
• Safety Risk Analysis Information
  • The information from the safety risk analysis report.
• Safety Status Information
  • The information from each safety status report.
• Accident Investigation Information
  • For each accident, the information from the accident investigation report.
• Related Information
  • References to enterprise and application identification information.
  • References to safety requirements.
  • References to safety mechanisms.
  • References to safety review and audit results.
  • Safety resource changes (e.g., staffing, training, tools).

Stakeholders

The typical stakeholders of the safety compliance repository are:

• Producer:
  • Safety Team
• Evaluators:
  • Safety Evaluation Team
• Approvers:
  • Project Management Team
  • Customer Representative
• Maintainers:
  • Safety Team
• Users:
  • Safety Team
  • Legal Department

Phases

• Business Strategy: Completed
• Business Optimization: Completed
• Initiation: Completed
• Construction: Maintained
• Delivery: Maintained
• Usage: Maintained
• Retirement: Archived

Preconditions

The safety log typically can be started if the following preconditions hold:

• The initiation phase is started.
• The safety team is staffed and trained in safety engineering.

Inputs

A safety compliance repository typically has the following inputs:

• Work Products:
  • Safety Work Products:
    • Accident Investigation Report
    • Safety Certificate
    • Safety Compliance Report
    • Safety Program Plan
    • Safety Risk Analysis Report
    • Safety Status Report
  • Other Work Products:
    • Safety Requirements
    • Safety Mechanisms
    • Safety Review Reports
    • Safety Audit Reports
• Stakeholders:
  • Requirements Engineers
  • System Architect
  • Quality Engineers
  • Test Engineers
  • Safety Domain Experts

Guidelines

• Scope.
  The scope of a safety compliance repository can be:
  • A business unit
  • A data or contact center
  • An application
  • A reusable component
  • Any other system.

Conventions

The safety compliance repository is typically constrained by the following conventions:

• Content and Format Standard
• MS Word Template
• XML DTD
• Evaluation Checklist

Examples

• Example Safety Compliance Repository