NukDEW_TO_1_(12_Jul_16).doc

AIR FORCE OPERATIONAL TEST & EVALUATION CENTER (AFOTEC)

TEST SERVICES (ATS)

NUCLEAR WEAPONS, DIRECTED ENERGY WEAPONS, AND NATURAL SPACE ENVIRONMENT SURVIVABILITY SERVICES (NukDEW) 12 July 2016

1.1 SCOPE

The objective of this Task Order is to provide technical services to Headquarters Air Force Operational Test and Evaluation Center (HQ AFOTEC) in very specialized areas, across a wide variety of programs. This task is within the scope of the AFOTEC Test Services (ATS) contract Performance Work Statement (PWS), Section 3. Specifically, this task order requests services in the following areas: 3.1, 3.2, 3.3, 3.4, 3.5, and 3.6. The programs to be supported may be at any point in their progress through the AFOTEC process. Responsibility for the programs may be at HQ AFOTEC, any Detachment or Operating Location.

Services may be needed through every phase of an AFOTEC test program, or they may taper off as operational requirements and missions become clear. The contractor shall calculate the nuclear, directed energy, and natural space environment survivability levels the acquisition programs should have based on current and projected threats. The contractor will then compare these calculated levels to the levels the system is designed to have, and identify any differences. AFOTEC’s goal is to improve Integrated Test (combined Developmental Test (DT)/Operational Test (OT)) by engaging the System Program Office (SPO) and developers to ensure the goals and needs of AFOTEC and the other Operational Test Agencies (OTAs) are considered, included, and met.

1.2 BACKGROUND

There are various existing and future strategic programs that may involve nuclear weapons survivability. These include space programs such as Advanced EHF (AEHF), Weather System Follow-on (WSF), Space Based Infrared Satellite System (SBIRS), ground terminal programs, Family of Advanced Beyond Line of Sight Terminals (FAB-T), and aircraft programs such as the KC-46A replacement tanker and the B-21 Long Range Strike Bomber (LRSB).

There may be various existing and future systems that may involve directed energy survivability. For the purpose of this task order, directed energy weapons are laser or high power microwave weapons.

In addition, there may be future tactical aircraft and radio systems, or hypersonic craft with similar required capabilities.

2.0 APPLICABLE DOCUMENTS

The contractor shall follow the guidance contained in section 2.0 of the PWS.

3.0 PERFORMANCE REQUIREMENTS

These contractor shall perform the requirements within the service task areas listed in this section.

3.1 Management Requirements. The contractor shall provide a management structure to accomplish this task order in compliance with the provisions in Section 3.1 of the PWS. (A001, A002)

3.2 The contractor shall:

3.2.1 For AFOTEC test programs, as assigned by the COR, follow the sequential steps below to perform a complete analysis of each major system being acquired. After each step, report interim results to the COR. (Contractor's format is acceptable.) After each step is finished, decide whether the process should stop, and if so, inform the COR who will make the decision. When the last step is finished, document the effort and conclusions from each step in a single technical report (A015). Over the period of involvement with a particular program, some of these steps may need to be repeated due to changes in the threats or in the program.

1a Research and perform analysis to identify the mission of the system.

1b Research and perform analysis to identify the system’s mission critical functions and equipment.

1c Identify the potential impacts upon the mission critical functions and equipment from the following threats and effects:

i) Nuclear threat

Effects:

HEMP (High-altitude Electromagnetic Pulse)

Blast

Overpressure Fall-out

Scintillation

ii) Natural radiation threat

iii) Directed Energy Weapons threat, Laser

iv) Directed Energy Weapons threat, High Power Microwave (HPM)

1d Identify any potential mission impacts that may result from the potential impacts identified in step 1c.

1e Calculate the survivability requirements of the system that would avoid the results of step 1d, and support mission accomplishment.

2a. Research the survivability requirements and specifications that are planned for the system by the users and the SPO.

