Attachment 1 - CyOFTS III PWS 19May25.pdf

Cyber Operations Formal Training Support III

(CyOFTS III)

May 2025

CONTENTS

1 Introduction

1.1 Objective

1.2 Mission

1.3 Background

1.4 Scope

1.5 Vacancies

2 BASIC REQUIREMENTS

2.1 Business Relations

2.2 Non-Personal Services

2.3 Contract Administration and Management

2.4 Contract Management

2.5 Contractor Employees

2.6 Acceptable Quality Control Plan (QCP) for the PWS

2.7 Quality Assurance (QA)

2.8 Travel Requirements

2.9 Training

2.10 Intellectual Property

2.11 Technical Reports-Study/Services

2.12 Transition: Fully Executed Contractor Transition Plan

3 PERFORMANCE REQUIREMENTS

3.1 Training Mission and Mission Support

3.2 Cyber Mission Forces Instruction

3.3 DoDIN Ops Forces Instruction

3.4 Agile Combat Employment Expeditionary Communications (XCOMM) Instruction . 35

3.5 Information Warfare Instruction

3.6 Mission Support, Systems Operation and Range Operations

3.7 Cyber Training Range Environment (CTRE) Hardware / Software Purchase

4 DELIVERABLES

4.1 Contract Data Requirements List (CDRL)

4.2 Deliverable Requirements

5 SERVICE DELIVERY SUMMARY (SDS)

6 Government Property

6.1 Contractor Acquired Property (CAP)

6.2 Government Furnished Property (GFP)

6.3 Shared Property of the Government – As Is Condition

6.4 Baseline Support

7 Special Requirements

7.1 Security Requirements

7.2 Contractors Accessing and Handling Personally Identifiable Information (PII), If Applicable

7.3 Key Control

7.4 Locks/Keypad Combinations

7.5 Hours of Operation

7.6 Contractor Records

7.7 Government Observations

7.8 Safety Requirements

7.9 Mishap Notification

7.10 Housekeeping

Appendix A: Historical Level of Support

Appendix B: Professional Equivalency Codes

Appendix C: Education and Certification Requirements

Appendix D: Instructor Training Requirements

Appendix E: Applicable documents

Appendix F: Acronyms

1 INTRODUCTION

1.1 Objective

This performance work statement (PWS) establishes the requirement for contractor services in support of 39th Information Operations Squadron (39 IOS), also referred to as the Cyber Operations (CO) and Information Operations (IO) Formal Training Unit (FTU). This contract provides subject matter expertise (SME) and other essential capabilities to augment and support the mission of 39 IOS in support of Air Combat Command (ACC), Air Forces Cyber (AFCYBER), US Cyber Command (USCYBERCOM), and the US Government.

1.2 Mission

1.2.1 The mission of 39 IOS and its partners is to provide Initial Qualification Training (IQT), USCYBERCOM 2000-level work role training, and advanced training for Total Force (TF) Airmen to plan and execute tasks requiring CO and IO capabilities. The course offerings currently include disciplines that span Cyberspace Operations, Information Operations, Expeditionary Communications (XCOMM) and Instructor Training courses.

1.2.2 The 39 IOS is comprised of one squadron, with two geographically separated detachments. The main squadron is located at Hurlburt Field, Florida with Detachment 1 located at Joint Base San Antonio, Texas, and Detachment 2 located at Keesler AFB, Mississippi. The 39 IOS reports to the 318 Cyber Operations Group, 67 Cyberspace Wing, 16th Air Force/AFCYBER, Joint Base San Antonio Texas.

1.3 Background

1.3.1 The Department of Defense (DoD) Strategy for Operations in the Information Environment (OIE) (July, 2023) defines OIE as: “Military actions involving the integrated employment of multiple information forces to affect drivers of behavior.” As discussed by Carl von Clausewitz in On War, warfare is politics by other means. It is about coercive influence on an enemy to be able to affect their willingness to continue to fight. This can be achieved through kinetic means and maneuver and non-kinetic means and maneuver in the information environment. Operations in the Information Environment (OIE) are more contested than ever.

The DoD has made concerted efforts to address the growing concern for the Information Environment and introduced “Information” as a joint function of warfighting.

1.3.2 The 39 IOS is charged with providing the training for Cyberspace Operations and Information Operations. Cyberspace operations training includes the employment of cyberspace capabilities where the primary purpose is to achieve objectives in or through cyberspace.

Information Operations training includes those Information Warfare (IW) forces specifically trained to apply social science principles and fundamentals to shape the perceptions and behavior of relevant actors. The ability to integrate civilian/commercial technology and military tactics, techniques, procedures, discipline, and rigor into the training enables our graduates to defend our nation.

1.3.2.1 The Cyber Weapon Systems currently in use include but are not limited to the following:

Air Force Cyberspace Defense (ACD)

Air Force Intranet Control (AFINC) Cyberspace Defense Analysis (CDA)

Cyber Security and Control System (CSCS) Cyberspace Vulnerability Assessment/Hunter (CVA/H)

Joint Cyber Command and Control (JCC2)

1.3.2.2 Other Cyber and Information Operations Mission Areas include but are not limited to the following:

