Updated_PWS.pdf

Performance Work Statement (PWS)

Raytheon Sensor Systems

September 09October 28, 2015

Version 1.0

Performance Work Statement (PWS)

Raytheon Sensor Systems

1 Introduction

This Performance Work Statement (PWS) provides technical services to the Naval Air Warfare

Center Weapons Division (NAWCWD). The primary technical customer will be the F/A-18

Integrated Product Team (IPT)/Advanced Weapons Lab (AWL) at the China Lake site. The IPT is responsible for managing and executing assigned F/A-18/EA-18G avionics and weapons integration workload including development, test and evaluation, in-service engineering, and operations support of all current and future models of F/A-18/EA-18G aircraft.

Task Orders issued under this contract will support any F/A-18/EA-18G sensor systems, which includes the AN/APG-65, AN/APG-73 and AN/APG-79 radars, and the AN/ALR-67(V)3 electronic warfare system. The contractor shall provide technical support for hardware and software anomaly investigation, design, development, documentation, integration, test, and evaluation of systems and support equipment as a result of the F/A-18/EA-18G lifecycle.

2 Applicable Documents

The Government will provide all necessary reference documents not generally available to the contractor as required. Throughout the life of the contract, if any instruction or document is replaced or superseded, the replacement or superseding instruction or document shall be applicable to the requirements defined in this PWS.

These documents will be used as guidance for execution of this PWS and as invoked in T.O.s issued under this contract:

2.1 MANUALS

A1-F18AC-NFM-000 Navy Model F/A-18 Aircraft Flight Manual (NATOPS)

2.2 INSTRUCTIONS

OPNAVINST 3432.1A Operations Security, 4 Aug 11

DoDI 8500.01 Cybersecurity, 14 Mar 2014

2.3 STANDARDS

DOD 5220.22-M National Industrial Security Program Operating Manual (NISPOM), 28

February 2006, Incorporating Change 1, 28 Mar 13ISO/IEC 12207:2008 Systems and Software

Engineering-Software Life CycleProcesses, 2nd Edition, dtd 1 February 2008

MIL-HDBK-881C Work Breakdown Structure, 3 Oct 2011

2.4 F/A-18 PROGRAM UNIQUE DOCUMENTS

F/A-18 & EA-18G System Life Cycle Plan for the F/A-18 & EA-18G

Plan-U-643 Aircraft, 5 January 2010 (aka System Engineering Technical Review (Tailored)

SETR (T))

PEO(T) CSP Cybersecurity Plan, 1 June 2015 Version 3.2

P32008-826 F/A-18 APG-73 Software Design Document, Volumes I(U), II (C), and III (S), Revision M, 15 September 2000 (U)

AS-6195 (S) F/A-18E/F AESA Radar AN/APG-79 Weapons System Specification, 19

December 2002 (U)

AS-6171 (S) System Performance Specification for the AN/ALR-67(V)3 Radar Warning

Receiver System, 18 Jun 1998 (U)

2.5 RAYTHEON UNIQUE DOCUMENTS

EI-09-01, Rev D Configuration and Data Management Process, 1 May 2005

Software Quality Program Plan Manual

10255 Earned Value Management System Process Description, Version 3.0, 15 Sep 2003

2.6 INFORMATION TECHNOLOGY

The Government will provide all necessary reference documents not generally available to the

Contractor as required. Throughout the life of the contract, if any instruction or document is replaced or superseded, the replacement or superseding instruction or document shall be applicable to the requirements defined in this SOW.

The Contractor shall not purchase any IT equipment on behalf of NAVAIR in support of this

Contract, which reports to PBIS-IT, without a Naval Air Systems Command (NAVAIR)

Command Information Officer (CIO) approved NAV-IDAS ITPR.

Clinger-Cohen Act:

In 1996, Congress enacted the Clinger-Cohen Act (CCA) requiring agencies to use a disciplined capital planning and investment control process to acquire, use, maintain and dispose of information technology. In accordance with the following Department of Defense Directive

(DoDD), Department of Defense Instruction (DoDI), Office of the Secretary of Defense (OSD) memo, and Secretary of the Navy Instruction (SECNAVINST), CCA compliance is required for all programs that contain IT, including National Security Systems (NSS). NSS are defined in

National Institute of Standards and Technology (NIST) Special Publication (SP) 800-59. Six factors are used to identify NSS, one of which is IT in weapons and weapons system programs.

The law provides authority to the agency’s Chief Information Officer (CIO) to manage IT resources effectively and ensure cybersecurity and interoperability. The authority to grant compliance with CCA as a statutory milestone program document resides at either first echelon or second echelon. The level of the Acquisition Category (ACAT) or designation as an

Abbreviate Acquisition Program (AAP) determines which echelon has this authority. ACAT III and below acquisition programs CCA compliance assertion confirmation approval authority is delegated to the second echelon Command Information Officers. ACAT I and ACAT II acquisition programs CCA compliance assertion confirmation approval resides at DON CIO

(First echelon). Approval of interoperability standards compliance for all acquisition programs resides at DON CIO. Approval of the Cybersecurity Strategy (formerly Acquisition Information

Assurance Strategy) is a component of CCA compliance however it is approved separately.

Approval authority is divided among the DoD, and DON CIOs as well as the second echelon

Command Information Officers. See Table 1 for allocation of approval authorities.

ACAT Review and

Endorsement by Command

Information

Officer

Approval by as Command

Information

Officer

Review and

Endorsement by DASN

(C I&Space)

Review and

Endorsement by DON CIO

Approval by DON

CIO

Approval by DoD

CIO

IC X X X

ID X X X X

IAM X X X X

IAC X X X X

II X X X

III X

