Draft_PWS_FA704615R0001-0005.docx

PERFORMANCE WORK STATEMENT

Task Order 0005 AFOTEC Det 6 Fighter Test Services 1 June 2015

1.0 SCOPE

This effort shall be conducted pursuant to the provisions of the Fighter Test Services (FTS) contract Performance Work Statement (PWS) paragraphs 3.0, 3.1, 3.2, 3.3, 3.4, 3.5, 3.6 and 3.7. The objective of this effort encompasses aspects of the following FTS Core Competencies: Mission Level, Man-in-the-Loop Modeling and Simulation (Requirements and Verification, Validation and Accreditation (VV&A)), Air-to-Air Range Infrastructure (AARI), fighter test instrumentation, Software Engineering/Programming/Database Management and real-time/post-flight data processing and data analysis. This task order supports operational assessments (OA) and initial operational test and evaluation (IOT&E) of modernization efforts for the F-22 aircraft. The contractor shall work in a collaborative test environment with some or majority of tasks being performed jointly. Place of performance is AFOTEC Det 6, Bldg. 584, Nellis AFB, NV. The contractor shall perform the task in paragraphs 3.0 and 5.0 as applicable.

1.1 Background. AFOTEC Det 6, headquartered at Nellis AFB, NV, is the lead for all AFOTEC fighter and fighter system OT&E with the exception of the F-35. Det 6 is currently tasked to conduct testing of the F-22A Increment 3.2B and Tactical Mandates upgrade programs. Operational test activities for these programs will occur at test ranges and test facilities to include the Nevada Test and Training Range (NTTR), Utah Test and Training Range (UTTR), Eglin Gulf Test and Training Range (EGTTR) and the Air Combat Simulation (ACS). The ACS, located at the Lockheed Martin contractor facility in Marietta, GA, was accredited for use in determining mission level effectiveness during F-22A IOT&E and Increment 3.1 FOT&E. Although not accredited as a test capability, the ACS was used for scenario development in FOT&E Increment 1, FOT&E Increment 2, and FOT&E Increment 3.2A. AFOTEC plans to use the ACS for F-22A Increment 3.2B scenario development and mission level effectiveness evaluation which will require VV&A of the simulator.

2.0 APPLICABLE DOCUMENTS

2.1 FTS Guidance. Guidance contained in the FTS PWS Section 2.0 applies to this task order.

2.2 Operational Test Related Documents. The following documents are also applicable to this task order (the contractor shall use the most current version):

2.2.1 F-22A Enhanced Global Strike Capability Production Document (CPD), 4 Jan 2007 (classified)

2.2.2 Concept of Operations Air Force Global Strike (GS) and Global Persistent Attack (GPA) CONOPS (in CPD), 23 Apr 07

2.2.3 Operational Capability Definition Document for F-22A increment 3.2A Modernization Program, Rev A, 27 Apr 2011 (in its entirety)

2.2.4 F-22A Operational Capability Definition Document (OCDD) for Increment 3, Rev A 3.2B (classified), 21 Dec 11 (in its entirety)

2.2.5 F-22A Increment 3.2B Test and Evaluation Master Plan (TEMP), V15, 7 Jan 2013 (or most current version, in its entirety)

2.2.6 F-22A IOT&E 3.2B Initial Test Design Briefing, 6 Dec 2011 (in its entirety)

2.2.7 AFI 33-332 Records Management Program, most current version (paragraphs 1, 1.1, 1.3, 2, 5, 5.1, 5.2, 5.3, 5.4, and 5.5)

3.0 PERFORMANCE REQUIREMENTS

3.1 Management Requirements. The contractor shall provide a management structure to ensure efficient management of this effort. (A001, A002, A003)

3.2 Test Capabilities. The contractor shall augment the government in performing the following tasks:

3.2.1 Participate in identifying and documenting test capability requirements for F-22 IOT&E Increment 3.2B modeling and simulation (ACS and AARI), range capabilities, data processing, and data analysis. Support the government in identifying shortfalls, performing trade-off analyses, and recommending approaches to solve issues.

3.2.2 Reserved.