Offensive Cyber Operations (OCO) Defensive Cyber Operations (DCO) DoD Information Network Operations (DoDIN Ops) Expeditionary Communications (XCOMM) Data Analytics & Engineering Artificial Intelligence (AI) and Machine Learning (ML) Emerging Technologies Command and Control (C2) and Joint Planning Information Warfare (IW) Operations in the Information Environment (OIE) Military Deception (MILDEC) Operations Security (OPSEC) Military Information Support Operations (MISO) / Psychological Operations (PSYOP) Network Attack System (NAS)

1.3.3 Some courses within 39 IOS are accredited through the Community College of the Air Force (CCAF) or through Joint certification organizations. Each course syllabus identifies any external accreditation criteria.

1.3.4 The 39 IOS develops all courseware in accordance with (IAW) Air Force Instructional Systems Development (ISD) processes and procedures outlined in Department of the Air Force Handbook (DAFH) 36-2675, Information for Designers of Instructional Systems, Air Force Instruction (AFI) 10-217, Management of Air Force Operational Training Systems, Air Combat Command Instruction (ACCI) 11-251 and Department of the Air Force Policy Directive (DAFPD) 36-26 Total Force Development & Management. Other guiding references will include 39 IOS Operating Instructions (OI) and Standard Operating Procedures (SOPs). The organization utilizes the ISD method: Analyze, Design, Develop, Implement, & Evaluate, shorthanded as “ADDIE” to implement its curriculum.

1.4 Scope

1.4.1 The contractor shall provide qualified subject matter expertise (SME) manpower equivalents to augment and support training for the 39 IOS. The contractor shall augment and support 39 IOS to include but are not limited to the following:

Course Planning Course Instruction Course and Curriculum Development

Administrative Support

Technical Writing Project Management

Facility Management Instructor Training Training Systems Administration

Systems Administration Software Development Training Range Design and Development Training Range Engineering, Maintenance, and Management Help Desk Support

1.5 Vacancies

1.5.1 This requirement is for augmentation and support of Government employees. If any position goes vacant, the contractor shall notify the Government immediately. The Government will be compensated for any vacant position where work was not provided as required, with exception to normal holidays and/or vacation. This compensation will occur by reducing the monthly invoice amount by 8 hours times the number of duty days vacant for the period being invoiced, times the fully burdened labor category rate for each vacancy longer than 30 calendar days. A vacancy is defined by a Labor Category (position) proposed which does not have a current, qualified contractor employee fulfilling the daily requirements. Regular personal time off and/or company policy for “leave/vacation” does not constitute a vacancy. The vacancy calculation will immediately be effective upon the 31st calendar day of the vacancy; however, performance ratings will not be negatively affected until the vacancy is over 60 calendar days.

The contractor shall provide replacement personnel with substantially equal ability and qualifications when filling vacant positions. The contractor program manager will track vacant positions and provide a vacancy tracking chart in the Contractor Monthly Status Report (CMSR).

2 BASIC REQUIREMENTS

2.1 Business Relations

2.1.1 The contractor shall work with the government contracting officer’s representatives (COR), government program manager (GPM), and government team leads to accomplish government requirements, goals, and mission objectives as efficiently and effectively as possible.

This shall include sharing or coordinating information resulting from the work required within this PWS or previous government efforts and working as a team to perform tasks in concert.

2.1.2 The contractor shall ensure minimum duplication of effort in the execution of all work specified within this PWS and build upon work previously accomplished by the Government, the contractor, or other contractors to the fullest extent practical.

2.2 Non-Personal Services

2.2.1 This is a non-personal services contract. The Government will neither supervise contractor personnel 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 its employees and to guard against any actions that are of the nature of personal services or give the perception of personal services.

2.2.2 If the contractor believes that any actions constitute, or are perceived to constitute personal services, it shall be the contractor’s responsibility to notify the GPM and contracting officer immediately. The contractor will neither command forces nor lead military personnel.

These services shall not be used to perform any inherently government functions.

2.3 Contract Administration and Management

2.3.1 Contract Personnel Staff

2.3.1.1 The contractor shall ensure the number of personnel, job category, and expertise of the personnel assigned are sufficient to perform the work specified within the PWS. The contractor shall notify the COR 10 business days prior to any personnel re-assignments. The contractor, at its own expense, shall maintain proficiency, certification, and continuing education requirements in each performance area as listed within Appendix C: Education and Certification Requirements.

2.3.1.2 The contractor shall fully cooperate with the Government and other contractors.

2.3.1.3 The contractor shall provide employees who understand the unique requirements for the strategic, operational, and tactical levels of war in CO, IO and XCOMM to include planning and integration of these capabilities across the competition continuum. The provided contractor employees shall have the ability to manage and maintain the array of networks, infrastructure, ranges, and student mission training equipment required for the 39 IOS to effectively function.

