DRAFT ADC MK2 Follow on SOW.docx

ADC MK2

Statement of Work for the Acoustic Device Countermeasure (ADC) MK 2

2020 March 4

Distribution Statement D – Distribution authorized to DoD and U.S. DoD contractors only; Critical Technology; May 31, 2012. Other requests for this document will be referred to Program Executive Office, Submarine (PEO-SUB) (PMS 415).

WARNING: This document contains technical data whose export is restricted by the arms Export Control Act (Title 22, U.S.C Sec. 2751, Et. Seq) or the Export Administration Act of 1979, as amended, Title 50, U.S.C., App. 2401 Et. Seq. Violations of these export laws are subject to severe criminal penalties.

Disseminate in accordance with provisions of DoD directive 5230.25.

DESTRUCTION NOTICE: FOR UNCLASSIFIED, LIMITED DOCUMENTS, DESTROY BY ANY MEANS THAT WILL PREVENT DISCLOSURE OF CONTENTS OR RECONSTRUCTION OF THE DOCUMENT.

Table of Contents

STATEMENT OF WORK

FOR THE ACOUSTIC DEVICE COUNTERMEASURES (ADC) MK2

1. Scope This Statement of Work (SOW) defines the production, testing, associated program management, data management, systems engineering, non-recurring engineering (NRE), configuration management (CM), hardware reliability and maintainability, and integrated logistic support required to support fabrication of the ADC MK 2 and ADC MK 2 training devices. Comment by Malinski, Erin K CIV USN NUWC, 02200 (USA): Are there words for the

1.1 Background

The ADC MK 2 is a three-inch diameter expendable countermeasure capable of generating/transmitting signals to counter torpedo threats. There are two variants of the ADC MK 2. One variant of is launched from surface vessels. The other variant is launched from the Internal Countermeasure Launcher (ICL) on submarines. The ADC MK 2 device itself is classified CONFIDENTIAL.

The current standard operating procedures instruct operators to turn the device on and select the appropriate settings prior to use. For surface use, the devices are stored in accordance with surface vessel ammunition storage directives. For ICL operations, the ADC MK 2 is stowed in the submarine storage lockers for 3-inch diameter devices.

The ADC MK 2 training device is an ADC MK 2 that is inert and unclassified. The ADC MK 2 training device shares the same physical dimensions and weight without the operational aspects of the ADC MK 2. without acoustic output or hover motor when compared to the ADC MK 2.

2. Applicable Documents Copies of listed Federal and Military Standards, Specifications and Handbooks are available through the Department of Defense (DOD) single stock point, Commanding Officer, U.S. Naval Publications and Forms Center (Attn: NPFC 1032), 5801 Tabor Avenue, Philadelphia, PA 19120. Copies of military specifications and standards and DoD adopted non-Government publications may be obtained in accordance with Federal Acquisition Regulation (FAR) 52.211-2 Availability of Specifications, Standards, and Data Item Descriptions Listed in the Acquisition Streamlining and Standardization Information System (ASSIST). Copies of non- Government publications not listed in ASSIST may be obtained from the respective industry association. Requests for documents not available from either source should be directed to the Contract Specialist.

The following documents are applicable to this SOW to the extent specified herein.

2.1 Department of Defense Specifications

DoD Directive 5220.22-M National Industrial Security Program

SECNAVINST 5510.36 Department of the Navy Information Security Program

DoD Regulation 5400.7-R The DoD Freedom of Information Act Program

DoD Directive 5230.24 Distribution Statements on Technical Documents

2.2 Department of Defense Standards

2.3 Other Publications

2.4 Drawings

PMS415-CMP-08-

030 Rev F Undersea Warfare Defensive Systems (PMS

415) Configuration Management Plan (CMP)

3. Requirements The Contractor shall provide all necessary facilities, resources and management required to build, fabricate, test, and deliver ADC MK 2 and ADC MK 2 training devices as specified in the Prime Item Performance Specification (PIPS) and as delineated in this SOW.

3.1 ADC Devices

3.1.1 ADC MK2 Devices

The Contractor shall test and produce ADC MK2 devices to meet the requirements of the PIPS. The Contractor shall request any changes or deviations from the PIPS and any such changes shall be submitted for approval in accordance with the PMS415 Configuration Management Plan PMS415-CMP-08-030 Attachment X.

3.1.2 ADC MK2 Training Devices

The Contractor shall produce ADC MK2 training devices to conform to all requirements of the ADC MK2 except for the acoustic output hover operation which shall be modified to meet the requirements identified in PIPS paragraph 3.2.1.4.2.2.1 only.

3.1.3 Non-Recurring Engineering (NRE)

The Contractor shall design devices to meet the requirements of the PIPS. Engineering and software development shall be conducted to develop and test new functionality of ADC MK 2 devices leading up to First Article Testing (FAT). The Contractor shall be responsible for the design of acoustic, power, depth control, and electronics design.