3.2.3 Provide inputs to the development of F-22 IOT&E Increment 3.2B modeling and simulation verification, validation, and accreditation (VV&A) plans and/or reports for the AARI and ACS to include their component subsystem, threat, and weapon models. Participate in Det 6 reviews of AARI and ACS developer’s verification and validation (V&V) plans and reports and identify F-22 IOT&E Increment 3.2B modeling and simulation risk areas and/or limitations.

3.2.4 Reserved.

3.2.5 Participate in the development of analytical techniques, methodologies, and tools for OT&E.

3.2.6 Reserved.

3.2.7 Reserved.

3.2.8 Participate in identifying modifications required to AARI graphical displays, user interfaces, and weapon models beyond existing AARI toolset to meet test execution and data requirements.

3.3 Test Planning. The contractor shall augment the government in performing the following tasks:

3.3.1 Reserved.

3.3.2 Provide inputs to develop and/or revise the Initial Test Design (ITD) and the Test Concept.

3.3.3 Provide inputs in developing or revising critical operational issues (COIs), measures of effectiveness (MOE), and measures of suitability (MOS).

3.3.4 Provide inputs in developing operational test scenarios.

3.3.5 Provide inputs to test methodologies, the identification of test risks and limitations, mitigation strategies, readiness to test activities, and test readiness and support requirements needed to complete the OT&E plan.

3.3.6 Provide inputs to support development of test methodologies and test scenarios for AFOTEC, Director of Operational Test and Evaluation (DOT&E), and program special interest items.

3.3.7 Provide inputs to develop and/or revise OT&E test plans, data management and analysis plans (DMAPs), test planning briefings, and schedules. Provide inputs to and/or develop detailed test procedures (DTPs). (A029)

3.3.8 through 3.3.14 Reserved.

3.3.15 Participate in the identification of system effectiveness data requirements and specific data processing and analysis tools.

3.3.16 Participate in the review and incorporation of lessons learned from other OT&E efforts into Det 6 test plans.

3.3.17 Reserved.

3.3.18 Provide inputs to program introduction documents (PID) for the appropriate range support.

3.3.19 through 3.3.21 Reserved.

3.3.22 Provide inputs to prepare for the conduct of OT&E control room White Force Command and Control Operations during test trails. Provide inputs to define white force tasks (i.e. white force commander, kill removal officers, lead analyst, and observers), task rehearsals, and post-trial debriefing efforts.

3.4 Test Execution. The contractor shall augment the government in performing the following tasks:

3.4.1 Reserved.

3.4.2 Reserved.

3.4.3 Participate in the execution of test plans, data management and analysis plans, and detailed test procedures.

3.4.4 Use, participate in the development of, modification of, and/or maintenance of the required automated data collection/reduction systems to include developing interfaces with existing digital information stored on available databases. Analyze content for interoperability and compatibility with existing information and data systems.

3.4.5 Participate in government control room White Force Command and Control Operations (i.e. white force commander, kill removal officers, analyst, and observers) during test trials, task rehearsals, and post-trial debriefing efforts.

3.4.6 Participate in and collect data from DT&E operations to support Integrated Test and Evaluation.

3.5 Test Evaluation. The contractor shall augment the government in performing the following tasks:

3.5.1 Participate in the collection, compilation, review, and analysis of test data.

3.5.2 Participate in running computer models and simulations and analyzing/characterizing the resulting output.

3.5.3 Participate in studies, analyses and evaluations on operation effectiveness and mission capability of weapon system programs undergoing OT&E.

3.5.4 Participate in analyses and evaluations for AFOTEC, DOT&E, and program special interest items.

3.6 Test Reporting. The contractor shall augment the government in performing the following tasks:

3.6.1 Reserved.

3.6.2 Reserved.

3.6.3 Provide inputs to report briefings as a part of the report coordination process.

3.6.4 Provide inputs to lessons learned reports.

3.6.5 Participate in the development of, and provide inputs to, test documentation, quick-look, interim, final reports and briefings.

4.0 SERVICE SUMMARY ITEMS

5.0 GENERAL INFORMATION, DELIVERABLES, SCHEDULES, AND REPORTING

5.1 Government Furnished Property – Base Support. The government will provide on-site work space, support equipment, software, administrative equipment, and supplies. The contractor will abide by government directives, Air Force, AFOTEC and MAJCOM and local base instructions pertaining to the proper use and protection of government furnished equipment, security, and access to and use of government facilities and property.

