Sec J Atch 2 - IDIQ SOW UEWR 04.25.12.doc

Rev 2 – 19 MAY 2010

FOR OFFICIAL USE ONLY - COMPETITION SENSITIVE

SOURCE SELECTION INFORMATION - SEE FAR 2.101 AND 3.104

Public Release – 25 April 2012

Upgraded Early Warning Radar & COBRA DANE (UEWR & CD) Ballistic Missile Defense System (BMDS) Integration & Test (UEWR & CD BIT) Statement of Work

Prepared By Missile Defense Agency (MDA) BMDS Sensors Directorate (SN) Huntsville, AL 35897-3801 25 April 2012 table of contents

Introduction.

11.1 Overview.

11.2 Scope.

31.3 Background.

41.4 Contract Execution Strategy.

Applicable Documents.

52.1 Reference Documents

62.2 Common Compliance Documents

112.2.1 Government Documents (Raytheon)

112.2.2 Government Documents (Boeing)

122.2.3 Other Government Documents

Requirements.

133.0 General.

133.1 Program Management.

233.2 Training.

233.3 Long Term Agreements.

243.4 Delays.

243.5 Facility and Data Access.

253.6 Systems Engineering.

253.7 Configuration Management.

253.8 Safety, Quality, and Mission Assurance (SQMA).

283.9 Infrastructure

313.10 Test and Evaluation.

443.11 Warfighter Support.

443.12 Modeling and Simulation. (M&S)

TRANSITION.

464. Transition Periods.

Additional Test EFFORT.

ORDERING PERIOD.

Appendices.

50Appendix A: DATA DELIVERABLES.

54Appendix B: LIST OF ACRONYMS.

59Appendix C: Government Furnished Listing.

1 Introduction.

1.1 Overview.

The Missile Defense Agency/Sensors (MDA/SN) Program Office is responsible for development and testing of Upgraded Early Warning Radars (UEWR) and the COBRA DANE (CD) radar that provide acquisition and tracking of ballistic missiles launched against the United States, deployed forces, friendly nations, and allies. The radars include UEWRs at Beale Air Force Base (AFB) in California, Royal Air Force (RAF) Fylingdales in the United Kingdom, Thule Air Base (AB), Greenland and CD radar located at Eareckson Air Station (AS) on Shemya Island, AK. All three UEWRs will subsequently transfer to the United States Air Force (USAF) for sustainment in FY12. The Early Warning Radar in Clear Air Force Station (AFS), AK is planned to begin UEWR modernization in FY13. Additionally, Ballistic Missile Defense System (BMDS) integration may be required for future UEWRs (e.g., Cape Cod AFS). MDA/SN performs developmental testing with these radars to ensure the ability to detect, track, and discriminate threat missiles during the early, midcourse and terminal phases of flight.

1.2 Scope.

1.2.1

This UEWR & CD BMDS Integration & Test (BIT) Statement of Work (SOW) defines the tasks and scope which will be acquired through an Indefinite Delivery/Indefinite Quantity (IDIQ) contract. The effort encompasses the radar platforms discussed in paragraph 1.1 and execution of BMDS test related activities that includes planning, executing, and analyzing UEWR & CD BMDS flight tests, UEWR & CD BMDS ground tests (including MDA Benchmark (BM) integration testing), and element tests for each test event defined in the BMDS Integrated Master Test Plan (IMTP) in the manner outlined in the MDA BMDS Test Concept of Operations (CONOPS).

1.2.2

This SOW covers test management for MDA/SN managed UEWR & CD BMDS programs. If additional UEWRs become available through the course of the UEWR & CD BIT ordering period (See paragraph 1.1) they shall require integration into the UEWR & CD BMDS test management framework for MDA/SN testing.

1.2.3 This SOW addresses developmental test transition tasks which the Contractor shall execute during transition periods at the beginning and end of the contract ordering period (up to three months) as defined within the relevant Task Order (TO).

1.2.4 The contractor shall use the Hardware-In-the-Loop (HWIL) representations for each UEWR & CD sensor along with laboratory facilities that are required to execute flight Pre-Mission Testing/System Pre-Mission Testing (PMT/SPMT), UEWR & CD BMDS ground testing, Post-Flight Reconstruction/System Post-Flight Reconstruction (PFR/SPFR), Root Cause Analysis (RCA), element testing, and all analysis tools and if necessary suggest HWIL improvements for testing. The HWIL equipment utilized in testing consists of UEWR & CD test strings at the Integrated System Test Capability–1 (ISTC-1), ISTC-2, and Prime Consolidated Integration Laboratory (PCIL) system test labs located in Huntsville, AL. Close coordination through MDA/SN with contractors at existing Government or contractor laboratories shall be required in order to effectively execute all tasks in a cost efficient manner. The UEWR & CD BIT Contractor may propose test provisioning solutions that are cost efficient and effective, and if accepted and directed by the Government, develop and implement such solutions.

