Atch_8_-_ATS_Basic_PWS.pdf

PDF 274 KB Posted

Attached to
AFOTEC Test Services (ATS) Federal contract opportunity
Solicitation number
FA7046-16-R-0003
Issued by
Department of the Air Force Materiel Command Test Center

About this file

ATS Basic PWS

View the file

Other files for this federal contract opportunity

Other files attached to AFOTEC Test Services (ATS), newest first.
File Type Posted
Follow_up_ATS_Amend_3&4_Q&As.pdf PDF
Final_ATS_Labor_Category_Rate_Matrix.xlsx XLSX spreadsheet
FA7046-16-R-0003_Amd_4_Final_Copy.pdf PDF
Final_ATS_Basic_PWS_28_June_2017.pdf PDF
Final_ATS_Labor_Category_Rate_Matrix.xlsx XLSX spreadsheet
Atch_11_-_ATS_TO_Evaluation_Factors.pdf PDF
Atch_2_-_ATS_CAP.pdf PDF
Atch_3_-_ATS_C2ISR.pdf PDF
Atch_10_-_ATS_TO_1_-_Post_Award_PWS.pdf PDF
Atch_4_-_ATS_NukDEW.pdf PDF
FA7046-16-R-0003_Amd_2_Conformed_Copy.pdf PDF
Final_RFP_Q&As.pdf PDF
ATS_RFP_-_16-R-0003_Amd_1.pdf PDF
ppi_tool.accdb —
Atch_5_-_ATS_RFP_DD_Form_254.pdf PDF
RFP_ATS_FA7046-16-R-0003.pdf PDF
Atch_1_-_Section_L__Atch_1-5.pdf PDF
Atch_4_-_ATS_TO_0001_NukDEW_12_Nov_2016.pdf PDF
Atch_9_-_ATS_RFP_Acronym_Listing.pdf PDF
Atch_7_-_ATS_CDRLs_(Exhibit_A).pdf PDF
Atch_6_-_ATS_CDRLs_(Exhibit_B).pdf PDF
Responses_to_ATS_Draft_RFP_17_Nov_2016.pdf PDF
https //www.fbo.gov/fedteds/ATSFA945116R0003 —
D5_C2ISR_TO_(12_Jul_16).doc DOC document
Basic_ATS_PWS_(12_Jul_16).doc DOC document
ATS_Draft_RFP_Acronyms_list.doc DOC document
ATS_CDRLs_(Exhibit_B).doc DOC document
SECTION_L_ATTACHMENTS_L1_-_L5.pdf PDF
NukDEW_TO_1_(12_Jul_16).doc DOC document
ATS_CDRLs_(Exhibit_A).doc DOC document
ATS_Draft_RFP_29_Aug_16.docx DOCX document
OL-KT_TO_(12_July_16).docx DOCX document
ATS_Industry_Day_WebEx_Attendees.xlsx XLSX spreadsheet
ATS_Industry_Day_Attendees.xlsx XLSX spreadsheet
ATS_Brief_for_Industry_Final-_Post.pdf PDF
ATS_Agenda_9_Jun_15.pdf PDF
ATS_Agenda_9_Jun_15.pdf PDF
ATS_Q A_2_June_16.docx DOCX document
DRAFT_ATS_PWS.docx DOCX document
ABQ_Map_of_PTi__Sunport__Collaboration_Center.pdf PDF
ATS_Questions_and_Answers_14_Apr_2016.docx DOCX document
D5_C2ISR_TO_(12_Jul_16).doc DOC document
ATS_CDRLs_(Exhibit_A).doc DOC document
DRAFT_DD_Form_254_for_ATS_Request_for_Proposal.pdf PDF
ATS_SSS-RFI_-_1_Apr_16_Final.docx DOCX document
NukDEW_TO_1_(12_Jul_16).doc DOC document
SECTION_L_ATTACHMENTS_L1_-_L5.pdf PDF
Basic_ATS_PWS_(12_Jul_16).doc DOC document
OL-KT_TO_(12_July_16).docx DOCX document
ATS_CDRLs_(Exhibit_B).doc DOC document
Show all 50

AFOTEC Test Services (ATS) has more files on GovTribe.

On GovTribe

Work with this file on GovTribe

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

AIR FORCE OPERATIONAL TEST AND EVALUATION CENTER (AFOTEC)

TEST SERVICES (ATS)