IV X

AAP X

1 See Interim DoD 5000.02 Enclosure 11, Section 6.b.(1): For ACAT ID, IAM, and IAC programs, the DoD CIO will review and approve the Cybersecurity Strategy prior to milestone decisions or contract awards.

Cybersecurity Strategy approval process begins after the Program Manager signs the

Cybersecurity Strategy and puts it forward to the Command Information Officer. The final approved Cybersecurity Strategy is an appendix to the Program Protection Plan (PPP) as well as an element of CCA compliance (Interim DoDI 50000.02, Tables 2 and 9).

a. Interim DoD Instruction 5000.02, "Operation of the Defense Acquisition System, November

25, 2013

b. OSD Memo, Clinger-Cohen Act Compliance Policy, Mar 8 2002

c. SECNAVINST 5000.2E, Implementation and Operation of the Defense Acquisition Web

Sites, Web Enablement and Application / System Development, Modification, and

Web Sites, Web Enablement and Application / System Development, Modification, and

Maintenance Support Services:

All Information Technology systems, software, and website development, modification or support shall be performed in accordance with all applicable Federal, DoD, DON, and NAVAIR policy, guidance, standards, and strategies, and should be integrated within the NAVAIR

Enterprise portal and collaboration environment whenever possible. Any Web sites/servers hosted/located in contractor facilities, or outside NAVAIR enclave, will transition to NAVAIR architecture and infrastructure in accordance with Legacy Shutdown guidance. Policies include, but are not limited to:

a. Office of Management and Budget Management of Federal Information Resources, OMB

CIRCULAR NO. A-130 Revised.

b. OMB Policies for Federal Agency Public Websites, OMB M-05-04 http://www.whitehouse.gov/sites/default/files/omb/memoranda/fy2005/m05-04.pdf

c. Section 508 Amendment to the Rehabilitation Act of 1973 http://www.section508.gov/

d. Department of Defense Web Policies and Guidelines http://www.defense.gov/webmasters

e. Navy Information Operations Command (NIOC) Norfolk Web Risk Assessment Team

Website http:www.public.navy.mil/fcc-c10f/nionorfolk/Pages/AboutWRA.aspx

f. DON Policy for Content of Publicly Accessible World Wide Web Sites SECNAVINST

5720.47B www.navy.mil/navydata/internet/secnav5720-47b.pdf

g. NAVAIR CIO Website (NAVAIR specific policy and guidelines)

To request this policy contact the NAVAIR CIO office 7.2.2 Applications Integration team Web

Manager: Shane Malamphy at 301- 342-1825

h. Defense Information Systems Agency (DISA) Hosting of All Navy Websites (NAVADMIN

061/08) http://www.public.navy.mil/bupersGnpc/reference/messages/Documents/NAVADMINS/NAV20

08/NAV08061.txt

i. Consolidation of Navy Web Sites - Reduction of IM/IT Footprint NAVADMIN 145/07 http://www.public.navy.mil/bupers-npc/reference/messages/Documents/NAVADMINS/NAV2007/NAV07145.txt

j. DON Web Presence Policy: The Registration, Compliance of, and Investment in, All

Unclassified Web Sites and Uniform Resource Locators http://www.doncio.navy.mil/ContentView.aspx?ID=577

k. Policy and Procedures for Web Risk Assessment (WRA) of Publicly Accessible NavySites

(ALCOM 129/09)

http://www.public.navy.mil/fccGc10f/niocnorfolk/Documents/NTDG08G09.txt

Cybersecurity:

NAVAIRs Cybersecurity Program is a unified approach to protect unclassified, sensitive or classified information, and is established to consolidate and focus efforts in securing that information, including its associated systems and resources. Cybersecurity is required operationally throughout the DON. The DON CIO is responsible for IT within the Navy, as mandated by the Clinger-Cohen Act, and is the lead for departmental compliance with the

Federal Information Security Management Act of 2002

All Cybersecurity shall be in compliance with the following listed instructions:

a. ASD (NII) Directive-Type Memorandum (DTM) 08-027 Security of Unclassified DoD

Information on Non-DoD Information Systems, 31 July 2009

b. Chairman of the Joint Chiefs of Staff Instruction CJCSI 3170.01H (series), Joint Capabilities

Integration and Development System, 10 January 2012

c. CJCSI 6211.02D Defense Information System Network (DISN): Policy and Responsibilities, 24 Jan 2012

d. CJCSI 6212.01F Net Ready Key Performance Parameter (NR KPP), 21 March 2012

e. CJCSI 6251.01D Narrowband Satellite Communications Requirements, 30 Nov 2012 http://www.public.navy.mil/bupersGnpc/reference/messages/Documents/NAVADMINS/NAV2008/NAV08061.txt http://www.public.navy.mil/bupersGnpc/reference/messages/Documents/NAVADMINS/NAV2008/NAV08061.txt http://www.public.navy.mil/fccGc10f/niocnorfolk/Documents/NTDG08G09.txt

f. CJCSI 6510.01F, Information Assurance (IA) and Support to Computer Network Defense

(CND), 09 Feb 2011, certified current 10 Oct 2013

g. Chairman of the Joint Chiefs of Staff Manual CJCSM 6510.01B Cyber Incident Handling

Program 10 July 2012

h. Chief of Naval Operations/Headquarters, United States Marine Corps CNO N614/HQMC C4

Navy-Marine Corps Unclassified Trusted Network Protection (UTN- Protect) Policy, Version

1.0, 31 October 2002

i. Defense Acquisition Guidebook Chapter 7, Acquiring Information Technology, Including

National Security Systems, Section 7.5 Information Assurance (IA)