1.2.5 Test provisioning, planning, execution and analysis can require close collaboration and data sharing with development and sustainment contractors, other MDA elements, Operational Test Agencies, and Warfighter operators and maintainers. A key requirement for the UEWR & CD BIT Contractor is the ability to identify all interaction and coordination required from each of these external organizations in order to successfully accomplish all test participation identified in the IMTP.

1.2.6 The Government will interface and coordinate between the UEWR & CD BIT Contractor, Government development and sustainment contractors, (e.g., ITT Sensors for UEWR and Raytheon for CD), and Operational Test Agencies for all test planning and design, pre-test analysis, test execution, and post-test analysis. The Contractor will plan for all personnel, facilities, equipment, operations, maintenance and support as required by the contract.

1.2.7 Government tasking to the Contractor will be via TO. For the initial effort of the contract, the test events and requirements are provided in TO 0001. Other Task Orders will be executed on an as needed basis, but at a minimum once a year.

Examples of TOs (note, the list is not exhaustive):

a) BMDS Ground Tests, Focused (GTX); Ground Tests, Integrated (GTI); Ground Tests, Distributed (GTD);

b) BMDS Flight Tests (including PMT or SPMT);

c) Sensor Element Ground Tests (EGT) and Satellite Test Campaign (STC)

d) Integration BM 1-3 Testing

e) Warfighter Support

f) Additional Test Effort 1.2.8 The Contractor shall ensure their personnel have Government Secret level clearances and that their facilities, information technology equipment, and networks are cleared for processing information up to Government Secret Formerly Restricted Data (S/FRD).

1.3 Background.

The primary objective of MDA/SN is to provide a pervasive sensor net for the BMDS. Each sensor integrates into the layered BMDS. The MDA/SN Mission is to develop, test, acquire, deploy, and sustain BMDS Radars.

1.3.1 Upgraded Early Warning Radar (UEWR).

Three Air Force Early Warning Radars (Beale AFB, CA; RAF Fylingdales, United Kingdom, and Thule AB, Greenland) were upgraded and operationally integrated into the BMDS. The upgrades modernized the hardware and software to improve midcourse BMDS UEWR & CD coverage by providing critical early warning, tracking, object classification and cueing data. The Early Warning Radar in Clear, AK is planned to begin the UEWR modernization in FY13. UEWRs are solid state, phased array, all weather, long-range radars that operate in the Ultra High Frequency (UHF) Band. They provide Integrated Tactical Warning / Attack Assessment through estimated launch and impact points, support the Space Surveillance Network by classifying reentry vehicles and other space objects and provide midcourse coverage for the BMDS by tracking threat ballistic missiles with sufficient accuracy to commit the launch of interceptors.

1.3.2 COBRA DANE Radar.

The U.S. Air Force CD radar at Eareckson AS, Alaska has been upgraded to include the missile defense mission and has been integrated into the BMDS. The upgrade improves midcourse BMDS coverage by providing acquisition, tracking, object classification, and data that can be used for cueing, launch of interceptor missiles, and course updates of interceptors while retaining the site’s legacy intelligence and space track missions. The CD has transitioned system operations, maintenance and sustainment responsibilities to the Air Force.

1.3.3 Upgrade Strategy.

The BMDS program of work couples aggressive Research, Development, Test, and Evaluation (RDT&E) with capability-based acquisition to field new or upgraded capabilities. The result is evolutionary systems design with no final or fixed architecture, but instead a continuous emphasis on improvement over time.

1.4 Contract Execution Strategy.

