SPEG 1.4 DTD 22 June 11.pdf

System Operational Verification Test

(SOVT)

Preparation and Execution Guide (SPEG) for Ship, Shore, and Submarine Installations

Version 1.4

Space and Naval Warfare Systems Command Command, Control, Communications, Computers and Intelligence

Program Executive Office

22 June 2011

DISTRIBUTION STATEMENT D: Distribution authorized to Department of Defense (DoD) and U.S. DoD contractors only. (February 2008) Other requests shall be referred to: Commander, Space and Naval Warfare Systems Command, 4301 Pacific Highway, San Diego California 92110-3127

DESTRUCTION NOTICE: For UNCLASSIFIED, limited distribution of documents, destroy by any method that will prevent disclosure of contents or reconstruction of the document.

This page intentionally left blank

COMSPAWAR M-3084.1

SOVT Preparation and Execution Guide Record of Changes

Version 1.4 22 June 2011 iv

Record of Changes

Version Date Changed by Description of Change

1.1 09 Oct 2007 SOVT LSS Team Review Update to figure 4-1 and section 4

1.2 03 Nov 2008 SOVT LSS Team Review Update to Distribution Statement, update to Figures 4-2 and 6-2, update to paragraph 4.8

1.3 06 May 2010 4.0/5.0 Process Owners Multiple corrections after usage since v1.2. Specifically more detail on Test Element mapping in sections 5, 6, and Appendix A.

1.4 4.0/5.0 Process Owners Multiple corrections after usage since v1.3. Lessons learned incorporated on responsibilities and Test Element mapping in sections 4, 5, 6, 7 and Appendix A and D

SOVT Preparation and Execution Guide Table of Contents

Version 1.4 22 June 2011 v

Version 1.4 22 June 2011 vi

Table of Contents

1. INTRODUCTION............................................................................................................. 1–1

1.1. SCOPE AND APPLICABILITY .......................................................................................... 1–1

1.1.1. SOVT Definition (Boundaries) ............................................................................ 1–1

1.2. PURPOSE ...................................................................................................................... 1–2

2. APPLICABLE DOCUMENTS ........................................................................................ 2–1

2.1. AFLOAT AND SHORE COMMON GUIDANCE DOCUMENTS ............................................. 2–1

2.1.1. Government Specifications and Standards ......................................................... 2–1

2.1.2. Commercial/Industry Specifications and Standards ........................................... 2–1

2.2. AFLOAT ONLY GUIDANCE DOCUMENTS ...................................................................... 2–1

2.2.1. Government Specifications and Standards ......................................................... 2–1

2.2.2. Commercial/Industry Specifications and Standards ........................................... 2–2

2.2.3. Naval Sea Systems Command Documents .......................................................... 2–2

2.3. SHORE ONLY GUIDANCE DOCUMENTS ........................................................................ 2–3

2.3.1. Military Specifications and Standards ................................................................ 2–3

2.3.2. Commercial/Industry Specifications and Standards ........................................... 2–4

2.4. ORDER OF PRECEDENCE ............................................................................................... 2–4

3. DEFINITIONS .................................................................................................................. 3–1

4. SOVT PROCESS .............................................................................................................. 4–1

4.1. PROCESS STEPS ............................................................................................................ 4–2

4.1.1. Development of System SOVT Document Process Steps .................................... 4–2

4.1.2. Development of Platform SOVT Document Process Steps ................................. 4–3

4.1.3. SOVT Execution and Closeout Process Steps ..................................................... 4–4

4.2. ROLES AND RESPONSIBILITIES FOR SOVT DEVELOPMENT PHASE ............................... 4–5

4.2.1. Program or Project Office .................................................................................. 4–5

4.2.2. SOVT IPT ............................................................................................................ 4–6

4.3. ROLES AND RESPONSIBILITIES FOR SOVT EXECUTION PHASE .................................... 4–6

4.3.1. Installation Activity Installation Management Office (IMO).............................. 4–6

4.3.2. AIT Manager/OSIC/NTR or Shore PE/OSGR .................................................... 4–6

4.3.3. Installation Team ................................................................................................ 4–7

4.3.4. SOVT Manager/SOVT Team ............................................................................... 4–7

4.4. PREPARING FOR SOVT EXECUTION ............................................................................. 4–7

4.5. EXECUTING THE SOVT ................................................................................................ 4–7

4.5.1. Recording, Monitoring, and Reporting ............................................................... 4–8

4.5.2. Discrepancy Tracking and Resolution ................................................................ 4–8

4.5.3. Platform SOVT Sign Off...................................................................................... 4–8

4.6. REPORTING REQUIREMENTS ........................................................................................ 4–8

4.7. REPOSITORY OR APPLICABLE TOOLS REQUIREMENTS ................................................. 4–8

4.8. APPROVAL REQUIREMENTS AND CHANGE CONTROL PROCESS .................................... 4–8

5. GENERAL REQUIREMENTS ....................................................................................... 5–1

5.1. FORMAT REQUIREMENTS ............................................................................................. 5–1

Version 1.4 22 June 2011 vii

5.1.1. Standardized SOVT Document Structure............................................................ 5–1

5.1.2. Acceptable Formats for SOVT Documents ......................................................... 5–4

5.1.3. Acceptable Data Formats for Test and Inspection Results ................................. 5–4

5.1.4. File Size ............................................................................................................... 5–4

5.1.5. Wording of Text/Style .......................................................................................... 5–5

5.2. TEST REQUIREMENTS FOR VARIOUS INSTALLATION TYPES ......................................... 5–5

5.2.1. Minimum Required Tests and Inspections .......................................................... 5–5

5.2.2. Factors Influencing Amount of Testing Required ............................................... 5–8

5.2.3. Level of Writing Detail........................................................................................ 5–8

6. SYSTEM SOVT DOCUMENT DEVELOPMENT ....................................................... 6–1

