Section 2 Information to be submitted

2.1.1  In addition to the documentation and information associated with the Submarine Assurance Planning process, the documentation listed in this section is to be submitted.

2.2.1 A Standards Plan and Justification Document is to be submitted by the submarine designer.

2.2.2 The plan is to list the Submarine Assurance Framework Goals, Functional Objectives and Performance Requirements in accordance with the intended scope of verification.

2.2.3 The plan is to identify project specifications, Rules Codes and standards, the requirements of which, which when correctly applied, are considered to satisfy relevant framework Performance Requirements and therefore satisfy the corresponding Functional Objectives and Goals of the framework.

2.2.4 For each of the Performance Requirements in scope and the corresponding project specifications, Rules Codes and standards, the plan is to provide a justification for the proposed solution.

2.3.1 A Concept of Operations Statement (ConOpS) is to be submitted by the submarine Owner.

2.3.2 With respect to the submarine, the statement is to list the:

1. Particulars;
2. Owner;
3. Naval Administration;
4. Primary and secondary roles;
5. Attributes;
6. Operational area;
7. Operating environment;
8. Operating philosophy;
9. Survey, maintenance and disposal philosophy; and
10. Design life.

2.4.1 A System Operational Concept Document is to be submitted by the submarine designer for each system.

2.4.2 The document is to document the system operational concept and provide traceability to the ConOpS and is to describe the design intent and operational requirements for the key submarine systems.

2.4.3 The document will typically include the following systems as appropriate to the scope of verification:

1. Structural and watertight integrity;
2. Submarine control;
3. Manoeuvring;
4. Power and propulsion;
5. Energy storage, power generation and distribution;
6. Ballast, trim and compensation;
7. Life-support and protection;
8. Munitions storage and handling; and
9. Integrated damage control and fire protection.

2.4.4 The document is to include the following information, as appropriate to the system:

1. System function and performance requirements derived from the ConOpS;
2. Operating modes including abnormal, reversionary and emergency modes recognising the operational and manning philosophy for the submarine;
3. Design intent descriptions;
4. System, equipment and component safety criticality;
5. System, equipment and component dependencies;
6. Performance requirements necessary to maintain submarine functions for normal, abnormal and emergency operating conditions; and
7. Intended Operational envelope.

2.5.1 A System Design Document is to be submitted by the submarine designer for each system.

2.5.2 The document is to describe the system design and provide traceability to the System Operational Concept document for the systems, sub-components, equipment and is to detail their capability and functionality under normal, abnormal and emergency operating conditions.

2.5.3 The document is to include the following information, as relevant to the system:

1. Requirements derived from the System Operational Concept;
2. User interfaces, control and alert arrangements including reversionary and emergency modes recognising the operational and manning philosophy for the submarine;
3. System parameters (capacity, power, discharge rate, etc.);
4. System redundancy;
5. Performance degradation under extreme operating conditions;
6. Components, equipment and sub-systems;
7. The system safety definitions and safety functional requirements;
8. Justification of the selected system architecture; and
9. Design analysis results.