The UEWR & CD BIT contract is an IDIQ type contract. This SOW covers the contemplated scope over the five year effort. Individual TOs will provide authority for the Contractor to execute scope, (e.g., TO #1 that details the Ground and Flight Testing required during the first year of testing.)

The Contractor shall develop a Work Breakdown Structure (WBS) based on this Contract. That WBS shall be maintained and updated by the Contractor. The WBS shall maintain the SOW numbering convention by maintaining the SOW language with WBS level language added through sub indentures. Cost Accounts shall be maintained and reported at the SOW level with cost collected from across the Organizational Breakdown Structure and reported by Contract Line Item Number (CLIN). The Government will designate each test event by CLIN and funding by sub-CLIN. The Contractor shall invoice the funding using Accounting Classification Reference Number (ACRN) level.

2 Applicable Documents.

All documents listed in this SOW shall apply to the IDIQ Contract, hereafter IDIQ, and option CLINs.

2.1 Reference Documents

2.2 Common Compliance Documents

The following documents, of the exact issue specified, form a part of this UEWR IDIQ SOW which shall be executed in accordance with (IAW) the documents specified herein. Where no date is specified, the revision of the document current as of the date of this Statement of Work applies.

6 Apr 11

Practice, Identification Marking of

U.S. Military Property 17 Dec 07

Standard: Electromagnetic Environmental Effects Requirements for Systems 1 Dec 10

2.2.1 Government Documents (Raytheon)

G760805 Hazardous Materials Management Program Plan Rev. F 20 Jan 05 H292487 XBR/UEWR Product Assurance Plan G761775 Electromagnetic Compatibility (EMC) Control Plan Rev. G 7 Feb 05 G760806 Human Systems Integration Program Plan (HSIPP) Rev. D 25 Jan 05 G760162 Software Design Description (SDD) of the Mission Application Software (MAS) Rev. L 07 Apr 10 H366713 Software Product Specification (SPS) Rev. B 23 Oct 08 G760923 Software Interface Design Description (IDD) for the Mission Application Software / Simulation & Tools Software (MAS/STS) Rev. G 14 Mar 05 2.2.2 Government Documents (Boeing)

D742-10109-2 Interface Design Description (IDD) for Ground-Based Midcourse Defense Fire Control and Communications / Upgraded Early Warning Radar, D742-10109-2 Revision F - June 30, 2010 version.

D742-10104-2 Ground-Based Midcourse Defense Interface Design Description (IDD) for Embedded Test and Upgraded Early Warning Radar, Revision A, 5 November 2004.

H313775 Ground-Based Midcourse Defense COBRA DANE Upgrade (CDU) Interface Control Document (ICD) Rev. A; 05 May 05 H315931 Ground-Based Midcourse Defense CDU Software Design Document (SDD) for Simulation Software (SIM) (CSCI-3) Rev. A; 28 May 04

H315943 Ground-Based Midcourse Defense CDU Software User Manual (SUM) for Operational Support Software (OSS) and Simulation Scenario Generation (SGEN) 28 May 04 H315930 Ground-Based Midcourse Defense CDU Software Design Document (SDD) for Mission Software (MSN) (CSCI-2) Rev D; 4 December 07 H315929 Ground-Based Midcourse Defense CDU Software Design Document (SDD) for Operating System Augmentation (OSA) (CSCI-1) Rev C; 4 December 07 H315932 Ground-Based Midcourse Defense CDU Software Design Document (SDD) for Operational Support Software (OSS) (CSCI-4) Rev C; 4 December 07 List of UEWR ICDs/IDDs:

1) UEWR to ITW/AA and SSN Interface Control Document (ICD) Document No. H381864, Rev. G 15Sept10

2) UEWR Internal Network Processing Equipment (PE) Networking ICD Document No. G760210 Rev G 15 Sep 10

3) UEWR Stand-Alone Trainer (UST) ICD Document No. H329070 Rev. E 15 Jul 10

4) UEWR External Communication Interfaces ICD H337211 - Rev. C 15 Jul 10

5) UEWR to SSF "Draft" ICD developed by Missile Defense System Engineering and Test (MDSET) Government Team 2.2.3 Other Government Documents

IMTP

BMDS Integrated Master Test Plan (IMTP) Version 12.1, 1 March 2012

IMAP

MDA Integrated Master Assessment Plan (IMAP) Version 12.1, 2 Sep 2011 Directive 3002.03 MDA Directive, BMDS Test Policy, 21 Jun 2010

Test CONOPS

MDA BMDS Test Concept of Operations (CONOPS), 8 Apr 2009

Directive 3200.06 Mission-Related Scientific and Technical Data – Information Management, 13 Jun 2008

Directive 3200.07 Test and Experiment Event Notification, 17 Dec 2010

Directive 3200.09 Common System Test & Flight Experiment Event Nomenclature, 26 Oct 2010 3 Requirements.

3.0 General.

This SOW establishes the UEWR & CD BIT work content, which is implemented by individual capability TOs. The Contractor shall perform specific work as directed and funded by individual TOs. The Contractor shall perform TO referenced SOW requirements, to include completing deliverables and providing the Government access to specified data. The Contractor shall plan, execute, and analyze all assigned test events IAW this SOW.

3.1 Program Management.

