LTC_PWS_7-31-2014_Rev_2.2_Updated_8-25-14.doc

Performance Work Statement (PWS)

Launch Test Capability

07/31/2014 Version 2.2 CLIN 0001 – The Contractor shall provide assistance in the development of a launch test complex for prototype testing and qualification of a launcher subsystem in accordance with the Performance Work Statement (PWS).

CLIN 0002 – The Contractor shall provide Travel in support of CLIN 0001 and in accordance with the Performance Work Statement.

CLIN 0003 –The Contractor shall provide data in accordance with the Performance Work Statement Sections and Exhibit A, DD Form 1423, CDRLs.

1.0 Scope

The objective of this Performance Work Statement (PWS) is to provide design and development, site activation, test and evaluation, and sustainment of the Launch Test Complex at China Lake, CA, for prototype testing and qualification of a missile launcher subsystem. The LTC will allow testing that will provide data verifying the system’s ability to achieve eject performance, as well as analyze design deficiencies to ensure the system installation can support the overall production schedule.

Tasking associated with this PWS includes developing, updating and maintaining the: Control and Data Acquisition System (CDAS); Launch Test System (LTSYS); Launch Test Stand (LTS), Launch Test Vehicle (LTV); and Launcher portions of the Concept of Operations (CONOPS). Additional tasking shall include: providing safety risk mitigation analysis; performing launch and arrestment simulations; developing, testing, and installing the CDAS; developing installation plans for the CDAS, LTSYS, LTS and LTV; ensuring compliance with the Interface Control Documents (ICDs) for CDAS, LTSYS, LTS and LTV; providing Earth Based Arrestment (EBA) media; developing the test site maintenance and sustainment plans for the LTC; maintaining the LTC complex; and providing maintenance, modifications, and repairs for the CDAS, LTS, LTV, Launcher, and LTC complex during the period of performance of this requirement.

1.1 Background

The Naval Air Warfare Center Weapons Division (NAWCWD) is a member of the LTC Integrated Product Team (IPT), comprised of Government and industry, to provide specific expertise and experience necessary to achieve success in the development of a timely, cost-effective launch test capability. NAWCWD Weapons and Energetics Department (470000D) has been tasked with assisting with the development of a test capability for prototype testing and the qualifying of a launcher subsystem. This requirement includes testing to provide data to verify the ability to achieve eject performance.

The LTC project requires two testing series, evaluation testing and qualification testing, which are directly related to the design and qualification of the launcher subsystem. Currently, the design, development, fabrication, qualification, and ultimate delivery of the launcher subsystem to the shipyard are critical path for the program.

2.0 Applicable Documents

The following documents apply to the work under this contract and will be provided by the Government. The most current versions will be used. Additional documentation may be provided by the Government over the course of the contract. Documents not publicly available will be provided.* LTC Requirements Document (WS32300)

LTC CONOPS Document (OD68896) LTF Requirements Document (WS32303)

Facility Design Criteria

LTV-LTF Interface Control Document (ICD) (LTC-ICD-24-001)

LTS-LTF ICD (LTC-ICD-14-001)

CDAS-LTF ICD (LTC-ICD-34-001)

Launcher-LTF ICD (LTC-ICD-L4-001)

LTS-CDAS ICD (LTC-ICD-13-001)

LTV-CDAS ICD (LTC-ICD-23-001)

CDAS Requirements Document (WS32302)

LTF most current submittal

* The Government will provide all necessary reference documents not generally available to the Contractor, as required. 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.

It is the Government's responsibility to ensure that any "IT" procurement (hardware/hardware maintenance, software/software maintenance, support services, web services, telecommunications, etc.) procured by the Contractor under the scope of this Contract meets the requirements defined in sections 2.1, 2.2, 2.3, and 2.4 of this PWS.