3.2 Program Protection

In relation to Information Assurance, the ADC MK 2 is categorized as an expendable torpedo countermeasure weapon system that is a sealed, self-contained unit containing embedded electronics to perform a specialized mission to counter torpedo threats. The ADC MK 2 fits the specific category of Non-Information Technology (IT). Being a self-contained unit, there are no external interfaces. The embedded electronics contain a micro-processor that is pre-loaded with pre-programmed instructions for the device to boot and interface properly with the internal device components in order to perform its mission. This production contract will build to the specifications detailed in the PIPS.

Concerning Program Protection, the PMS 415 Program Office has determined that the ADC MK 2 torpedo countermeasure device does not contain Critical Program Information (CPI); therefore, Anti- Tamper (AT) features are not required to be integrated into the device.

The Contractor shall establish and develop a Program Protection Implementation Program (PPIP) in accordance with Attachment 6 PPP for ADC Programs, DoD Manual 5220.22-M and SECNAVINST 5510.36, to protect all Government systems and data under this contract (CDRL XXXX). Comment by Malinski, Erin K CIV USN NUWC, 02200 (USA) [2]: No CDRL provided

3.3 Systems Engineering

The Contractor shall perform system engineering tasks to meet all the requirements of the PIPS, this SOW, and all other requirements of the contract. The Contractor shall implement a system engineering process that translates ADC MK 2 requirements into an all-encompassing open system architecture solution that includes design completion, system fabrication, and support processes and products.

The Contractor’s system engineering process shall establish a proper balance between performance, risk, life-cycle cost, and schedule. The Contractor shall ensure the compatibility, interoperability and integration of all functional and physical interfaces, and ensure that the system definition and configuration reflect the requirements for all system elements: hardware, software, facilities, human resources, and data products. Any variations requested from the PIPS or this contract shall be submitted via the Procuring Contracting Officer (PCO) to PEO-SUB PMS 415 for approval.