The Contractor shall provide Program Management (Business Operations, Integrated Master Schedule (IMS), Contract Management, Security, Program Operations, Risk, Developmental Labs Maintenance and Safety, Quality, and Mission Assurance) to enable planning, controlling, directing, monitoring, reporting and managing timelines, and managing all aspects of cost, schedule, and performance as set forth in this SOW and MDA guidance. Program Management activities shall include high quality program leadership, risk management, and integration of testing with MDA/SN program level activities. The Contractor shall conduct acquisition planning and market research to the extent needed to maximize small business participation. The Contractor shall participate in joint meetings with the Government on the contract schedule, cost and technical status.

3.1.1 Integrated Process and Product Management (IPPM).

The Contractor shall apply an IPPM approach that is approved by the Government in all technical/functional disciplines and requirements in a coordinated effort to meet established cost, schedule, performance, and supportability requirements for this contract. The Contractor shall establish a formal organization responsible for executing the total effort required by this contract. A clear line of project authority shall exist among all organizational elements (including subcontractors). Roles, responsibilities, authority, and reporting requirements shall be established for each organizational element.

3.1.1.1

UEWR & CD BIT Program Manager.

The Contractor shall appoint a full-time UEWR & CD BIT Program Manager who has responsibility for accomplishment of all tasks to be performed under this contract. The UEWR & CD BIT Program Manager shall be responsible for cost, schedule and performance. The UEWR & CD BIT Program Manager shall have full authority over all UEWR & CD BIT activities and resources under this contract. The UEWR & CD BIT Program Manager shall be the principal interface between the project and the Contractor’s corporate organization, the project and associate contractors, and between the Contractor and the Government on all matters relating to the contract.

3.1.1.2

Staffing Plan.

The Contractor shall develop and maintain a staffing plan (Contract Data Requirements List (CDRL) A001) that addresses the human resources staffing requirements and the Contractor’s plans for satisfying any surge, core expertise, and/or reach-back capability necessary to support multiple on-going test events and test related activities. The plan shall include surge staffing for all labs as required and the approach to accomplishing unique test events. The UEWR & CD BIT organization structure, roles, responsibilities, authorities, and the staffing plan shall be documented in the Contractor Program Management Plan.

3.1.1.3

Program Management Plan.

The Contractor shall develop and maintain the Program Management Plan (PMP) (CDRL A001). The PMP shall:

· Establish the project organization, structure, authority, roles, responsibilities, internal reporting relationships, and identify associate stakeholders, (e.g., managing Subcontractor, Teaming partners, joint venture partners and/or Associates).

· Define the interface between the project and the Government.

· Define the roles relative to other corporate units and interfaces between the project and other corporate units, e.g., identifying and resolving potential resource conflicts associated with multiple, independent Government contractors engaged in on-going Advanced Research Center (ARC) efforts.

· Establish reporting requirements (project-to-corporation and project-to-Government).

· Clearly identify all Government Furnished Property (GFP), Government Furnished Equipment (GFE), and Government Furnished Information (GFI), Government Furnished Services (GFS) and associated need dates required for performance of this contract.

· Establish project management procedures and policies

· Incorporate by reference the project IMS.

· Discuss program management of budget, cost control, and excursions based upon surge, reach-back and unique event execution.

3.1.2 Kick-off Meeting.

The Contractor shall participate in a UEWR & CD BIT Kick-off Meeting hosted by MDA/SNT within 10 working days after TO 0001 contract award. The purpose of the meeting is to introduce key Government and Contractor personnel, discuss the status of any risks or issues, and to discuss any other issues the Government or Contractor wishes to discuss.

3.1.3 Business Operations.

3.1.3.1

Contractor Integrated Performance Management.

The Contractor shall prepare and utilize, in the performance of this contract, an integrated performance management system. Central to this integrated system shall be a validated Earned Value Management System (EVMS), compliant with the EVMS guidelines contained in ANSI/EIA-748-B. To establish the integrated performance management system, the EVMS shall be linked to, and supported by, the Contractor’s management processes and systems to include the IMS, Contract Work Breakdown Structure (CWBS), change management, material management, procurement, cost estimating, and accounting. The correlation and integration of these systems and processes shall provide for early indication of cost and schedule problems, and their relation to technical achievement.

3.1.3.2

Integrated Baseline Reviews (IBRs).

The Contractor shall engage with the Government’s program manager in IBRs to evaluate the risks inherent in the contract’s planned performance measurement baseline. The initial IBR shall occur not later than four months after contract/TO award with baseline reviews semi-annually thereafter. The Government does not anticipate the need for more than two reviews per year, but may request a review at any time. Subsequent IBRs shall occur after each major change to the baseline or at the Government’s discretion. Each IBR shall verify that the Contractor is using a reliable performance measurement baseline (to include the entire contract scope of work), is consistent with contract schedule requirements, and has adequate resources assigned. Each IBR shall record any indications that compliant Earned Value Management (EVM) is not being used. IBRs shall be conducted on subcontracts that meet or exceed the EVM application threshold. The Prime Contractor shall lead the subcontractor IBRs with participation by the Government.

