Section_J_-_Attachment_1_TIH_Statement_of_Work_20130819.doc

N00253-13-R-0013

N00253-13-R-0013

Attachment 1

STATEMENT OF WORK

FOR

PROGRAM EXECUTIVE OFFICE SUBMARINE

TECHNOLOGY INSERTION HARDWARE (TI-16 / TI-18)

30 APRIL 2013

Table of Contents

SCOPE

31.1 Purpose

31.2 Background

41.3 Summary

REFERENCE DOCUMENTS

62.1 Government Specifications, Standards, & Handbooks

82.2 Industry Based Standards Documents

REQUIREMENTS

93.1 General Requirements

93.1.1 Collaborative Development Environment

113.1.2 Integrated Program Management

183.1.3 System Engineering

203.1.4 Test and Evaluation

213.1.5 Quality Assurance

223.1.6 Contract Data Requirements List Items

223.1.7 Manufacturing & Production Order Process

233.2 Specific Requirements - Products

233.2.1 Hardware Deliverables

243.2.2 Installation Support Equipment Deliverables

243.2.3 Software Deliverables

253.3 Specific Requirements - Services

253.3.1 Systems Engineering Services

313.3.2 Hardware Engineering Services

313.3.3 Software Engineering and Management

343.3.4 Test and Evaluation Services

363.3.5 Integrated Logistics Support Services

453.3.6 Configuration Management

513.3.7 Installation and Checkout Services

Appendix A List of Acronyms A-1

1 SCOPE

1.1 Purpose

This Statement of Work (SOW) defines the efforts required for the program management, engineering, design, development, logistics, configuration management, production, test, evaluation, installation support, and support of displays, processors, network systems, and other equipment associated with the Program Executive Office Submarine Technology Insertion Hardware project (hereinafter called TIH (16/18)).

The Contractor shall design, develop, test, qualify, produce, deliver, install and support TIH (16/18) equipment and enclosures. The term “equipment” is used to refer to Advance Production Units (APU), Lowest Replaceable Unit (LRU), systems, kits, parts, spares, units, products, and all other deliverable hardware/test software/firmware contained within this SOW. An APU is any TIH (16/18) component that has not yet been approved for production under this contract. Effort may include upgrades to existing Technology Insertion level to the target configuration.

This SOW also defines the efforts required for production equipment, parts, engineering services, and management oversight to support Royal Australian Navy (RAN) customers.

Contractor personnel supporting some areas of a delivery/task order will require access to restricted data. The security clearances required are outlined in the DD254, Attachment 2. Some of the Contractor personnel supporting TIH (16/18) will require a security clearance level of up to Secret.

A table showing the anticipated configuration change (from/to) per class for TIH 16/18 is available for review in the Electronic Technical Information Center (E-TIC). Access instructions are provided in Section L. Data is available for all baselines and will be released to awardee upon contract award. Upon issuance of a delivery order, a full set of drawings and other data applicable to the effort will be provided.

1.2 Background

TIH (16/18) is the U.S. Navy’s latest generation of a continuously evolving family of display, processor and network systems that provide computer processing and memory, data storage and extraction, and Input/Output (I/O) interfaces to support specific software applications of Navy Combat Control and Sonar Systems. TIH (16/18) is designed to support the Program Management and Program Executive Office Submarine implementation of Open Architecture (OA) for Navy Submarine systems. TIH (16/18) will maximize flexibility and modularity by procuring a processing system designed around commercially available hardware and software, which will conform to Open Architecture Computing Environment (OACE) Technologies and Standards. It is the Government’s intent to adopt best commercial practices in completing system development and acquisition objectives.

The purpose of the TIH (16/18) Combat Control and Sonar System contract is to provide display, workstation, processor, and network systems functionality for Mission Critical/Essential Systems onboard submarine platforms. Each TIH (16/18) “suite” consists of display and processor components arranged in specific system configurations to satisfy specific workstations, processors, file servers, or other network requirements. The Navy will be procuring these systems incrementally, and will require technical services for fielded equipment delivered under this contract. Life cycle support and technical services will also be required to ensure adequate supportability of TI-16 and TI-18 fielded units.

1.3 Summary

The work shall be performed as specified in Section B and as directed by delivery orders/task orders where applicable, to include the following tasks:

