IWS5B_Surface_Ship_USW_Combat_Systems_Configuration_Management_Plan.pdf

June 2012 IWS5B-12-CMP-009R4

SURFACE SHIP

UNDERSEA WARFARE COMBAT SYSTEMS

CONFIGURATION MANAGEMENT PLAN

Naval Sea Systems Command Program Executive Office

Integrated Warfare Systems, IWS 5 1333 Isaac Hull Ave SE, Stop 7019

Washington Navy Yard, DC 20376-7019 i

IWS 5B

SURFACE SHIP

UNDERSEA WARFARE COMBAT SYSTEMS

CONFIGURATION MANAGEMENT PLAN

SIGNATURE PAGE

Submitted by: Date Recommended by: Date

Helen Rice, Product Support Manager, IWS 5PSM

Colleen Cannon, Deputy Program Manager, IWS 5B DEP

Approved by:

Commander Todd Boehm, Director for Surface Ship Undersea Warfare Combat Systems, IWS 5B

Date ii

RECORD OF CHANGES

CHANGE DATE TITLE AND/OR BRIEF DESCRIPTION

R4 Revision 4 reflects the following changes:

05/30/2012 Updated D/W Process and workflow Update Program Office Titles Updated references list with current revisions 10/14/2009 Modified Section 1.4.1 for accuracy Modified Section 1.4.2 to bulletize list of systems for improved legibility Modified responsibilities of all billets under Section 2.1 for accuracy and renumbered subordinate paragraphs to reflect appropriate relationships Modified Section 2.2 for accuracy and to reflect distinct organizational responsibilities Modified Section 2.3 for accuracy Created Section 2.4 to reflect distinct SSA responsibilities Modified Section 2.5 for accuracy and to remove TDA responsibilities Modified Section 2.6 for accuracy Modified Section 2.7 for accuracy and to reflect current NAVSEA naming convention, i.e. NSWC/Dam Neck Modified Section 2.8 for accuracy and to reflect distinct organizational responsibilities Created Section 2.9 to compile CM checklists Rewrote Section 3.2 for accuracy Modified Section 4.6 for applicability to all contract deliverables Created and moved all illustrations from body into Appendix C to compile

CM process flowcharts Inserted references to figures in Appendix C into body of plan where appropriate Modified Appendix D for accuracy and completeness Replaced all references to Configuration Control Board (CCB) with Local

Configuration Control Board (LCCB) Replaced all references to Configuration Manager & CM Manager with

Supportability Manager Updated Reference Documents list Added A(V)15 SCI part numbers Add AN/UYQ-100 ILA Comments Modified functions of field commands due to various reorganizations Incorporated changes to reflect PEO IWS 5B 12/12/2005 Revision 4 reflects the following changes:

Modified D/W signature requirements 9/21/2005 Added NUWCDIVKPT references to CM Plan Added paragraph 6.6.2 detailing NUWCDIVKPT CSA responsibilities Added paragraph 1.14 to Appendix A detailing NUWCDIVKPT CM roles and responsibilities 6/30/2005 Replaced all references to PEO B with PEO Replaced all references to PDM with iPDM Added advanced development paragraph 1.4.4 iii

CHANGE DATE TITLE AND/OR BRIEF DESCRIPTION

Replaced all references to Project Team Leaders (PTL) with Project Officer

(PO)

Removed figure 3-1 CM support teams as it is no longer relevant Updated paragraph 6.6.1 NSWC Cranes responsibilities Added SHIPMAIN statement paragraph 5.1 Removed Figure D-2 due to redundancy Updated figure D-4 Deviation and Waiver process flow chart Minor editorial changes to paragraphs in section 1.0 Added reference to PEO CONOPS in section 2.1 R3 3/12/2004 Revision 3 reflects the following changes:

Changed Sections 2.2.b and Attachment G to reflect Unique Item Identifier

(UID) marking requirements 9/30/2003 Changed Sections 1.3, 1.4.1, 1.4.2, 1.4.3, 2.1, 2.1.3, 2.3, 3.3, 4.1, 4.2, 4.3.1, 4.4, 4.4.2, 4.4.3, 4.5.1, 5.1, 5.2, 5.2.1, 5.3, 5.4, 5.6, and 6.6 to reflect the functional part number (FPN) approach to identify and track parts.

Minor editorial changes made to Appendix A Minor editorial changes made to Appendix C Added USW Maintenance Bulletins in Appendix E Streamlined ECP process (reduced number of types of ECPs, PTL driven) and classified ECP process introduced in Appendix D Incorporated FPN changes to the affected Appendices F, G, H, and J Added new Appendix K to add the Configuration Planning Checklist for

New Systems (Functional Part Number Approach) Change of document numbering from PMS411-94-Q89-CMP-009 to PEO

B-94-Q89-CMP-009R3

Changed all other references from PMS411 to PEO B due to Program

Office reorganization Changed all references from PDM to iPDM R2 Revision 2 reflects the following changes:

Jan-01 Editorial changes Oct-00 Revision 2 reflects the following changes:

Added section 1.4.3, New Development Systems, to address the emerging procurement policies based on performance specifications and Prime Vendor Support (PVS).

Reverting back to title of PEO B-94-Q89-CMP-009R2 with appendices and deletion of Volume I and Volume II as titles. This revision incorporates CMPWG inputs from July 27, 2000 meeting and incorporation of PEO B PTL inputs.

The CM Plan contains summarized information pertinent to the overall management of CM processes and CM configuration items and products.

This information will help Managers and Project Team Leaders ensure

CM principles are considered during the development, production, and in-service support phases of PEO B Sonar Systems, Functional Elements and associated products.

iv

CHANGE DATE TITLE AND/OR BRIEF DESCRIPTION