5.2 Travel Requirements. Contractors may be required to travel to military installations for team meetings, test events, etc. Travel to non-military locations may also be required. Prior to travel, all travel requirements must be coordinated through the COR, who will then obtain approval from AFOTEC/CC. Travel will be cost reimbursable (no fee) in accordance with the Joint Travel Regulation. A travel ceiling will be established for the basic period and each option.

5.3 Transition. The FTS contractor shall insure a smooth transition with the successor, whether another contractor or government personnel, during the phase-out period, prior to completion of contractual performance. The contractor shall aid the successor in the development of plans, procedures and methods for assumption of all on-going work. The contractor must provide an orderly transition of work acceptance and accomplishment so that full control by the successor is achieved by the end of the new phase-in period.

5.4 Reserved.

5.5 Period of Performance. Proposed --- Effort is 34 months from date of award to. Basic: From Date of Award for twelve months. Option 1: 12 month period from Date of Award. Option 2: 10 month period from end of Option 1.

5.6 Contract Data Requirements List (DD 1423s). With the exception of contractor management documents (e.g. Monthly Status Reports), and the identified CDRLs, all documents and reports generated are to be U.S. Government reports. All documents shall be marked with applicable classification markings and the following statement: Export Control Warning. 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 DoD Directive 5230.25. Hard copy reports and physical media shall be delivered to:

AFOTEC Det 6 Attn: Contracting Officer Representative 5960 Devlin Dr., Bldg. 584 Nellis AFB, Nevada 89191-7048

The contractor shall provide:

5.6.1 Management Plan (A001) Reference paragraph 3.1. Management plan shall be presented in contractor format at the time of proposal submittal.

5.6.2 Funds & Manpower Expenditure (A002) – Reference paragraph 3.1.

5.6.3 through 5.6.6 Reserved.

5.6.7 DTP (A029) – Reference paragraph 3.3.7. The contractor shall develop specific DTPs as specified by the COR. DTPs shall be in the current AFOTEC format and are due as specified by the COR to support draft and final document coordination.

5.6.8 Reserved.

5.6.9 Reserved.

5.6.10 Conference Minutes (A004) – Reference paragraphs 3.2, 3.3, 3.4, and 3.5. The contractor will summarize the results of meetings and conferences attended. Contractor trip report format is acceptable. Reports shall be submitted to the COR within five working days after the end of local area events and seven workdays after the end of all other events.

6.0 SECURITY REQUIREMENTS

6.1 Security

6.1.1 The contractor shall comply with all security requirements in accordance with DD Form 254, DoD Contractor Security Classification Specification.

6.1.2 The contractor will require access to classified and Special Access Program source data up to and including Top Secret Special Compartmented Information. The contractor must have a Top Secret Security Clearance current within five years and be SAP and SCI eligible. The contractor must have a current clearance in place by the first day of the task order.

6.1.2.1 The contractor shall provide the government with required information for program access requests to include justifications, letters of compelling need, and any other information to support program access packages. The contractor must ensure they are accurate and complete IAW applicable guidance.

6.1.3 The contractor submits classified visit requests via the Joint Personnel Adjudication System (JPAS) in support of tasks within the DoD. Classified visits outside of the DoD require Visit Authorization Letters in accordance with the National Industrial Security Program Operating Manual. Direct requests must be approved by AFOTEC with coordination by the COR/test manager prior to travel.

6.1.4 Report to an appropriate authority any information or circumstances of which they are aware may pose a threat to the security of DOD personnel, contractor personnel, resources and classified or unclassified defense information. Contractor employees shall be briefed by their immediate Contractor supervisor upon their initial on-base assignment. Government personnel do not supervise contract employees.

6.1.5 Any failure to adhere to security regulations will result in a security incident and will be processed according to DoDM 5200.01, Volume 3, SAF/AQ Security Pamphlet 5, AFI 31-401, AFMAN 14-304, JAFAN 6.0, 1-301a (10), DoD 5105.21-M-1 and/or other applicable guidance.

6.1.6 Classified deliverables shall be marked in accordance with applicable guidance as listed in Attachment 1, to include any subsequent changes and/or revisions. Any extracts or use of the data will require the contractor to apply derivative classifications and markings consistent with the Original Classification Authority and current security classification guides (SCGs). The contractor must meet derivative classifier requirements and meet biennially training requirements.

