Attachments_J-1_through_J-13.pdf

ATTACHMENT J-1

STATEMENT OF WORK

FOR

UNMANNED INFLUENCE SWEEP SYSTEM (UISS)

July 2013

Department of the Navy Program Executive Officer (PEO) Littoral Combat Ships (LCS)

Program Management Office for Unmanned Maritime Systems PMS406

N00024-13-R-6312 Statement of Work for the Unmanned Influence Sweep System (UISS)

TABLE OF CONTENTS (CONTINUED)

ii

TABLE OF CONTENTS

1.0 SCOPE

1.1 System Overview

2.0 REQUIREMENTS

2.1 Deliverables

2.1.1 UISS EDM (CLIN 0001)

2.1.2 Provisioned Items Orders ((If option is exercised) CLIN 0002)

2.1.3 Engineering Services ((If options are exercised) CLINs 0003, 0100, 0202, 0302, and

0402)

2.1.4 Support for Engineering Services ((If options are exercised) CLINs 0004, 0101, 0203, 0303, and 0403)

2.1.5 UISS EDM Spares ((If option is exercised) CLINs 0005)

2.1.6 UISS Tools and Test Equipments ((If options are exercised) CLINs 0006, 0209, 0210, 0309, 0310, 0409, and 0410)

2.1.7 Data Requirements (CLIN 0007)

2.1.8 Technical Manuals (CLINs 0008)

2.1.9 Data Rights ((If option is exercised) CLIN 0010)

2.1.10 Training ((If options are exercised) CLINs 0102, 0204, 0304, and 0404)

2.1.11 UISS Production Unit ((If options are exercised) CLINs 0200, 0201, 0300, 0301, 0400, and 401)

2.1.12 UISS Training System ((If options are exercised) CLINs 0205, 0206, 0305, 0306, 0405, and 406)

2.1.13 UISS Production Option Spares ((If options are exercised) CLINs 0207, 0208, 0307, 0308, 0407, and 0408)

2.1.14 Data Requirements ((If option is exercised) CLIN 0211)

2.1.15 Reserved

2.1.16 Interactive Electronic Technical Manual (IETM) ((If option is exercised) CLIN 0213) 5

2.1.17 Reserved

2.2 Program Management (Applicable to all CLINs)

2.2.1 Work Breakdown Structure (WBS)

2.2.2 Subcontract Management

2.2.3 Risk Management

2.2.4 Integrated Product Team (IPT)

2.2.5 Working Groups (WGs)

2.2.6 Government Furnished Property (GFP)

2.2.7 Integrated Program Management Report (IPMR)

2.2.8 Contract Funds Status Report (CFSR)

2.2.9 Integrated Data Environment (IDE)

2.2.10 Information Assurance (IA)

2.2.11 Program Protection Implementation

for the Unmanned Influence Sweep System (UISS)

TABLE OF CONTENTS (CONTINUED)

iii

2.2.12 Electromagnetic Environmental Effects (E3)

2.3 Meetings, Conferences and Reviews (Applicable to all CLINs)

2.3.1 Meetings

2.3.1.1 Technical Interchange Meetings (TIMs) (Applicable to all CLINs)

2.3.1.2 Post Award Conference (PAC) (Applicable to CLIN 0001)

2.3.2 Reviews

2.3.2.1 Program Reviews (PR) (Applicable to all CLINs)

2.3.2.2 Integrated Baseline Review (IBR) (Applicable to CLIN 0001)

2.3.2.3 System Requirement Review (SRR) (Applicable to CLIN 0001)

2.3.2.4 Preliminary Design Review (PDR) (Applicable to CLIN 0001)

2.3.2.5 Critical Design Review (CDR) (Applicable to CLIN 0001)

2.3.2.6 Software CDR (Applicable to CLIN 0001)

2.3.2.7 Production Readiness Review (PRR) (Applicable to CLIN 0001)

2.3.2.8 Production Technical Design Review (TDR) (Applicable to CLIN 0200)

2.3.2.9 Test Readiness Review (TRR) (Applicable to all CLINs)

2.4 Systems Engineering (Applicable to all CLINs)

2.4.1 Modular Open System Architecture (MOSA), Compatibility, and Performance

2.4.2 System Engineering Management Plan (SEMP)

2.4.3 System Design Documentation (SDD)

2.4.3.1 Critical Item Product Functional Specifications (CIPFSs)

2.4.3.2 System/Subsystem Design Description (SSDD)

2.4.3.3 Specification Requirement Verification Matrix (SRVM)

2.4.3.4 Interface Control Document (ICD)

2.4.3.5 UISS System/Subsystem Specification

2.4.4 Weight Management

2.4.4.1 Weight and Stability Report

2.4.5 Command, Control, Communications, Computers (C4)

2.4.6 Engineering Analyses (Applicable to CLIN 0001)

2.4.6.1 Transportability

2.4.6.2 Hull and Structure

2.4.6.3 Resistance, Powering and Propulsion

2.4.6.4 Electrical Load Analysis and One-Line Diagram

2.4.6.5 Electrical Detail Design and Diagrams

2.4.6.6 Electronic Monitoring and Recording

2.4.6.7 Auxiliary Systems

2.4.6.8 Sweep System Design and Performance

2.4.6.9 Lifting Points and Slings

2.4.6.10 Tie-Down Fittings

2.4.6.11 Mooring and Tow Fittings

2.4.6.12 Trailer Calculations

2.5 Software Engineering (Applicable to all CLINs)

2.5.1 Software Product Specification (SPS)

for the Unmanned Influence Sweep System (UISS)

TABLE OF CONTENTS (CONTINUED)

iv

2.5.2 Software Development Plan (SDP)

2.5.3 Software Requirements Specification (SRS)

2.5.4 Software Design Description (SDD)

2.5.5 Interface Design Document (IDD)

2.5.6 Software Testing and Evaluation

2.5.6.1 Software Test Plan (STP)

2.5.6.2 Software Test Description (STD)

2.5.6.3 Software Code Walkthroughs

