FINAL_PWS_FA704615R0001-0001_21_Oct_15.docx

FA7046-15-R-0001

PERFORMANCE WORK STATEMENT

Task Order 0001 F-35 Joint Strike Fighter (JSF) Air System Operational Test and Evaluation (OT&E) Core Planning Team 21 October 2015

1.0 SCOPE

This effort shall be conducted pursuant to the provisions of the Fighter Test Services (FTS) contract Performance Work Statement (PWS) paragraphs 3.0, 3.1, 3.2, 3.3, 3.4, 3.5, 3.6, and 3.7. The objective of this task order is to provide test capabilities, planning, execution and reporting of F-35 Operational Test to the Air Force Operational Test and Evaluation Center (AFOTEC) Detachment (Det) 1. This effort includes test plans, data management and analysis plans, and detailed test procedures development, execution, and results reported to the appropriate decision-makers. The majority of tasks will be performed jointly with the Government.

This task order supports operational assessments (OA), Initial Operational Test and Evaluation (IOT&E), and Operational Test (OT). The contractor shall work in a joint and combined test team environment where F-35 operational test products are developed and coordinated with the US Air Force, US Navy, US Marine Corps, United Kingdom (UK) Air Warfare Centre (AWC), Royal Netherlands Air Force (RNLAF) and Royal Australian Air Force (RAAF) team members. The Core Planning Team will continue test planning activities during execution including updates to plans as the test progresses. Test planning, execution, and reporting requires specialized skills to test Low Observable (LO), sensor fusion aircraft in both open-air and modeling and simulation. Additionally, the Core Planning Team will be augmented with another task order supporting test execution.

The potential locations of performance include AFOTEC Detachment 1 (Det 1) primary location of Edwards AFB, CA; AFOTEC Det 1 Operating Locations (OL); and/or temporary duty at government test range locations and other associated facilities/locations as approved by the JOTT Combined Test Director. Current AFOTEC Det 1 OLs include: Fort Worth, TX (OL-FT), Marietta, GA (OL-MG) and Arlington, VA (OL-AV).

1.1. Background. 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), and the United Kingdom (UK) Air Warfare Centre (AWC). Other national partners participating include the Royal Netherlands Air Force (RNLAF) and the Royal Australian Air Force (RAAF). The F-35 OT&E will consist of multiple OAs, IOT&E, and OT of flying, simulator, suitability and other test events.

2.0 APPLICABLE DOCUMENTS

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

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

2.2.1. F-35 Test and Evaluation Master Plan (TEMP) Revision 4, 23 May 2013 (in its entirety, both classified and unclassified versions)

2.2.2. JSF Operational Requirements Document (ORD), Change 3, 19 Aug 2008 (in its entirety-unclassified only)

2.2.3. F-35 Acquisition Strategy 4.0, 27 March 2012 (in its entirety)

2.2.4. F-35 Joint Strike Fighter (JSF) Operational Assessment (OA) Plan OT-IIE, 1May 2010 (in its entirety -unclassified only)

2.2.5. JSF IOT&E MOU- US, UK, 27 Jan 2007

2.2.6. JSF IOT&E MOU – US, UK, NL, IT, 30 May 2008

2.2.7. F-35 Readiness to Test (RTT), Team Process, Nov 09 (in its entirety)

2.2.8. JSF RTT Templates (in its entirety)

2.2.9. RTT Periodic Review -7 May l0 (PowerPoint Briefing - in its entirety)

2.2.10. JSF Operational Test Team IOT&E Management Plan, 17 Nov 08, (in its entirety)

2.2.11. Roadmap to OT Management Plan, 5 Aug 10, (in its entirety)

3.0 PERFORMANCE REQUIREMENTS

3.1. Management Requirements. Provide a management structure to ensure efficient management of this effort in compliance with Section 3.1 through 3.7.5 of the Core Planning Team Performance Work Statement (PWS). (A001, A002, A003)

3.2. F-35 Test Capabilities. The contractor shall:

3.2.1. Identify and document into appropriate documents test capability requirements, existing test capabilities shortfalls, trade-off analyses for resolution of shortfalls, and recommend approaches to resolve F-35 OT issues. (A021)