PERFORMANCE WORK STATEMENT (PWS)

12 November 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)

CORE COMPETENCIES

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

Reference Date Title Specific Paragraphs/ Chapters/Sections

AFI 10-601 16 Nov 13 Operational Capability Requirements Development Entire Document

AFI 16-1001 22 Jun 16 Verification, Validation and Accreditation (VV&A) Entire Document

AFI 16-1003 19 Apr 11 Air Force Standard Analysis Toolkit Sections B and C

AFMAN 33-152 1 Jun 12 User Responsibilities and Guidance for Information Systems Entire Document

AFI 33-200 31 Aug 15 Air Force Cybersecurity Program Management Entire Document

AFI 33-210 2 Oct 14 Air Force Certification and Accreditation (C&A) Program Entire Document

AFM 33-285 26 May 16 Cybersecurity Workforce Improvement Program Entire Document

AFMAN 33-302 26 May 16 FOIA Program Entire Document

AFI 33-332 12 Jan 15 Air Force Privacy and Civil Liberties Program Entire Document

AFMAN 33-363 21 Jul 16 Management of Records Entire Document

AFI 33-364 9 Apr 15 Records Disposition – Procedures and Responsibilities Entire Document

AFI 63-101/20-101 23 Feb 15 Integrated Life Cycle Management Entire Document

AFMAN 63-119

19 Feb 16

Certification of System Readiness for Dedicated Operational Testing

Entire Document

AFI 91-202 24 Jun 15 The US Air Force Mishap Prevention Program Entire Document

AFI 91-202

AFOTEC

Supplement

30 Jun 16 The US Air Force Mishap Prevention Program, AFOTEC Supplement Entire Document

AFPD 99-1 3 Jun 14 Test and Evaluation Entire Document

AFI 99-103 16 Oct 13 Capabilities-based Test and Evaluation Entire Document

Air Force Test and Evaluation Guidebook Ver 2.1

April 2007 Air Force Test and Evaluation Guidebook Ver 2.1 Entire Document

AFOTECI 99-101 20 Jun 14 Operational Test and Evaluation Management Entire Document

AFOTECMAN 99-

101 11 Oct 12 Operational Test Processes and

Procedures Entire Document

AFOTECPAM 99-

104 24 Sep 13 AFOTEC Operational Suitability Test and Evaluation Guide Entire Document

AFOTEC

Cybersecurity OT Guide

30 Sep 14 AFOTEC Cybersecurity OT Guide, 1st Edition Entire Document

AFOTEC OT&E

Guide 9th Edition

21 Nov 13 AFOTEC OT&E Guide Entire Document

AFOTEC Test Design Guide 7 Jul 15 AFOTEC Test Design Guide Entire Document

CJCSI 3170.01I 23 Jan 15 Joint Capabilities Integration and Development System Entire Document

CJCSI 6510.01F 9 Jun 15 Information Assurance and Support to Computer Network Defense (CND) Entire Document

Defense Acquisition Guidebook (DAG) 28 Jun 13 Defense Acquisition Guidebook (DAG) Entire Document

DOT&E

Cybersecurity Guidebook v1

1 Jul 15 DOT&E Cybersecurity Guidebook v1 Entire Document

DoDD 5000.01 20 Nov 07 The Defense Acquisition System Paragraphs 3 and 4;

Enclosure 1

DoDI 5000.02 7 Jan 15 Operation of the Defense Acquisition System Entire Document

DoDI 5000.61 9 Dec 09 DoD Mod Sim Ver Val Accreditation Entire Document

DoDD 5134.08 14 Feb 13 Asst SecDef for Nuclear, Chemical, and Biological Defense Programs Entire Document

DoD 5400.07 2 Jan 15 DoD Freedom of Information Act (FOIA) Program Chapter 4

DoDI 8500.01 14 Mar 14 Cybersecurity Entire Document

DoD 8570.01-M 11 Oct 15 Information Assurance Workforce Improvement Program, Change 4 Entire Document

Generic Acquisition Process 17 Dec 14 Generic Acquisition Process 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 Submit a Quality Control Plan for each awarded Task Order that ensures the government receives the level of quality consistent with the requirements specified in the task order, and maintain the Quality Control Plan throughout the duration of the 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

Performance Objective PWS Ref Performance Threshold Method of

Assessment