6.1. TEST ELEMENT ANALYSIS, SELECTION, AND ASSIGNMENT ......................................... 6–1

6.1.1. Analysis of System Functional and Key Performance Characteristics .............. 6–3

6.1.2. Analysis of Interface Requirements .................................................................... 6–3

6.1.3. Test Element Selection ........................................................................................ 6–4

6.1.4. Assigning Test Elements to a Test Stage ............................................................. 6–4

6.1.5. Developing the SOVT Document Outline and Test Procedures ......................... 6–5

6.2. DOCUMENT CONTENTS ................................................................................................ 6–6

6.2.1. Front Matter Requirements................................................................................. 6–6

6.2.2. Section 1: Introduction and Administration ....................................................... 6–6

6.2.3. Section 2: Inspection and Validation Tests (Stage 1) ......................................... 6–8

6.2.4. Section 3: Cold Checks (Stage 2) ...................................................................... 6–12

6.2.5. Section 4: Equipment Tests (Stage 3) ............................................................... 6–14

6.2.6. Section 5: Intra-System Tests (Stage 4) ............................................................ 6–16

6.2.7. Section 6: Inter-System Tests (Stage 5) ............................................................ 6–19

6.2.8. Section 7: Operational Tests (Stage 6) ............................................................. 6–21

6.2.9. Section 8: At-Sea and Other Special Tests (Stage 7) ........................................ 6–22

6.2.10. Appendix A – Configuration Audit Results ....................................................... 6–23

6.2.11. Appendix B – Record of SOVT Discrepancies .................................................. 6–23

6.2.12. Appendix C – SOVT Signature Page ................................................................ 6–23

6.2.13. Appendix D – Test Element Assignment Mapping Table .................................. 6–23

7. PLATFORM SOVT DOCUMENT DEVELOPMENT ................................................. 7–1

7.1. SINGLE SYSTEM INSTALLATION ................................................................................... 7–1

7.1.1. Test Element Analysis and Selection................................................................... 7–1

7.1.2. Document Approval and Storage ........................................................................ 7–1

7.2. MULTIPLE SYSTEM INSTALLATION .............................................................................. 7–2

7.2.1. Analyzing and Synchronizing Test Requirements ............................................... 7–2

7.2.2. Preparing for SOVT Execution ........................................................................... 7–5

7.2.3. Determine Redundant Interface Testing ............................................................. 7–5

7.2.4. Special Testing Requirements for Multiple System Installations ........................ 7–6

7.2.5. SOVT Execution .................................................................................................. 7–6

APPENDIX A: SOVT TEMPLATE .......................................................................................... A

APPENDIX B: SOVT DOCUMENT APPROVAL CHECKLIST .......................................... B

Version 1.4 22 June 2011 viii

APPENDIX C: ACRONYMS USED IN THIS DOCUMENT ................................................. C

Version 1.4 22 June 2011 ix

List of Figures

FIGURE 4-1. SOVT PROCESS ....................................................................................................... 4–1 FIGURE 4-2. SOVT CHANGE CONTROL PROCESS ........................................................................ 4–9 FIGURE 6-2. TEST ELEMENT ASSIGNMENT MAP (TEAM)............................................................ 6–5 FIGURE 7–1. NETWORK DIAGRAM ............................................................................................... 7–5

List of Tables

TABLE 2–1. GOVERNMENT SPECIFICATIONS AND STANDARDS–AFLOAT AND SHORE .................. 2–1

TABLE 2–2. COMMERCIAL/INDUSTRY SPECIFICATIONS AND STANDARDS–AFLOAT AND SHORE . 2–1

TABLE 2–3. GOVERNMENT SPECIFICATIONS AND STANDARDS–AFLOAT ONLY ........................... 2–2

TABLE 2–4. COMMERCIAL/INDUSTRY SPECIFICATIONS AND STANDARDS–AFLOAT ONLY .......... 2–2 TABLE 2–5. NAVSEA DOCUMENTS–AFLOAT ONLY ................................................................... 2–2 TABLE 2–6. MILITARY SPECIFICATIONS AND STANDARDS–SHORE ONLY .................................... 2–3 TABLE 2–7. COMMERCIAL/INDUSTRY SPECIFICATIONS AND STANDARDS–SHORE ONLY ............ 2–4

TABLE 3–1. DEFINITIONS ............................................................................................................. 3–1 TABLE 4-1. SOVT CHANGE REQUEST FORM ............................................................................. 4–10

TABLE 4-2. SOVT CHANGE NOTICE FORM ................................................................................ 4–11 TABLE 5–1. MINIMUM REQUIRED TESTS AND INSPECTIONS ........................................................ 5–6 TABLE 6–1. MINIMUM STAGE 1 REQUIREMENTS FOR COMMON INSTALLATION TASKS ............... 6–9

TABLE 6–2. MINIMUM STAGE 2 REQUIREMENTS FOR COMMON INSTALLATION TASKS ............. 6–12 TABLE 6–3. MINIMUM STAGE 3 REQUIREMENTS FOR COMMON INSTALLATION TASKS ............. 6–14

TABLE 6–4. MINIMUM STAGE 4 REQUIREMENTS FOR COMMON INSTALLATION TASKS ............. 6–16 TABLE 6–5. MINIMUM STAGE 5 REQUIREMENTS FOR COMMON INSTALLATION TASKS ............. 6–19

TABLE 6–6. MINIMUM STAGE 6 REQUIREMENTS FOR COMMON INSTALLATION TASKS ............. 6–22 TABLE 7–1. DEPENDENCY TABLE ................................................................................................ 7–4

SOVT Preparation and Execution Guide Introduction

Version 1.4 22 June 2011 x

Version 1.4 22 June 2011

1–1

1. Introduction This document is the result of a Lean Six Sigma study undertaken to improve the Team SPAWAR