3.2.2. Identify, develop, modify, verify, and/or validate modeling and simulation 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.2.1. Participate in planning, documenting, developing and supporting implementation and validation of probability of removal (Pr) tables for use with AARI and F-35 Verification Simulation Environment (VSE). These tables will be used to adequately support real-time kill removal within AARI and F-35 VSE and shall capture the effects of the representative capabilities of both threat and System Under Test (SUT) weapons end game effects. Process (A012, A021, A032, A033, and B007)

3.2.3. Participate, develop, and/or update modeling and simulation (M&S) verification, validation, and accreditation (VV&A) plans and/or reports for the F-35 VSE and other M&S tools.

3.2.3.1. Participate in the development, coordination, and approval of VV&A plans. VV&A is an integral part of the use of M&S in the F-35 OT&E Program. All uses of M&S shall address VV&A requirements in terms of the potential use of M&S and current government policy on the degree of VV&A required. Results of this task shall be either separate VV&A plans for each M&S venue, or an integrated plan. (A032)

3.2.3.2. Conduct of VV&A. Participate in VV&A activities required for OT&E planning and execution. Activities under this paragraph are focused on F-35 VSE and its associated support models and databases. (A032, A033)

3.2.4. Maintain configuration management of developed and modified tools. Identify, develop, and/or apply analytical techniques, methodologies, and tools for F-35 OT.

3.2.5. Identify, develop, recommend, and/or integrate test capabilities (including Air-to-Air Range Infrastructure (AARI)) for ranges, and ways to use test capabilities to answer operational questions.

3.2.5.1. Provide specialized technical expertise to support investigation of solutions to technical issues related to test planning and analysis of test results. Technical areas include:

1) Experimental test design.

2) Analysis and investigation of Integrated Air Defense System (IADS) capabilities.

3) Analysis of mission reliability to include methods for censored data and complex failure modes.

4) VV&A methods for federated simulations, including risk-based approaches, methods to formulate validation criteria (for individual and combined elements) of a federated simulation with impacts on mission outcomes. (A012, A021, H- 270)

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

3.2.7. Develop an instrumentation plan for the F-35. Identify instrumentation system requirements and document system design in an interface control document (ICD) or appropriate document.

3.2.8. 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. (A020, A021)

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

3.2.10. Develop and deliver combined OT&E briefings and debriefings for program/OT&E events. (A013)

3.2.11. Participate in identifying and documenting a Data Acquisition Recording Telemetry (DART) ground station user guide/manual for processing various security levels of aircraft data (periods processing and requirements for and considerations of handling COMSEC data in the data stream), include procedures for handling and processing various national data sets (US, UK, NL, AU), archiving data through COTS software and performing backups, and general DART data preparation and processing. (B012)

3.2.12. Train government personnel in the operation, interpretation of outputs, and maintenance of test tools such as computers, databases, instrumentation, and models and simulations and data analysis systems. This will include range system operations, systems and range data systems/toolsets. Training will occur as new members are added to the team, or current members obtain appropriate clearances. This includes both effectiveness and suitability models currently used by the JOTT. (A020)

3.2.13. Participate in developing and documenting detailed F-35 IOT&E range interface requirements and concepts (both classified and unclassified).

3.2.13.1. Recommend options for the identification, development, and/or application of analytical techniques, methodologies, and tools for combined OT&E efforts. Include combat identification issues of targets and friendlies in close air support environment, low light identification of targets and friendlies, use of streaming video in identification of targets and friendlies, and Communications, Navigation, and Identification (CNI) use in identification of targets and friendlies. Include dynamic measurement options, importance, and significance for on-board use.

3.2.14. Participate in documenting test capability requirements and concepts for F-35 instrumentation, data capture and data analysis system needed to support OT&E. Contractor shall make recommendations on specific data bus message requirements for the System Under Test (SUT).

