PWS CGC Draft.docx

PERFORMANCE WORK STATEMENT (PWS) FOR

CIVILIAN GUARDIAN COURSE (CGC)

INSTRUCTION AND CURRICULUM DEVELOPMENT AND ITERATION

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 the SSC/ECZGI, 1050 E. Stewart Ave., STE 2025, Peterson SFB, CO 80914.

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.

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 of Work Statement

1 Introduction/Background The Officer/Enlisted/Civilian (O/E/C) Principles and Narratives set the foundation for how each member of the United States Space Force (USSF) contributes to space superiority. To support this structure, dedicated training programs were established for officers and enlisted personnel. However, a specific developmental course for Civilian Guardians—who comprise over one-third of the total force—was missing from this triad. This gap resulted in an inconsistent onboarding process, impacting the speed of mission integration and posing a risk to long-term civilian talent retention.

This gap led to the creation and execution of three prototype courses in Los Angeles, Colorado Springs, and the National Capital Region to test content and curriculum based on guidelines provided by USSF/S1 and STARCOM. The purpose of this Statement of Work is to implement the evolved and formalized training model developed from these prototypes: the Civilian Guardian Course (CGC).

1.1 Mission Overview

The mission of the Civilian Guardian Course (CGC) is to serve as the foundational developmental experience for new Civilian Guardians. It is designed to accelerate their transformation into mission-focused professionals, providing the operational stability, unit continuity, and depth of expertise necessary to support Joint Warfighting functions and U.S. National Security.

The CGC is structured to guide new Civilian Guardians into becoming fully integrated, space-minded, warfighting Guardians. The CGC begins by establishing a foundational space-minded perspective, requiring graduates to analyze the strategic environment to understand the 'why' behind the USSF mission. From there, it builds towards forging the Guardian identity by examining how USSF doctrine and Guardian warfighting ethos define their unique role and responsibilities and shape their impact as a civilian Guardian. The course then advances from theory to application, challenging students to apply concepts to solve complex, simulated operational challenges. By the conclusion of the course, each Guardian will have constructed a personalized development plan. This final step transforms the course from a singular training event into the starting point of a career-long journey, directly linking personal growth to USSF strategic needs and serving as a powerful tool for talent retention.

1.2 Scope

This effort shall be for the initial design and full development of CGC classes/lessons, corresponding instructor guides, and all student-facing training materials as described in this PWS. All contractor-developed materials, including but not limited to lessons, activities, templates, and assessments, are subject to formal Government review and approval prior to implementation. Delivered over a two-month period, CGC is a cohort-driven, interactive course that uses a blended learning model. The initial online phase shall consist of a 40-hour online portion that is a mix of 36 hours of asynchronous and 4 hours of synchronous online engagements and will primarily be developed to a Chapman Alliance Level 2 (Interactive) standard. The course culminates in a one-week, approximately 40-hour residential capstone focused on high-fidelity, performance-based activities, including instructor-led simulations. See Attachment 2: CGC Objectives and Proficiency Levels.

As part of CGC instruction and sustainment, the Contractor will be required to participate in all efforts from pre-execution through post-execution. The Contractor shall be responsible for the complete build-out and technical configuration of all course content within the Government-provided Learning Management System (LMS). Curriculum maintenance and updates will occur on a consistent and reoccurring schedule as part of this effort. Additionally, this PWS covers all required multi-media support and Instructional Systems Design (ISD) support for the performance period outlined in this PWS. The Government retains final authority on all course content, instructional methodologies, and learning activities.

2 General Requirements CGC is a 80 hour course taught over 2 months that will have two prototype offerings during OY4, it is composed of multiple online modules and culminates in an immersive engagement to tie in all aspects of the CGC. Further details of the course descriptions and needed work are listed in section 3 of the PWS. Iteration of course content and related materials will take place throughout the period of performance.

The Period of Performance is as follows:

OY4: 1 June 2026 – 24 Jan 2027

