PWS_533TRS_EIST_GET_DRAFT.docx

PERFORMANCE WORK STATEMENT (PWS)

FOR

SPACE FORCE ENLISTED INITIAL SKILLS TRAINING (IST)

1 May 2026

533d Training Squadron Delta 1

STATEMENT D: Distribution authorized to the Department of Defense and U.S. DoD Contractors only; administrative/operational use; 13 August 2021. Other requests for this document shall be referred to HQ STARCOM Enterprise Sourcing Office.

WARNING: This document contains technical data whose export is restricted by the Arms Export Control Act (Title22, USC, Sec 2751, et. seq.) or the Export Administration Act of1979, as amended, Title 50,USC., App. 2401,et.seq. Violations of these export laws are subject to severe criminal penalties. Dissemination of this document is controlled under DoD Directive 5230.25.

DESTRUCTION NOTICE: Destroy by any method that will prevent disclosure of contents or reconstruction of the document.

CHANGE CONTROL SUMMARY

Revision (Rev). A revision should be used to consolidate all changes into a new basic document with a new basic date. It should be used to clean up the document when it begins to become confusing with too many changes. It is the Data Managers (DM) decision when to revise the document. Number the revision and include a summary of the revisions in the change table. DM will remove all change bars when the document is revised since the revised document takes all previous changes into account. Do not remove changes from the change table when the document is revised since they may lend important historical value.

Version (Ver). A change that is administrative in nature does not require the document to be re-staffed. Changes that remove or add items periodically assessed or affect items assessed in frequency of assessment or thresholds must be re-staffed for approval. Consolidate changes when possible. Include a summary of the changes incorporated in the change table. Ensure change bars have been inserted after initial release.

Table of Contents

Performance Work Statement (PWS)

1 Introduction/Background In 2023, the Chief of Space Operations (CSO) initiated an effort to refine the roles for Space Force officer, enlisted, and civilian Guardians to better prepare the USSF for dominating in the space-domain. In this new construct, the enlisted Guardians serve as the technical specialists that execute orders while serving as leaders, weapon system experts, and advisors to their officer and civilian counterpart across satellite operations, cyberspace operations, and intelligence operations in the space-domain. The development, education and training of the enlisted force starts with the foundation built during Initial Skills Training. To achieve this level of technical depth across knowledge, skills and abilities, the USSF is transforming its initial skills training to meet the CSO’s vision. This evolution is called the Guardian Enlisted Training (GET) initiative.

1.1 Mission Overview

The mission of the 533d Training Squadron (533 TRS) is to transform Guardians and Airmen into joint-minded space professionals possessing both the necessary technical skills, and the Guardian Spirit required to protect, defend, and deliver spacepower.

1.2 Scope

The 533 TRS is the provider of all required foundational skills and knowledge, through space-centric training for the United States Space Force enlisted Guardians.

In order to accomplish this training, initial skills training courses must be developed, instructed and maintained. This PWS is to provide subject matters experts and instructors to fulfil those three objectives. A list of current and projected courses is provided in Attachment 4.

2 General Requirements This section describes the general requirements for this effort. The following sub-sections provide details of various considerations on this effort.

The Period of Performance is as follows:

Base Year: Contract start – 1 Jan 2027 OY1: 01 Jan 2028 – 31 Dec 2028 OY2: 01 Jan 2029 – 31 Dec 2029 OY3: 01 Jan 2030 – 31 Dec 2030

2.1 Non-Personal Services

The Government will neither supervise Contractor employees nor control the method by which the Contractor performs the required tasks. Under no circumstances will the Government assign tasks to or prepare work schedules for individual Contractor employees. The Contractor shall ensure its employees understand the prohibitions imposed on the Government regarding personal services contracts, as defined in the FAR as “a personal services contract is characterized by the employer-employee relationship it creates between the Government and the contractor’s personnel.” The Contractor shall manage its employees and guard against any actions that are of the nature of personal services or give the perception of personal services. If the Contractor believes that any actions constitute, or are perceived to constitute personal services, the Contractor shall notify the Procuring Contracting Officer (PCO) immediately.

2.2 Contractor Management

The Contractor shall integrate and coordinate all activity needed to satisfy the requirements of this PWS. The Contractor shall manage the timeliness, completeness, and quality of problem identification, and resolution. The Contractor shall provide corrective action plans, proposal submittals, timely identification of issues, and effective management of sub-Contractors. The Contractor shall seek to ensure customer satisfaction and professional and ethical behavior of all Contractor personnel. If the Contractor has any proposed revisions to this PWS or any other contract attachment, for the purpose of making the documents more accurate (regulatory changes) or complete (for clarity), the Contractor shall submit suggested revisions as word document with tracked changes and a change request to the COR and CO for consideration.

The Contractor shall provide a Monthly Status Report (MSR) covering activities of the preceding month.

