SOW_14-R-0108.pdf

N68936-14-R-0108

Section C - Descriptions and Specifications

STATEMENT OF WORK (SOW)

FOR

WEAPONS SYSTEMS INTEGRATION SOFTWARE SUPPORT SERVICES (WSISS) IV

Table of Contents

1 SCOPE

1.1 Background

1.2 General Scope of Work

1.3 Contract Work Environment

2.0 APPLICABLE DOCUMENTS

2.1 Government Specifications, Standards, Handbooks, and Publications

2.2 Clinger-Cohen Act

2.3 System Software / Application Compliance

2.4 Web Sites, Web Enablement and Application / System Development, Modification, and Maintenance Support Services

2.5 Software Development/Server Procurement

2.6 Information Assurance (IA): This is required on all DON Contracts

2.7 Enterprise Architecture

2.8 Software Process Improvement Initiative (SPII)

2.9 Commercial Specifications, Standards, and Handbooks

2.10 Other Publications and Documents

2.11 Sources for Publications and Documents

2.12 Publications Available Post-Award

3.0 REQUIREMENTS

3.1 General

3.1.1 Definition of Customer

3.1.2 Process Improvement Initiatives & Innovations

3.1.3 Contractor Training

3.2 Contractor Program Management, Reporting, and General Performance Requirements

3.2.1 Tracking & Oversight

3.2.2 Periodic Contract Status Reporting

3.2.3 Security and Classified Data

3.2.4 Systems Engineering and Software Process Improvement

3.2.5 Transportation and Leased Vehicle Requirements

3.2.6 Contractor and NAWCWD

3.2.7 Contract Phase-Out

3.2.8 Trained Contractor Work Force

3.3 Technical Performance Requirements

3.3.1 Systems Integration -- Integration of weapons, avionics, sensors and targeting systems, and system

3.3.3 Program-Level Support

3.3.4 Test Laboratory Equipment, Flight Trainers/Simulators, Mission Simulations, and RDT&E Legacy System Support

3.3.5 Aircraft Test Instrumentation and Telemetry Systems

3.3.6 Training/Mentoring

CLIN 0001 – The contractor shall provide Weapons and Systems Integration Software Support services in accordance with Section C Statement of Work.

CLIN 0002 – The contractor shall procure Other Direct Costs in accordance with Section C Statement of Work.

CLIN 0003 – Not Separately Priced (NSP) – The Technical Data to be furnished hereunder shall be in accordance with Exhibit A, Contract Data Requirements List.

1.0 SCOPE

1.1 Background

The Naval Air Warfare Center Weapons Division (NAWCWD) is the weapons systems integration and software support activity for all assigned aircraft Integrated Product Teams (IPTs). IPTs and Program Support Offices currently operating at the NAWCWD include the F/A-18 & E/A-18, AV-8, AH-1, JSF, and Unmanned Systems. In addition to the aircraft named above, the contract may support any other aircraft that may be assigned to the NAWCWD in the future, any system carried by or supporting aircraft IPTs assigned to the NAWCWD, and interoperability initiatives involving supported aircraft. The mission of each IPT and Program Support Office is to provide research, development, test, evaluation, systems integration, and programmatic support for weapons systems and associated tactical computer systems embedded within or carried on their aircraft, including related systems, support equipment, and interoperability initiatives.

The term "aircraft weapon system,” in the context of this Statement of Work (SOW), is defined as weapons/trainers/sensors and targeting/mission computer/avionics systems and software, including electronic warfare (EW) systems, integrated into NAWCWD IPT supported aircraft, as well as associated pre- and post-flight support systems, and/or support equipment hardware and software for any of the above.

1.2 General Scope of Work

The contractor shall provide the following services: research, development, test, and evaluation (RDT&E) technical support services (including full systems integration) to all present and future NAWCWD aircraft IPTs and their associated aircraft weapons and support systems (including foreign military sales (FMS) versions of each aircraft or system), and other related and/or interfacing systems, including related test laboratories and equipment. The scope of the contract includes performing related technical functions necessary to satisfactorily complete primary tasking.

As directed by written task orders issued by the Government, the contractor shall provide RDT&E and other technical services to NAWCWD aircraft IPTs and other NAWCWD customer Codes in the following general areas:

(a) Integration of weapons, avionics, sensors, targeting systems, system hardware, and software (including system analysis, research, development, engineering, testing, test equipment design/fabrication/maintenance, mission simulation, and interoperability assurance);

(b) Software engineering/development for aircraft computers, avionics, sensors, targeting systems, weapons systems, test laboratories, simulators, mission, and system support equipment (including Software Quality Assurance (SQA), Software Configuration Management (SCM), and Verification and Validation (V&V));