3.1.3.3

Cost/Finance.

3.1.3.3.1 Cost Reporting.

The Contractor shall develop, maintain and deliver: The Contract Funds Status Report (CFSR) (CDRL A002); Contract Performance Report (CPR) (CDRL A003); Cost Data Summary Report (CDSR - DD Form 1921) (CDRL A004); Functional Cost-Hour Report (FCHR), CWBS (CDRL A005), and the CWBS Dictionary at the contract and TO level. The Contractor shall develop and maintain an estimate at completion (EAC) for each TO by test event and the CWBS. The Contractor shall develop and maintain near term (90 day) cost and schedule variance forecasts monthly to increase visibility into emerging problems and improve reliability of forecasts. The financial reports shall be organized by CWBS to include Work Status Documents (Contractor format)). The Contractor shall deliver monthly financial expenditure reports organized by TO and CWBS unique to each test event (Contractor format). The Work Status Document, Level of Effort (LOE) Report, Rate Impact Report, and Monthly Billing Report shall be available through the Integrated Data Environment (IDE).

3.1.3.3.2 Financial Performance Reviews.

The Contractor shall report as directed by the Government and participate in required financial reviews with the Government to provide visibility into program schedule and cost performance (no more frequent than once per quarter).

3.1.4.

Program Control.

3.1.4.1 The Contractor shall plan, monitor, and control technical, cost, and schedule performance. The Contractor’s cost accounting system shall comply with Federal Acquisition Regulation (FAR) Part 30.

3.1.4.2 The Contractor shall implement procedures to monitor UEWR & CD BIT product cost, schedule and performance. The Contractor shall employ industry standard metrics (cost, schedule, performance, quality, risk, etc.) to assess and report UEWR & CD BIT project and product status. These metrics and procedures shall enable the Contractor to detect and predict deviations from planned or required cost, schedule and performance in time to take effective corrective action. The Contractor shall implement corrective action procedures to prevent, circumvent, or at least limit the consequences of deviations from planned or required UEWR & CD BIT product cost, schedule and performance. Monitoring procedures, metrics, and corrective action procedures shall be documented in the PMP.

3.1.5 Integrated Master Schedule (IMS).

The Contractor shall prepare an IMS (CDRL A006) by logically networking detailed program activities. The schedule shall contain the Integrated Master Plan (IMP) planned test events and milestones, accomplishments, exit criteria, and activities, as well as critical path elements and key dependencies and is subject to Government approval. The Contractor shall quantify risk in hours, days, or weeks of delay and provide optimistic, pessimistic, and most likely duration for each IMS activity and event. The IMS shall be prepared IAW.

3.1.6 Program Management Review (PMR) and Technical Interchange Meeting (TIM).

The Government may schedule, or the Contractor may request the Government schedule PMRs and TIMs. The PMR is a scheduled review (no more frequent than once per quarter) of a program’s cost, schedule and performance. The purpose of the TIM is to provide technical interchange between the various UEWR & CD BIT stakeholders (e.g., other MDA Prime contractors) and/or the Government experts.

3.1.7 Contract Management.

3.1.7.1

Task Orders (TO).

The Contractor shall develop, submit, and facilitate definitization of TO proposals, provide correspondence control, track CDRL submissions, develop and negotiate required Associate Contractor Agreements (ACAs) and Non-Disclosure Agreements (NDAs), and perform other required contract administration activities. The Contractor shall implement export administration policies and procedures and ensure compliance with International Traffic in Arms Regulations (ITAR) and other Government laws and regulations.

3.1.7.2

Contractor Closeout Actions.

The Contractor shall plan and execute in an orderly fashion IAW guidance from the Administrative Contracting Officer (ACO) for Contract Closeout actions. The Contractor shall develop a Contract Closeout Plan (CDRL A001).

3.1.7.3

Subcontract Management.

The Contractor shall pass down to the subcontractor(s) all contract requirements applicable to the subcontract level and only those necessary to complete tasks within their functional area. The Contractor shall establish subcontract management processes commensurate with subcontracted efforts and sufficient to ensure acceptable UEWR & CD BIT cost, schedule, and performance on subcontracted efforts. The Contractor shall periodically review the subcontractor progress and status and communicate the results of these reviews to the Government at the PMRs and in the Project Schedule and Status Reports (CDRL A007). As appropriate the Contractor shall specifically address in Contractor Plans the integration of subcontractors into the overall work effort, to include subcontractor processes, configuration and quality initiatives.