Item 1: Provide responsive task order/team management including quick response to contingencies, to include timely and accurate task order document and report requirements, customer interaction and feedback, contributions to meetings and reviews, and task order modifications and change orders.

All Clear, consistent, and timely written and verbal communication (i.e. returns phone calls, emails or other communication attempts within 1 business day) with no more than 1 customer complaint per month. Any late replies or customer complaints must be resolved within 5 working days.

Customer complaint as validated by COR and PCO.

Assessment

Item 2: The contractor must effectively monitor funding on each individual task order and of all Other Direct Costs (ODCs).

3.1 Actual task order expenditures

shall be within the percentage the COR determines of the approved projected budget. Meets task order schedule requirements.

Monthly Status and/or Funds and Man-hours Expenditure Reports.

Item 3: The contractor must be responsive to Government requirements, ensure PWS compliant performance, provide prompt identification and resolution of problems, effectively communicate concerns with the COR and meet the delivery schedule required in the Contract Data Requirements List (CDRL).

All Within each task order, no more than one late document per month or no more than three total customer complaints, to include timely CDRL delivery, per assessment period. Any late document delivery, or customer complaints must be resolved within 5 working days.

Customer complaint as validated by COR and PCO.

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

All Compliance is mandatory; failure to meet security requirements are unacceptable. Each security incident, inadvertent disclosure and violation must be reported to the government within 1 working day and violations resolved within 30 working days to the governments 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.

All Contractor receives no more than three formal discrepancy reports per year from all task orders. Each formal discrepancy must be resolved to the government’s satisfaction within 30 days.

Customer complaint as validated by COR and PCO.

Assessment

Item 6: AFOTEC Safety requirements compliance:

Contractors shall ensure their employees and subcontractors comply with all applicable OSHA standards, identify and mitigate hazards, and report pertinent facts regarding mishaps involving damage or injury.

Contractors will cooperate in any safety investigation, to include toxicology testing.

7.6 Compliance is mandatory;

contractor must meet minimum OSHA requirements. Per quarter, contractor must have zero willful OSHA violations; zero “serious” violations; no more than 2 “other than serious” violations (“violation” is defined in OSHA standards). Each OSHA violation must be resolved to the government’s satisfaction within 3 working days, except imminent danger situations which must be mitigated or resolved and reported immediately.

Incidents as reported in Status Reports, or violations reported to/observed by customer or COR.

5.0. GENERAL INFORMATION

5.1 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 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.3.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.4 Travel Requirements

Contractor employees may be required to travel to various locations both CONUS and outside the continental United States (OCONUS) in performance of Task Orders. For OCONUS travel, contractor employees shall possess passports, visas, and medical clearance for designated operations areas. The Government will not directly reimburse the contractor for these types of expenses. Travel will be cost reimbursable (no fee) in accordance with the Joint Travel Regulation (JTR). Contractors will not be required to price any travel costs on task orders. Ceilings will be established at time of award of each individual task order where the ceilings shall be inclusive of all indirect costs.

5.5 Relocation Costs

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

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

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

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

5.6 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.6.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.6.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.7 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.8 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:

(1) New Year’s Day

(2) Martin Luther King’s Birthday

(3) Presidents’ Day

(4) Memorial Day

(5) Independence Day

(6) Labor Day

(7) Columbus Day

(8) Veterans Day

(9) Thanksgiving Day

(10) Christmas Day

5.9 Government Downtime. Government Downtime occurs for various authorities including the President, Secretary of Defense, Secretary of the Air Force, AFOTEC/CC, or Base Commander of any Government Installation where work is performed.

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

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

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

(i) 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.

(ii) Government may forego the work. The contractor will not be paid for work not performed.

(iii) Government may reschedule the work on any day satisfactory to both parties.

(iv) 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.

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

(b) Base Closure Notification Procedures.

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

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

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

(4) If the decision to close all or part of the base is made during the duty day, and the

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

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

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

(2) If there is a need for work during the base closure but access will not be available, the Contractor may work off-site provided meaningful work may be accomplished.

Contractor shall certify to the government by letter within 5 business days or returning on-site the nature and scope of the work completed off-site. Contractor shall bill the Government at the labor rates specified in the contract.

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

5.10 Deliverables.

Deliverables will be specified in each task order.

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

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

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.

This is the start of the file's text. The full file is on GovTribe.

File details come from the government source that posted it. Updated .