(herein referred to as SPAWAR) System Operational Verification Test (SOVT) process. The expected benefits of using this document are the following:

Reduction in installation planning and design time and consequent reduction in planning and design cost

Improved readiness for operational units through improved testing

Reduced operational risk

Improved customer relations

Better SOVT documentation

Better understanding of roles and responsibilities

Fewer SOVT discrepancies and improved tracking and resolution.

1.1. Scope and Applicability

The purpose of this document is to provide detailed guidance for the development of SPAWAR standardized System SOVTs, development of Platform SOVTs, approval of SOVT documents, execution of approved SOVTs, and recording SOVT discrepancies. Applicability is further defined in

SPAWARINST 3084.1 of 03 Dec 08.

Even for a one-of-a-kind install, the requirements identified in the SPEG shall be followed. For a one-of-a-kind install, the System and the Platform SOVT may be one and the same document.

Any change to a hardware or software configuration at an operational or training facility requires a

SOVT compliant with the guidance contained in this document. This includes alterations, engineering changes, field changes, software deliveries, temporary installations, prototype installations, and removals. For software pushes that require no validation of post-installation functionality, a SOVT is not required. For removal of stand-alone systems or removals with no impact to remaining configuration/systems, a SOVT is not required.

1.1.1. SOVT Definition (Boundaries)

SOVT is defined as:

A test or battery of tests that verifies the installed or modified equipment, systems, interfaces with existing systems, and systems impacted by the installation are properly installed and operates as intended at the platform specific location and environment.

The SOVT document is defined as:

A version-controlled and approved test plan that provides procedures for performing defined system parameter checkout as a result of a system installation or upgrade.

The document that provides procedures with pass/fail criteria as applicable to verify and validate safety, security, environmental conditions, signal connectivity, configuration

(e.g., strapping, ECs, etc.), internal and external system interfaces, system integration, Version 1.4 22 June 2011

1–2 offline/online system functionality, all required operational modes, any impacted equipment/systems functionality, and as-designed operating requirements. When required to verify external system interfaces or functions that can only be tested with another platform, the SOVT document contains procedures to test the operational interface and functionality with other platforms.

The document that provides procedures and tables for recording test results, conducting a final equipment inventory, and documenting the system baseline results at the end of testing.

The signed SOVT document is defined as:

A completed or executed SOVT plan that has been witnessed and signed, with all test results and any discrepancies recorded.

1.2. Purpose

The purpose of the SOVT process and documentation is to verify, validate, and demonstrate that the newly installed equipment, system, or systems and all other affected systems are operating as intended.

SOVT Preparation and Execution Guide Applicable Documents

Version 1.4 22 June 2011

2–1

2. Applicable Documents The following specifications, standards, handbooks, and instructions form a part of this document to the extent specified herein. Unless otherwise specified, the issues of military specifications and standards are those listed in the issue of the Department of Defense Index of Specifications and

Standards and supplement thereto, cited in the solicitation.

2.1. Afloat and Shore Common Guidance Documents

The following specifications, standards, and handbooks apply to both Afloat and Shore installation requirements. The standards listed are the latest available as of the date of this document. Users are responsible for ensuring that the standards they are using are current.

2.1.1. Government Specifications and Standards

Table 2–1 lists the applicable Government specifications and standards for Afloat and Shore installation.

Table 2–1. Government Specifications and Standards–Afloat and Shore

Document ID Title

MIL-STD-188-114A(1) Electrical Characteristics of Digital Interface

Circuits

MIL-STD-1472F(1) Design Criteria Standard, Human Engineering

MIL-HDBK-759C(2) Human Engineering Design Guidelines

DODD 5230.24 Distribution Statements on Technical Documents

2.1.2. Commercial/Industry Specifications and Standards

Table 2–2 lists the applicable Commercial/Industry specifications and standards for Afloat and Shore installations.

Table 2–2. Commercial/Industry Specifications and Standards–Afloat and Shore

Document ID Title

ASME Y14.38-1999 (with Y14.38A-

2002 Addenda)

Abbreviations and Acronyms

H4/H8, Cataloging Handbook H4/H8 Commercial and Government Entity (CAGE)

2.2. Afloat Only Guidance Documents

The following specifications, standards and handbooks apply to Afloat installations only.

2.2.1. Government Specifications and Standards

Table 2–3 lists Government specifications and standards for Afloat installations.

Version 1.4 22 June 2011

2–2

Table 2–3. Government Specifications and Standards–Afloat Only

Document ID Title

MIL-STD-1310G Shipboard Bonding, Grounding and Other Techniques for Electromagnetic Comparability and Safety

MIL-STD-1399C Interface Standard for Shipboard Systems

MIL-STD-1399-300A(1) Interface Standard for Shipboard Systems Section 300, Electric Power, Alternating Current (Metric)

MIL-STD-1399-390 Interface Standard for Shipboard Systems Section 390, Electric Power, Direct Current, (Other than Ship‟s

Battery) for Submarines (Metric)

MIL-STD-1399-502A Interface Standard for Shipboard Systems Section 502, Electronic Systems Parameters

DOD-STD-1399-304(1) Interface Standard for Shipboard Systems Section 304, Electrical Cables and Connectors

DOD-STD-1399-441 Interface Standard for Shipboard Systems Section 441, Precise Time and Time Interval (PTTI)

MIL-HDBK-290(1) Standard Electrical Symbol List

DOD-STD-2106 (NAVY) Development of Shipboard Industrial Test Procedures

2.2.2. Commercial/Industry Specifications and Standards

Table 2–4 lists Commercial/Industry specifications and standards for Afloat installations.

Table 2–4. Commercial/Industry Specifications and Standards–Afloat Only

Document ID Title

ANSI Y32.10-1967(R1999) Graphic Symbols for Fluid Power Diagrams

IEEE-200-1975 Reference Designations for Electrical and Electronics