The Appendices section consists of both newly developed and updated appendices from PMO411-94-Q89-CMP-009R1. These appendices contain detailed information that the project and functional element team members require for the development of the various CM documents associated with their respective equipment/products.

Introduction of the Product Data Management System (PDMS), and the requirement to use PDMS.

Updated definitions of the Class I Series ECPs and Class II ECPs.

Introduction of the Class I 3000, 8,000 and 10,000 series ECP.

An expansion of the PEO B Configuration Management process to include all PEO B projects and functional elements.

Change of document numbering from PMO411-94-Q89-CMP-009 to PEO

B-94-Q89-CMP-009R2

R1 Aug-95 Revision 1 reflects the following changes:

Removal of references to MIL-STD-480, MIL-STD-965, MIL-STD-973, and MIL-STD-1521.

Removal of most references to the AN/SRQ-4. There is a stand-alone

AN/SRQ-4 CM Plan.

Introduction of CM guidance for AN/SQQ-89(V) Development Programs.

Elimination of the Change Evaluation Committee (CEC). Its functions have been included with those assigned to the Configuration Control Board

(CCB).

The introduction of the concept of CM for Commercial-off-The-Shelf items.

Engineering Documentation and Magnetic Media Requirements.

Product Marking Requirements A Process for Installation Control Drawing ECPs A Value ECP Section.

An Alternate Design ECP Section.

Contractor CM Data Base and CSA Responsibilities New Appendices:

Appendix A – PEO Class I Hardware & Firmware ECP Guidelines Appendix B – PEO Class I Software & Documentation ECP Guidelines.

Appendix J – AN/SQQ—89(V) CM Forms.

Appendix L – COTS Product Descriptions, G&PP-006R1.

Appendix M – As-Built Listing.

Appendix N – Combined CIM/CSAR.

Removal of MIL-STD-480B and MIL-STD-973 ECP Guidance

Appendices.

v

TABLE OF CONTENTS

Section Page

1.0 INTRODUCTION

1.1 Purpose

1.2 Scope

1.3 Process Improvement

1.4 Description of Systems/Subsystems/Functional Segments Supported by IWS 5B

1.4.1 AN/SQQ-89(V)

1.4.2 Non-AN/SQQ-89(V)

1.4.3 New Development Systems

2.0 CONFIGURATION MANAGEMENT RESPONSIBILITIES

2.1 IWS

2.1 PEO IWS 5B Program Management Office

2.1.1 Major Program Manager (MPM) for Surface Ship USW Combat Systems

2.1.2 IWS 5 System Engineer

2.1.3 PEO IWS 5 Configuration Management Manager

2.1.4 PEO IWS 5B Director of In-Service Support (ISS)

2.1.5 PEO IWS 5B Logistics Manager

2.1.6 IWS 5 Financial / Acquisition Coordinator

2.1.7 IWS 5 Director of Test and Evaluation

2.1.8 IWS 5B Director of Installations

2.2 Technical Design Agent (TDA)

2.3 In-Service Engineering Agent (ISEA)

2.4 System Integration Agent (SIA) & Technical Design Agent (TDA)

2.5 Naval Surface Warfare Center, Crane Division

2.6 Prime ILS Support Contractor

2.7 Naval Undersea Warfare Center, Division Keyport (NUWCDIVKPT)

2.8 Production Contractor

2.9 General CM Tasks

3.0 CONFIGURATION MANAGEMENT REQUIREMENTS

3.1 Configuration Management Manager Responsibility

3.2 Integrated Product Data Management System (iPDM)

3.3 Configuration Identification

3.3.1 Configuration Item

3.3.2 Configuration Item Identification Numbers

3.3.3 Assignment of Unit Numbers

3.3.4 Marking Requirements

3.3.5 Request for Nomenclature

3.3.5.1 Nomenclature rules

3.3.5.1.1 Variable Assignment

3.3.5.1.2 Modification Letter Assignment

3.3.5.1.3 Nomenclature Updates

3.3.6 System Configuration Summary

3.4 Baselines

3.4.1 Functional Baselines and Documents

3.4.2 Allocated Baselines and Documents

3.4.3 Product Baselines and Documents

3.5 Installation Control Drawings (ICDs)

vi

3.5.1 ICD Ordering Data

3.5.2 ICD Revision Data

3.6 Training Configuration

3.6.1 Training Configuration Management

3.6.2 Shore Facility (Laboratory) Configurations

3.6.3 ILS Development and Production Site (IDAPS) Configurations

3.7 Contractor Configuration Management Plan

3.8 CM and COTS

3.8.1 COTS Cross Reference Database (CCRDB)

3.8.2 Design Control Document (DCD)

3.8.3 Functional Part Number (FPN)

4.0 CONFIGURATION ITEM CHANGE CONTROL PROCESS

4.1 Surface Ship / Aircraft Carrier Modernization Program

4.2 Change Control Documentation (CCD) Process

4.3 Trouble Report (TR)

4.3.1 TR Development

4.3.2 TR Submission

4.3.3 TR Disposition

4.4 Engineering Change Proposal (ECP)

4.4.1 Class I Hardware, Firmware and Documentation ECPs

4.4.1.1 Class I ECP Development

4.4.1.2 Class I ECP Submission

4.4.1.3 Class I ECP Review

4.4.1.4 Class I System ECP Approval

4.4.2 Class I Software ECPs

4.4.2.1 Class I Software ECP Development/Submission

4.4.3 Class II Documentation/ Firmware ECPs

4.4.4 Class II Software ECPs

4.5 Engineering Change (EC) Development

4.6 Deviation/Waiver (D/W)

4.6.1 D/W Development

4.6.2 D/W Submission

4.6.3 D/W Review

4.6.4 D/W Approval

4.7 Technical Review Board (TRB)

4.8 Local Configuration Control Board (LCCB)