j. DoD 5220.22-M, National Industrial Security Program Operating Manual, February 28, 2006

(NISPOM)

k. DoD 8570.01-M, Information Assurance Workforce Improvement Program, 19 Dec 2005

(Incorporating Change 3, 24 Jan 2012)

l. DoDD 8000.01 Management of the Department of Defense Information Enterprise, 10

February 2009

m. DoDD 8100.02, Use of Commercial Wireless Devices, Services, and Technologies in the

Department of Defense (DoD) Global Information Grid (GIG), 14 April 2004, Certified Current as of 23 April 2007

n. DoDD 8570.01 Information Assurance Training, Certification, and Workforce Management, 15 August 2004, Certified Current as of 23 April 2007

o. DoDI 8330.01, Procedures for Interoperability and Supportability of Information Technology

(IT) and National Security Systems (NSS), 21 May 2014. p. DoDI 8500.1, Cybersecurity, 14

March 2014

q. DoDI 8510.01, Risk Management Framework (RMF) for DoD Information Technology (IT), 12 March 2014

r. DoDI 8520.2, Public Key Infrastructure (PKI) and Public Key (PK) Enabling, 01 April 2004

s. DoDI 8551.1, Ports, Protocols, and Services Management (PPSM), 13 August 2004

t. DoDI 8580.1, Information Assurance in the Defense Acquisition System, 9 July 2004

u. DoDI 8581.01, Information Assurance (IA) Policy for Space Systems Used by the Department of Defense, 8 June 2010

v. DON CIO Memo 02-10, Department of the Navy Chief Information Officer Memorandum 02-

10 Information Assurance Policy Update for Platform Information Technology, 26 April 2010

w. DON letter 5239 NAVAIR 726/2322 of 18 Feb 09, NAVAIR Data at Rest Policy x. Federal

Information Processing Standards Publications (FIPS PUB) http://www.nist.gov/itl/fips.cfm

y. National Security Telecommunications and Information Systems Security Policy NSTISSP

No. 11, Revised Fact Sheet National Information Assurance Acquisition Policy, July 2003.

aa. Office of the Chief of Naval Operations OPNAV INST 5239.1C, Navy Information

Assurance (IA) Program, 20 Aug 08

bb. SECNAV M-5239.1, Department of the Navy Information Assurance Program; Information

Assurance Manual, November 2005

cc. SECNAVINST 5230.15, Information Management/Information Technology Policy for

Fielding of Commercial Off the Shelf Software, 10 April 2009

dd. SECNAVINST 5239.3B, Department of the Navy Information Assurance Policy, 17 June

ee. SECNAVINST 5239.19, Department of the Navy Computer Network Incident Response and

Reporting Requirements, 18 March 2008

ff. The National Security Act of 1947

gg. Title 40/Clinger-Cohen Act

hh. Title 44/ Federal Information Security Management Act

All IT procured on behalf of this contract shall meet all DoD/DON and NAVAIR IA polices.

Failure to follow these policies will result in denied access to NMCI, One Net, Integrated

Shipboard Network System (ISNS) and other DON, DoD and Joint Networks. These IA policies are standard across the Department and ensure IA compatibility and interoperability.

IT systems and or networks operated by contractors pursuant to a NAVAIR contract, regardless of the level of data processed, shall be operated in accordance with the NISPOM.

Contractor-owned equipment shall be permitted connections to NAVAIR/DoD networks in order to carry out the performance of this contract. All Contractor-owned hardware and/or software shall meet DoDI 8500.2 Cybersecurity Controls, is subject to validation scanning and must be approved by the NAVAIR site IA Manager prior to connection.

The following specific criteria must be met before the contractor may be connected to any DoD or NAVAIR network in support of this contract. Requirements include:

a. Network Vulnerability Scanning. NAVAIR Deputy CIO for Information Assurance maintains authorized auditing tools and shall provide for firewall/port scans, device discovery scan, vulnerability assessment, and other requirements as required to ensure secure interoperability with DoD Contracts. The contractor shall be responsible for the remediation of any equipment that fails these audits prior to the connection the system to the networks; Results of approvals shall be documented via Memorandum of Agreement with the Facility Security officer and the Defense Security Service Representative for that contractor;

b. Extent of Validation Scanning. To prevent scanning of corporate assets, all such networks, equipment and connections shall be physically segregated from any government/contractor corporate networks that are not in direct support of DoD contracts;

c. Circuit Provisioning. Any circuit or connection between NAVAIR and/or DoD site and the contractor site shall be provisioned via the Defense information Security Agency and comply with CJCSI 6211.02C (series), Defense Information System Network (DISN): Policy and

Responsibilities, 9 July 2008;

d. Servicing Systems from a Remote Contractor Site. Remote Access Service connections that allow off-station operation and/or administration of contractor owned systems, located at any

NAVAIR facility or site, shall not be permitted, with the exception of those systems connecting to the Command via the Outreach Services identified in Section 7, Enterprise Architecture;

e. Memorandum of Agreement and Inter-connection Agreements. An Information Assurance

Memorandum of Agreement (MOA) between the contractor owning the equipment and AIR-

7.2.6 shall be developed and signed before the equipment can be connected to NAVAIR networks. Failure to comply with the signed MOA shall be grounds for disconnection from the network.

Enterprise Architecture:

a. Contractor Networks and Connections. Contractor-owned and operated networks are prohibited on any Naval Air Systems Command (NAVAIR) facility or site in support of this contract. The contractor may access non-government, external IP space via the NAVAIR-provided Virtual Private Network (VPN) Outreach service or NAVAIR CIO approved Internet

Protocol (IP) service.