Deliverable A001 – Monthly Status Report (MSR)

2.2.1 Contract Administration

The Contractor shall ensure its personnel do not perform inherently Governmental activities, as defined in FAR 7.5. The Contractor shall ensure its personnel do not attempt to represent the Government of the United States (US) to any other person or entity, US, or foreign, except for delivering a Government-approved message or position. The 533 TRS will review all briefings, policies, plans and other formal products developed by the Contractor.

2.2.2 Contractor POC

The Contractor shall appoint a Program Manager as a single point of contact between the COR and Contractor personnel assigned to support this contract. This lead shall coordinate with the Contracting Officer’s Representative (COR) to obtain and clarify contract requirements and shall be responsible for the daily control and supervision of the Contractor’s employees.

2.2.3 Personnel Administration

The Contractor shall maintain the currency of their employees by providing initial and refresher training as required to meet the PWS requirements. The Contractor shall obtain approval from Government COR prior to attending Government-provided training classes.

2.2.4 Contractor Identification

Contractor employees shall clearly always identify themselves As “Contractors”, in all communications and representations, including in the workplace, at meetings, in conversations, telecommunications, mail, electronic mail (e-mail), and faxes.

2.3 Contractor Personnel, Disciplines, and Specialties

The Contractor shall accomplish the assigned work by employing and utilizing qualified personnel with appropriate combinations of education, training, and experience. Certain positions are identified as key personnel, and have minimum qualifications, as outlined in Attachment 4.

2.3.1 533 TRS Instructor Policies All contract personnel shall follow the guidelines set forth in the 533 TRS Policies. Specifically:

- Instructor Evaluations (CCAF Policies, Procedures, and Guidelines)

- Capstone Instructor Subject Matter Testing

- Instructor Evaluator Guide

- Instructor Qualification

- Instructor Restriction and Decertification

2.3.X Abuse of Power Agreement All contract personnel read, acknowledge and follow the instructor/staff rules layout in the abuse of power form(s).

2.3.2 Key Personnel Removal

The Contractor shall not substitute key personnel in the first 60 days of contract performance unless the substitution is necessitated by illness, death, or termination of employment. The Contractor shall notify the COR and PCO within 15 calendar days after the occurrence of any of these events and provide a detailed explanation of the circumstances necessitating the proposed substitutions in compliance with the Health Insurance Portability and Accountability Act (HIPAA). After the initial 60-day period, the Contractor shall submit the information required to the PCO and COR at least 15 days before making any permanent substitutions.

2.3.2 Key Personnel Substitution

The Contractor shall provide complete resumes for the proposed substitutes to the 533 TRS COR and PCO. The 533 TRS COR will approve all key personnel changes.

2.3.1 Personnel Turnover

The Contractor shall ensure continuity of services during personnel absences due to sickness, leave, and voluntary or involuntary termination from employment such that the impact to the Government is minimal. Once the Contractor knows an employee will no longer support the contract, the Contractor shall provide written documentation to the PCO and COR within three (3) business days. In this notification, the Contractor shall include the date the position will be vacant, anticipated fill date, and what management actions the Contractor will take to ensure uninterrupted performance. Position vacancies shall not exceed 21 calendar days unless approved in writing or otherwise directed in advance by the CO.

2.3.2 Removal of Personnel at Government Request

The COR may request removal (permanent or temporary) of personnel for security, safety or health reasons, or when Contractor personnel behave in an unprofessional manner that would be considered unacceptable.

2.4 Location and Hours of Work

This PWS primarily requires work at Government facilities on Vandenberg Space Force Base, California. Normal workdays are eight (8) hours per day, Monday through Friday, except US Federal Holidays. Portions of required work may take place outside of normal hours, such as weather cancellations necessitating class hours scheduled on a weekend to make up a lost day of instruction. With two-week notice, a T-shift (1530 to 0030) schedule may be required to meet student throughput requirements, if those requirements exceed a day-shift classroom capacity. If a T-shift is required, the minimal number of contractors will be used to continue training operations, with the remainder staying on a normal workday schedule.

2.4.3 Building Access

The Government will provide Contractor personnel unescorted access to 533 TRS facilities, consistent with task requirements. Access to Government facilities, documents and systems will be in accordance with the DD Form 254.

2.4.4 Morale Events

Contractor personnel shall comply with their company’s policy regarding interaction with 533 TRS employees during morale and recreational activities. Activities may include holiday parties, sports outings, or other similar activities.

2.4.5 Closures

Classes will occur according to the approved schedule, unless weather conditions dictate delays or cancellations.

2.4.6 Teleworking