Parts & Equipments

ASTM F 856 Standard Practice for Mechanical Symbols, Shipboard

Heating Ventilation and Air Conditioning (HVAC)

2.2.3. Naval Sea Systems Command Documents

Table 2–5 lists applicable Naval Sea Systems Command (NAVSEA) documents.

Table 2–5. NAVSEA Documents–Afloat Only

Document ID Title

S-0300-AT-GTP-0l0/ESL Standard Electrical Symbol List.(MIL-HDBK-290)

SE000-00-EIM-110 Electronics Installation and Maintenance Book, Installation Standards (NIMB)

0967-LP-000-0130 Electronics Installation and Maintenance Book, Test

Methods and Practices

Version 1.4 22 June 2011

2–3

Document ID Title

S9407-AB-HDBK-010 REV 2 Handbook of Shipboard Electromagnetic Shielding

Practices

NAVSEA Drawing No. 53711-803-

5001049

Piping System Symbols and Abbreviations

NAVSEA TS 9090-310D Alterations to Ships Accomplished by Alteration Installation Teams

S9AA0-AB-GOS-010-GSO REV 4 General Specifications for Overhaul of Surface Ships

2.3. Shore Only Guidance Documents

The following specifications, standards, and handbooks apply to Shore sites only.

2.3.1. Military Specifications and Standards

Table 2–6 lists Military specifications and standards for Shore installations.

Table 2–6. Military Specifications and Standards–Shore Only

Document ID Title

MIL-STD-188-124B(3) Grounding, Bonding and Shielding for Common Long

Haul/Tactical Communication Systems Including

Ground Based Communications-Electronics Facilities and Equipments

MIL-HDBK-411B(1), Vol 1-3 Power and the Environment for Sensitive DOD

Electronics Equipment

MIL-HDBK-419A Grounding, Bonding & Shielding for Electronic Equipments & Facilities, volume 1 & 2

MIL-HDBK-1004/7 Wire Communications and Signal Systems

MIL-HDBK-1012/1 Electronic Facilities Engineering

MIL-HDBK-1012/3 Telecommunications Premises Distribution, Planning, Design & Estimating

NAVSO P-5239-22 Protected Distribution System (PDS) Guidebook

OPNAV INST 5100.23G Navy Safety and Occupational Health (SOH) Program

Manual

OPNAV INST 5530.14D Navy Physical Security and Law Enforcement

OPNAV INST 5090.1C Environmental & Natural Resources Program Manual

UFC 3-520-01 Interior Electrical Systems

UFC 3-550-03N Design, Power Distribution Systems

UFC 3-560-10N Safety of Electrical Transmission & Distribution

Systems

UFC 3-600-1 Fire Protection Engineering for Facilities

Version 1.4 22 June 2011

2–4

Document ID Title

UFGS 16710 Building Telecommunications Cabling Systems

UFGS 26 2000 Interior Distribution Systems

EM385-1-1 U.S. Army Corps of Engineers Safety and Health

Requirements

USDA RUS Bulletin 1753F-201(PC-4) Standards for Acceptance Tests and Measurements of

Telecommunications Plant

--- SPAWAR Shore Installation Process Handbook

2.3.2. Commercial/Industry Specifications and Standards

Table 2–7 lists Commercial/Industry specifications and standards for Shore installations.

Table 2–7. Commercial/Industry Specifications and Standards–Shore Only

Document ID Title

NFPA 70 National Electrical Code (NEC)

NFPA 780 Standard for the Installation of Lightning Protection

Systems

ANSI/NECA/BICSI-568-2006 Standard for Installing Commercial Building

Telecommunications Cabling

TIA-942 Telecommunications Standard for Data Centers

TIA/EIA-568-B.1 Commercial Building Telecommunications Cabling Standard, Part 1, General Requirements

ANSI/EIA/TIA-526-14A Optical Power Loss Measurements of Installed

Multimode Fiber Cable Plant

ANSI/TIA/EIA-526-7 Optical Power Loss Measurements of Installed

Singlemode Fiber Cable Plant

ANSI/TIA/EIA-455-59A Measurement of Fiber Point Discontinuities Using an

OTDR

ANSI/TIA/EIA-455-60A Measurement of Fiber or Cable Length Using an

OTDR

ANSI/TIA/EIA-455-61A Measurement of Fiber or Cable Attenuation Using an

OTDR

2.4. Order of Precedence

This SPEG is a process guide that directs steps to accomplish a SOVT. As a process guide, this

SPEG takes precedence when developing and conducting a SOVT. However, the cited references take precedence with regard to technical standards to be employed in the conduct of the SOVT.

Nothing in this document, however, supersedes applicable laws and regulations unless a specific exemption has been obtained.

SOVT Preparation and Execution Guide Definitions

Version 1.4 22 June 2011

3–1

3. Definitions For the purpose of this document, the definitions listed in Table 3–1 apply.

Table 3–1. Definitions

Term Definition

At-Sea Testing A test or a series of tests performed on equipment or systems in a real time “At-Sea” scenario. Testing of this type may involve RF emissions that cannot be conducted in port, or it may involve the verification of a specific system function that can only be tested in an underway ship-to-shore operational scenario.

C4ISR System Any equipment or system that provides Command, Control, Communications, Computers, Intelligence, Surveillance, and Reconnaissance services.

Characteristic Any quality, property, capacity, or attribute of equipment or a system that defines performance requirements.

Combat System Any equipment or system that provides functions for the purpose of detecting, tracking, identifying, processing, evaluating, and controlling the engagement of hostile threats.

End-to-End Testing End-to-End Testing, for the purposes of this document, is defined as the testing of an installed system or systems from user to user. It does not include the testing of systems unrelated or not impacted by the installation.

Equipment A single unit of hardware or closely related group of hardware units that for testing purposes cannot be independently tested.