b. Architecture Compliance. The contractor shall ensure all IT solutions, including database solutions, comply with the appropriate NAE Enterprise Architecture, and are verified by the

NAVAIR Enterprise Architect (AIR-7.2.3) prior to build out.

c. Disclosure of pre-existing networks, circuits or connections. Any and all networks, circuits or connections between the contractor and any NAVAIR site related to previous contracts shall be identified in the MOA. Failure to comply and subsequent discovery of an unregistered network, circuit or connection shall be grounds for immediate disconnection.

3 Performance Requirements

3.1 Tactical System Support

3.1.1 System Development. The Contractor shall design and develop system and subsystem hardware/software for the F/A-18/EA-18G sensor systems for the United States Navy, Marine

Corps, and foreign military System Configuration Sets (SCSs).

Performance Standards

a) STD: Timely and Meets design review criteria.

AQL: 100%

3.1.2 The Contractor shall incorporate updates in system and subsystem documentation for modified, new, and improved tactical capabilities as specified by a Functional Requirements

Document (FRD), System Trouble Report (STR), or System Anomaly Report (SAR) approved for implementation via the Developmental Configuration Review Board (DCRB). (CDRL A002)

Performance Standards

a) STD: Meets Schedules as specified in the FRD, DCRB, or project plan and provides accurate updates.

AQL: 90%

3.1.3 The Contractor shall upgrade or modify hardware and software to correct system anomalies identified by the customer.

Performance Standards

a) STD: Meets schedules to correct system anomalies and provides accurate corrections for identified anomalies.

3.1.4 The Contractor shall update Operational Flight Programs (OFPs) and deliver documentation including requirements document, design changes, program performance specification (PPS) changes, interface changes and a final version description document (VDD) detailing the final delivery of the OFP. (CDRL A002, CDRL A008)

Performance Standards

a) STD: Complete, accurate, and timely

3.1.4.1 The Contractor shall deliver the OFPs for the Test, Analyze, and Fix (TAF) testing in an agreed upon format. (CDRL A008)

Performance Standards

3.1.5 The Contractor shall deliver software tools and documentation developed under this contract in the order of precedence: (1) as specified by the associated T.O., and if not specified,

(2) no later than 30 days from the expiration of the final order under the basic contract. The software tools and documentation are those utilized for the purpose of system software development, performance analysis, system modeling, and data reduction. (CDRL A005)

Performance Standards

a) STD: Meets Schedules and delivers accurate software tools and related documentation.

3.2 Studies and Analysis

3.2.1 The Contractor shall prepare studies and document analyses in support of generating new or modified system requirements and capabilities. Tasking shall include preparation and delivery of technical reports in accordance with CDRL A003. Technical reports shall describe investigation, analysis, and evaluation of technical problems stating the cause of the problem, providing detailed recommended changes, and describing the associated risks to correct the deficiencies or implement the new capabilities.

Performance Standards

3.2.2 The Contractor shall investigate and analyze System Anomaly Reports (SARs) or System

Trouble Reports (STRs) and related problems for the F/A-18/EA-18G sensor systems. Tasking may include preparation and delivery of modified hardware/software for evaluation as potential solutions to the defined anomaly. Tasking shall include preparation and delivery of technical reports in accordance with CDRL A003.

Performance Standards

3.2.3 The Contractor shall participate in system/software development boards, which may include the Operations Advisory Group (OAG), Maintenance Advisory Group (MAG), Developmental Configuration Review Board (DCRB), and the System Change Review Board

(SCRB). Tasking shall include preparation and delivery of technical reports in accordance with

CDRL A003.

3.2.3.1 The Contractor shall review and report on analyses and investigations. (CDRL A003)

a) STD: Technical reviews and reports are timely, clear, concise, foster dialogue, and enable technical decision making.

3.2.3.2 The Contractor shall make and document recommendations for system changes in accordance with CDRL A003.

Performance Standards

a) STD: Complete, accurate, and timely.

3.2.3.3 The Contractor shall evaluate system problems for impact to the systems and provide documentation of the analysis in accordance with CDRL A003.

Performance Standards

a) STD: Evaluation is thorough, addresses technical and programmatic feasibility of implementation, and supports an integrated program plan or schedule.

3.2.4 Test Data Analysis. The Contractor shall provide traceability forwards and backwards among test results, conclusions, and customer performance requirements which are expressed through the new software designs under performance testing conditions. (CDRL A009)

3.2.4.1 The Contractor shall design, develop, and maintain sensor analysis software tools required to support system level analysis. The sensor analysis software tools shall be able to convert instrumentation data into engineering data format that can be imported into various

Commercial Off the Shelf (COTS) engineering analysis applications. All data analysis software tools and associated documentation shall be delivered under this contract according to the same schedule reflected in 3.1.5..

Performance Standards

a) STD: Meets Schedules and provides accurate and maintained software tools

3.2.4.2 The Contractor shall perform analysis and provide integrated data that allows correlation and tracking of test results, test status, test profiles, design documents, and system performance for the problem being investigated/corrected or the defined requirement. The results of the analysis shall be provided in accordance with CDRL A003.

Performance Standards

3.2.4.3 The Contractor shall evaluate Government or contractor test data per the requirements specified by the T.O in accordance with CDRL A00A.

a) STD: Evaluation of test data is complete, accurate, and timely

3.2.4.4 The Contractor shall perform analysis, develop, and deliver documentation in support of

Formal Qualification Test (FQT) performed prior to acceptance of software deliverables. The analysis and documentation shall be delivered in accordance with CDRL A00A, A00B.

Performance Standards

3.2.5 Integration Support. The Contractor shall provide technical support during an SCS life-cycle.

