Attachment_1_PWS_FA704615R0001_-_BasicContract_21_Oct_15.docx

AIR FORCE OPERATIONAL TEST AND EVALUATION CENTER (AFOTEC)

FIGHTER TEST SERVICES (FTS)

PERFORMANCE WORK STATEMENT (PWS)

21 October 2015

1.0 SCOPE

The objective of this acquisition is to obtain Operational Test and Evaluation (OT&E) services in response to task orders issued by the contracting officer related to the OT&E of proposed 4th and 5th generation fighter system and programs. Services include a broad range of engineering, technical, and analytical test services in support of OT&E activities. OT&E activities include integrated test functions for Air Force and Multiservice fighter aircraft acquisition programs; test design; test planning, execution, and reporting; post test data analysis; cybersecurity evaluation, digital test tool development and associated tool training; special studies and analysis; and research and development of test capability requirements, shortfalls, and solutions. The contractor will work in a joint and combined test team environment where F-35 Joint Strike Fighter (JSF) OT&E products are developed and coordinated with the United States (US) Air Force (USAF), US Navy (USN), US Marine Corps (USMC), United Kingdom (UK) Air Warfare Centre (AWC), Royal Netherlands Air Force (RNLAF) and Royal Australian Air Force (RAAF) team members. Additionally, the contractor will work in an environment that produces products for F-22 and 4th and 5th generation fighter aircraft updates and modifications.

The scope of this acquisition is to provide engineering, technical and analytical services to support accomplishment of AFOTEC Detachment 1 (Det 1), Edwards Air Force Base (AFB), CA and Det 6, Nellis AFB, NV, OT&E activities using the following core competencies:

Core Competencies