The development and phased rollout of the curriculum will be composed of five distinct modules (M0, M1, M2, M3, M4). The process is designed to be cyclical, involving an initial delivery for a validation pilot, followed by iterative refinement based on feedback.

A "Complete Deliverable Package" for each module is defined as all of the following components, fully integrated and operational on the designated Learning Management System (LMS):

· Student-facing content

· Instructor-facing content

· All associated feedback mechanisms for content feel and learning assessment (e.g., quizzes, surveys, assessments)

· Any and all supplementary or supporting materials

Schedule of Deliveries The project will adhere to the following phased delivery schedule.

Phase 1: Initial Delivery for Validation Pilot. The Complete Deliverable Package for each module shall be loaded on the LMS for the initial validation pilot no later than the dates specified below.

Phase 2: Iteration of content. The iteration process is intended to be continuous. For each module, the analysis of student feedback and subsequent content iteration shall begin as soon as that specific module's validation pilot is complete and feedback becomes available. This work should not be postponed until all modules have completed their initial pilot. An iterated and updated version of the Complete Deliverable Package, incorporating all feedback, shall be delivered by the dates specified below for pilot 2.

Phase 3: Final Revisions and Project Completion. Following the delivery of each iterated module during the second pilot, any subsequent changes and updates requested based on a final review must be completed. All project activities and final revisions are to be concluded by the end of the period of performance on January 24, 2027.

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 requirement. The Contractor shall manage the timeliness, completeness, and quality of problem identification, and resolution, as applicable. The Contractor shall provide corrective action plans, proposal submittals, timely identification of issues, and effective management of subContractors. 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 purposes 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. The MSR shall be reviewed via a monthly scheduled meeting with the Government stakeholders.

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. All briefings, policies, plans and other formal products the Contractor develops, reviews, and creates, will be reviewed and approved by the Government.

2.2.2 Contractor Program Manager (PM)

The Contractor shall have a single point of contact between the Government 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. The Contractor shall provide the name, telephone number (to include mobile telephone and pager, as applicable) and e-mail address of the Contract PM and alternate to the COR and CO within one (1) business day of contract award. In the event of replacement of the Contract PM, the Contractor shall notify the Contracting Officer’s Representative (COR) and CO, in writing, of such replacement at least 15 calendar days prior to a planned replacement and within 24 hours following an unplanned replacement.

The Contractor PM shall:

· Interface, as appropriate, with the Delta 1 Commander, CGC Director, CGC Deputy, and COR.

· Assess and resolve issues and provide recommendations as appropriate in support of the contract towards the mission owners.

· Ensure all Contractor personnel under their authority comply with all required training required by Delta 1 or higher authority.

· Ensure all Contractor personnel under his/her authority have the proper security clearances needed to instruct courses.

· If required, ensure full compliance with International Traffic in Arms Regulations (ITAR)

· Ensure all contract deliverables are submitted on the agreed schedule established by the COR and the Government CO.

· Ensure developers are competent to build the most recent developments in systems and employment concepts, maintain assigned lessons, and incorporate Government approved changes into all relevant course documentation.

· The Contractor POC shall coordinate ISD course requirements and ISD compliance with Delta 1 and associated ISD Contractor(s).

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 COR or CO prior to attending Government-provided training classes. Provided there is no cost to the Government, the Contractor may be eligible to attend Government-sponsored and Government-provided training to maintain proficiency in software, administrative procedures, or other areas. Additionally, provided there is no cost to the Government, the Contractor may be eligible to attend third-party-provided off-site seminars and classes.

2.2.4 Contractor Identification

Contractor employees shall clearly identify themselves as “Contractors” at all times, in all communications and representations, including in the workplace, at meetings, in conversations, telecommunications, mail, electronic mail (e-mail), and faxes, whether with Government personnel, other Contractor personnel, or with the public. Contractor personnel shall wear a readily visible badge that clearly identifies them as Contractor employees.