5.0 CONFIGURATION STATUS ACCOUNTING (CSA)

5.1 Purpose

5.2 Applicability

5.3 Contractor Configuration Status Accounting

5.4 As-Built Records and Listings

5.5 Configuration Status Accounting Report

5.6 Government Configuration Status Accounting

5.6.1 Naval Surface Warfare Center, Crane Division (NSWC/Crane)

5.6.2 Naval Undersea Warfare Center Division Keyport (NUWCDIVKPT)

5.6.3 Naval Undersea Warfare Center, Newport (NUWC/NPT)

6.0 TECHNICAL REVIEWS AND CONFIGURATION AUDITS

6.1 Purpose

6.2 Technical Reviews

6.3 Configuration Audits

6.3.1 Functional Configuration Audit (FCA)

6.3.2 Physical Configuration Audits (PCA)

vii

6.3.2.1 Physical Configuration Audits (Traditional)

6.3.2.2 Physical Configuration Audit (Functional)

6.3.3 Configuration Reviews

6.3.4 Audit Reports

APPENDIX A: IWS 5B Equipment Marking Requirements ................................................... A-1 A.1.0 CONFIGURATION IDENTIFICATION AND MARKING REQUIREMENTS .................. A-2 A.2.0 PRODUCT MARKING .......................................................................................................... A-2

A.2.1. Marking Method and Material .......................................................................................................... A-2 A.2.2. Marking Requirements ..................................................................................................................... A-2 A.2.3. Identification Plates .......................................................................................................................... A-4 A.2.4. COTS PRODUCT MARKING......................................................................................................... A-4 A.2.5. Marking of COTS Within Legacy Systems ...................................................................................... A-5 A.2.6. Marking of COTS Within New Systems .......................................................................................... A-5

A.3.0 FIELD CHANGE PLATES..................................................................................................... A-5

A.4.0 SOFTWARE CONFIGURATION IDENTIFICATION AND MARKING REQUIREMENTS .

................................................................................................................................................. A-6

A.4.1. General Scheme For Software Part Numbers ................................................................................... A-6 A.4.2. Currently Assigned Core CI Numbers .............................................................................................. A-8

A.4.2.1. Legacy systems ....................................................................................................................... A-8 A.4.2.2. AN/SQQ-89(V)6 TAUs .......................................................................................................... A-8 A.4.2.3. AN/SQQ-89A(V)6 Block I ..................................................................................................... A-8 A.4.2.4. Training ................................................................................................................................... A-9 A.4.2.5. AN/SQQ-89(V)15 ................................................................................................................... A-9

A.4.2.5.1. AN/SQQ-89 w/EC200 ....................................................................................................... A-9 A.4.2.5.2. AN/SQQ-89 w/EC204 ....................................................................................................... A-9

A.4.2.6. AN/SQQ-89A(V)15 ................................................................................................................ A-9 A.4.2.7. FMS ......................................................................................................................................... A-9

A.4.3. AN/SQQ-89A(V)15 Software Versioning (A.4.3) ........................................................................... A-9 A.4.4. General Items .................................................................................................................................. A-10

A.4.4.1. CM ........................................................................................................................................ A-10 A.4.4.2. Library ................................................................................................................................... A-10 A.4.4.3. AN/SQQ-89 program level ................................................................................................... A-10 A.4.4.4. Acoustic Data ........................................................................................................................ A-10 A.4.4.5. Application Software Documents.......................................................................................... A-10

APPENDIX B: Production Configuration Reports .................................................................. B-1 B.1.0 General .................................................................................................................................... B-2

B.1.1. Configuration Status Accounting Report (CSAR) ............................................................................. B-2 B.1.2. As-Built List (ABL) ........................................................................................................................... B-2

APPENDIX C: Configuration Management Processes ........................................................... C-1 C.1.0 General .................................................................................................................................... C-1

Acronyms and Definitions .......................................................................................................... D-1 viii

Table Title Page No.

Table 2-1: New Product/System CM Requirements Checklist Table 2-2: Changes to Existing Baseline CM Requirements Checklist Table A-1: Samples of Product Identifiers ................................................................................. A-8

Figure Title Page No.

Figure 6-1: Unit Level FCA/PCA Log Figure 6-2: PCA Work Sheet Figure 6-3: PCA Completion Letter Figure A-1: Mil-Spec ESD Symbols ........................................................................................ A-11 Figure A-2: Module Marking Illustration ................................................................................. A-12 Figure A-3: System ID Plate ..................................................................................................... A-13 Figure A-4: Unit ID Plate ........................................................................................................ A-14 Figure A-5: GFE Identification Plate ........................................................................................ A-15 Figure A-6: IWS 5B Warranty Plate ......................................................................................... A-16 Figure A-7: IWS 5B Transducer Identification Plate ............................................................... A-17 Figure A-8: IWS 5B Field Change Plate .................................................................................. A-18 Figure B-1: CSAR Cover Page ................................................................................................... B-4 Figure B-2: Configuration Item Report ...................................................................................... B-5 Figure B-3: Engineering Change Summary ................................................................................ B-5 Figure B-4: Document Change History ...................................................................................... B-5 Figure B-5: ABL Cover Page ..................................................................................................... B-6 Figure B-6: System Configuration Item Listing ......................................................................... B-7 Figure B-7: Alteration Incorporation Status ............................................................................... B-7 Figure C-1: Generic CM Process ................................................................................................ C-1 Figure C-2: Generic CM Process with interaction/facilitated by iPDM Workflow ................... C-2 Figure C-3: General TR to ECP Approval Progression .............................................................. C-3 Figure C-4: Engineering Change Development Process ............................................................ C-4 Figure C-5: D/W Process ............................................................................................................ C-5 ix

REFERENCE DOCUMENTS