3.1.7.4

Government Property.

The Contractor shall manage the requirements, acquisition, accountability, and maintenance for Government Property (GP) via their Government approved property accounting system. GP includes GFP and Contractor Acquired Property (CAP). The Contractor shall track and provide status updates as required by FAR Part 45, FAR 52.245-1 and H-Clause “Contractor Acquired Property” concerning GP (e.g., quantity, location and purpose) via the IDE.

The Contractor shall track and manage GFE/M in accordance with FAR 52.245-1, DoD Instruction 5000.64, and MDA Instruction 4161.01-INS, Accountability and Reporting of MDA Property. The Contractor shall provide the following CDRLs: 1) Physical Inventory Schedule and Reports for GFP (CDRL A008), and 2) Final Government Property Inventory Report (CDRL A009). The Contractor shall provide an electronic status report, in accordance with the applicable CDRL, describing the condition and usage status of GFE/M received under this contract. CDRL reporting shall exclude material purchased by the Contractor for use in deliverable end items and scrapped material consumed in testing.

In the report, the Contractor shall also document part numbers and National Stock Numbers (NSNs), when available, and justify any requested GFE changes in Requirements compared to the GFE/M list in the contract. The Contractor shall notify and coordinate the repair and test of GFE/M items as required to support the program.

3.1.7.4.1 Item Unique Identification (IUID).

The contractor shall mark the components, parts, and end items with Item Unique Identification (IUID) as required by Defense Federal Acquisition Regulation Supplement (DFARS) 252.211-7003 and IAW MDA Directive 4161.02. The contractor shall insure the IUID markings are machine readable and meet MIL-STD-130N. The contractor shall develop the IUID marking/tags, enter the IUID and required data elements into the IUID Registry, and verify that the IUID numbers are not duplicated in the UII Registry. The Contractor shall update the IUID Registry for parts provided as GFE that have an IUID assigned.

3.1.7.5

Rough Order of Magnitude (ROM) and Not to Exceed (NTE) Pricing and Estimating.

The Contractor shall interface with the Government to ensure that the work for the contract, including changes, is mutually understood. The Contractor shall prepare and submit (1) correspondence for contract deliverables, (2) budgetary or ROM estimates for planning purposes, (3) NTE estimates, (4) estimates leading to negotiations of proposals for changes to the contract, and (5) closeout activities for closeout of this contract. The Contractor shall prepare, submit, fact find and negotiate proposals for changes to the IDIQ contract and each TO.

3.1.7.6

Performance Management System.

The Contractor shall utilize their existing, internal performance management system to plan, schedule, budget, monitor, manage, and report cost, schedule, and technical status applicable to the contract. The Contractor’s internal performance management system shall serve as the single, formal, integrated system that meets both the Contractor’s internal management requirements and the requirements of the Government for timely, reliable, and auditable performance information.

3.1.7.7

Life Cycle Cost Management (LCCM).

The Contractor shall develop and maintain the MDA/SN LCCM Plan (CDRL A001) for this contract using as a guide the Department of Defense (DoD) 5000.04-M-1, Cost and Software Data Reporting Manual.

3.1.8 Program Operation.

The Contractor shall perform Program Operations IAW DFAR 232.7003. Wide Area Work Flow (WAWF) must be utilized as part of the electronic document flow process.

3.1.8.1

Integrated Digital Environment. (IDE) It is the Government’s intention to maximize the use of an IDE for the storage and transmission of all data generated under this contract and for reports generation unless otherwise specified. The Contractor shall establish, operate, and maintain an IDE as the central repository and archive for MDA/SNT program data and documentation IAW the 24 Sep 2009 Memorandum titled, “MDA Knowledge On-line (MKO) IT Governance Standards and Guidelines.” The Contractor shall identify critical components, (e.g., applications, computers, peripherals, networks, data, documentation, and other IT infrastructure), and provide proper data protection/access.

3.1.8.1.1 IDE Guidance.

The Contractor shall populate an IDE with program data and integrate/migrate databases to verify data integrity. The Contractor shall develop or use accepted Industry quality control standards and procedures for updates and handling of IDE data. The Contractor shall fulfill Integrated Product Teams (IPT) information needs and integrate team-linking tools for collaboration purposes via IDE. The Contractor shall develop scripts and methodology for the extraction and transfer of data from unclassified vaults for re-check into the MDA IDE; and the Contractor shall provide a classified version of the IDE.