Deliverable:

A002 – Contractor Personnel Roster

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. The Contractor shall ensure the labor categories, labor rates, and man-hours utilized in the performance of each PWS line item issued here under will be the minimum necessary to accomplish the task. The Contractor shall provide the necessary resources and infrastructure to manage, perform, and administer the contract.

Excellent Soft skills; familiarity with engaging multiple DoD agencies / organizations (e.g., SMC, HQ USSF, NRO, Intelligence Community (IC) as well at multiple levels (e.g., Section, Division,

· Active Sensitive

· Project Management Professional Certification or 6 years of experience as a Program Manager.

· 3 years of experience with creative design software tools building 2D/3D animations with motion graphics with video production, special effects and sound design while using Adobe Creative Cloud Suite and/or Autodesk’s 3DS Max, Maya, or similar

· Knowledge of instructional design, development tools, and delivery methodologies.

· Research and recommend cutting edge technologies and tools to enhance design and development practices

experience in related field

· Active Sensitive

· 3 years of experience in curriculum/lesson development and instruction

Qualification Substitutions

experience may be substituted for a Bachelor’s Degree

Degree

for a Doctorate’s Degree

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 impact to the Government is minimal. Once the Contractor knows an employee will no longer support the requirement, the Contractor shall provide written documentation to the CO and COR within three (3) business days. In this notification, the Contractor shall include the date and time 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 30 calendar days unless approved in writing or otherwise directed in advance by the CO (e.g. a grace period associated with new awards and PWS modifications increasing the number of personnel on a task order).

2.3.2 Removal of Personnel at Government Request

The Government may request removal (permanent or temporary) of personnel for security, safety or health reasons.

2.4 Location and Hours of Work

Curriculum Development: The primary place of performance for all tasks related to curriculum development is the contractor's own facility, located within the general vicinity of Colorado Springs, Colorado. The contractor is responsible for providing its own facilities and resources for this phase of the work.

CGC duty hours shall normally consist of one eight (8) hour shift, Monday through Friday, except US Federal Holidays and STARCOM family days. Any work schedules that deviate from the normal duty hours will be coordinated with the Contracting Officer's Representative (COR).

The Contractor shall generally support a normal work week of 40 hours per week. Core hours of work are from 0900 to 1500 daily. The standard core working hours for the contractor are 0900 to 1500 daily. Recognizing that virtual instruction will support a global student audience, the Contractors will flex their hours or work schedules to accommodate various time zones (maximum slip left/right +/-3 hours).

The development and maintenance of the curriculum shall be iterative, allowing for frequent updates and feedback integration following each stage of pilot execution to ensure the curriculum remains current.

No overtime hours with associated additional pay are authorized.

2.4.1 Building Access

The Government will provide Contractor personnel access (escorted or unescorted) to office space as needed when meeting with Civilian staff and during the in-person course execution phases. Access to Government facilities, documents and systems will be in accordance with the DD Form 254.

2.4.2 Morale Events

There may also be occasions when Contractors are invited to participate in morale and recreational activities (e.g., holiday parties, golf outings, sports day, and other various social events). Under these circumstances, Contractor employees shall comply with individual company policy in accordance with company compensation system. Because the Government does not have an employer/employee relationship with Contractor employees, it is not authorized to grant administrative leave or expend Government resources to compensate Contractor employees for hours expended on activities not included in the PWS. The Contractor shall insure all performance requirements are met in accordance with this PWS.

2.4.3 Closures

For closures affecting the availability of the Government site (e.g., weather closures, a National Day of Mourning, etc.), the Government will notify the Contractor through normal means such as the Snow Call Line and local news outlets, or via email from the COR or CO. During such closures, Contractor personnel may telework if they have a COR-approved telework request in place.

2.4.4 Teleworking

“Teleworking” is defined as authorization for a Contractor employee that normally works at the Government location, to work at an alternate location (at the employee’s residence or other Contractor location) either permanently or temporarily. “Contractor location” is defined as Contractor-approved place of performance for certain employees that is not an employee’s residence or Government location. The COR may approve Contractor personnel to telework on a case-by-case basis. The Contractor shall obtain COR approval prior to any teleworking. To obtain approval for teleworking, the Contractor shall submit a teleworking request with appropriate rationale to the COR in writing. This request shall include the Contractor’s [“lead’s”, “Project Manager’s”, “Task Lead’s”, etc.] approval, as well the primary Government customer’s approval, if different than the COR, when the request is submitted to the COR for approval. If approved for teleworking, the Contractor shall support Government core hours in the same manner they would if they were working at a Government location. Although the Government may allow the Contractor to use Government computer resources for teleworking, all other teleworking expenses for internet, telephone connectivity, and other equipment services are the responsibility of the Contractor. Use of Contractor facilities for classified curriculum development is authorized only for those locations that possess the applicable facility clearance. Authorized teleworking does not abrogate the Contractor’s requirement to protect information IAW applicable requirements in this PWS, the DD Form 254, or other Government regulations applicable to this contract.

2.5 Travel / Temporary Duty (TDY)

Travel is not required for work performed under this PWS.

2.6 Security and Safety

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

Every Contractor employee shall obtain and possess a DoD CAC and an Access ID Badge as required. Contractor shall use the card IAW AFFARS 5352.242-9001. Upon favorable review .and initiation of the Personnel Security Investigation (PSI) to establish the suitability of an employee for the job and the approval for temporary Automated Information System (AIS) access pending final adjudication of the PSI, the Contractor shall submit to a Contractor’s onsite System Manager’s request for the DoD CAC and ID Badge.

The Contractor shall ensure employees who terminate their services shall immediately return any Government identification/access badges issued in support of this contract.

2.6.1 DD Form 254

Course material will be unclassified. No DD Form 254 will be required.

2.6.2 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 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 and HQ Space Operations Command’s countermeasures and measures. 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.3 Controlled Unclassified Information (CUI)

The Contractor shall safeguard all information provided and marked as CUI via this contract IAW DoD Instruction (DoDI) 5200.48. 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.

2.7 Manpower Reporting

In accordance with FAR 52.204-14 Service Contract Reporting Requirements, the Contractor shall report all Contractor labor hours (including subcontractor labor hours) required for performance of services provided under this contract via a secure data collection site. The Contractor shall fill in all required data fields at the data collection site. Use the following web address: www.sam.gov.

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

2.8 Documentation

The Contractor shall make all information and documentation generated or maintained (to include Government-furnished documents) by this contract available for Government review upon request for the duration of the contract. Request may cover the range of activities under this PWS. The Contractor shall generate and maintain all such documentation in an electronic, editable (where appropriate) format. Contractor-generated format is acceptable, unless otherwise noted by this PWS.

The Contractor shall provide responses to requests for information. These requests are in addition to Deliverable submissions and other documentation that is available for review by request. Requests may cover the range of activities under this PWS.

2.8.1 Documentation Rights

The Government has unlimited rights to data for all deliverables developed under this PWS. The Contractor shall not use any materials pertaining to this contract for business development or any other Contractor purposes; however, the Contractor is authorized to include summary performance information in proposals to be submitted to the Government to satisfy past performance information requirements.

All products developed and produced by the Contractor in the performance of this PWS are the property of the Government, and this could include software, electronic files, hard copy documents, etc. Rights to all documentation are governed by Defense FAR Supplement (DFARS) 252.227-7032, Rights in Technical Data and Computer Software.

2.8.2 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 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 Quality Control

The Contractor shall develop, implement, and maintain a comprehensive inspection system that assures compliance with all requirements of this contract.

Deliverable:

A004 Quality Control Plan The Contractor shall develop a Quality Control Plan (QCP) that demonstrates how the Contractor shall maintain an inspection system acceptable to the Government covering the services under this contract to include deliverable requirements. The QCP will include procedures to identify, prevent, and ensure non-recurrence of defective services that inhibit or negatively impact the Delta 1 missions.

The Contractor's QCP is the means by which the contracting company providing the product or services reaffirms internally that the work complies with the requirement of the contract.

The QCP shall demonstrate the Contractor’s documented processes and procedures to monitor and control:

· Objectives for Services Summary Items

· Subcontractor relationships

· Contractor and subcontractor invoicing

· Non-conformances

The draft finalized QCP will be provided to the government within 30 days after award for potential acceptance and review. It will be accepted, if deemed adequate to prevent or correct defective services as described above. The CO may notify the Contractor of required modifications to the plan during the period of performance. The Contractor then shall coordinate suggested modifications and obtain acceptance of the plan by the CO. Any modifications to the program during the period of performance shall be provided to the Contracting Officer for review no later than 10 working days prior to effective date of the change. The QCP shall be subject to the Government's review and approval. The Government may find the QCP "unacceptable" whenever the Contractor's procedures do not accomplish quality control objective(s). The Contractor shall revise the QCP within 10 working days from receipt of notice that QCP is found "unacceptable."

The Government shall monitor the Contractor's performance under this contract in accordance with the Government's Quality Assurance Surveillance Plan (QASP). The QASP is a Government-only document and will not be released to the Contractor.

In addition to the QCP, the Contractor shall provide a Monthly Status Report (MSR) covering activities of the preceding month. The Contractor shall provide the MSR no later than 10 business days after the end to the preceding month.

2.10 Performance Evaluation

The Delta 1 Contracting Officer Representative, IAW the Contracting Officers direction, will oversee the execution of performance on behalf of the Commander.

The process used is the Quality Assurance Surveillance Plan (QASP), which provides a documented process for surveilling the contractor's actual performance and comparing that to the technical requirements of the contract. The QASP identifies what is going to be inspected, the inspection process, and who will do the inspecting. The QASP identifies and describes the roles and responsibilities for implementing and maintaining the key elements of contract performance management.

The contractor is responsible for implementing and delivering performance that meets contract standards using its Quality Control Plan (QCP), as required by the PWS. The QASP provides the structure for the government's surveillance of the contractor's performance to assure that it meets contract standards. The QASP is not part of the contract nor is it intended to duplicate the contractor's QCP. The QASP is NOT releasable to the Contractor. “The Services Summary (SS) is releasable to the contractor but the QASP is an internal Government document.” [SOURCE AFI 63-138, para 6.2]

The QASP will contain the surveillance schedule in Enclosure 1. AFI 63-138, para 2.10.5 requires the Program Manager to review, approve, and sign surveillance schedules; the incorporation of the surveillance schedule into the QASP, and the PM signature of this document constitutes approval of the surveillance schedule. The Government has the right to inspect all services required by the contract to the extent practicable at all times and places during the term of the contract; the surveillance schedule (Enclosure 1) is only the minimum level of surveillance.

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

Access. The Contractor shall permit the CO or authorized representative access to all work areas, records, and data used in the performance of the contracted services. 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.

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.

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.

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 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.11 Government Furnished

The Government will make available the materials, communications capability, and information for the duration of this contract is identified in Attachment 1 for use by the Contractor in the performance of this contract.

2.11.1 Government Furnished Resources

Hot desks with Government equipment (remaining under Government control and custody) will be made available for visiting developers on an as-needed basis. Classroom facilities for the prototypes will be arranged and furnished by the Government. Any equipment is considered incidental to performance location.

2.11.2 Government Furnished Information (GFI)

Government staff personnel will be available for technical exchanges with the Contractor. Government personnel will provide technical input, answer questions, review and approve completed work, and provide feedback regarding Contractor efforts. The COR is the primary source of technical guidance for this PWS.

All GFI in contractor possession, regardless of how received, is subject to DFARS 52.227-7025 Limitations on the use or disclosure of government-furnished information marked with restrictive legends. GFI will be listed on Attachment 1.

Deliverable:

A005 Government Furnished Property, Resources, Information list An initial Government Furnished Property, Resources, and Information list will be provided within 30 days of contract award. Any changes to this list must be reported within 3 business days. The Government Furnished Property, Resources, Information list must include all applicable identifying information as required and all required IT identifying information when assigned.

2.11.3 Materials and Other Direct Costs (ODC)

ODC includes travel and material support of Delta 1 for the execution and curriculum development and maintenance of CGC. ODCs may occur in performance of contract and are to be reviewed by the COR prior to them being incurred to have government payment. The following contains broad examples of categories of Equipment and Materials that may be purchased as ODCs by the contractor in support of the requirements in this PWS.

Specialized Hardware Needs for Commander’s Travel Team

Unique requirements

DL/LMS support as applicable

Camera’s and Camera Equipment

ODC materials purchases All open market materials purchases must be approved in advance by the COR. Contractor shall submit invoices for these purchases and provide records to the COR. For material purchases exceeding $10,000, the Contractor shall obtain review and concurrence, from both the COR and the CO prior to purchase. In addition, the Contractor shall provide at least three quotes to the COR and the CO for determination of reasonable cost and best technically acceptable offeror that meets the Government need. If the contractor recommends a solution other than the lowest cost, detailed rationale shall be provided to the Government. The Contractor shall not break up purchases to meet this threshold. All receipts for charges on the ODC CLIN shall be submitted with the invoice when billed.

ODC Equipment All open market equipment purchases must be approved in advance by the COR. Contractor shall submit invoices for these purchases and provide records to the COR. For equipment purchases exceeding $10,000, the Contractor shall obtain review and concurrence, from both the COR and the CO prior to purchase. In purchasing equipment, the contractor shall ensure that all DoD and service IT equipment network equipment policies are followed and that the equipment is purchased from a qualified vendors and is approved for use on the applicable network. In addition, the Contractor shall provide at least three quotes to the COR and the CO for determination of reasonable cost and best technically acceptable offeror that meets the Government need. If the contractor recommends a solution other than the lowest cost, detailed rationale shall be provided to the government. The Contractor shall not break up purchases to meet this threshold. All receipts for charges on the ODC CLIN shall be submitted with the invoice when billed.

Deliverable:

A006 ODC Funds Status Report The Contractor shall provide a monthly itemized listing of purchased items to the COR via the ODC Funds Status Report so they can be added to internal Government tracking list, as applicable.

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.

The Contractor shall provide required tools, materials, and labor necessary to support and execute the in-residence courses required by CGC. Technical efforts required by this contract include the maintenance and instruction of in-residence covering key CGC discipline subject matter areas utilizing the ISD Process.

Performance Standards:

Upon mutual agreement between the GOV and the Contractor on the finalized CDG to support execution of CGC, the following performance standards will be implemented.

a) Standard: Course maintenance will utilize the ISD process and guidance as specified within the 319 CTS Curriculum Development Guide (CDG).

b) Standard: Contractor course lessons and instructor guides will be developed IAW 319 CTS OI and 319 CTS CDG. These lessons are developed in accordance with the Master List of Objectives for the CGC. See Attachment 2: CGC Objectives and Proficiency Levels.