Function Any intended operation of equipment or a system that defines performance requirements.

Grooming Activities or actions taken to clean, align, adjust, and repair equipment or a system. Procedures for this work are not normally included in the SOVT document.

Inspection An examination of the physical aspects of equipment or a system installation (e.g., physical appearance, materials used, and location conforms to approved design) to determine work is complete and accurate, workmanship, pre-requisite conditions, etc.

Version 1.4 22 June 2011

3–2

Term Definition

Integrated SOVT For the purposes of this document, an Integrated SOVT and

Consolidated SOVT are synonymous. They occur when multiple systems are installed together as one installation effort. The Integrated or Consolidated SOVT is designed to test each installed system and each affected system in a systematic and synchronized sequence based upon a functional dependency analysis. These comprehensive tests and analyses of more than one system installed in a nearly concurrent effort verify all individual system functionality as well as the extended functionality of the entire suite of systems.

Interface An electrical or mechanical connection between two or more equipment items or systems.

Inter-System Tests Inter-system Tests are defined as testing between the installed or changed system and the other systems with which it interfaces. These tests shall include interface testing and the testing of any function requiring more than one system to perform.

Intra-System Tests For the purposes of this document, Intra-system Tests are defined as those that are performed within a single system. It may include tests between equipment or groups of equipment within the same system to determine the functional status of the equipment or system, including internal interfaces.

Key Performance Parameters Those characteristics or functions that define the critical performance requirements of equipment or a system.

Off-line Testing A test or a series of tests that are conducted while the equipment/system is in a non-operational or “Off-line” state.

On-line Testing On-line functional tests are normally limited to the testing of functions that cannot be tested “Off-line”. “On-line” tests may include the insertion and analysis of defined patterns, automatic error generators, or a pre-defined data sample into an operational “On-Line” system or equipment in order to verify that the system is operating as intended. “On-line” testing may also involve testing a specific operational scenario in order to validate that the system operates in that specific operational situation. “On-line” testing can also include a limited period during which normal operations are observed and results recorded.

Version 1.4 22 June 2011

3–3

Platform End-to-End Testing A series of tests designed to groom and prepare a platform for deployment. These tests may include the entire installed

C4I suite of systems on a platform or some subset or specific mission area such as communications. The Platform End-to-

End Testing is not considered part of SOVT since it extends beyond the purpose of checking out the newly installed equipment or systems.

Platform SOVT A tailored SOVT that provides specific testing procedures for an equipment or system installation/upgrade at a designated Ship, Submarine, or Shore facility. The Platform

SOVT is derived from the SPEG-compliant, Technical Authority approved System SOVT.

Pre-Installation Checkout (PICO) This testing is conducted at the installation platform on the existing or already installed system and equipment.

Sometimes referred to as “Baseline System Testing”, the purpose of these tests is to establish a functional baseline of the existing system before the installation begins. PICO differs from PITCO in that this testing is on the existing system vice the new equipment or system. PICO testing, if performed, precedes SOVT and is not considered part of

SOVT.

Pre-Installation Test and Checkout

(PITCO)

A test or series of tests that provides a level of confidence that the new equipment or system received from a vendor or assembled by the government that shall be delivered for installation is fully operational. PITCO testing, if performed, precedes on-site installation and is not considered part of

SOVT.

Pre-Installation Tests A type of testing that is conducted on new or existing equipment or systems that precede the on-site installation.

PICO and PITCO are both examples of Pre-Installation Tests.