Telecommuting/telework is defined as authorization for an employee that works at a United States Government (USG) location, to work at an alternate location, i.e., at the employee’s home or Contractor location, either routinely or situationally. A contractor-designated location is defined as a contractor-identified place of performance for specific employees, i.e., not at the USG location. There are two types of telecommuting/telework; 1) routine telework in which telework occurs as part of an ongoing, regular schedule within the designated installation operating location area, and 2) situational telework that is approved on a case-by-case basis, where the hours worked were not part of a previously approved, ongoing and regular telework schedule, to include pandemic situations and remote telework (teleworking outside the operating location area), and other non-routine telework situations.

2.4.6.1 Routine Telework Approval

The Contractor shall submit a teleworking request with appropriate rationale via e-mail to the COR no later than 15 days prior to the requested change in work status. The request shall include the Contractor’s Program Manager’s approval, as well as the primary Government customer’s approval (Academic Affairs, Provost, Plans and Programs).

2.4.6.2 Classified Telework

Teleworking is not authorized for classified work. Authorized telework locations do not abrogate the Contractor’s requirement for complying with the protection of information IAW DoD, USAF, and USSF regulations, Security and Protection of Information sections of this PWS, contract clauses or the DD Form 254.

2.4.6.3 Remote Telework Approval

Remote telework (teleworking outside the operating location area), will be considered on a case-by-case basis. Any costs related to maintenance required for remote telework Government furnished equipment not due to negligence, including shipping costs (if required), will be paid by the Government. The Contractor shall provide a written request with appropriate rationale for COR approval prior to any remote telework. For approved remote telework, Contractor employees may be required to return to the operating location on an as needed basis. All Government-directed travel requirements shall be approved IAW Section 2.5 of this PWS and FAR 31.205-46, and expenses will be paid by the Government.

2.4.6.4 Remote Work – For curriculum development only

While not the preferred solution, remote work will only be considered for curriculum development to bring in required expertise on a case-by-case basis. All instruction must be done locally at the schoolhouse. If a contractor is dual-hatted as curriculum developer and instructor, they can’t be a remote worker on this contract.

2.4.6.4 Contractor Personnel Roster

The Contract shall update the Contractor Personnel Roster (A002) for any government approved changes to employee routine telework or remote work status or location and submit it on the schedule in the Deliverable Table.

Deliverable:

A002 - Contractor Personnel Roster

2.5 Travel / Temporary Duty (TDY)

The Contractor shall make their own travel and lodging arrangements and shall ensure all required security requirements (e.g., Visit Requests, DoD Foreign Clearance Guide, Force Protection Training) required for access to installations and/or facilities are completed prior to travel.

2.5.1 Travel Approval

The Contractor shall submit all travel requirements (including plans, agenda, itinerary, or dates) to the COR for approval

2.5.2 Travel Costs

The Contractor shall bill travel separately and at cost. The Government has established Travel at a Note to Exceed (NTE) amount. If additional funds are required, the Contractor must seek modification for increase prior to approval. If the NTE is exceeded without modification and/or approval, the Government reserves the right to reject invoices for travel in excess of the established NTE amount. Costs for travel shall be billed in accordance with the regulatory implementation of Public Law 99-234, Federal Acquisition Regulation (FAR) 31.205-46 Travel Costs, and the Joint Travel Regulation (JTR) to the greatest extent possible. Travel expenses for local travel are not chargeable to the contract; local travel is defined as within 60 miles of Vandenberg Space Force Base (SFB).

2.5.4 Estimated Travel Requirements

If travel is required, the Contractor shall propose a travel schedule to the COR that does not exceed the approved amount.

Deliverable:

A003 Travel Report (if required)

For all trips, the Contractor shall provide a trip report within ten (10) business days of the return date from travel. Extensions may be granted by the COR on a case by case basis. As a minimum, trip reports will include the objectives and outcomes of the trip. Trip reports do not have a specific format and may range from an email to a formal presentation depending on the type of trip.

2.6 Security

All Contractor personnel proposed to work on this task order must be U.S. citizens. All Contractor personnel with access to unclassified information systems, including e-mail, shall have at a minimum a favorable National Agency Check (NAC).

2.6.1 Common Access Card (CAC) and Access ID Badge

Contractor employees shall obtain and possess a DoD CAC, and an Access ID Badge as required for access to government systems or government facilities in the performance of this contract. Contractors shall use the card IAW AFFARS 5352.242-9001. The Contractor shall submit applications to the COR for the DoD CAC.

2.6.1.1 Sensitive Compartmented Information Facility (SCIF) Bage Contract employees are required to wear the approved SCIF identification badge at all time within the sensitive compartmented information facilities (SCIFs). Badges must be visible above the waist, on the front of the body so it can be clearly seen.

2.6.2 Contract Employee Termination

The Contractor shall ensure employees who terminate their services to this contract shall immediately return any Government identification/access badges issued in support of this contract. Any GFI must be returned to the Government prior to departure. The Contractor shall immediately notify the COR of the employees’ departure to ensure all access to Government systems and facilities is terminated and update the Contractor Personnel Roster (A002).