3.2.5.1 The Contractor shall provide analysis and documentation of sensor performance, anomaly investigation, and hardware/software characterization as it pertains to the entire weapon system platform. The Contractor shall submit analysis and documentation in accordance with

CDRL A003.

Performance Standards

3.2.5.2 The Contractor shall modify hardware, software and/or special test equipment during the integration effort as required to support system level testing.

Performance Standards

3.2.6 Problem Tracking. The Contractor shall derive a list of problems from the NAWCWD

OFP Project Status (OPS) database. The Government will advise and prioritize tasking for OFP development efforts.

Performance Standards

3.2.7 Document Development Matrix (DDM). The Contractor shall generate, document, and deliver to the Government for approval, a DDM to define all documentation deliverables generated by the contractor. Frequency will be specified at the T.O. level. (CDRL A004)

3.2.7.1 The Contractor shall include those items defined within this paragraph, the SETR (T), as well as those defined in the specific T.O. This matrix shall be updated to reflect current status and accompany each data submission. Documents may include but are not restricted to, the following: SCS Planning Schedule, Financial Reporting Documents, Test Plans/Reports, Software Development Plan, Functional Requirements Document (FRD) Traceability Matrix, Computer Operation Manuals, and Firmware Support Manuals. Other documentation may include Functional Decomposition Descriptions, Engineering Change Proposals (ECPs), Interface Definition Documents, White Papers, Analysis Results, Software Tools, Source Code, Executable Code, and Design Models. (CDRL A002, A003, A008, A00A, A00G, A00H, A00J)

Performance Standards

3.2.7.2 The Contractor shall provide a matrix describing traceability for the data deliverables between the T.O. and the contractor's data products, as defined at the T.O. level. (CDRL A004)

Performance Standards

3.2.8 Instrumentation. The Contractor shall provide laboratory, ground, and flight test instrumentation support to maintain or improve existing instrumentation suites.

3.2.8.1 The Contractor shall prepare and make ready all test instrumentation software and hardware as defined in the T.O. This support may include troubleshooting and repair of: unique instrumentation software and hardware; design improvements; implementation; modification;

maintaining and updating drawings; wire lists, change notices, and specifications and providing input to, writing, and/or reviewing instrumentation test plans. (CDRL A002)

Performance Standards

a) STD: Meets Schedules and accurately prepares test instrumentation software.

3.2.8.2 The Contractor shall maintain intermediate software required to extract recorded data, time-align the extracted data, and transform the time aligned-collected instrumentation data into engineering units required by analysis programs.

Performance Standards

a) STD: The output is timely, accurate, and in a readable/useable format

3.2.8.3 The Contractor shall upgrade or modify instrumentation hardware and software to facilitate correction of anomalies identified during the Integrated Test and Evaluation (IT&E) phase.

Performance Standards

a) STD: Meets Schedules and provides upgrades/modifications meeting the repair requirements

3.2.8.4 The Contractor shall deliver all instrumentation software tools and associated documentation developed under this contract according to the same schedule reflected in 3.1.5.

(CDRL A005)

3.2.9 Laboratory and Test Equipment Support. The Contractor shall investigate, analyze, recommend, and implement corrections or changes in the contractor or Government laboratories necessary to resolve problems, anomalies, and project-required modifications.

3.2.9.1 The Contractor shall conduct fault isolation and repair of malfunctioning laboratory

Weapons Replaceable Assemblies (WRAs), Shop Replaceable Assemblies (SRAs), and

Replaceable Items (Ris) at the contractor's sensor system laboratory, NAWCWD sensor systems integration laboratories, or other developmental/test facility.

Performance Standards

a) STD: Meets Schedules and is accurately repaired to operating function.

3.2.9.2 The Contractor shall provide technical support for special test equipment (STE) in support of system level and subsystem level testing. Technical support includes designing, developing, delivering, maintaining, repairing, and/or upgrading software and/or hardware of the

STE in support of test activities.

Performance Standards

a) STD: Meets testing schedules and maintains and repairs STE if required, to operating function.

3.2.10 Technical Assistance. The Contractor shall host and/or participate in Technical

Interchange Meetings (TIMs) to discuss and resolve technical issues. TIMs may be performed at the contractor or Government facilities, by phone, or by video teleconferencing. The Contractor shall provide meeting minutes those events they host in accordance with CDRL A00C.

a) STD: Complete, accurate, and timely.

3.2.10.1 The Contractor shall provide technical assistance in the form or verbal or electronic mail interchanges to help resolve problems and anomalies. Record of assistance shall be documented in CDRL A003.

Performance Standards

a) STD: Complete, accurate, and timely

AQL: 90%

3.2.10.2 The Contractor shall provide technical assistance for identified fleet problems by characterizing anomalies. Technical assistance may be required on-site at domestic or FMS operational/developmental facilities. Record of assistance shall be documented in CDRL A003.

Performance Standards

3.3 Test and Evaluation Support

3.3.1 The Contractor shall support integration level testing with weapons systems, sensor development testing, and SCS verification and validation.

3.3.1.1 The Contractor shall perform flight test engineering and performance assessments in support of SCS development, interfaces, and weapons when operated in aircraft or laboratories.

The Contractor shall provide performance assessments in accordance with CDRL A00D.

Performance Standards

a) STD:Complete, accurate, and timely.

3.3.1.2 The Contractor shall support mission briefs and debriefs of flight test and laboratory missions in accordance with CDRL A00D.

a) STD:Complete, accurate, and timely AQL: 90%

3.3.1.3 The Contractor shall support ground tests, conduct anomaly investigations and post-mission analysis to assess weapon system level performance in accordance with CDRL A00D.

Performance Standards