Pre-SOVT Activities conducted prior to and during Stage 1 testing (e.g., configuration, design, and production verification actions; a dry-run SOVT without the customer's presence).

Software Application Modular code designed to perform a set of specific functions.

System A combination of two or more equipment items that operate in concert to accomplish the required set of performance requirements.

Version 1.4 22 June 2011

3–4

System SOVT A System SOVT provides the standard baseline all-encompassing test procedures for a specific system architecture/configuration. The System SOVT is the parent document from which a Platform SOVT will be developed.

Test For the purposes of this document, tests are a predetermined set of conditions, operations, and measurements that are formally documented in test procedures and recorded results that, when correctly performed, verify and validate the equipment and system installation and enable a quantitative assessment of installation operability and readiness to support mission objectives.

Test Elements Any equipment or system characteristic, function, or interface that may be verified or demonstrated through testing.

Test Procedures A detailed step-by-step description of the operations to be performed during the conduct of a specific test. Test procedures provide information and forms to plan for, conduct the test, record the test results, and identify the test pass/fail requirements.

Test Staging A building block approach, where each subsequent test stage builds upon known test results from previous test stages. For the purposes of this document, test stages are defined as follows:

Stage 1: Inspection and Validation

Stage 2: Cold Checks

Stage 3: Equipment Tests

Stage 4: Intra-system Tests

Stage 5: Inter-system Tests

Stage 6: Operational Tests

Stage 7: At-Sea and Other Special Tests

Validation Tests the performance of a system within its intended operational environment with anticipated operators and users.

Verification Confirms that the system meets the design-to or build-to specifications; for SOVTs, tests the installed system against its as-designed requirements.

SOVT Preparation and Execution Guide SOVT Process

Version 1.4 22 June 2011

4–1

4. SOVT Process The SOVT development and execution process is shown in figure 4-1. The process consists of three major components: development of a

System SOVT document; development of a Platform SOVT document; and SOVT execution and closeout.

Figure 4-1. SOVT Process

Feedback mechanisms created to correct discrepancies in the test procedures

P ro je c t

O ff ic e

(e .g

P ro d u c t

P M

W P ro je c t

M a n a g e r)

S y s te m s E n g in e e ri n g

(e .g

S

P A

W A

R

.0

In s ta ll a ti o n

A c ti v it y

(e .g

S

P A

W A

R

.2

SOVT CAO IPT Review

N/A

Start

System

SOVT

exist?

IAW the

SPEG,

Project

Office develops

System

SOVT with

System

Engineering support

No

Develop Platform

SOVT IAW System

SOVT & SPEG,

upload to respository by A-4/I-4

Coordinate and schedule

SOVT with

Platform

Conduct Pre-

SOVT tests and inspections

Conduct Test

IAW Platform-

SOVT in the presence of witness

Add discrepancy list to draft completion message/

Alteration

Completion Report

Track discrepancies and resolve

End

Test

Discrepan

-cies?

No

Conduct

Sign-off with witnesses & upload signed

SOVT

Complies with SPEG?

Yes

No

SOVT CAO

IPT reviews

System

SOVT &

provide comment

Incorporate revisions to

System

SOVT

SOVT CAO IPT:

- Product PM/Project Mgr

- Appointed Tech Authority

- System Engineer (e.g., APM-E)

- ISEA

Upload

System

SOVT to repository by

A-8/ I-8

Obtain

Platform

SOVT

Yes

System SOVT Discrepancy Feedback (see Figure 4.2)

Platform SOVT Discrepancy Feedback (see Figure 4.2)

Yes

Platform

SOVT

exists ?

No

Yes

PM/Proj Mgr signs System

SOVT

certifying tech suitability & compliance w/ SPEG

TA signs

PM/Proj Mgr establish

SOVT CAO

IPT

TA review

& approve

Yes

No

When required SOVT CAO IPT, co-chaired by PM & TA, reviews and approves System SOVT

System

SOVT

developed

IAW SPEG

standard Defined clear roles and responsibilities for SOVT execution and discrepancy tracking

Library of approved

System SOVTs

(repository)

Develop and Approve Execute Track and FeedbackPlan

Platform SOVT based upon approved System SOVT

TA reviews for suitability and compliance

PM/Proj. Mgr signs verifying tech suitability and compliance w/ SPEG

Feedback mechanisms created to correct discrepancies in the test procedures

P ro je c t

O ff ic e

(e .g

P ro d u c t

P M

W P ro je c t

M a n a g e r)

S y s te m s E n g in e e ri n g

(e .g

S

P A

W A

R

.0

In s ta ll a ti o n

A c ti v it y

(e .g

S

P A

W A

R

.2

SOVT CAO IPT Review

N/A

Start

System

SOVT

exist?

IAW the

SPEG,

Project

Office develops

System

SOVT with

System

Engineering support

No

Develop Platform

SOVT IAW System

SOVT & SPEG,

upload to respository by A-4/I-4

Coordinate and schedule

SOVT with

Platform

Conduct Pre-

SOVT tests and inspections

Conduct Test

IAW Platform-

SOVT in the presence of witness

Add discrepancy list to draft completion message/

Alteration

Completion Report

Track discrepancies and resolve

End

Test

Discrepan

-cies?

No

Conduct

Sign-off with witnesses & upload signed

SOVT

Complies with SPEG?

Yes

No

SOVT CAO

IPT reviews

System

SOVT &

provide comment

Incorporate revisions to

System

SOVT

SOVT CAO IPT:

- Product PM/Project Mgr

- Appointed Tech Authority

- System Engineer (e.g., APM-E)

- ISEA

Upload

System

SOVT to repository by

A-8/ I-8

Obtain

Platform

SOVT

Yes

System SOVT Discrepancy Feedback (see Figure 4.2)

Platform SOVT Discrepancy Feedback (see Figure 4.2)

Yes

Platform

SOVT

exists ?

No

Yes

PM/Proj Mgr signs System

SOVT

certifying tech suitability & compliance w/ SPEG

TA signs

PM/Proj Mgr establish

SOVT CAO

IPT

TA review

& approve

Yes

No

When required SOVT CAO IPT, co-chaired by PM & TA, reviews and approves System SOVT

System

SOVT

developed

IAW SPEG

standard Defined clear roles and responsibilities for SOVT execution and discrepancy tracking

Library of approved

System SOVTs

(repository)

Develop and Approve Execute Track and FeedbackPlan

Platform SOVT based upon approved System SOVT

TA reviews for suitability and compliance

PM/Proj. Mgr signs verifying tech suitability and compliance w/ SPEG

Version 1.4 22 June 2011

4–2

4.1. Process Steps

The steps for developing and approving the System SOVT document are identified in section 4.1.1;

the steps for developing and approving the Platform SOVT document in section 4.1.2; and the steps for SOVT execution and closeout in section 4.1.3. Other required system turnover aspects of the installation such as logistics support materials, training, etc. are not part of SOVT, but are part of the turnover process and are recorded in an “Alteration/Installation Completion Report.” All open installation discrepancies are also recorded in a draft completion message that the customer is asked to provide. Upon successful completion of the SOVT, the platform assumes all operations and maintenance responsibilities.

4.1.1. Development of System SOVT Document Process Steps

1. Determine if System SOVT exists (reference figure 4-1, step 1)

1) Description: Review system/project/program records to determine if a System SOVT document exists

2) Inputs: system/project/program test records and history files

3) Product (Output): System SOVT if test records exist. No output if records do not exist

4) Responsible: Program/Project Office

I. SPEG Compliance Certification: Certified by Developer

II. Completed: When records search completed.

2. Develop, review, and certify System SOVT (reference figure 4-1, step 2-3)

Description: Consult and follow sections 5 and 6 of SPEG to develop System SOVT. Use SOVT checklist in Appendix B to ensure SOVT document is complete. After the draft System SOVT is signed by the PM, APM, or Project Manager certifying that the SOVT document is technically suitable and complies with the SPEG, upload the document into the SPAWAR/PEO Integrated Data

Environment & Repository (SPIDER) SOVT module workflow.

1) Inputs: Current version of SPEG, any applicable system documentation and SOVT checklist

2) Product (Output): Program/Project Office signed System SOVT document