Cybersecurity (including requirements, assessments, and knowledge of Department of Defense (DoD) cyber defense and provision of computer network defense services, functional and technical DoD network capabilities and limitations (to include Internet Protocol, telephony, satellite, Tactical Data Link, Radio Frequency, Integrated Air and Missile Defense System (IAMDS), Industrial Control Systems (ICS), & mobile communications), and Platform Integrated Technology systems and required certification actions/responsibilities (such as Risk Management Framework (RMF) & the DoD Information Assurance Certification and Accreditation Process (DIACAP)).

4th and 5th Generation Fighter Maintainability and Supportability

5th generation secure systems and crypto key management knowledge and experience

Fighter Systems Aerospace Ground Equipment (AGE)

Fighter Systems Support Equipment (SE)

Fighter Airframe and Powerplant

Aircraft Structures

Fighter Aircraft Avionics, Electrical, and Environmental Systems

Fighter Weapons Loading and Alternate Mission Equipment (AME)

Fighter Life Support and Survival Equipment

Aircraft Computerized Maintenance Management Systems

Fighter Logistics (home station and deployed)

Aircraft Maintenance Training Systems

Joint Reliability and Maintainability Evaluation Team (JRMET)

Reliability, Maintainability, and Availability Analysis

Information Operations (IO); specifically Information Assurance (IA) and Electronic Warfare (EW)

Interoperability

Low Observable (LO) Mission Planning

Fighter LO Employment, Tactics, Concept of Operations (CONOPS)

Advanced Sensors (Advanced Electronically Scanned Array (AESA)Radar, Radio Frequency (RF), Electro-Optical (EO), Infra-Red (IR))

Sensor Fusion

Fighter Performance

Fighter Datalinks (Link 16, Intra-Flight Data Link (IFDL), Multi-function Advanced Data Link (MADL)

Aircrew Training Systems

Fighter Scenario Development including red/blue capabilities

Logistics Composite Model (LCOM) experience and operation

Multirole Fighter Aircrew (Offensive Counter Air (OCA), Defensive Counter Air (DCA), Suppression of Enemy Air Defenses (SEAD)/Destruction of Enemy Air Defenses (DEAD), Electronic Warfare (EW), Close Air Support (CAS))

Software Engineering/Programming/Database Management

Fighter Test Instrumentation and Real-time/Post flight data processing

Mission Level, Man-in-the-Loop Modeling and Simulation (Requirements and Verification, Validation and Accreditation (VV&A))

Fighter Weapons Effectiveness Analysis

Air-to-Air Range Infrastructure (AARI)

Intel/Operations Debriefing

Range Training Officer/Kill Removal Officer (Red Flag, Cope Thunder or similar)

Range Requirements/Coordination/Scheduling

Operations Analysis (including Math/Statistics/Design of Experiments (DOE), data analysis)

Flight Test Execution and Analysis

Net-Centric Warfare Systems Integration(to include working knowledge of cyber and electronic warfare integration capabilities with 4th and 5th generation data link systems)

The Contractor shall support task orders for various test and evaluation efforts and phases, consisting of various sizes and complexities of Department of Defense (DoD) related systems. A system is understood to be an assembly or combination of interrelated elements (hardware, software, materiel, training, tactics, or procedures) working together toward a common objective or performance requirement.

Each task order shall direct tasks in one or more areas specified in Section 3.0 of this PWS. The potential places of performance include Edwards AFB, CA, Nellis AFB, NV, HQ AFOTEC at Kirtland AFB, NM, any Det 1 or Det 6 Geographically Separated Unit (GSU) or Operating Location (OL), any Government test range, and contractor facilities. Current OL and GSU locations include Fort Worth, TX, Arlington, VA, Norfolk, VA, Marietta, GA, and Patuxent River, MD. This PWS applies only to Det 1 and Det 6 Fighter Programs.

Each approved task order may identify: the objective, scope, specific work location(s), background, applicable documents, technical requirements, desirable skill set (core competency), period of performance and required schedule, data items, deliverables, government property, and any other considerations for each task.

In rendering services to the identified tasks, outputs may take the form of information, advice, opinions, alternatives, analyses, evaluations, recommendations, and/or services to complement the Government's technical expertise in accomplishing its mission

1.1 Background. The overarching functions of Test and Evaluation (T&E) are to mature system designs, manage risks, identify and help resolve deficiencies as early as possible, and ensure systems are operationally mission capable (i.e., effective and suitable). AFOTEC is responsible for planning, executing, and reporting independent OT&E. AFOTEC supports Air Force, DoD and other government agencies by:

· Testing and evaluating new weapon system capabilities in operationally realistic battlespace environments to provide independent, fact-based, decision-quality data to inform decision makers on a range of accurate, balanced, and timely assessments of effectiveness, suitability, and mission capability.

· Conducting and/or participating in the following types of testing: Initial Operational Test and Evaluation (IOT&E); Follow-on Operational Test and Evaluation (FOT&E): Multi-Service OT&E (MOT&E); Qualification OT&E (QOT&E); Operational Utility Evaluation (OUE) and others as defined in AFI 99-103.

· Achieving positive effects on air, space and cyberspace capabilities through early influence of capability requirements development, early acquisition strategy/planning efforts, integrated testing, and timely operational test reporting.

· Directly supporting Air Force Goals: Sustain air, space, and cyberspace capabilities; and, foster Air Force Smart Operations across the Total Air Force.

AFOTEC Det 1, headquartered at Edwards AFB, CA, serves as the lead Operational Test Agency (OTA) for the multi-service, multi-national F-35 Operational Test and Evaluation (OT&E). In addition to AFOTEC, the F-35 JSF Operational Test Team (JOTT) consists of IOT&E participants from other OTAs that include the United States Navy/United States Marine Corps (USN/USMC) Commander, Operational Test and Evaluation Force (COMOPTEVFOR), the United Kingdom (UK) Air Warfare Centre (AWC), the Royal Netherlands Air Force (RNLAF) and the Royal Australian Air Force (RAAF). The F-35 OT&E will consist of multiple Operational Assessments (OA), OT&E, and Initial Operational Test and Evaluation (IOT&E). Associate Contractor Agreements (ACA) may be required as detailed in the task orders.

AFOTEC Det 6, headquartered at Nellis AFB, NV, is the lead for all other AFOTEC fighter and fighter system OT&E to include the F-22, F-15C, F-15E, F-16, and A-10 aircraft and related systems such as targeting pods and data links.

2.0 APPLICABLE DOCUMENTS

Applicable guidance consists of Department of Defense, Air Force and AFOTEC documents associated with requirements definition, acquisition, and test and evaluation. The contractor shall use the most current version. Key documents applicable to this PWS are listed in the table below. The government documents cited as references in this PWS are available electronically and will be provided by AFOTEC only if not readily available from publically accessible sources. Each task order will identify unique guidance not contained herein.

Reference

Title Specific Paragraphs/Chapters/Sections

AFOTECMAN

99-101

AFOTECPAM

99-104

DOT&E Memo, 21 Jan 2009

DOT&E Memo, 4 Nov 2010

DOT&E Memo, 1 Feb 2013

DOT&E Memo, 1 Aug 2014 Procedures for Operational Test and Evaluation of Cybersecurity in Acquisition Programs

Entire document

3.0 PERFORMANCE REQUIREMENTS

The contractor shall perform requirements within the service task areas listed in this section. Task orders will identify specific tasks for completion within a specific period of time. The contractor shall initiate no work under a task order without written approval by the contracting officer. These efforts apply to new and legacy fighter aircraft and associated systems.

3.1 Management Requirements. The contractor shall:

3.1.1 Prepare task order proposals in support of task order performance requirements in accordance with the task order procedures set forth in Section 10 below. Identify and propose mitigation for any organizational conflict of interest associated with supporting each task order. Task management costs, both direct and indirect, shall be reflected for each task order. The contractor shall identify an appropriate management approach for each task order and shall be required to submit corrective management plans as necessary.

3.1.2 Be responsible for overall responsiveness, cost control and reporting, adherence to schedule, ability to adapt to schedule changes, responsible and cooperative behavior, data management, technical quality of work, management of contractor team's efforts including level of understanding of AFOTEC's mission and commitment to customer satisfaction.

3.1.3 Maintain a Quality Control Program (QCP) that ensures the government receives the level of quality that is consistent with the requirements specified in each task order.

3.1.4 Be responsible for a risk plan, including risk identification and mitigation associated with supporting each task order.

3.1.5 Include a management method for information flow/sharing between Det 1 and Det 6 task orders.

3.2 Test Capabilities. Test capabilities consist of infrastructure (ranges, simulators, labs, instrumentation, etc.), modeling and simulation tools, data management and analysis tools, and analytical methodologies and techniques used to support OT&E. Test capability activities are the formal processes of identifying/developing test capability requirements, shortfalls, and solutions. Activities include identifying test capability requirements, documenting existing test capabilities, identifying shortfalls, performing trade-off analyses, and recommending approaches to solve issues. The contractor shall:

3.2.1 Perform analysis of test capabilities. Activities include: identifying test capability requirements, documenting existing test capabilities, identifying shortfalls, performing trade-off analyses, and recommending approaches to solve issues.

3.2.2 Identify, develop, modify, verify, and/or validate modeling and simulation tools such as constructive tools that represent real world entities by means of computer models, virtual tools involving real people operating simulated systems and live tools involving real people operating real systems.

3.2.3 Participate, develop, and/or update modeling and simulation (M&S) verification, validation, and accreditation (VV&A) plans and/or reports.

3.2.4 Train government personnel in the operation, interpretation of outputs, and maintenance of contractor developed test tools such as computer software, applications, instrumentation, and models and simulations.

3.2.5 Identify, develop, and/or apply analytical techniques, methodologies, and tools for OT&E.

3.2.6 Develop and/or integrate Commercial Off the Shelf (COTS) based data and graphical analysis tools that are capable of high fidelity mission data replay using any combination of aircraft, M&S, and/or range instrumentation truth data.

3.2.7 Provide system level/test methodology training in Subject Matter Expert (SME) areas to appropriate government personnel using continuity books, briefings, and on-the-job training.

3.2.8 Identify and document modifications to Air-to-Air Range Infrastructure (AARI) graphical displays, user interfaces, and weapon models beyond existing AARI toolsets to meet test execution and data requirements. Work on-site with AARI development team.

3.2.9 Maintain configuration management of developed and modified M&S, analysis, and data processing tools.

3.2.10 Identify, develop, recommend, and/or integrate test capabilities for ranges, and ways to use test capabilities to answer operational questions.

3.2.11 Identify, develop, recommend, and/or integrate test capabilities for cyber test ranges, and ways to use test capabilities for red and blue team activities to answer operational questions.

3.2.12 Provide input to assist with developing and coordinating annual forecasts for munitions, missiles, targets, and expendables.

3.2.13 Develop an instrumentation plan for the System Under Test (SUT). Identify instrumentation system requirements and document system design in an Interface Control Document (ICD) or appropriate document.

3.2.14 Perform fighter weaponeering including weapons analysis, air-to-ground weapons, air-to-air weapons, and fighter expendables and countermeasures.

3.2.15 Develop inputs for the delivery of combined OT&E briefings and debriefings for program/OT&E events.

3.3 Test Planning. Test planning focuses on developing test designs/concepts, supporting program/technical reviews, developing test plans, developing Data Management and Analysis Plans (DMAP), establishing deficiency reporting, supporting test readiness reviews, and developing briefings. The contractor shall:

3.3.1 Provide input to develop red and blue team planning

3.3.2 Provide input to develop and/or revise the evaluation framework.

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

3.3.4 Provide input in developing critical operational issues (COIs), measures of effectiveness (MOE) and measures of suitability (MOS).

3.3.5 Provide input in developing operational test scenarios.

3.3.6 Analyze and submit test methodologies, identify test risks and limitations and propose mitigation strategies, and test readiness and support requirements needed to complete the OT&E plan.

3.3.7 Provide input into developing test methodologies and test scenarios for AFOTEC, Director of Operational Test and Evaluation (DOT&E), and program special interest items.

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

3.3.9 Provide input to develop and/or revise the basis of estimate for test resources (e.g. test resource plan) to accomplish the test design.

3.3.10 Review for test and evaluation considerations and document feedback on program documents such as the: Program Management Directive (PMD), any capabilities documents, System Threat Assessment Report (STAR), Test and Evaluation Master Plan (TEMP), Lifecycle Management Plan (LCMP), Program Protection documents, and concepts of operations, maintenance, and employment.

3.3.11 Provide input to develop and/or revise AFOTEC portions of test documentation such as test team charters, test and evaluation master plans (TEMPs), and integrated test plans.

3.3.12 Participate as an Integrated Test Team member to gain knowledge of Integrated Testing (IT) activities.

3.3.13 Identify OT&E test planning requirements and design priorities in order to eliminate redundancies between the OT&E and the OT&E program.

3.3.14 Perform site surveys on potential test sites and prepare site preparation requirements such as defining site specific installation, integration, preparation of environmental permit plans, and integration of AFOTEC equipment with equipment available from other agencies or host areas.

3.3.15 Provide environmental health and safety planning services for test programs addressing occupational health, and environmental concerns.

3.3.16 Identify and describe data requirements and specific data processing and analysis tools needed to complete the Data Management and Analysis Plan (DMAP).

3.3.17 Review and incorporate joint and combined Lessons Learned from other OT&E efforts into Det 1 and Det 6 test plans and execution.

3.3.18 Develop, propose staff coordination, and provide configuration control for OT&E Test Plans, briefings, reports and other related program documents. All product timelines shall be linked to program requirements or current OT schedule.

3.3.19 Develop program introduction documents (PIO) for the appropriate range support.

3.3.20 Provide input in developing the Joint Reliability and Maintainability Evaluation Team (JRMET) charter.

3.3.21 Prepare and track status of deficiency reports.

3.3.22 Support Readiness to Test (RTT) planning, tracking, resolution, and checklist items.

3.3.23 Prepare for the conduct of OT&E control room White Force Command and Control Operations during test trials. Define white force tasks (i.e. white force commander, kill removal officers, lead analyst, and observers), task rehearsals, and post-trial debriefing efforts.

3.3.24 Develop and/or present talking papers or briefings on OT&E efforts to various meetings and conferences.

3.3.25 Provide input to develop planning for cybersecurity and cyber test events, including schedule, location, qualified personnel, methodology and best practices. This will include participating in joint and combined cybersecurity conferences, working groups and task forces.

3.4 Test Execution. Test execution consists of all activities associated with executing the OT&E plan with identified resources. The contractor shall:

3.4.1 Provide field operations services such as deployment/redeployment, requesting/scheduling/tracking of test equipment resources, identifying/preparing test equipment, and calibrating test instrumentation and site support equipment with on-site equipment and power.

3.4.2 Provide safety services such as ground, flight, and environmental protection support in compliance with safety, occupational health, and environmental concerns/regulations.

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

3.4.4 Use, develop, modify, and/or maintain 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 Conduct OT&E control room White Force Command and Control Operations during test trials including white force tasks (i.e. white force commander, kill removal officers, analyst, and observers) task rehearsals, and post-trial debriefing efforts.

3.4.6 Participate in and collect data from DT&E operations to support integrated testing.

3.4.7 Participate in the execution of cybersecurity and cyber test events IAW the cyber plans developed.

3.5 Test Evaluation. Test evaluation determines if the system under test meets the warfighter's mission needs, in addition to system requirements as outlined in the program requirement documents. The contractor shall:

3.5.1 Collect, compile, review, and analyze test data.

3.5.2 Run computer models and simulations and analyze/characterize the resulting output.

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

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

3.5.5 Participate in the Joint Reliability and Maintainability Evaluation Team (JRMET) and attend on-going meetings to provide subject matter expertise on the accuracy and completeness of the JRMET process and charter.

3.6 Test Reporting. Test reporting consists of communicating the analysis and evaluation of test results. Test reporting may be required in any multimedia format. The contractor shall:

3.6.1 Prepare test documentation for inclusion in OT&E reports.

3.6.2 Participate with government personnel in the research and preparation of audio, animation, video, graphics, and still pictures and insert into test plans, reports and associated briefings.

3.6.3 Prepare and/or present briefings as a part of the report coordination process.

3.6.4 Prepare lessons learned reports.

3.6.5 Participate in the development of quick-look, interim, and final reports.

3.6.6 Brief SME areas to associated audiences as pertaining to quick-look, interim, and final reports.

3.7 FOT&E. FOT&E is the continuation of OT&E after IOT&E, QOT&E or MOT&E. It answers specific questions about unresolved test issues. The contractor shall:

3.7.1 Participate in the verification of the resolution of IOT&E, QOT&E or MOT&E deficiencies or shortfalls determined to have substantial or severe impact(s) on mission operations.

3.7.2 Provide services to complete T&E of areas not finished or deferred during IOT&E, QOT&E or MOT&E that are determined to have substantial or severe impact(s) on mission operations.

3.7.3 Participate in block upgrades, modifications, or pre-planned product improvements following the completion of IOT&E, QOT&E or MOT&E.

3.8 Program Protection Support Service Requirements. The contractor shall support the program protection support service requirements of this effort. The contractor shall:

3.8.1 Follow public laws, Country Memorandums of Understanding (MOU), DOD, Air Force and AFOTEC regulations that require the protection of information. This protection shall be built into all joint and combine OT&E activities.

3.8.2 Provide input for the conduct of program security risk assessments to include threat and vulnerability analyses.

3.8.3 Provide inputs for the development and implementation of plans to mitigate security risks, which may include foreign country participation, test range operations, education, training, and countermeasures.

3.8.4 Participate in the efforts to provide security support such as the monitoring and execution of International Traffic in Arms Regulation (ITAR) requirements, information security, computer security, communications security, and operations security.

3.8.5 Technical Assistance Agreement(s) (TAA) The contractor may be required to register with the State Department as a prerequisite to obtaining and executing Technical Assistance Agreements in accordance with (IAW) Defense Federal Acquisition Regulations System (DFARS) Subpart 227.6 Foreign License and Technical Assistance Agreements. The requirement for a TAA will be identified in individual task orders.

4.0 SERVICE SUMMARY ITEMS

Contracting Officer Representatives (CORs) will use Table 4.1 as a guide when identifying service summary items in Task Orders.

Table 4.1 Service Summary

Ref Performance Threshold

complaints/contract discrepancy reports per Task Order. The contractor successfully resolves customer complaints within 10 working days of receipt, 100% of the time.

5.0 GENERAL INFORMATION, DELIVERABLES, SCHEDULES, AND REPORTING

5.1 The Government will neither supervise Contractor employees nor control the method by which the Contractor performs the required tasks. Under no circumstances shall the Government assign tasks to, or prepare work schedules for individual Contractor employees. It shall be the responsibility of the Contractor to manage their employees and to guard against any actions that are of the nature of personal services, or give the perception of personal services. If the Contractor feels that any actions constitute, or are perceived to constitute personal services, it shall be the Contractor’s further responsibility to notify the PCO immediately.

5.2 Contracting Officer Authorization. The Contracting Officer shall be the only individual authorized to direct and/or redirect the effort or in any way amend any of the terms of this contract, other than those instances specifically delegated to an Administrative Contracting Officer or a Termination Contracting Officer by a contract clause of this contract or in writing by the Procuring Contracting Officer (PCO). For purposes of this contract "the Contracting Officer" is the individual located at the issuing office, and may be abbreviated as "CO" or "PCO". Any changes made by the contractor WITHOUT CO authority will be made at the contractor's own risk.

5.3 Hours of Work and Contract Holidays. The contractor shall provide services Monday through Friday, except for Federal Holidays. Occasional weekend work may be required and will be coordinated between the Government and the contractor. The prices/costs in Section B of the contract include holiday observances; accordingly, the Government will not be billed for such holidays, except when services are required by the Government and are actually performed on a holiday. Holidays in addition to those reflected in this contract, which are designated by the Government, will be billable provided the assigned Contractor employee was available for performance and was precluded from such performance. The following days are contract holidays:

(10) Christmas Day

5.4 Relocation Costs

a. Relocation costs are prohibited unless approved by the Contracting Officer.

b. In rare circumstances, the Government or Contractor may request a permanent change of station for a contractor employee when it is in the best interest of the Government to meet program objectives. In such a circumstance, upon negotiation with and approved by the Contracting Officer, the contractor may charge relocation costs as “travel” costs under CLIN 0003 of this contract/task order.

c. Per FAR 31.205-35(b)(2), the contractor must adhere to its established policy or practice when charging relocation costs to this contract/task order. In addition, the contractor shall comply with all requirements of FAR 31.205-35 – Relocation Costs, and shall refund or credit the relocation costs to the Government if the employee resigns, is terminated, or is reassigned in such manner that the employee no longer provides support to this contract within 12 months of the date of the move for which relocation costs are charged.

d. In no event shall relocation costs be allowable without prior written approval of the Contracting Officer.

5.5 Government Furnished Property-Base Support. When the Task Order requires the Contactor to work in a Government facility, the Government may furnish or make available working space, equipment, and network access. Copies of required materials cited in the RFP, PWS, DD Form 254, and/or in the Task Order may be provided to the contractor in hard copy or soft copy. All materials will remain the property of the Government and will be returned to the COR upon request or at the end of the Task Order period of performance.

5.6 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 (JTR). Contractors will not be required to price any travel costs on task orders. Ceilings will be established at time of award of each individual task order where the ceilings shall be inclusive of all indirect costs.

5.7 Government Downtime for Various Authorities Including the President, Secretary of Defense, Secretary of the Air Force, AFOTEC/CC, or Base Commander of any Government Installation where work is performed.

(a) Base Closures Due to Emergencies. From time to time, the AFOTEC or Base Commander, of any Government installation where work is performed, may decide to close all or part of the base in response to an unforeseen emergency or similar occurrence. Sample emergencies include, but are not limited to, adverse weather such as snow or flood, an act of God such as a tornado or earthquake, acts of war or terrorism, computer failures or a base disaster such as a natural gas leak or fire. Contractor personnel are "non-essential personnel" for purposes of any instructions regarding the emergency.

(1) Contractor shall be officially dismissed upon notification of a base closure in accordance with paragraph b. Contractor shall promptly secure all government furnished property appropriately and evacuate in an expedient but safe manner.

(2) With regard to work under the contract, the government shall retain the following options:

1. Government may grant a time extension in the contract, delayed by the closure equal to the time of the closure, subject to the availability of funds.

1. Government may forego the work. The contractor will not be paid for work not performed.

1. Government may reschedule the work on any day satisfactory to both parties.

1. The government may, in its discretion, permit the contractor to perform at an off-site location during the period of base closure if meaningful work can be accomplished. Contractor shall certify to the government by letter within 5 businesses days of returning to work the nature and scope of the work completed off-site. Contractor shall be permitted to bill the government at the labor rates identified in the contract.

1. In rare instances, Government may request that the Contractor continue on-site performance during the base closure period. Such a request shall be subject to agreement by Contractor.

(b) Base Closure Notification Procedures.

(1) After an official decision to close the base has been made by the AFOTEC or Base Commander, of any Government installation where work is performed, local television and radio stations will be notified of the closure.

(2) The Contractor is directed to listen or watch one of the local radio or television stations for notification of a base closure. Contractor should follow instructions intended for non-essential personnel.

(3) The contractor will not receive any other form of notification of a base closure from the government. The Contractor is responsible for notification of his or her employees.

(4) If the decision to close all or part of the base is made during the duty day, and the AFOTEC or Base Commander's, of any Government installation where work is performed, decision is transmitted through official notification channels, the Contractor shall follow the instructions as given. Contractor personnel shall notify their COR and act in accordance with the Contract Officer Representative’s (COR) instruction.

(c) Base Closure Due to Non-Emergencies. The AFOTEC or Base Commander, of any Government installation where work is performed, may elect to close all or part of Kirtland Air Force base or any other Government installation where work is performed, for non-emergency reasons such as time-off award, base open house, etc. In the event of a non-emergency base closure, the COR and the Contractor shall jointly choose a course of action within the following options:

(1) If there is a need for the service during the base closure the Contractor may continue on-site work. Contractor shall bill the Government in accordance with the contract.

(2) If there is a need for work during the base closure but access will not be available, the Contractor may work off-site provided meaningful work may be accomplished. Contractor shall certify to the government by letter within 5 business days or returning on-site the nature and scope of the work completed off-site. Contractor shall bill the Government at the labor rates specified in the contract.

(3) If there is no need for the service during the scheduled base closure, contractor shall not work on or off-site. Government may grant a time extension by the closure equal to the amount of time of the closure, subject to the availability of funds. The government will not be liable for time not worked.

5.8 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 the interruption. Therefore, the contract must provide for maximum cooperation between successor and incumbent while ensuring 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.8.1 Phase-In. As a successor, the FTS contractor shall ensure a smooth transition with the incumbent Fighter OTES contractor during the phase-in period. The contractor shall develop plans for assumption of awarded Task Orders. The contractor must provide an orderly transition of work acceptance and accomplishment so that impact to the program is minimized.

5.8.2 Phase-Out. The FTS incumbent shall ensure a smooth transition with the successor 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.9 Associate Contractor Agreements. The Contractor may enter into Associate Contractor Agreements (ACA) for portions of individual Task Orders requiring joint participation in the accomplishment of the Government's requirement. The agreements shall include the basis for sharing information, data, technical knowledge, expertise, and/or resources essential to the integration of Task Order requirements, which shall ensure the greatest degree of cooperation to meet the terms of the Task Order.

5.10 Period of Performance. The ordering period for FTS will be five years from the date of contract award.

5.11 Contract Data Requirements List (DD Forms1423). Data and documents to be delivered under each authorized task order shall include one or more of the data items listed and on the DD Form 1423. Deliverable reports specific to each task order will be specified in each individual task order.

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

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 16-1404, AFMAN 14-304, JAFAN 6.0, 1-301a (10), and/or DoD 5105.21-M-1.

6.2 Cybersecurity: the contractor shall:

6.1.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.1.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.1.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 Cybersecurity Office 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.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.1.5 All contractor personnel who will be using IT systems belonging to the federal Government to generate, process, store, transfer, or communicate information shall attend mandatory systems security training. The format for the training will be completion of the DoD IAA Cyber Awareness Challenge Course. The training must be completed prior to application for an account on the AF Network. 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 The contractor shall immediately notify the COR of any Government IT 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 No foreign nationals are authorized to work on this effort.

6.1.8 All contractor personnel who require access to Government IT 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 Government 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 the Cybersecurity Office. 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 Security Office. Any interim accesses that may be granted may be rescinded at any time by the PCO, COR, Directorate Security Office or Cybersecurity Office. The requirements for a full NAC shall not be authorized to work under this effort granted by the Security Office. Any interim accesses that may be granted may be rescinded at any time by the PCO, COR, Directorate Security Office or Cybersecurity Office. The requirements for a full NAC shall not be authorized to work under this effort.

7.0 SAFETY REQUIREMENTS

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 are 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. The contractor shall support field events. 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 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 Procuring Contracting Officer and the Contracting Officers Representative for a determination of whether a mitigation plan is required.

9.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 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 identify 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://ww.ecmra.mil.

10.0 Task Order Proposal Procedures

a. When the Government has a requirement for work to be performed, the CO will notify the contractors of:

1. The work to be performed;

1. The desired performance period; and

1. Any other information considered to be of assistance to the Contractor in preparing a proposal. These RFTOPs will be written, and may be transmitted by any means including the mail, E-mail, facsimile or Internet. The standard method of transmission will be E-mail.

b. The Request For Task Order Proposal (RFTOP) shall not obligate the Government to issue Task Orders under this contract, nor shall it authorize the Contractor to perform any work pursuant to such requests for proposal prior to the Contractor’s receipt of an authorized notice to proceed.

c. Task Order Proposals (TOP) shall consist of management and technical data, and cost/price information. TOPs shall be submitted in a format readable and useable with Microsoft Excel 2010. All spreadsheets shall include all cell formulas.

d. TOPs shall include, but not limited to, the…