The "V" Model organizes safety tasks in system lifecycles, ensuring early and ongoing safety focus. While it highlights a structured phase approach with verification and validation, alternatives like agile exist for different projects. It's crucial for traceability, change management, and error reduction, aiding in system safety and risk management

Phase 1: System Definition and Operational Context (Philosophy) - Define the functionality and environmental and operational paradigm of the system.

Inputs:

• Legislation and regulator guidance (Codes of Practice)
• Company policy/safety management system/ company standards (end user)
• Operational and maintenance requirements (end user)
• Autonomous mobile equipment specifications (from original product supplier) including functional product description
• Infrastructure/utility condition

Outputs:

• Concept of Operations (ConOps).
• Preliminary safety

Phase 2: Risk Analysis and Evaluation - Understand and document hazards, define risk criteria, and evaluate risks (consequence and frequency).

Inputs: Outputs from Phase 1 and:

• Company risk criteria (end-user).
• Relevant standards.
• Product design information (from OPS).

Outputs:

• Hazard log.
• System Safety management plan.
• Determine level of safety rigor required.

Phase 3: System Safety Requirements - To derive safety requirements from the risk analysis, standards, and regulations.

Inputs: Outputs from Phase 2 and:

• Site procedures.

Outputs:

• Safety requirements specification.
• System architecture, layer of protection analysis (LOPA), etc.
• Safety definition.

Phase 4: Design - Develop the system to the requirements.

Inputs: Outputs from Phase 3 and:

• Work design.
• Human-system interactions.

Outputs:

• Verification report of design to requirements.
• Test plan and impact/integration analysis.
• Design acceptance criteria.

Phase 5: Build Autonomous System - Build the system from the design and build confidence in safety systems are rigorously implemented with appropriate assurance.

Inputs: Outputs from Phase 4 and:

• Quality Management Plan.
• Inspection plan.

Outputs:

• As built diagrams.
• Quality assessment (QA) report.

Phase 6: Integration - Optimize system use with allied site systems.

Inputs: Outputs from Phase 5 and:

• System requirements specifications.
• Interface (e.g., application programming interface (API)) required and available.

Outputs:

• Verification of effective integration.
• Configuration management plan and governance model.

Phase 7: Commissioning and Testing - Verify the requirements have been delivered.

Inputs: Outputs from Phase 6 and:

• Functional and operational test plan.
• Test Specification.

Outputs:

• Test report.
• Commissioning documentation.

Phase 8: Validation - Demonstrate the overall system meets the requirements and expected performance.

Inputs: Outputs from Phase 7 and:

• Validation plan including acceptance criteria.

Outputs:

• Validation report.

Phase 9: Transition to Operations - Prepare the operations team to use the system.

Inputs: Outputs from Phase 8 and:

• Work design.
• Training requirements.
• Competency requirements.
• Workforce planning.
• Change management.
• Regulatory engagement or approvals.
• Historical record and lessons learned.
• Handover to operational team to use system.

Outputs:

• Safety case.
• Acceptance into service.
• Operational and maintenance procedures.
• Training needs assessment and procedures.
• Competencies assessments (including profiles for recruitment and resourcing).

Phase 10: Operate Autonomous System - Build confidence in the effective operation of the system and monitor its performance.

Inputs: Outputs from Phase 9 and:

• Operations and maintenance processes.

Outputs:

• Change requests and management.

Phase 11: System Upgrade Cycle - Conduct change and obsolescence management, performance reviews/incident response, and additional functionality implementation.

Inputs: Outputs from Phase 10 and:

• Details of any change.
• Details of functionality – scope and limitations.
• Competency requirements.
• Training requirements.
• Operations change requirements.

Outputs:

• Updated operations, maintenance, and training materials and systems.
• Updated risk assessment and controls.

Continuous improvement is the linking factor between phase 1 and 11, and refers to an iterative process of enhancing the development, functionalities, verification and validation methods, and overall safety and productivity of the autonomous system.

Continuous improvement involves systematically identifying areas for improvement and implementing measures to refine/improve system performance, address safety concerns, and meet evolving requirements throughout the system lifecycle.

Continuous improvement addresses the opportunities and challenges associated with implementing, operating, and adopting new technologies. Continuous improvement can be triggered by incidents, industry learnings, and/or product upgrades.

Return to Guideline for Applying System Safety in Mining :

• Private Link - visible for members of this organisation.
• Public Link - visible to anyone on the internet.