2.3.1.4 The contractor shall staff site supervision at each site IAW the PWS. The site supervisor(s) or team lead(s) is responsible for the overall management of contractor personnel and is the primary interface between the Government and the contractor. These individuals shall have full contractor authority to act in all contractual matters and be responsible and accountable to the GPM, contracting officer, and COR in representing the contractor for meeting the performance requirements of this PWS. The site supervisors(s) and/or team lead(s) shall be available during normal business hours to meet with the COR or government team lead to discuss program and/or technical issues. The site supervisor(s) and/or team lead(s) shall attend scheduled meetings, as requested by the COR. The site supervisor(s) and/or team lead(s) is responsible for the overall management of contractor employees at their respective site, as the contractor program manager (PM) is the primary interface between the Government and contractor. Site supervisor(s), team lead(s), and/or PM will be the daily interface; therefore, they must have ongoing knowledge of daily activities within each work section. The site supervisor(s) and/or team lead(s) shall provide accountability of all employees to the COR/Government team leads no later than (NLT) 0900 hours each duty day. If the contractor PM and/or site supervisor(s) are unavailable for an extended period (more than 48 hours), these duties must be delegated to another Contractor Manpower Equivalent (CME) and the Government must be notified who will be performing these duties. The contractor personnel shall perform daily activities as coordinated with the site supervisor(s) and/or team lead(s). The site supervisor(s) and/or team lead(s) shall coordinate with the designated COR/government team leads on all tasks. The site supervisor(s) and/or team lead(s), along with the

COR/government team leads, shall establish workload requirements for the PM, site supervisor(s), and/or team lead(s) to align contractor employees to fulfill the task assignments.

2.3.2 The contractor shall ensure that personnel accessing information systems have the proper and current information assurance (IA) certification to perform information assurance functions IAW Air Force Manual (AFMAN) 17-1303, Air Force Cybersecurity Workforce Improvement Program, DoD Directive (DoDD) 8140.01, Cyberspace Workforce Management, and DoD 8570.01-M, Information Assurance Workforce Improvement Program.

2.3.2.1 DFAR 252.239-7001 Information Assurance Contractor Training and Certification.

a) The Contractor shall ensure that personnel accessing information systems have the proper and current information assurance certification to perform information assurance functions in accordance with DoD 8570.01-M, Information Assurance Workforce Improvement Program. The Contractor shall meet the applicable information assurance certification requirements, including—

(1) DoD-approved information assurance workforce certifications appropriate for each category and level as listed in the current version of DoD 8570.01-M; and

(2) Appropriate operating system certification for information assurance technical positions as required by DoD 8570.01-M.

b) Upon request by the Government, the Contractor shall provide documentation supporting the information assurance certification status of personnel performing information assurance functions.

c) Contractor personnel who do not have proper and current certifications shall be denied access to DoD information systems for the purpose of performing information assurance functions.

2.3.2.2 DoD Directive 8140.01, Cyberspace Workforce Management, establishes the DoD Cyberspace Workforce Framework (DCWF) as the authoritative reference for the identification, tracking, and reporting of DoD cyberspace positions and foundation for developing enterprise baseline cyberspace workforce qualifications.

2.3.2.3 DoD Manual 8140.03, Cyberspace Workforce Qualification and Management Program, requires contractors to be fully qualified by qualification standards and requirements in accordance with DoDD 8140.01 and this issuance. All contractor personnel in cyberspace work roles under the cybersecurity workforce element must be qualified in accordance with this issuance at the commencement of work. Contractor personnel assigned to perform Cyber and Cyber Weapon System IQT, IA, and Computing Environment/Infrastructure Support functions shall have a current applicable baseline certification as described in Appendix C: Education and Certification Requirements. The certificates must be provided to the COR during squadron in-processing. Throughout the course of this contract, internal movement of personnel may require updated certifications prior to move. The contractor employees shall maintain the minimum certification/training requirements in an electronic record through a government-shared network drive location. (CDRL A018)

2.3.2.4 Upon request by the Government, the contractor shall provide documentation supporting the IA certification status of personnel performing IA functions.

2.3.2.5 Contractor personnel who do not possess proper and current certifications shall be denied access to DoD information systems for the purpose of performing IA functions.

2.3.2.6 The contractor shall comply with all applicable Air Force Instruction (AFI), Operating Instructions (OI), Technical Orders, and 39 IOS Standard Operating Procedures (SOP) listed in Appendix E: Applicable Documents (Not Inclusive).

2.3.2.7 The contractor shall complete ancillary training, as required. This shall include Operations Security (OPSEC), Force Protection (FP), Human Relations (HR), Security, and Information Protection training and other ancillary training assigned and approved by the COR.

2.3.2.8 Contractor shall be proficient in Microsoft Office (or equal) suite of software products.

2.4 Contract Management

2.4.1 Program Management & Reporting. The contractor shall provide a management structure that enables contractor personnel to effectively perform the roles and responsibilities associated with the execution of PWS requirements, and ensures employees are present and engaged in appropriate tasks as identified in the PWS. (CDRL A009)

2.4.2 The contractor PM, site supervisor and/or team lead may participate in unit tasking and task update meetings. The contractor or Government may schedule additional formal or informal meetings to review deliverables, address any issues, and review contract status.