3.3.1.4 The Contractor shall provide engineering input to Government-generated flight and laboratory test plans. The Contractor shall provide inputs via CDRL A002.

Performance Standards

3.4 Technical Planning Estimates

3.4.1 Rough Order of Magnitude (ROM) Estimate. The Contractor shall provide ROM estimates that cover the identified risks to assist the Government in programmatic planning

(CDRL A00E). ROMs shall be tailored for the effort to be estimated and shall provide cost, schedule, and technical information pertinent to the effort based upon written requirements provided by the Government in the form of a draft task statement or draft FRD. ROMs shall identify the fidelity of the estimates and shall typically include the following types of information:

a. Line of code per software configuration item

b. Number of components or board changes for hardware configuration items

c. Estimated costs for lab modifications or build-up

d. Estimated costs for aircraft prototyping

e. Estimated labor hours and costs, including non-labor costs

f. Estimated changes to Avionics Support Equipment (ASE)

g. Estimate documentation, Technical Publications, and Technical Directives

h. Assumptions used for the ROM with the highest cost drivers identified

i. Total cost of effort.

Performance Standards

3.4.2 Impact Statements. The Contractor shall provide impact statements that define the cause and effect of proposed new or changed requirements on the planned SCS efforts. When impact statement estimates are provided, they may have an uncertainty value of + 10%. Impact statements shall be based upon written requirements provided by the Government in the form of a draft task statement, draft SOR or FRD change, SAR or STR. Impact statements shall include at a minimum:

a. Lines of code per software configuration item

b. Number of components or board changes for hardware configuration items

c. Estimated costs for lab modification or build-up

d. Estimated costs for aircraft prototyping

e. Estimated labor hours and costs, including non-labor costs

f. Estimated changes to ASE

g. Estimates for documentation, Technical Publications, and Technical Directives

h. Assumptions used for the impact statement estimates with the highest cost drivers identified

i. Total cost of effort.

The Contractor shall submit impact statements in accordance with CDRL A00E.

Performance Standards

3.5 Performance Reporting

3.5.1 The Contractor shall utilize their existing internal performance management system, identified in paragraph 2.0 above, to plan, monitor, manage and report cost, schedule, and technical status applicable to the task order. The Contractor’s Progress Status and Management report shall be in accordance with CDRL A001.

Performance Standards

3.5.1.1 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.5.1.2 The Contractor shall not establish a separate or unique internal performance management system for purposes of planning, scheduling, directing, statusing, recording, or reporting progress under this contract.

3.5.2 The Contractor shall maintain the existing Contract Work Breakdown Structure (CWBS) and dictionary, using MIL-HDBK-881 for guidance only. The CWBS shall provide the basis for further extension by the contractor to lower levels during the performance of the T.O.

3.5.2.1 The Contractor shall extend the CWBS to the appropriate level required to provide adequate internal management, surveillance, and performance measurement, regardless of the reporting level stipulated in the T.O. for Government visibility.

Performance Standards

3.5.2.2 The Contractor shall prepare technical elements of the CWBS.

3.5.2.3 The Contractor shall update the CWBS during execution of the T.O. Changes to the

CWBS or associated definitions at any reporting level shall require approval of the Contracting

Officers Representative (COR).

Performance Standards

3.5.2.4 The Contractor shall provide an Integrated Master Schedule (IMS). (CDRL A006). The

IMS shall have the following characteristics: It shall be consistent with the CWBS. It must be detailed sufficiently that critical and high risk efforts are identified and planned realistically to assure executeability. The IMS will be extended and expended as the T.O. or agreement unfolds and additional insight is needed (for example, rolling wave detail planning or scope changes). It shall include the efforts of all activities, including contractor or supplier and subcontractor. It shall present a current, integrated view of the T.O. or agreement that it is consistent with resource plans, Contract Performance Reports and other approved documentation. It shall reflect those risks identified and documented in the contractor's risk management plan.

Performance Standards

3.6 Configuration Management

3.6.1 The Contractor shall implement a configuration management program in accordance with their approved Configuration Management Plan (CMP). Any changes or deviations to this program that affect performance of T.O.s on this contract shall be submitted as revisions to this

CMP for COR concurrence prior to implementation. (CDRL A00F)

Performance Standards

3.7 Escort Requirements: Contractor personnel shall perform escort responsibilities for foreign nationals whose contractual or program related efforts require access to sensitive areas at the

Contractor’s facility. Only those contractor employees assigned to the particular contract/program being visited may be utilized.

3.8 Required Enterprise-wide Contractor Manpower Reporting Application (ECMRA)

Information.

Per contract clause C-01, the contractor shall report ALL contractor labor hours for (including subcontractor labor hours) required for performance of services provided under this contract for

NAWCWD via a secure data collection site. The contractor is required to completely fill in all required data fields using the following we address: https://doncmra.nmci.navy.mil.

Reporting inputs will be for the labor executed during the period of performance during each

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

a) STD: Timely and accurate.

3.9 Operations Security (OPSEC) Requirements. The Contractor shall develop, implement, and maintain a facility level OPSEC program to protect controlled unclassified and classified activities, information, equipment, and material used or developed by the contractor and any subcontractor during performance of the contract. The contractor shall be responsible for any subcontractor implementation of the OPSEC requirements. This program may include

Information Assurance and Communication Security (COMSEC). The OPSEC Program shall be in accordance with National Security Decision Directive (NSDD) 298, and at a minimum shall include:

1) Assignment of responsibility for OPSEC direction and implementation.

2) Issuance of procedures and planning guidance for the use of OPSEC techniques to identify vulnerabilities and apply applicable countermeasures.

3) Establishment of OPSEC education and awareness training.

4) Provisions for management, annual review, and evaluation of OPSEC programs.