3.1.8.1.2 IDE Access.

Access to program data on Contractor-managed systems shall be restricted to both external users and those internal to the Contractor’s facility with an established need-to-know. Direct connectivity between Government and other commercial networks outside the IDE that may result in a peering of two networks is prohibited. Implementation of a solution using an existing secure corporate gateway or other secure, cost-effective, best practice method is acceptable. The Contractor shall provide Government personnel IDE access within 30 days of receipt of a Government approved application. The Contractor shall be responsible for identifying and approving personnel access within their organization and fulfilling requirements associated with BMDS Controlled Unclassified Information. Access to the MDA Portal (MDA Knowledge Online 3.0) for all personnel is contingent on fulfilling Government Portal access requirements and restrictions outlined in DD Form 254 (notably section 11.l “Other”).

3.1.8.1.3 Unclassified IDE.

The Contractor shall make documents available through the IDE that are compatible with the current standard business suite of software deployed by the MDA/SN Project Office. The Contractor shall establish connectivity and provide access to their IDE for the MDA/SN facilities, ranges, other Government agencies, and support contractors designated by the MDA/SN Program Office.

3.1.8.1.4 Classified IDE.

The Contractor shall provide the same capability, functionality, and oversight as described for the unclassified IDE. The Contractor shall utilize the Missile Defense Agency Classified Network (MDACnet) for productivity enhancements, file sharing, and collaborative user environment for the MDA mission of RDT&E. A Contractor-controlled firewall shall be installed when connecting classified systems to the MDACnet and coordinate with all applicable agencies for approval to operate.

3.1.8.2

Document, Data, and Property Management.

3.1.8.2.1 Document Management.

The Contractor shall develop and implement comprehensive procedures for the management of documentation, and Government property (equipment, hardware, or software). These procedures shall be documented in the PMP. Data management shall encompass all data and documentation produced by the Contractor under the contract, procured by the Contractor under the contract, and provided by the Government or received by the Government for use on the contract.

3.1.8.2.2 Data Accession List. (DAL) The Contractor shall develop and maintain a Data Accession List (DAL) (CDRL A010). The DAL shall be maintained in the Contractor’s facility. Copies of the DAL shall be delivered to the Government on the schedule identified in the CDRL.

3.1.8.2.3 CDRL Management.

All Contractor CDRL items require Government approval unless otherwise noted. Applicable procedures included or referenced in the CDRL items shall be written with specific test procedures. Contractor CDRLs shall be placed into the IDE in a configuration controlled environment.

3.1.8.3

Security.

3.1.8.3.1 Security Program.

The Contractor and their subcontractors shall implement a security program IAW DoD 5200.1-R Information Security Program Regulation, DoD 5200.08R Physical Security Program, and MDA Directives, policies and issuances. All Contractor supplied facilities or systems shall provide protection and control of information, data, equipment, documentation, and network access. The Contractor shall implement DoD 5220.22-M, National Industrial Security Program Operating Manual (NISPOM) to govern facility security. The Contractor shall not store, transmit, or process information on common Contractor networks except as approved in advance by the Government Contracting Officer. The Contractor shall establish and maintain a security environment in accordance with MDA policy and any other security required by the contract or Public Law.

3.1.8.3.2 Operations Security (OPSEC).

The Contractor shall be knowledgeable of OPSEC requirements and implement appropriate OPSEC measures IAW DoDD 5205.02, DoD Operations Security Program, throughout the effort of this contract. All classified and unclassified information, data and material shall be managed IAW the NISPOM, and as directed by the DoD Contract Security Classification Specification (DD Form 254) issued for this effort.

3.1.8.3.3 Program Security.

The contractor shall meet all requirements of the MDA Information Security Program. The contractor shall execute tasks listed below and as otherwise defined in this SOW.

The Contractor shall maintain security features using established System Security Engineering process IAW DoD 5200.1-M Acquisition Systems Protection Program, DoD 5000.2 Defense Acquisition Guidebook, MIL-HDBK-1013/1A Design Guidelines for Physical Security of Facilities, DoD 5200.1-R Information Security Program Regulation, DoD 5200.08R Physical Security Program, National Security Telecommunications and Information Systems Security Advisory Memorandum (NSTISSAM) Tempest/2-95, Committee on National Security Systems (CNSS) Advisory Memorandum Tempest 01-02, National Security Telecommunications and Information Systems Information (NSTISSI) 7003, Common Criteria and National Security Telecommunications and Information Systems Security Policy (NSTISSP) Number 11.