2.6.3 DD Form 254

DD Form 254 specifies overarching security requirements and Contractor access to classified information. All Contractor personnel satisfying the requirements of this contract directly shall have Top Secret (TS)/Sensitive Compartmentalized Information (SCI) or Secret clearances, depending on the roll, as of their start of performance date. All Contractor personnel shall be able to access material up to the classification level in accordance with the DD Form 254.

2.6.4 Operational Security (OPSEC)

The Contractor shall adhere to OPSEC guidance as defined in Air Force Instruction (AFI) 10-701, Operations Security (OPSEC). The Contractor shall complete OPSEC in-processing training and follow-on OPSEC training such as event-driven and annual OPSEC training, as required by the OPSEC Program Manager per Department of Defense (DoD) Directive (DoDD) 5205.02E, DoD Operations Security (OPSEC) Program; DoD Manual (DoDM) 5205.02, DoD Operations Security (OPSEC) Program Manual; Chairman of the Joint Chiefs of Staff (CJCS) Instruction (CJCSI) 3213.01D, Joint Operations Security; and AFI 10-701.

2.6.5 Critical Information and Indicator List

The Contractor shall be familiar with the organization’s Critical Information and Indicator List (CIIL) and ensure indicators and vulnerabilities are protected from Unauthorized Disclosure (UD) per HQ Space Training and Readiness Command’s (STARCOM’s) countermeasures and measures.

2.6.6 Controlled Unclassified Information (CUI)

The Contractor shall safeguard all information provided and marked as CUI via this contract IAW DoD Instruction (DoDI) 5200.48, Controlled Unclassified Information (CUI). If the Contractor generates any CUI information, it shall protect and disseminate that information per the controls required by DoDI 5200.48. The Contractor shall monitor CUI for aggregation and compilation based on the potential to generate classified information pursuant to security classification guidance addressing the accumulation of unclassified data or information. The Contractor shall immediately report the potential classification of aggregated or compiled CUI to the CO and the COR. The Contractor shall safeguard unclassified nonpublic information by applying specified network security requirements, as defined in DoD Instruction 8582.01, Security of Non-DoD Information Systems Processing Unclassified Nonpublic DoD Information, which includes identified CUI and Federal Contract Information that resides in or transits contractor unclassified information systems.

2.6.7 Protection of Classified Information

The Contractor shall take proper precautions to ensure unauthorized persons do not gain access to classified information. The Contract shall only use methods identified in DoDM 5200.01, Volumes 3 and 4 to store classified information when it is not under personal observation and control of an authorized individual.

2.6.8 Personnel Security Program

The Contractor’s assigned personnel shall establish and maintain eligibility for access to TOP SECRET Sensitive Compartment Information (SCI). Government security officers will determine whether the Contractor’s personnel meet the personnel security requirements for the tasks under this contract. Personnel without access to TOP SECRET SCI must be approved by the COR, prior to costs being reimbursed related to providing personnel who fail to meet the security requirements.

2.6.9 Non-Disclosure Agreements (NDA)

The Contractor’s assigned personnel shall complete and sign Non-Disclosure Agreement(s) (SF-312) regarding protection of sensitive Government and third-party Contractor information.

Deliverable:

A004 - NDA

2.6.10 Communications Security (COMSEC) Monitoring

Telecommunications networks are continually subject to interception by unfriendly intelligence organizations. All communications within DoD organizations are subject to Communications Security (COMSEC) review. The Government may conduct COMSEC monitoring and recording of electronic or voice communications originating from or terminating at DoD organizations at any time. The Contractor shall ensure all assigned personnel are aware any time they communicate to or from a Government facility, they are subject to COMSEC procedures. The Contractor shall ensure wide and frequent dissemination of the above information to all employees dealing with Government information.

2.6.11 Physical Security

The Contractor shall safeguard all Government equipment, information, and property provided for Contractor use. The Contractor shall comply with Government Operations Plans and Instructions for Force Protection Condition procedures, Random Antiterrorism Measures, and local search and identification requirements.

2.6.12 Counterintelligence Cooperation

The Contractor shall attend mandatory Counterintelligence (CI) briefs when traveling to a foreign country and complete a debrief upon their return with the Air Force Office of Special Investigations.

2.7 Manpower Reporting

The Contractor shall report the labor executed during the period of performance during each Government fiscal year (FY), which runs October 1 through September 30. The Contractor shall report all data no later than October 31 of each calendar year.

Deliverable A009 – Manpower Reporting

2.8 Documentation

2.8.1 Data Rights

The Contractor shall provide all materials developed, maintained, and utilized under this PWS to the Government with unlimited data rights.

2.8.1.1 Curriculum