The Contractor shall develop and provide a System Engineering Management Plan (SEMP) (Contract Data Requirements List (CDRL A010) for Government approval. The SEMP shall provide a thorough description of the Contractor’s proposed system engineering process, with specific details addressing how the plan will meet the Government’s PIPS. The Contractor shall submit a Specification Requirement Verification Matrix (SRVM) (CDRL A019). The contractor shall conduct various reviews, as detailed in Section 3.5.2.2, Schedule Management.

When required by an approved Engineering Change Proposal (ECP) (CDRL A004), the Contractor shall provide system engineering support to include system equipment development and interface integration; system-level joint test activities; system certifications; technical reviews; Integrated Product Team (IPT) meetings and other major meeting events; and engineering support for system interface problem resolution activities.

3.3.1 Non-Developmental Items/Commercial Off-The-Shelf (NDI/COTS) The Contractor shall utilize COTS and NDI wherever feasible. The Contractor shall develop new hardware or software only when analysis indicates that requirements cannot be met with NDI/COTS or if NDI/COTS do not provide a cost-effective solution. If the Contractor proposes the use of a NDI, the supporting documentation shall be submitted to the Government for review and approval prior to implementation. The use of COTS and commercial standards does not relieve the Contractor from meeting any performance and environmental requirements stated in the PIPS. The use of NDI and COTS hardware and firmware does not relieve the Contractor from providing full design disclosure. Selection of a COTS item requires that the Government possess disclosure of functional requirements, envelope dimensions and interface criteria to enable it to competitively procure the COTS item. Use of MIL-HDBK-2036 Commercial-Off-the-Shelf is the guiding document.

3.3.1.1 NDI/COTS Licenses

The Contractor shall be responsible for the procurement of all hardware and software licenses for non-Government Furnished Equipment (GFE) NDI/COTS products delivered in this contract including both Contractor developed and third-party NDI/COTS. If the Contractor needs to obtain a license for any NDI/COTS incorporated into a deliverable under this contract, the Contractor shall notify the Government immediately and in writing. This notification shall specify whether the license(s) that need to be procured are transferable to the Government and/or any of its other Contractor(s). The use of licensed software or hardware designs, requiring fees, shall require written Government approval prior to use by the Contractor.

Approved licenses shall be transferred to the Government in accordance with the technical data clauses in Section I of the contract and shall be of the appropriate scope to allow the Government to develop, maintain, use, release, disclose and support (including updates and modifications) the deliverable throughout the life cycle of the product in accordance with (IAW) the PIPS.

3.3.2 Problem Trouble Report (PTR) System

The Contractor shall establish a single system for the identification, tracking, and resolution of all hardware, software and base documentation problems. Data on any problems encountered by the Contractor to satisfy the contract deliverables shall be included in the Contractor’s Progress, Status, and Management Report (CDRL B001).

3.3.3 Risk Assessment, Mitigation, and Management

The Contractor shall maintain a risk management process and Risk Management Plan as part of the Program Management Plan that identifies, evaluates, and mitigates program risks from a technical, cost, and schedule perspective (CDRL B014). Risk management activities shall encompass all aspects of the ADC MK 2 program including system design, system engineering, fabrication, integration, test and evaluation, support, and management.

Risks shall be evaluated as to their impact on reliability, safety, supportability, readiness, affordability, schedule and technical performance objectives.

3.3.4 Engineering Documentation and Drawings

The Contractor shall fully disclose to the Government the detailed design of all hardware, firmware, and software developed under this contract.

No Contractor proprietary designs or components shall be utilized nor shall royalties be imposed. The use of licensed software or hardware designs, requiring fees, shall require written Government approval prior to use by the Contractor. The Contractor shall deliver to the Government, with Government Purpose Rights, all licenses, source code, drawings, repair documentation, and engineering documentation in accordance with MIL-STD-31000A. The engineering drawings shall be comprised of commercial drawings and production drawings and shall be non- proprietary in nature. Existing NDI and COTS shall be provided with its existing support documentation. Contractor modified NDI/COTS shall be supported with production drawings detailing the products delivered (CDRL A005).

3.4 Test and Evaluation

The Contractor shall implement a test program and provide a Test and Evaluation Program Plan (TEPP)(CDRL A001) that (1) demonstrates compliance with all requirements of the PIPS; (2) minimizes redundant testing; and (3) minimizes use of test resources. The Government will monitor the test program and reserves the right to witness any test(s) performed on the ADC MK 2 devices. The Government also reserves the right to perform any of the inspections or tests set forth where deemed necessary to ensure that supplies and services conform to prescribed requirements. The Contractor shall submit for Government approval, any proposed alternate test sequences and methodologies to those presented in the PIPS as part of plans and procedures that meet all requirements of the PIPS.

Failure of the Contractor to correct discovered deficiencies promptly shall be cause for suspension of acceptance until corrective action has been made or until conformance of the product to prescribed criteria has been demonstrated. See FAR clause 52.246-2, Inspection of Supplies – Fixed Price for additional details regarding correction of deficiencies. Comment by Malinski, Erin K CIV USN NUWC, 02200 (USA) [2]: We talk about Fixed Price for the Supply however the MOPAS talks to CPFF

3.4.1 Production Qualification Tests (PQT)

The Contractor shall perform PQT as a key component in achieving a successful ADC MK 2 program. Subsystem and system testing shall be used to ensure all components individually meet system requirements prior to final integration.

The qualification process confirms that the system element meets the performance specifications. The purpose of product qualification is to:

· Verify the realized (implemented or integrated) system element (including interfaces) from the lowest level system element up to the total system to ensure that the realized product conforms to the performance specifications;

· Generate evidence necessary to confirm that system elements at each level of the system hierarchy meet their performance specifications;

· Verify the materials employed in system solutions can be used in a safe and environmentally compliant manner.

Production Qualification at all levels of the physical architecture should utilize a cost-effective combination of analysis, examination, demonstration, and testing, all of which can be aided by modeling and simulation.

3.4.2 Production Lot Testing (PLT)

The Contractor shall provide devices for PLT and shall facilitate the testing if requested by the Government. The Government will perform PLT as a key component in maintaining a successful ADC MK 2 program. Subsystem and system testing shall be used to ensure all components collectively meet system requirement. The Contractor may attend lot-testing activities as an observer and subject matter expert. The Contractor shall support investigations into any findings after PLT has been completed. Comment by Malinski, Erin K CIV USN NUWC, 02200 (USA) [2]: Testing costs money – so is it required or not?

The lot testing process confirms that the system element maintains the performance specification. The purpose of the production lot test is to:

· Verify each production option year lot (implemented or integrated) system element (including interfaces) from the lowest level system element up to the total system to ensure that the realized product conforms to the performance specifications;

· Generate evidence necessary to confirm that system elements at each level of the system hierarchy meet their performance specifications;

· Verify the materials employed in system solutions can be used in a safe and environmentally compliant manner.

Production lot testing at all levels of the physical architecture should utilize a cost-effective combination of analysis, examination, demonstration, and testing, all of which can be aided by modeling and simulation.

In addition, the Government reserves the right to conduct random performance testing to ensure the ADC MK 2 meets the requirements of the PIPS. This testing will be conducted on completed units taken randomly from a production lot (any lot at any time) after DD250 acceptance by the Government. The cost of this testing, whether conducted by the Government or Contractor, will be the responsibility of the Government. Costs associated with corrective action, rework, and demonstrating conformance to the requirements of the PIPS shall be the responsibility of the Contractor.

3.4.3 Environmental Qualification Tests

The Contractor shall perform environmental qualification testing in accordance with the PIPS.

3.4.4 First Article Test (FAT)

The Contractor shall develop and submit for Government approval First Article Test Plan and Procedures (CDRL A020) to conduct FAT on sixteen (16) ADC MK 2 in accordance with the PIPS. Then, using approved First Article Test Plans and Procedures, the contractor shall demonstrate device compliance with all the requirements of the PIPS. The contractor shall provide a First Article Test Report (CDRL A021) to the Government using MIL-HDBK-831 as a guide.

The Contractor shall perform testing of weight, balance and dimensions, in lieu of FAT, on sixteen (16) MK 2 training devices first article devices.

3.4.5 Factory Acceptance Test

The Contractor shall perform Factory Acceptance Testing gand provide test reports of the results in accordance with the PIPS on each device prior to delivery to the Government. The Government reserves the right to have a representative witness any such testing. Factory Acceptance Test procedures, special test equipment and test reports shall be developed and delivered to the Government for review prior to implementation (CDRL A002).

Inspections and checks made as part of the Contractor’s Statistical Process Control (SPC) system shall be incorporated into the Factory Acceptance Test procedures (CDRL A002). Further, acceptance test results shall be evaluated for modifying SPC control limits and measuring methods, as necessary.

3.4.6 Test Location

All first article and factory acceptance testing will be performed at the facility agreed to by the Contractor and the Government.

3.4.7 Test Inspection Requirements

Unless otherwise specified in the contract, the contractor shall perform all inspection and test requirements as specified in the PIPS. The Government reserves the right to perform any of the inspections or tests set forth where deemed necessary to ensure that deliverables and services conform to prescribed requirements. Failure of the Contractor to correct discovered deficiencies promptly shall be cause for suspension of acceptance until corrective action has been made or until conformance of the product to prescribed criteria has been demonstrated.

3.4.8 Production/Process Changes

After the start of first article testing and throughout the life of the contract, if the Contractor alters facilities or processes, the contractor shall demonstrate to the Government that the product continuously meets the requirements of the PIPS. An updated process description shall be submitted in writing to the Government for review and approval (CDRL A004). The Government reserves the right to request an in-person demonstration at the Contractor facility.

3.5 Program Management

The Contractor shall designate a Program Manager (PM) who shall have responsibility for all aspects of the execution of this contract and the authority to commit the Contractor to specific actions within the scope of the contract. The Contractor shall organize, coordinate, control and report the status, of all program activities including those activities assigned to subcontractors, to ensure the correct and timely delivery of all supplies and services specified in this contract. The Program Management Plan (CDRL B014), an Agenda of the Program Reviews (CDRL B002), and resultant Minutes (CDRL B003) shall be provided to the Government by the Contractor. The Contractor shall document the results of all special studies and analyses (CDRL A024).

3.5.1 Cost Reporting

3.5.1.1 Contract Work Breakdown Structure (CWBS)

The Contractor shall develop and maintain a CWBS. The CWBS shall be to the lowest level necessary to reach manageable units of functional tasks that reflect the way the work is being performed. The CWBS shall ensure the correlation of these lower levels to the specification, statement of work tasks, contract line item numbers (CLINs), contract sub line item numbers (SLINs), configuration items and data items. The CWBS shall be the key reference document for planning, controlling, and reporting progress. The initial and any changes to the CWBS and CWBS reporting (CDRL B007) shall be submitted for review and receive concurrence from the government prior to implementation.

3.5.1.2 Contracting Officer’s Representative (COR) Production Status Reviews

The Contractor shall participate in monthly COR production status review meetings with the designated Government personnel. The COR production status review meetings’ duration shall be one hour or less and may be combined with other meetings.

3.5.2 Program Planning and Tracking

The Contractor shall maintain control of program cost and schedule. The Contractor’s Progress, Status, and Management Report (CDRL B001) shall provide visibility to CWBS level 3 unless it is determined by the Government that certain risk elements require visibility to a lower level for all tasks on cost plus fixed fee CLINs. The Contractor’s Progress, Status, and Management Report (CDRL B001) shall accomplish the following:

· Relate time-phased budgets to specific tasks identified in the statement of work;

· Produce data that indicates work progress;

· Properly relate cost, schedule, and technical accomplishment; and

· Produce data that is valid, timely, and auditable.

3.5.2.1 Monthly Status Reporting

The Contractor shall monitor cost expenditures, activities undertaken, and progress towards completion of work and shall deliver Contractor’s Progress, Status and Management Report (CDRL B001).

3.5.2.2 Schedule Management

The Contractor shall develop, maintain, and deliver original and revisions of an Integrated Master Schedule (IMS) for all contract efforts, planned events, milestones and activities related to technical deliverables. The elements of the IMS shall be grouped accordingly for ease of analysis. Proposed changes to the program schedule must be approved by the Government prior to the implementation by the Contractor. The Contractor shall quantify risk in hours, days, or weeks of delay and provide optimistic, pessimistic, and the most likely duration for each IMS activity and event. The Contractor shall deliver an Integrated Program Management Report Format 6 (CDRL B017).

The IMS shall support the needs of all functional areas (i.e., system engineering, logistic support, etc.) as well as all IPTs and reviews. Contractor schedule revisions shall not affect the contract delivery dates.

The Contractor shall conduct Technical Reviews, Interim Reviews, and audits in accordance with IEEE STD 15288.2, to demonstrate hardware and software design with the PIPS. The Contractor shall conduct the following reviews:

· System Requirements Design Review

· Preliminary Design Review (PDR)

· Critical Design Review (CDR)

· Test Readiness Review (TRR)

· Functional Configuration Audit (FCA)

· Physical Configuration Audit (PCA)

3.5.3 Configuration Management Program

The Contractor shall implement and maintain a CM program throughout the duration of this contract using MIL-HDBK-61A and ISO9001 as guidance as well as the PMS 415 Configuration Management Plan (PMS 415 CMP) (CDRL A022). The Government will maintain control of the functional baseline, as documented in the PIPS, throughout the life of this contract. The Contractor shall maintain control of the product baseline until the Physical Configuration Audit (PCA) is officially completed. A Government designated representative will participate in Contractor internal configuration control meetings to assist the Contractor and ensure that product changes are consistent with the functional baseline requirements.

The Contractor shall maintain a Configuration Management program for all documentation, physical media, and physical parts representing or comprising the products to be identified in the Product Base Line (PBL). These include, but are not limited to, all specifications and engineering drawings; software code and all software development documentation; supply support data lists; and technical manuals. NDI and COTS items used in the top-level configuration items (CI) are subject to all CM program requirements in accordance with the PMS 415 CMP. The Contractor shall maintain Configuration Status Accounting and a Configuration Status Database for the Functional Base Line, Allocated Base Line, and PBL in accordance with the PMS 415 CMP.

3.5.3.1 Technical Data Package (TDP) Comment by Malinski, Erin K CIV USN NUWC, 02200 (USA) [2]: Are we providing the previous TDP as part of the solicitation.

The Contractor shall develop, deliver, update and maintain the TDP for each product baseline and production units IAW MIL-STD- 31000A (CDRL A005). The TDP shall contain all data (commercial and product drawings/models and associated lists), specifications, and information necessary and sufficient for a third party to provide life cycle support for ADC MK 2 configurations developed and qualified under this contract. The Contractor shall provide developmental design/engineering drawings and associated lists IAW ASME Y14.100 and associated contract CDRL to support both the PDR and CDR.

The TDP shall be verified by the Government at least 30 days prior to any required PCA. The Contractor shall incrementally deliver each complete TDP to the Government upon completion of the required element. For test software and firmware, updates and maintenance of the TDP shall only be required for one operating environment based on one COTS operating system. An updated TDP shall be delivered to the Government within 90 days of any associated ECP approval and any subsequent contract modifications.

3.5.3.2 Configuration Audits

The Government will identify the items to be audited, and the documentation, hardware, firmware and software shall be made available for review. The Contractor shall be required to provide input to the Government plan for those sections identified as “To Be Determined” (TBD) as part of support for the Government’s configuration audits.

The Contractor shall provide the necessary facilities, personnel, and documentation to conduct the audits. The Contractor shall prepare Configuration Audit Reports for the Functional Configuration Audit (FCA) and PCA (CDRL A006). The reports shall document the audit findings and planned corrective actions for the adjudicated discrepancies. Comment by Malinski, Erin K CIV USN NUWC, 02200 (USA) [2]: Do we have historical information about how much effort this takes?

A moratorium on changes to all audited CIs shall be imposed one week prior to each of the FCA and PCA and during any audit conduct. When the FCA and PCA are being conducted, a list of all approved and in-process changes against hardware, firmware, software, and documentation shall be presented to the audit teams as the listing of outstanding changes at the beginning of each audit.

A representative of the Contract Administrative Office (CAO) will be responsible for continuing surveillance of the Contractor’s quality assurance practices before, during, and after the audits; this, in effect, constitutes a continuous audit of the Contractor’s manufacturing operations.

3.5.3.2.1 Functional Configuration Audit (FCA)

The FCA verifies that the system is functionally in compliance with the PIPS, and shall be accomplished prior to conducting the PCA. After completing all Government-required testing, the contractor shall forward test report(s) including signed test summary data sheets (CDRL A016). Any retesting shall require resubmission of new test summary data sheets signed by a Government representative. The FCA shall be performed in accordance with the PMS 415 CMP, Attachment 5.

3.5.3.2.2 Physical Configuration Audit (PCA)

The PCA verifies that the actual hardware and software of the final configuration are physically in compliance with the Technical Data Package. The PCA shall be performed in accordance with the PMS 415 CMP. At the completion of the PCA, the product configuration is under the Government’s control.

3.5.3.3 Configuration Status Accounting (CSA)

The Contractor shall maintain a CSA database to record and track hardware, software and firmware configuration items status and configuration history. The Contractor shall record CSA data for each as-built configuration in this database when equipment is delivered and when any change is made to a configuration item. The Contractor shall maintain a CSA database and supply the as- built configuration upon delivery in electronic form (CDRL B018).

3.5.3.4 Engineering Change Proposals (ECPs)

The Contractor shall prepare and submit ECP(s) using the PMS 415 CMP as guidance regarding preparation, routing, and disposition, for all Contractor-proposed configuration changes, including changes implemented by sub-contractors. The Contractor shall include schedule and cost impact estimates and/or updates as part of the ECP (CDRL A004).

As a general rule, unsolicited major and minor ECP(s) are discouraged. The Contractor shall, upon approval of PMS 415, submit a preliminary ECP to evaluation of the desirability of expending resources to fully document changes proposed by the Contractor, including but not limited to changes to expand device capability, engineering improvements, or corrective action for performance or reliability.

The Contractor should immediately notify the Government by electronic message (e-mail preferred) when the need for an emergency or urgent priority ECP is determined. Follow-up to the electronic message should be in the form of a formal ECP submittal within 30 days. However, when this is impractical, a preliminary ECP may be used as an interim measure. Both the preliminary ECP and the final ECP resulting from a message ECP would be identified as revisions of the initial message ECP.

3.5.5 Request for Variance

The Contractor shall prepare and submit a Request for Variance (RFV) using the PMS 415 CMP as guidance regarding routing, approval or disapproval. A variance requests temporary departure from a specific requirement of an approved baseline. RFVs (CDRL A026) may be submitted against the appropriate approved baseline prior to production or after the configuration item has been submitted for Government Inspection and Acceptance.

3.5.6 Risk Management

The Contractor shall maintain a risk management process and Risk Management Plan as part of the Program Management Plan that identifies, evaluates, and mitigates program risks from a technical, cost, and schedule perspective (CDRL B014). Risk management activities shall encompass all aspects of the ADC MK 2 program including system design, system engineering, fabrication, integration, test and evaluation, support, and management.

Risks shall be evaluated as to their impact on reliability, safety, supportability, readiness, affordability, schedule and technical performance objectives.

3.5.7 Integrated Product Team (IPT)

The Contractor shall participate in joint IPT(s) as required. When required, the Contractor shall provide representatives to each IPT with the appropriate level of expertise, degree of authority and responsibility to make decisions on behalf of the Contractor. Any findings/recommendations of these IPT teams shall not change the terms and conditions of this contract. IPT findings shall be forwarded to the COR for review. Changes to the contract shall be made via contract modification under full purview of the COR.

3.5.8 Data Management

The Contractor shall manage technical data under this contract to afford the Government visibility of all data. DoD Directive DoD 5220.22-M National Industrial Security Program Operating Manual (NISPOM) applies to technical data developed by, maintained by, or provided to the Contractor. Unclassified limited documents, such as, For Official Use Only (FOUO)and Distribution Statement Controlled, shall be marked in accordance with DoD Regulation 5400.7-R – The DoD Freedom of Information Act (FOIA) Program and DoD Instruction 5230.24 Distribution Statements on Technical Documents. All classified CDRL deliverables and program documentation shall be appropriately marked in accordance with SECNAV M-5510.36. All data shall be developed, managed, used, delivered and exchanged electronically to the greatest extent practical.

3.5.8.1 Digital Data Management

The Contractor shall establish, maintain and control an electronic documentation database, which includes all documents received, generated and distributed under this contract. Authorized Government personnel shall have unlimited access, including the ability to read and download ADC MK 2 program documentation contained in the databank throughout the life of the contract.

The Contractor shall establish and maintain E-Mail capability, compatible with the Government (transmit and receive). A list of files transmitted and/or to be transmitted electronically, along with any procedures necessary for accessing them, shall be included in the Contractor’s Progress, Status, and Management Reports (CDRL B001). Electronic information exchange shall adhere to SECNAV M5510.36 Department of the Navy Information Security Program and DoD Regulation 5400.11-R – Department of Defense Privacy Program.

Deliverable data items, identified in Section I of this contract, stored electronically shall be made available to the Government via practical electronic means (e.g. Internet, remote dial-in, local login, etc.). Unless otherwise indicated, all unclassified CDRLs shall be delivered electronically via email as per the distribution list identified on the CDRL. All electronic CDRLs shall be delivered as read only. Classified data shall be mailed in compliance with all applicable security regulations in the data format specified on its CDRL, normally CD-ROM.

3.5.8.2 Quality Deficiency Reports

The Contractor shall manage and control Government Furnished Information/Property/Equipment/Material (GFI/P/E/M) identified in accordance with the provisions of this contract. The contractor shall report to the Government if any GFI/P/E/M is found unsuitable for use via the applicable Quality Deficiency Report (CDRL B006). Comment by Malinski, Erin K CIV USN NUWC, 02200 (USA) [2]: Are we providing GFM?

3.5.9 Reviews

3.5.9.1 Post Award Conference Comment by Malinski, Erin K CIV USN NUWC, 02200 (USA) [2]: This requires travel. Why is the contractor in charge of a Post Award conference?

The Contractor shall conduct a post award conference within thirty (30) days after the date of contract at the Contractor's facility. The purpose of the Post Award Conference is to clarify contract requirements and address potential problems in executing the contract.

3.5.9.2 Program Reviews

The Contractor shall conduct a formal review of the status of all projects every six (6) months at the Contractor’s facility or by video teleconference (VTC) during the first year of the contract and thereafter as required by the Government. The Contractor shall have available all necessary data and personnel so all Program Reviews may be conducted in a timely and efficient manner. Subcontractor personnel shall be present at, and shall participate in, these reviews on an as-required basis. The location and date of reviews (after the first year of the contract) will be determined by the Government at least 30 calendar days prior to the review. Agenda topics shall include, as a minimum or as applicable, the following as specified by the COR prior to the reviews:

· program critical path assessment;

· cost/schedule performance;

· technical issues;

· risk analysis and management activities;

· test results;

· reliability and maintainability;

· quality program;

· production line of balance;

· logistics and support efforts;

· safety program requirements;

· configuration management activities;

· Government-Furnished Property (GFP) and Information (GFI) status;

· manpower utilization projection/actual;

· data items delivery schedule;

· hazardous material management efforts; and

· status of action items from previous reviews.

In addition, any unresolved issues requiring the attention of senior Government and Contractor personnel may be addressed in detail at an executive meeting held separately from the Program Review, any agreements that incur changes, cost or schedule made during the executive meeting will be briefed and must receive formal concurrence via the PCO. The Contractor shall provide minutes within 15 days following each review. The contractor shall deliver a monthly status on the above items as part of the Contractor’s Progress, Status and Management Report (CDRL B001).

System Production Progress Review (SPPR) meetings may be requested by the Government to be incorporated in other scheduled reviews. The SPPR shall provide the Government visibility of the Contractor’s production and manufacturing process in order to make the appropriate first article decisions and adjustments

3.6 Product Assurance

3.6.1 Quality Program

The Contractor shall maintain a quality system, subject to Government review, that ensures conformance to contractual requirements and meets the requirements of ISO 9001, or an equivalent quality system model (CDRL B011).

All quality assurance operations performed by the Contractor shall be subject to Government verification at any time, to include observing Contractor operations to determine that practices, methods and procedures of this contract are being properly applied.

3.6.2 Workmanship

The Contractor shall use commercial products, processes, and practices to reduce design changes, production, and operational support costs using ANSI/EIA 632 as guidance.

In the case that custom electronics must be designed, Circuit Card Assemblies (CCAs) shall meet or exceed the requirements of the Acceptability of Printed Boards IPC-A-600J standard. All electronics shall be inspected to conform to the Requirements for Soldered Electrical and Electronic Assemblies IPC J-STD-001 standard. The handbook MIL-HDBK-454B General Guidelines for Electronic Equipment should be considered for additional guidance.

3.7 Reliability and Maintainability (R&M) Program

The Contractor shall implement and maintain an R&M Program to ensure the reliability requirements of the PIPS and overall contract are met and a reliability prediction shall be submitted. All internal control procedures, plans and data shall be subject to Government audit and review. The Contractor shall present the status of the reliability program elements at program and technical reviews. MIL-STD-785 shall be used as guidance in meeting the reliability requirements defined in this SOW.

The Contractor shall deliver Reliability and Maintainability Predictions Report (CDRL A007). Data collected within the FRACAS shall be incorporated into all updated versions of the Reliability and Maintainability Predictions Report.

3.7.1 Failure Reporting, Analysis and Corrective Action System (FRACAS) The Contractor shall establish and document a closed-loop failure reporting system that collects, analyzes, and records all equipment/system failures. The Failure Reporting, Analysis, and Corrective Action System (FRACAS) shall promote risk identification and reduction. The Contractor shall use existing data collection, analysis and corrective action system(s), modified only as necessary to meet the requirements of this SOW. The FRACAS shall isolate failures to the failed part/component level. Failure reporting (CDRL A008) shall commence with incoming inspection of parts, followed by Environmental Stress Screening (ESS), first functional inspection/test of assemblies or modules and shall continue through all subsequent subsystem and system level tests. An analysis of the cause of each failure shall be made and documented. All failures (both relevant and non- relevant), which are used to determine compliance with reliability requirements, shall have corrective actions implemented to prevent or reduce recurrence of the failure. The FRACAS data shall be used to identify failures on test items, track reliability growth, provide analysis of failure modes and causes, prioritize failure trends, propose changes to correct deficiencies, and track solution effectiveness. Failure data for NDI shall be included in the FRACAS. The FRACAS database shall be available for Government review. Corrective action approval procedures shall also be documented and available for Government review.

3.7.2 Part Selection

The ADC MK 2 shall be based upon the use of components of standard manufacture when suitable units can be procured and used. The ADC MK 2 shall permit standardization to the maximum extent possible. Connectors, cabling, screw sizes, and packaging shall be standard size. The Contractor’s part selection process shall use for information SD-18 NOTE 3, MIL- PRF-38535K, with respect to microcircuit selection. Parts with limited availability or potential obsolescence issues shall not be used by the Contractor. The Contractor shall provide a list of parts with potential obsolescence issues, or a parts list that can be screened and vetted for Diminishing Manufacture Sources and Material Shortages (DMSMS) (CDRL C004). Parts derating shall be in accordance with NAVSEA SD-18 NOTE 3.

3.8 Environmental and Safety Requirements

3.8.1 Environmental Health and Safety Program

The Contractor shall implement a Programmatic Environmental Health and Safety Program. The Contractor shall deliver a Programmatic Environmental Safety and Health Evaluation (PESHE) Plan (CDRL B012).

3.8.2 Hazardous Material Program

In accordance with the tenets of NAS 411, the Contractor shall implement and maintain a Hazardous Material Management Program (HMMP) to identify any hazardous materials, federally regulated substances and any ozone depleting solvents that are used in the manufacture of items delivered under this contract or that are produced as a by-product of the manufacturing process under this contract.

The hazardous materials, federally regulated substances and ozone depleting solvents are identified and defined in FAR 52.223-3 and FAR 52.223-11. Any substance or material that is regulated or controlled locally (by State or local Government authorities) that is not identified by FAR 52.223-3 or 52.223-11 shall be defined as a hazardous material for the purposes of this contract and shall be addressed in all tasks identified in this paragraph.

Any material (hazardous or otherwise) contained with the unit shall be on the list of approved materials for surface ships and submarines. The Contractor shall identify any hazardous materials defined above that are anticipated to be produced during the manufacture of items under this contract as part of the HMMP Report (CDRL B015).

3.8.3 System Safety Program

The Contractor shall maintain a System Safety Program Plan (SSPP) for the ADC MK 2 using MIL-STD-882E as guidance (CDRL B004). The ADC MK 2 shall be produced to prevent or lessen the risk of personnel injuries and shipboard and/or support equipment damage. The Contractor shall minimize the use of hazardous material and shall incorporate safety features for protection during storage, shipment, handling and service use.

The Contractor is responsible for ensuring that device safety is achieved and that all system specific safety requirements are met. This includes verifying as safe any changes due to engineering or production changes. Once complete, the Contractor is responsible to verify system safety and to determine the safety risk being assumed prior to test or operation. The Contractor is permitted to propose changes to the SSPP where needed to control costs, fit organizational protocols, leverage lessons learned from past SSPPs, or to otherwise improve the safety approach.

Any Lithium battery proposed for use shall comply with the instructions contained in technical manual S9310-AQ-SAF-010 Batteries, Navy Lithium Safety Program Responsibilities and Procedures of 18 Oct. 2010, regarding design, use, packaging, storage, transportation and disposal.

If Ordnance and/or Electro-Explosive Devices (EEDs) are used, ADC MK 2 shall have incorporated the safety requirements of MIL-STD-1316E (1), MIL-STD-2105D and MIL-DTL-23659F. Further, MIL-STD-709D and MIL-D-21625G shall be used as guidance. The Contractor shall provide Explosive Hazard Classification Data (CDRL A009). The Contractor shall comply with publication SW020-AC-SAF-010 Transportation and Storage Data for Ammunition, Explosives and Related Hazardous Materials.

3.9 Integrated Logistics Support

The Contractor shall establish an ILS program for the products used in the ADC MK 2. The objective of this ILS program is to ensure that all hardware and software products, including all NDI/COTS, modified NDI/COTS, and newly developed items delivered under this contract are fully supportable throughout their life cycle.

3.9.1 Maintenance Planning Requirements

The Contractor shall minimize the required preventive maintenance actions to meet the shelf/service life of the ADC MK 2. The Contractor shall perform an evaluation of all maintenance requirements and recommend any changes or improvements to the Government. As specified in the PIPs, there shall be no maintenance requirements, apart from inspection and cleaning, after the ADC MK2 units are delivered.

3.9.2 Inventory Documentation

3.9.2.1 Asset Management Data

The Contractor shall provide Naval Supply Systems Command (NAVSUP) Logistical Operations Center (NLOC) with…