3) Responsible: Program/Project Manager

I. Approval/Signature Authority: Program/Project Manager

II. Completed: After completion of sections 5 and 6 of SPEG and reviewed using

SOVT checklist.

3. Technical Authority reviews the System SOVT (reference figure 4-1, step 4).

1) Description: Tech Authority reviews SOVT for technical suitability and compliance with the SPEG; if not suitable or compliant SOVT is returned to Program/Project Manager. If approved go to process step 5 of this section (reference figure 4-1, step 9).

2) Inputs: Program/Project Office signed System SOVT document

3) Product (Output): Approved/disapproved System SOVT

4) Responsible: Tech Authority

5) Approval/Signature Authority: Tech Authority

6) Completed: After completion of review and approval/disapproval of the provided

System SOVT.

4. Program/Project Office establishes a SOVT Competency-Aligned Organization (CAO)

Integrated Product Team (IPT) (herein referred to as SOVT IPT) based on disapproval from Tech

Version 1.4 22 June 2011

4–3

Authority for review and approval of System SOVT. Chair and Co-chair for the IPT are the

Product PM or Project Manager and the Technical Authority representative. (reference figure 4-1, steps 5-8)

1) Description: Program/Project Office shall establish and convene SOVT IPT for review and final preparation of System SOVT

2) Inputs: Program/Project Office signed System SOVT document

3) Product (Output): Final System SOVT

4) Responsible: Program/Project Office

I. Approval/Signature Authority: SOVT IPT Chair and Co-chair

II. Completed: Upon Chair and Co-chair concurrence that SOVT document is final

5. Upload System SOVT to repository (reference figure 4-1, step 9)

1) Description: Approval is obtained by uploading the System SOVT to the SPIDER SOVT module workflow. SPIDER is the designated common repository for access and collaboration by individuals with authorized access

2) Inputs: Final System SOVT document

3) Product (Output): Approved System SOVT loaded in repository

4) Responsible: Program/Project Office

I. Approval/Signature Authority: Not applicable.

II. Completed: Approved SOVT is loaded in designated repository and accessible by individuals with authorized access.

4.1.2. Development of Platform SOVT Document Process Steps

1. Develop Platform SOVT (reference figure 4-1, steps 10-11)

1) Description: A Platform SOVT shall be developed from the System SOVT using

Chapter 7 in SPEG as guideline. Use SOVT checklist in SPEG to verify completeness.

2) Inputs: Approved System SOVT and current version of SPEG

3) Product (Output): Final Platform SOVT

4) Responsible: Project Office

I. SPEG Compliance Certification: Certified by Developer

II. Approval/Signature Authority: Program/Project Manager

III. Completed: Final Platform SOVT completed IAW Chapter 7 of SPEG.

2. Upload Platform SOVT to repository (reference figure 4-1, step 11)

1) Description: The final Platform SOVT document shall be uploaded to the SPIDER

SOVT workflow for approval. Approved SOVTs are on permanent file in the SPIDER repository for access and collaboration by individuals with authorized access.

2) Inputs: Final Platform SOVT document

3) Product (Output): Approved Platform SOVT document loaded in repository

4) Responsible: Program Manager

I. Approval/Signature Authority: Not applicable.

Version 1.4 22 June 2011

4–4

II. Completed: Approved SOVT is loaded in repository and accessible by individuals with authorized access.

4.1.3. SOVT Execution and Closeout Process Steps

1. Obtain Platform SOVT (reference figure 4-1, step 12)

1) Description: Installation activity shall obtain Platform SOVT from repository.

2) Inputs: Platform SOVT

3) Product (Output): Platform SOVT

4) Responsible: Installation Activity

II. Completed: Platform SOVT obtained.

2. Coordinate and schedule SOVT with platform (reference figure 4-1, step 13)

1) Description: Installation activity shall coordinate and schedule SOVT IAW Platform

SOVT requirement or constraints.

2) Inputs: SOVT pre-brief.

3) Product (Output): Agreed to SOVT schedule

4) Responsible: Installation Activity

I. Approval/Signature Authority: Not applicable.

II. Completed: Mutually agreeable schedule and understood SOVT responsibilities between Installation Activity and platform.

3. Conduct Pre-SOVT tests and inspections (reference figure 4-1, step 14)

1) Description: Conduct Pre-SOVT tests IAW approved Platform SOVT

2) Inputs: Approved Platform SOVT and agreed upon schedule

3) Product (Output): Pre-SOVT test and inspection results

4) Responsible: Installation Team or SOVT Team

II. Completed: When Pre-SOVT checks and inspections completed

4. Conduct test IAW Platform SOVT (reference figure 4-1, step 15)

1) Description: Conduct Platform SOVT using the approved SOVT according to the agreed to schedule and requirements with the platform.

2) Inputs: Approved Platform SOVT and platform schedule

3) Product (Output): Completed SOVT

4) Responsible: SOVT Team / Witnessed by platform

II. Completed: Platform SOVT completed.

5. Conduct SOVT sign off with witnesses and upload signed SOVT (reference figure 4-1, step 16)

Version 1.4 22 June 2011

4–5

1) Description: Obtain signatures from authorized platform‟s representative and SOVT lead.

Upload signed SOVT into repository

2) Inputs: Completed SOVT

3) Product (Output): Signed SOVT

4) Responsible: SOVT Team and platform

I. Approval/Signature Authority: SOVT Manager and Platform Witness

II. Completed: SOVT sign-off sheet and SOVT uploaded in repository.

6. Determine and assess any SOVT test discrepancies (reference figure 4-1, step 17)

1) Description: Review completed SOVT test data and determine what, if any, discrepancies exist

2) Inputs: SOVT test results

3) Product (Output): Discrepancies input into discrepancy tracker.

4) Responsible: Installation Management Office (IMO)

II. Completed: When discrepancies are input into SPIDER discrepancy tracker