2.4.3 The contractor shall participate in government Program Management Reviews (PMR) with the GPM, contracting officer, and CORs. Frequency will be determined by the GPM. The PMR shall be held at a mutually agreed location to discuss financial, performance, and other programmatic matters. All contractor information presented at the PMR will be provided to the GPM and contract officer two weeks prior to the scheduled PMR in a presentation format (e.g.

Power Point slides). The charts will report on status, action items, problem areas, and accomplishments. The contractor will ensure minutes and action items are provided. (CDRL A013, A015, A016)

2.4.4 The contractor shall deliver a Monthly Status Report (MSR) to the Government. The MSR shall identify key accomplishments, performance gaps, recommended solutions, critical analysis, etc. Areas requiring management intervention shall be clearly identified in the report.

(CDRL A007)

2.4.5 The contractor shall participate in a “Post Award Conference” NLT 20 business days after the contract awards at a time, date and place coordinated and approved by the GPM. The contractor shall pre-coordinate, by email, with the GPM, Contracting Officer, and COR(s) on specific agenda topics and shall be prepared to discuss their program implementation strategy at this meeting. The contractor shall provide a detailed risk, issue and opportunity (RIO) management plan to identify known program RIOs and strategies to avoid or limit risks, manage issues, and enable opportunities. Following the Post-Award Conference, the contractor shall submit meeting minutes that include, at a minimum, summaries of topics discussed, action items, briefing slides, and handouts for GPM and COR approval. (CDRL A014)

2.4.6 The contractor shall effectively track, monitor, manage, and report costs, down to the contract line-item number (CLIN)-level. The contractor shall submit a Contract Funds Status Report (CFSR) IAW CDRL A016.

2.4.7 The contractor shall provide an Employee Work Schedule (EWS) consisting of all personnel to support resource allocation of operational schedules. The schedule shall list employee names and functions supported. The schedule shall be updated on a continual basis as changes occur, located on a government-shared network location (e.g. network drive or Microsoft Teams), and reported in the MSR (CDRL A007). Any unforeseen calendar changes shall be coordinated with the COR within 24 hours of notification of change. This information is vital and ensures mission is covered during times of emergency/natural disaster/pandemic/force majeure. The contractor shall identify all acronyms, codes, abbreviations, signs, and symbols used in the schedule. The contractor shall use the same format for initial and subsequent submissions of the same schedule unless otherwise approved by the COR.

2.4.8 The contractor will maintain a duty roster of contract personnel, to include phone number and address of those who are available to contact in emergencies. This information is considered Personal Identifiable Information (PII) and will be labeled, routed, and stored IAW 39 IOS SOPs, OIs, DAF, ACC & other Instructions. (CDRL A009)

2.4.9 Reporting. The contractor shall report all labor hours (including subcontractor labor hours) required for performance of services under the contract effort via a secure data collection site. The contractor shall completely fill in all required data fields using the following web address: www.sam.gov. Reporting inputs will be for the labor executed during the period of performance (PoP) during each government fiscal year (FY), which runs October 1 through September 30. While inputs may be reported any time during the FY, all data shall be reported no later than October 31 of each calendar year.

2.4.9.1 Annual Reporting. Reporting inputs will be for the direct labor executed during the PoP for each government FY. While inputs may be reported any time during the FY, all data shall be reported no later than 31 October of each calendar year. The contractor shall provide reporting inputs for the final PoP of this contract no later than 30 calendar days after contract expiration.

The contractor may direct technical questions about the SAM Service Contract Reporting tool to the Federal Service Desk FSD at https://www.fsd.gov/fsd-gov/home.do.

2.4.10 The contractor shall be responsible for any subcontract management necessary to integrate work performed on this requirement and shall be responsible and accountable for subcontractor performance.

2.4.11 Organizational Conflict of Interest (OCI)

2.4.11.1 The prime contractor shall manage work distribution to ensure there are no OCIs. The contractor may add or remove subcontractors to its team after GPM, contracting officer and COR notification.

2.4.11.2 The contractor shall not employ any person who is an employee of the US Government if employing that person would create an OCI. Additionally, the contractor shall not employ any person who is an employee of the Department of the Air Force, either military or civilian, unless such person seeks and receives approval according to DoD Regulation 5500.7- R, Joint Ethics Regulation (JER) and/or AFI 64-106, Contractor Labor Relations Activities. Contractor employees shall work in conjunction with, and in coordination with, all contractor organizations and government and contractor employees supporting 39 IOS initiatives. This includes, but is not limited to conducting research, instructing courses, developing lessons, establishing program schedules, system administration, range administration/operations, and identifying potential problem areas.

2.4.12 Associate Contractor Agreements (ACA)

2.4.12.1 During performance of this contract, the contractor shall be required to work with other contractors who have separate government contracts. IAW the AF Federal Acquisition Regulation (AFFAR) 5317.9000, Associate Contractor Agreements, the contractor shall enter into an ACA for any portion of the contract requiring joint participation in the accomplishment of the government requirement. The agreements shall include the basis for sharing information, data, technical knowledge, expertise, and/or resources essential to the success of 39 IOS and its mission partners. The agreements ensure the greatest degree of cooperation for successfully meeting the terms of the contract. The agreements shall also include the agreement start and expiration dates, and appropriate protection proprietary information and restrictions on personnel.