3.1.8.3.4 The Contractor shall ensure that cleared subcontractor facilities shall schedule and conduct annual Information Security Program Reviews (IPRs) and self-inspections. Serious deficiencies at the subcontractor location shall be reported to the Contractor. When a security risk has been identified at an uncleared location the Contractor will conduct a security program review or a Security Assistance Visit (SAV) with the concurrence of the Contracting Officer Representative (COR). Develop IPR reports and conduct briefings with programs to identify and review goals, processes, and findings.

3.1.8.3.5 The Contractor shall assist with implementation of the Security Incident and Preliminary Inquiry (PI) process IAW DOD and Agency policy; analyze security incidents to verify incident descriptions and address cause, impact, mitigation, and recommended courses of action; coordinate, discuss, and resolve discrepancies; submit reports to MDA Security.

3.1.8.3.6 The contractor shall support the execution of the MDA Program Protection activities. The contractor shall execute tasks listed below:

3.1.8.3.6.1 Plan and implement an Acquisition System Protection program encompassing program security, program protection, and systems security engineering for this contract based upon the requisite threat documents provided by MDA.

3.1.8.3.6.2 The Contractor shall conduct an analysis of the Government directed Program Protection Plan (PPP) to determine adequate protection levels required for the government developed Critical Program Information (CPI). The Contractor shall develop a plan to implement the required protection in accordance with the Government directed PPP. Assess, develop, and draft a Program Protection Implementation Plan (PPIP) and CPI protection training guidelines for contractor personnel with access to CPI for the BMDS.

3.1.8.3.6.3 The Contractor shall generate, update, maintain and implement a PPIP (CDRL A001) which will be a stand-alone document for this contract. The PPIP shall include compliance implementation planning in accordance with the AF/SN PPP, DoDI 5200.39, DoDI 5200.1-M, SD 538-2, DoD 5200.1-R, DoDD 8500.1E, DoD 5200.8-R, CJCSI 6510.01, CJCSI 3210.01, NSTISSP No. 11, MDA 5200.01, and MDA 5200.05. The Contractor shall provide inputs to and support Government security analyses, including system security analyses, the System Vulnerability Analysis (SVA), Operations Security (OPSEC) Plan, System Security Engineering (SSE) requirements analysis, and Information Assurance (IA)/Computer Network Defense (IA/CND) technical assessments. The Contractor shall support Government-conducted Certification & Accreditation (C&A) planning and testing associated with Interim Approval to Operate (IATO), Approval to Operate (ATO), Authorization to Connect (ATC), and System Administration in accordance with DoDI 8510.01. The Contractor shall support government Protection Assessment Reviews (PAR), and Security and Program Protection Working Groups.

3.1.8.3.6.4 Develop PP Training Plans (CDRL A001) and conduct Contractor training of how to assess criticality of technologies and mitigate CPI risks from known or postulated threats IAW government issued PPPs.

3.1.8.3.6.5 Conduct periodic self-assessments to evaluate Program adherence to PPIP and processes. Develop security policy and procedures. Provide government updates on implementing the BMDS SSE requirements IAW the BMDS system specifications.

3.1.8.3.6.6 Develop SSE requirements, System Connection Authorization Requirements documents, and Security Accreditation Agreements documents.

3.1.8.3.6.7 The Contractor shall comply with security requirements in accordance with DoDD 8500.1, DoDI 8500.2, and the National Security Agency Guide for Addressing Malicious Code Risk, and be accredited by the Designated Approving Authority (DAA) prior to operation.

3.1.8.3.7 Supply Chain Risk Management

3.1.8.3.7.1 The Contractor shall demonstrate visibility into its supply chain for critical components, understands the risks to that supply chain, and has implemented or plans to implement risk mitigations to counter those risks in the PPIP.

3.1.8.3.7.2 The provisions of this SOW shall be included in the solicitations and subcontracts for all suppliers, and be suitably modified to identify the security risks suppliers must address to ensure the protection of CPI within the supply chain.

3.1.8.3.8 Program Security Performance.

Performance under this contract requires access to DoD, MDA and MDA Prime and subcontractor locations to provide some service, product, or perform some other official function of interest to MDA. All applicable security requirements shall be satisfied prior to access and may include completing the Standard Form 86 (SF-86), Questions for National Security Positions and/or other forms of identification. All completed forms, to include signed release forms, shall be provided to the Contracting Officer or designated representative at least 30 days prior to required access. Failure to complete documentation and data requirements properly and timely may lead to significant delays in processing and approval for access.

3.1.8.3.9 Non-disclosure Agreements (NDA).

The Contractor shall complete all NDAs suitable for approved access. The Contractor shall immediately notify the Contracting Officer or designated representative when previously cleared contractor or…