2.1 Information Technology Information

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 Information Technology (IT) equipment on behalf of NAVAIR in support of this Contract without Naval Air Systems Command (NAVAIR) Command Information Officer (CIO) signed IT approval.

2.2 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 IT in weapons and weapons system programs. The law provides authority to the agency’s Chief Information Officer (CIO) to manage IT resources effectively. The authority to grant compliance with CCA and approve the Information Assurance (IA) strategy depends on the Acquisition Category (ACAT).

a. DoDD Number 5000.01 The Defense Acquisition System, May 12, 2003, Certified Current as of 20 November 2007

b. DoDI 5000.02 Interim, Operation of the Defense Acquisition System, 25 November 2013

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

d. SECNAVINST 5000.2E, Implementation and Operation of the Defense Acquisition System and the Joint Capabilities Integration and Development System, 01 Sept 2011

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)), Department of the Navy (DON)/Naval Air Systems Command (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 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 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 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/secnav5720www.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/bupers‐ npc/reference/messages/Documents/NAVADMINS/NAV2008/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 Navy Sites (ALCOM 129/09) http://www.public.navy.mil/fcc‐c10f/niocnorfolk/Documents/NTD‐08‐09.txt

2.4 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.5 Information Assurance (IA):

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. 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 IA 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.01G (series), Joint Capabilities Integration and Development System, 1 March 2009

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

d. CJCSI 6212.01F Net Ready Performance Parameters (NR KPP) 21 March 2012

e. CJCSI 6250.01D (series) – “Satellite Communications,” 17 Feb 2010

f. CJCSI 6510.01E, Information Assurance (IA) and Computer Network Defense (CND), 09 Feb 2011, certified current 10 Oct 2013

g. Chairman of the Joint Chiefs of Staff Manual CJCSM 6510.01B – 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, 28 February2006 (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 8500.01E (series), Information Assurance (IA), October 24, 2002, Certified Current as of 23 April 2007

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

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

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

r. DoDI 8510.01, DoD Information Assurance Certification and Accreditation Process (DIACAP), 28 November 2007

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

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

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

v. DoDI 8581.01, Information Assurance (IA) Policy for Space Systems Used by the Department of Defense, 8 June 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

ab. SECNAV M-5239.1, Department of the Navy Information Assurance Program; Information Assurance Manual, November 2005

ac. SECNAVINST 5230.15, Information Management/Information Technology Policy for Fielding of Commercial Off the Shelf Software, 10 April 2009

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

ae. SECNAVINST 5239.19, Department of the Navy Computer Network Incident Response and Reporting Requirements, 18 March 2008

af. The National Security Act of 1947

ag. Title 40/Clinger-Cohen Act

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, are subject to validation scanning, and must be approved by the NAVAIR site IA Manager prior to connection. 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.

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

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

3.0 Performance Requirements (CLIN 0001)

The following section specifies the Performance Objectives and Performance Elements for the LTC project.

3.1 Design & Development

3.1.1. The contractor shall develop the CDAS, LTSYS, LTS, LTV, and Launcher portions of the CONOPS for the LTC project site activation, test and evaluation, and post operations and maintenance phases. (CDRL A001)

3.1.1 Standards:

(1) CDAS, LTS, LTV, and Launcher portions of the CONOPS are accurate, complete, executable, operationally relevant, maintainable, and meet the program schedule.

AQL: 100%

(2) All data submissions are complete and accurate IAW with DID and all applicable policies and procedures.

AQL: 100%

3.1.2 The contractor shall conduct and provide safety risk mitigation analysis for the LTC project.

3.1.2.1 The contractor shall conduct Air Dispersion analysis for the LTC project to evaluate the LTSYS gaseous and aerosol plume release, transport, dispersion and deposition to land surfaces downwind of the test site. (CDRL A002)

3.1.2.2 The contractor shall conduct meteorological data collection and analysis for design and development of the LTC project to support the Air Dispersion modeling and to assist in developing a CONOPS for the LTSYS that minimizes test derived environmental impacts while meeting the operational objectives of the LTC project. The contractor shall participate in the development of gaseous and aerosol plume contaminant mitigation design and evaluation. (CDRL A002)

3.1.2.3 The contractor shall provide magnetometer surveying and analysis for the LTC project in an attempt to locate any unexploded ordnance that may be buried in a landfill or significant other buried objects within the operational area that could impede fabrication or operation of the LTSYS. (CDRL A002)

3.1.2.4 The contractor shall conduct and provide test site safety risk assessment in accordance with MID-STD-882. (CDRL A004)

3.1.2 Standards:

(1) Accuracy and execution is shown through analysis reports that meet program schedules and addresses all program areas, analytically viable data, and implementable recommended solutions.

AQL: 100%

(2) All data submissions are accurate and IAW with DID and all applicable policies and procedures.

AQL: 100%

3.1.3 The contractor shall provide field design and analysis during fabrication of the LTC and installation of the arrestment system. This support shall include, but is not limited to the following: drawing reviews, assisting with special test equipment tests prior to shipment, and aiding in the resolution of fabrication issues. The contractor shall also provide on-site support during the start-up and operation of the site.

3.1.3 Standards:

(1) Accurately addresses all program areas during field design and analysis during fabrication and is comprehensive, executable, and mitigates risk.

AQL: 100%

3.1.4 The contractor shall perform launch and arrestment simulations for the LTC project. The contractor shall document and report the data based on the outcome of the simulations. (CDRL A006)

3.1.4.1 The contractor shall provide test plans and procedures for the launch and arrestment simulations. (CDRL A005)

3.1.4.2 The contractor shall provide all test equipment and materials for the launch and arrestment simulations. The contractor shall comply with the approval procedures stated in paragraph 6.0.

3.1.4 Standards:

(1) Accurate and useable data for arrestment simulations is provided in the test plans. Procedures and inspection reports are executable, accurate, and meet the technical specifications.

AQL: 100%

(2) All data submissions are accurate and IAW DID and all applicable policies and procedures.

AQL: 100%

3.1.5 The contractor shall develop, test and install the CDAS for the LTC project.

3.1.5.1 The contractor shall document and provide analysis of the CDAS requirements, and shall include the development of its system architecture for the CDAS. (CDRL A007)

3.1.5.2 The contractor shall provide all hardware for the CDAS. This includes, but is not limited to computers, instrumentation, cabling, data acquisition equipment, and racks. The contractor shall comply with the approval procedures stated in paragraph 6.0.

3.1.5.3 The contractor shall provide testing of developmental and final systems for the CDAS. (CDRL A006)

3.1.5.4 The contractor shall install the CDAS hardware and software for the LTC project. The contractor shall demonstrate that the installed CDAS is operational and functioning as designed. (CDRL A006)

3.1.5.5 The contractor shall develop and provide calibration methods and documentation for the CDAS. (CDRL A008) 3.1.5.6 The contractor shall develop and provide a preliminary and a final maintenance plan, due 60 days prior to operations and sustainment for the CDAS. (CDRL A009)

3.1.5 Standards:

(1) Accurate, usable, and executable data is provided in order to develop and test the CDAS.

AQL: 100%

(2) All data submissions are accurate and IAW with DID and all applicable policies and procedures.

AQL: 100%

3.1.6 The contractor shall develop installation plans for the CDAS, LTSYS, LTS, and LTV. (CDRL A00E)

3.1.6.1 The contractor shall provide the lifting operating procedures for all activities at the LTC complex in accordance with the LTC CONOPS Document #OD68896. (CDRL A00A)

3.1.6.2 The contractor shall provide the designs for installation of the CDAS, LTSYS, LTS, and LTV, as well as the special test equipment within the LTSYS. (CDRL A00B)

3.1.6.3 The contractor shall provide testing methods to verify that the LTC project design requirements are met. (CDRL A005)

3.1.6 Standards:

(1) Installation plans for the CDAS, LTSYS, LTS, and LTV are accurate and comprehensive.

AQL: 100%

(2) All data submissions are accurate and IAW with DID and all applicable policies and procedures.

AQL: 100%

3.1.7 The contractor shall ensure compliance with the Interface Control Documents (ICD), listed in Section 2.0, for the Launcher, LTSYS, LTS, CDAS, and LTV.

3.1.7.1 The contractor shall analyze and document verification opportunities with respect to the ICDs during the critical phases of the facility fabrication and site activation for LTS, LTSYS, CDAS, LTV, and Launcher. (CDRL A003)

3.1.7.2 The contractor shall identify and document midpoint inspections during facility fabrication for the LTS, CDAS, LTV, and Launcher installation. (CDRL A006)

3.1.7.3 The contractor shall document and report any ICD compliance issues in paragraph 3.1.7.2 for the LTS, CDAS, LTV, and Launcher installation. (CDRL A002) 3.1.7.4 The contractor shall develop methods and perform inspections to verify compliance with the ICD between the LTV, LTS, and CDAS. (CDRL A005)

3.1.7 Standards:

(1) ICD’s address all program areas and are accurate, comprehensive, executable, and meet technical standards.

AQL: 100%

(2) All data submissions are accurate and IAW with DID and all applicable policies and procedures.

AQL; 100%

3.1.8 The contractor shall provide Earth Based Arrestment (EBA) media for the LTC complex that meets the characteristics identified under contract N68936-09-D-0040, Task Orders 0130 and 0231.

3.1.8 Standards:

(1) Media provided meets technical specifications.

3.1.9 The contractor shall design and develop thermal conditioning systems for the ordnance and ordnance magazines IAW LTC Requirements Document (WS32300) and the LTC CONOPS Document (OD68896).

3.1.9 Standards.

(1) Design and development of the thermal conditioning systems for ordnance and ordnance magazines are accurate and meet technical specifications.

AQL: 100%

3.1.10 The contractor shall provide ordnance magazines for storage at the LTC complex as defined in the LTC Requirements Document (WS32300) and the LTC CONOPS Document (OD68896).

3.1.10 Standards:

(1) Ordnance magazines provide storage that is usable and meets technical specifications.

AQL: 100%

3.2 Site Activation

3.2.1 The contractor shall update the CDAS, LTSYS, LTS, LTV, and Launcher portions of the CONOPS for the LTC project.

3.2.1.1 The contractor shall update the CDAS, LTSYS, LTS, LTV, and Launcher portions of the CONOPS for site activation, test and evaluation, and post operations and maintenance phases. (CDRL A001)

3.2.1 Standards:

(1) CDAS, LTS, LTV and Launcher portions of the CONOPS are accurate, complete, executable, operationally relevant, maintainable, and meet the program schedule.

AQL: 100%

(2) All data submissions are accurate and IAW with DID and all applicable policies and procedures.

3.2.2 The contractor shall insert the media into the EBA. The contractor shall also develop installation and maintenance plans for the EBA media for the LTC complex. (CDRL A009)

3.2.2 Standards:

(1) Insertion of the media meets technical specifications.

AQL: 100%

(2) All data submissions are accurate and IAW with DID and all applicable policies and procedures.

AQL: 100%

3.2.3 The contractor shall develop the test site maintenance and sustainment plans for the LTC project. (CDRL A009)

3.2.3 Standards:

(1) The development of site maintenance and sustainment plans is accurate, addresses all program areas, and is comprehensive.

AQL: 100%

(2) All data submissions are accurate and IAW DID and all applicable policies and procedures.

AQL: 100%

3.2.4 The contractor shall ensure compliance via inspections, demonstration, test, analysis, or by any other means available with the ICDs listed in Section 2.0, for the Launcher, LTSYS, LTS, CDAS, and LTV. (CDRL A006)

3.2.4.1 The contractor shall document and report any post fabrication ICD compliance issues for CDAS, LTS, LTV, and Launcher installation. (CDRL A006)

3.2.4 Standards:

(1) ICDs are accurate, address all program areas, comprehensive, executable, and meet technical specifications.

AQL: 100%

(2) All data submissions are complete and accurate IAW DID and all applicable policies and procedures.

AQL: 100%

3.2.5 The contractor shall conduct and provide safety risk mitigation analyses for site activation of the LTC project.

3.2.5.1 The contractor shall conduct Air Dispersion analysis for the LTC project to evaluate the LTSYS gaseous and aerosol plume release, transport, dispersion, and deposition to land surfaces downwind of the test site. (CDRL A002)

3.2.5.2 The contractor shall conduct meteorological data collection and analysis for design and development of the LTC project to support the Air Dispersion modeling and to assist in developing CONOPS for the LTSYS that minimize test derived environmental impacts while meeting the operational objectives of the LTC project. The contractor shall participate in the development of gaseous and aerosol plume contaminant mitigation design and evaluation. (CDRL A002)

3.2.5.3 The contractor shall provide magnetometer surveying and analysis for the LTC project in an attempt to locate any unexploded ordnance that may be buried in a landfill, or significant other buried objects, within the operational area that could impede fabrication or operation of the LTSYS. (CDRL A002)

3.2.5.4 The contractor shall conduct and provide test site safety risk assessment IAW MID-STD-882. (CDRL A004)

3.2.5 Standards:

(1) Safety risk mitigation analysis addresses all program areas, and is accurate, executable, and meets technical specifications, and data is useable for analysis. Recommended solutions and procedures are implementable, and align with the schedule.

AQL: 100%

(2) All data submissions are accurate and IAW DID and all applicable policies and procedures.

AQL: 100%

3.2.6 The contractor shall provide aid in the resolution of fabrication and installation issues and general support during site activation.

3.2.6 Standards:

(1) Accurately addresses all program areas during aid and support of fabrication and installation issues during site activation, and ensure it is comprehensive, executable, and mitigates risk.

AQL: 100%

3.2.7 The contractor shall provide all lifting and extraction operations, and lifting operating procedures for all activities at the LTC complex in accordance with the LTC CONOPS document #OD68896, LTC Requirements Document #WS32300, and the lift plans and packages developed in PWS paragraph 3.1.6. It is anticipated this activity would be started during the design and development phase, PWS paragraph 3.1. (CDRL A00A)

3.2.7 Standards:

(1) Lifting operating procedures are accurate, comprehensive, executable, and meet technical specifications.

AQL: 100%

(2) All data submissions are accurate and IAW DID and all applicable policies and procedures.

AQL: 100%

3.3 Test and Evaluation

3.3.1 The contractor shall provide the data and analysis performed in PWS paragraphs 3.1 and 3.2 in support of the LTC System Verification Review (SVR) and the Test Readiness Review (TRR). (CDRL A002)

3.3.1 Standards:

(1) Analysis provided is accurate and comprehensive.

AQL: 100%

(2) All data submissions are accurate and IAW DID and all applicable policies and procedures.

AQL: 100%

3.3.2 The contractor shall update the CDAS, LTSYS, LTV, LTS, and Launcher portions of the CONOPS for the LTC project.

3.3.2.1 The contractor shall update the CDAS, LTSYS, LTS, LTV, and Launcher portions of the CONOPS for the test and evaluation, and post operations and maintenance phases. (CDRL A001)

3.3.2 Standards:

(1) CDAS, LTS, LTV, and Launcher portions of the CONOPS are accurate, comprehensive, and provide usable data for analysis.

AQL: 100%

(2) All data submissions are accurate and IAW DID and all applicable policies and procedures.

AQL: 100%

3.3.3 The contractor shall maintain the LTC complex inclusive of the CDAS, LTS, LTV, LTSYS, and Launcher.

3.3.3.1 The contractor shall analyze, document, and provide solutions for the maintenance, repair, and modification of the CDAS, LTS, LTV, Launcher, and LTSYS. (CDRL A003)

3.3.3.2 The contractor shall provide maintenance, modification, and repairs for the CDAS, LTS, LTV, Launcher, and LTSYS.

3.3.3 Standards:

(1) Contractor’s monitoring, tracking, and reporting activities enable the Government to determine status of assets.

AQL: 100%

(2) CDAS, LTS, LTV, Launcher, and LTSYS are functional and meet all performance test requirements after maintenance, repair, or modification.

AQL: 100%

(3) Maintenance, repairs, and modifications are completed IAW required schedules.

(4) All data submissions are accurate and IAW DID and all applicable policies and procedures.

AQL: 100%

3.3.4 The contractor shall provide aid in the resolution of fabrication, installation, and operational issues; and general support during test and evaluation.

3.3.4 Standards:

(1) Accurately addresses all program areas during aid and support of fabrication, installation and operational issues during test and evaluation; and ensure it is comprehensive, executable, and mitigates risk.

AQL: 100%

3.4 Sustainment

Sustainment tasking shall be conducted as required throughout Design & Development, Site Activation, and Test and Evaluation.

3.4.1 The contractor shall update the CDAS, LTSYS, LTV, LTS, and Launcher portions of the CONOPS for the LTC project.

3.4.1.1 The contractor shall update the CDAS, LTSYS, LTS, LTV, and Launcher portions of the CONOPS for the post operations and maintenance phase. (CDRL A001)

3.4.1 Standards:

(1) CDAS, LTS, LTV, and Launcher portions of the CONOPS address all program areas and are accurate and executable.

AQL: 100%

(2) All data submissions are accurate IAW DID and all applicable policies and procedures.

AQL: 100%

3.4.2 The contractor shall provide maintenance, modification, and repairs for the CDAS, LTS, LTV, Launcher, and LTSYS.

3.4.2 Standards:

(1) Maintenance, modification, and repairs for the LTC project are accurate, address all program areas, and are executable.

AQL: 100%

(2) All data submissions are accurate and IAW DID and all applicable policies and procedures.

AQL: 100%

3.4.3 The contractor shall provide aid in the resolution of issues or problems that may occur, and provide general support, during sustainment.

3.4.3 Standards:

(1) Accurately addresses all program areas during sustainment to ensure they are comprehensive, executable, and mitigate risk.

AQL: 100%

4.0

DATA DELIVERABLES (CLIN 0003)

Required reports, test plans, procedures, technical support documents, meeting minutes, and progress reports will be provided in accordance with the applicable Contract Data Requirements Lists (CDRLs).

5.0 SPECIAL CONSIDERATIONS (CLINs 0001, 0002 and 0003) 5.1.1 Travel. During performance of this contract, the contractor may be required to perform local and non-local travel to support the tasking. The estimated travel in support of this contract for the performance period of five years is documented below:

The contractor shall submit a request for each travel requirement a minimum of one week in advance to the Government Contracting Officer's Representative (COR). COR approval must be obtained prior to each travel departure. Each travel request will minimally consist of:

· Date of Request

· Name(s) of employee(s)

· Date and duration of proposed travel

· Purpose of travel

· Destination

· Cost estimate (airfare, per diem, car rental, miscellaneous expenses)

· Total travel allowance on contract

· Total travel cost expended to date

· Approval signatures

Upon completion of each trip, the contractor shall submit a trip report. (CDRL A00D)

5.1.1 Standard:

(1) All data submissions are accurate and IAW DID and all applicable policies and procedures.

AQL: 100%

5.1.2 Security The contractor will not require access to any Classified Material Information (CMI) in support of this contract and a Department of Defense Contract Security Classification Specification (DD Form 254) will not be required. However, the contractor will be required to support Noncritical-Sensitive (NCS) IT Level II (Limited Privilege, sensitive information access) duties. The investigative basis for assignment to a designated NCS IT-II position is a favorably completed and adjudicated National Agency Check with Local Agency and Credit Checks (NACLC). Contractor service support personnel who do not require access to any CMI in performance of this work but are assigned to sensitive national security duties shall require a favorable personnel security determination regarding his/her loyalty, reliability and trustworthiness. In accordance with Department of the Navy Implementation of Homeland Security Presidential Directive 12 (HSPD-12) and Department of Defense Standardized Investigation Request Procedures, Non National Industrial Security Program (Non-NISP) Investigations are to be conducted for contractors requiring access to an installation, require a Common Access Card and access an IT-I or IT-II system but who do not require access to classified information. Non-NISP investigations for contractor personnel under Naval Air Warfare Center Weapons Division (NAWCWD) contract are processed through the NAWCWD Personnel Security (PERSEC) Office. The NAWCWD PERSEC Office will fingerprint the contractor and send the completed package along with a request for appropriate investigation to Office of Personnel Management (OPM) on behalf of the FSO. NAWCWD will service the contractor in JPAS using our Submitting Office Number (SON).

5.1.2.1 Reporting Requirements: Contractor personnel working on a federal installation in support of this contract shall report to the NAWCWD Command Security Manager any adverse information or circumstances of which they are aware pose a threat to the security of DoD personnel, contractor personnel, resources, and classified or unclassified defense information.

5.1.22 Controlled Unclassified Information (CUI): The contractor shall implement and maintain security procedures and controls to prevent unauthorized disclosure of controlled unclassified information and to control distribution of controlled unclassified information in accordance with Department of Defense (DoD) Manual 5200.01, Information Security Program: Controlled Unclassified Information (CUI) Volume 4 (enclosure 3); DoD 5400.7-R, Freedom of Information Act Regulation (Chapter 3); and Department of the Navy (DoN) SECNAV M-5510.36, DoN Information Security Manual.

5.1.2.3 Contractors requiring access to federal installations shall obtain the appropriate base identification for all contractor personnel who make frequent visits to or perform work at government sites. Contractor personnel are required to wear or prominently display installation identification badges or contractor-furnished identification badges while visiting or performing work on the installation(s). The contractor shall be responsible for obtaining required identification for newly assigned personnel and for prompt return of credentials, Common Access Card (CAC) and any other secondary area access badges/identification for any employee who no longer requires access to the work site(s). Upon separation, resignation, firing, completion or termination of the contract or expiration of base identification, the contractor shall ensure that all base identification passes to include CACs and any other secondary area access badges/identification issued to contractor employees are returned to the appropriate component issuing office.

5.1.2.4 Contractor employees shall comply with local base procedures for entry into any federal installation controlled and restricted areas. If contractor employees require unescorted entry to controlled or restricted areas, the contractor shall comply with the appropriate Federal Installations Command Physical Security Plan and DoD Personnel Security Program, DoD 5200.2-R.

5.1.2.5 For Official Use Only (FOUO)

For Official Use Only information generated and/or provided under this contract shall be marked and safeguarded as specified in DoDM 5200.01 (DoD Information Security Program: Controlled Unclassified Information (CUI)) Vol. 4 (enclosure 3 pages 11-18) 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 .

All controlled unclassified technical information shall be appropriately identified and marked with the following distribution statement(s):

U.S. DISTRIBUTION STATEMENT D: Distribution authorized to the Department of Defense and U.S. Department of Defense contractors only; Critical Technology determined April 2012.

WARNING: This document contains technical data whose export is restricted by the Arms Export Control Act (Title 22, U.S.C., Sec 2751, et seq.) or the Export Administration Act of 1979, as amended, Title 50, U.S.C., App 2401, et seq. Violations of these export laws are subject to severe criminal penalties. Disseminate in accordance with provisions of OPNAVINST 5510.161.

Destruction Notice: Destroy by any method that will prevent disclosure of contents or reconstruction of the document.

This document is pre-decisional and fully or partially exempt from release under the Freedom of Information Act, P.L. 93-502 (5 U.S.C. § 552) by Exemption 5, 5 U.S.C. § 552(b)(5). Do not release without the prior specific approval of the originator.

This information is furnished upon the condition that it or knowledge of its possession will not be released to another nation without specific authority of the Department of the Navy of the United States; that it will not be used for other than military purposes; that individual or corporate rights originating in the information, whether patented or not, will be respected; that the information will be provided the same degree of security afforded it by the Department of Defense of the United States.

EXPORT CONTROLLED: This document contains data whose export/transfer/disclosure is restricted by US law. Dissemination to non-US persons whether in the United States or abroad requires an export license or other authorization.

5.1.2.6 Information Security

Direct Support contractor personnel working under the purview of a DoN Commanding Officer/Commander shall comply with the local security provisions and the requirements of SECNAV M-5510.36 (series).

5.1.2.7 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, CA 93555-6100.

5.1.2.8 Operations Security (OPSEC):

The contractor shall develop, implement, and maintain an OPSEC program to protect controlled unclassified 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 the subcontractor implementation of the OPSEC requirements. This program may include Information Assurance. 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.

5.1.2.9 Information Assurance

The contractor shall comply with the IA security requirements for accessing U.S. Government IT systems. The contractor shall adhere to the Department of the Navy’s (DON) Information Assurance Program prescribed methodologies for the protection of information to support DON Missions.

5.1.3 Place of Performance. Approximately 50% of performance is expected to take place at China Lake, CA at either a Government facility or the contractor’s facility. The other 50% of performance may take place at other contract/subcontractor sites.

5.1.4 Access to Government Property and Government Facilities. During performance of this contract the contractor may require access to Government Furnished Property (GFP) and/or Government facilities. The contractor shall request and obtain approval from the POC cited in the contract to obtain the necessary access. Submitted requests shall identify either the required GFP or the necessary facilities and specific personnel expected to require access to a Government facility.

5.1.5 Reports. The contractor shall develop, update, deliver, and maintain the following reports: Progress, Status and Management, Financial and Cost Graphs, and Contract Summary. In addition, the contractor shall provide task execution highlights and labor expenditure reporting. (CDRL A00C)

5.1.5.1 The contractor shall manage program schedules, provide budget planning estimates, perform technical evaluations, and perform program synthesis for current needs. This includes future planning due to emergent needs and changes in program philosophy and direction, as related to the overall Launcher Development Program. (CDRL A00C)

5.1.5 Standard:

All data submissions are reviewed for accuracy, are IAW DID cited in the CDRL, are technically correct, and are delivered on time and IAW with applicable policy and procedures.

AQL: 100%

6.0

MATERIAL AND PURCHASING (CLIN 0001)

The contractor shall manage material and consumable supplies at levels appropriate to meet mission requirements. The contractor must obtain prior approval from the COR for any purchases valued over $3,000. All COR-approved purchases shall be submitted to the Contracting Officer for post action review within five business days. The contractor must obtain prior approval from the Contracting Officer for any purchases valued over $20,000. To receive approval for the purchases, the contractor shall submit a consent package providing the description, price, evidence of adequate price competition, or if unavailable, a justification for use of a single source and a determination that the price is fair and reasonable. These requirements apply to all contractor purchases.

7.0

QUALITY SURVEILLANCE AND PERFORMANCE STANDARDS

A Quality Assurance Surveillance Plan (QASP) will be used by the Government to provide surveillance. A copy of the standards and acceptable levels of quality is provided as part of this PWS.