TI-16_Section_C_SOW_10-5-2015_DRAFT.DOCX

Section C - Descriptions and Specifications

SECTION C-1 LINE ITEM DESCRIPTIONS

CLINs 0001, 0004 and 0007– The Contractor shall design and develop the TI 16 OL-798(V)3 Network Server Group (NSG(V)3), Remote Display Processor (RDP) Cabinet (and supporting Display Control Units (DCU)) and Auxiliary Processing Cabinet (APC) in accordance with Statement of Work and the requirements detailed in Attachment J-2. CLINs 0001, 0004 and 0007 shall include all development efforts for the TI 16 OL-798(V)3 Network Server Group, Remote Display Processor (RDP) Cabinet, DCUs and Auxiliary Processing Cabinet (APC), resolution of design deficiencies and conduct of design reviews Critical Design Review (CDR). Three (3) months after completion of CLINs 0003, 0006 and 0009, the Contractor shall deliver a Level III Technical Data Package (TDP) which will be incorporated into Section J, Attachment J-8. Additionally, all contract deliverables for Integrated Logistics Support, Reliability and Maintainability, Configuration Management, etc. shall be delivered under these CLINs.

CLINs 0002, 0005 and 0008 – After successful completion of the CDR, the Contractor shall manufacture and support first article requirements as defined in this Statement of Work and the requirements detailed in Attachment J-2. This CLIN will be used to conduct all production activities associated with FAU manufacturing. The activities completed under this CLIN shall be the basis for determination of test readiness.

CLINs 0003, 0006 and 0009 – The Contractor shall support as directed by the government,) Environmental Qualification Testing (EQT) and shall develop production acceptance test procedures for TI 16 OL-798(V)3 Network Server Group, Remote Display Processor (RDP) Cabinet and Auxiliary Processing Cabinet (APC) configurations. The contractor shall complete the Test Readiness Review (TRR) under this CLIN. Testing shall be done in accordance with the SOW, Attachment J-2, and government approved CDRLs (A017 - Test Plan/Test Procedures: Production Acceptance Test (PAT) Procedures; A018 - EQT Test Report.)

CLIN 0010– The Contractor shall provide the necessary labor to support the engineering services. The specific tasks shall be defined in each Delivery Order.

CLIN 0011,– The Contractor shall provide all parts and material to support CLINs 0010 in accordance with this Statement of Work.

CLINs 0012– The Contractor shall provide all other direct costs/travel to Support CLINs 0010 in accordance with this Statement of Work.

CLINS 0013, 0014, 0015- The Contractor shall manufacture, test and deliver NSG(V)3, RDP (with required DCUs) and APC fully qualified Production Units that reflect the baseline after completion of design (CLINs 0001, 0004 and 0007), manufacture (CLINs 0002, 0005 and 0008), and qualification (CLINs 0003, 0006 and 0009) of First Article Units (FAUs) by the delivery date stated in Section F. The contractor shall conduct a formal Production Readiness Review (PRR) prior to the exercise of this CLIN. These CLINs shall include delivery of hardware.

CLIN 0020 - Provisioned Item Orders will be established in accordance with the Statement of Work. The supplies or services shall be identified in each Delivery Order.

CLIN 0021– The Contractor shall test and deliver new or repaired spare parts. Spares pricing will be negotiated and priced after completion of the design, but no later than the end of option year one, which will be incorporated into Section J, Attachment J-9. The spares shall be identified in each Delivery Order.

SECTION C-2 STATEMENT OF WORK

1.0 INTRODUCTION (Applicable to all CLINs)

The Ship Self Defense System (SSDS) is installed in carrier and amphibious ship classes: CVN 68 class, CVN 78 class, LPD 17 class, LHD 1 class, LHA class, and LSD 41/49 classes.

The TI 16 SSDS Mk 2 is the next evolution in the SSDS ICS and shall consist of the TI-16 Air-Cooled Processing and Storage System (PS2), the TI-16 Common Display System (CDS), the TI 16 OL-798(V)3 Network Server Group (NSG(V)3), Remote Display Processor (RDP) Cabinet and Auxiliary Processing Cabinet (APC) and ancillary equipment. The Air-Cooled PS2 and the TI-16 CDS will be procured via NAVSEA Enterprise Production Contracts; the ancillary equipment will be procured via current Indefinite Delivery-Indefinite Quantity (IDIQ) contracts managed by NSWC Dahlgren Division. The NSG(V)3 provides network switching and boundary defense capabilities, the RDP provides remote display capability to the Command and Control Group consoles and the APC provides maintenance capability and interfaces to sensors; details are in the requirements in Attachment J-2. The Contractor shall design, develop, test, qualify and produce TI 16 NSG(V)3, RDP and APC. First Article Units (FAUs) shall be produced, tested and qualified and the Contractor shall demonstrate production readiness prior to entering into full rate production in accordance with the requirements documents listed in Attachment J-2.