DOCUMENT TITLE

NUMBER

DATE

PMS411 Configuration Control Board Charter PMS411 Ltr Serial PMS 411/0516 Jun 00

PMS411 Guidance & Policy Paper; PEO B-G&PP-030, Direction to Use Product Data Management System PMS411-G&PP-030 Aug 00

Military Handbook Configuration Management Guidance MIL-HDBK-61A(SE) Mar 07

Identification Marking of US Military Property MIL-STD-130N Dec 07 Fleet Modernization Program (FMP) Policy OPNAVINST 4720.2g May 95 Types and Applications of Engineering Drawings Revision of ASME Y14.24M-1989 ASME Y14.24-1999 Jan 99

Drawing Sheet Size and Format ASME Y14.1-1980 Jan 99 Mathematical Definition of Dimensioning and Tolerance Principles ASME Y14.5.1 M- 1994 Rev 99

Reference Designations for Electrical and Electronics Parts and Equipment IEEE STD 200

Supplement to Graphic Symbols for Electrical and Electronics Diagrams IEEE STD 315A

Surface Ships and Carriers Entitled Process (EP) For Modernization (SSCEPM) Operations and Management Manual (One Book)

SL720-AA-MAN-030 Apr 09

Configuration Management (CM) Policy and Guidance NAVSEAINST 4130.12B Jul 04

1.0 INTRODUCTION

Configuration Management (CM) is a discipline which applies technical and administrative direction and surveillance over the life cycle of items to identify and document the functional and physical characteristics of configuration items; control changes to configuration items and their related documentation; record and report information needed to manage configuration items effectively, including the status of proposed changes and implementation status of approved changes; and audit configuration items to verify conformance to specification, drawings, interface control documents, and other contract requirements. As applied to digital data files, CM is the application of selected configuration identification and configuration status accounting principles to uniquely identify the digital data files, including versions of the files and their status (e.g., working, released, submitted, approved) and record and report information needed to manage the data files effectively, including the status of updated versions of files.

1.1 Purpose

The purpose of the PEO, IWS 5B USW Combat System Configuration Management Plan is to establish uniform requirements for the application of CM principles for items that are developed, acquired, and supported by PEO IWS 5B. This PEO IWS 5B CM Plan describes the processes for documenting and managing the configuration of those items. Compliance with this plan allows the Program Manager more positive control of life cycle costs, contract requirements, schedules, operational performance readiness and Integrated Logistic Support (ILS).

1.2 Scope

This document establishes the total life cycle plan for implementing CM requirements for the system, subsystems, Computer Software Configuration Items (CSCIs) and Hardware Configuration Items (HWCIs) that comprise the Surface Ship USW Combat Systems and functional segments managed by IWS 5B. This document supports the adherence to CM principles by the Program Office and applies to all Government and contractor activities associated with the programs. This CM Plan is to be considered a living document and will be updated as necessary to support evolving program requirements such as performance specification procurement policies and supportability in the Commercial Off-The-Shelf (COTS) environment.

1.3 Process Improvement

The many processes detailed in the appendices are the results of task knowledge, past experiences, and current agreements of the IWS 5B CM community. These processes and procedures are meant to provide guidance, and will remain dynamic with regard to process improvements.

Refer to Figure C-1 and Figure C-2 in Appendix C for illustrations of generic CM processes.

1.4 Description of Systems/Subsystems/Functional Segments Supported by IWS 5B

1.4.1 AN/SQQ-89(V)

The AN/SQQ-89(V) is an integrated surface ship USW combat system that contains a variety of underwater sensors and weapon control subsystems, with advanced acoustic data processing and display capabilities on-board US Navy Frigates, Destroyers and Cruisers. The AN/SQQ-90 Surface Ship Anti-Submarine Warfare (ASW) Combat System is an advance follow on system and will be installed on board DDG 1000. Both systems support naval USW missions through the search, detection, tracking, localization, classification, and correlation of surface and subsurface targets. In the discussion that follows, components are arranged roughly into two categories; 1) hardware/software that are internal to the ship, and 2) hardware that have a major external interface with the ocean or air environments. This division was made because the potential environmental impact assessment(s) tend to be related to these groupings.

The AN/SQQ-89(V) system for a given platform, destroyer, guided missile destroyer, guided missile cruiser or guided missile frigate, is a combination of the designated sub-systems depicted in Figure 2-1. Refer to the IWS 5 Program Plan for an AN/SQQ-89(V) history and a more complete system variant overview. These configurations are maintained in accordance with the AN/SQQ-89(V) System Configuration Summary by Variant document. A Variant Summary listing is also maintained on the Internet at the Integrated Product Data Management (iPDM) website <<https://ipdm.navy.mil>>. The decommissioning of ships and the installation of new or updated variants make the configuration summary dynamic.

The subsystems that comprise the AN/SQQ-89(V) suite include: Internal Hardware/Software Systems;

• MK 116 -- Fire Control System, Undersea Control Functional System (UCFS)

• AN/UYQ-25-- Sonar In-situ Mode Assessment System (SIMAS), Sensor Performance

Prediction Functional Segment (SPPFS)

• On Board Trainer (OBT), Target Control Workstation (TCW)

• AN/SQQ-28(V) – Light Airborne Multi-Purpose System (LAMPS) Sonobuoy Functional