2.4.12.2 ACAs shall be initiated as soon as practical after contract award NLT 60 calendar days for existing contracts and shall be provided to the Government for review within 30 calendar days of notification and prior to execution by the parties. Any costs of entering and maintaining the ACAs shall be included in the negotiated cost of this contract. Liability for improper disclosure of any proprietary data contained in or referenced by any agreement shall rest with the parties to the agreement and not the Government. Failure to resolve disagreements with associate contractors does not entitle the contractor to any adjustment or waiver of terms of this contract.

2.5 Contractor Employees

2.5.1 The contractor shall not employ any person for work on this contract if such employment is identified to the contractor by the GPM or contracting officer as a potential threat to the health, safety, security, general wellbeing, or maintenance mission of the installation and its population.

2.5.2 All contractor employees shall be able to read, write, speak, and understand the English language to the extent necessary in the performance of the work.

2.5.3 Contractor employees shall identify themselves as contractor personnel by introducing themselves or being introduced as contractor personnel and displaying distinguishing badges or other visible identification for meetings with government personnel. In addition, contractor personnel shall appropriately identify themselves as contractor employees in telephone conversations and in producing formal and informal written correspondence.

2.5.4 The office environment at 39 IOS is predominately business casual. Contractor employees’ attire shall be business casual or contractor company logo apparel, depending on position and duties. Contractor personnel shall present a clean and neat appearance. Contractor shall not permit cut-off shorts and clothing with tears, faddish style, revealing/tight clothing, or clothing with obscene or inflammatory designs, slogans, or remarks, and clothing representing military attire or military uniform. The contractor PM/site supervisor/team leads shall ensure personnel wear appropriate clothes suited for their job.

2.5.5 The contractor shall provide to the COR resumes and certifications for all prospective candidates, identifying the positions being filled and the candidates’ ability to perform task in the described performance areas (CDRL A006). All resumes, throughout the life of the contract, will be vetted through the COR to ensure security compliance prior to performing on this contract.

The COR will have five (5) business days to review the resume and provide comments back to the contracting officer. The Government may impose a technical assessment of proposed employees performing tasks in support this PWS.

2.5.6 The contractor shall ensure all personnel are qualified, commensurate with education and experience levels for each labor category. The contractor shall ensure all employees possess the qualifications and certifications before starting work under this contract.

2.5.7 The contractor shall ensure all employees possess a valid civilian driver’s license and be able to hold a valid military driver’s license, if required.

2.5.8 The contractor shall ensure all employees submit to drug testing as required by the Government.

2.5.9 The contractor shall maintain a current listing of employees, which includes each employee’s full name, aliases, and areas of subject matter expertise (labor category) and shall be marked “Controlled Unclassified Information” (CUI). An electronic document shall be furnished to the GPM, contracting officer, and COR at the post-award conference. Personnel changes that are made during the performance of this contract shall be sent to the GPM, contracting officer, COR and 39 IOS/SO within 1 working day of the change and included in the MSR (CDRL A007).

2.5.10 Contractor Common Access Cards (CAC)

2.5.10.1 Contractor personnel will be issued a contractor CAC identified by a green stripe. The CAC is required to access any government base and certain facilities.

2.5.10.2 Contractor personnel indoctrinated for Sensitive Compartmented Information (SCI) access shall be identified by a locally produced badge, visible and worn above the waist and below the shoulders when present within the SCI Facility (SCIF). When exiting the SCIF, contractor personnel shall conceal their credentials from plain view and keep said credentials secure when not inside the SCIF.

2.5.11 Work Locations

2.5.11.1 The contractor shall perform the required support at the 39 IOS government facilities (may be subject to modification), at a contractor facility located off-base, or at an approved telework/remote or alternate work location (see para 7.5). Contractor personnel shall comply with all installation and facility safety and security regulations, as well as the health, safety, and security provisions of the contract.

2.5.11.2 Contractor personnel shall report security or safety problems to the GPM, contracting officer, COR and/or security police as appropriate. The contractor shall not perform any classified work in an off-base facility unless the facility is cleared to the appropriate security levels and coordinated with the Government before any classified work is accomplished. The COR or government team lead will notify the contractor PM of any current or future change in work location, if required. (CDRL A013)

2.5.12 Contractor Personnel

2.5.12.1 The contractor shall provide all qualified personnel required for maintenance at all sites within the continental United States (CONUS), as specified in the PWS. The contractor shall be responsible for the selection, recruitment, hiring, assignment of duties, and reassignment of duties, transfer, supervision, management, control, and termination of contractor employees in performance of government requirements. Contractor personnel are employees of the contractor and under its administrative control and supervision.

2.5.12.2 The contractor, through its personnel, shall perform the tasks prescribed herein IAW the Basic Contract PWS or other technical data contained in or referenced by the contract, contract modifications, and addendums.

2.5.12.3 The contractor shall accommodate rapid response and deployment to any operational government location. The response shall include, but may not be limited to, passports, visas, immunizations, and security/country clearances as required by the PWS.