All curriculum developed under this PWS will be owned by the Government. Examples included (but not all inclusive) lesson plans, workbooks, test questions, hands on activities, and scenarios.

2.8.1.2 Licensed Material

The one exception to government owning the material applies to proprietary materials licensed from third-party vendors, that is incorporated into a course’s flow. Hypothetical Example: The government purchases a third-party cyber lab product (ex: HackTheBox) that is to be used in the course. The government would not own this material. The work under this PWS would work to integrate it into the government’s curriculum as seamlessly as possible.

2.8.2 Contractor Use of Materials

The Contractor shall request COR approval to use any 533 TRS or Delta 1 products pertaining to this contract for business development or any other Contractor purposes. The Contractor is authorized to include summary performance information in proposals to be submitted to the Government to satisfy past performance information requirements.

2.8.3 Government Data

The Contractor shall request Government approval prior to the use of any proprietary data or software tools to fulfill the requirements of this contract. The Government will provide the Contractor with access to information required to accomplish assigned tasks commensurate with security clearance and on a need-to-know basis. The Contractor shall not retain classified or unclassified material generated or received under this contract after the contract ends without approval of the Contracting Officer.

2.9 Performance Evaluation

Contractor performance is subject to Government surveillance to ensure PWS compliance. The Contractor shall comply with the following:

2.9.1 Access

The Contractor shall provide support, and not interfere with the CO, Contracting Officer’s Representatives (CORs), state, federal, and other designated personnel in the performance of their official duties. The Contractor shall provide access as soon as possible, but not to exceed one (1) workday after the request.

2.9.2 Non-Conformance

The Contractor shall identify root causes of non-conformances and shall control them through analysis, corrective actions, and preventive actions. The Contractor shall focus on eliminating the cause to prevent reoccurrence. The Contractor shall maintain records of non-conformities and actions taken. The Contractor shall correct and provide responses to all Government-identified non-conformances in accordance with (IAW) time frames specified by the CO. There are two types of non-conformances: Minor and Major.

2.9.2.1 Minor Non-conformance

A Minor Non-conformance is a non-conformance, which by itself does not adversely impact mission, safety of personnel and equipment, performance (quality), schedule (delivery), or cost. A Minor Non-conformance does not normally increase risk to the Government. Minor Non-conformances are typically low risk and are communicated through a Corrective Action Request (CAR) notice. First notices are issued for any identified non-conformance, second notices are issued for repeat non-conformances or failing to correct issues within a reasonable amount of time. Upon receipt of a non-conformance notification (first or second notice), the Contractor shall complete applicable sections and return it to the CO within time constraints directed by the CO in the notice. A formal corrective action plan may not be required for minor CAR notices.

2.9.2.2 Major Non-conformance

A Major Non-conformance is a non-conformance that adversely impacts (or has the potential to impact) mission, safety of personnel and equipment, performance (quality), schedule (delivery), or cost. A Major Non-conformance may also be a significant number of recurring minor non-conformances, which is an indication of inadequate preventive measures or actions and lowers the Government’s confidence that the Contractor can provide quality services on time and within costs. The CO will communicate Major Non-conformances using the CAR notice and will include a suspense date for the Contractor’s Corrective Action Plan. As a minimum, the Contractor’s Corrective Action Plan shall address:

• Actions taken to fix the immediate problem

• Root cause analysis of the problem to determine cause

• Corrective action on the cause of the problem

• Actions taken to prevent recurrence

2.9.2.3 Remedies for Non-Conformance

In accordance with the contract Inspection of Services clause, if any of the services do not conform to contract requirements, the Government may require the Contractor to perform the services again in conformity, at no increase in contract amount. This includes but is not limited to termination of Contractor personnel and recruitment of substitute personnel that are equally qualified within established timeframes. When the defects in services cannot be corrected by re-performance, the Government may:

• Require the Contractor to take necessary action to ensure that future performance conforms to contract requirements; and

• Reduce the contract price to reflect the reduced value of the services performed. This may include a reduction in the number of paid hours to reflect the total non-performance period.

If the Contractor fails to promptly perform the services again or to take the necessary action to ensure future performance in conformity with contract requirements, the Government may:

• By contract or otherwise, perform the services and charge to the Contractor any cost incurred by the Government that is directly related to the performance of such service; or

• Decrement invoice as stated in the PWS related to performance; or

• Terminate the contract.

3 Performance Requirements The following section specifies the Performance Objectives and Performance Elements for the contract. Acceptable Quality Level (AQL) is a tolerable variation in the execution of a PWS Standard.

3.1 Transition

The Contractor shall follow the transition plan submitted as part of the proposal and keep the COR fully informed of status throughout the transition period. Throughout the phase-in/phase-out periods, it is essential that attention be given to minimize interruptions or delays to work in progress that would impact the mission. The Contractor shall plan for the transfer of work control, delineating the method for processing and assigning tasks during the phase-in/phase-out periods.