The Contractor shall design, develop, test, qualify, produce, deliver and support the TI 16 SSDS equipment (NSG(V)3, RDP and APC) in accordance with this statement of work (SOW) and requirements documents referenced therein. Initial contract deliverables for Integrated Logistics Support (ILS), Reliability and Maintainability (R&M) and Configuration Management (CM), etc. shall be included in the design CLINS, 0001, 0004 and 0007. Updates to these contract deliverables shall be included in production CLINs 1001, 1002, 1003, 2001, 2002, 2003, 3001, 3002, 3003, 4001, 4002 and 4003.

In order to support production unit deliveries in July 2017, the Contractor shall develop a TI 16 SSDS Component Program Schedule to accomplish the milestones and events listed below. Milestones and events can be combined, as necessary and appropriate, in order to accomplish production unit delivery in July 2017.

Key Program Milestone Event Preliminary Design Review (PDR) (CLINs 0001, 0004, 0007) Critical Design Review (CDR) (CLINs 0001, 0004, 0007) Incremental Progress Review (IPR) #1(CLINs 0001, 0004, 0007) First Article Unit (FAU) (CLINs 0002, 0005, 0008) Test Readiness Review (TRR) (CLINs 0003, 0006, 0009) Incremental Progress Review (IPR) #2(CLINs 0001, 0004, 0007) Environmental Qualification (CLINs 0003, 0006, 0009) Production Readiness Review (PRR) (CLINs 0001, 0004, 0007) Production Deliveries (CLINs 0013, 0014, 0015)

2.0 APPLICABLE DOCUMENTS (Applicable to all CLINs)

The following documents are applicable to the tasks herein and are for use by the Contractor as general guidance in the fulfillment of the Statement of Work as required.

2.1 Government Documents

See Section J

2.2 Military Standards

MIL-STD-2073-1E

w/CHANGE 1

2.3 DoD/DON Regulations, Directives and Instructions

2.4 RESERVED

2.5 SECNAV and OPNAV Instructions and Memoranda

2.6 NAVSEA and PEO IWS, NSWC DD AND CDSA DAM NECK Regulations, Directives and Instructions

2.7 Military Handbooks and DoD Guidance

2.8 Non-Government Documents

2.9 RESERVED

2.10 Availability of Documents (Applicable to all CLINs)

Copies of military handbooks, instructions, standards and specifications and DoD adopted non-Government standards may be obtained in accordance with Federal Acquisition Regulation (FAR) Subpart 52.211-2. Copies of specifications, standards and data item descriptions cited in this solicitation, if listed in the DoD Index of Specifications and Standards (DoDISS) or the Acquisition Management Systems and Data Requirements Control List, DoD 5010.12-L (Dec 2003) may be obtained from:

1. ASSIST database via the Internet at https://assist.daps.dla.mil/;