2.5.12.4 The contractor and its employees shall not supervise, direct, or control the activities of government personnel or the employees of any other contractor. The Government will not exercise any supervision or control over the contractor’s employees in their performance of contractual services under this contract.

2.5.13 Site Supervision

2.5.13.1 The contractor shall staff site supervision at each site IAW the PWS.

2.6 Acceptable Quality Control Plan (QCP) for the PWS

2.6.1 Acceptable Quality Control Plan (QCP) for the PWS: The contractor shall ensure quality service is maintained throughout the life of the contract and shall prepare and implement a quality control plan (QCP) Quality Control Plan. The QCP shall reflect the contractor’s overall approach to quality, internal controls, and establishment of procedures for evaluating each of the major service areas (who, method, how often), reporting to the Government, resolving deficiencies, identifying potential improvements, documenting quality control inspections and any corrective actions taken, and maintaining quality control documentation (CDRL A020).

2.6.2 To meet the minimum standard for submission of QCPs, the contractor shall ensure the QCP is submitted to the government Quality Assurance Representative (QAR), or COR, within 30 calendar days after the start of the PoP. The contractor shall submit the QCP IAW PWS paragraphs 2.7.1 – 2.7.4. The COR will review these procedures (CDRL A020).

2.6.3 The QCP shall remain in effect during the term of the contract (including any option periods if exercised). Any revisions to the QCP shall be submitted to the COR within 30 days of revision following paragraphs 2.7.1-2.7.4. The contractor shall retain a copy on site and always ensure availability to all members of its on-site staff, as well as the GPM, COR and contracting officer (CDRL A020).

2.7 Quality Assurance (QA)

2.7.1 The COR is the authorized government representative(s) who will perform assessments of the contractor’s performance.

2.7.2 The COR(s) may inform the contractor in person when discrepancies occur and may request corrective action. The COR(s) may make a notation of the discrepancy on their assessment checklist with the date and time the discrepancy was noted and may request the contractor to initial the entry on the checklist.

2.7.3 Any matter concerning a change to the scope, prices, terms, or conditions of this contract shall be referred to the contracting officer.

2.7.4 The services performed by the contractor during the performance period of this contract shall, at all times and places, be subject to review by the GPM, contracting officer and COR.

2.8 Travel Requirements

2.8.1 Separate CLINs will be established to reimburse the contractor for allowable costs related to the performance of the contract requirements.

2.8.2 Travel shall be required under this contract to support 39 IOS mission activities. The contractor shall be required to travel CONUS and may be required to travel to Other than Continental United States (OCONUS) to base location(s) or Air Force site(s) in performing site visits, conference and training attendance, and Mobile Training Teams (MTT). All travel requirements (including plans, agenda, itinerary, dates) shall be pre-approved by the COR, contracting officer, and GPM and are on a cost reimbursable basis. Government contractors presenting themselves for travel shall have letters of identification and shall require passports for OCONUS travel. Government Contract City Pair fares are not available to contractors. The contractor shall provide the trip report (CDRL A008) with the MSR (CDRL A007). The trip report shall detail the work completed, lessons learned, and applicable recommendations, and shall include a copy of the traveler’s submitted travel voucher.

2.8.3 Contractor on-site personnel may be required to travel to worldwide locations. The contractor is responsible for acquiring the contractor Defense Base Act (DBA) insurance expense for travel outside the United States (US). These trips may be necessary to support training, conference attendance, real world or exercise planning and participation, and other travel as required. Contractor personnel expenses for lodging and per-diem will not exceed the government rates listed in the Joint Travel Regulations (JTR). Contractor personnel are authorized and may be directed to utilize military lodging facilities. All contractor travel requests must be submitted and approved in advance of travel by the COR.

2.8.4 Lump Sum Invoicing shall be processed through Wide Area Workflow (WAWF) for each CLIN of this requirement; however, the contractor shall provide a separate detailed breakdown of the costs associated with the reimbursable CLINs. Government rates used in the request for reimbursement will be verified for compliance with the JTR at the time of billing. Payment instructions will be dictated via appropriate clauses.

2.9 Training

2.9.1 The contractor is responsible to schedule and coordinate specialized training that ensures contractor personnel maintain currency in military/defense-specific systems, to include hardware, software, and other systems throughout the performance of the contract. As the need for additional training is discovered, the contractor will identify the location of the training and prepare a cost estimate for attendance and submit this estimate to the Government for approval.

If attendance is approved, the contractor will be reimbursed for all allowable and allocable costs.

Employees of the contractor are expected to maintain currency in their core professional competencies in a manner that is standard practice in the industry, which includes the maintenance of certifications, attendance at required refresher courses, and obtaining training in new product releases or updates. The Government will not reimburse the contractor for professional training and the maintenance of certifications, except where the requirement is new and government directed. The Government may allow no-cost Letter of Intent (LOI) for the employee to attend applicable required training.

2.9.2 Government-Provided Formal Training. If the contractor attends any government provided formal training, the contractor is responsible to provide the trained capability for the duration of the contract base or option year. The Government will provide 39 IOS-specific required formal training to contractor employees requiring the training to complete their instructor certification requirements. If a government-trained contract employee leaves the employment of the contractor within one year, then the contractor shall reimburse the Government for the provided formal training or hire a replacement with the same education credentials. Government reimbursement shall be negotiated with the contracting officer on a case-by-case basis. (CDRL A017)