Deliverable:

A007 – Monthly CGC and MQT Instruction Status Report. All associated contract performance requirements are to be included in the monthly status report. During the curriculum development the report will include progress updates. During the piloting stage, the report will include changes made or not made based on feedback of the content.

3.1 Associate Contractor Agreements (ACA)

Upon contract award for follow-on support, if the incumbent is not selected, the Contractor shall enter into Associate Contractor Agreements (ACA) for any portion of the contract requiring joint participation in the accomplishment of the Government’s requirement. The Contractor shall also have an ACA with any other Contractor that will participate as part of in-person portion as well as class scheduling for those classes within the same stage.

The agreements shall include the basis for sharing information, data, technical knowledge, expertise, resources, or any combination thereof, which shall ensure the greatest degree of cooperation for the development of the program to meet the terms of the contract.

The ACA shall:

1. Identify the associate contractors and their relationships.

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

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

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

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

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

7. A copy of such agreement shall be provided to the PCO for review before execution of the document by the cooperating contracts.

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

However, the Government may assist the Contractor in the event of non-responsiveness from an associate contractor.

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.

All costs associated with the agreements are included in the negotiated cost of this contract. Agreements may be amended and associate contractors added or deleted as required by the Government during the performance of this contract.

3.2 Civilian Guardian Course Descriptions and Requirements

