MODUK - DEF STAN 00-56: PART 1
Safety Management Requirements for Defence Systems Part 1: Requirements
|Publication Date:||28 February 2017|
Scope and Applicability
This Standard specifies the requirements for achieving, assuring and managing the safety of PSS defined by the scope of contract.
This Standard provides the Contractor with guidance for compliance with the requirements, thereby supporting the MOD in meeting their obligations with regard to the management of Risk to Life associated with the operation of military systems.
This Standard considers that a product can be an engineering artefact, whether physical Data or software, from the small scale, such as a pump or a digital map, to the large scale, such as a ship or a geographically distributed logistics application.
This Standard considers that a system is a combination of elements, with defined boundaries which are used together in a defined operating environment to perform a given task or achieve a specific purpose. These elements may include personnel, procedures, materials, tools, products, facilities, services and/or Data as appropriate.
This Standard considers a Service to be any activity using a System, eg providing air-to-air refuelling, running a naval dockyard or calculating the safe flight envelope for an aircraft, which are provided by the Contractor.
The Contractor, together with the MOD, has responsibility for safety of all deliverable PSS. This Standard is intended to cover the full range of possibilities including.
a) Where the Contractor has visibility and understanding of in-service Risk to Life, and can design PSS taking operation into account
b)Where the Contractor does not have visibility of in-service Risk to Life but is responsible for providing information to those who are responsible for in-service Risk to Life of the PSS.
The MOD considers all Defence Lines of Development for PSS, but this may not be included in the scope of contract, eg Concepts and Doctrine would consider Risk to Life and would be a MOD responsibility.
The responsibility of the Contractor also varies with the scope of analysis. This Standard is intended to cover the full range of possibilities including:
a) Enhanced, where the Contractor carries out safety engineering and safety management for the duty holder, beyond the deliverable PSS.
b) Full, where the Contractor carries out safety engineering and safety management for the deliverable PSS.
c) Reduced, where the Contractor carries out safety engineering and safety management only for parts or aspects of the deliverable PSS, eg for maintenance of a product.
The scope of analysis is intended to be adapted to the wide range of possible MOD acquisition scenarios.
Guidance on MOD safety management is available through the ASG.
Whilst Contract life may be limited, this Standard considers the whole life cycle of the PSS, including disposal. Various phases of the life of the PSS that need to be considered should be explicitly included within the scope of analysis. This applies to all in-service situations and scenarios including, but not limited to, trials, operations anc training for operations as defined in the Contract.
This Standard applies to all acquisition scenarios and all PSS but the responsibility of the Contractor varies with the scope of supply.
The distinction between scope of supply and scope of analysis is intended to facilitate the clear definition of the Contractor's responsibilities.
The scope of analysis may be extended beyond the scope of supply particularly where the contracted activity is limited to early phases of the CADMID/T cycle. The scope of analysis may need to cover the full CADMID/T cycle.
This Standard applies to PSS that have identified duty holders, supported by Safety Committees and relevant stakeholders.
For all PSS to which this Standard is applied a crown servant will retain responsibility and accountability for the Risk to Life. The scope of contract is agreed between the MOD and the Contractor and would identify duty holders and relevant stakeholders who are responsible for managing safety of the PSS. The relevant stakeholders may include representatives from MOD and Industry (for other related PSS) that may impact the PSS safety interfaces.
The mechanism for managing safety is through the agreed Safety Committees. Terms of Reference and membership will be specific to the scope of contract.
i. This Standard is specifically about safety and there is expectation that requirements will be set by the MOD and be included in the project documentation, eg capability, performance and reliability criteria and User and System Requirements Documents (URD/SRD).
ii. This clause is an indicative commitment from the MOD to the Contractor and a limitation on the scope of this Standard. The Contractor must assume that the MOD has a Safety Management System (SMS) for their PSS responsibilities, eg a Safety Committee exists prior to Invitation to Tender (ITT). Agreeing a scope of contract is intended to clarify responsibilities between the MOD and the Contractor. As the PSS evolves through life the scope cf contract may need to be revisited and may neer to be renegotiated.
iii. The interface and degree of support/co-operation
iv. One of the main mechanisms of the MOD SMS is managing safety through the relevant Safety Committees. The Contractor's Terms of Reference and membership of Safety Committees will be specific, to the agreed scope of contract, and based on POSMS guidance.
vi. Where there is any doubt over the validity of assumptions, or the scope of analysis the contractor must discuss resolution with the MOD.