3.1.1 Phase In

While the government owns the course material and classrooms, the Contractor shall transition all course materials and supporting documents within their possession no later than 30 days after contract award, and all classrooms within 60 days of contract award.

Deliverable:

A020: Transition Plan

3.1.2 Phase Out

At the conclusion of this contract, the incumbent contractor, when notified, shall work in good faith with the successor to determine the nature and extent of the phase-in/phase-out services required. The incumbent Contractor shall not seek reimbursement for phase in/phase out activities that occur within their associated award period of performance.

3.2 Associate Contractor Agreements (ACA)

The Contractor shall enter into Associate Contractor Agreements (ACA) for any portion of the contract requiring joint participation in the accomplishment of the Government's requirement. Liability for the improper disclosure of any proprietary data contained in or referenced by any agreement shall rest with the parties to the agreement, and not the Government.

3.2.1 ACA Costs

The Contractor shall include all costs associated with the ACA in their proposal. Agreements may be amended and associate contractors added or deleted as required by the Government during the performance of this contract.

3.3 533 TRS Directed Meetings/Events Contractor personnel shall attend 533 TRS newcomer orientation, all calls, and other major organizational related 533 TRS meetings deemed necessary by the 533 TRS Commander.

3.3.1 Kick-Off Meeting

The Contractor shall present a kick-off meeting to describe cost, schedule, and performance requirements and associated risks within 10 days of contract award. The briefing shall include a description of deliverables as well as key personnel roles and responsibilities.

Deliverable A007: Kick-Off Meeting A008: Meeting and Review Minutes

3.3.2 Program Management Review (PMR)

The Contractor shall present a PMR to the Government to describe cost, schedule, and performance requirements on a quarterly basis.

Deliverable A006: Program Management Review

3.3.3 End of Course Review (EOCR)

The Contractor shall present a EOCR to the 533 Commander (or designated Government representative) to describe/evaluate each course’s (list of courses in Attachment 3) execution and evaluation, and include lessons learned and desired areas of curriculum update. EOCR is a written report. The EOCR will be delivered NLT 30 days after each course completion (Threshold) (30 days Objective).

Deliverable A005: End of Course Review

3.4 Tasks

The contractor shall perform the following tasks. Tasks paragraph 3.4.1 through 3.4.4 all involve a combination of curriculum development and instruction (see section 3.5 below for details). Current and projected course offerings under these tasks are listed in Attachment 3: Course Catalog.

3.4.1 Guardian Fundamentals

Foundational service level knowledge and skills related to the Space Force and the Space Domain. As currently outlined, this maps to Phase I of Guardian Enlisted Training.

3.4.2 Space Discipline Specific Courses

Space mission area specific courses cover the individual SFSC courses.

3.4.2.1 Space Systems Operations.

Space Systems Operations covers training specific to the 5S SFSC.

3.4.2.2 Intelligence Operations

Intelligence Operations covers training for the 5I SFSC.

3.4.2.3. Cyberspace Operations

Cyberspace Operations covers training for the 5C SFSC.

3.4.3 Mission Integration, Exercises and Capstone Events

This task services three purposes. The first is to dive deeper into the 9 mission areas: Orbital Warfare, Space Electromagnetic Warfare, Cyber Warfare, Satellite Communications (SATCOM), Navigation Warfare (NAVWAR), Missile Warning/Missile Defense, C2-CSpOC, C2-NSDC, and Space Domain Awareness (SDA). Second, this task looks at integrate training events with the courses outlines in 3.4.2. These integrated events connect training days between two or more courses in 3.4.2. Third, this tasks culminates in running an integrated capstone exercise (ICE) where all USSF enlisted SFSCs come together to work through a introductory Space Flag exercise, similar to the USAF’s Intel School House Operation: Lone Star wargame.

3.4.4 Training Support

This task covers functions that are needed to support the execution of instruction or curriculum development.

3.4.4.1 Modeling and Simulation

This task involves using the government provided software and/or information to create realistic scenarios for use in student activities and exercises.

3.4.4.2. Student IT Support

This task is responsible for the inventory, maintenance, issuing and retrieving student IT equipment.

3.5 Course Development, Maintenance, Production, & Instructors The Contractor shall develop and maintain all course material while providing instruction for all courses in conjunction with the government team of mission area experts and instructors.

3.5.1 Course Lead

The Contractor shall appoint a designated Course Lead (for each course in Attachment 3) to serve as a focal point for each course. A contractor may be a Course Lead for more than one course.

3.5.2 Instructional Systems Design

The Contractor shall use course planning, analysis, design, development, implementation and evaluation IAW Instructional Systems Design principles as stated in DAF Handbook 36-2675 Info for Designers of Instructional Systems and any 533 TRS specific policies.