• AN/SQS-53 - Hull Array Sonar Processing Series (53B, 53C, 53D, Hull Sonar Functional

• AN/SQS-56 Hull Array Sonar Processing System, MK 309 Weapons Alternate Processor

• AN/SQR-19 - Towed Array Sonar Processing System

• Multi Function Towed Array (MFTA), Towed Array Sonar Processing System

• Scaled Improved Performance Sonar (SIPS)

• Surface Vessel Torpedo Tube (SVTT)

External Interface Hardware

• AN/SQS-53 & AN/SQS-56 - Hull Mounted Sonar’s

• AN/SQR-19 & MFTA, Towed Arrays

Supported USW Systems

• Littoral Combat Ship (LCS) ASW System Mission Package (ASWMP)

• AN/SQQ-90 Surface Ship ASW Combat System

1.4.2 Non-AN/SQQ-89(V)

Systems that are managed by PEO IWS 5B, but are not considered part of the AN/SQQ-89(V) include: AN/ARR-75 Sonobuoy Receiver, AN/BQH-7A Bathythermograph Set, AN/SKR-4A/B LAMPS MK 1 Data Receiver, AN/SSQ-61/61A Bathythermograph Set, MK 309 Mod 0/2 Control Panel (CP), MK 429 Mod 1 Air Charging Panel (ACP), MK 432 Torpedo Pre-Setter Test Set, PP-7100 Sonar Power Supply, PP-7777 Sonar Power Supply, Sonar Rubber Domes, Sonar Dome Pressurization Systems, AN/SQQ-121 (Computer Aided Dead Reckoning Tracer (CADRT)), AN/SRQ-4, AN/WQC-2/6, AN/UQN-1/4, Littoral Combat Ship (LCS) ASW Mission Package. These Non-AN/SQQ-89(V) programs are required to utilize the CM procedures contained in this document; however, some modifications may be adapted to meet specific program requirements via waiver approval by the IWS 5B Program Manager.

1.4.3 New Development Systems

Project Officers (PO) are responsible for ensuring that all systems are developed, produced, operated and maintained. In order to ensure a smooth transition from development to production, they are responsible for tracking and maintaining the configuration of their projects through the development phases via adherence to IWS 5B CM policies and procedures. This becomes more complex as the Navy moves towards more COTS insertion and performance specifications (Functional Part Number Approach) versus Level III drawing requirements. The emerging new systems that are comprised of Government Furnished Equipment/Government Furnished Information (GFE/GFI) elements, as well as performance based elements, may require a combination of policies and procedures that are identified in this plan. Any changes made to GFE/GFI during development must be documented and approved in accordance with this plan.

Use of internal contractor CM procedures for managing and approving such changes is not acceptable without a corresponding IWS 5B Change Control Document. Internal contractor CM procedures will be evaluated for compliance to IWS 5B CM requirements. Contractor Prime Vendor Support (PVS) requirements will also be evaluated for compliance to IWS 5B requirements. This plan will be revised to incorporate any changes as they evolve and become part of applicable contracts.

2.0 CONFIGURATION MANAGEMENT RESPONSIBILITIES

2.1 PEO IWS 5B Program Management Office

IWS 5B CM is a program management responsibility which is implemented by the MPM for Surface Ship USW Combat Systems, PEO IWS 5. The number of agencies and personnel involved within IWS 5B’s numerous and diverse projects present a complex management challenge. IWS 5B manages these challenges by establishing specific and thorough processes as well as tailoring unique groups of personnel to staff the processes. IWS 5B has established several layers of CM qualified personnel to address CM concerns and has issued charters to detail their involvement.

POs are required to integrate CM, Logistics and the System Integration Agent (SIA) in their review and approval processes for development of new systems and changes to existing systems as detailed within MIL-STD-2549. POs have the responsibility to ensure the principles of CM are fully integrated into the normal business routine of the Project. It is the responsibility of the PO to determine the total impact of all proposed changes to their cognizant equipment. This is done via reviews performed by Functional Area Experts, who must be consulted to report impacts, including costs. See Table 2-1 for CM tasks that must be completed in the development of a new product or system, and Table 2-2 for CM tasks that must be completed when a new piece of equipment or subsystem is added or changed to an existing baseline. These tables identify the CM tasks that must be completed in the development of a new product or system. It is designed to assist IWS 5B Project Officers (POs) to ensure that all CM requirements have been properly addressed in the development of the product or system. This will ensure that proper configuration support is in place for the equipment's delivery, and eventual lifecycle support.

IWS 5B managers of Non-AN/SQQ-89(V) functional components or elements, supported by IWS 5B, are required to follow the processes described and or implemented by this CM Plan.

This will provide consistency in how change control documents appear and are processed. Use of the Integrated Product Data Management System (iPDM) is required by all managers of Non- AN/SQQ-89(V) functional elements and their respective supporting activities.

CM personnel support all IWS 5B POs and functional element teams in accordance with this plan and the Technical Review Board (TRB) Charter, to achieve and maintain configuration control for systems and elements in development or in life cycle support.

2.1.1 Major Program Manager (MPM) for Surface Ship USW Combat Systems PEO IWS 5 MPM is responsible for the acquisition, configuration management, integration and Integrated Logistics Support (ILS) of Surface Ship USW Combat Systems. Configuration Management is a program management responsibility duly implemented by the Surface Ship Undersea Warfare (USW) Combat Systems MPM, PEO IWS 5. PEO IWS 5 establishes and controls the allocated, functional, and product baselines. PEO IWS 5 is responsible for life cycle support of AN/SQQ-89(V) and Non-AN/SQQ-89(V) USW Combat Systems, and for the scheduling, execution, and support of approved system changes. All changes to configuration items are approved for implementation by the PEO IWS 5B Local Configuration Control Board (LCCB). Individual responsibilities of major participants are described below.

2.1.2 IWS 5 System Engineer

The System Engineer’s responsibilities include:

a. Reviewing all PEO IWS 5 ECPs and providing an evaluation of their impact to the design of PEO IWS 5 systems.

b. Providing technical inputs for the resolution of combat system level issues.

c. Maintaining interface documentation between the AN/SQQ-89(V), the Surface Ship USW Combat System and Non-AN/SQQ-89(V) systems as necessary.

d. Resolving USW Combat System interface issues between subsystems.

e. Providing systems engineering technical concurrence to the Technical Review Board(s) (TRBs) and CCB(s).

f. Serving as a member of the CCB.

2.1.3 PEO IWS 5 Configuration Management Manager

PEO IWS 5 Configuration Management Manager is responsible for establishing and maintaining configuration control over the USW Combat System baselines. The Configuration Management Manager's responsibilities include:

a. Ensuring that PEO IWS 5 CM policies and processes conform to current project/program requirements, while providing a method to ensure effective configuration management.

b. Developing and maintaining the IWS 5B CM Plan.

c. Establishing and maintaining a liaison with Ship Program Managers (SPM) and other Government agencies e.g., NAVSEA, Regional Maintenance Centers (Mid -Atlantic and South West) to ensure a coordinated approach and resolution of configuration management issues for all PEO IWS 5 systems and subsystems.

d. Ensuring the Project Technical Review Board (TRB) has been completed, ensuring technical accuracy and administering the LCCB.

e. Implementing an Integrated Project Team (IPT) approach to “Change Management” whereby all system life cycle disciplines are addressed when a change is proposed.

f. Ensuring that a PEO IWS 5 controlled, detailed, automated process for Configuration Status Accounting (CSA) is maintained for PEO IWS 5 Software, Firmware and Hardware Configuration Items (CIs).

g. Ensuring that product baselines and Configuration Status Accounting Reports (CSAR) are updated and maintained for the USW Combat Systems in iPDM.

h. Evaluating Configuration Control Documents (CCDs) to ensure adequate information is provided for thorough understanding of overall system impact (functionality, schedule and cost), and compliance with PEO IWS 5 development guidelines.

i. Distributing, reviewing and processing proposed IWS 5B Engineering Change Proposals (ECP) through the appropriate PO.

j. Identifying and tracking programmatic and technical conflicts/issues to the Program Manager. Issues are resolved through the ECP development process utilizing iPDM.

k. Providing a functional CM Point of Contact for PEO IWS 5 Project Teams.

l. Ensuring final approval authority for changes to all PEO IWS 5 CIs is documented by the appropriate PEO IWS 5 PO. Contracts will write and issue approval letters for Waivers/Deviations and the PEO IWS 5 CM manager writes and submits approval letters for all other CCD’s to PEO IWS 5 for approval.

m. Coordinating with the Logistics Manager to ensure that correct part numbers are assigned for hardware/software/firmware.

n. CM verifies that the Software Version Description Document (SVDD) adequately defines the software release.

o. Serving as a member of CCB.

2.1.4 PEO IWS 5B Director of In-Service Support (ISS)

IWS 5B Director of In-Service Support is responsible for the Fleet support of all USW Combat Systems configurations, except AN/SQQ-89A(V)15. The ISS Director's responsibilities include:

a. Reviewing all ECPs to ensure ISS issues and impacts are adequately addressed.

b. Initiating the ECP process to correct deficiencies related to ISS hardware or software.

c. Serving as a member of the LCCB.

2.1.5 PEO IWS 5B Logistics Manager

IWS 5B Logistics Manager is responsible for establishing and maintaining Integrated Logistics Support (ILS) for all USW Combat Systems configurations. The Logistics Manager’s responsibilities include:

a. Reviewing all IWS 5B ECPs to ensure ILS issues, costs and impacts are adequately identified.

b. Implementing ILS for each configuration and revising that support as approved changes are implemented.

c. Ensuring training programs are established to support PEO IWS 5B USW Combat Systems.

d. Ensuring that hardware/software/firmware upgrades performed by the Navy field activities utilize approved configuration control procedures.

e. Coordinating with the Configuration Management Manager to ensure that correct part numbers are assigned for hardware/software/firmware.

f. Coordinating the development and proof-in of ECO’s.

g. Review and reconciliation of fleet feedback reports in regard to delivered ILS products.

h. Serving as a member of the LCCB.

i. Provide guidance and information sharing for the PEO IWS 5 Technical and Logistics community.

2.1.6 IWS 5 Financial / Acquisition Coordinator

The IWS 5B Financial / Acquisition Coordinator has the following responsibilities:

a. Providing financial oversight to the IWS 5B POs.

b. Ensuring all ECP funding lines are covered by written and approved Project Task Instructions (PTI) in the Financial Information Navigation System (FINS).

c. Elevating funding issues to the Major Program Manager for adjudication.

d. Serving as a member of the LCCB.

2.1.7 IWS 5 Director of Test and Evaluation

IWS 5 Director of Test and Evaluation has the following responsibilities:

a. Reviewing IWS 5B ECPs for Test and Evaluation impacts.

b. Providing technical support to CM boards.

c. Serving as a member of the LCCB.

2.1.8 IWS 5B Director of Installations

IWS 5B Director of Installations has the following responsibilities:

a. Review all ECPs to ensure that all installation issues are addressed and all associated costs have been identified for presentation to the LCCB.

b. Coordinate the installation of ECs by creating SCDs (Ship Change Documents) in compliance with the Navy Modernization Process.

c. Serving as a member of the LCCB.

2.2 Technical Design Agent (TDA)

The Technical Design Agent (TDA) has been selected from NAVSEA NUWC-Division Newport (NPT) and NSWC Dahlgren. The TDA provides the necessary insight into available mature technologies that may be applicable across multiple programs or specifically applicable to USW-systems. In-Service Engineering Agents (ISEAs) have been designated from NAVSEA NUWC-Division Newport (NPT) and Keyport (KPT), NSWC Crane and Dahlgren, and their subordinate command NSWCDD Combat Direction Systems Activity (CDSA) Dam Neck. The TDA has the following responsibilities:

a. Providing applicability status and part numbers of software baselines for incorporation into the CSA database.

b. Coordinating software problem resolution.

c. Recommending sensor set upgrade content and schedule to IWS 5B for approval.

d. Developing and reviewing IWS 5B ECPs and providing input to TRBs or appropriate

IPT.

e. Managing and coordinating IWS 5B Functional Configuration Audits (FCAs).

f. Maintaining the IWS 5B software product baseline installed in production systems.

g. Ensuring methodologies/procedures/tools/ and policies for software version control, Program Trouble Report (PTR) tracking and lower level documentation such as Software Version Description (SVD) and VDD control are documented and followed.

h. Maintaining a software generation and integration facility.

i. Accompanying the In-Service Engineering Agent (ISEA)/installation activity during the first few installations of a new system configuration, Engineering Change (EC) delivery.

j. Validating software package materials.

k. Training the ISEA team.

2.3 In-Service Engineering Agent (ISEA)

The In-Service Engineering Agents (ISEA) for in-service equipment are responsible for dealing directly with the Fleet and waterfront logistics support activities. The ISEA has the following responsibilities for IWS 5B:

a. Make recommendations for equipment changes and reviewing IWS 5B ECPs and providing input to the POs TRB.

b. Creation of Trouble Reports (TR) describing high failure items, equipment deficiencies, or fleet requests for engineering analysis.

c. Resolution of obsolescence issues through interchangeability testing.

2.4 System Integration Agent (SIA) & Technical Design Agent (TDA) NAVSEADIV/Dahlgren performs SIA duties, is the TDA and ISEA for the ASWCS MK 116 MOD 4/6/7, Undersea Warfare Control Functional Segment (UCFS), AN/SQQ-89(V)15 Undersea Warfare Control Functional Segment (UCFS), TDSS and CADRT. Dahlgren works with IWS 5A in performing the following responsibilities:

a. Developing and reviewing IWS 5B ECPs and providing input to the TRB and/or appropriate IPT.

b. UCFS, TDSS, and CADRT CM associated information (e.g., such as software applicability and part numbers) to NAVSEADIV/Newport.

c. Maintaining methodologies, procedures, tools and policies for software version control, PTR tracking and lower level documentation (e.g. SVD and VDD).

d. Maintaining a software generation facility.

e. Accompanying the installation activity during the first few installations of a new system configuration, EC delivery.

f. Developing and reviewing IWS 5B ECPs for interface impact and providing input to the TRB and/or appropriate IPT.

g. Distributing external program office Interface Change Requests (ICRs) to the IWS 5B technical community and coordinating review comments.

h. Maintaining the IWS 5B interface documentation, by developing ICRs/ECPs to update, as required.

i. Representing PEO IWS 5 at PEO IWS 1 Enterprise Configuration Control Process (ECCP) activities with emphasis on Warfare System Interface Diagram (WSID) updates and Warfare System Working Group (WSWG) participation.

2.5 Naval Surface Warfare Center, Crane Division

Naval Surface Warfare Center Crane Division (NSWC/C) is responsible for maintaining iPDM.

NSWC/C responsibilities include:

a. Developing and maintaining the iPDM website.

b. Incorporating approved Enhancement Requests into iPDM.

2.6 Prime ILS Support Contractor

The ILC is responsible for maintaining the AN/SQQ-89(V) and assigned Non-AN/SQQ-89(V) product baselines. The ILC responsibilities include:

a. Reviewing, adjudicating, and approving AN/SQQ-89(V) Alternate Process and Materials and Class II Documentation ECPs for components/materials/processes below the LRU.

b. Identifying Commercial Off-the-Shelf (COTS) information to support product baselines.

c. Developing and reviewing IWS 5B ECPs and providing input to TRBs or appropriate

IPT.

d. Performing configuration identification, change control, status accounting/audits.

e. Defining and maintaining multiple production baselines and managing the engineering data to support the baselines.

f. Reviewing and integrating new drawings generated by IWS 5B development projects into existing baselines and establishing new product baselines.

g. As the Acquisition Engineering Agent (AEA) for PEO IWS 5 production support, responsible for the development and maintenance of manufacturing drawings, and configuration management of the production baseline.

h. Conducting and coordinating PEO IWS 5 Physical Configuration Audits (PCAs).

i. Developing and maintaining the iPDM website.

2.7 Naval Undersea Warfare Center, Division Keyport (NUWCDIVKPT) NUWCDIVKPT is the TDA, Original Equipment Manufacturer (OEM), SSA, and ISEA for the AN/SQQ-34(V). As such, NUWCDIVKPT is responsible for maintaining the AN/SQQ-34A(V) product baselines as well as working with NSWC Crane to integrate configuration data into a shared data environment for all Program Office personnel availability. NUWCDIVKPT responsibilities include:

a. Developing and reviewing AN/SQQ-34(V) ECPs and providing input to TRBs or appropriate IPT to the IWS 5B LCCB.

b. Reviewing, adjudicating, and approving AN/SQQ-34(V) Alternate Process and Materials and Class II Documentation ECPs for components/materials/processes below the LRU.

c. Performing configuration identification, change control, status accounting/audits, maintenance and document distribution for the AN/SQQ-34(V).

d. Defining and maintaining multiple production baselines and managing the engineering data to support the baselines of the AN/SQQ-34(V).

e. Reviewing and integrating new drawings into existing baseline and establishing new product baselines.

f. As the TDA and ISEA, responsible for the development and maintenance of manufacturing drawings, and configuration management of the production baseline.

g. Conducting and coordinating IWS 5B Physical Configuration Audits (PCAs) on the

AN/SQQ-34(V).

h. Maintaining COTS information to support product baselines, AN/SQQ-34(V) COTS information with IWS 5B COTS Cross Reference (CCR) data.

2.8 Production Contractor

The AN/SQQ-89(V) System Contractor shall provide and maintain (CM) for the AN/SQQ-89(V) in accordance with the Contract’s Statement of Work (SOW) and the IWS 5B CM Plan. The System Contractor's responsibilities may include, but are not limited to:

a. Maintaining the applicable Allocated, Functional and Product Baselines.

b. Supporting Configuration Audits.

c. Preparing and submitting ECPs/Requests for Deviations and Waivers.

d. Preparing and maintaining documentation for hardware identification.

e. Maintaining internal contractor configuration control processes.

f. Preparing and maintaining engineering documentation.

g. Preparing, submitting, and maintaining Installation Control Drawings.

h. Preparing and submitting Engineering Change Kit components.

i. Preparing and installing identification plates and complying with product marking requirements.

j. Maintaining COTS information to support product baselines.

k. Assisting in installation of SCDs.

2.9 General CM Tasks

The following flowcharts identify the CM tasks that must be completed when a new product or system is developed and produced (Table 2-1) and when a piece of equipment or subsystem is added to or changed in an existing baseline (Table 2-2). They are designed to assist IWS 5B POs in ensuring that all CM requirements have been properly addressed such that proper configuration support is in place for an equipment's delivery and eventual lifecycle support.

Table 2-1: New Product/System CM Requirements Checklist

Requirement Description

Review IWS 5B CM Plan

Review of the IWS 5B CM Plan is necessary to ensure that the PO becomes familiar with the CM process and requirements. This will allow planning and discussions ahead of time in the event that any of the CM milestones or requirements must be modified or additional requirements are needed. If the PO wants exceptions or unique requirements (such as incremental PCAs or to set up an IPT), the PO may develop a system CM Plan that references this plan and identifies the differences. A POA&M should be established to track the major CM milestones that must occur during a systems or products development, production, and delivery.

Define Functional Baseline (FBL)

This is performed by ensuring the Functional Baseline documentation has been developed, reviewed and approved for the system/product.

The IWS 5B CM Plan, Section 4.4.1 contains additional information concerning the FBL and the documentation requirements.

Review Contractor CM Plan

This will give insight as to how a contractor plans to track the design and production of the system up to government delivery. It will give the government a level of confidence that the contractor knows what should be built for each system to be delivered to the government.

Define Allocated Baseline (ABL)

This is performed by ensuring the Allocated Baseline documentation has been developed, reviewed and approved for the system/product.

The IWS 5B CM Plan, Section 4.4.2 contains additional information concerning the ABL and the documentation requirements.

Define Configuration Items

A definition and explanation of a Configuration Item (CI) is contained in the IWS 5B CM Plan, Paragraph 4.3.1. It is necessary to define the CI(s) at the beginning of the process to ensure that a correct determination is made as to the types of configuration documentation that will be required to support the system/product. This documentation defines hardware/software CI/CSCI performance, functional and physical attributes, and internal and external interfaces.

It also establishes a basis for the logistics processes that must occur to ensure proper support of the system/product at delivery.

Configuration Items that are COTS items should be loaded and tracked in the CCR.

Submit Request for Nomenclature

When required, a Joint Electronic Type Designation Automated System (JETDAS) nomenclature must be prepared and submitted for the system/product being built. Detailed instructions regarding the requirements and procedures for nomenclature request development/submittal are included in IWS 5B CM Plan.

Develop Documentation

ECP

For AN/SQQ-89(V) systems only, a Documentation Only ECP should be written to document the system/product in the IWS 5-SPN-001 System Configuration Summary by Variant for USW System Integration (SCS). The IWS 5B CM Plan, Paragraph 4.3.6 contains additional information concerning the content and update of the SCS.

Requirement Description

Analyze COTS Requirements

Communication with the IWS 5B COTS Managers will be required to ensure that the system/product being built will not have obsolete or unsupported items prior to delivery. Adjustments may have to be made to replace obsolete items with items that will be supported for a more significant period of time. COTS items should be loaded and tracked in the CCR.

In-Process Drawing Review

Required to ensure that the drawings are being developed in a timely and satisfactory fashion. It will ensure that all items including COTS are being correctly considered and documented. Detailed instructions as to the marking of CIs are included in IWS 5B CM Plan.

Conduct Functional Configuration Audit (FCA)

A FCA should be conducted for the system in accordance with IWS 5B CM Plan.

Physical Configuration Audit (PCA)

A PCA should be conducted for the system in accordance with IWS 5B CM Plan.

Define Product Baseline (PBL)

This is performed by ensuring the Product Baseline documentation has been developed, reviewed and approved for the system/product.

This is generally performed after a successful PCA. The IWS 5B CM Plan contains additional information concerning the PBL and the documentation requirements.

CSA Database Load

Configuration data for the system/product shall be electronically provided and loaded into the IWS 5B CSA Database for lifecycle configuration tracking. Configuration data, along with the Record Identification Codes (RICs), and Equipment Identification Codes (EIC) for the equipment must be provided to the planning yard 12-18 months prior to the system being delivered to the shipyard for installation. Information concerning the PMS 411 CSA Database data maintenance and process is contained in the IWS 5B CM Plan.

Production

Reports

Configuration Status Accounting Reports (CSAR) shall be delivered in accordance with IWS 5B CM Plan. The CM plan also includes information regarding the format and the information requirements for each report. As-Built Listings (ABLs) shall be provided with each system that is delivered (DD250 signoff) to IWS 5B. Information regarding ABL delivery and report content is contained in IWS 5B CM Plan. ABLs should be reviewed for any configuration discrepancies or issues.

Transition Product Drawings

Once the contractor has finalized the Product drawings (i.e., all comments resolved from the PCA), they shall be transitioned to IWS 5B for…