3.2.15. Develop and integrate a classified F-35 OT data and graphical analysis system using COTS software products that is capable of measure computation and analyses and mission data replay of all player Time Space Position Indication (TSPI) and track data, that correlates TSPI with various track data and that ensures interoperability and transparency between the disparate range data sets and M&S facilities' data sets and OT analysis tools. (B001, B002, B006, B007)

3.2.16. Develop user manuals for the operation, interpretation of outputs, and maintenance of contractor developed test tools. (B012)

3.2.17. Develop, present and maintain an up-to-date F-35 OT Orientation using AFOTEC, USN, USMC and F-35 training programs. (A011)

3.2.17.1. This presentation combines information from all F-35 program documentation into one source to provide a general overview of JOTT and the Operational Test. This document shall be presented during the training (orientation) period.

3.2.18. Provide inputs for the development of test resource plans.

3.3. Test Planning. The contractor shall:

3.3.1. Provide input to develop and/or revise the F-35 Initial Test Design.

3.3.2. Provide input to develop and/or revise the F-35 OT Test Concept. (A013)

3.3.3. Provide input to develop and/or revise the F-35 OA Plans and Briefs. (A0 l 4, A022)

3.3.4. Provide input to develop and/or revise the F-35 Test Plans and Briefs. (A015, A023)

3.3.5. Provide input to develop and/or revise the F-35 Data Management and Analysis Plans (DMAP). (A028)

3.3.6. Provide input to develop and/or revise the F-35 Detail Test Procedures (DTP) to include range execution, debriefing, AARI data and data collection. (A029)

3.3.7. 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.8. Review for test and evaluation considerations and document feedback on the Program Management Directive (PMD), all capabilities documents, System Threat Assessment Report (STAR), Test and Evaluation Master Plan (TEMP), Lifecycle Management Plan (LCMP), program protection documents, and concepts of operations and maintenance. (A021)

3.3.9. Participate with the Integrated Test Force (ITF) to gain knowledge of F-35 Integrated Developmental Test/Operational Test (IDT/OT) activities.

3.3.10. Prepare, submit and/or revise AFOTEC portions of test documentation to include test team charters, TEMPs, integrated test plans, OT&E plans, DMAPs, detailed test procedures, test planning briefings, and schedules (A021)

3.3.11. Analyze and submit test methodologies, test scenario descriptions, test measures, test risk/ limitation and mitigation strategies, and test readiness and support requirements needed to complete the F-35 OT&E plan.

3.3.12. Perform site surveys on potential test sites, and prepare site preparation requirements. (A004)

3.3.13. Provide environmental health and safety planning for test programs addressing occupational health, and environmental concerns. (A008, A009, A010, A011)

3.3.14. Identify, describe, and/or apply distributed test techniques and real-time simulations to enable interactions among many users.

3.3.15. Review and incorporate joint and combined Lessons Learned from other OT&E efforts (i.e. F-22, F/A-18, and others) into F-35 test plans and execution.

3.3.16. 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 F-35 OT schedule.

3.3.17. Develop Program Introduction Documents (PIDs) for the appropriate range support. (A021)

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

3.3.19. Provide inputs to Readiness to Test (RTT) process planning, tracking, resolution, and checklist items.

3.3.20. Recommend evaluation methodologies and general analytic techniques, assess data requirements, and review specific data collection tools.

3.3.21. Attend Technical Interchange Meetings (TIMs), IPT working groups, design reviews, and discussions with the JSF Program Office (JPO), Air Combat Command (ACC), COMOPTEVFOR, Integrated Test Force (ITF), United Kingdom Air Warfare Centre (AWC), and the development contractor personnel. (A004)

3.3.22. Identify F-35 OT&E test planning requirements and design priorities in order to eliminate redundancies between the DT&E and the joint and combined OT&E program.

3.3.23. Participate in developing methods for evaluating each of the required test measures. Methods shall include a mixture of analysis, modeling and simulation (M&S), field test, M&S versus field and open-air test data, required data elements, test conditions, resources, and schedules via trade-off analysis to determine optimal methodologies.

3.3.24. Participate in updating the F-35 OT M&S plan and keep current with the DT test schedule and plan. Correlate changes to the F-35 OT plan of M&S usage based on DT progress/deletions. (A021, A03 l, A032)

3.3.25. Participate in updating and maintaining the signature sustainment evaluation methodology using current pole and chamber testing products to refine the signature evaluation methodology. This includes describing possible configuration concerns, operational impact over time, establishing a firm baseline, and LO maintenance efforts evaluating a unit's ability to effectively perform LO coating restoration activities to maintain aircraft Radar Cross Section (RCS) signature within mandated guidelines and evaluating the overall performance of the LO system to withstand day-to-day flight operations in an operational flight line environment. (A02 l)

3.3.25.1. Participate in updating and maintaining a methodology to interpret and evaluate F-35 signature performance from government test range data. This methodology shall serve to verify F-35 signature assumptions at specified periods throughout test, anticipate performance during open-air mission level evaluations, and participate in resolving observed anomalies.

3.3.25.2. Upon government approval, coordinate and interface with other government test agencies to ensure F-35 signature performance results and conclusions are consistent with existing fifth generation LO fighter evaluation techniques.

3.3.25.3. Participate in performing trial runs of computer models and virtual simulations and provide inputs to analyze/characterize the models and simulations performance.

3.3.26. Participate in joint and combined F-35 OT&E planning to incorporate lessons learned into F-35 test plans and execution.

3.3.26.1. Provide F-35 operational test lessons learned when working with the JPO, other DoD/civilian agencies, international partners in support of planning, executing, and reporting of the F-35 program. (A021)

3.3.27. Participate in maintenance of a mission planning test concept/plan for the JSF Offboard Mission Support (OMS) mission planning system. This test concept shall include joint testing by AFOTEC Det 2, COMOPTEVFOR/Mission Planning and JOTT. Mission planning measures shall be developed based on the requirements of the Joint Mission Planning System, service Operational Concepts of Employment and CONOPS, COIs, and measures.

3.3.28. Participate in maintenance of a cryptographic keys test concept in support of AFOTEC, Air Force information Operations Center (AFIOC), Navy Information Operations Command (NIOC) and the Joint Interoperability Test Command (JITC) F-35 testing efforts. This shall include end-to-end testing of cryptographic key support to the F-35.

3.3.29. Participate in maintenance of a mission data reprogramming test concept in support of AFOTEC, AFIOC, NIOC and JITC F-35 testing efforts. This will include end-to-end testing of the process for developing, testing, and fielding mission data for the JSF, to include mission data reprogramming tools.

3.3.30. Participate in maintenance of an Information Assurance (IA) test concept to include the Net Readiness KPP in support of AFOTEC, AFIOC, NIOC and JTIC F-35 testing efforts to include the involvement of service information operations centers and other applicable agencies to conduct OT&E of IA on specific areas of the F-35 and to provide inputs to OT&E reports. The concept shall include IDT/OT with the 46th Test Squadron's independent Security Test and Evaluation efforts in support of the JPO. IA test measures and test events will be developed based on applicable documents, policies, and guidance.

3.3.31. Participate in maintenance of an interoperability test concept, to include Net Readiness KPP in support of AFOTEC, AFIOC, NIOC and JTIC F-35 testing efforts. This concept will support JITC interoperability test data requirements for Interoperability Certification and completion of the Net Readiness KPP. Interoperability test measures will be developed based upon applicable documents, policies, and guidance.

3.3.31.1. As a minimum, address advanced LO fighter attributes of susceptibility including differences between variants, combat ID issues, and lethality issues against various target sets. Develop unique test capabilities needed to test integrated avionics reflecting advanced LO fighter avionics attributes that include integrated avionics, sensor fusion and sensor suites. (A022)

3.3.32. Write and track deficiency reports (DRs). (A030)

3.3.33. Develop and present talking papers or MS PowerPoint presentations on the F-35 joint and combined OT&E efforts to various symposiums and conferences on an as required basis. (A011, A021)

3.3.34. 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, including the JOTT Cybersecurity Working Group (JCWG). (A021)

3.4. Test Execution. The contractor shall:

3.4.1. Operational Assessments (OA):

3.4.1.1. Participate in the execution of the detailed test procedures IAW OA plans during test execution.

3.4.1.2. Perform data collection during the OA per the OA plans.

3.4.1.3. Perform OA data reduction and analysis.

3.4.2. Participate in preparing for the conduct of F-35 OT control room White Force command and control operations during open air test trials. Participate in defining range mission controller white force tasks, task rehearsals, and post-trial debriefing efforts.

3.4.3. Participate in and collect data from DT&E operations to support IDT/OT.

3.4.3.1. Observe and collect applicable data from DT field operations. Field operations are based on system maturity and DT's decision to deploy aircraft to different locations. Observe DT field operations such as deployment/redeployment, tracking and use of all resources, and use this data along with advanced LO fighter lessons learned to plan for OT test objectives.

3.4.3.2. Participate in DT computer analysis when applicable for OT planning and data gathering purposes. Conduct trial runs of applicable computer models and virtual simulations with JOTT ground rules and assumptions and mission scenarios for insight to OT planning.

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

3.5. Test Evaluation. The contractor shall:

3.5.1. Participate in the review and analysis of F-35 test and M&S data (OT and IDT/OT).

3.5.2. Participate in evaluating the results of F-35 data analysis.

3.5.3. Run computer models and simulations and analyze/characterize the resulting output. (A021)

3.5.4. Conduct studies, analyses and evaluations on operation effectiveness, suitability and mission capability of the F-35 during OT&E.

3.5.5. Provide SME inputs for the determination of effectiveness and suitability, and support the assessment of the operational impacts of the F-35.

3.5.6. Identify the impact of any lost test data, and contribute to the preparation of a comprehensive correlation of test results to the mission decomposition efforts performed during test concept development.

3.5.7. Analyze data and information collected relative to the multiple OAs to include the use of System Design & Development (SDD) M&S results and address readiness to enter dedicated OTs.

3.6. Test Reporting. The contractor shall:

3.6.1. Participate in development and delivery of OA reports and briefings. The contractor shall provide inputs to the OA Report NLT 2 weeks prior to the due date established by the government. The contractor shall provide inputs to OA Report Brief NLT 1 week prior to planned briefing date.

3.6.2. Participate in development and delivery of OT reports and briefings. The contractor shall provide inputs to the OT Report NLT 2 weeks prior to the due date established by the government. The contractor shall provide inputs to OT Report Brief NLT 1 week prior to planned briefing date.

3.6.3. Participate in the research and preparation of audio, animation, video, graphics, and still pictures and insert into test plans, reports and associated briefings. (A020)

3.6.4. Prepare and/or present briefings as a part of the report coordination process. (A011)

3.6.5. Provide inputs for the development of lessons learned reports. (A021)

3.6.6. Develop quick-look and interim reports and briefs. Be prepared to brief SME areas to associated audiences as pertaining to these reports. (A011, A021)

3.7. Program Protection Support Services Requirement. The contractor shall:

3.7.1. Protect F-35 information in all joint and combined OT&E activities IAW public laws, Country MOUs, DoD, AF, and AFOTEC regulations.

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

3.7.3. Register with the state department as a prerequisite to obtaining and executing Technical Assistance Agreement(s) (TAA) in accordance with (IAW) Defense Federal Acquisition Regulations System (DFARS) Subpart 227.6 Foreign License and Technical Assistance Agreements. Adhere to the guidance contained in the TAAs while working with foreign F-35 operational test (OT) participant nations to include the United Kingdom Ministry of Defence, the Netherlands Ministry of Defence, the Australian Department of Defence, and other Cooperative Project Personnel countries that may become future OT participants. Provide an Empowered Official (as defined in International Traffic in Arms Regulations (ITAR)) at JOTT, Edwards AFB, CA having a position of authority for policy or management within the contractor's organization and is legally empowered in writing by the contractor to sign license applications or other requests for approval on behalf of the contractor. (A001)

3.7.3.1. In accordance with the Arms Export Control Act (AECA) as amended, International Traffic in Arms Regulations (ITAR) and Air Force Instruction (AFI) 16-201, Air Force Foreign Disclosure and Technology Transfer Program, the transfer of F-35 technical information to foreign nationals by contractors is not permitted. F-35 technical information intended for foreign consumption within the Joint Operational Test Team (JOTT) must be accomplished as stated in paragraph 3.7.3.2.

3.7.3.2. Provide military controlled unclassified information (CUMI) and controlled classified information (CMI) disclosure analysis and decision rationale in both verbal and written format to the JOTT and the JOTT Foreign Disclosure Officer (FDO). (A011, A021)

3.7.3.3. Provide military controlled unclassified information and program-level controlled classified information disclosure training to the JOTT and JOTT supporting organizations quarterly or as program changes. Provide training material to the FDO for approval. (A011)

3.7.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.7.5. Training. Training on program specific and proprietary systems (not including Microsoft and COTS software) is anticipated to include courses designed to provide updates to computer software techniques, test policy and procedures, F-35 specific training not available to non-F-35 personnel, etc. The government will approve all formal training.

4.0 SERVICE SUMMARY ITEMS

Ref Performance Threshold

Expenditure Reports will be used as tracking tools to identify impact on budget and schedule. Actual task order expenditures shall be within 10% of approved task order price. Meets task order schedule requirements.

5.0 GENERAL INFORMATION

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:

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

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

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

5.4.1.2. With regard to work under the contract, the government shall retain the following options:

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

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

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

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

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

5.4.2. Base Closure Notification Procedures.

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

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

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

5.4.2.1.4. If the decision to close all or part of the base is made during the duty day, and the AFOTEC or Base Commanders 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 Contracting Officer’s Representative’s (COR) instruction.

5.4.3. 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:

5.4.3.1. Option 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.

5.4.3.2. Option 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.

5.4.3.3. Option 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.5. Relocation Costs

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

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

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

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

5.6. Government Furnished Property-Base Support. The Government will furnish or make available applicable working space, equipment, databases and network access to F-35 contractor personnel at the primary test locations (Edwards AFB and Marietta). All materials provided by the Government will remain the property of the Government and will be returned to the F-35 COR upon request or at the end of the task order period of performance.

5.7. Travel Requirements. Contractor employees will be required to travel to various locations both CONUS, seaborne, and outside the continental United States (OCONUS) in performance of this task order. For OCONUS travel, contractor employees shall obtain passports, visas, and medical clearance for designated operations areas and perform required training for government contractor personnel traveling overseas. The Travel Ceiling for this task order, inclusive of all indirect costs, will not exceed the dollar threshold identified in the task order.

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 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.8.1. Phase-In. As a successor, the FTS contractor shall insure 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 program is minimized. Phase-in period is 90 calendar days.

5.8.2. Phase-Out. The Fighter OTES incumbent shall ensure a smooth transition with the FTS successor during phase-in 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. Phase-out period is 90 calendar days.

5.9. Associate Contractor Agreements. The contractor shall enter into Associate Contractor Agreements (ACA) for any portion of the contract requiring joint participation in the accomplishment of the Government's requirement. The agreement shall include the basis for sharing information, data, technical knowledge, expertise, and/or resources essential to the integration of the F-35 OT&E which shall ensure the greatest degree of cooperation for the development of the program to meet the terms of the contract. Associate Contractors are listed below.

5.9.1. ACAs shall include the following general information:

5.9.1.1. Identify the associate contractors and their relationships.

5.9.1.2. Identify the program involved and the relevant Government contracts of the associate contractors.

5.9.1.3. Describe the associate contractor interfaces by general subject matter.

5.9.1.4. Specify the categories of information to be exchanged or support to be provided.

5.9.1.5. Include the expiration date (or event) of the ACA.

5.9.1.6. Identify potential conflicts between relevant Government contracts and the ACA; include agreements on protection of proprietary data and restrictions on employees.

5.9.1.7. A copy of such agreement shall be provided to the Contracting Officer for review before execution of the document by the cooperating contractors.

5.9.1.8. Nothing in the foregoing shall affect compliance with the requirements of the clause at 5352.209-9000, Organizational Conflict of Interest (OCI).

5.9.1.9. The contractor is not relieved of any contract requirements or entitle to any adjustments to the contract terms because of a failure to resolve a disagreement with an associate contractor.

5.9.1.10. Liability for the improper disclosure of any proprietary data contained in or referenced by any agreement shall rest with the parties to the agreement, and not the Government.

5.9.1.11. All costs associated with the agreements are included in the negotiated cost of this contract. Agreements may be amended as required by the Government during the performance of this contract.

5.9.2. The following contractors are associate contractors with whom agreements are required:

5.10. Period of Performance. Effort is 60 months from date of award. Basic: From Date of Award for twelve months. Option 1 : 12 month period from end date of basic period. Option 2: 12 month period from end date of Option 1. Option 3: 12 month period from end date of Option 2. Option 4: 12 month period from end date of Option 3. (this includes the 90 calendar day phase-out).

5.11. Contract Data Requirements List (DD 1423s).

5.11.1. Data Items and Deliverables. With the exception of contractor management documents (e.g. Monthly Status Reports), and the identified CDRLs, all documents and reports generated by the F-35 joint and combined test team are to be U.S. Government reports due to the nature of ITAR requirements. Contractor format is acceptable except where AFOTEC OT&E guide or policy provides specific templates. The contractor's participation must comply with required program protection criteria, joint and combined requirements, and AFOTEC standards, unless given other direction (e.g., document not required to meet current standards due to grandfathering). The history of this program has shown that many of the program's documents will require multiple versions due to program protection criteria, and require extensive additions and updates after initial development. The contractor shall provide inputs to these revisions or updates, as required.

All documents shall be marked with the following statement:

Export Control Warning. WARNING- This document contains technical data whose export is restricted by the Arms Export Control Act (Title 22, U.S.C., Sec 2751, et. seq.) or the Export Administration Act of 1979, as amended, Title 50, U.S.C., App. 2401 et. seq. Violations of these export laws are subject to severe criminal penalties. Disseminate in accordance with provisions of DoD Directive 5230.25. All reports shall be delivered to:

AFOTEC Det 1 Attn: Contracting Officer’s Representative 187 N. Flightline Road Edwards AFB, CA 93524

The contractor shall provide or participate in:

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

5.11.3. Funds & Manpower Expenditure (A002) and Status Reports (A003) - Reference paragraph 3. l. Immediately highlight in writing to the COR areas of concern.

5.11.4. Scientific and Technical Report - Generic (A021) Reference paragraph 3.2.1. Contractor shall provide inputs to support test planning activities. Contract format is acceptable and shall be provided on a timeline specified by the government.

5.11.5. DoD M&S Verification and Validation Plan (A032) Reference paragraph 3.2.3.1. Contract shall provide inputs to the VV&A plans and reports no later than 21 calendar days prior to the report due date established the government.

5.11.6. DoD M&S Verification and Validation Plan (A032) and DoD M&S Verification and Validation Report (A033) Reference paragraph 3.2.3.2. Contractor shall provide inputs to the draft VY&A plans and reports no later than 7 calendar days prior to the draft report due date established the government. The contractor shall provide inputs to the final report NLT 7 calendar days prior to the final report due date established by the government.

5.11.7. Presentation Material (A020) and Scientific and Technical Report - Generic (A021) Reference paragraph 3.2.8. The contractor shall provide continuity books and briefings on SME areas on a timeline directed by the government. Drafts will be due NLT 2 weeks prior to the established due date. These will be updated semi-annually.

5.11.8. Software User’s Manual (B012) Reference paragraph 3.2.11. A draft of the user's guide will be delivered 120 days after the establishment of the final DART ground station configuration or at the discretion of the government. A final version is due 30 days after receipt of the government comments.

5.11.9. Computer Program End Item Documents (B001), Software Development Plan (B002), Software Design Description (B006), Data Base Design Description Reference paragraph 3.2.15. Contractor shall developing and designing software on a timeline specified by the government to meet F-35 program requirements.

5.11.10. Software User’s Manual (B012) Reference paragraph 3.2.16. Software user’s manual draft will be delivered no later than 30 days after software delivery. The final manual will be delivered 3 weeks after the draft.

5.11.11. Briefing Material-Generic (A011) Reference paragraph 3.2.17. Orientation program to include the Test Concept shall be updated semi-annually effective with task order contract award. Courseware will be presented to the government NLT 2 weeks prior to training. This will be presented in AFOTEC PowerPoint slide format.

5.11.12. Briefing Material - Test Concept Brief (A013) Reference paragraph 3.3.2. Participate in documenting, refining, and maintaining the JSF OT Test Concept IAW the JPO's SDD test events schedule. This document will support the planning of joint and combined OT that consider joint and combined dedicated IOT&Es of blocks of capabilities.

5.11.13. Briefing Material-OA/EOA Plan Brief (A014) and Scientific and Technical Reports OA/EOA Plan (A022) Reference paragraph 3.3.3. The contractor shall provide inputs to the OA Plan NLT 2 weeks prior to the due date established by the government. The contractor shall provide inputs to OA Plan Brief NLT 1 week prior to planned briefing date.

5.11.14. Briefing Material-OT&E/OUE Plan Brief (A015) and Scientific and Technical Reports- OT&E/OUE Plan (A023) Reference paragraph 3.3.4. The contractor shall provide inputs to the OT Plan NLT 2 weeks prior to the due date established by the government. The contractor shall provide inputs to OT Plan Brief NLT I week prior to planned briefing date.

5.11.15. Scientific and Technical Report-DMAP (A028) Reference paragraph 3.3.5. Contractor shall provide inputs to the DMAP NLT 2 weeks prior to the due date established by the government.

5.11.16. Scientific and Technical Report-Detailed Test Plan (A029) Reference paragraph 3.3.6. Detailed Test Procedures shall be developed based on a parallel effort with the DMAP document. DTPs shall be delivered based on the maturity of the DMAP and completed 30 days prior to spin-up.

5.11.17. Science and Technical Report - Generic (A021) Ref paragraph 3.3.8. In the contractors format; provide a logical flow of information for the development of proposals for the government to review to assist in the resolution of Det I OT issues to incorporate in the appropriate documents being reviewed. Documents for review and due dates are as required.

5.11.18. Scientific and Technical Report – Generic (A021) Reference paragraph 3.3.10. Contractor shall participate with and provide inputs to government personnel during times of program documentation creation or updates to existing documents.

5.11.19. Conference Minutes (A004) Reference paragraph 3.3.12. Enter all site survey data in trip report format on the JOTT data base.

5.11.20. Environmental Permit (A008), Environmental Health and Safety Plan (A009), Safety Assessment Report (A010), Occupational Health Hazard Assessment Report. Reference paragraph 3.3.13. Contractor shall provide inputs to environmental assessments for F-35 operating locations 30 days after receipt of the requirement.

5.11.21. Scientific and Technical Report - Generic (A021) Reference paragraph 3.3.17. Contractor shall participate in developing Program Introduction Documents. Timeline will be specified by the government based on current AFOTEC and program guidance.

5.11.22. Scientific and Technical Report (A021) Reference paragraph 3.3.18. When required, provide inputs for JRMET charter updates in a comment resolution matrix format 30 days after receipt of requirement.

5.11.23. Conference Minutes (A004) Reference paragraph 3.3.21. Document all meetings, conferences, etc. in trip report format.

5.11.24. Scientific and Technic I Report-Generic (A021), DoD M&S Accreditation Plan (A031), DoD M&S Verification and Validation Plan (A032) Reference paragraph 3.3.24. Contractor shall provide inputs to the M&S plan and associated accreditation and VV&A plans. Inputs are due on the date established by the government.

5.11.25. Scientific and Technical Report-Generic (A021) Reference paragraph 3.3.25. Contractor shall participate in updating and maintaining the signature sustainment evaluation methodology, as required.

5.11.26. Scientific and Technical Report-Generic (A021) Reference paragraph 3.3.26. Contractor shall provide inputs into lessons learned reports. Timeline will be specified by the government based on current AFOTEC and program guidance.

5.11.27. Scientific and Technical Reports-Deficiency Reports (A030) Reference…