· Provide and deliver CDRLs as required in this SOW (applicable to CLIN 1006).

· Provide engineering services to include the design, development, fabrication, assembly, test, and delivery of equipment, configurations, and or enclosures for TIH (16/18) platforms as applicable. Each initial delivery will include all base-lined engineering documents, drawings, product lists, and Integrated Logistic Support (ILS) products (applicable to CLINs 1002 and 2002).

· Deliver spares/repair parts and technology insertion/refresh kits for each delivery as required by the Government (applicable to CLINs 1004 and 2004).

· Provide all support material and pre-production hardware (applicable to CLIN 1001 and 2001).

· Develop and manage factory acceptance tests, evaluation plans, procedures, and operating environment products (where applicable) for equipment under this contract (applicable to CLINs 1002 and 2002).

· Participate in the design and integration efforts to include technology insertion and refresh planning and validation. Support design, development, installation, and validation/verification, including participation in Integrated Product Teams (IPT), modernization planning, and various reviews and working group meetings (applicable to CLINs 1002 and 2002).

· Provide and deliver associated firmware and test software (where applicable) for equipment developed under this contract (applicable to CLINs 1002 and 2002).

· Provide reliability engineering and failure analysis (applicable to CLINs 1002 and 2002).

· Provide maintenance and upgrades for equipment under this contract. Procure material in support of maintenance and upgrades for equipment under this contract (applicable to CLINs 1004 and 2004).

· Develop and update Configuration Management (CM) products. Through production, applicable CLINs are 1002 and 2002. Post production, applicable CLINs are 1004 and 2004.