INFORMATION ASSURANCE: The contractor shall:

6.1.6.1 Comply with DoD 5400.7-R, Chapter 4, DoD Freedom of Information Act (FOIA) Program, and AFI 33-332, The Air Force Privacy and Civil Liberties Program requirements. These regulations set policy and procedures for the disclosure of records to the public and for marking, handling, transmitting and safeguarding FOUO material.

6.1.6.2 The contractor is prohibited from attaching any computer hardware to the Air Force network, or running any computer software unless it has been certified and accredited according to current USAF Instructions. Any such requests for reconfiguration, upgrade, or addition of computer hardware or software must be approved by the USAF Designated Approval Authority (DAA) Representative via the contractor's submission of a written request to the COR. Contractor use of computer modems, thumb drives, and external hard drives on any machine attached to the Air Force network is prohibited. Use of commercial internet service providers is prohibited.

6.1.6.3 Contractor personnel using computer assets shall comply with all computer security requirements. In addition, should contractor personnel require access to computer networks or databases, they shall inform the COR or Alternate COR, who will arrange for the contractor personnel to complete the required documentation for a new computer account. The contractor shall notify the COR or Alternate COR within one workday of any contractor personnel who no longer require an open account and shall take action to close the computer account with the appropriate office within that same workday.

6.1.6.4 All contractor personnel who will be using C4 systems belonging to the federal government to generate, process, store, transfer, or communicate information shall attend mandatory C4 systems security training. The format for the training may be either the Air Force C4 Systems Security Awareness Training program format or an in-house contractor program that meets DOD requirements, subject to agreement by the COR. The training must be completed within the first thirty calendar days of the start of the contract or within the first 10 calendar days for contracts that have duration of 60 days or less. The contractor shall inform the COR when the training has been completed. The notice shall include the contract number and any applicable task order number, names of contractor personnel who attended and dates of training.

6.1.6.5 The contractor shall immediately notify the COR of any government C4 system problems or issues which come to their attention which may impact the contractor's or the government's ability to access the systems.

6.1.6.6 All contractor personnel who require access to C4 systems are required to obtain a National Agency Check (NAC) consistent with Public Trust Positions (Standard Form 85P or most current form). The contractor may submit a request to the COR that the government grant contractor employee(s) interim access to the C4 network while awaiting the results of a NAC. Interim access to the C4 network will only be granted after the contractor employees obtain at least a local background files check, and have submitted the appropriate documentation to obtain a NAC. These requests will be processed in accordance with government information security regulations and policy, and must include Security Office and DAA Representative Approval. These requests may be subject to disapproval. In no case will a contractor be given access to the network, including a group account, until a favorable NAC has been completed or interim access granted by the DAA Representative. Any interim accesses that may be granted may be rescinded at any time by the PCO, COR, Directorate Security Office or DAA Representative at the government’s discretion. Any individual who subsequently does not pass the requirements for a full NAC shall not be authorized to work under this effort.

6.1.6.7 No foreign nationals are authorized to work on this effort without prior written notification to the COR and PCO, and until approval is obtained from the PCO in accordance with current government policy and regulations.

6.1.6.8 Reserved.

6.1.6.9 The contractor will require access to and use of COMSEC materials. Coordinate with the government COMSEC manager or functional representative on all COMSEC operating instructions, and any required training plans.

6.2 Submit application for Department of Defense Common Access Card/DEERS Enrollment, DD Form 1172-2, for initial request of contractor employee; contractor to furnish updated CAC list as needed throughout the PoP, and update an annual CAC listing and provided to the Det 6 COR and Security Manager.

7.0 MISCELLANEOUS INFORMATION

7.1 Safety Considerations. The contractor shall plan for and implement safety procedures and protective equipment to reduce/negate injury to personnel engaged in activities supporting this contract. Safety areas of concern include but not limited to ground, flight, occupational, and environmental safety. Contractor will comply with all applicable OSHA, Federal, State and Local regulations.

7.2 Program Safety Considerations. Contractor employees shall be trained and certified IAW applicable OSHA standards as required. The contractor shall maintain current training records and/or certificates of completion and provide them to the Government upon request.