2b Research the SPO’s plans for Developmental Test (DT) of survivability.

2c Research the SPO's plans for Hardness Assurance, Maintenance, and Surveillance (HA/HM/HS) procedures.

3. Identify any deficiencies in program survivability requirements, specifications, DT plans, data requirements, and maintenance procedures by comparing the results of steps 1 and 2.

4. Identify any program survivability requirements, specifications, DT plans, data requirements, and maintenance procedures that are beyond adequate by comparing the results of steps 1 and 2.

5. Identify and recommend appropriate test tools, facilities, and methods.

3.2.2 For AFOTEC test programs, as assigned by the COR, ensure that the system being procured has adequate survivability requirements, and is adequately tested.

Advocate for integrated tests between the SPO, development contractors, and operational test agencies (OTAs) in order to save government funds and reduce acquisition program risk.

Work with AFOTEC test teams to ensure that AFOTEC’s test plans include adequate survivability measures of effectiveness (MOE) and suitability (MOS).

Participate in all relevant DT and integrated test, and conduct OT, collect data where appropriate, perform data analysis, and report the results of each test event (A015).

Assist AFOTEC test teams in the evaluation and reporting of survivability MOEs and MOSs. (Contractor's format is acceptable.)

3.3 Perform the following activities as needed:

3.3.1 Attend meetings: teleconferences, VTCs, test working groups, system design reviews, technical interchange meetings, Initial Test Designs (ITD), Measures Workshops, and core team meetings.

3.3.2 Review documents: Capabilities Development Documents (CDD), Test and Evaluation Master Plans (TEMP), System Threat Assessment Report (STAR), system description information, development program specifications, equipment interface specifications, HA/HM/HS program concepts and plans, DT and OT test plans and reports, design documentation, Defense Intelligence Agency (DIA) and/or AF/IN approved threats, Concepts of Operations (CONOPS), and/or Concepts of Employment (CONEMPs).

3.3.3 When appropriate, recommend to the Contracting Officer’s Representative (COR) any of the listed threats that do not impact the particular program, or any threats which no longer require attention due to completion of adequate testing. Removing threats from consideration requires approval of the COR in writing or e-mail.

3.3.4 Monitor related plans for DT, monitor system or operational measures to counter threats.

3.3.5 Research and analyze the available test options, develop adequate test concepts, test methods, analyses, determine test resources and schedules adequate to achieve the suggested methods, identify appropriate test support tools for use in testing survivability.

3.3.6 Witness or participate in all relevant DT and integrated test. Investigate problems found with the system under test (SUT), and develop work arounds to allow mission accomplishment.

3.3.7 Write notes and memos to the COR, test directors or analysts, and SPO personnel. Examples include: memo for record (MFR), deficiency list, weekly activity report (during tests), monthly activity notes, meeting notes, test event progress report, test event quick-look summary, draft sections of a report, and some technical analyses. Where possible, these shall be delivered via e-mail (Contractor's format is acceptable.)

3.3.8 Write documents in specified formats if required, such as conference minutes (A003), sections of the final report briefing (A012), technical reports (A015), test event reports (A015), and technical analyses (A016).

3.3.9 Develop briefings to show the technology behind threats, the technology to overcome the threats, test methods and techniques. (A012)

3.3.10 Collect, compile, review, analyze, and evaluate test results. Run computer models and simulations; analyze/characterize the resulting output.

3.3.11 Determine the capability of the system to withstand the natural and man-made threat environments, and quantify the degree of impairment of its ability to accomplish its designated mission.

3.3.12 Aid in the determination of system effectiveness, suitability, and survivability. Prepare test documentation for inclusion in test and evaluation reports (contractor's format is acceptable). Prepare briefings or slides as a part of the report coordination process (A012). Prepare lessons learned reports (contractor's format is acceptable).

4.0. Surveillance Matrix

Table 4.1. Surveillance Matrix

Ref

Item 6: AFOTEC Safety Requirements: contractors shall ensure their employees and subcontractors comply with all applicable OSHA standards, identify and mitigate hazards, and report pertinent facts regarding mishaps involving damage or injury. Contractors will cooperate in any safety investigation, to include toxicology testing.

Each OSHA violation must be resolved to the government’s satisfaction within 3 working days, except imminent danger situations which must be mitigated or resolved and reported immediately.

Incidents as reported in Status Reports, or violations reported to/observed by customer or COR.

5.0 GENERAL INFORMATION

5.1 Base Support/Government Furnished Property (GFP)/Government Furnished Information (GFI) – Government Furnished Property (GFP)/Government Furnished Information (GFI) AFOTEC will provide program documentation such as the Initial Capabilities Document (ICD), CDD, TEMP, Preliminary Design Review (PDR) slides, Critical Design Review (CDR) slides, STAR, etc. as appropriate.

5.2 Travel Requirements

Contractor employees may be required to travel to various locations, both within in continental United States (CONUS) and outside the continental United States (OCONUS). For OCONUS travel, contractor employees shall possess passports, visas, and medical clearance for designated operations areas. The Government will not directly reimburse the contractor for these types of expenses. Travel will be cost reimbursable (no fee) in accordance with the Joint Travel Regulation. The travel ceiling for this Task Order is $20K per year.

5.3 Transition

It’s anticipated that some important work will be in progress through the phase-in and phase-out periods of this contract. Interruptions or delays to the work would impact the mission. Its essential attention be given to minimizing any interruption, therefore, the contract must provide for maximum cooperation between successor and incumbent, while also insuring that no work receives inadequate attention during phase-in/phase-out. The contractor shall plan for the transfer of work control, delineating the method for processing and assigning tasks, during phase-in/phase-out.

5.3.1 Phase-In. As a successor, the ATS contractor shall insure a smooth transition with the incumbent Operational Test and Evaluation Services (OTES) contractor(s) during the phase-in period. There will be no phase-in if the successor contractor subcontracts to an OTES incumbent. The contractor shall develop plans for assumption of awarded Task Orders. The contractor must provide an orderly transition of work such that any impact to a program is minimized. The phase-in time period is 30 days and is the first month of the period of performance.

5.4 Deliverables. Where feasible, delivery shall be made by electronic means compatible with AFOTEC software. All deliverables shall be marked with: 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. Classified deliverables shall be marked in accordance with Executive Order 13526, DoD 5200.1-R, DoDM 5200.01 Vol 3-8, DoDI 5210.02, AFI 31-401, AFI 31-407, and ISSO Marking Classification Handbook. Reports shall be delivered to the COR via e-mail.

5.4.1 Funds and Manhour Expenditure Report (A001). The contractor shall provide a funds and manhour expenditure report via e-mail to the COR and hard copy to A-7K 15 calendar days after the end of prime contractor's monthly accounting period. These reports shall include the status of each program, in the form of bar charts.

5.4.2 Status Reports (A002). Reports shall provide status of all programs. Reports are due 15 calendar days after the end of prime contractor's monthly accounting period.

5.4.3 Conference Minutes (A003). The contractor shall provide conference or trip minutes to the COR and test director within 5 working days after any trip, meeting, or conference. These shall take the form of a memo for record (MFR), and shall be delivered in electronic form. Reports shall be delivered to the COR via e-mail.

5.4.4 Briefing Materials (A012). The contractor shall provide briefing material as requested by COR. COR will provide draft and final submission schedule for each briefing request.

5.4.5 Scientific and Technical Reports (A015). The contractor shall provide scientific and technical reports to the COR for each program at significant milestones as needed. Draft submission is due within 20 days, final within 30 days. Final version shall be delivered in both paper and electronic formats.

5.4.6 Reports shall be delivered to:

HQ AFOTEC/A2A9O

Attn: Survivability COR 8500 Gibson Blvd. SE Kirtland AFB, NM 87117-5558

5.5 Period of Performance. Ordering Period is DOA plus 60 months.

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 Compartmental Information (SCI). 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.3 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.4 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 IAW the National Industrial Security Program Operating Manual. Direct requests must be approved by AFOTEC with coordination by the COR, Test Manager, and/or Test Director prior to travel.

6.1.5 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 supervisor upon initial on-base assignment.

6.1.6 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), and/or DoD 5105.21-M-1.

6.1.7 Safeguarding Information. The contractor shall:

6.1.7.1 Comply with DoD 5400.7-R, Chapter 4, DoD Freedom of Information Act Program, and AFI 33-332, Privacy Act Program requirements. These regulations set policies and procedures for the disclosure of records to the public and for marking, handling, transmitting, and safeguarding official material.

6.1.7.2 Report to an appropriate authority any information or circumstances, of which they are aware, that may pose a threat to the security of DoD personnel, contractor personnel, resources, and/or 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.7.3 The contractor is prohibited from attaching any computer hardware to the USAF 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 USAF network is prohibited. Use of commercial internet service providers is prohibited.

6.1.7.4 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. IAW 5352.242-9001. The contractor shall notify the COR or Alternate COR of any contractor personnel who no longer require an open account.

6.1.7.5 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 USAF 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.7.6 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.7.7 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 Persistent Cyber Operations Forces, 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.

7.1 ATTACHMENTS/MISCELLANEOUS INFORMATION

7.1.1 Environmental Controls. The contractor shall comply with all environmental requirements imposed by the Federal Government, the USAF, and at locations where services are being performed. Such requirements are delineated in USAF Policy Directive 32-70, “Environmental Quality,” and other laws and regulations.

7.1.2 Administrative Dismissal for Safety Reasons. The contractor will provide alternate work sites for personnel during local emergency situations when the Base Commander has declared an emergency and has stated personnel should not report to base or should leave the base during a workday. Local emergency conditions include inclement weather (i.e., snow, tornados, earthquakes, hurricanes, etc.). NOTE: only the Base or AFOTEC Commander can declare such an emergency (not a Government Director, Division Chief, Site Commander, Program Manager, COR, PCO, etc.).

7.1.3 Performance of Services during crisis declared by the President of the United States, the Secretary of Defense, or Overseas Combatant Commander. The performance of these services is not considered to be mission essential during time of crisis. Should a crisis be declared, the PCO or his/her representative will verbally advise the contractor of the revised requirements, followed by written direction.

7.1.4 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 AFFARS 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 PCO for a determination of whether a mitigation plan is required.

7.1.5 AFOTEC Safety Requirements. It is the contractor’s responsibility to ensure its employees and managers have a comprehensive understanding of and full compliance with Occupational Safety and Health Administration (OSHA) requirements. Detailed information is available on the OSHA website at http://www.osha.gov.

8.0 CONTRACTOR FULL-TIME EQUIVALENT REPORTING.

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 may be collected by task order. 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 Contracting Manpower Reporting Application (CMRA) help desk.

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: Security Reference Documents

Applicable to All

Note: Source: The provisions of Executive Order 12829 (PDF format), as amended by Executive Order 12885, Vol. 58, No. 240, 16 Dec 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, 18 August 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

Amended 21 July 2015

NOTE: Superseded by ICD 700 on 7 June 2012

1 Oct 2008

2 October 2008

2 October 2008

01 May 1999

SAP Documents

Security Manual: Physical Security, 31 Dec 15

53.

Organizational Standard Operating Procedures

54.

Organizational Master System Security Plans and Annexes

Collateral Documents

NATIONAL INDUSTRIAL SECURITY PROGRAM OPERATING MANUAL (NISPOM)

ISOO

Information Assurance Documents

OPSEC Documents

NATO Documents

CNWDI- RD/FRD

NC2-ESI

Policy Letters