· Develop source data to the Government in support of ILS products (i.e. Interactive Electronic Technical Manuals (IETM), Allowance Parts List (APL), and Computer Based Training (CBT). Develop and deliver ILS products to support development, production, and installation for delivered items Through production, applicable CLINs are 1002 and 2002. Post production, applicable CLINs are 1004 and 2004.

· Support in-service engineering and field service tasking, such as installation, field integration support, repair, and refurbishment efforts as required. Procure material procured in support of in-service engineering and field service tasking efforts (applicable to CLINs 1004 and 2004).

· Provide commercial component obsolescence management including vendor monitoring, replacement component qualification, testing, and ILS updates. Through production, applicable CLINs are 1002 and 2002. Post production, applicable CLINs are 1004 and 2004.

· Produce and deliver production equipment (applicable to CLINs 1000 and 2000).

· Provide engineering services to include the design, development, fabrication, assembly, test, and delivery of equipment, configurations, and or enclosures for RAN (applicable to CLIN 2009). Procure materials in support of design and development phase for RAN (applicable to CLINs 2008). Produce and deliver production equipment for RAN (applicable to CLIN 2007).

2 REFERENCE DOCUMENTS

2.1 Government Specifications, Standards, & Handbooks

The following documents form a part of this SOW and are incorporated by reference.

(U) MIL-STD-108E

through Notice 2

27 Jun 1994 (Amendment)

2.2 Industry Based Standards Documents

2.3 Document Library

Unclassified technical information related to the Technical Insertion Hardware (TIH) effort will be provided by the Navy on an Electronic Technical Information Center (E-TIC).

3 REQUIREMENTS

3.1 General Requirements

3.1.1 Collaborative Development Environment

To ensure continued success of the program, the Contractor will be required to work in a collaborative environment with a consortium of Government and industry partners including but not limited to the U.S. Navy, Navy Laboratories, Academia, and Royal Australian Navy (RAN) as part of the Navy's Foreign Military Sales Program to ensure continued success of the program.

Contractor shall participate in a process to reduce cycle time for proposals and minimize the contract award timeframe utilizing maximum communication and exchange of data. Participants will include Government and Contractor resources as required to ensure process success.

3.1.1.1 Integrated Data Environment

The Contractor shall utilize an integrated (electronic) data environment for electronic exchange of contract-related data and data products. The data environment may be Government provided, Contractor provided, or a combination of both. For segments of the data environment that are Government provided, Contractors shall abide by all access control regulations and policies. For segments that are Contractor provided, the Contractor shall provide the Government (and/or Government support Contractors) electronic access to that segment of the integrated development environment throughout the term of the contract.

The Contractor shall be responsible for the digital generation, receipt, and electronic delivery of data. All data shall be developed, managed, used, and delivered/exchanged electronically to the greatest extent practical. Data shall be stored/disseminated in a non-proprietary format, compatible with DoD standard software tools. Data archives may be requested throughout and at the end of the contract term.

The Government may request the Contractor to deliver internal data developed or modified under this contract.

Controlled Unclassified Information (CUI) such as FOUO, Security Classification Guides (SCG), and other distribution statement controlled documents, are not authorized for public release and cannot be placed on a publicly accessible web site or web server. All emails containing such information or attachments must be digitally signed if being transmitted within Navy networks, and digitally signed and encrypted if being transmitted outside a Navy network to an approved contractor email address. Transmission of CUI to personal email accounts (AOL, Yahoo, Hotmail, Comcast, etc.) is strictly prohibited.

3.1.1.2 Design Disclosure, Intellectual Property and Data Rights

The Contractor shall utilize and maintain a process that provides design disclosure directly to authorized third party developers via electronic access to in-process design documentation and computer test software. The Contractor shall support an Open Source Initiative with other participants within the Combat Control and Sonar Systems development community. The Contractor shall discuss and attempt to resolve any problems between the Contractor and the third party developers and shall provide written notification to the Contracting Officer of any problems, including documentation of problem resolution. (CDRL A014 – Technical Report – Study/Services).

The Contractor shall provide a list, entitled "Background Inventions--Identification and Licensing" (the BIIL List), identifying all inventions described in and covered by any patents or pending patent applications in which the Contractor (1) has any right, title, or interest; and (2) intends to include in any items, equipment, processes to be developed or delivered under the resulting contract, or that are described or disclosed in any Technical Data (TD), Computer Software (CS), or Computer Software Documentation (CSD) to be developed or delivered under the resulting contract. Such inventions are hereafter referred to as "background inventions." (CDRL A014 – Technical Report – Study/Services).

The Contractor's failure to identify a background invention in the BIIL List, as set forth above, shall constitute a grant to the Government of a nonexclusive, nontransferable, irrevocable, worldwide, paid-up license to practice, and to have practiced for or on its behalf, such invention for Government purposes related to the affected TIH (16/18) equipment.

3.1.2 Integrated Program Management

The Contractor shall perform business management functions to ensure contracting related actions provide for production orders that meet established need dates of the Government. Contracting related actions include development and submission of proposals, negotiation of proposals, and responses to requests for cost estimates.

The Contractor shall provide internal management functions, including technical direction, risk management, administration, and planning for all activities within this contract. The Contractor shall provide program planning, budget allocations, cost control, cost estimates, proposal support and status reporting for tasks associated with this contract. The Contractor shall be responsible for coordination with the Contracting Officer, Program Office and other agencies in the execution of this contract.

3.1.2.1 Progress, Status and Management Report

The Contractor shall develop and propose program management metrics appropriate to the Contract Line Item Number (CLIN) or Technology Insertion phase of the contract. Metrics must accurately reflect cost, schedule, and performance. These proposed program management metrics shall be initially presented at a post award review. The Contractor shall report these metrics in the Progress, Status and Management Report (CDRL A001 - Contractor’s Progress, Status and Management Report) and at each design review and program review.

The Contractor shall maintain technical and financial status and generate Progress, Status and Management Reports (CDRL A001 - Contractor’s Progress, Status and Management Report). The financial status shall include the Estimate at Completion (EAC), Actuals to Date (ATD), Estimate to Complete (ETC), amount funded, and outlooks for when additional funding is required, as necessary, for tasks as identified in the delivery/task orders. Status shall contain the current status of all orders including required, estimated, and actual delivery dates.

The Contractor shall support Program Management Reviews and Program Milestones as required per CDRL requirements and Government direction.

3.1.2.2 Contract Performance Report

In the performance of this contract, the Contractor shall utilize and maintain an integrated performance management system. The Contract Performance Report shall be linked to and supported by the Contractor’s management processes and systems to include the Integrated Master Schedule (IMS), Contract Work Breakdown Structure (CWBS), change management, material management, procurement, cost estimating, and accounting systems. The Contract Performance Report shall be per Technology Insertion (TI) and grouped per delivery/task order. The correlation and integration of these systems and processes shall provide for early indication of cost and schedule problems, and their relation to technical achievement (CDRL A002 - Contract Performance Report).

Furthermore, the Contractor shall report ALL Contractor labor hours (including subcontractor labor hours) required for performance of services provided under this contract for NAVSEA, PEO Submarines, via a secure data collection site. The Contractor is required to completely fill in all required data fields using the following web address https://doncmra.nmci.navy.mil.

Reporting inputs will be for the labor executed during the period of performance during each Government fiscal year (FY), which runs October 1 through September 30. While inputs may be reported any time during the FY, all data shall be reported no later than October 31 of each calendar year. Contractors may direct questions to the help desk, linked at https://doncmra.nmci.navy.mil.

3.1.2.3 Contract Work Breakdown Structure

The Contractor shall develop, deliver, and maintain a Contract Work Breakdown Structure (CWBS) and CWBS dictionary using the guidance of MIL-HDBK-881. The CWBS provides the basis for further extension by the Contractor to lower levels during the performance of the contract. The Contractor shall extend the CWBS down to the appropriate level required to provide adequate internal management, surveillance, and performance measurement. The Contractor shall use the CWBS as the primary framework for contract planning, budgeting, and reporting of the cost, schedule, and technical performance status to the Government. The Contractor shall analyze the system requirements specified in the SOW and system specifications and translate them into a structure representing the products and services that comprise the entire work effort under the contract. The Contractor's team or organizational entity responsible for the systems engineering of the system shall prepare the technical elements of the extended CWBS. The Contractor, if necessary, shall update the CWBS during the execution of the contract. Changes to the CWBS or associated definitions require approval of the Government (CDRL A003 - Contract Work Breakdown Structure).

3.1.2.4 Integrated Master Schedule

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 each Technology Insertion and grouped per delivery/task order. Proposed changes to the program schedule must be approved by the Government prior to 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. (CDRL A004 - Integrated Master Schedule)

3.1.2.5 Subcontract Management and Control

The Contractor shall identify and monitor subcontractor technical, quality, schedule, and milestone achievement on a continuing basis, according to the Contractor’s own established subcontract management techniques. Contractor shall obtain Government approval to exceed the subcontractor portion reflected in the contract, in accordance with FAR 52.244-2. In addition the Contractor shall have an approved purchasing system in accordance with DFARS 252.244-7001.

3.1.2.6 Reviews

The Contractor shall coordinate, schedule, make preparations for, conduct, facilitate, participate, and host reviews, meetings, and conferences as required. The Contractor shall provide agendas (CDRL A005 - Conference Agenda), presentation materials, action items, action item status, and minutes (CDRL A006 - Conference Minutes). The agendas shall be reviewed jointly between the Government and Contractor and distributed electronically by the Contractor as required by the CDRL. Minutes of the meetings shall be kept by the Contractor unless otherwise directed by the Government. Minutes shall include a summary of discussions, copies of handouts or graphics, and a listing of action items, and shall be distributed electronically.

The Contractor shall develop and maintain an action item status and tracking system for all reviews to ensure actions are assigned to specific individuals, due dates are established, and accurate status is provided to the Government.

The Contractor shall conduct a post award review as requested by the Government to establish contacts with Government personnel.

The Contractor shall conduct program reviews every three (3) months. The Contractor shall support management meetings regarding delivery/task order status on a regular basis (to be mutually agreed upon between the Government and Contractor) between the program reviews. These reviews will be used to assess the Contractor’s progress and status. During these reviews, the Contractor shall provide, at a minimum, comprehensive status of:

a. Cost and schedule performance

b. Design and technical issues

c. Integration and interoperability issues

d. Hardware and computer software engineering

e. Risk analysis activities

f. Reliability and maintainability

g. Quality program

h. Test and evaluation activities

i. Production activities

j. Logistics development and support efforts

k. Safety program status

l. Configuration management activities

m. Government Furnished Property/Information (GFP/I) status

n. Efforts authorized under delivery and task orders

o. Manpower utilization projection/actual (three (3) month history, nine (9) month future)

p. Data items delivery schedule

q. Hazardous material management efforts

3.1.2.7 Integrated Baseline Reviews

The Contractor shall engage jointly with the Government’s Integrated Baseline Reviews (IBR) to evaluate the risks inherent in the Contractor’s planned performance measurement baseline. The initial IBR for each delivery/task order shall occur within one month after issuance of the order, or as requested by the Government. Subsequent IBR(s) shall occur following Class I Engineering Changes to the product baseline. Each IBR shall verify that the Contractor is using a reliable performance measurement baseline, which includes the entire Scope of Work for the supply item, is consistent with contract schedule requirements, and has adequate resources assigned.

3.1.2.8 Risk Assessment and Management

The Contractor shall perform a continuing analysis of program, technical, cost, and schedule risks associated with this contract. The analysis shall identify the risks associated with each area, identify the impact of each risk on the overall program, and propose approaches for reducing identified risks. Risk analysis status shall be reported in the Contractor’s Progress, Status and Management Report (CDRL A001 - Contractor’s Progress, Status and Management Report) and presented during Program and Technical Reviews.

3.1.2.9 Government-Furnished Information/Property/Equipment/Material

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 any GFI/P/E/M found unsuitable for use (CDRL A007 - Government Furnished Information Deficiency Report; CDRL A008 - Quality Deficiency Report).

3.1.2.10 Data Management

The Contractor shall maintain Contract data status for recording, planning, scheduling, and reporting the status of program data requirements including electronic mail transmittals; and maintain a list of all Contractor and subcontractor data generated in support of this contract.

3.1.2.10.1 Electronic Contract Data Requirements List Delivery

The Contractor shall deliver all unclassified Contract Data Requirements List(s) (CDRL(s)) electronically. Refer to Section 3.1.1.1 for Controlled Unclassified Information (CUI). Authorized transmission modes for CUI are identified in Attachment 2 – DD 254, Contract Security Classification Specification. CDRL(s) too large for delivery by e-Mail or electronic media (file size, drawings, data packages etc.) shall be delivered in accordance with the CDRL distribution requirements. (CDRL A018 – Technical Data Package).

3.1.2.11 Integrated Product Team

The Contractor shall participate in joint Integrated Product Teams (IPTs) as required. The Contractor shall assist the Government in developing IPT charters. These IPTs will integrate schedule and performance data to provide a global perspective with detailed insight into the managerial and technical aspects impacting Government and industry. The Contractor shall provide representatives to each IPT with the appropriate level of expertise and degree of authority and responsibility to make decisions on behalf of the Contractor. As part of the IPTs, the Contractor shall have responsibility for the following functions:

a. Monitoring and reporting of subsystem status and progress;

b. Joint identification, evaluation, management, and reporting of risk mitigation and cost reduction initiative efforts;

c. Identification, collection, analysis, and reporting of appropriate metrics for measurement of cost/schedule control, engineering and production progress;

d. Joint evaluation and management resolution of major issues (including obsolescence) associated with hardware and software engineering, production, integration, test, and shipboard Installation/Checkout (I&C) activities;

e. Verification that the Contractor’s design disclosure process is providing data that is current, complete and accurate to third party developers;

f. Joint evaluation and management of the Integrated Logistic Support (ILS) effort; and

g. Additional functions as determined by the specific IPT charter.

Contractor shall participate in Government held contracts IPT(s) as required by the Government whose purpose will be to discuss and execute a process to reduce cycle time for proposals and minimize the contract award timeframe utilizing maximum communication and exchange of data. Participants will include Government and Contractor resources as required to ensure process success.

3.1.2.12 Government On-Site Activities

The Contractor shall make available to the technical representatives authorized by the Government all required program data pertaining to the Contractor and subcontractor activities in the performance of this contract.

The Contractor shall make available access to telephones, FAX transmission and reception, computer and network components, word processing, internet services, and copier machines as required, to support analytical and tracking tasks. This access is needed for temporary visits to contractor facilities by one to two government personnel.

3.1.2.13 Formal Proposals

All formal proposals and budgetary estimates shall be prepared and submitted only in response to a Request for Proposal (RFP) received from the Contracting Officer or duly authorized representative. Contractor proposals shall include all costs, including material costs, technical costs, labor mix and man-hour estimates, required to complete tasking provided via delivery/task order.

Unless otherwise mutually agreed to by the parties, formal proposals shall be submitted within 45 calendar days. A change in the Government’s requirements will reset the delivery schedule for proposals and budgetary estimates. Incomplete or unknown information shall be identified within three (3) business days and concurrence obtained from the Contracting Officer or duly authorized representative, to preclude delays.

3.1.2.14 Rough Order of Magnitude

The Government may request Rough Order of Magnitude (ROM) estimates in support of program affordability and feasibility analyses. Unless otherwise mutually agreed to by the Government and the Contractor, ROM estimates shall be submitted within five (5) calendar days of the request. Incomplete or unknown information shall be identified within three (3) business days and concurrence obtained from the Contracting Officer or duly authorized representative, to preclude delays. During performance of the contract when requested by the Government the Contractor shall provide an annual estimate of effort corresponding with each Fiscal Year (FY) to assist with programmatic budgets.

3.1.3 System Engineering

3.1.3.1 Open Systems Architecture Approach

The Government intends to procure system(s) that are compliant with the tenets of Open System Architecture, as described and referenced in the Defense Acquisition Guide. As part of this contract, the Contractor will define, document, and follow an open systems approach for using modular design, standards-based interfaces, and widely-supported consensus-based standards. The Contractor shall comply with open systems architecture during all design reviews.

Equipment developed under this contract will be built to comply with OA standards, incorporating functionally modular designs comprised of COTS/NDI software, hardware and firmware. The equipment will be integrated together using industry-accepted interface standards in accordance with the specifications.

As part of an open system architecture approach, the Contractor will identify to the Government all Commercial-Off-the-Shelf/Non-Developmental Item (COTS/NDI) equipment, their functionality and proposed use in the system, and provide copies of license agreements related to the use of the equipment for Government approval prior to use.

During all technical and design reviews, the Contractor shall present/demonstrate how developmental items will be Open Systems Architecture compliant, and at a minimum:

· Describe traceability of the requirements back to authoritative sources, and the traceability process used.

· Describe how the proposed system architecture meets the modular, open design goals, including the steps taken to use non-proprietary or non-vendor unique COTS or reusable NDI equipment wherever practicable.

· Describe its rationale for the modularization choices made to generate the design.

· Provide rationale that explicitly addresses any tradeoffs performed, particularly those that compromise the modular and open nature of the equipment.

· Describe how it will mitigate the risks associated with technology obsolescence.

· Describe how it will avoid being locked into proprietary or vendor-unique technology and reliance on a single source of supply over the life of the equipment.

The Contractor shall utilize the following open systems architecture approach characteristics:

a. The Contractor shall develop and maintain an architecture that incorporates appropriate considerations for re-configurability, portability, maintainability, technology insertion, vendor independence, reusability, scalability, interoperability, upgradeability, and long-term supportability.

b. The Contractor shall develop an architecture that is layered and modular, and uses COTS/NDI hardware, operating systems, and middleware that utilize non-proprietary or non-vendor-unique, key Application Programming Interfaces (API). The Contractor’s design approach shall be applied to all subsystems and equipment.

c. Modular Open Systems Approach (MOSA) –The Contractor’s design approach shall produce equipment that consists of hierarchical collections of software and hardware configuration items (components) where applicable. These components shall be of a size that supports competitive acquisition as well as reuse. The Contractor’s design approach, to the maximum extent practicable, shall utilize components that are available commercially or within the DoD, to avoid the need to redevelop products that already exist and that can be re-used.

3.1.3.2 Human Factors Engineering

The Contractor shall incorporate the Human Engineering Design Criteria Standard (MIL-STD-1472) into the Human Factors Engineering (HFE) design of equipment. HFE analyses and tradeoffs shall be reported at all technical reviews.

3.1.3.3 Safety

The Contractor shall utilize and maintain a System Safety Program to support efficient and effective achievement of overall safety objectives in accordance with MIL-STD-882.

3.1.3.4 Environmental Compliance

The Contractor shall utilize and maintain a process to identify, track and resolve Environmental, Safety, and Occupational Health (ESOH) hazards associated with the manufacture, test, repair, and disposal of TIH (16/18) equipment. The Contractor shall report ESOH hazards and status of hazard resolution in the Progress, Status and Management Reports (CDRL A001 – Contractor’s Progress, Status and Management Report) and at all design reviews and program reviews.

The Contractor shall eliminate (or minimize to the greatest extent possible) the use of hazardous materials in the design, development, qualification, and production of the TIH (16/18). The Contractor shall not use materials that are Class I or Class II Ozone Depleting Substances. The Contractor shall refer to guidance per Submarine class to determine specific environmental compliance required. The Contractor shall report and track hazardous materials that cannot be eliminated in the Progress, Status and Management Reports (CDRL A001 - Contractor’s Progress, Status and Management Report) and at all design reviews and program reviews. The Contractor shall provide Material Safety Data Sheets (MSDS) (OSHA Form 174) for hazardous materials that cannot be eliminated.

3.1.4 Test and Evaluation

The Contractor shall plan, program, schedule, conduct, support and document all performance testing associated with the hardware, software, firmware and operator/system interface, that are necessary to demonstrate that equipment designed, developed, and produced under this contract is compliant with the specifications and will operate in the users’ environments. The Contractor shall identify and provide all test hardware, software, tools, support equipment, test stimuli, and operating systems necessary to conduct component qualification, reliability burn-in testing, Environmental Qualification Tests (EQT), and Factory Acceptance Tests (FAT). The Contractor shall provide access to the TIH (16/18) equipment in its development and test facilities for the Government to perform on-site independent tests or evaluations.

3.1.5 Quality Assurance

Contractor shall implement and maintain a Quality Assurance (QA) program that meets or exceeds the requirements represented in ISO9001 (or equivalent) to meet program objectives during the performance of the contract. The Contractor shall utilize manufacturing processes under an established QA program that ensures equipment produced under this contract is delivered in accordance with contract requirements. The QA program shall address development, production, and post-delivery phases of TIH (16/18) equipment. At a minimum, the quality management process shall include the following key QA activities:

a. Establishment of capable processes;

b. Monitoring and control of critical processes and product variation;

c. Establishment of mechanisms for feedback of field product performance;

d. Implementation of an effective root cause analysis and corrective action system; and

e. Continuous process improvement.

3.1.5.1 Problem Reporting System

The Contractor shall utilize a single system for the identification, tracking, and resolution of all hardware, test software, firmware, and baseline documentation problems not resolved prior to delivery. In addition, this problem reporting system shall be used to track test problems and errors. The Contractor shall provide the Government (and/or Government support Contractors) electronic access to its problem reporting system and associated project data throughout the term of the contract via the project IDE; historical data from the change report system shall be delivered to the Government in a form specified in the CDRL. Problems shall be included with the Contractor’s Progress, Status and Management Report (CDRL A001 – Contractor’s Progress, Status and Management Report).

3.1.5.2 Manufacturing Process Control

The Contractor shall implement manufacturing processes that ensure all TIH (16/18) equipment produced under this contract are delivered without defects.

The Contractor shall follow current industry or Government approved standards for manufacturing controls to include ANSI/J-STD-001.

3.1.5.3 Information Assurance

The Contractor shall implement and apply safeguards for information and information technology resources in accordance with the specifications provided in the Contract Security Classification Specification (DD FORM 254, Attachment 2). The information and information technology resources must be maintained at an appropriate level of confidentiality, integrity, availability, authentication, and non-repudiation based upon mission criticality, level of required information assurance and classification or sensitivity level of information entered, processed, stored, or transmitted for Submarine Systems. The Contractor shall safeguard information and information systems through the use of multi-disciplined defensive layers, as well as sound administrative and operational practices.

3.1.6 Contract Data Requirements List Items

Contract Data Requirements List (CDRL) items are specified in Section J. Whenever a CDRL requirement is referenced in this SOW, the CDRL number is provided.

Contractors shall note the following with regards to technical documentation to include, but not limited to: reports, material, drawings.

3.1.7 Manufacturing & Production Order Process

The Contractor shall provide, update, and maintain an ordering system/process as requested by the Government for use by the Government and their support Contractors.

The Contractor shall perform workload planning to ensure requirements of individual programs of record utilizing this contract are balanced against the production capacity of the Contractor, and that the hardware requirements associated with this contract are met for these programs of record.

3.2 Specific Requirements - Products

3.2.1 Hardware Deliverables

The Contractor shall design, build, and test the required units, ship sets, enclosures, kits and/or spares in accordance with the delivery/task order(s).

3.2.1.1 Variant Kits

Variant Kits are defined as the collection of COTS and non-COTS equipment and miscellaneous hardware that would be installed in existing shipboard enclosures to comprise a Variant Unit.

3.2.1.2 Variant Enclosures

Variant Enclosures are defined as the mounting structure and associated miscellaneous hardware necessary to provide the physical interface between the variant kit and the submarine structure.

3.2.1.3 Variant Units

Variant units are defined as the complete assembly of a Variant Kit and Variant Enclosure to create a specific configuration item.

3.2.1.4 Variant Ship Sets

Ship sets are defined as a specific collection of Variant Units to fulfill the hardware requirements for a program of record system (e.g. Sonar Suite or Combat Systems Suite).

3.2.1.5 Spares

Spares are defined as individual COTS and non-COTS components that may be required to repair kits or enclosures during production, testing, or installation.

3.2.2 Installation Support Equipment Deliverables

3.2.2.1 Pre-Cable Kits

The Contractor shall manufacture and deliver Pre-Cable Kits used during shipboard installation of variant unit and variant kits. Definition, design, and composition of the Pre-Cable Kits are discussed in the Services section (3.3.7.1) of this SOW.

3.2.2.2 Installation Aids

As necessary, the Contractor shall develop, manufacture, deliver, update and maintain Installation Aids (drawer lifts / fitting jigs) necessary to safely and efficiently install the equipment aboard the submarine. Definition, design, and composition of the Installation Aids are discussed in the Services section (3.3.7.2) of this SOW.

3.2.2.3 Two Dimensional Installation Mock-Ups

The Contractor shall develop, manufacture, deliver, update and maintain Two Dimensional (2D) mockups as part of the Installation Support Equipment. Composition and definition of the 2D mockups are discussed in the Services section (3.3.7.3) of this SOW.

3.2.3 Software Deliverables

3.2.3.1 Developmental Software

Software/scripts developed under this SOW are solely for the purposes of test/demonstration of the TIH (16/18) equipment itself. Software/scripts developed under this SOW shall not be considered proprietary to any Contractor. The Contractor shall be responsible for the development of any test software not available in the open market. OA conventions shall be used in this development.

3.2.3.2 Diagnostic Software

The Contractor shall provide diagnostic software that is capable of operating at startup. The diagnostics software shall detect and isolate system faults down to the Lowest Replacement Unit (LRU). It shall provide the system health and fault detection information at start up time. In addition to startup, diagnostics shall be able to execute continuously in support of FAT and EQT.

3.3 Specific Requirements - Services

To support the entire range of potential tasks envisioned under this contract, this section of the SOW supports the conduct of design, development, and test, reverse engineering, technology insertion/refreshment, engineering services, field engineering services, and system support. The services identified in this section of the SOW will be as tasked under specific delivery/task orders executed during performance of this contract as required.

3.3.1 Systems Engineering Services

3.3.1.1 Systems Engineering Management

The Contractor shall provide a System Engineering Management Plan (SEMP) with the incorporation of inputs from the supporting IPTs and working groups (CDRL A016 - System Engineering Management Plan). The SEMP shall describe how development will progress, and how the various technical inputs to the systems engineering effort will be integrated into a collaborative development environment. A description of each major technical review shall be included.

3.3.1.2 Requirements Analysis

The Contractor shall conduct detailed system engineering and design analyses of the proposed hardware/firmware/test software test system(s) in accordance with the specifications included in individual delivery/task orders. Materials and equipment to be incorporated into the system or subsystems shall be specified including a listing of any hazardous materials or processes incorporated or used in the fabrication of the system or subsystems. The design analyses shall consist of detailed examinations of the design techniques and materials that the Contractor plans to use to meet the requirements of the specifications. The design analyses shall be performed on both the system and component levels.

The Contractor shall develop engineering design data packages (CDRL A019 - Design Review Data Package). Materials and equipment to be incorporated in the system shall be specified. Stress levels and safety factors, as appropriate, shall be identified for all mechanical and electrical parts. Methods and materials to be used to protect the equipment from the environment shall be in accordance with MIL-S-901, MIL-STD-461, MIL-STD-810, MIL-STD-167-1, and MIL-HDBK-470. In addition to the system hardware physical considerations, the design analyses shall evaluate the system concept in terms of operability, reliability, producibility, maintainability and supportability objectives using the guidance of MIL-STD-1472 and MIL-HDBK-470. The Contractor shall utilize analysis and application of Reduction of Total Ownership Cost (RTOC) considerations within the design, development, production, and support of TIH (16/18) equipment.

The Contractor shall ensure that the…