8.0 Organizational Conflict of Interest. In accepting and performing the work required by this task order, and all amendments thereto, the contractor certifies that the requirements of clause 5352.209-9000 Organizational Conflict of Interest (OCI) have been or will be adhered to. The contractor must immediately bring any OCI issues to the attention of the Procuring Contract Officer and the Contracting Officers Representative for a determination of whether a mitigation plan is required.

9.0 WORKLOAD DATA: To be removed upon award.

A total of 5 estimated Full-time Equivalents (FTE) for this task order is provided based on historical data. This information is merely an estimate and is not considered mandatory. This data may not necessarily reflect manpower needed to perform this task order. The offeror shall propose the manpower as they determine appropriate for this task order. An FTE is defined as 40-hour work week.

10.0 CONTRACTOR FULL-TIME EQUIVALENT REPORTING ADDENDUM

Contractor Full-Time Equivalent Reporting: The contractor shall report ALL contractor labor hours (including subcontractor labor hours) required for performance of services provided under this contract for AFOTEC via a secure data collection site. Data will be collected and reported at both the task order and specific program level. The contractor is required to completely fill in all required data fields at http://www.ecmra.mil. Reporting inputs will be for the labor executed during the period of performance for each Government fiscal year (FY), which runs 1 October through 30 September. While inputs may be reported any time during the FY, all data shall be reported no later than 31 October* of each calendar year. Contractors may direct questions to the CMRA help desk. * Reporting Period: Contractors are required to input data by 31 October of each year. Uses and Safeguarding of Information: Information from the secure website is considered to be proprietary in nature when the contract number and the contractor identity are associated with the direct labor hours and direct labor dollars. At no time will any data be released to the public with the contractor name and contract number associated with the data. User Manuals: Data for Air Force service requirements must be input at the Air Force CMRA link. However, user manuals for government personnel and contractors are available at the Army CMRA link at http://www.ecmra.mil

Attachment 1:

Applicable to All

Note: Source: The provisions of Executive Order 12829 (PDF format), as amended by Executive Order 12885, Vol. 58, No. 240, December 16, 1993

NOTE: Amended by: EO 13467, June 30, 2008 See: Final rule of March 26, 1997 (62 FR 17683); Final rule of July 1, 1997 (62 FR 36984); EO 13284, January 23, 2003; EO 13311, July 29, 2003; EO 13462, February 29, 2008; EO 13516, October 28, 2009; EO 13539, April 21, 2010; EO 13549, August 18, 2010

VOL. 1

DOD INFORMATION SECURITY PROGRAM: OVERVIEW, CLASSIFICATION, AND DECLASSIFICATION

VOL. 2

DOD INFORMATION SECURITY PROGRAM: MARKING OF CLASSIFIED INFORMATION

VOL. 3

DOD INFORMATION SECURITY PROGRAM: PROTECTION OF CLASSIFIED INFORMATION

VOL. 4

DOD INFORMATION SECURITY PROGRAM: CONTROLLED UNCLASSIFIED INFORMATION (CUI)

SCI Documents

16 Jan 2009

15 Sep 2008

21 Sep 2007

18 Feb 2008

1 Oct 2008

2 October 2008

2 October 2008

2 October 2008

2 Oct 2008

2 Oct 2008

26 May 2010

17 Sep 2010

17 Sep 2010

5 May 2011

9 Oct 2008

01 April 1999

01 May 1999

SAP Documents

Feb 1998

29 May 2008

15 Oct 2004

9 May 2006

23 Mar 2004

1 Nov 1995

47.

AFOTEC, Detachment, Operating Locations Standard Operating Procedures

48.

AFOTEC, Detachment, Operating Locations Master System Security Plans and Annexes

Collateral Documents

see also

DTM-09-012

DTM-08-004

PHYSICAL SECURITY PROGRAM

SUPPLEMENT 1

NATIONAL INDUSTRIAL SECURITY PROGRAM OPERATING MANUAL SUPPLEMENT

21 Sep 2012

ISOO

Information Assurance Documents

92.

NRO Network Communications Security Manual 95.1

OPSEC Documents

NATO Documents

CNWDI- RD/FRD

NC2-ESI