5) Flow down of OPSEC requirements to subcontractors when applicable.

The contractor shall prepare an Operations Security Plan for government review in accordance with the (CDRL A007).

4 Deliverables

The Contractor shall provide the following data:

CDRL Number Title

A001 Contractor's Progress Status & Management Report

A002 Revisions to Existing Government Documents

A003 Technical Report-Study/Services

A004 Technical Report-Study/Services

A005 Computer Software Product End Items

A006 Integrated Program Management Report (IPMR)

A007 Operations Security (OPSEC) Plan

A008 Software Product Specification (SPS)

A009 Technical Report-Study/Services

A00A Software Test Report (STR)

A00B Software Test Description (STD)

A00C Report, Record of Meeting/Minutes

A00D Technical Report-Study/Services

A00E Technical Report-Study/Services

A00F Supplier's Configuration Management Plan

A00G Test Plan

A00H Engineering change proposal

A00J Interface Design Document

The Contractor shall provide a secure website for the posting of CDRLs with access to selected personnel from the AWL for the distribution and processing of CDRL submittals under this contract.

5 Security

The contractor shall provide personnel with the appropriate personnel security clearance levels for the work to be performed. Access to Top Secret information is required in the performance of this contract and shall be in accordance with the DoD 5220.22-M, National Industrial Security

Program Operating Manual (NISPOM), applicable DoD personnel security regulations and DoD

Contract Security Classification (DD Form 254). The contractor shall maintain sufficiently cleared personnel to perform the tasks required by this SOW IAW the DD Form 254 and the contract. All contractor personnel shall possess the requisite security clearance, accesses, and need-to-know commensurate with the requirements of their positions.

The contractor shall implement and maintain security procedures and controls to prevent unauthorized disclosure of controlled unclassified and classified information and to control distribution of controlled unclassified and classified information in accordance with the National

Industrial Security Program Operating Manual (NISPOM) and DoDM 5200.01, Information

Security Program Manual. The DoD Contract Security Classification Specification, DD Form

254 defines program specific security requirements. All controlled unclassified technical information shall be appropriately identified and marked as For Official Use Only in accordance with DoDM 5200.01 (Information Security Program Manual) (Volume 4) and DoD 5400.7-R

(Freedom of Information Act Regulation) (Chapter 3). All contractor facilities shall provide an appropriate means of storage for controlled unclassified and classified documents, equipment, and materials in accordance with Operational Security (OPSEC) requirements.

For Official Use Only information generated and/or provided under this contract shall be marked and safeguarded as specified in DoDM 5200.01, Information Security Program Manual

(Volume 4) available at http://www.dtic.mil/whs/directives/corres/pdf/520001_vol4.pdf and

DoD 5400.7-R, Freedom of Information Program, Chapter 3 (pages 31-42) available at http://www.dtic.mil/whs/directives/corres/pdf/540007r.pdf. Contractor shall not store or transmit

CUI on personal information technology systems or via personal e-mail.

Public Release: Any controlled unclassified information pertaining to this contract shall not be released for public dissemination, including posting to any social media sites such as Facebook or Twitter, unless it has been approved for public release by appropriate U.S. Government authority. Proposed public releases shall be submitted for approval prior to release through

Commander, Code 4L0000D, Naval Air Warfare Center Weapons Division, 1 Administration

Circle, STOP 6305, China Lake, California 9355-56100.

Communications Security (COMSEC): The contractor will require access to COMSEC and will require a COMSEC account for the work being performed under this contract. U.S.

cryptographic equipment inventory information, as well as the systems and manner in which each particular equipment is used, is for official use only. Publication or release of any related

COMSEC information by any means, by the contractor, without prior written approval of the contracting officer is prohibited. The contractor must be a U.S. citizen, have a final Government security clearance with the appropriate personnel security background investigation for the level of classification involved, have strict need-to-know, have the appropriate COMSEC briefing before access is granted, and granted access only in conformance with procedures established for the particular type of COMSEC information involved. The contractor shall adhere to the DD

Form 254 COMSEC security requirements, facility COMSEC material control and operating procedures, and all applicable COMSEC regulations, instructions, and policies. Prior approval from the Government Contracting Activity is required in order for a prime contractor to grant

COMSEC access to a subcontractor.

5.1 Cybersecurity Plan

http://www.dtic.mil/whs/directives/corres/pdf/520001_vol4.pdf http://www.dtic.mil/whs/directives/corres/pdf/540007r.pdf

For Cybersecurity (CS) requirements see the PEO (T) Cybersecurity Plan (CSP) PEO(T), dated 1

June 2015 Version 3.2. Specific mentioned policies in the CSP can be accessed via the

Cybersecurity Policy Chart. The Contractor shall address the CSP requirements within the

Cybersecurity Implementation Plan (CSIP).

6 Special Requirements

6.1 Travel

Travel shall in accordance with clause 5252.232-9509 and will be identified in individual orders.

All travel requests shall be submitted to and approved by the COR in advance of the travel.

Performance Requirements Summary (PRS)

Statements Standards/AQLs Remedy

3.1 Tactical System

Support

3.1.1 System

Development. The

Contractor shall design and develop system and subsystem hardware/software for the F/A-18/EA-

18G sensor systems for the United States

Navy, Marine Corps, and foreign military

System

Configuration Sets

(SCSs).

a) Timely and meets design review criteria.

AQL: 100%

52.246-5 -- Inspection of

Services -- Cost-

Reimbursement.

3.1.2 The Contractor shall

incorporate updates in system and subsystem documentation for modified, new, and improved tactical capabilities as specified by a

Functional

Requirements

Document (FRD), System Trouble