2.10 Intellectual Property.

All programs/deliverables developed per this contract are the property of the US Air Force and shall not be released by the contractor to third party organizations.

2.11 Technical Reports-Study/Services.

Upon government request, the contractor shall perform an analysis of requested topic and/or area of study. A technical report provides fully documented results of studies or analysis performed.

(CDRL A012)

2.12 Transition: Fully Executed Contractor Transition Plan

Transition is defined as the time in days from contract award until the last date prior to the start of the specified start date in the PoP. Contract PoP start is defined as the first day of hands-on labor performance and the day after the transition period ends. To achieve the required team, complement as specified in the PWS by day 1 of PoP start, the contractor shall provide a time-phased transition plan IAW the PWS (CDRL A021) and provide status to the COR on weekly basis throughout the transition period. The contractor shall provide a transition execution status report, as specified in PWS. The contractor shall execute each transition within the contractor specified timelines and goals. Qualified personnel shall be determined qualified by the contractor prior to the start of their labor performance. The contractor shall be able to meet a transition timeframe of no fewer than seven (7) calendar days and no more than sixty (60) days while minimizing disruption during the transition period and maintaining cost and schedule.

2.12.1 To meet the minimum standard for transition, the contractor must fully execute all transitions within the contractor specified goals. The metric will be measured on the contractor’s ability to meet all contractor specified timelines as reported to the Government in CDRL A021.

2.12.2 Transition Process (Phase-In/Phase-Out Period)

To minimize any decreases in productivity and to prevent possible negative impacts on additional services, the contractor shall have appropriate personnel on board during the phase-in/phase-out periods. The contractor shall retain all responsibilities and maintain the same level of performance specified in this PWS during the entire Phase-Out period of the contract.

2.12.3 Contractor Phase-In

During the initial transition period (Phase-In), the contractor shall become knowledgeable with all performance requirements and shall commence full performance of services and assume full responsibility the first day of the contract PoP.

The phase-in period is intended to afford the contractor the opportunity to complete all tasks necessary to assume full contract performance responsibilities. While under no obligation, the Government plans to grant no less than a sixty (60) calendar day phase-in period after contract award (CA).

The CA date initiates the first date of the phase-in period. The phase-in period expires the calendar day preceding the PoP start date. The length of the phase-in period will be at the discretion of the Government.

During phase-in, the contractor shall conduct the joint inspection, acquire personnel, obtain access for personnel, conduct training for its personnel and perform all other tasks as required to assume full performance of duties at start of the PoP. During this period, the contractor may observe all operations and maintenance being performed on a not to interfere basis.

During the phase-in period, the contractor shall complete all activities necessary to inventory, operationally check, and ensure sufficient staffing and management is available to perform the PWS requirements at start of the PoP.

2.12.4 Phase-In Plan

The contractor shall provide a phase-in plan at CA (CDRL A022). The phase-in plan shall include how the contractor will conduct phase-in requirements in accordance with the requirements of this contract. During the phase-in period, the contractor shall provide weekly updates to the COR, which includes the weekly progress of work, status of phase-in significant tasks, and identification of any potential problems.

2.12.5 Contractor Phase-Out

The phase-out period is a period of time prior to the expiration of the contract’s final PoP. The transition timeframe is 60 calendar days prior to the end of the final PoP.

2.12.6 Phase-Out Plan

Prior to the end of contract performance, the performing, incumbent contractor shall provide the Government with a Phase-Out Plan 90 calendar days prior to expiration of contract performance, unless otherwise directed by the CO (CDRL A023). The Phase-Out plan shall include how the contractor, as the incumbent contractor, will conduct transition activities with the successor contractor. The transition period shall start 60 calendar days prior to contract expiration.

2.12.7 Transition to Successor Contractor

The incumbent contractor shall provide all reasonable support to the successor contractor to ensure orderly transition and minimize impact on operational readiness. Throughout the

Transition Period, the incumbent contractor shall allow the successor contractor to observe the performance of all required maintenance and support tasks on a not to interfere with training and maintenance basis.

3 PERFORMANCE REQUIREMENTS

3.1 Training Mission and Mission Support

3.1.1 The contractor shall augment and support the government and the 39 IOS in accomplishing its training mission and mission support tasks.

3.1.2 The contractor shall comprehend the 39 IOS mission, the cyber training ranges and Weapon Systems associated with the training requirements.

3.1.3 The contractor shall augment and support mission operations in the areas of course development, research, analysis, curriculum development, curriculum instruction, and curriculum evaluation in unclassified and classified environments.

3.1.4 The contractor shall augment and support mission support functions in the areas of course management support, faculty development, planning, project management, administrative support, facility management, cyber range systems, communications and information technology systems, audio visual systems in unclassified and classified environments.

3.2 Cyber Mission Forces Instruction

3.2.1 Cyber Operations Training Research and Analysis

3.2.1.1 The contractor shall plan, contribute to, research, and analyze Joint and service-specific training documents IAW government-approved directions, guidance, and timeline milestones.