3.5.3 Course Development

The Contractor shall, when directed by the Commander, provide an analysis of requirement documents, recommend changes, develop learning objectives, a syllabus, and a lesson plan (aka Plan of Instruction or POI) for new blocks or courses. For clarity, updating and maintenance of existing course material or adding/deleting material to an existing block or course is not covered under 3.4.3 (instead reference: Course Maintenance). There will be no more than six such requests per year.

3.5.3.1 Agile Course Development

The Contractor shall provide agile course development services to iteratively deliver high-quality, engaging learning modules that meet the Government's evolving curriculum goals. The Contractor shall utilize agile methodologies to promote collaboration, transparency, and continuous feedback throughout the course development lifecycle. The goal is to deliver a flexible and adaptable solution that rapidly responds to changing needs and maximizes value for the Government.

3.5.3.2 Course Development Team

The Contractor shall work in conjunction with the Training Development/Curriculum Development Manager (CDM) (aka the Government team) to form a cross-functional Curriculum Development Teams (CDT) that prioritize and deliver content based on Government priorities to meet Service level requirements, ensuring frequent communication and demonstration of progress through reviews.

3.4.3.2.1 Continuum of Learning

[BMT and OTC] The seamless transition of trainees from BMT to GET, or integration with the Officer Training Course (OTC) requires collaboration between other Delta 1 units. The Contractor will support the Government team in preparing by recommending the proper placement of material in BMT vs GET curriculum. Additionally, support of the Government while they do analysis of course material connecting with initial and mission qualification training conducted by Combat Forces Combat at each specific Delta.

3.5.4 Agile Course Maintenance

The Contractor shall provide agile maintenance services for existing course materials to ensure their continued accuracy, relevance, and effectiveness in meeting evolving curriculum goals. The Contractor shall utilize agile methodologies to promote collaboration, transparency, and continuous feedback throughout the maintenance lifecycle. The goal is to maintain a high-quality, adaptable curriculum that effectively supports student learning and remains current with advancements in the field. The Contractor shall prioritize, and address identified issues, updates, and enhancements based on Government priorities and student feedback. The Contractor shall ensure frequent communication and demonstration of progress through reviews.

3.5.5 Course Production

The Contractor shall perform all tasks or activities required to accomplish the course objectives as stated in the Plan of Instruction (POI) to include course preparation, instruction, and student assessment and guidance. End Of Course Surveys (EOCS) and in-class evaluations conducted by the IS or will be used by the Government to determine the performance of instruction provided by the Contractor.

3.5.6 Course Instructors

The Contractor will provide the required number and specialties outlined in Attachment 4 in order to conduct classes independently or in conjunction with the Government instructors.

3.5.6.1 Instructor Qualification

The Contractor will provide personnel who have subject matter expertise and mission specific experience to be credible instructors in their courses.

3.5.6.2 Instructors Supporting Multiple Courses or Integrated Events Event though each contactor has an area of specialty and a course they are supporting, there are times when they may be asked to support one of the other courses either in curriculum development or instruction. In the near future, some course events or blocks will be integrated across courses.

Example: A GET-INTEL instructor could support a GET-SPACE instructor when the 5I0 Trainees are conducting a threat briefing to the 5S Trainees in the GET-SPACE course. Likewise, the end-of-course capstone/graduation exercise is an integrated training event where all three SFSCs from across the course will come together for a single integrated exercise.

3.5.6.3 Guest Instructing

There will be times when an instructor with specific experiences or knowledge may be asked to be a guest instructor in another course. This enables trainees to be exposed to a variety of mission areas and military experiences. If Guest Instructing, they will be backed up by the primary instructor if they aren’t qualified for that block of instruction in that course. Guest Instructing is crucial to enable the integration of events (3.4.6.2).

3.5.6.4 Multi-Course Certification

Specific contractor instructors will (within 6 months, but NLT 12 months of assignment) be asked to become certified in two courses. This is due to the integrated nature of the GET Initiative and the need to have the flexibility to utilize instructors to ensure uninterrupted training operations. This is also due to the fact that Phase 2 instructors will be used in Phase 3 to train Cohort in their area of expertise. Likewise, capstone/GRADEX in Phase 3 will be an “all-hands” events with instructors from across Phase I, II, and III participating.

3.5.6.4 Faculty development

Contractor instructors shall participate in faculty development, defined as the ongoing enhancement of teaching and professional expertise.

3.5.7 Classroom Management

The Contractor shall notify the designated instructor supervisor (IS) for the course verbally and through email, by close of business of all matters of student deficiency or unprofessional behavior, such as test failures, plagiarism, cheating, disruptive behavior, and/or tardiness.

3.5.8 Student Services