Report (STR), or

System Anomaly

Report (SAR) approved for implementation via the Developmental

Configuration

Review Board

(DCRB). (CDRL

A002)

a) Meets schedules as specified in the FRD, DCRB, or project plan, and provides accurate updates.

3.1.3 The Contractor shall

upgrade or modify

a) Meets schedules to correct system anomalies and provides hardware and software to correct system anomalies identified by the customer.

accurate corrections for identified anomalies.

3.1.4 The Contractor shall

update Operational

Flight Programs

(OFPs) and deliver documentation including requirements document, design changes, program performance specification (PPS) changes, interface changes and a final version description document (VDD) detailing the final delivery of the OFP.

(CDRL A002,

CDRL A008)

a) Complete, accurate, and timely

3.1.4.1 The Contractor shall

deliver the OFPs for the Test, Analyze, and Fix (TAF) testing in an agreed upon format. (CDRL

A008)

3.1.5 The Contractor shall

deliver software tools and documentation developed under this contract in the order of precedence: (1) as specified by the associated T.O., and if not specified, (2) no later than 30 days from the expiration

a) Meets schedules and delivers accurate software tools and related documentation.

of the final order under the basic contract. The software tools and documentation are those utilized for the purpose of system software development, performance analysis, system modeling, and data reduction. (CDRL

A005)

3.2 Studies and Analysis

3.2.1 The Contractor shall

prepare studies and document analyses in support of generating new or modified system requirements and capabilities. Tasking shall include preparation and delivery of technical reports in accordance with

CDRL A003. Technical reports shall describe investigation, analysis, and evaluation of technical problems stating the cause of the problem, providing detailed recommended changes, and describing the associated risks to correct the deficiencies or implement the new capabilities.

a) Complete, accurate, and timely

52.246-5 -- Inspection of Services -- Cost-

3.2.2 The Contractor shall a) Complete, accurate, and 52.246-5 -- Inspection investigate and analyze

System Anomaly Reports

(SARs) or System Trouble

Reports (STRs) and related problems for the

F/A-18/EA-18G sensor systems. Tasking may include preparation and delivery of modified hardware/software for evaluation as potential solutions to the defined anomaly. Tasking shall include preparation and delivery of technical reports in accordance with

CDRL A003.

3.2.3 The Contractor shall

participate in system/software development boards, which may include the

Operations Advisory

Group (OAG), Maintenance Advisory

Group (MAG), Developmental

Configuration Review

Board (DCRB), and the

System Change Review

Board (SCRB). Tasking shall include preparation and delivery of technical reports in accordance with

CDRL A003.

3.2.3.1 The Contractor shall

review and report on analyses and investigations. (CDRL

A003)

a) Technical reviews and reports are timely, clear, concise, foster dialogue, and enable technical decision making.

3.2.3.2 The Contractor shall make

recommendations for

a) Complete, accurate, and 52.246-5 -- Inspection system changes in accordance with CDRL

A003.

timely.

3.2.3.3 The Contractor shall

evaluate system problems for impact to the systems and provide documentation of the analysis in accordance with CDRL A003.

a) Evaluation is thorough, addresses technical and programmatic feasibility of implementation, and supports an integrated program plan or schedule.

3.2.4 Test Data Analysis. The

Contractor shall provide traceability forwards and backwards among test results, conclusions, and customer performance requirements which are expressed through the new software designs under performance testing conditions.(CDRL A009)

3.2.4.1 The Contractor shall

design, develop, and maintain sensor analysis software tools required to support system level analysis. The sensor analysis software tools shall be able to convert instrumentation data into engineering data format that can be imported into various Commercial Off the Shelf (COTS) engineering analysis applications. All data analysis software tools and associated documentation shall be delivered under this contract according to the same schedule reflected in

a) Meets schedules and provides accurate and maintained software tools.

3.1.5.

3.2.4.2 The Contractor shall

perform analysis and provide integrated data that allows correlation and tracking of test results, test status, test profiles, design documents, and system performance for the problem being investigated/corrected or the defined requirement.

The results of the analysis shall be provided in accordance with CDRL

A003.

a) Complete, accurate, and

3.2.4.3 The Contractor shall

evaluate Government or contractor test data per the requirements specified by the T.O in accordance with CDRL A00A.

a) Evaluation of test data is complete, accurate, and

3.2.4.4 The Contractor shall

perform analysis, develop, and deliver documentation in support of Formal

Qualification Test (FQT) performed prior to acceptance of software deliverables. The analysis and documentation shall be delivered in accordance with CDRL A00A, A00B.

a) Complete, accurate, and

3.2.5 Integration Support. The

technical support during an SCS life-cycle.

3.2.5.1 The Contractor shall

provide analysis and documentation of sensor performance, anomaly investigation, and hardware/software characterization as it

a) Complete, accurate, and pertains to the entire weapon system platform.

The Contractor shall submit analysis and documentation in accordance with CDRL

A003.

3.2.5.2 The Contractor shall

modify hardware, software and/or special test equipment during the integration effort as required to support system level testing.

a) Complete, accurate, and

3.2.6 Problem Tracking. The

Contractor shall derive a list of problems from the

NAWCWD OFP Project

Status (OPS) database.

The Government will advise and prioritize tasking for OFP development efforts.

a) Complete, accurate, and

3.2.7 Document Development

Matrix (DDM). The

Contractor shall generate, document, and deliver to the Government for approval, a DDM to define all documentation deliverables generated by the contractor. Frequency will be specified at the

T.O. level. (CDRL A004)

3.2.7.1 The Contractor shall

include those items defined within this paragraph, the System

Engineering Technical

Review (Tailored) (SETR

(T)), as well as those…