TO Nuclear Space 15_JUL_11_AFL.docx

Task Order 0001 Nuclear Weapons, Directed Energy Weapons, and Natural Space Environment Survivability Services 25 Jul 11

1.0 SCOPE

The objective of this task order is to provide technical services to the HQ AFOTEC in very specialized areas, across a wide variety of programs. This task is within the scope of the Operational Test and Evaluation Services (OTES) 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.

Services may be needed through every phase of an AFOTEC test program, or it may taper off as operational requirements and missions become clear. The contractor shall identify the nuclear and directed energy survivability capabilities the military users have for acquisition programs, and ensure those capabilities are adequately tested and reported. The method is to improve combined DT/OT by engaging the program office and developers to ensure the goals and needs of AFOTEC and OTAs are considered, included, and met.

There are also 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 with similar required capabilities.

The contractor shall ensure AFOTEC addresses all of capabilities effectively and efficiently, whether in OT or combined DT/OT.

1.1 BACKGROUND

There are various existing and future strategic space programs that may involve nuclear weapons survivability. These include Advanced EHF (AEHF), Space Based Radar (SBR), Rapid Attack Identification, Detection and Reporting System (RAIDRS), National Polar Orbiting Operational Environmental Satellite System (NPOESS), Wideband Gapfiller System (WGS), and Transformational Communications MILSATCOM (TCM). The related ground terminal programs may also have similar requirements. These programs include Family of Advanced Beyond Line of Sight Terminals (FAB-T), and Ground Multi-Band Terminal (GMT).

2.0 APPLICABLE DOCUMENTS

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

3.0 PERFORMANCE REQUIREMENTS – Applicable to the basic effort and each option, if exercised.

For each program, the contractor shall consider the potential system required capabilities for the following threats:

A) Nuclear threat HEMP (High altitude Electromagnetic Pulse) Blast Overpressure Fall-out Scintillation HM/HS/HA (Hardness Maintenance, Surveillance, and Assurance)

B) Natural radiation threat

C) Directed energy weapons threat Laser weapons High Power Microwave (HPM) weapons

At the end of each major phase, the contractor shall recommend to the COR,which threats are to no longer be considered. Upon approval updates will be incorporated.

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, A003)

3.2 Test Capability (A003 & A016)

The contractor shall:

3.2.1 Perform analysis of test capabilities during the Early Involvement Phase such as:

Identify mission; identify mission critical functions and equipment; estimate potential impacts of threats upon functions and equipment; identify potential mission impacts; determine program requirements; and, determine the System Program Office's (SPO) plans for Developmental Test (DT), for the threats listed below:

Work to eliminate deficiencies Push for combined DT/OT events Identify appropriate test tools Attend meetings: teleconferences, VTCs, test working groups, system design reviews, technical interchange meetings, and core team meetings.

3.2.2 Review documents: ORDs, TEMPs, STARs, system description information, development program specifications, equipment interface specifications, Hardness Assurance, Hardness Maintenance and Hardness Surveillance program concepts and plans, OT&E and DT&E test plans and reports, design documentation, Defense Intelligence Agency (DIA) and/or AF/IN approved threat and concepts of operation, CONOPs, CONEMPs.

3.3 Test Planning. )

The contractor shall:

3.3.1 Research and analyze the available test options such as: determine the best and most cost effective test methods; monitor SPO and system developer plans for DT; monitor system or operational measures to counter threats; recommend appropriate wording on Critical Operational Issues (COI)/Measures of Effectiveness (MOE)/Measures of Performance (MOP); develop adequate test concepts, test methods, and analysis; determine test resources and schedules adequate to achieve the suggested methods; identify appropriate test support tools for use in testing survivability; and attend meetings: teleconferences, VTCs, test working groups, system design reviews, technical interchange meetings, and core team meetings.

3.4 Test Execution. (A003 & A016)

The contractor shall:

99-101.

3.5 Test Evaluation. (A003 &A016)

The contractor shall:

3.6 Test Reporting. (A016)

The contractor shall:

4.0. Surveillance Matrix

Table 4.1. Surveillance Matrix

5.0 GENERAL INFORMATION

5.1. Government Furnished Property – Base Support

Government Furnished Property (GFP)/Government Furnished Information (GFI) AFOTEC will provide program documentation such as the ICD, CDDt, TEMP, PDR slides, CDR slides, STAR, etc. as appropriate.

5.2. Travel Requirements

Contractor employees may be required to travel to various locations, both CONUS and outside the continental United States (OCONUS), in performance of task orders. 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 and is inclusive of all indirect costs and tax.

5.3 Transition

It is 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. It is essential that 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 OTES contractor shall insure a smooth transition with the incumbent Engineering and Technical Services (ETS) contractor(s) during the phase-in period. There will be no Phase-in if the successor contractor subcontracts to an ETS incumbent. The contractor shall develop plans for assumption of awarded task orders. The contractor must provide an orderly transition of work acceptance and accomplishment such that any impact to a program is minimized. The phase-in time period is 30 days and is the first month of the 12-month period of performance for the basic effort.

5.4 Deliverables. Where appropriate, 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. Reports shall be delivered to the COR using an e-mail address of the form: first name.last name@kirtland.af.mil

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 within 10 working days after the end of each month. 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 the tenth day after end of each calendar month reporting period.

5.4.2 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.mailto:name@kirtland.af.mil

5.4.3 Scientific and Technical Reports (A016) The contractor shall provide scientific and technical reports to the COR for each program following the end of each phase (A through D) listed in section 3.2 above. Draft submission is due within 30 days, final within 60 days. Final version shall be delivered in both paper and electronic formats. Reports shall be delivered to:

5.6 Period of Performance. Basic effort is 12 months, 1 Feb 12 through 31 Jan 13; Option 1 is 12 months, 1 Feb 13 through 31 Jan 14; Option 2 is 12 months, 1 Feb 14 through 31 Jan 15; Option 3 is 12 months; 1 Feb 15 through 31 Jan 16; Option 4 is 12 months, 1 Feb 16 through 31 Jan 17.

6.0 SECURITY REQUIREMENTS

6.1 Security Clearances

DD Form 254, Contract Security Classification Specification (FA7046-05-D-0030) applies to this work effort. Access to classified documents up to and including Top Secret/Critical Weapons Design Information (CNWDI) and Restricted Data is required.

6.2 Safeguarding Information

The contractor shall:

6.2.1 Comply with DoD 5400.7-R, Chapter 4, DoD Freedom of Information Act Program, and AFI 33332, 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.2.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 supervisor upon their initial on-base assignment.

6.2.3 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.2.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. 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.2.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 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.2.7 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.2.8 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.2.9 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.

7.0 ATTACHMENTS / MISC. INFO:

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

7.2 Safety Requirements. The contractor shall comply with all safety requirements imposed by the Federal Government, the Air Force, and at locations where services are being performed. Such requirements are delineated in AFPD 91-2, “Safety Programs”, AFI 91-301, “AF Occupational and Environmental Safety, Fire Protection and Health Program”, and AFI 91-202, “USAF Mishap Prevention Program.”

7.3 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.4 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.5 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.

8. WORKLOAD DATA: To be removed upon award.

A total of one (1) estimated Full-time Equivalent (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 workweek.