(c) IPT program-level services (including special technical research, studies, Quality Assurance (QA), Configuration Management (CM), Data Management (DM), communications management, equipment management, and maintenance of support systems);

(d) Design, fabrication, integration, operation of test and simulation equipment, flight and system trainers and/or simulator equipment (including mission and interoperability simulations);

(e) Aircraft modifications, aircraft test instrumentation, telemetry systems design, development, installation, maintenance, service, setup, and operation (including ground-based telemetry systems);

(f) Provide training in areas where the contractor has special/unique knowledge or expertise and in the use and/or maintenance of software and/or systems designed by the contractor.

1.3 Contract Work Environment

The majority of the contractor’s work force shall be physically located in Government-provided work spaces at China Lake, CA; Pt. Mugu, CA; Yuma, Arizona; Chery Point, NC; Camp Pendleton, CA; and Eglin, FL where contractor tasking is to be performed. In this environment, contractor personnel shall be responsible for knowing and using existing work processes. The Contractor is expected to propose improvements to work processes that result in cost or time savings to the Government. The contractor’s consistent and skillful application of these work processes is critical to the NAWCWD process improvement initiative described in Sections 3.1.2 and 3.2.4

2.0 APPLICABLE DOCUMENTS

Standard requirements documents (Government and Industry Specifications and Standards), reference texts, specific design requirements, and other references will be defined by individual Task Orders. The Government will apply commercial specifications and standards to the greatest extent reasonably possible.

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

The following list of general requirements documents and reference texts is a sampling of those that have been imposed by Task Orders in the past. The list is provided here for contractor reference only.

2.1 Government Specifications, Standards, Handbooks, and Publications

2.1.1 DoD-5000 Series Defense Acquisition

2.1.2 MIL-STD-1553 Aircraft Internal Time Division

2.1.3 MIL-STD-1760 Aircraft/Store Electrical Interconnection System

2.1.4 MIL-STD-2217 Requirements for Memory Loader/Verifier Multiplex Bus

Interface with Avionics Systems

2.1.5 NAVAIR 01-1A-505 Aircraft Electrical and Electronic Wiring

2.1.6 NAVAIRINST 4355.19 Systems Engineering Technical Review (SETR) Process

2.1.7 NAVAIRINST 5239.2 Naval Air Systems Command Information Systems Security

Program

2.1.8 NAVAIRINST 8012 Non-Nuclear Ordnance Non-Combat Expenditure

Requirements/Allocations

2.1.9 NAVAIRINST 13034 series Flight Test Requirements

2.1.10 NAVSO Pamphlet 3627 Earned Value Systems

2.1.11 NAWCWPNCENINST 7320.1 NAWCWPNS Equipment Management Manual (series)

2.1.12 NAWCWPNS WDPS NAWCWPNS Plant Property System

2.1.13 NAWCWPNSINST 3960.4 Project Test Plans for Test of Air Vehicles, Weapons, and

Installed Systems

2.1.14 OPNAV 43P6 Metrology Automated System for Uniform Recall and

Reporting (MEASURE) User’s Manual

2.1.15 OPNAVINST 4790 series Naval Aircraft Maintenance Program

2.1.16 OPNAVINST 5000.42D T&E Policy and Procedures, Encl. (13)

2.1.17 OPNAV 5100.23C Safety Ashore Manual

2.1.18 OPNAVINST 5239.1A Department of Navy ADP Security Manual

The following statements are for information only:

2.2 Clinger-Cohen Act: This clause is required in all IT procurements.

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.

Per CCA, OSD Memo of 08 Mar 2000, the DoD 5000.2 of 13 May 2003, and SECNAVINST 5000.2C of 19 Nov 2004, CCA compliance is required for all programs that contain IT, including IT in weapons and weapons system programs. The law provides authority to the agency’s CIO to manage IT resources effectively. The authority to grant compliance with CCA and approve the Information Assurance strategy depends on the Acquisition Category (ACAT).

2.3 System Software / Application Compliance:

"All Information Technology Systems or software/application development, modification or support shall be performed in accordance with Defense Business Transformation guidance (formerly Business Management Modernization Program (BMMP)), DON/NAVAIR Functional Area Manager (FAM) Policies and Guidance, Network and Server Registration, and Web Enablement mandates."

2.4 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 with MyNAVAIR (NAVAIR Corporate Portal) 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. OMB Management of Federal Information Resources, OMB CIRCULAR NO. A-130 Revised http://www.whitehouse.gov/omb/circulars_a130_a130trans4

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, 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 https://www.nioc-norfolk.navy.mil/wra/index.html

f. DON Policy for Content of Publicly Accessible World Wide Web Sites SECNAVINST 5720.47B http://www.doncio.navy.mil/PolicyView.aspx?ID=421