2.5.6.4 Software Test Report (STR)

2.5.6.5 Software Defect Tracking Database

2.5.7 Firmware Programming

2.5.8 Software Version Description (SVD)

2.5.9 Software Users Manual

2.5.10 Software Maintenance Document

2.6 Reliability, Availability, and Maintainability (RAM) Program (Applicable to all CLINs)

2.6.1 Reliability Prediction

2.6.1.1 Reliability Report

2.6.2 Failure Modes, Effects, and Criticality Analysis (FMECA)

2.6.3 Failsafes

2.6.4 Failure Reporting and Corrective Action System (FRACAS)

2.6.5 Reliability Growth

2.6.6 Maintainability

2.7 System Safety Program (Applicable to all CLINs)

2.7.1 System Safety Program Plan

2.7.2 System Safety Reviews/Audits

2.7.3 System Safety Working Group Support

2.7.4 Hazard Tracking System

2.7.5 System Requirements Hazard Analysis

2.7.6 System Hazard Analysis

2.7.7 Operating and Support Hazard Analysis

2.7.8 Health Hazard Analysis

2.7.9 Safety Assessment Report

2.7.10 Hazardous Materials Management Program (HMMP) and Pollution Prevention (P2) 37

2.7.11 HMMP Plan

2.7.12 HMMP Report

2.7.12.1 Material Safety Data Sheets

2.7.13 Environmental Compliance

2.7.14 Corrosion Prevention and Control Plan (CPCP)

2.8 Configuration Management (CM) (Applicable to all CLINs)

2.8.1 Configuration Baselines

2.8.2 Configuration Control

for the Unmanned Influence Sweep System (UISS)

TABLE OF CONTENTS (CONTINUED)

v

2.8.2.1 Engineering Change Proposals (ECPs)/ Requests for Deviation (RFD)

2.8.2.2 Specification Change Notices (SCNs)

2.8.2.3 Classified Data

2.8.3 Configuration Status Accounting

2.8.4 Functional Configuration Audit (FCA)

2.8.5 Physical Configuration Audit (PCA)

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

2.10 Integration (Applicable to all CLINs)

2.11 Test and Evaluation (T&E) (Applicable to all CLINs)

2.11.1 Master Test and Evaluation Program Plan (MTEPP)

2.11.2 Test/Inspection Documents

2.11.3 Test Readiness Reviews (TRR)

2.11.4 Tests/Inspections/Trials Administration and Conduct

2.11.5 In-Plant Tests/Demonstrations (Applicable to EDM CLINs Only)

2.11.6 In-Plant Inspections (Applicable to EDM CLINs Only)

2.11.7 Builder’s Trials (Applicable to EDM CLINs Only)

2.11.8 Pre-Delivery Inspection and Trials (PDIT) (Applicable to EDM CLINs Only)

2.11.8.1 Post Construction Inspection (PCI)

2.11.8.2 Dockside Trials

2.11.8.3 Maintenance Demonstration

2.11.8.4 Underway Testing (UT)

2.11.8.5 Post Underway Testing Inspection

2.11.9 Inclining Test (Applicable to EDM CLINs Only)

2.11.10 Post-Delivery Inspection (Applicable to EDM CLINs Only)