The Contractor shall work with 533 TRS & Delta 1 Government personnel to ensure all student information is properly captured and student records updated.

3.5.8.1 Learning Management System (LMS)

The Contractor shall use the designated Learning Management System (LMS) software for all courses.

3.5.8.2 Student Records

The Contractor shall update all LMS student entries within one business day.

3.5.9 Copyright

The Contractor shall maintain compliance with copyright practices to include instructional material, FAR data rights issues, Scientific and Technical Information policies, and International Trafficking in Arms practices.

4 Applicable Publications The Contractor shall comply with all documents listed below in the table of publications and referenced under paragraph 3.0, Performance Requirements. The Directive/Guidance (D/G) column indicates the extent of Contractor compliance with the publication that is prescribed by the PWS. A “D” in the column means the publication is a “directive publication,” that requires mandatory compliance by the Contractor. A “G” in the column means the publication is a “guidance publication.” Compliance with documents listed as guidance is the Contractors' option. If there is any conflict between the directive referenced in PWS paragraph 3.0 and the reference listed in the tables below, the reference in PWS paragraphs 3.0 takes precedence.

When directive chapters, paragraphs, appendices, attachments, etc. are referenced as a standard in this PWS, the standard shall be inclusive of all subordinate paragraphs unless specifically excluded. For example, if the PWS standard lists paragraph 1.2 as directive, and paragraph 1.2 has subparagraphs 1.2.1, and 1.2.2 those subparagraphs are directive as well.

Publications

5 Deliverables The Contractor shall provide deliverables as described in the PWS. The format and delivery schedule for deliverables shall be outlined in the table below. All Deliverable distribution shall be by an electronic method unless otherwise specified. Email documents in a Microsoft Office or Adobe Acrobat-compatible format. Submit drawings in a uniform electronic format.

Informal, recurring work products may not require a deliverable. These products are still required as described in paragraph 3 of the PWS.

If there is any conflict between the Deliverable reference in paragraph 3 of this PWS and the Deliverable specifics in the following table, paragraph 3 takes precedence. Days referenced shall be calendar days, unless otherwise noted. For recurring Deliverables, if the due date falls on a holiday or a weekend the Deliverable may be sent on the following business day. Contractor format is acceptable, unless a specific format is identified. The Contractor shall not include its name or any logos on any Deliverable except when a Contractor signatory is required by the Deliverable. The Contractor shall ensure all markings included in Deliverables are consistent with the contract’s requirements, to include copyright and proprietary markings addressed in the contract’s clauses.

Deliverable Table

PCO

Description: (Contractor format acceptable) As a minimum, the MSR shall detail:

· Executive summary detailing a self-assessment of the Contractor’s performance during the reporting period

· Major tasks/activity status

· Cost data for all CLINs

· Contractual issues or risks requiring Government resolution/mitigation

· Self-identified performance efforts exceeding the PWS requirements, along with how these efforts provide a benefit to the Government

· Self-identified performance deficiencies during the period; including the cause of each identified deficiency, corrective actions, the impact, and actions taken to preclude recurrence

· Deliverables submitted

A002

2.6.2

PCO

Description: Roster of all current personnel with an indicator of which require and possess a CAC or access badge (PWS 2.6), status of NDA completion (PWS 2.6.6), Instructor qualification and government approved work status and primary location (PWS 2.4.6).

A003

PCO

Description: (Contractor format acceptable) As a minimum, the Travel Report shall detail:

- The objectives and outcomes of the trip.

- The 5 Ws (Who, What, When, Where, and Why)

- Lesson learned

PCO

Security Manager

Description: Standard Form 312

PCO

Description: (Contractor format acceptable; written report) As a minimum, the EOCR shall detail:

· Describe/evaluate each course’s (list of courses in Attachment 3) execution and evaluation,

· Lessons learned

· Desired areas of curriculum update.

PCO

Description: (Contractor format acceptable) As a minimum, the PMR shall detail:

· cost, schedule, and performance relative to requirements

PCO

Description: (Contractor format acceptable) As a minimum, it shall detail:

· Cost, schedule, and performance requirements

· Description of deliverables (content, due date)

· Key personnel roles and responsibilities.

· Transition Plan

PCO

Description: (Contractor format acceptable) As a minimum, it shall detail:

· Cost, schedule, and performance requirements

· Description of deliverables (content, due date)

· Key personnel roles and responsibilities.

· Transition Plan

PCO

Description:

The Contractor shall report the number of FTE working on this contract effort annually. An email is sufficient.

Attachment 1 – Course Catalog

GET-PHASE 1

Provides foundational service level knowledge and skills related to the Space Force and the Space Domain.

Guardian Fundamentals (GET-FUN) In Phase 1 of Guardian Enlisted Training (GET), Guardian Fundamentals (GET-FUN) is the course that teaches foundational service…