7. Add discrepancy list to draft completion message / Installation Completion Report (ICR) /

Alteration Completion Report (ACR) (reference figure 4-1, step 18)

1) Description: Add all agreed to discrepancies to draft completion message / ACR

2) Inputs: Conditional signed off SOVT

3) Product (Output): Draft completion message / ACR with discrepancies listed

4) Responsible: Alteration Installation Team (AIT) Manager or Project Engineer (PE)

I. Approval/Signature Authority: Not applicable.

II. Completed: Mutually agreed to draft message / ACR with discrepancies reviewed by platform and SOVT Lead

8. Track discrepancies and resolve (reference figure 4-1, step 19)

1) Description: All discrepancies in completion message / ACR shall be addressed, tracked and resolved to mutually agreed SOVT Lead and platform satisfaction

2) Inputs: List of discrepancies from completion message / ACR

3) Product (Output): discrepancy list tracker with all completed actions annotated

4) Responsible: AIT Manager or PE

II. Completed: When all discrepancies closed in discrepancy tracker.

4.2. Roles and Responsibilities for SOVT Development Phase

The following roles and responsibilities apply to the SOVT development phase.

4.2.1. Program or Project Office

For centrally managed systems, the cognizant program office is responsible for the development of both the System level and Platform SOVT documents. For Other Command Funded projects, the cognizant project office has the same requirement/responsibility for development of the System and

Version 1.4 22 June 2011

4–6

Platform SOVT documents. The program or project office may elect to develop the System SOVT utilizing in-house support, contractor support, In-Service Engineering Agent (ISEA) support, or any combination thereof. The program or project office shall involve those responsible for the systems engineering with System SOVT development.

If the Tech Authority review results in a disapproval of the System SOVT, the program or project office has the responsibility to establish a SOVT IPT to review, resolve, and approve the System

SOVT, upload the approved document into the data repository, and develop the Platform SOVT.

4.2.2. SOVT IPT

The SOVT IPT is comprised of representatives from the Program or Project office, System Technical

Authority, System Subject Matter Experts (SMEs), and the Technical Area Expert (TAE) for SPEG

Compliance/System SOVT approval. The Program or Project Manager and the TAE for SPEG shall serve as Chair and Co-chair of the team. The IPT shall review System SOVTs, provide review comments, and reach consensus to approve and certify that the SOVT document is technically suitable and in compliance with the SPEG.

4.3. Roles and Responsibilities for SOVT Execution Phase

Roles and responsibilities for the SOVT Execution and Closeout Phase are provided below.

4.3.1. Installation Activity Installation Management Office (IMO)

In accordance with SPAWARINST 4720.1, the planning and execution of all installations shall be centralized in the established SPAWARSYSCEN Atlantic and SPAWARSYSCEN Pacific IMOs.

The IMOs shall act as a single POC and portal for all installations that are planned and executed by

SPAWAR employees or SPAWAR contractors. For Afloat installations, a Ship Superintendent

(SHIPSUP) is assigned to coordinate all installation efforts on board the ship. The Regional Shore

Installation Manager (RSIM) is responsible for coordinating all shore installations within their specific region.

The IMO shall ensure that the executed and signed Platform SOVT is uploaded to SPIDER prior to closure of each installation job.

4.3.2. AIT Manager/OSIC/NTR or Shore PE/OSGR

Upon receipt of tasking the IMO shall designate an Alteration Installation Team (AIT) manager

(a.k.a. On-Site Installation Coordinator (OSIC), Navy Technical Representative (NTR)) for ship and submarine installations or a PE (a.k.a. On-Site Government Representative (OSGR)) for shore installations. The AIT manager or PE is responsible for coordinating the entire installation effort. The

AIT manager shall interface with the IMO, SHIPSUP, SOVT manager, Regional Maintenance and

Modernization Coordination Office (RMMCO), ship‟s force, etc. Part of the AIT manager‟s responsibilities is to provide an installation in-brief to the ship. The in-brief shall include general

SOVT requirements in accordance with NAVSEA Tech Spec 9090-310D. Likewise, PEs shall interface with the IMO, RSIM, installation team, the SOVT Manager, station forces, etc. In-briefs shall include general SOVT requirements and schedule in accordance with the SPAWAR Shore

Installation Process Handbook (SIPH).

Version 1.4 22 June 2011

4–7

4.3.3. Installation Team

The installation team is responsible for conducting the installation. As part of the installation effort, the installation team is responsible for the quality, workmanship, and accuracy of the installation.

The installation team conducts “Cold Checks” to ensure all cable connections and grounds are complete using the correct cable, are in accordance with the design, and to verify continuity of wiring through all cables and connectors throughout the system installation.

The installation team inspects and tests applicable physical interfaces, stress relief, and cable management systems. The installation team also verifies the correct voltage is present to safely turn on the equipment in order to begin the SOVT. These checks should be accomplished by the installation team prior to start of SOVT.

4.3.4. SOVT Manager/SOVT Team

The SOVT Manager is the government employee responsible for coordinating and executing the

SOVT effort. Depending upon the complexity of the installation, the SOVT Manager may assemble a

SOVT team of ISEA representatives or SMEs to conduct the SOVT. The SOVT Manager shall obtain a copy of the Platform SOVT document from either SPIDER or the cognizant program office and provide it to the SOVT team. The SOVT Manager shall ensure that appropriate clearance information is sent to the ship or shore site.

4.4. Preparing for SOVT Execution

Close coordination shall be maintained between the AIT manager, SOVT Manager and SHIPSUP

(for ship and submarine installations) and between the Project Engineer (PE), SOVT Manager, and

RSIM (for shore installations) to facilitate an orderly transition from the installation phase to the

SOVT phase. The SOVT manager and SHIPSUP or PE shall interface with the ship or shore station forces to determine best time frame to conduct the SOVT.