2.11.11 Sweep Performance Verification (Applicable to EDM and Production Option CLINs

2.11.12 Developmental Testing (DT) Support (Applicable to EDM CLINs Only)

2.11.12.1 LCS Integration Test

2.11.13 Acceptance Testing ((If options are exercised) Applicable to Production Option

CLINs Only)

2.11.13.1 Production Inspection and Trials

2.11.14 Initial Operational Test and Evaluation (IOT&E) Support ((If options are exercised) Applicable to Production Option CLINs Only)

2.12 Quality Assurance (QA) (Applicable to all CLINs)

2.13 Supportability and Integrated Logistic Support (ILS) (Applicable to all CLINs)

2.13.1 Logistics Management Information (LMI)

2.13.2 Training

2.13.3 Reliability Centered Maintenance (RCM) Analysis

2.13.4 Tools and Test Equipment

2.13.5 Supply Support

2.13.5.1 Diminishing Manufacturing Sources Material Shortages (DMSMS)

2.13.6 Parts Control and Standardization Program

for the Unmanned Influence Sweep System (UISS)

TABLE OF CONTENTS (CONTINUED)

vi

2.13.6.1 Item Unique Identification (IUID) and Valuation of Items

2.13.7 Spares

2.13.8 Packaging, Handling, Storage, and Transportation (PHS&T)

2.13.9 Facilities

2.13.10 Manpower

2.13.11 Technical Manuals

2.13.12 Interactive Electronic Technical Manuals

2.13.13 Technical Drawings

2.13.13.1 Commercial-Off-The-Shelf (COTS) and Non-Developmental Items (NDI) Drawings (Commercial Drawings)

2.13.13.2 Special Inspection Equipment (SIE) and Special Tooling (ST) Drawings

2.13.13.3 Source Control Drawing

2.13.14 UISS Drawing Tree

2.13.15 Technical Data Package (TDP)

2.13.16 Demilitarization (DEMIL) and Disposal

3.0 Security (Applicable to all CLINs)

4.0 Release of Information (Applicable to all CLINs)

for the Unmanned Influence Sweep System (UISS) vii

LIST OF APPENDICES

APPENDIX A ACRONYMS AND ABBREVIATIONS ........................................................ A-1 for the Unmanned Influence Sweep System (UISS)

1.0 SCOPE

This Statement of Work (SOW), attachments, exhibits, and appendices define the technical and management effort required for the Unmanned Influence Sweep System (UISS) procurement. This SOW is applicable to both the Engineering Development Model (EDM) and Production Units unless otherwise specified. The Production Units, Training Systems and other related option CLINs (0200, 0201, 0202, 0203, 0204, 0205, 0206, 0207, 0208, 0209, 0210, 0211, 0212, 0213, 0214, 0215, 0300, 0301, 0302, 0303, 0304, 0305, 0306, 0307, 0308, 0309, 0310, 0311, 0312, 0313, 0400, 0401, 0402, 0403, 0404, 0405, 0406, 0408, 0409, 0410, 0411, and 0412) are subject to the conditions set forth in Attachment J-13, Selection Criteria for Exercise of Production Options.

UISS consists of the following subsystems: UISS Mission System (an Unmanned Surface Vehicle (USV), an Influence Sweep System, Command, Control, Communications, and Computer (C4)), UISS Support Equipment (Diagnostic Support Device (DSD), Trailer, Stowage Cradle Bunk Pads, Man-Portable Control Unit (MPCU)), UISS Tools and Test Equipments, and UISS Spares. This requires the Contractor to design, procure materials, manufacture, assemble, integrate, inspect, test, and deliver the EDM and Production Units. The EDM and Production Units efforts encompass:

• All analysis, system engineering and design, development, fabrication, assembly, testing, qualification, training, documentation, planning, and management.

• All materials, software, and services necessary to ensure the successful integration and employment of UISS aboard the Littoral Combat Ships (LCS). The Contractor shall provide all material and software except for those provided as Government Furnished Property (GFP) for performance and incorporation via Attachments J-6 and J-7, respectively.

The end product of this effort shall be a fully tested and operational UISS that meets or exceeds Attachment J-2, UISS System Requirements Document (SRD) and Attachment J-3, System Specification, developed by the Contractor in accordance with (IAW) SOW 2.4.3.5.

1.1 System Overview

The UISS Program will satisfy the U.S. Navy's need for a rapid, wide-area coverage mine clearance capability, required to neutralize magnetic/acoustic influence mines. UISS will target acoustic, magnetic, and magnetic/acoustic combination mine types only. UISS will be an integrated magnetic/acoustic minesweeping asset that will provide the required capability to execute magnetic and acoustic influence minesweeping operations deployed from the LCS.

for the Unmanned Influence Sweep System (UISS)

2.0 REQUIREMENTS

2.1 Deliverables

2.1.1 UISS EDM (CLIN 0001)

The Contractor shall provide all labor, materials, and facilities to design, fabricate, procure, assemble, integrate, test (including Developmental Testing (DT) support) and deliver a fully functional UISS, meeting the contractual requirements as defined in this SOW, Attachment J-2, UISS SRD, dated 3 July 2013, and Contractor Developed Attachment J-3, System Specification and including all appendices thereto. The UISS is defined in Attachment J-2, UISS SRD in Section 1.3 as containing an Off-board Component, LCS Component and MPSF Component. The Contractor shall provide under this CLIN the Off-board Component and the following componets of the LCS and MPSF Components: the Operator Interface Software (OIS), DSD and Trailer. The integration shall include GFP provided for incorporation, Attachment J-7, IAW SRD 3.9.14. The Government will also provide all GFP listed in Attachment J-6. Government approved and accepted EDMs will serve as a manufacturing standard for production units, if option(s) are exercised. The Contractor shall deliver the EDM within 24 months of contract award. The period of performance in Section F of 30 months is for final acceptance, which includes Developmental Testing.

2.1.2 Provisioned Items Orders ((If option is exercised) CLIN 0002) The Contractor shall deliver components as ordered by the Government IAW Naval Sea Systems Command (NAVSEA) Clause PROVISIONED ITEMS ORDERS (APR 1999).

2.1.3 Engineering Services ((If options are exercised) CLINs 0003, 0100, 0202, 0302, and 0402)

The Contractor shall supply Engineering Services for the UISS efforts for work not under the scope of any other Contract Line Item Number (CLINs). (CDRL J001) Engineering Services shall include tasks such as:

• Directed studies, analysis, and reports;

• Field services;

• Engineering Change Proposals (ECPs);

• Provide support for Government test events;

• Life Cycle Management and Open Systems;

• Software Support Activity;

• Provide fabrication services;

• Provide feedback to current production and continuing engineering programs;

• Assist in planning, installation, testing, checkout, adjustment, operation, disassembly, reassembly, modification, refurbishment, and repair of the UISS and related equipment;

• Maintain UISS mandated design performance capabilities such as systems engineering and efforts associated with engineering change proposals;

• Perform various maintenances for the Unmanned Influence Sweep System (UISS)

• UISS repairs and overhauls; and

• Record all maintenance, repair, and modernization actions as outlined in the

Government’s Visual Information Display System/Maintenance Action Form.

Individual work efforts will be defined and authorized by separate Technical Instruction (TI) as issued under NAVSEA Clause 5252.242-9115. TIs will be prepared and reviewed by the Program office and approved by the NAVSEA Procuring Contracting Officer

(PCO).

Contractor work performed under Studies, Analysis, and Services shall not impact cost, schedule, or increase risk to other CLINs without the approval of the NAVSEA PCO. If there are impacts to other CLINs, the Contractor shall notify the PCO immediately before compliance with TI. Engineering services resources, to include key personnel, key equipment, and other critical resources shall not receive priority over activity or deliverable on any other CLIN without approval of the NAVSEA PCO. Status of TIs shall be included in Monthly Progress Reports.

2.1.4 Support for Engineering Services ((If options are exercised) CLINs 0004, 0101, 0203, 0303, and 0403)

The Contractor shall provide support such as, but not limited to, travel, subsistence and lodging, Other Direct Costs incurred as required during performance of TIs for the related studies, analysis, and services item(s) IAW Support for Engineering Services Clause, ENGINEERING SERVICES (NAVSEA) (APR 2004).

2.1.5 UISS EDM Spares ((If option is exercised) CLINs 0005)

The Contractor shall fabricate and/or procure, assemble, test, and deliver the UISS Spares specified in Exhibit N IAW SOW 2.13.7. Varying quantities of spares shall be ordered based upon per unit pricing in Exhibit N.

2.1.6 UISS Tools and Test Equipments ((If options are exercised) CLINs 0006, 0209, 0210, 0309, 0310, 0409, and 0410)

The Contractor shall fabricate and/or procure, assemble, test, and deliver the UISS Tools and Test Equipments specified in Exhibit P IAW SOW 2.13.4. Varying quantities of tools and test equipments shall be ordered based upon per unit pricing in Exhibit P.

2.1.7 Data Requirements (CLIN 0007)

Data deliverables shall be produced and submitted IAW the applicable Contract Data Requirements Lists (CDRL) in Exhibits A, B, C, D, E, F, H, and J listed under Section J for both EDM and Production Units.

2.1.8 Technical Manuals (CLINs 0008)

The Contractor shall provide Technical Manuals (TM) IAW the applicable CDRL in Exhibit G under Section J for both EDM and Production Units as defined in SOW 2.13.11.

for the Unmanned Influence Sweep System (UISS)

2.1.9 Data Rights ((If option is exercised) CLIN 0010)

CLIN 0010 includes Technical Data (TD), Computer Software (CS), and Computer Software Documentation (CSD) including source code for all software. The TD, CS, and CSD shall be in sufficient details to allow Government to meet the UISS life cycle requirements including independent construction, upgrade, repair, installation, operation, training, and maintenance. The Government may purchase Government Purpose Rights (GPR) for all or some of the TD, CS, and CSD that the Contractor uses in the UISS Program but intend to deliver with less than GPR. The TD, CS, and CSD shall include all CDRLs and data required for independent construction, upgrade, repair, installation, operation, training, and maintenance.

2.1.10 Training ((If options are exercised) CLINs 0102, 0204, 0304, and 0404) The Contractor shall provide operation training and organizational and intermediate level maintenance training as defined in SOW 2.13.2.

2.1.11 UISS Production Unit ((If options are exercised) CLINs 0200, 0201, 0300, 0301, 0400, and 401)

The Contractor shall provide all labor, materials, and facilities to design, fabricate, procure, assemble, integrate, test and deliver a fully functional UISS, meeting the contractual requirements as defined in this SOW, Attachment J-2, UISS SRD, dated 3 July 2013, and Contractor Developed System Specification, Attachment J-3 including all appendices thereto. The UISS is defined in Attachment J-2, UISS SRD in Section 1.3 as containing an Off-board Component, LCS Component and MPSF Component. The Contractor shall provide under this CLIN the Off-board Component and the following componets of the LCS and MPSF Components: the Operator Interface Software (OIS), DSD and Trailer. The integration shall include GFP provided for incorporation, Attachment J-7, IAW SRD 3.9.14. The Government will also provide all GFP listed in Attachment J-6. Government approved and accepted EDMs will serve as a manufacturing standard for production units, if option(s) are exercised.

The Contractor shall include in the first production unit (if option is exercised) CLIN 0200 a complete Technical Data Package (TDP) that allows the Government to fabricate and manufacture all the assemblies and subassemblies of the UISS as defined in SOW

2.13.15. TDP deliverables shall be produced and submitted IAW the applicable CDRLs in Exhibit M listed under Section J. The Contractor shall include in the first production unit (if option is exercised) CLIN 0200 Initial Operational Test and Evaluation (IOT&E) Support.

The Contractor shall deliver the first Production Unit (CLIN 0200) 18 months after option exercise. The period of performance in Section F of 27 months is for final delivery of the TDP.

for the Unmanned Influence Sweep System (UISS)

2.1.12 UISS Training System ((If options are exercised) CLINs 0205, 0206, 0305, 0306, 0405, and 406)

The Contractor shall provide UISS Training System, meeting all of the training requirements as defined in this SOW, including all appendices thereto; and Section 3.27.8 of Attachment J- 2, UISS SRD.

2.1.13 UISS Production Option Spares ((If options are exercised) CLINs 0207, 0208, 0307, 0308, 0407, and 0408)

The Contractor shall fabricate and/or procure, assemble, test, and deliver the UISS Spares specified in Exhibit N IAW SOW 2.13.7. Varying quantities of spares shall be ordered based upon per unit pricing in Exhibit N.

2.1.14 Data Requirements ((If option is exercised) CLIN 0211) Data deliverables shall be produced and submitted IAW the applicable CDRLs in Exhibit K listed under Section J for the Production Units.

2.1.15 Reserved

This section is reserved.

2.1.16 Interactive Electronic Technical Manual (IETM) ((If option is exercised)

CLIN 0213)

The Contractor shall develop an Interactive Electronic Technical Manual (IETM) for the UISS and its tools and test equipments as defined in SOW 2.13.12. IETM deliverables shall be produced and submitted IAW the applicable CDRLs in Exhibit L listed under Section J.

2.1.17 Reserved

This section is reserved.

2.2 Program Management (Applicable to all CLINs)

During the design, fabrication, production, and test of the UISS, the Contractor shall perform Program Management, Configuration Management, Technical, Environmental and Safety, Reliability, Availability, and Maintainability (RAM), Quality Assurance (QA), and Logistics support services. These services will be performed IAW this SOW.

The Contractor shall generate a Contractor’s Monthly Progress Report (MPR). (CDRL A002)

2.2.1 Work Breakdown Structure (WBS)

The Contractor shall develop a Work Breakdown Structure (WBS) IAW MIL-STD-881C Appendix I to Level 3. The Contractor shall use the WBS as the primary framework for all efforts under the subject contract including contract planning, budgeting, and reporting of the cost, schedule, and technical performance status to the Government.

2.2.2 Subcontract Management

The Contractor shall actively manage the performance and quality of all work performed for the Unmanned Influence Sweep System (UISS) under subcontract. The Contractor is responsible to flow all applicable contract requirements down to all subcontractors. The Contractor shall actively engage the Integrated Product Team (IPT) leads referenced in SOW 2.2.4 in the preparation of all subcontract specifications and statements of work. The Contractor shall invite Government contracting and technical representatives to participate in Subcontractor visits and reviews. The Contractor shall provide 15 working days advance notice to the Government Contracting Officer Representative (COR) prior to planned Subcontractor visits and reviews. Attendance at these reviews or tests is optional on the part of the Government and failure of the Government representative to attend shall not constitute an excusable delay on the part of the Contractor.

2.2.3 Risk Management

The Contractor shall develop and maintain a Risk Management Program IAW NAVSEAINST 5000.8 and PMS406 Risk Management Plan to assess the risks associated with program cost, schedule, and achievement of technical performance requirements.

(CDRL A008) The Contractor shall participate in the UISS Risk Management Board IAW the PMS406 Risk Management Plan. The Contractor shall maintain a risk database which:

• Identifies known and potential cost, schedule and technical performance risks.

• Assesses risks by determining likelihood of occurrence and assigns a relative ranking of program consequence.

• Documents actions to mitigate or minimize these risks and closure criteria.

• Effectively manage and track identified risks to potential impacts to cost, schedule, or technical performance.

The Risk Management database shall be maintained by the Contractor and reviewed at the Program Reviews (PR). The risk database shall be included in the PR’s presentation package. (CDRL A005) Risk mitigation actions shall have defined schedule milestones.

The Contractor shall prioritize risks. The Contractor shall notify the Government within three (3) working days of identifying a red risk, per the risk assessment matrix. Risk Management Status Report shall be submitted. (CDRL A009)

2.2.4 Integrated Product Team (IPT)

IPTs shall serve as a forum to exchange detailed systems information and development progress, including cost, schedule and technical information for the functional area governed by the respective IPT. Each IPT shall be empowered to make decisions for its functional area. The IPT membership will be composed of appropriate Contractor, Subcontractor, and Government representatives. The Contractor shall establish multidisciplinary IPT membership to ensure that decisions made in the IPT take into consideration impacts across multiple functional areas. IPTs shall be co-chaired by the Contractor and the Government.

for the Unmanned Influence Sweep System (UISS)

The Contractor shall hold IPT meetings at its facilities or utilize virtual IPT meetings, such as teleconferences or video teleconferences, as proposed by the Contractor and approved by the Government. Teleconferences or video teleconferences services shall be provided by the Contractor. The Contractor shall develop the agenda of each IPT meeting. The Contractor shall generate and record minutes and action items of the IPT meetings, and produce copies of all information presented. (CDRLs A005, A006, A007) The Contractor shall develop the meeting announcement containing the draft agenda prior to the IPT meetings. The Contractor shall generate and maintain an updated action item list, and attendance list at the conclusion of each IPT meeting. The meeting minutes shall not constitute a change and reporting of any change shall be IAW Federal Acquisition Regulation (FAR) 52.243-7 “NOTIFICATION OF CHANGES”.

IPT meetings shall commence immediately following the Post Award Conference (PAC), commencing with the Management IPT, and continuing on a regularly scheduled basis as agreed with the government co-chair for the duration of the subject contract. At a minimum, the Contractor shall schedule the following IPTs:

• Management

• Integrated Support Logistics (ILS)

• Test and Evaluation (T&E)

• Systems Engineering

• Safety

• Software

• LCS Integration

At the first Management IPT of each quarter, the Contractor shall propose for Government approval, the upcoming schedule of IPT meetings for the next ninety (90) days. The Government reserves the right to revise the functional focus of the aforementioned IPTs based on Program needs or risks. The Contractor shall provide fifteen (15) working days advance notice to the Government IPT members prior to each planned IPT meeting.

2.2.5 Working Groups (WGs)

Each IPT shall govern a specific functional area of the UISS program. Each IPT may be composed of multiple Working Groups (WGs), which shall govern individual systems, sub-systems or issues within that functional area. The membership of each WG may be composed of appropriate Contractor, Subcontractor and Government personnel, as determined by IPT Co-Chairs.

WGs shall serve as a forum to exchange detailed system information and development progress for a specific system or issue. The scope and authority of each WG shall be determined by its governing IPT. WG meetings for a specific system or issue shall begin when approved by its governing IPT. The number of WGs within an IPT is at the discretion of its governing IPT.

The Contractor shall provide seven (7) working days advance notice to the Government WG members prior to WG meetings. WGs shall utilize virtual meetings when possible.

for the Unmanned Influence Sweep System (UISS)

Meeting spaces, teleconferences or video teleconferences services shall be provided by the Contractor. The Contractor shall generate and record minutes and action items of the WGs, and produce copies of all information developed and presented to the governing IPT. The Contractor shall develop the meeting announcement containing the draft agenda prior to the WG. The Contractor shall generate an updated action item list, and attendance list at the conclusion of each WG meeting.

2.2.6 Government Furnished Property (GFP)

The Contractor shall provide for the receipt, storage accountability and installation support for GFP for Performance listed under Attachment J-6 and GFP for Incorporation listed under Attachment J- 7. The Contractor shall provide adequate space for proper storage of all GFP to preserve the security and physical configuration of all GFP.

The Contractor shall integrate and incorporate all GFP provided under Attachment J-7, GFP Incorporated. GFP integration shall include, but not be limited to, providing space, power, weight allocation, heat load, cabling, cableways, all through hull connections, and all other hardware and software interfaces necessary. After incorporation into UISS, the performance of the GFP shall not be less than the documented performance capability of the GFP at the time it was provided.

The GFP for Performance listed under Attachment J-6 will be handled IAW FAR Clause 52.245-1.

2.2.7 Integrated Program Management Report (IPMR)

The Contractor shall generate and maintain an Integrated Program Management Report (IPMR) which will include Contract Performance Reports (CPR) and the Integrated Master Schedule (IMS). (CDRL A001) The Contractor shall generate and maintain an Earned Value Management System (EVMS) that shall comply with Defense Federal Acquisition Regulation Supplement (DFARS) clause 252.234-7002.

The Contractor shall provide an IMS with the following characteristics:

• It is traceable to the WBS IAW SOW 2.2.1.

• It is detailed sufficiently that critical and high risk efforts are identified and planned realistically to assure executability.

• It includes the efforts of all activities, including Subcontractors and suppliers.

• It presents a current, integrated view of the contract or agreement that is consistent with resource plans, CPRs and other approved documentation.

• It shall reflect those risks identified and documented in the Contractor’s risk management plan.

• It shows links and dependencies between tasks and the critical path

2.2.8 Contract Funds Status Report (CFSR)

The Contractor shall provide a Contract Funds Status Report (CFSR). (CDRL A004) The Contractor shall reconcile reporting elements in the CFSR with the CPR monthly and for the Unmanned Influence Sweep System (UISS) provide as an addendum to the IPMR. The Contractor shall use the WBS developed in

SOW 2.2.1.

2.2.9 Integrated Data Environment (IDE)

The Contractor shall use an Integrated Data Environment (IDE) as a collaboration team site to exchange information with the Government for all exercised CLINs to the maximum extent practical. The IDE shall be a Contractor hosted and operated collaboration tool compliant with the requirements of Navy/Marine Corps Intranet.

The Contractor shall post deliverables, presentations, meeting minutes, models, final drawings, parts lists, IPT and WG information, and other related information as applicable and identified by the CDRL. The Contractor shall use a consistent descriptive file name scheme and folder structure.

The Contractor shall provide access for all UISS team members, as identified by the COR, to the IDE. It is the Contractor’s responsibility to obtain the appropriate digital certificates to access the website for all authorized individuals. The Contractor shall promptly address all the IDE accessibility or functionality issues. If the IDE is ever inaccessible, the Contractor shall deliver items as directed by the COR. The IDE being inoperable does not relieve the Contractor of their responsibility to produce all required items on time. All CDRLs and Contractor technical documentation shall be available for the Government to review and comment in the IDE environment.

Data shall be protected IAW the appropriate Information Assurance (IA) and Program Protection Plans (PPP) guidelines in SOW 2.2.11 and 2.2.12.

All items posted to the IDE, including drafts of deliverables that are not final versions, shall be considered delivered for purposes of all of the DFARS data rights related clauses (and subject to the same rights asserted for final deliveries). However, these non-final versions shall not constitute acceptance for purposes of Section E or the DFARS data rights clauses.

Classified deliveries shall be on CD ROM or hardcopy IAW Contract Security Classification Specification DD254, Attachment J- 4. Classified material shall be delivered to the COR.

The Contractor shall maintain and archive all data. The Contractor shall request and receive written permission from the Government PCO or COR before purging data files.

2.2.10 Information Assurance (IA)

The Contractor shall conduct IA IAW:

• DoDD 8500.01E, “Information Assurance”, October 24, 2002 Certified Current as of April 23, 2007

• DoDI 8500.2, “Information Assurance Implementation”, February 6, 2003

• DoDI 8510.01, “DoD Information Assurance Certification and Accreditation Process (DIACAP)”, November 28, 2007 for the Unmanned Influence Sweep System (UISS)

• DoDI 8523.01, “Communications Security (COMSEC)”, April 22, 2008

• NAVSEAINST 9400.2 Implementation of Naval Sea Systems Command (NAVSEA) Afloat Information Assurance (IA) Governance and Guidance, 18 Aug 2010

• Department of the Navy Chief Information Office (DON CIO) Acquisition Information Assurance Strategy Guidance, 4 February 2013

The Contractor shall develop and deliver an IA Implementation Plan, a Platform Information Technology Risk Assessment (PRA), and an IA Strategy (IAS) Security Plan. (CDRLs H011, H012, H014) The IA Implementation Plan will be used to manage the contractor’s planned implementation of each IA Control IAW DoD 8500.2 and appropriate Mission Assurance Category and the Confidentiality Level of the system, and to track IA compliance throughout the lifecycle of the system. Each IA Control shall be uniquely named and formally catalogued. Implementation guidance is provided within the template for each IA Control, as well as the Impact Code. The Impact Code indicates the consequence of a Non-compliant IA Control. Each IA Control shall be explicitly addressed as part of an information system security engineering process.

The compliance status of each IA Control shall be reported on the DIACAP Scorecard, included within the DoD C&A Package. A Defense Information Assurance Certification and Accreditation Process (DIACAP) team will be assembled to develop and implement the IA Implementation Plan for compliancy of the IA Controls. The IA Controls will be evaluated to determine the applicability of each control and/or whether or not the IA Control is inherited.

Compliant (C) IA controls are those for which the expected results for all associated validation procedures have been achieved. Non-Compliant (NC) IA controls are those for which one or more of the expected results for all associated validation procedures are not achieved. Not achieving expected results for all validation procedures does not necessarily equate to unacceptable risk. Not Applicable (N/A) IA controls are those that do not impact the IA posture of the system as determined by the Authorizing Official.

The Platform Information Technology (PIT) designated system is required to obtain a PRA from the PIT Designated Accrediting Authority (DAA). A PRA will allow the PIT system to operate in its intended environment. The PRA request will be submitted as far in advance as is practical to support the first instance the system will be connected to an operational network, requiring the PIT DAA's approval.

The primary purpose of the IA Risk Management is to identify, assess, minimize and accept (as necessary) IA risks in the context of systems, sub-networks, platform networks, and ship or submarine missions. NAVSEA IA Risk Management occurs through the PRA process.

The list of Non-Applicable IA Controls along with sufficient technical justification shall be submitted to the PIT DAA for formal concurrence. The Letter of Acceptance of Non-for the Unmanned Influence Sweep System (UISS)

Applicable IA Controls from the PIT DAA shall be included in the PRA submittal. Other requirements to support C&A include the implementation of Security Technical Information Guides (STIGS) and security checklists that correspond to the software installed, and implementation of an IA Vulnerability Management (IAVM) program to include patch maintenance, anti-virus scanning, and vulnerability scanning.

The Contractor shall host an IA test event to be performed by the Government to support the requirements for Verification and Validation (V&V). This test event shall be included in the Master Test and Evaluation Program Plan (MTEPP), SOW 2.11.1.

The IAS Security Plan, CDRL H014, shall remain a stand-alone document. The plan shall address the security measures to protect all aspects of the system to include the protection of classified information, critical program information, and/or critical components to meet DoD security and IA requirements.

In order to meet the IA standards for Commercial Off-the-Shelf (COTS), the acquisition of all IA- and IA-Enabled COTS hardware and/or software shall be limited to products that have been evaluated or validated through either the International Common Criteria, http://www.commoncriteriaportal.org/, the National Information Assurance Partnership Evaluation and Validation Program, http://www.niap-ccevs.org/, or Federal Information Processing Standards validation program, http://www.nist.gov/itl/fips.cfm.

The Contractor shall ensure that personnel providing IA services are certified and accredited IAW DoDD 8570.01 for the IA functions that they are performing on the UISS system.

2.2.11 Program Protection Implementation

The Contractor shall prepare a UISS Program Protection Implementation Plan (PPIP).

(CDRL H016)

The Contractor shall adhere to the following:

• DoDI 5200.39 “Critical Program Information (CPI) Protection Within the Department of Defense”, July 16, 2008 Incorporating Change 1, December 28,

• DoD 5200.1-M “Acquisition Systems Program Protection”, March 16, 1994

• Deputy Assistant Secretary of Defense, Systems Engineering Program Protection

Plan Outline and Guidance, July 2011

• The Directive-Type Memorandum (DTM) 09-016, “Supply Chain Risk

Management (SCRM) to Improve the Integrity of Components Used in DoD Systems”, dated 25 March 2010, Incorporating Change 3, 23 March 2012

• Anti-Tamper Security Classification Guide (SCG), 17 March 2010

The Contractor shall identify Critical Program Information (CPI)/Critical Technologies (CT) inherent in the system or inherited from external systems, and shall perform a Criticality Analysis (CA) for Supply Chain Risk Management (SCRM) to determine the mission critical functions that may result in catastrophic or critical protection failures due to operational, system information, or component integrity aspects.

http://www.commoncriteriaportal.org/ http://www.niap-ccevs.org/ http://www.nist.gov/itl/fips.cfm for the Unmanned Influence Sweep System (UISS)

For the identification of CPI/CT, the Contractor shall follow a Work Breakdown Structure (WBS) process to evaluate the hardware and software components according to the following specific questions IAW the DoN CPI WBS Tool:

a. If this technology was compromised could it cause significant degradation in combat effectiveness?

b. If this technology was compromised could it shorten the expected combat life of the system?

c. If this technology was compromised could it significantly alter program direction by requiring an additional investment to counter a compromise?

d. If this technology was compromised could it enable an adversary to copy or reverse engineer a unique technology or capability?

The Contractor shall initiate a request to Naval Criminal Investigative Service (NCIS) for a Multidiscipline Counterintelligence Threat Assessment (MDCI TA) to be compiled based on any CPI/CT identified for the Program.

The Contractor shall plan for the reduction of foreign intelligence, technology exploitation, supply chain and battlefield threats and system vulnerabilities that result in the catastrophic (Level I) and critical (Level II) protection failures. These plans shall be documented in the PPIP.

For any catastrophic (Level I) and critical (Level II) protection failures, the Contractor shall submit a request for a Defense Criminal Investigative Service (DCIS) Threat Assessment to be completed for those critical components. The Contractor shall use Government-provided foreign intelligence and technology exploitation threat information along with the traditional battlefield threat information to inform system security engineering and systems engineering, and the procurement decisions processes.

The Contractor shall demonstrate that the contractor has visibility into its supply chain for identified critical components, understands the risks to that supply chain, and has implemented or plans to implement risk mitigations to counter those risks. The Contractor shall ensure that updated criticality analysis assumptions, rationale, results, and supply chain risk information and mitigations are made available for Government review for each Systems Engineering Technical Review and are documented in the PPIP.

If applicable, the Contractor shall host an Anti-Tamper (AT) test event to be performed by the Government to support the requirements for V&V. This test event shall be included in the MTEPP, SOW 2.11.1.

2.2.12 Electromagnetic Environmental Effects (E3)

The Contractor shall establish, maintain, and document an Electromagnetic Environmental Effects (E3) program to ensure that the UISS is IAW Attachment J- 2, UISS SRD, and Attachment J-3, System Specification. E3 includes Electromagnetic Compatibility (EMC), Electromagnetic Interference, Electromagnetic Susceptibility, for the Unmanned Influence Sweep System (UISS)

Electromagnetic Vulnerability, Electrostatic Discharge (ESD), Radiation Hazards, magnetic fields, and lightning.

The Contractor shall provide E3 Integration and Analysis Report. (CDRL D005) The report shall also include information on all UISS electromagnetic frequency sources and the operating frequencies.

2.3 Meetings, Conferences and Reviews (Applicable to all CLINs) The Contractor shall provide minutes of meetings, to include conferences and technical reviews, and document and track assigned action items. The Contractor shall provide the agenda and minutes, including presentation materials and documented action items, for each meeting. (CDRLs A005, A006, A007)

2.3.1 Meetings

2.3.1.1 Technical Interchange Meetings (TIMs) (Applicable to all CLINs) The Contractor shall plan to conduct up to six (6) Government-initiated Technical Interchange Meetings (TIMs) per year for the life of the contract. The purpose of the TIM is to conduct face-to-face technical discussions that cannot wait until the next scheduled PR and cannot be conducted via conference call or web conference. The Government will identify agenda topics prior to each TIM. The Contractor shall host the TIMs at its facility or at a facility mutually agreed on by the Contractor and the Government.

2.3.1.2 Post Award Conference (PAC) (Applicable to CLIN 0001) The Contractor shall host a PAC at its facility no later than thirty (30) days after Contract Award. The PAC shall be no longer than four (4) business days. The Conference shall be held at the Contractor’s facility. Representatives from first-tier subcontractor on the Contractor's team shall attend. The discussion topics will include, but are not limited to, the following:

• Review the Contract and Technical requirements.

• Discuss the roles and working relationships between the Contractor and the Government.

• Discuss the Contractor’s planned management effort and requirements verification process.

• Review the schedules and mechanics for meetings and reviews:

o IPTs o Integrated Baseline Review (IBR) o PRs o System Requirement Review (SRR) o Preliminary Design Review (PDR) o Critical Design Review (CDR) o Software CDR o Production Readiness Review (PRR) for the Unmanned Influence Sweep System (UISS) o Production Technical Design Review (TDR) o Test Readiness Review (TRR)

• Identify the IPTs and their respective roles and responsibilities

• Configuration management approach

• Present updated key program milestones identified in the Contractor’s IMS

• Participate in the Defense Acquisition University Acquisition Program Transition Workshop IAW "Acquisition Program Transition Workshops, An Element of the DSMC Program Manager Mission Assistance Capability", October 2011, http://www.dau.mil/pubscats/PubsCats/Acquisiton_Prog_Transition_Guide.pdf

• Contract Mechanics:

o Contract Administration o Team Introductions o EVMS

• Technical Discussions:

o Management processes o Major Technical Risk Areas o Metrics proposed to track program status o Systems engineering approach and processes

The Contractor shall provide an overview as to how the program is intended to be executed, describing the planned approach for coordinating and establishing communications among the various team members, identifying the engineering activities and associated distributions of effort and responsibility, elaborating on the overall management philosophy as it relates to resolving conflicts and problems, and discussing achievement of key milestones and challenges to overcome in order to meet the program objectives. The Contractor shall resolve and/or clarify any additional issues.

2.3.2 Reviews

2.3.2.1 Program Reviews (PR) (Applicable to all CLINs)

The Contractor shall schedule and conduct joint Contractor/Government PRs that include senior-level program management, senior-level technical management and subject matter experts’ participation. A PR shall be held quarterly with up to two (2) additional Government-initiated PRs per year at the Contractor/Subcontractor facility. Initial PR held no later than 60 days after contract award.

Program reviews will be focused on cost, schedule, performance, and risk status. At a minimum, the Contractor shall address the following areas during each review in addition to topics proposed by the Contractor:

• Open action item status

• IMS status

• Engineering progress/ status / issues http://www.dau.mil/pubscats/PubsCats/Acquisiton_Prog_Transition_Guide.pdf for the Unmanned Influence Sweep System (UISS)

• System integration progress/ status / issues

• Test progress/ status / issues

• Manufacturing progress/ status / issues

• Long lead items status

• Logistics / Sustainment progress/ status / issues

• GFP progress/ status / issues

• Business / Financial / Contracts topics

• Earned Value Management (EVM)

• Affordability Goals

• CDRL status

• Risk

• Subcontractor Management

• Workload and Resource Requirements. Contractor’s overall manpower utilization projection/actual (3 month history, 9 month future)

The Contractor shall host the quarterly via conference call, or web conferencing.

2.3.2.2 Integrated Baseline Review (IBR) (Applicable to CLIN 0001) The Contractor shall conduct an IBR within one hundred and eighty (180) days after contract award IAW DFARS Clause 252.234-7002. IBR shall be no longer than five business days. The Contractor will host the IBR at its facility. The IBR shall identify and present how the Contractor has allocated all contracts and technical requirements down to the work package or cost account. The Contractor shall ensure that the baseline includes the entire contract technical scope consistent with the latest approved IPMR (CDRL A001), and has adequate resources assigned. The IBR will be used to achieve a mutual understanding of the baseline plan and the underlying management processes. The Contractor will develop the IBR structure and agenda IAW the National Defense Industrial Association Integrated Baseline Review Guide (2010 rev 1). The IBR shall include Control Account Manager (CAM) discussions. IBRs should also be conducted on subcontracts that meet or exceed a $5 Million EVM threshold. The Contractor shall lead the subcontractor IBRs, with active participation by the Government.

The IBR entrance criteria shall be:

• Submittal of all appropriate CDRLs

The Contractor shall have the following documentation available for the IBR:

• SOW

• WBS and dictionary. WBS or the Responsibility Assignment Matrix (RAM) should show mapping of the SOW paragraphs to the WBS.

for the Unmanned Influence Sweep System (UISS)

• RAM in Excel. RAM should show each control account (CA) and contain the WBS Identifier, related SOW Paragraph numbers, WBS Description, CA Manager Name, Performance Measurement Baseline Value, and whether the CA is Level of Effort (LOE) or discrete. If the CA has LOE and discrete mixed, the RAM will reflect a column showing the percent of the CA value that is LOE.

RAM should reflect the amount of Management Reserve (MR), the amount in Undistributed Budget (UB) if applicable, and the sum of MR, UB, and all CAs should equal the contract budget base.

• Work Authorization Documents (WADs). WADs should reflect the internal contract between the Program Manager and the CAM reflecting the scope, budget, and required schedule dates for each control account. Scope of the WAD shall reference the SOW and/or WBS.

• CA Plans. CA plans should show the time phased budget for the tasks/milestones within the CA by element of expense. The sum of all tasks within the CA plans must sum to the values reflected in the RAM.

• IMS [i.e. Master, Intermediate, and Detailed Schedules] in PDF format. Visible fields should include WBS ID, Accounting System Description, Duration, Baseline Start & Finish Dates, Earned Value Weight, Earned Value Method, Total Float, and Predecessors and Successors. Because of space limitations for this schedule, the predecessor/successor fields do not have to show all of the predecessors/successors in the schedule. If an intermediate schedule is not used by the Contractor, then it is not required to be provided.

• Critical Path Schedule showing all tasks on the critical path.

• Organizational Breakdown Structure (OBS). The OBS should show project organization and include major subcontractors and contract type. All CAMs should be identifiable on the OBS.

• Manpower Charts. For each CA to be reviewed, provide manpower charts over time by resource type.

• Risk Assessment to include mitigation steps and waterfall charts

• EVMS Description and any related procedures/processes. Project documentation shall reflect the variance thresholds to be used for the project.

• Current CPRs (if applicable) for last three months.

Exit criteria for the IBR, shall consist of:

• The agreement on the Program Measurement Baseline (PMB)

• All IBR…