Final_TO_01_Nuclear_Space.docx

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

1.0 SCOPE

The objective of this task order is to provide technical services to 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.

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, or at any Detachment.

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 identify the nuclear, directed energy, and natural space environment survivability capabilities the military users need from acquisition programs, and ensure those capabilities are adequately tested and reported. The method is to improve Integrated Test (combined DT/OT) by engaging the program office and developers to ensure the goals and needs of AFOTEC and the OTAs are considered, included, and met.

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

1.1 BACKGROUND

There are various existing and future strategic programs that may involve nuclear weapons survivability. These include space programs; [Advanced EHF (AEHF), Defense Weather Satellite System (DWSS), Space Based Infrared Satellite System (SBIRS)]; ground terminal programs; [Family of Advanced Beyond Line of Sight Terminals (FAB-T)]; and aircraft programs [KC-46A Replacement Tanker].

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

Applicable to the basic effort and each option, if exercised.

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 The contractor shall, for each program:

3.2.1 Throughout the time the contractor is working the program, consider the potential system impacts from the following threats:

3.2.2 Perform analysis of the system, perform analysis of test capabilities, identify test capability requirements, identify shortfalls, develop methodologies and tools, and recommend approaches through the following steps:

Identify mission Identify mission critical functions and equipment Estimate potential impacts of threats upon functions and equipment Identify potential mission impacts Determine program requirements Determine the System Program Office's (SPO) plans for Developmental Test (DT) for the threats Determine the SPO's plans for HM/HS/HA (Hardness Maintenance, Surveillance, and Assurance) Determine the survivability levels required to ensure user mission accomplishment Identify deficiencies in DT plans and data requirements Identify system specifications that are beyond what is required Work to eliminate deficiencies Push for combined DT/OT events Identify appropriate test tools and methods Participate in combined DT/OT events Analyze and report results

Over the period of involvement with a particular program, some of these steps may need to be repeated.

3.3 Perform the following activities as needed:

3.3.1 Attend meetings: teleconferences, VTCs, test working groups, system design reviews, technical interchange meetings, ITDs, and core team meetings.

3.3.2 Review documents: ORDs, CDDs, 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 threats and concepts of operation, CONOPs, CONEMPs.

3.3.3 When appropriate, recommend to the 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 integrated testing (combined DT/OT tests). Investigate problems found with 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.

3.3.8 Write documents that do require specific formats, such as conference minutes (A003), technical analyses (A017), technical reports (A017), test event reports (A017), and sections of the final report briefing. (A013)

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

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. (A013) Prepare lessons learned reports. (Contractor's format is acceptable.)

4.0. Surveillance Matrix

Table 4.1. Surveillance Matrix

Performance Objective PWS Ref

Performance Threshold Method of Assessment

Item 5: Overall Quality of Performance:

Contractor must efficiently perform all PWS tasks, including those requiring contributions to meetings and reviews.

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. Government Furnished Property – Base Support

Government Furnished Property (GFP)/Government Furnished Information (GFI) AFOTEC will provide program documentation such as the ICD, CDD, 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). 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 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. 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 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 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.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 Briefing Materials (A013). The contractor shall provide briefing material as requested by COR. COR will provide draft and final submission schedule for each briefing request.

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

5.4.5 Reports shall be delivered to:

5.5 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 applies to this work effort. Access to classified documents up to and including Top Secret/Critical Nuclear Weapons Design Information (CNWDI) and Restricted Data is required.

6.1.1 Possess or obtain a facility security clearance to at least Secret prior to performing contract work. If Top Secret work is required, workspace will be provided at Kirtland AFB, NM.

6.1.2 Process classified visits 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.

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 contractor-owned 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 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.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.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.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 OSHA requirements. Detailed information is available on the OSHA website at http://www.osha.gov.

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.