The CGC is structured to guide new Civilian Guardians into becoming fully integrated, space-minded, warfighting Guardians. The CGC begins by establishing a foundational space-minded perspective, requiring graduates to analyze the strategic environment to understand the 'why' behind the USSF mission. From there, it builds towards forging the Guardian identity by examining how USSF doctrine and Guardian warfighting ethos define their unique role and responsibilities and shape their impact as a civilian Guardian. The course then advances from theory to application, challenging students to apply concepts to solve complex, simulated operational challenges. By the conclusion of the course, each Guardian will have constructed a personalized development plan. This final step transforms the course from a singular training event into the starting point of a career-long journey, directly linking personal growth to USSF strategic needs and serving as a powerful tool for talent retention.

The Contractor shall provide all personnel necessary to develop the curriculum which will consist of a blended learning model, beginning with an online portion that is a mix of 36 hours of asynchronous and 4 hours of synchronous online engagements and ending with a one week, 40-hour, immersive in-person engagement.

Contractor developers operate as subject matter experts (SMEs) and play a critical role in courseware development, validation, maintenance, and instruction. They possess a deep understanding of the subject or tradecraft that will ultimately be instructed, and as such, they are considered the definitive expert in this regard. In the course design process, they coordinate with the CGC Gov team in validating the accuracy and relevancy of course scope and sequence, learning outcomes, samples of behavior, learning experiences instructional media, technology integration, mission planning scenarios, and desired levels of learning. These personnel will advise the Government on any course changes or modification.