Training documents including but not limited to: Training Needs Analysis (TNA), Training System Requirements Analysis (TSRA), Master Training Task List (MTTL), Systems Training Plan (STP), Training Task List (TTL), Task Analysis Worksheets (TAW), including USCYBERCOM Joint Cyberspace Training and Certification Standards (JCT&CS).

3.2.1.2 The contractor shall plan, contribute to, research, and analyze Joint and service-specific operations, activities and plans for cyber operations. This includes but is not limited to current and future organizations, teams, plans, operations, systems, and actions involved with cyber operations. (see para 1.3.2.1 and 1.3.2.2 for a non-inclusive list of CO and IW weapon systems and mission areas)

3.2.1.3 The contractor shall plan, design, develop, integrate, modify, update, and instruct required Special Access Program/Special Access Required (SAP/SAR) material to perform certain functions and technologies for integration into the curriculum and into mission systems where applicable.

3.2.1.4 The contractor shall plan, contribute to, research, and analyze Joint and service-specific Tactics, Techniques and Procedures (TTP) and threats.

3.2.1.5 Contractor shall plan, contribute to, research, and analyze DoD information systems associated with DAFIN, DAFNET, DoDIN, and Joint Information Environment (JIE) or other systems, in a manner that ensures training systems are kept up to date with the current cyber environments and learning objectives for each course requiring DoD information systems associated with DAFIN, DAFNET, DoDIN, and Joint Information Environment (JIE) or other systems integrating into Cyberspace Training Range Systems.

3.2.1.6 Contractor shall plan, contribute to, research, and analyze USCYBERCOM/AFCYBER Cyber Mission Forces (CMF), Cyber Protection Team (CPT), Cyber Support Team (CST), National Support Team (NST), Cyber Mission Team (CMT), National Mission Team (NMT), operations in a manner that ensures training systems are kept up to date with the current cyber environments and learning objectives for each course requiring USCYBERCOM/ AFCYBER CMF, CPT, CST, NST, CMT, and NMT integrating into Cyberspace Training Systems and Ranges.

3.2.1.7 Contractor shall plan, contribute to, research, and analyze 16 AF/AFCYBER Cyber Weapon System operations in a manner that ensures training systems are kept up to date with the current cyber environments and learning objectives for each course requiring integration into Cyberspace Training Systems. (e.g., AFINC, CSCS, ACD, CVA/H, JCC2, and CDA.)

3.2.1.8 Contractor shall plan, contribute to, research, and analyze computer Internet Protocol (IP) fundamentals, advanced IP concepts, cyber operations fundamentals, advanced cyber operations concepts, converging networks, and emerging technologies that ensures training systems are kept up to date with the current cyber environments and learning objectives for each course requiring integration into the curriculum and into mission systems where applicable.

3.2.1.9 Contractor shall plan, contribute to, research, and analyze Air Force and Joint Cyber OCO and DCO, operations that ensures training systems are kept up to date with the current cyber environments and learning objectives for each course requiring integration into the curriculum and into mission systems where applicable.

3.2.1.10 Contractor shall plan, contribute to, research, and analyze operations in the information environment, Information in Joint Operations, and Information in Air Force Operations that ensures training systems are kept up to date with the current environments and learning objectives for each course requiring integration into the curriculum and into mission systems where applicable.

3.2.1.11 Contractor shall analyze and review feedback from internal and external sources with military and Government staff to ensure currency, consistency, and quality of course material that ensures training systems are kept up to date with the current environments and learning objectives for each course requiring integration into the curriculum and into mission systems where applicable.

3.2.1.12 Contractor shall observe and participate in internal and external exercises and document the most up to date, unique processes and lessons learned that ensures training systems are kept up to date with the current environments and learning objectives for each course requiring integration into the curriculum and into mission systems where applicable.

3.2.1.13 Contractor shall survey current and post graduate cyber operations team members in order to fill information gaps and obtain recent real-world examples for inclusion in curricula that ensures training systems are kept up to date with the current environments and learning objectives for each course requiring integration into the curriculum and into mission systems where applicable.

3.2.2 Curriculum Development for Training

3.2.2.1 Contractor shall augment and support the Government in course planning and development, including, but not limited to, all formal training courses, lessons, and related courseware material.

3.2.2.2 Contractor shall develop curriculum IAW applicable Master Training Task List (MTTL) and Training Task List (TTL) requirements as well as audit and edit all developed courseware for accuracy, completeness, flow, balance, and clarity of understanding, IAW 39 IOS SOPs/Instructions/OIs, ACC Instructions, and Joint Directives.

3.2.2.3 Contractor shall provide associated documentation for design, development, revision, and administration of FTU training. (CDRLs A001 A002 A003 A004).

3.2.2.4 Contractor shall utilize the ISD ADDIE Model, along with Bloom’s taxonomy level of learning and/or the Substitution, Augmentation, Modification, Redefinition (SAMR) Model for all course development.

3.2.2.5 Contractor shall assist in the development of Training Systems Requirements Analysis to include Mission/Task Analysis (MTA), Training Requirements Analysis (TRA), Objective Media…