g. NAVAIR CIO Website (NAVAIR specific policy and guidelines https://mynavair.navair.navy.mil

h. DISA Hosting of All Navy Websites (NAVADMIN

061/08)http://www.npc.navy.mil/NR/rdonlyres/A4E463D0-02AF-4094-A054- BB1D807F631B/0/NAV08061.txt

i. Consolidation of Navy Web Sites - Reduction of IM/IT Footprint NAVADMIN 145/07 http://www.npc.navy.mil/NR/rdonlyres/787908B8-55E8-4A6F-9BD8- A74B3C0824F0/0/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/PolicyView.aspx?ID=577

2.5 Software Development/Server Procurement:

“Any tools developed that will be hosted by the Navy Marine Corps Intranet (NMCI) or run on NMCI workstations will be certified for NMCI and comply with NMCI policy. Additionally, any servers supporting this effort will be transitioned to meet the requirements of the current NAVAIR Server Consolidation effort.”

2.6 Information Assurance (IA): This is required on all DON Contracts:

NAVAIR’s Information Assurance (IA) 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. IA is required operationally throughout the DON. DON CIO (Chief Information Officer) 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 IA shall be in compliance with the following listed instructions to include those referenced within the below listing:

a. SECNAV M-5239.1 DoN Information Assurance Program; Information Assurance Manual

b. National Industrial Security Operating Manual (NISPOM)

c. CJCSI 6211.02 (series) --Defense Information System Network (DISN): Policy Responsibilities and Processes of 31 July 2003

d. CJCSI 6212.01 (series) --Interoperability and Supportability of Information Technology and

National Security Systems

e. DoDD 8100.1--Global Information Grid (GIG) Overarching Policy

f. DoDD 8500.1E--Information Assurance

g. DoDI 8500.2--Information Assurance Implementation

h. DoDI M-8510.1--DoD Information Technology Security Certification and Accreditation

Process (DITSCAP) Application Manual

i. DoDI 5200.40, “DoD IT Security Certification and Accreditation (C&A) Process (DITSCAP),”

30 Dec 1997

j. CNO N614/HQMC C4--Navy-Marine Corps Unclassified Trusted Network Protection (UTN-

Protect) Policy, Version 1.0, 31 October 2002”

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

(Incorporating Change 2, Feb 25, 2010)

l. DoDD 8000.01 “Management of the Department of Defense Information Enterprise,” February

10, 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 8500.01E (series), “Information Assurance (IA),” October 24, 2002, Certified Current as of April 23, 2007

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

p. DoDI 4630.8, “Procedures for Interoperability and Supportability of Information Technology (IT) and National Security Systems (NSS),” June 30, 2004

q. DoDI 8500.2, “Information Assurance Implementation,” February 6, 2003

r. DoDI 8510.01, “DoD Information Assurance Certification and Accreditation Process

(DIACAP),” November 28, 2007

s. DoDI 8520.2, “Public Key Infrastructure (PKI) and Public Key (PK) Enabling, April 1, 2004

t. DoDI 8551.1, “Ports, Protocols, and Services Management (PPSM),” August 13, 2004

u. DoDI 8580.1, “Information Assurance in the Defense Acquisition System,” July 9, 2004

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

w. 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

x. DON ltr 5239 NAVAIR 726/2322 of 18 Feb 09, “NAVAIR Data at Rest Policy”

y. Federal Information Processing Standards Publications (FIPS PUB)

[http://www.itl.nist.gov/fipspubs/by-num.htm]

z. (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,” June 17,

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

For more information on determining the applicability of these documents to the specific requirements of your program, contact your local information assurance point of contact for assistance. An IA Manager is available via the NAVAIR portal at https://mynavair.navair.navy.mil/portal/server.pt/gateway/PTARGS_32_0_856_01_47/http;/pxcpo013.nava ir.navy.mil;11930/collab/do/document/overview?projID=135128&folderID=247389

All IT procured on behalf of NAVAIR 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 subsequent to a NAVAIR contract, regardless of the level of data processed shall be operated and 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 IA 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 being connected to any DoD or NAVAIR network in support of this contract. Requirements include:

2.6.1 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;

2.6.2 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;

2.6.3 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 6212.11B;

2.6.4 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;

2.6.5 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.

2.7 Enterprise Architecture:

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 VPN Outreach service or NAVAIR CIO approved IP service.

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.

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.

IT Approval. The contractor shall not purchase any IT equipment on behalf of NAVAIR in support of a contract without a NAVAIR CIO signed IT approval.

2.8 Software Process Improvement Initiative (SPII)

The SPII Policy requires that standardized contract language be included in solicitations or contracts under which contractor(s) are required to perform “software development”.

As defined in the ASN Memorandum, Software Process Improvement Initiative (SPII) Guidance for Use of Software Process Improvement Contract Language dated 13 July 2007, “Computer Software development” or “software development” means, as applicable developing or delivering new source code, modifying existing source code, coding computer instructions and data definitions, building databases schema, and performing other activities needed to implement the design of a noncommercial computer software product.

This definition recognized that even small changes to software code can result in significant changes to software system behavior and quality, and, consequently, that it is necessary for developers to define and follow disciplined and appropriate processes.”

Mandatory elements of the SPII policy language are:

i. The requirement that Offerors submit a proposed Software Development Plan (SDP) with their proposals, and, during contract performance, deliver a completed SDP (based on the proposed SDP) as a Contract Data Requirements List (CDRL) deliverable, subject to Government review and approval.

ii. The information content of the SDPs, which shall follow the framework of IEEE/EIA Std 12207 regarding subject content, level of detail, and completeness.

iii. The requirement that the SDP serve during contract performance as the benchmark for the contractor’s software development effort.

iv. The requirement that the SDP shall be periodically evaluated and updated, as a part of continuous process improvement subject to Government review and approval.

Discretionary elements of the SPII policy language are:

i. Where the language is incorporated in the solicitation and contract.

ii. The format of the SDP (including whether it needs to be a single volume or may consist of multiple volumes.)

iii. The other elements of IEE/EIA Std 12207 that must be included, as based on the needs of the system to be acquired and its associated work content.

The policy and additional information can be found at http://acquisition.navy.mil/content/view/full/5144

2.9 Commercial Specifications, Standards, and Handbooks

2.9.1 ANSI STD X3.320-1994 Fibre Channel Standard

2.9.2 ANSI Y14.100 Engineering Drawing Practices

2.9.3 EIA-748 Earned Value Management Systems

2.9.4 J-STD-016 Standard for Information Technology Software Life Cycle

Processes, Software Development, Acquirer-Supplier Agreement

2.9.5 EIA/IEEE 12207 Information Technology -- Software Life Cycle Processes

2.9.6 IPC/EIA J-STD-001 Standard Requirements for Soldered Electrical and Electronic

Assemblies

2.9.7 SEI CMMI Version 1.1 CMMI Guidelines for Process Integration and Product

Improvement, ISBN: 0-3321-15496-7

2.10 Other Publications and Documents

"Agile Program Management with SCRUM" (Microsoft Professional) by Ken Schwaber "Capability Maturity Model Integrated for Development", Version 1.2, Guidelines for Process Integration and Product Improvement “Developing User Interfaces, Ensuring Usability Through Product & Process,” Hix and Hartson, Wiley “Object-Oriented Modeling and Design,” Rumbaugh, et al., Prentice Hall “Web Testing Handbook,” Steven Splain and Stefan P. Jaskiel, STQE Publishing

2.11 Sources for Publications and Documents

Internet on-line public and/or commercial sources for references cited above are:

http://www.dtic.mil/ http://www.disa.mil/ https://www.wpafb.af.mil/asc/index.asp/ http://www.sei.cmu.edu/ http://www.nssn.org/ http://www.ieee.org/portal/site/ http://www.eia.org/ http://www.tiaonline.org/standards/ http://www.document-center.com/ http://www.defenselink.mil/pubs/ http://www.amazon.com/

2.12 Publications Available Post-Award

The following references may be imposed on this contract and will be made available to the contractor only after award:

NAWCWPNSINST 3960.1 NAWCWPNS Flight Test Plans (For Official Use Only) NAWCWPNSINST 3960.4 Project Test Plans for Test of Air Vehicles, Weapons, and Installed

Systems (For Official Use Only) NAWSCLINST 5510.2 Foreign National Visitors/Disclosures (For Official Use Only) NAWSCLINST 5510.3 Information and Personnel Security Program, current version (For

Official Use Only) NWC IDP 3736 Security Guidelines (For Official Use Only) NWC TM 6928 Software Tailoring Plan Navy 5000 Series Publications

3.0 REQUIREMENTS

3.1 General

3.1.1 Definition of Customer

This contract provides products and services to the NAWCWD, and any successor entity to the NAWCWD, performing the mission currently performed by the NAWCWD.

3.1.2 Process Improvement Initiatives & Innovations (also see 3.3.3.3) Contractor personnel shall be knowledgeable regarding the established work process definition documents under each Task Order and shall actively work together with other contractor and Government personnel to establish, maintain, and continuously improve the NAWCWD work environment and ongoing process improvement initiatives.

3.1.3 Contractor Training

The Government may provide (on a space-available basis) special mandatory training to the contractor in the areas of military systems (ex. UAV), training mandated for all personnel working at the NAWCWD

(ex. Combatting Trafficking in Persons) or accessing Government systems, and other Government-required training. The contractor shall complete all applicable training required by the individual task orders.

3.2 Contractor Program Management, Reporting, and General Performance Requirements

3.2.1 Tracking & Oversight

The contractor shall establish and maintain a management system for controlling cost, schedule, and performance. The contractor shall maintain a cost accounting system that shall track, report, and invoice on actual expenditures for each Task Order. Additionally, the contractor’s cost accounting system shall be capable of tracking, reporting, and invoicing at the Work Breakdown Structure (WBS) level 3 within each Task Order, when specifically required by the Task Order.

3.2.2 Periodic Contract Status Reporting

The specific content, periodicity, delivery, and format (if applicable) requirements of each Report defined below are defined in Exhibit A. The general Report descriptions provided below may be superseded by the requirements specified in Exhibit A. The contractor shall present a proposed format and negotiate with the Government the final format for CDRL A009 not later than the first day of performance of the contract.

The contractor shall present a proposed format and negotiate with the Government the final format for CDRL A002 within the first week of performance of the contract. The contractor shall present a proposed format and negotiate with the Government the final format for CDRLs A001, A003 through A006, and A00B within the first two (2) weeks of performance of the contract. The contractor shall present a proposed format and negotiate with the Government the final format for CDRLs A007, A008, and A00C within the first month of performance of the contract.

3.2.2.1 Monthly Task Order Progress/Status Report (MSR): The contractor shall provide Monthly Task Order Progress/Status Reports for each Task Order, outlining work accomplished, problems encountered, problems solved, trip report(s), items delivered, current schedule, total hours worked/remaining on the contract, cost information, and monthly, total funds, and hours expended. Task order requirements may specify additional reporting items. The cost information shall include trend analysis graphs (labor and financial costs) to assist the Government in determining the status of each Task Order. (See Exhibit A, CDRL A001)

3.2.2.2 Weekly Task Order Expense Status Report: The contractor shall prepare and submit a Weekly Task Order Expense Status Report reflecting Task Order status relative to expense of dollars and labor hours. The Report shall reflect the contractor’s “best estimates” of actual dollars and labor hours expended through the end of the previous week, and projections of weekly “burn rate,” “stop work” date, and variances from expected expense plan. (See Exhibit A, CDRL A002)

3.2.2.3 Quarterly Contractor Personnel Reports: The contractor shall prepare and submit a Quarterly Employee Listing Report, a Quarterly Personnel Location Report, and a Quarterly Personnel Count by Labor Category Report. (See Exhibit A, CDRLs A003 and A005)

3.2.2.4 Monthly Contract/Task Order Summary Report: The contractor shall prepare and submit a Monthly Contract/Task Order Summary Report. The Report shall provide financial and labor hours data for each Task Order and contract cumulates. (See Exhibit A, CDRL A006)

3.2.2.5 Contractor Performance Self Evaluation Report: The contractor shall prepare and submit a Contractor Performance Self Evaluation for each evaluation period. (See Exhibit A, CDRL A007)

3.2.2.6 Semiannual Contract Historical Reporting: The contractor shall prepare and submit semiannual tabular and graphical presentations of defined labor hour and financial data. (See Exhibit A, CDRL A008)

3.2.2.7 Contract Data Product Summary: The contractor shall deliver a CD or DVD archiving all contract-level data products submitted from contract inception through "as of" date of this data product.

(See Exhibit A, CDRL A009)

3.2.2.8 Semiannual Contract Direct Labor Expenditure Report. The contractor shall submit a Semiannual Contract Direct Labor Expenditure Report identifying the percentage of direct labor dollars expended by the Prime and Subcontractors (See Exhibit A, CDRL A00A).

3.2.2.9 Quarterly Average Labor Cost Hourly Rate Report. The contractor shall submit a Quarterly Average Labor Cost Hourly Rate Report documenting the current unburdened direct labor rates for Government use in estimating future costs (See Exhibit A, CDRL A00B).

3.2.2.10 Estimate to Complete - Estimate at Completion (ETC-EAC) Report. The contractor shall prepare and submit an ETC-EAC Report (see Exhibit A, CDRL A00C) for each Task Order that accurately documents expenses (labor hours and costs) to the end of the reporting period and estimates expenses to complete the Task Order phase. It is recommended that the contractor solicit input from the Government technical customers relative to work to be assigned and events projected to occur during the remaining period of the Task Order phase.

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

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

3.2.2.12 Operations Security (OPSEC) Plan: The contractor shall submit an OPSEC Plan in accordance with CDRL A00D (see Exhibit A).

3.2.3 Security and Classified Data

3.2.3.1 NAVAIR Security Process: During performance under this contract, the contractor shall comply with the contractual Form DD-254 and applicable NAVAIR security processes. Additional Task Order specific information, if any, will be provided within the Task Orders.

3.2.3.2 Special Classified Data and Information (see contractual Form DD-254): Contractor performance related to certain IPT-supported aircraft equipment, avionics, sensors, etc. may involve access to: (1) classified information up to the TOP SECRET level, (2) cryptographic keys and data, (3) restricted and formerly restricted data, (4) foreign-nation weapons and sensors intelligence data requiring INTEL and NOFORN clearances, (5) NATO information, and (6) SIPRNET. Contractor personnel performing tasks that require access to cryptographic keys and data, and foreign-nation weapons and sensors intelligence data, shall satisfactorily complete the relevant Government-provided security training, including COMSEC certification training.

3.2.3.3 Foreign Military Sales (FMS): Contractor personnel working in support of FMS tasking shall interface or work with foreign-nation personnel as required, with any required Government oversight.

Those contractor personnel shall satisfactorily complete special Government-provided security training in this area when such training is required.

3.2.3.4 Security Responsibilities: The contractor shall comply with DD Form 254 and NAWCWD Security requirements, policies, practices, and procedures. Special Security requirements may be defined at the task order level.

3.2.3.5 Computer Security: Contractors with Government-furnished computer equipment connected to the NAVAIR’s computer networks shall comply with OPNAVINST 5239.1A and shall complete the NAVAIR Accreditation Package when required.

3.2.3.6 Special Access Information: The contractor may be granted access to SPECIAL ACCESS INFORMATION for some tasking within this Statement of Work. When this is applicable, it will be identified in the Task Order level form DD-254. When access to SPECIAL ACCESS INFORMATION is granted, it will be for access to information only at another contractor's facility or a Government activity.

3.2.4 Systems Engineering and Software Process Improvement

The contractor shall provide Systems Engineering and Software Process Improvement for NAWCWD’s active program to improve its processes to a higher maturity level in accordance with the Capability Maturity Model, Integrated (CMMI) principles developed by the Software Engineering Institute (SEI) (Levels 1 - 5). The SEI is a Defense Department sponsored organization located at the Carnegie Mellon University. Some NAWCWD groups have already been certified at Level 5. Other NAWCWD customer Code groups will be striving to attain certification at maturity levels 3-5 within the period of performance of this contract. The contractor shall participate in this program. While the Government is the “process owner,” the contributions of process users are vital to the success of this program. It is the overall collection of process users that achieves the CMMI certification.

3.2.5 Transportation and Leased Vehicle Requirements

The contractor shall provide all vehicles required for the performance of this contract unless shared access is authorized by the Government. Contractor personnel may use Government Owned Government Operated (GOGO) vehicles managed through the Transportation Office, NAVFAC Southwest, Code 270, under the following conditions: Contracting Officer’s Representative (COR) concurrence with the contractor’s need to use GOGO vehicle(s); COR oversight to ensure compliance with DoD 4500.36-R;

clause 5252.228-9501, LIABILITY INSURANCE is included in this contract and applies to the use of GOGO vehicles; the contractor shall meet all training and licensing requirements to operate the GOGO vehicles and equipment, as defined in NAVFAC P-300; the contractor need for GOGO vehicles and equipment shall not interfere with Government use of those vehicles and equipment; and use of GOGO vehicles is for work on a Government site and is for official use only for specific Task Order requirements.

The vehicle costs (including vehicle lease costs when all other options are exhausted) directly (and proportionally, if applicable) related to the transportation needed to support contractor performance requirements shall be invoiced against the task order(s) defining the tasking needing transportation. The Government may provide contractor access to Government fuel pumps for refueling (at Government expense) of vehicles performing transportation in response to the requirements of this contract. If provided, Government fuel pump access will be specified at the Task Order level

3.2.5.1 General Transportation Requirements: Contractor performance is required in a number of locations, many of which are accessible by paved roads, but some of which require effective and reliable off-road transportation. Worksites can be remote and/or limited in the number and type of vehicles that they can accommodate. The contactor may be responsible for moving hardware and test equipment; and for towing loads including but not limited to equipment trailers, weapons, and test modules on an as-needed basis. The contractor shall ensure that the transportation equipment that is used in contract performance meets all relevant Navy standards specified at the Task Order level. The vehicle costs (including vehicle lease costs) directly (and proportionally, if applicable) related to the transportation needed to support contractor performance requirements shall be invoiced against the task order(s) defining the tasking needing transportation. The Government may provide contractor access to Government fuel pumps for refueling (at Government expense) of vehicles performing transportation in response to the requirements of this contract. If provided, Government fuel pump access will be specified at the Task Order level. The contractor shall ensure that contractor personnel who drive vehicles on Base shall have a valid driver's license and vehicle insurance coverage, per FAR 52.228-7, and shall meet any other Government requirements that may be imposed upon drivers operating vehicles on Base.

3.2.5.2 Special Flight Line Transportation and Training Requirements: The contractor shall provide and operate vehicles on the flight line when required by individual Task Orders. The contractor shall coordinate with the Naval Air Weapons Station (NAWS) Air Operations Manager (Code 850000D) to ensure that special vehicle requirements (such as marking, communications radio, and operator training for airfield ramp operations) are met, prior to operating vehicles on the flight line. The Government will train and license contractor personnel on an as-needed basis to perform the following restricted special vehicle activities: operation of any vehicle within the flight line area, operation of flight line test support equipment, and for in-cockpit aircraft avionics and systems testing under ground support power.

Contractor personnel operating vehicles on the flight line shall pass all relevant Navy required training, as evidenced by receipt of a Navy Flight Ramp Vehicle License.

3.2.6 Contractor and NAWCWD-Provided Facilities

The contractor shall establish a facility within ten miles of the main gate that meets the security requirements as outlined in the attached DD Form 254. The contractor shall provide workspaces within the contractor facility for approximately 5% of the contractor’s technical staff. Contractor personnel working from the contractor facility may require frequent access to the lab and test facilities at the NAWCWD and frequent interface with Government and other contractor personnel at the NAWCWD. Costs for travel between the contractor's facility and the NAWCWD shall not be directly charged to the contract.

NAWCWD work-spaces will be provided for the remaining 95% of the contractor’s technical staff located at China Lake and Pt. Mugu. Government-provided work-spaces include, as necessary, desks/cubicles, computer equipment, telephone, special equipment, and supplies necessary for performance.

3.2.7 Contract Phase-Out

The contractor shall prepare and submit a Contract Phase-Out Plan describing the completion or transition of work in progress and the professional and orderly transition of contract responsibilities at the end of the contract’s period of performance. (See Exhibit A, CDRL A00E)

3.2.8 Trained Contractor Work Force

The contractor shall provide a work force properly trained (and certified, if required) to perform all tasking defined within this Statement of Work (SOW). If tasking requires certification and/or periodic recertification (examples: soldering and certain tasking related to computer system operation/administration), the contractor is responsible for the costs of certification and, if required, periodic recertification. Some technology areas supported by this SOW are continually evolving. The contractor shall provide advanced technology training to their personnel assigned to evolving technology work areas.

3.3 Technical Performance Requirements

Individual Task Orders will specify specific products and services to be delivered. The sections below provide additional definition of the range and types of tasking that the contractor may receive via Task Orders. Each Task Order will include a Statement of Work (SOW) and related DD Form 1423, Contract Data Requirements List (CDRL) for data deliverables. The CDRLs will define the required format, delivery requirements, periodicity, and other requirements for all data deliverables. Task order requirements may require contractor non-local travel (both domestic and foreign, including aboard Government ships-at-sea, aboard Government aircraft, and to war zone areas). The contractor shall not perform as both requirements developer and acceptance tester for any product.

3.3.1 Systems Integration

The contractor shall perform system integration to include integration of weapons, avionics, sensors, targeting systems, system hardware and software (including system analysis, research, development, engineering, testing, test equipment design, fabrication, maintenance, mission simulation, and interoperability assurance).

3.3.1.1 The contractor shall perform research and development and shall support systems engineering for supported systems. The contractor shall also provide systems analysis consisting of analytical studies of supported systems and analysis of FMS releasability. Additionally, the contractor shall perform system software design and development (D&D) and verification and validation (V&V) testing for supported systems.

3.3.1.2 The contractor shall research, analyze, perform engineering investigations, and document new and/or modified weapons, sensors, targeting systems, aircraft computers, avionics systems, databus architectures, trainers, and related software and systems (including EW systems) being considered for integration into the NAWCWD supported aircraft (or related systems), as well as associated pre- and post-flight support systems, simulators, and/or other test and support equipment hardware and software for any of the above.

3.3.1.3 The contractor shall provide trade-off studies, analyses, engineering and anomaly investigations and recommendations involving supported aircraft and/or systems.

3.3.1.4 The contractor shall research, analyze, and document operational concepts for system and subsystem performance.

3.3.1.5 The contractor shall conduct studies and analyses to support system definition requirements, human factors and pilot-vehicle interface considerations.

3.3.1.6 The contractor shall provide weapons delivery performance analyses and fire control algorithm design, modification, and/or implementation.

3.3.1.7 The contractor shall perform and/or support system, mission, and operational simulations;

including documentation, studies, analysis, and recommendations regarding simulations.

3.3.1.8 The contractor shall perform system performance analyses, including, but not limited to, malfunction monitoring, fault location and isolation, loading, optimization, compensation methodologies, reconfiguration, and associated tasks for software and hardware. Software performance analysis shall include the determination of optimum utilization of both hardware and software system assets.

3.3.1.9 The contractor shall provide analysis and reporting of data derived from various levels and stages of testing. As part of this effort, the contractor shall perform research and analysis of advanced tools and methods for data reduction and analysis. The contractor shall design and develop test related tools, methodologies, and test hardware (including building and maintaining of test hardware).

3.3.1.10 The contractor shall perform system D&D and V&V testing for supported systems. The contractor shall conduct laboratory, simulation, and ground testing, provide flight test support (including test planning, safety of flight testing, and regression testing), test design, test procedure development, test preparation, test conduct and monitoring, and post-test data collection, analysis, and reporting) to evaluate system and subsystem operation. The contractor shall perform D&D and V&V review and testing to include the following sampling of typical requirements:

(a) Criticality analyses;

(b) Documentation review;

(c) Test planning;

(d) Trace requirements through design, implementation, and test;

(e) Check compliance to standards, conventions, specifications, and FMS releasability;

(f) Prepare D&D and V&V test plans, test working documents (TWDs), and test procedures

(including ready for flight, safety of flight, and regression testing);

(g) Test preparation (including pre-test verification of the operability of test assets, setup of test assets, design, building, and placement of test assets and targets);

(h) Conduct of system/subsystem testing;

(i) Perform laboratory, simulation, and ground tests and provide flight test support necessary to evaluate function and performance (including escort of test visitors within NAWCWD secure areas);

(j) Operation of test assets (including piloting of Unmanned Air Systems or performing as "Mission Commander" for test events);

(k) Test documentation (including post-test data collection, analysis, and reporting).

3.3.1.11 The contractor shall provide performance analyses of test results from system and subsystem testing.

3.3.1.12 Test Laboratory and Support Equipment Requirements Development Support -- The contractor shall identify and document any coincidental upgrades or modifications to the test labs, associated software, support or test equipment necessary to perform developmental, validation, and acceptance testing.

3.3.1.13 The contractor shall research, analyze, report, and document advanced technology concepts, tools, methods, hardware, and software for real-time embedded computing and supported systems.

3.3.2 Software Development, Programming, Test, and Integration -- Software engineering/development for aircraft computers, avionics, sensors and targeting systems, weapons systems, test laboratories, simulators, and mission/system support equipment (including Software Quality Assurance (SQA), Software Configuration Management (SCM), and Verification and Validation (V&V)).

3.3.2.0 General -- This Section covers contractor performance related to the prototyping, development, coding, maintenance, and code development testing of software for the computers on aircraft assigned to NAWCWD, associated tactical support equipment, and other interfacing systems.

3.3.2.1 Prototyping/Development/Maintenance/Testing of Subsystem Software

3.3.2.1.0 The contractor shall support development and maintenance of systems/subsystems software that include, but are not limited to: the mission computer(s), stores management system, radar, navigation, displays, electronic warfare systems, sensors, pilot-vehicle interface, and other avionics and support systems of NAWCWD-supported aircraft and related systems.

3.3.2.1.1 The contractor shall support software research and development, requirements definition, architecture and detailed design, coding, development and module integration testing (including Verification and Validation testing), and develop and maintain related documentation.

3.3.2.1.2 The contractor shall provide software problem-analysis and documentation. The contractor shall investigate and evaluate reported software problems and propose problem solutions and enhancements.

3.3.2.2 Software Project Support

3.3.2.2.0 The contractor shall support activities surrounding the software engineering task performed by the NAWCWD IPTs for NAWCWD supported aircraft and airborne and related projects. Note: The contractor shall not be the product acceptance authority for any software product developed by the contractor.

3.3.2.2.1 The contractor shall support software design, development, validation, test, acceptance, operation, maintenance, and modification of aircraft weapon systems and associated subsystems software, including mission support and related systems.

3.3.2.2.2 The contractor shall support other software project activities; such as: product assurance (Software Quality Assurance (SQA) and Software Configuration Management (SCM)); database design, development, and maintenance; metrics collection, analysis, and reporting; and process improvement. The contractor shall provide data entry, data verification, and data maintenance on existing database systems.

3.3.2.2.3 The contractor shall support product reviews and testing during the various project phases, including the following typical services: the conduct of traceability analyses; standards compliance reviews; the performance of peer reviews; escort of review attendees within NAWCWD secure areas, and the planning, preparation, and conduct of system/subsystem testing.

3.3.2.3 Any software tools developed by the contractor that will be hosted by NMCI or run on NMCI workstations shall be certified for NMCI and comply with NMCI policy. Any software tools developed by the contractor that are to be run in the RDT&E environment shall be certified and in compliance with Navy security and RDT&E policy.

3.3.3 Program-Level Support -- IPT program-level services (including special technical research, studies, Quality…