1. DoD issuances (http://www.dtic.mil/whs/directives)

1. DON issuances (http://doni.daps.dla.mil/default.aspx)

1. PEO IWS, NSWC DD AND CDSA Dam Neck, documents are included in the Government Furnished Information (GFI) Attachment J-2.

1. By submitting a request to the Department of Defense Single Stock Point (DoDSSP) Building 4, Section D 700 Robbins Avenue Philadelphia, PA 19111-5094

1. Naval Systems Data Support Activity (NSDSA) website at: https://nsdsa2.phdnswc.navy.mil/

Copies of non-Government publications not listed in the DoDISS may be obtained from the respective industry association.

2.11 SOW Order of Precedence

In the event of conflict between the documents referenced herein and the contents of this SOW, the contents of this SOW shall be considered the superseding requirement. See Section C Clause FAR 52.215-8 Order of Preference.

3.0 REQUIREMENTS (Applicable to all CLINs)

This Contract will provide for the design, development, test, qualification, production, delivery and support of TI 16 SSDS Principal Component equipment and software in accordance with this Statement of Work (SOW), the SSDS TI 16 NSG(V)3 Critical Item Development Specification (CIDS), the SSDS TI 16 RDP CIDS, and the SSDS TI 16 APC CIDS and preliminary government designs provided as GFI in the form of Autodesk Inventor (Version TBD) mechanical engineering models, AutoCAD (version TBD) and other engineering drawings. For the purposes of this document, the term “SSDS TI 16 equipment” is used to refer to systems, kits, parts, spares, units, products, and all other deliverable hardware and software associated with this SOW.

3.1 Program Management (Applicable to all CLINs)

The Contractor shall communicate and document its plans, processes and approaches to meet all program requirements. The Contractor shall use a metrics-based management approach for planning, scheduling and technical, cost, risk, and quality monitoring/reporting with program-wide visibility of plan versus actual efforts under this contract. The Contractor shall establish and maintain a Program Management Plan (CDRL A001) that ensures all work associated with this contract is clearly and concisely demonstrated and meets all technical objectives within the Contractor’s established cost and schedule baseline. The Program Management Plan shall include appropriate metrics and tracking processes to allow clear visibility into the program and ensure program milestones are met within cost and schedule constraints.

Deliverable Data Item (See DD-1423):

CDRL A001: “Program Management Plan”

In support of the Program Management effort, the Contractor shall:

a. Support PEO IWS, NSWC DD and CDSA Dam Neck as directed, in completing Acquisition requirements and design and technical reviews of the acquisition process under DoD 5000 instructions.

b. Participate in Government led Integrated Product Team (IPTs) and Working Integrated Project Team (WIPTs), conferences, executive and working level meetings.

c. Provide project data and information as well as assistance to PEO IWS, NSWC DD and CDSA Dam Neck, as directed, for the management of the Integrated Master Schedule (IMS) in accordance with CDRL A002, Integrated Program Management Report (IPMR).

d. Support management of financial controls including Other Direct Costs (ODCs) and risks.

e. Perform quality assessment, subcontracting, issue resolution, and human resource management activities.

f. Support and document scheduled program briefings. (CDRL A006)

g. The Contractor’s Program Manager shall meet and communicate with the NSWC DD and CDSA DN SSDS Program Manager and Technical Director, Technical Leads, Contracting Office’s Representative (COR), and other designated representatives on a regular basis (not less than once a month).

h. The Contractor shall prepare and deliver monthly the Contractor’s Progress, Status, and Management Report, including funding levels per CDRL A003. As part of CDRL A003, the report shall include a section that notes deficiencies in any Government Furnished Information (GFI) or equipment to meet requirements of this contract.

i. The Contractor shall support the design review process and conduct reviews in accordance with the PEO IWS/NAVSEA 05H Technical Review Manual (TRM).

j. The Contractor shall make available to Government personnel through its secure Integrated Data Environment (IDE) all data used on or produced in support of this contract. Data shall be protected in accordance with approved Program Protection Plans and Information Assurance guidelines. The Government reserves the right to witness all Contractor efforts to accomplish the SOW requirements and maintains the right to comment on processes. The Contractor shall provide thirty (30) days advance notice of any events, tests, or activities.

k. The Contractor shall establish and maintain Government controlled Sharepoint accounts to transfer data with the NSWC Dahlgren Division data sites and other data transfer accounts for unclassified data.

l. The Contractor shall provide and maintain office space collocated at the contractor’s facilities and related services generally equivalent to those provided to the Contractor’s staff for similar purposes for two (2) positions beginning within sixty (60) days of contract award and remain in place while projects are active or open (until completion of final deliverable). At a minimum, the contractor shall provide desks, chairs, working computing equipment, internet access, and access to filing space, conference facilities, working printing equipment, faxing equipment, and environmental security for these 2 positions.

Deliverable Data Item (See DD-1423):

CDRL A002: “Integrated Program Management Report (IPMR)”

Deliverable Data Item (See DD-1423):

CDRL A003: “Contractor’s Progress, Status and Management Report”

3.1.1 Program Manager (Applicable to all CLINs)

The Contractor shall designate a full-time Program Manager (PM). The PM shall have complete responsibility for the planning, execution, and control of all aspects of this contract, and for directing in-house and subcontractors’ efforts in the areas of design prototyping, documentation, test and evaluation. The PM shall ensure all work conducted within this contract is planned and executed in a manner that achieves all management, technical, logistics, budget, and schedule objectives. The PM may have specific task managers and shall ensure that the necessary controls of in-house equipment, development, production and support efforts are appropriately applied (e.g., design reviews, reliability and maintainability, safety program, quality assurance, configuration management, integrated logistics support, financial management, and subcontract management).

The PM shall have the necessary authority to utilize the company’s resources to assure the SOW is accomplished. The PM shall be authorized to deal directly with either NSWC DD or CDSA DN, as directed, or designated representative on all matters pertaining to this contract.

3.1.2 Integrated Master Schedule (Applicable to all CLINs)

The Contractor shall develop and maintain an Integrated Master Schedule (IMS) for the SSDS TI 16 Principal Components. The schedule shall include all major design reviews (e.g., Preliminary Design Review (PDR), Critical Design Reviews (CDR)), qualification(s), test events, ILS product development reviews (e.g., Interactive Electronic Technical Manual (IETM) source data development, reviews, and deliveries), validations (e.g., eXtensible Markup Language (XML) view package for the IETM), verifications, audits (e.g., FCA, PCA), and associated data deliverables. (CDRL A002)

3.1.3 Program Management Meetings and Technical Reviews (Applicable to all CLINs)

a. Post Award Kick-off Meeting - The Contractor shall provide a detailed briefing on its management and contract execution strategy at the Post-Award Kick-off Meeting to be held within two (2) weeks of contract award. The Contractor shall plan for a one-day Post Award Kick-off Meeting. As options are executed, the Government reserves the right to conduct additional kick-off meetings.

b. Program Management Reviews - The Contractor shall conduct monthly Program Management Reviews (PMRs) prior to the Production Readiness Review (PRR). The PMRs, which may be conducted via WebEx or other Government-approved means, shall be documented with conference agendas, conference minutes, and presentation materials per CDRLs A004, A005, and A006. The purpose of the reviews is to ensure that the approach and progress are technically sound, meet the requirements, and are properly documented in the design documentation. Minutes of meetings shall be delivered via CDRL A005 or via electronic mail for all meetings that had a formal agenda. The Program Management Reviews shall include the following:

1. Ensure a mutual understanding of the objectives and scope of the work

2. Address Technical Instructions

3. Review progress to-date

4. Review metrics

5. Review project deliverables

6. Validate detailed work plans

7. Confirm resolved issues and manage outstanding issues. This shall include status of significant problems faced by the program manager and current plans to resolve the problems or mitigate their impacts

8. Identify and evaluate risk factors and address areas where risk has changed

9. Identify cost and schedule variance in a combined manner by graphing the normalized cost and schedule variance together on an X-Y plot for all Work Breakdown Structure (WBS) elements at the third indenture level. The presentation should identify with unique colors or shapes the data points that are considered “out of tolerance” per the Cost Performance Report (CPR) reporting criteria

10. Identify problems with Government Furnished Information or Equipment, impacts, and work around plans or solutions

11. Report on the status of ESOH hazards, Configuration Management activities, design issues and engineering issues that impact system supportability, Post PRR, Program Reviews shall be conducted in accordance with the requirements of Production Program Reviews specified below

c. Technical Reviews - Technical Reviews shall be scheduled in the IMS and shall be coordinated with PMRs. Design artifacts shall be disclosed throughout their development via the Contractor Integrated Data Environment (IDE) or other electronic media, as mutually agreed upon with the Government. Formal review of technical packages shall be electronically uploaded into the secure network specified by the Government in accordance with the applicable CDRL A006. Management, cost, and schedule data shall be presented at reviews and then electronically uploaded in accordance with the applicable CDRLs (A002 and A006) to document meetings and discussions. Materials in support of Technical Reviews shall be prepared in accordance with the PEO IWS/NAVEA 05H TRM.

d. Integrated Baseline Review (IBR) (Applicable to CLINs 0001, 0002, 0004, 0005, 0007, 0008) - The Contractor shall establish a performance measurement baseline of the Contract Work Breakdown Structure (CWBS) within 45 days of contract award. The Contractor shall work with the Government team to conduct an IBR for the purpose of evaluating the risks inherent in the contract’s planned performance measurement baseline within four (4) months (120 calendar days) of contract award. The IBR shall verify that the Contractor is using a reliable performance measurement baseline which includes the entire scope of the effort, is consistent with contract schedule requirements, and has adequate resources assigned. The Contractor shall lead the subcontractor IBRs, as needed, with active participation by the Government. See DFARS 252.234-7002.

e. Integrated Product and Process Development - The Contractor shall support and collaborate with the Government, other Contractors, and other applicable organizations in the performance of the efforts of this contract. The Contractor is expected to fully support the Navy Review Team (NRT) and Integrated Project Team (IPT) processes. The Contractor shall participate in the applicable Working Groups, IPTs, and Boards and shall prepare reports, minutes, and materials of these events in accordance with the CDRLs A004, A005, and A006. Contractor participants shall be subject matter experts in the appropriate areas and have sufficient decision making authority to expedite process and product changes within the scope and terms of this contract. Efforts are expected to include activities such as contributing to meetings, preparation of presentation material, providing subject matter expertise, sharing of pertinent technical data and work products, sharing of cost data (as appropriate) and performing design analyses and trade studies for the respective Contractor’s area(s) of responsibility. Participation in IPTs and Contractor-led chartering of new IPTs shall require prior written government authorization. All IPTs shall deliver work products to Government.

f. Production Program Reviews - The Contractor shall conduct quarterly program reviews, beginning three (3) months after PRR approval, to assess the Contractor’s progress and status. Production Program Reviews shall include as a minimum:

1. Organization Overview, including organization structure, SSDS TI 16 principal component Program structure, and facilities overview

2. Operations Overview, including current status of contract, IMS, procurement schedules, delivery schedules, production issues, supplier issues and risks.

3. Quality Overview, including Quality Organization, MRB and supplier escapes, internal defects, internal Escapes, failure data for system burn-in and acceptance test and field failure data.

4. Engineering Overview, including a summary of Engineering tasking, ECPs, and DMSMS forecasting and resolution

5. Logistics Overview, including status of technical documentation, operational issues, material support issues and lifecycle issues.

6. Contracts Overview including Outstanding Contract Actions, Upcoming Contract Actions and Proposed Contract Actions:

Deliverable Data Item (See DD-1423):

CDRL A004: “Conference Agenda”

Deliverable Data Item (See DD-1423):

CDRL A005: “Conference Minutes”

Deliverable Data Item (See DD-1423):

CDRL A006: “Presentation Material”

3.1.4 Contract Work Breakdown Structure (Applicable to all CLINs)

The Contractor shall develop, deliver, and maintain a CWBS in accordance with MIL-HDBK-881C. The CWBS shall be an essential reference document for planning, controlling, and reporting requirements. The Contractor shall ensure traceability of subcontractor data supporting the prime CWBS. This CWBS shall be used to develop, maintain and report all financial information related to efforts on this contract. (CDRL A007) Deliverable Data Item (See DD-1423):

CDRL A007: “Contract Work Breakdown Structure”

3.1.5 Cost Performance Report (Applicable to CLINs 0001, 0002, 0003, 0004, 0005, 0006, 0007, 0008, 0009, 0013, 0014, 0015)

The Contractor shall deliver a Cost Performance Report (CPR) to the Government per the IPMR, CDRL A002. The CPR presents data for measuring contract cost and schedule performance. For each CWBS element, the CPR shall identify the original contract budget allocation, budgeted and actual expenditures to date, and estimated cost at contract completion. Overrun and under-run cost and schedule conditions shall be provided for each element as a variance relative to budget. Recurring and non-recurring costs shall be presented separately, where applicable. The CPR shall clearly distinguish the performance data associated with each CLIN. Variance analysis thresholds shall be set at the IBR for CLINs 0001, 0002, 0004, 0005, 0007 and 0008 and approved by the Navy; subsequent adjustments shall be made on a quarterly basis as required and approved by the Navy.

3.1.6 Earned Value Management System (CLINs 0001, 0002, 0004, 0005, 0007, 0008, 0010-0012)

The Contractor shall be responsible for the development, execution, and maintenance of an Earned Value Management System (EVMS) to be implemented on this contract. This system shall comply with industry standard ANSI/EIA publication ANSI/EIA 748-1998, Earned Value Management System and EVMS Criteria Mandatory Procedures and Reporting requirements of DoD 5000.2-R, Appendix IV, per (CDRL A002).

3.1.7 Program Management Metrics (Applicable to all CLINs)

The Contractor shall develop and propose program management metrics for program management including cost, schedule, and performance. These proposed program management metrics shall be presented at the Preliminary Design Review. The Contractor shall report these metrics in the Contractor’s Progress, Status, and Management Report. (CDRL A003)

3.1.8 Risk Assessment and Management (Applicable to all CLINs)

The Contractor shall establish and maintain a formal risk management program in accordance with the PEO IWS, Instruction 3058.1 Risk Management., to include risk identification, risk assessment, risk ranking, risk trends, risk mitigation and risk monitoring. Risk metrics shall be generated in accordance with PEO IWS Instruction 3058.1, Risk Management, and reported as part of the Contractor’s Progress, Status and Management Report (CDRL A003) and during program reviews. The Contractor’s risk report shall include, as a minimum, the following:

a. Identification of the risk areas

b. Assessment of identified risks, including a relative ranking by program impact

c. Definition of methods or alternatives to mitigate each risk, including the identification of criteria upon which to base programmatic decisions

d. Human, hardware, and software performance analysis and tradeoffs impacted/considered during risk analysis

e. Status of resolving/mitigating identified risks

3.1.9 Data Management (CLINs 0016, 0017, 0018 and 0019)

The Contractor shall post contract data and applicable deliverables to a Government specified website, unless otherwise specified on the applicable Contract Data Requirements List (CDRL) DD Form 1423-1. The Contractor shall provide electronic-mail (e-mail) notification to the Contracting Officer's Representative (COR) and other Government personnel identified on the CDRL Addressee List within 24 hours of CDRL delivery (posting new/revised information and CDRL deliverable(s) on the website or delivering as specified on the associated DD Form 1423-1).

The Contractor shall provide a Contract Status Deliveries Report (CDRL A008). This report shall include the status of each data deliverable required by this contract, including contract identification, shipping/transmittal data, acceptance status, security classification and scheduled due date information.

Deliverable Data Item (See DD-1423):

CDRL A008: “Status Report: Contract Deliveries Status”

3.1.10 Formal Proposals, Rough Orders of Magnitude (ROM), and Technical Instructions (TIs) (Applicable to CLIN 0010)

Formal proposals for delivery orders shall be prepared and submitted only in response to requests received from the Contracting Officer or duly authorized representative. Contractor proposals shall include all costs, including material costs, technical costs and man-hour estimates, required to complete tasking provided via delivery order. 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. (Man hour Estimates and Technical Cost Proposals, CDRL A009)

Deliverable Data Item (See DD-1423):

CDRL A009: “Man Hour Estimate and Technical Cost Proposals”

The Government may request Rough Orders of Magnitude (ROM) estimates in support of program efforts not included in the completion scope of this contract. Unless otherwise agreed to by the Government, ROM estimates shall be submitted within fifteen (15) calendar days of the request. Incomplete or unknown information shall be identified within three (3) business days and concurrence obtained from the Contracting Officer Representative (COR), to preclude delays. These ROM estimates are not contractually binding. Upon COR approval and signature of the ROM, the Contractor shall provide a TI that details the efforts associated with the work to be accomplished. The Contractor must obtain written COR approval prior to expending any effort associated with the proposed TIs or proposed TI scope modifications.

3.1.11 End of Contract Transition Planning (Applicable to all CLINs)

The Contractor shall develop an End of Contract Transition Plan that addresses the long-term support requirements of all TI 16 SSDS equipment procured under this contract, as support agent responsibility transitions from the Contractor. This plan shall describe how the Contractor would transition the follow-on support of TI 16 SSDS equipment to a third party. (CDRL A010)

Deliverable Data Item (See DD-1423):

CDRL A010: “Technical Report – Studies/Services: End of Contract Transition Plan”

3.2 Systems Engineering (Applicable to all CLINs)

3.2.1 General Systems Engineering Requirements (Applicable to all CLINs)

The Contractor shall: (1) perform system engineering to design, develop, test, qualify, produce, deliver and support the SSDS TI 16 equipment ; (2) provide subject matter expertise to the PEO IWS 10 Major Program Managers (MPMs), NSWC DD and CDSA DN, as directed, for SSDS TI 16 Product Lines; (3) support DoD data architecture strategy and create or support Community Of Interest (COIs) to develop Navy enterprise data architecture and strategy in each technical capability area, and (4) document studies and investigations per CDRL A011.

Deliverable Data Item (See DD-1423):

CDRL A011: “Technical Report – Studies/Services: Engineering Studies and Investigations”

The Contractor’s systems engineering activities shall ensure SSDS TI 16 equipment meet the requirements of Attachment J-2. The Contractor shall establish performance standards, analyze overall SSDS TI 16 equipment performance, evaluate competing alternatives, negotiate interface designs, and integrate Government directed modifications into the SSDS TI 16 equipment.

The Contractor shall provide systems engineering analysis in order to enhance reliability and maintainability of SSDS TI 16 equipment. The Contractor shall evaluate Fleet problems, provide recommended solutions to the Navy, and implement enhancements when tasked by the Government. The Contractor shall brief the Navy on problems identified to them and the recommended solutions, including risk assessment and cost estimates.

The Contractor shall validate modular interface specifications as necessary to support integration with user computer programs and equipment. The contractor shall ensure interoperability of the SSDS TI 16 equipment with the parent system, (element, weapon or full combat system). The contractor shall provide all documentation such as, but not limited to, driver information, physical connection information and physical layout of internal components to users as necessary to support integration with user systems and generation of final user support documentation. The contractor shall provide technical integration and engineering support to Capability Developers and System Integrators, both internal to the SSDS TI 16 equipment Developer as well as Component Development Contractors funded by the Government under separate contracts. This support shall be used to ensure all SSDS TI 16 equipment functional issues are resolved prior to full combat system delivery to ships or shore facilities.

3.2.1.1 Coordination, Review Team & IPT Support (Applicable to all CLINs)

The Contractor shall conduct SSDS TI 16 equipment-related system engineering efforts and contribute to Navy-led Interface Control Working Groups (ICWGs) and government combat system product line working groups to identify and recommend Combat System interface changes required to implement and deliver a fully integrated SSDS TI 16 Combat Management System.

3.2.2 Open Systems Approach (Applicable to all CLINs)

The Contractor shall define, document, and follow an open systems approach utilizing modular design and standards-based interfaces. The Contractor shall present the open systems plan to the Government at all design reviews. The design approach characteristics shall be utilized, as defined below.

3.2.2.1 Open Architecture (Applicable to all CLINs)

The Contractor shall use an architecture that incorporates portability, maintainability, interoperability, upgradeability, transportability, and long-term supportability. The architecture shall be layered and modular. The system design shall make maximum use of Commercial-Off-The-Shelf (COTS)/ Non-Developmental Item (NDI) hardware, operating systems, and middleware.

3.2.2.2 Open Modular Design (Applicable to all CLINs)

The Contractor shall use a modular design. Modules shall consist of components that are self-contained elements with well-defined interfaces. The design shall minimize inter-component dependencies to ensure that components can be decoupled and reused.

The Contractor shall provide the rationale for the modularization choices made to generate the design. The Contractor’s rationale shall explicitly address any tradeoffs performed, particularly those that compromise the modular and open nature of the system. These designs shall be documented and modeled using industry standard formats, (e.g., Unified Modeling Language (UML)), and using tools that are capable of exporting model information in a standard format (e.g., XML Metadata Interchange (XMI)). The Contractor shall ensure that all requirements are accounted for by tracing them to one or more modules.

3.2.2.3 Interface Design and Management (Applicable to all CLINs)

The Contractor shall clearly define the component and system interfaces. The Contractor shall define and document all subsystem and configuration item level (CI) interfaces to provide full functional, physical and electrical specifications. Interfaces shall include, but not be limited to, mechanical, electrical (power and signal wiring), software, firmware, and hardware.

If applicable, interfaces shall be selected from existing commercial or Government standards. Selection of interfaces shall be driven by the need to:

a. Maximize the ability of the system to easily accommodate technology insertion (both hardware and software)

b. Facilitate the insertion of alternative or reusable modular system elements

c. Minimize future integration and testing costs for upgraded elements

3.2.2.4 Treatment of Proprietary Elements (Applicable to all CLINs)

The Contractor shall identify and justify the use of proprietary or closed interfaces, code modules, hardware, firmware, or software. For those portions of interfaces, hardware, firmware or modules that are proprietary, the Contractor shall employ hardware and/or software partitioning or other design techniques to isolate the proprietary portions from the rest of the system.

The integration of closed or proprietary equipment, interfaces, data systems or functions due to a unique or specific system requirement shall not force additional closed system or proprietary equipment, interfaces, data systems or functions in the remaining components integration. It is the Contractor’s responsibility to protect the open elements of the system from being intertwined with the proprietary elements.

3.2.2.5 Open Business Practices (Applicable to all CLINs)

The Contractor shall demonstrate that the modularity of the system design promotes the identification of multiple sources of supply and/or repair for each Lowest Replaceable Unit (LRU), and supports flexible business strategies that enhance subcontractor competition. The Contractor shall identify any pre-existing alternative for solutions they have proposed to custom build. The Contractor shall identify those pre-existing items it intends to reuse and provide the Government with data that clearly shows the alternative solutions meets performance requirements and cannot be purchased using normal COTS vendors. Exceptions to reuse must be accompanied by justification, such as cost, schedule, etc., and must be approved by the Program Office prior to inclusion into the design.

3.2.2.6 Peer Review Rights (Applicable to all CLINs)

The Government intends to procure open architectures, designs, and corresponding software components. For designs or software for which the Government has Government Purpose Rights (GPR) as defined at DFARS 252.227-7013, the Government intends to conduct third party reviews on an ongoing basis.

3.2.2.7 Technical Insertion Method (Applicable to CLINs 0013-0015)

The Contractor’s architectural approach shall provide a viable technology insertion and refresh process.

3.2.2.8 Prioritization of Standards (Applicable to CLINs 0013-0015)

In accomplishing the above, the Contractor shall use the standards identified in this contract.

a. Standards as specified within the contract

Standards that are not specified within this contract must be approved by the Government prior to their use.

3.2.2.9 Open Architecture Interfaces (Applicable to all CLINs)

The Contractor shall profile SSDS TI 16 principal component OA interfaces and data using the Open Architecture Assessment Tool (OAAT). The Contractor shall consider PEO IWS, Open Architecture Computing Environment Design Guidance and Open Architecture Computing Environment Technologies and Standards. The OAAT is available in the tools section of the Defense Acquisition University (DAU) Acquisition Community Connection (ACC) at https://acc.dau.mil/oa. (CDRL A012) Deliverable Data Item (See DD-1423):

CDRL A012: “Scientific and Technical Reports: Open Architecture Assessment Tool”

3.2.3 Modular Open Systems Approach (MOSA) (Applicable to all CLINs)

The Contractor shall use a modular open systems approach (MOSA) to evaluate the appropriateness of implementing a modular design strategy for building systems in accordance with Under Secretary of Defense Memorandums: Amplifying DoDD 5000.1 Guidance Regarding Modular Open Systems Approach (MOSA) Implementation and Instructions for Modular Open Systems Approach (MOSA) Implementation.

A primary consideration in selection of equipment to meet the design functionality shall be the impact to the overall modular open systems architecture. A modular open systems approach and analysis of long term supportability, interoperability, and growth for future modifications shall be major factors in the Contractor’s final selection of equipment and integration approach. The architectural approach shall provide a viable technology insertion methodology and refresh strategy that supports application of a modular open systems approach and is responsive to changes driven by mission requirements and new technologies. The Contractor shall maximize commonality of components used in TI 16 SSDS equipment across all product baselines. The Contractor shall develop metrics to measure the degree of success in achieving commonality goals. The Contractor shall report the degree of commonality success at program and design reviews.

3.2.4 Human Systems Integration (HSI) (Applicable to all CLINs)

The Contractor shall incorporate the Human Engineering Design Criteria Standard (MIL-STD-1472G), the Standard Practice for Human Engineering Program Requirements for Ships and Marine Systems, Equipment, And Facilities (ASTM F1337-91) into the HSI design of TI 16 SSDS equipment. HSI analyses and tradeoffs shall be reported at all technical reviews.

The Contractor shall work with the Government HSI team to schedule and conduct joint assessments to validate and verify the adherence to MIL-STD-1472G as well as verify closure of HSI related action items from formal technical reviews.

The Contractor shall maintain a human factors documentation file in accordance with ASTM F1337-91. The file shall be available for Government review.

3.2.5 Environmental, System Safety, and Occupational Health (ESOH) (Applicable to all CLINs)

The Contractor shall develop and deliver an Environmental Health and Safety Plan (HSP) that establishes a process to identify, track and resolve ESOH hazards. The Contractor shall track potential hazards in an ESOH database. Each hazard tracking record shall, at a minimum, contain:

The Contractor shall report ESOH hazards and status of resolution in the Contractor’s Progress, Status and Management Reports (CDRL A003) and at all Design Reviews and Program Reviews. The ESOH database shall be available for Government review.

3.2.5.1 Systems Safety Program (Applicable to all CLINs)

The Contractor shall develop and deliver a System Safety Program Plan (SSPP), and develop, establish and implement a System Safety Program using MIL-STD-882E as guidance. Hazards associated with production, operation, maintenance and handling of the TI 16 SSDS equipment shall be identified, reported, and eliminated. Hazards that cannot be eliminated shall be dispositioned to the satisfaction of the Government.

The Contractor shall report real and potential safety hazards associated with the TI 16 SSDS equipment program using a System Safety Hazard Analysis (SSHA) report. The Contractor shall track system safety issues in the ESOH database, identify processes and methodologies to mitigate these hazards, and implement them within the program. The Contractor shall resolve all safety issues reported by the Government.

3.2.5.2 Hazardous Materials Management/Pollution Prevention (Applicable to all CLINs)

Hazardous materials are materials or substances that, due to their chemical, physical, radiological or biological nature, cause safety, public health, or environmental concerns. The Contractor shall eliminate (or minimize to the greatest extent possible) the use of hazardous materials in the design, development, qualification, and production of TI 16 SSDS equipment. The Contractor shall not use materials that are Class I or Class II Ozone Depleting Substances. The Contractor shall track hazardous materials that cannot be eliminated from the TI 16 SSDS equipment in the ESOH database and provide Material Safety Data Sheets (MSDS) for each hazardous item. (CDRL A013)

Deliverable Data Item (See DD-1423):

CDRL A013: “Material Safety Data Sheet (MSDS)”

3.3 Design, Development and Test Requirements (Applicable to CLINs 0001, 0002, 0003, 0004, 0005, 0006, 0007, 0008, 0009)

3.3.1 Design Reviews (CLINs 0001, 0004, 0007)

The Contractor shall conduct design reviews for SSDS TI 16 equipment in accordance with the requirements of this document and the PEO IWS/NAVSEA 05H TRM. Reviews for each component should be conducted as a single event with artifacts unique to each component clearly articulated unless otherwise dictated by the schedule or directed by the government Program Manager.

The Contractor shall meet the entrance and exit criteria as stated in the PEO IWS/NAVSEA 05H TRM for all design reviews. Tailoring of the requirements, including the entrance and exit criteria, in the PEO IWS/NAVSEA 05H TRM shall be approved by the government Program Manager prior to the review. For any review exit criteria not successfully achieved, the Contractor shall create a formal closure plan including schedule, resources and detailed technical plan for closure and gain Government approval prior to exiting the review.

3.3.1.1 Requirements Verification (CLINs 0001, 0004, 0007)

The Contractor shall develop a verification compliance matrix of data to reflect adherence to the CIDS requirements, including Open Architecture (OA) and Modular Open Systems Approach (MOSA) methodologies. The compliance matrix shall indicate how and when requirements were met during design, development, and qualification. The compliance matrix must be approved by the COR prior to exiting the design phase of this contract.

This matrix shall be approved by the Government prior to each major design review as identified in the PEO IWS/NAVSEA 05H TRM Technical Review Manual (TRM).

3.3.2 Preliminary Design Review (CLINs 0001, 0004, 0007)

The Contractor shall conduct a Preliminary Design Review (PDR) to address the requirements and preliminary design for SSDS TI 16 equipment. Proposed changes in requirements from the Government to the SSDS TI 16 NSG(V)3 CIDS, the SSDS TI 16 RDP CIDS and the SSDS TI 16 APC CIDS, and associated technical, cost, and schedule impacts shall be addressed. The Contractor shall meet the PDR entrance and exit criteria as stated in the PEO IWS/NAVSEA 05H TRM. In addition to the PDR exit criteria of the PEO IWS/NAVSEA 05H TRM, the Contractor shall provide the following at the PDR: