Basic_ATS_PWS_(12_Jul_16).doc

AIR FORCE OPERATIONAL TEST AND EVALUATION CENTER (AFOTEC)

TEST SERVICES (ATS)

PERFORMANCE WORK STATEMENT (PWS)

12 July 2016

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 Procuring Contracting Officer (PCO) and related to the OT&E of proposed systems and programs. Services include a broad range of engineering, technical, and analytical services in support of OT&E activities which include: integrated test functions for U.S. Air Force (USAF) and Multi-Service air, ground, space, and cyberspace programs; test design; test planning, execution, and reporting; post-test data analysis; Cybersecurity, Risk Management Framework (RMF), and Cybersecurity/ Information Assurance assessments; digital test tool development and associated tool training; special studies and analysis; and research and development of test capability requirements, shortfalls, and solutions. All services requested under this PWS are non-personal in nature and will be requested by a task order generated by the applicable functional area and PCO.

The scope of this acquisition is to provide engineering, technical and analytical services to support accomplishment of AFOTEC’s OT&E activities involving the core competencies in table 1.1:

Table 1.1. Core Competencies

CORE COMPETENCIES

1. Aeronautical/aerospace, civil, electrical, metallurgical, mechanical, chemical, cyber, computer/communications, software, and systems engineering expertise

2. Agile Combat Support expertise (aircrew flight equipment, force protection, logistics, support equipment, ground equipment, motor vehicles, aerospace ground equipment)

3. Air Force Cybersecurity Assessment Program (CAP) (Cybersecurity, Information Technology, Multi-disciplinary Security, Joint Exercises, Joint Planning, exercise training objective development, Joint Lessons Learned)

4. Aircraft and aircraft systems expertise (avionics, radar, simulators, air-refueling, bombers, mobility, special operations aircraft, helicopters, and remotely piloted aircraft (RPA))

5. Chemical, Biological, Radiological, and Nuclear (CBRN) expertise (decontamination, defense, detection, diagnostics, identification, modeling, personal protection, recovery, survivability, transportation, warning)

6. Command, Control, Communications, Computers, Intelligence, Surveillance and Reconnaissance (C4ISR) expertise (Air Operations Center (AOC), radar, RPAs, analysis (Signals, Geo-spatial))

7. Cyberspace systems expertise (business systems, cyber-protection, cyber-defense, cyber-attack, finance systems, information systems, medical records systems, mission planning systems, personnel systems)

8. Defense acquisition process and test and evaluation process expertise (early involvement, operational capability requirements development, planning, execution, reporting)

9. Directed energy, high power microwave, hypersonics, and advanced technologies expertise

10. Electromagnetics (electromagnetic compatibility, electromagnetic interference)

11. Electronic warfare, radar, infra-red, electro-optical, radio frequency, and sensor fusion expertise (active, passive, counter measures, counter-counter measures, intercept systems, missile warning systems, autonomous decoys, towed decoys, sensors, simulations, modeling, threat analysis)

12. Global Positioning System expertise (operations, threats)

13. Human factors engineering expertise (engineering psychology, behavioral science)

14. Intercontinental Ballistic Missile (ICBM) Operations and Maintenance expertise (weapons systems command and control, booster guidance, reentry systems, munitions infrastructure, integrated logistics support, Ground Based Strategic Defense (GBSD))

15. Cybersecurity, Risk Management Framework, Information Assurance, and intelligence test and evaluation expertise (protection, defense, detection, recovery)

16. Logistics planning and analysis expertise (availability, compatibility, transportability, interoperability, reliability, maintainability, supportability, life cycle management, and deficiency reporting)

17. Modeling and Simulation (M&S) applications expertise (distributed test capabilities; verification, validation, and accreditation (VV&A))

18. Munitions and munitions systems expertise (air-to-air, air-to-ground, conventional, fuzes, build-up and load, guidance systems, nuclear, release/launch systems, stand-off weapons, sub-munitions)

19. Nuclear survivability expertise (High-Altitude Electromagnetic Pulse)

20. Operations analysis expertise (math, statistics, Design of Experiments, reliability growth, data analysis)

21. Space and terrestrial weather expertise

22. Space systems test and evaluation expertise (radar, communications, command and control, Global Positioning System, missile defense, overhead persistent infrared)

23. Technology test support expertise (computers, networking, instrumentation, web support)

24. Test and evaluation resources expertise (manpower, ranges, simulators, labs, specialized test facilities, instrumentation, production)

25. Threat system analysis and intelligence test and evaluation expertise

The contractor shall provide services under PCO issued task orders for various test and evaluation efforts and phases, consisting of various sizes and complexities, of Department of Defense (DoD) related systems, where a system is understood to be an assembly or combination of interrelated elements (hardware, software, material, 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. This effort applies to Headquarters AFOTEC, Kirtland AFB, NM and the following Detachments (Det) and Operating Locations (OLs): Buckley AFB, CO (OL-BC); Edwards AFB, CA (Det 5); Eglin AFB, FL (Det 2); Everett, WA (OL-EW); Hill AFB, UT (OL-HU); Hurlburt Field, FL (OL-HF); Joint Base San Antonio, TX (OL-KT); Nellis AFB, NV (OL-NN); Peterson AFB, CO (Det 4), and Schriever AFB, CO. The potential exists for places of performance to include other locations such as the Pentagon, MAJCOMs, contractor facilities, government test ranges, and various meeting and conference venues.

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

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 effective, suitable, and operationally mission capable. AFOTEC is responsible for planning, executing, and reporting independent OT&E. AFOTEC supports USAF, 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: Operational Assessment (OA); Operational Utility Evaluation (OUE); Initial Operational Test and Evaluation (IOT&E); Multi-Service OT&E (MOT&E); Qualification OT&E (QOT&E); Follow-On Test and Evaluation (FOT&E); Joint/Urgent Operational Need (J/UON); and other operational test activities as defined in AFI 99-103 or as directed by higher authority.

· Achieving positive effect on air, space and cyberspace capabilities through early influence of capability requirements development, early acquisition strategy/planning efforts, integrated development/operational 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 testing activities evaluate the operational effectiveness, operational suitability, and mission capability of air, ground, space and cyberspace systems, such as: Agile Combat Support systems; aircraft and aircraft systems; CBRN systems; C4ISR systems; cyberspace systems; GPS; munitions and munitions systems; support and ground equipment; and augmentations of these systems by new technologies in the future.

AFOTEC testing activities involve skills and knowledge in the following areas: military aircraft and aircraft systems (excluding fighter aircraft), aeronautical; aerospace; civil, electrical, metallurgical, mechanical, chemical, computer/communications, and systems engineering; CBRN; C4ISR; cyberspace systems; defense acquisition processes; test and evaluation processes; directed energy; high power microwave; advanced technologies; electronic warfare; radar; infra-red, electro-optical, and radio frequency engineering; human factors engineering; Cybersecurity, RMF, Information Assurance evaluation; intelligence test and evaluation; logistics planning and analysis; modeling and simulation applications; munitions and munitions systems; nuclear survivability; operations analysis; space and terrestrial weather; technology test support; and test and evaluation resources.

For the purpose of this PWS the following definitions apply:

· Assessment (Cybersecurity): These assessments focus on the attributes of a system or network to ensure the availability, integrity, authenticity, confidentiality, and non-repudiation of the data handled by that system, system of systems, or network.

Test and Evaluation (T&E): The term “test” denotes any project or program designed to obtain, verify, and provide data to evaluate, research and develop; progress in accomplishing development objectives; performance and operational capability of systems, subsystems, and components; and equipment items.

· Evaluation: The term “evaluation” denotes the review and analysis of data produced during current or previous testing and data obtained from test conducted by other government agencies and contractors, from operation and commercial experience, or combinations thereof.

Operational Effectiveness is the measure of overall ability to accomplish a mission when used by representative personnel in the environment planned or expected for operational employment of the system considering organization, doctrine, supportability, survivability, vulnerability, and threat.

· Operational Suitability is the degree to which a system can be placed satisfactorily in field use with consideration given to availability, compatibility, transportability, interoperability, reliability, wartime usage rates, maintainability, safety, human factors, manpower supportability, logistics supportability, natural environmental effects and impacts, documentation, and training requirements.

· Mission Capability is the determination of the system’s overall capability to execute or support a tasked mission with consideration given to: operational costs on the form of manpower, time, ease of use, supplies, work-arounds and risk; limitations associated with aspects or portions of the mission; and mission accomplishment across a variety of operational conditions.

2.0. APPLICABLE DOCUMENTS

Applicable guidance consists of DoD, AF and AFOTEC documents associated with requirements definition, acquisition, and test and evaluation. The contractor shall use the most current version, as supplemented, during the contract period of performance. Key documents applicable to this PWS are listed in table 2.1 below. The government will post the documents cited as references on Fed Biz Ops during the source selection phase. Each task order may identify unique guidance not contained herein. All records generated under this PWS are government property.

Table 2.1. Applicable Documents

AFOTECMAN 99-

AFOTEC OT&E

Guide 9th Edition

Guide Entire document

2.1 Records Management

Air Force Manual (AFMAN) 33-363 Management of Records, 21 Jul 16; Chapters 2, 3 and 4 in their entirety, Paragraph 6.4.

Air Force Instruction (AFI) 33-364 Records Disposition – Procedures and Responsibilities, 9 Apr 15; Paragraphs 1.1.1, 1.1.2, 1.2.2, 2.1.1, 2.10 through 2.10.1.3; Chapter 3 in its entirety, 4.1 through 4.1.7, 4.4 through 4.4.1, 5.1, 5.1.1, 5.1.2, 5.5, 5.5.2, 5.5.3, 5.6, 5.6.1, 8.1 and 8.1.1.

3.0 PERFORMANCE REQUIREMENTS

The contractor shall perform the requirements within the service task areas listed in this section. Task orders will identify specific tasks for completion within a specified period of time. The contractor shall initiate no work under a task order without approval by the contracting officer. These efforts apply to new and current and on-going systems and emerging weapons technologies.

3.1 Management Requirements

The contractor shall:

3.1.1 Have the training, understanding and ability to adhere to AFOTEC safety requirements, processes and procedures while in/out of military installations and while supporting test activities in the field. Test activity safety can be found in AFOTEC Test Plans and Health and Safety Plans. Below are the AFOTEC safety references and guides.

AFI 91-202 AFOTECSUP 1

AFOTECMAN 99-101

AFOTECPAM 99-104

AFOTEC OT&E Guide

3.1.2 Prepare task order proposals in support of task order performance requirements and in accordance with the task order procedures set forth in Section J of the contract. Task and program 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.3 Be responsible for contractor overall responsiveness, cost control and reporting, adherence to schedule, ability to adapt to schedule changes, responsible and cooperative behavior, subcontractor control/ management/ oversight, 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.4 Maintain a Quality Control Plan that ensures the government receives the level of quality consistent with the requirements specified in each task order.

3.1.5 Be responsible for risk identification and mitigation associated with supporting each task order.

3.2 Test/Assessment 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 Integrated Testing, operational assessments, and dedicated 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. Test capabilities may be live, virtual, or constructive and include threat representation.

The contractor shall:

3.2.1 Perform analysis of current and future test/assessment capabilities. Activities include: identifying test/assessment capability requirements, documenting existing test/assessment 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. This includes constructive tools that represent real world entities by means of computer models, hardware-in-the-loop simulators (HITL), human-in-the-loop simulators, installed system test facilities, and distributed interactive simulations.

3.2.3 Develop accreditation packages. Activities include: Developing verification, validation, and accreditation (VV&A) plans, reports, and briefings.

3.2.4 Maintain configuration management of developed and modified tools.

3.2.5 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.6 Assist in the development and coordination of cyber assessment plans and reports. This includes cooperative-vulnerability, and penetration/exploitation assessments (Blue Team) and adversarial assessment (Red Team), IAW appropriate Director, Operational Test and Evaluation (DOT&E) and AFOTEC guidance.

3.2.7 Provide Information Technology (IT) support during test support and execution.

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

3.2.9 Identify, develop, recommend, and/or integrate test capabilities for ranges (live and virtual), state-of-the-art instrumentation, and ways to use test capabilities to answer operational questions. This includes a range of technical fields such as aerodynamics, electronic warfare, M&S, software development and maintenance, and the space environment.

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

3.2.11 Identify, schedule, and track program activities and deliverables for all tasked programs. Maintain a master schedule for all tasked programs using common project management software. Provide inputs to leadership to manage multiple programs.

3.2.12 Provide support of test investment forums as requested. Forums include, but are not limited to, the Central Test and Evaluation Program (CTEIP), the Resource Enhancement Project (REP), and the Threat Systems Working Group (TSWG).

3.3 Test/Assessment Planning and Early Influence

Test planning focuses on developing test designs/concepts, supporting program/technical reviews, developing test plans, developing data management and analysis plans, establishing deficiency reporting, supporting test readiness reviews, and developing briefings.

The contractor shall:

3.3.1 Accomplish operational task decomposition showing the interlacing and overlapping relationships between the system under test and the family of systems it interacts with.

3.3.2 Review lessons learned and test methods used in the testing and evaluation of similar systems.

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

3.3.4 Participate and provide input to Initial Test Designs and subsequent stages of test planning.

3.3.5 Provide input in developing and revising Critical Operational Issues, Measures of Effectiveness, and Measures of Suitability.

3.3.6 Recommend appropriate test facilities/ranges and identify improvements necessary to create a realistic environment.

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/assessment design.

3.3.8 Provide logistic planning in support of AFOTEC.

3.3.9 Review program documents for test and evaluation/assessment concerns and provide feedback. Documents include: Program Management Directive, applicable capabilities documents, virtual/system threat assessment report, Test and Evaluation Master Plan, Systems Acquisition Management Plan (SAMP), Lifecycle Management Plan (LCMP), program protection documents, concepts of operations/employment (CONOPS/CONEMP), and maintenance concepts.

3.3.10 Participate as an Integrated Test Team member to gain knowledge of developmental, integrated, and operational test activities.

3.3.11 Identify and/or develop integrated test opportunities as appropriate to support OT&E.

3.3.12 Prepare, submit and/or revise AFOTEC portions of test documentation, such as test team charters, TEMPs, integrated test plans, and schedules.

3.3.13 Develop, prepare, submit, review and/or revise AFOTEC test planning documentation. Examples include: Program Introduction Document (PID), Statement of Capabilities (SOC), OT&E/assessment plans, cyber vulnerability and penetration test plans, cybersecurity adversarial assessment, joint OT&E/assessment plans, Data Management and Analysis Plans (DMAP), detailed test/assessment procedures, test/assessment planning briefings, and schedules.

3.3.14 Develop evaluation methodologies and general analytic techniques, assess data requirements, and recommend/utilize the necessary tools needed to support the evaluation, such as digital modeling and Hardware-in-the-Loop (HITL) simulations.

3.3.15 Analyze and submit test/assessment methodologies; test/assessment scenario descriptions; test/assessment measures; test/assessment risk, limitation and mitigation strategies; and test/assessment readiness and support requirements needed to complete the OT&E plan.

3.3.16 Develop DMAPs, test procedures, evaluation methodologies, analysis methods, and schedules. Provide multimedia data file management and archiving. Assure configuration control of any software codes used by or in support of the evaluation activity.

3.3.17 Develop, modify, operate and/or maintain the required automated data collection/reduction systems, to include developing interfaces with existing digital information stored on available databases. Develop, refine, and implement plans to insure interoperability with data from appropriate test facilities/ranges. Analyze content for interoperability and compatibility with existing information (data) systems.

3.3.18 Define instrumentation requirements, propose instrumentation solutions, and develop instrumentation to collect and store data.

3.3.19 Provide input for the development of operational test/assessment scenarios/demonstrations.

3.3.20 Support the identification of candidate operational exercise participation opportunities. Assist in site surveys on potential test/assessment sites and support the development of site preparation requirements, such as defining site-specific installationand integration of equipment.

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

3.3.22 Support program, technical, and Test Readiness Reviews (TRR).

3.4. Test/Assessment Execution

Test/assessment execution consists of all activities associated with executing the OT&E/ Assessment plan with identified resources.

The contractor shall:

3.4.1 Provide field operations services, such as deployment and redeployment; requesting, scheduling, and tracking of test/assessment equipment resources; identifying and preparing test/assessment equipment; computer systems design and engineering for test/assessment; network administration and system administration for test/assessment support networks and data management; and calibrating test/assessment instrumentation and site support equipment with onsite equipment and power.

3.4.2 Provide information to support airspace/range management services, such as providing airspace management for manned aircraft and/or unmanned air vehicles and ground vehicles (UAV and UGV) tests, assessments, and field evaluation activities both within the continental United States (CONUS) and outside the continental United States (OCONUS).

3.4.3 Participate in the execution of test/assessment plans, DMAPs, and detailed test/assessment procedures. Accomplish electronic and/or physical data collection, management and transfer.

3.4.4 Provide field communications and frequency management support such as the installation, testing, and operation of communication equipment and data links.

3.4.5 Support the development of OT&E mission briefs and deliver mission briefings and debriefings.

3.4.6 Prepare, review, and update OT&E test documentation. Examples include: Test deviation memo’s, updating DMAP/DTPs, trip reports, quick look reports, resource requirements.

3.4.7 Provide evaluation services for special interest items as defined in AFOTECMAN 99-101.

3.5 Test/Assessment Evaluation

Test/assessment evaluation determines the extent to which the system under test meets the warfighters’ mission needs, in addition to system requirements as outlined in the program requirement documents.

The contractor shall:

3.5.1 Collect, compile, review, analyze, and evaluate test/assessment data.

3.5.2 Run computer models and simulations and analyze/characterize the resulting output. Provide contractor developed raw data used in analysis to the Test Director.

3.5.3 Identify the impact of lost data (due to corruption, instrumentation failure, etc.) on analysis and evaluation of test results. Identify alternative data sources as appropriate.

3.5.4 Conduct studies, analyses and evaluations of test results. For example, the impact on operational effectiveness, suitability, and survivability of systems undergoing OT&E/Assessment.

3.5.5 Determine the capability of a system to operate within its intended environment and withstand man-made environments and quantify the degree of impairment of its ability to accomplish its designated mission. The environments include: natural, nuclear, conventional, cyber-contested, electronic, radio-frequency, directed energy, chemical, biological and unconventional operations warfare.

3.6 Test/Assessment Reporting

Test/assessment reporting consists of communicating the analysis and evaluation of test/assessment results. Test/assessment reporting may be required in any multimedia format.

The contractor shall:

3.6.1 Provide input to develop and/or revise the final test/assessment report.

3.6.2 Prepare test/assessment documentation for inclusion in test/assessment reports.

3.6.3 Prepare briefings as a part of the report coordination process.

3.6.4 Prepare Quick Look, Interim Summary Reports, and Lessons Learned reports/briefings.

4.0. Surveillance Matrix

Contracting Officer Representatives (COR) will use Table 4.1 as a guide when identifying a surveillance matrix in task orders.

Table 4.1 Surveillance Matrix

Ref

Item 4: Comply with applicable portions of the DD Form 254 for task order requirements.

government’s satisfaction.

Customer complaint as validated by COR and PCO and cognizant security authority.

Item 5: Overall Quality of Performance:

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

5.0. GENERAL INFORMATION

5.1 Government Furnished Property – Base Support

When the task order requires the contactor to work in a government facility, the task order will define the type of base support and/or government furnished property. 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.

a.) Facilities: The government may provide office space, cubicle, or work area (hereinafter referred to as “office”) for each requirement identified in a task order.

b.) Equipment:

1.) ADPE Equipment and Software: The government may provide a computer for each position identified in the task order. Each computer will have the necessary software required to perform the duties ascribed to the requirement (such as Microsoft Office).

2.) Communication Equipment: Each office provided by the government may have a telephone. Each computer that must be linked to local servers and/or to the internet or external networks will be so linked at appropriate levels (NIPR; SIPR, etc.)

c.) Furniture: Each office provided by the government will have a desk and chair. Additional furniture (such as bookcases, credenzas, etc.) will be provided upon determination of need by the government.

d.) Custodial Service: The contractor will receive the same level of support from the host wing as would government employees. This may include keeping their work area neat and clean and emptying personal trash bin in a government designated trash and recycling receptacles.

e.) Telephones: AFOTEC will request base telephone service for the contractor to include common user instruments. Telephone service provided will include access to local off-base service and DSN as needed. All services will be provided “for official use only” in performance of the contract. Commercial service as needed by the contractor for company business will not be provided.

5.1.1 Property Control Procedures. Property control procedures will be established by the contractor for all government furnished property, facilities and equipment in accordance with government instructions. Computers and peripheral equipment will not be signed over to the contractor as Government Furnished Equipment. Hand receipts will be used to track the assignment of such equipment, and location and condition will be verified through periodic audits. The contractor’s signature on a hand receipt shall indicate the contractor’s acceptance of responsibility for the proper use and care of such equipment. This could include financial responsibility for lost or stolen equipment if contractor negligence is established.

5.2 Travel Requirements

Contractor employees may be required to travel to various locations, both CONUS and 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. 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 and tax.

5.3 Transition

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

5.3.1 Phase-In. As a successor, the ATS contractor shall insure a smooth transition with the incumbent Operational Test and Evaluation Services (OTES) contractor(s) during the phase-in period. Phase-in is not required if the successor contractor subcontracts to or is an OTES incumbent. The contractor shall develop plans for assumption of awarded task orders. The contractor must provide an orderly transition of work acceptance and accomplishment such that any impact to a program is minimized. The phase-in time shall be no more than 30 days.

5.3.2 Phase-Out. The ATS incumbent shall ensure a smooth transition with the successor during the ATS contract phase-out period, prior to completion of contractual performance. The incumbent contractor shall aid the successor in the development of plans, procedures and methods for the assumption of all on-going work. The contractor must provide an orderly transition of work acceptance and accomplishment, such that full control by the successor is achieved by the end of the new contract phase-in period. The phase-out time shall be no more than 30 days.

5.4 Deliverables.

Deliverables will be specified in each task order.

5.5 Associate Contractor Agreements (ACA). The contractor may enter into an 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.6 Schedule/Period of Performance. ATS Ordering Period is DOA plus 60 months.

5.7 Contract Data Requirements List (DD 1423s). 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 1423. Deliverable reports specific to each task order will be specified in each individual task order. DD 1423’s are available in Exhibit A of the contract.

6.0 SECURITY REQUIREMENTS

6.1 Security

6.1.1 The contractor shall comply with all AFOTEC security requirements and all requirements outlined in the DD Form 254 (DoD Contractor Security Classification Specification).

6.1.2 The contractor will require access to classified and Special Access Program (SAP) source data up to and including Top Secret Sensitive Compartmented Information (SCI). The contractor must have and maintain a current Top Secret security clearance current within 5 years and be SAP and SCI eligible. The contractor must have a current Top Secret security clearance and be SAP and/or SCI eligible the first day of the task order. The Joint Personnel Adjudication System (JPAS) must reflect these requirements have been met by the first day of the task order.

6.1.3 The contractor shall provide the government with the required information for obtaining special program accesses; to include questionnaire information, letters of compelling need, and any other information to support special program access packages. The contractor must ensure they are accurate and complete IAW applicable guidance.

6.1.4 The contractor will submit visit requests via the 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 (NISPOM). Direct requests must be approved by AFOTEC with coordination by the COR/Test Director prior to travel.

6.1.5 The contractor will report, to an appropriate authority, any information or circumstances of which they are aware may pose a threat to the security of DoD personnel, contractor personnel, resources and classified or unclassified defense information. Contractor employees shall be briefed by their immediate supervisor upon initial on-base assignment.

6.1.6 Any failure to adhere to security regulations could result in a security infraction or incident and will be processed according to DoDM 5200.01, Volume 3, DoD 5105.21-M-1, SAF/AQ Security Pamphlet 5, AFI 16-1404, AFMAN 14-304, and any subsequent changes and/or revisions.

6.2 Cybersecurity

The contractor shall:

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

6.2.2 Report to an appropriate authority any information or circumstances, of which they are aware, that may pose a threat to the security of DoD personnel, contractor personnel, resources, and/or classified or unclassified defense information. Contractor employees shall be briefed by their immediate supervisor upon their initial on-base assignment.

6.2.3 The contractor is prohibited from attaching any computer hardware to the Air Force network, or running any computer software unless it has been certified and accredited according to current USAF Instructions. Any such requests for reconfiguration, upgrade, or addition of computer hardware or software must be approved by the 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.2.4 Contractor personnel using computer assets shall comply with all computer security requirements. In addition, should contractor personnel require access to computer networks or databases, they shall inform the COR or Alternate COR, who will arrange for the contractor personnel to complete the required documentation for a new computer account. The contractor shall notify the COR or Alternate COR within one workday of any contractor personnel who no longer require an open account and shall take action to close the computer account with the appropriate office within that same workday.

6.2.5 All contractor personnel who will be using IT systems belonging to the Federal Government to generate, process, store, transfer, or communicate information shall complete 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.2.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.2.7 No foreign nationals are authorized to work on this effort without prior written notification to the COR and PCO, and until approval is obtained from the PCO in accordance with current government policy and regulations.

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

7.0 ATTACHMENTS/MISCELLANEOUS INFORMATION. Attachments/miscellaneous info will be specified in each task order as needed.

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

7.2 Administrative Dismissal for Safety Reasons. The contractor will provide alternate work sites for personnel during local emergency situations when the Base Commander has declared an emergency and has stated personnel should not report to Base or should leave the Base during a workday. Local emergency conditions include inclement weather (e.g. snow, tornados, earthquakes, hurricanes, etc.).

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

7.4 Conflict of Interest. In accepting and performing the work required by this task order, and all amendments thereto, the contractor certifies the requirements of clause AFFARS 5352.209-9000, Organizational Conflict of Interest (OCI) have been or will be adhered to. The contractor must immediately bring any OCI issues to the attention of the PCO for a determination of whether a mitigation plan is required.

7.5 AFOTEC Safety Requirements. It is the contractor’s responsibility to ensure its employees and managers have a comprehensive understanding of and full compliance with OSHA requirements. It is the contractor’s sole responsibility for compliance with OSHA, Public Law 91-596. Detailed information is available on the OSHA website at http://www.osha.gov.

8.0 CONTRACTOR FULL-TIME EQUIVALENT REPORTING.

Contractor Full-Time Equivalent Reporting: The contractor shall report all contractor labor hours (including subcontractor labor hours) required for performance of services provided under this contract for AFOTEC via a secure data collection site. Data may be collected by task order. The contractor is required to completely fill in all required data fields at http://www.ecmra.mil.

Reporting inputs will be for the labor executed during the period of performance for each Government fiscal year (FY), which runs 1 October through 30 September. While inputs may be reported any time during the FY, all data shall be reported no later than 31 October of each calendar year. Contractors may direct questions to the Contracting Manpower Reporting Application (CMRA) help desk.

Uses and Safeguarding of Information: Information from the secure website is considered to be proprietary in nature when the contract number and the contractor identity are associated with the direct labor hours and direct labor dollars. At no time will any data be released to the public with the contractor name and contract number associated with the data.

User Manuals: Data for Air Force service requirements must be input at the Air Force CMRA link. However, user manuals for government personnel and contractors are available at the Army CMRA link at http://www.ecmra.mil.

9.0 Task Order Proposal Procedures

a.

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

· The work to be performed;

· The desired performance period; and

· 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 following:

· The management and technical proposal shall identify the Contractor’s proposed approach to the specific task.

· The contractor shall identify any organizational conflicts of interest issue and submit a mitigation plan.

· The Contractor’s proposal shall address the number(s) of personnel performing on each task; the number of hours worked by each individual and an explanation of why each is necessary to perform the Task Order; the rationale for the personnel, skill levels and number of hours proposed; and an overall discussion of the Contractor’s proposed technical solution. Any Government property, material or data required for performance must be identified in the response to the RFTOP. In addition, all program management functions, e.g. PM, QA/QC, MFT participation, etc., except for those costs identified in paragraph c above, shall be imbedded as part of the task order proposal.

· The technical proposal must include relevant past performance and relevant information about performing the same or similar work. Recent performance on Task Orders performed under this contract will be evaluated.

· Cost/Price proposals shall utilize the most current Defense Contract Audit Agency (DCAA) approved Forward Pricing Rate Agreements (FPRAs) or approved billing rates for both labor and all indirect rates.