The contractor's responsibility is to build lessons and activities that teach and assess at the Enabling Learning Objective (ELO) level, with the understanding that successful completion of all ELOs will result in the achievement of the Terminal Learning Objective (TLO).

Online Foundation The online foundation (Modules 0, 1, 2, and 3) is a 40 hour mix of 36 hours of asynchronous and 4 hours of synchronous (the 36 hours includes time for students to complete assignments). It is designed to provide students with the foundational knowledge required for advanced application. During this phase, students will analyze the strategic space environment, learn core USSF doctrine, and use digital tools like AI to collaboratively produce analytical products. This phase culminates in each student developing a complete first draft of their 18-month career development plan, ensuring they arrive at the residential portion fully prepared to move from theory to practice.

E-Learning Development Standards: All asynchronous online courseware shall be developed in accordance with the Chapman Alliance learning levels framework. The Contractor shall employ a blended-level approach to ensure a balance of instructional effectiveness and fiscal responsibility.

Level 2 (Interactive) as the Primary Standard: The majority of the instructional content shall be developed to a Level 2 standard. This includes the use of interactive elements such as click-to-reveal, drag-and-drop, simple animations, and scenario-based knowledge checks to explain key concepts and principles. All major asynchronous learning activities shall be designed at this level to foster an engaging, active learning experience.

Level 1 (Basic) for Supporting Content: The use of Level 1 is authorized and appropriate for the delivery of static content, such as required readings, course documents, instructor video lectures, and the low-stakes, automated "Self-Checks for Understanding" quizzes.

In-Person Application The in-person application is a culminating, final synthesis of all learning experiences executed over a one-week residential capstone. The goal is to forge foundational knowledge from online learning into practical professional skills.