Attachment 01 HADES Basic IDIQ PWS 20260820.pdf

UNCLASSIFIED

i

UNCLASSIFIED

HYBRID ARCHITECTURE AND DEVELOPMENT FOR

EXPERIMENTAL SYSTEMS (HADES) SERVICES

BASIC IDIQ

PERFORMANCE WORK STATEMENT (PWS)

FA8809-26-R-B002

SPACE SYSTEMS COMMAND (SSC)

SYSTEMS DELTA 89 (SYD89)

INNOVATION AND PROTOTYPING DELTA (SD)

INNOVATION AND PROTOTYPING DIVISION GROUND (SDG)

KIRTLAND AFB, NM

24 JULY 2026

Distribution Statement A. Approved for public release. Distribution is unlimited.

Destruction Notice: For unclassified, limited documents, destroy by any method that will prevent disclosure of the contents or reconstruction of the document.

ii

UNCLASSIFIED

REVISION HISTORY

Revision Date Version Description

1 1/15/2026 1.0 Initial Basic IDIQ PWS

2 1/28/2026 2.0 Initial published Basic IDIQ PWS to SAM.gov

3 2/10/2026 3.0 Aerospace revision, HADES Basic IDIQ PWS

4 4/20/2026 3.4 Aerospace revision, HADES Basic IDIQ PWS

5 7/24/2026 3.8 Aerospace revision, HADES Basic IDIQ PWS w/SDG input iii

UNCLASSIFIED

Innovation and Prototyping Division Ground

SSC/SYD89/SDG

Kirtland AFB, NM

7/24/2026

(U) Hybrid Architecture and Development for Experimental Systems

(HADES) Services

Basic IDIQ

Performance Work Statement (PWS)

(U) Contents

(U) Contents .................................................................................................................................................................iii

1. (U) PURPOSE AND OBJECTIVES

1.1 (U) Purpose

1.2 (U) Objectives

2. (U) BACKGROUND

2.1 (U) Background

3. (U) SCOPE

3.1 (U) Tasks Included in the Task Order (TO) PWS’s

3.2 (U) Outputs and Deliverables

3.3 (U) Security Clearance Requirements

3.4 (U) Reserved

3.5 (U) Contractor Identification

3.6 (U) Reserved

4. (U) ACCESS TO DEPARTMENT OF THE AIR FORCE COMPUTER SYSTEMS

4.1 (U) System Access and Compliance

5. (U) BASIC SERVICES

5.1 (U) Contract Transition

5.1.1 (U) Phase-In

5.1.2 (U) Phase-Out

5.2 (U) Support Services

5.2.1 (U) Program Management

5.2.2 (U) Cost Management

5.2.3 (U) Information Management

5.2.4 (U) Security and Data Handling Management

5.2.5 (U) Quality Control

5.2.6 (U) Risk Management

5.2.7 (U) Training and Certification

5.2.8 (U) Configuration Management

5.2.9 (U) Procurement, Logistics, and Lifecycle Management

5.2.10 (U) Concept Development

5.3 (U) Grounds System Services

5.3.1 (U) Ground System Engineering and Design

5.3.2 (U) Ground System Development

5.3.3 (U) Ground System Integration

5.3.4 (U) Ground System Sustainment

5.3.5 (U) Ground System Decommission, Disposal, and/or Transfer

5.4 (U) Facility Services iv

UNCLASSIFIED

5.4.1 (U) Power Distribution and Resiliency Support

5.4.2 (U) Heating, Ventilation and Air Conditioning Support

5.4.3 (U) Facility and Furniture Maintenance

5.4.4 (U) Network Infrastructure Support

5.4.5 (U) Space Optimization and Layout

5.5 (U) Software Support Services

5.5.1 (U) Software Setup

5.5.2 (U) Software Development

5.5.3 (U) Software Configuration

5.6 (U) Other Activities

5.6.1 (U) Communication Security (COMSEC) and Cryptographic Support

5.6.2 (U) Cybersecurity

5.6.3 (U) Defensive Cybersecurity Operations (DCO)

5.7 (U) Special Studies and Recommendations

5.7.1 (U) Assessment of Current Capabilities

5.7.2 (U) Development of Courses of Action (COAs)

5.7.3 (U) Study Report, Analysis, and Rationale

5.7.4 (U) Reserved

5.7.5 (U) Coordination and Stakeholder Engagement

6. (U) GOVERNMENT FURNISHED PROPERTY/GOVERNMENT FURNISHED SERVICE. .............. Error!

Bookmark not defined.

Appendix A – (U) APPLICABLE PUBLICATIONS AND FORMS

Appendix B – (U) ENABLING REQUIREMENTS FOR GOVERNMENT PROGRAM CONTRACTS

Appendix C – (U) ASSOCIATE CONTRACTOR AGREEMENTS

Tables

No table of figures entries found.

Copy no. ____ of ____ copies

Innovation and Prototyping Division Ground

SSC/SYD89/SDG

Kirtland AFB, NM

7/24/2026

(U) Hybrid Architecture and Development for Experimental Systems

(HADES) Services

Basic IDIQ

Performance Work Statement (PWS)

1. (U) PURPOSE AND OBJECTIVES.

1.1 (U) Purpose

The purpose of this Performance Work Statement (PWS) is to define the requirements for the Hybrid Architecture and Development for Experimental Systems (HADES) Indefinite Delivery/Indefinite Quantity (IDIQ) contract. This contract is designed to support the rapid design, development, integration, testing, and sustainment of prototype and operational satellite ground systems, satellite operations centers (SOCs), and related support services.

This effort directly supports the Innovation and Prototyping Division Ground (SDG) by maintaining mission readiness, advancing ground infrastructure, and ensuring the seamless integration of experimental and operational systems. Activities under this contract are primarily concentrated at the Research, Development, Test, and

Evaluation (RDT&E) Support Complex (RSC) aboard Kirtland Air Force Base, New Mexico, with the flexibility to extend to other contractor or mission partner facilities as necessary.

The organization’s goal is to accelerate mission design, ground integration, launch and on-orbit operations, ground system testing, and the rapid fielding of innovative solutions. Through the HADES program, these efforts ensure the reliable and rapid delivery of low-cost access to space capabilities that support the warfighter and align with national defense priorities.

1.2 (U) Objectives

The objective of this PWS is to set contractor requirements for the engineering, sustainment, support, development and integration of RSC’s satellite ground systems and operations centers. This includes maintaining system availability, supporting high-tempo and rapid-fielding operations, and enabling mission success through innovative solutions the seamless execution of experimental and operational systems.

Specifically, the contractor shall:

1. Collaborate with stakeholders, including Prototype Operations I (POPS-I) personnel, space vehicle contractors (SV Ctrs), and external mission partners, to meet mission objectives.

2. Provide engineering and sustainment services to maintain system reliability and readiness.

3. Support high-tempo mission operations, ensuring quick adaptation to dynamic mission requirements.

4. Ensure mission systems are integrated effectively, advancing experimental systems into operational capabilities.

5. Implement innovative, cost-effective solutions in alignment with DoD objectives and policies.

The contractor is responsible for meeting all clarified and specified requirements directly related to the successful execution of this effort.

2. (U) BACKGROUND

This section provides essential context for the project or effort outlined in the Performance Work Statement (PWS).

2.1 (U) Background

The Research, Development, Test, and Evaluation (RDT&E) Support Complex (RSC) serves as a critical multi-mission support facility for enabling and sustaining Department of Defense (DoD) space operations. The RSC provides the infrastructure and expertise necessary to support experimental, demonstrative, and prototype satellite missions, space vehicles, satellite ground control systems, tracking systems, and related technologies.

The Research Development Space and Missile Operations (RDSMO) program is central to these activities. Managed by Space Systems Command’s (SSC) Innovation and Prototyping Division Ground (SDG) and executed by the

Prototype Operations Branch (SDX), the RDSMO program delivers the expertise, infrastructure, and processes required to execute satellite and ground system engineering and operations. RDSMO’s operations require flexible and dynamic timelines, and the Contractor may be expected to deliver functional ground systems in line with mission-specific Task Orders (TOs)

The contractor operates as a mission partner to the Government, collaborating with stakeholders including customers, Federally Funded Research and Development Centers (FFRDCs), and associate contractors. The RSC provides reliable, low-cost access to ground systems and resources for 24x7 spacecraft operations, supporting both the scientific and space acquisition communities. Satellite ground systems supported at the RSC use a wide range of technologies, including commercial software with on-premises hardware, contractor-developed mission-unique software, and cloud-based environments. This diverse technical portfolio ensures the RSC remains adaptable to current and future DoD mission needs.

The satellite ground system, SOCs, and support services procured through this contract shall occur primarily, but not solely, at the RSC located at Kirtland Air Force Base in Albuquerque, New Mexico. Contractor personnel will be required to work onsite as needed to fulfill mission objectives. Contractor-occupied spaces within Government facilities must be clearly identified with contractor-provided signage or nameplates. Access to classified areas and equipment will be coordinated through the Government, and contractors must comply with all facility access protocols. Additional contractor or mission partner facilities may be used as needed to achieve mission objectives.

3. (U) SCOPE.

The HADES IDIQ provides comprehensive engineering, development, integration, sustainment, and operational support services for prototype and operational satellite ground systems, satellite operations centers (SOCs), and related infrastructure at the Research, Development, Test, and Evaluation (RDT&E) Support Complex (RSC) at

Kirtland Air Force Base. The contract supports high-tempo, rapid-fielding operations with flexible task order execution to maintain mission readiness, advance ground infrastructure, and enable seamless integration of experimental and operational space systems. Activities encompass facility services, ground system services, software support, cybersecurity, logistics, and lifecycle management to deliver reliable, low-cost access to space capabilities supporting the warfighter.

3.1 (U) Tasks Included in the Task Order (TO) PWS’s

The contractor shall accomplish all tasks specified in each TO PWS. For each task order issued by the Government, the contractor shall appoint a dedicated Task Order Manager to oversee all activities and serve as the primary point of contact with the Government. The Task Order Manager is responsible for ensuring effective task order execution, maintaining timely communication with Government stakeholders, and ensuring alignment with mission objectives.

3.2 (U) Outputs and Deliverables

In rendering support to the identified tasks, outputs may take the form of information, advice, opinions, alternatives, analyses, evaluations, recommendations, reports in the form of deliverables (Contract Delivery Requirements List), training, and/or services to complement the Government’s technical expertise in accomplishing its mission.

3.3 (U) Security Clearance Requirements

All work activities require varying security clearances (Secret, Top Secret, and Top Secret/Sensitive Compartmented

Information) as defined in the DoD Contract Security Specification, DD Form 254. Every person assigned to the

HADES contract is required to obtain at least a Secret clearance. Each person requiring access to the space ground control systems to perform their work must obtain at least a Top-Secret clearance with Sensitive Compartmented

Information eligibility.

3.4 (U) Reserved.

3.5 (U) Contractor Identification

Contractor personnel and their subcontractors must identify themselves as contractors or subcontractors during meetings, telephone conversations, in electronic messages, or correspondence related to this contract

3.6 (U) Reserved.

4. (U) ACCESS TO DEPARTMENT OF THE AIR FORCE COMPUTER SYSTEMS.

4.1 (U) System Access and Compliance

Contractor-occupied facilities, on Government Performance under this contract requires access to Department of the

Air Force computer systems, including stand-alone and networked environments. Compliance with Air Force

Instruction (AFI) 33-119 and AFI 33-202V1 is mandatory. Such access requires, at a minimum, a National Agency

Check or Entrance National Agency Check with Inquiries (NACI) in accordance with DoD 5200.2-R, Personal

Security Program, and HSPD-12.

5. (U) BASIC SERVICES.

The contractor shall perform in the work areas listed in this section. TOs will be issued with identifiable tasks that must be completed within a specified period. The contractor shall perform all tasks related to the engineering, development, integration, sustainment, and management of the HADES system as defined in this PWS and as specified by subsequent Task Order(s).These requirements are applicable to the basic effort and all options, if exercised.

The PWS line items listed in this section specify the work required by the contractor. Not all line items may apply to every task order, project, or mission. Applicable PWS line items will be specified in detail in each task order PWS based on specific mission or project requirements. Individual task orders may expand, extend, clarify, and/or establish additional standards within the scope of this PWS and as related to the tasks below.

The Support Services TO will include the non-mission-specific support functions for overall contract management.

The individual mission TOs will include mission-specific support functions.

5.1 (U) Contract Transition

Intent: Continuity of service is of the utmost importance through the phase-in and phase-out periods of this contract. Interruptions or delays to the work will cause negative impacts to the mission. It is essential that attention be given to minimizing these impacts. The contract requires maximum cooperation between the incumbent and successor contractors to minimize disruptions while ensuring all work receives adequate attention during the transition. The incumbent contractor maintains full and sole responsibility for executing the requirements of the contract through the last day of the transition period.

5.1.1 (U) Phase-In

The successor contractor shall provide for a smooth and efficient transfer of responsibilities during the designated

60-day phase-in period. The successor contractor shall develop plans for assumption of contract requirements. The contractor must provide for an orderly transition of work acceptance and accomplishment so that impacts to mission are minimized. The successor contractor shall plan the phase-in tasks and work with the incumbent contractor to finalize a phase-in plan.

The successor contractor shall ensure that by the conclusion of the phase-in period, all contractor personnel will be able to perform the duties outlined in the TOs issued at contract start, to include procurement of appropriate security clearances, facilities access, system accounts, and any necessary certifications.

5.1.2 (U) Phase-Out

The incumbent contractor shall cooperate with the successor contractor and the Government through the end of the current contract to facilitate a smooth transition. The incumbent contractor maintains overall contract responsibility until successful transfer to the successor contractor, as determined by the Government. The incumbent contractor shall plan the phase-out tasks and work with the successor contractor to finalize a phase-out plan.

5.2 (U) Support Services

Intent: Support services are the functions necessary for overall contract management and are not necessarily mission specific. Non-mission-specific support service requirements will be specified in the Ground Supprt TO

PWS. Mission-specific support service requirements will be specified in each TO PWS.

5.2.1 (U) Program Management

Intent: Have and implement a process to accomplish program objectives for development, production, and sustainment to meet the user’s operational needs. Will be accountable for credible cost, schedule, and performance reporting to the Government.

5.2.1.1 The contractor shall be responsible management of contractor and subcontractor teams to reflect

SD’s mission and commitment to customer satisfaction.

5.2.1.2 The contractor shall support high-tempo operations, as necessary, and may require off-hour support, in which case the contractor may need to adjust personnel schedules to meet mission needs.

5.2.1.3 Reserved.

5.2.1.4 The contractor shall identify a single point of contact, or manager, to the Government for the overall contract effort and for each TO.

5.2.1.5 Reserved.

5.2.1.6 The contractor shall immediately notify the Government of cost, schedule, or performance changes to, or deviations from, the program.

5.2.1.7 The contractor shall notify the PCO, in writing, if there is work required beyond the scope of the contract. The PCO is the only person authorized to change the terms and conditions of the contract.

All technical and management interchanges between the Government and the contract personnel shall be conducted subject to this condition.

5.2.1.8 The contractor shall provide reports and information reviews integrating technical accomplishments with the schedule and work progress for each TO on contract.

5.2.1.9 The contractor shall attend routine status meetings with Government, associate contractors and/or external mission partners.

5.2.1.10 Reserved.

5.2.1.11 The contractor shall ensure all contractor personnel comply with Government operating instructions, policies, and procedures as required by Appendix C.

5.2.1.12 The contractor shall use government furnished or purchased tools, such as Excel, Jira, Visio, Teams, SharePoint, Project, etc., for all products. Mission-specific tools will be further defined in the individual mission TO PWS.

5.2.2 (U) Cost Management

Intent: Have and implement a process of planning, estimating, and controlling the costs of the program throughout the entire life cycle, from development to disposal, and against accepted proposal costs.

5.2.2.1 The contractor shall be responsible for managing and controlling program costs in accordance with the technical and cost proposals for the contract requirements.

5.2.2.2 The contractor shall identify an appropriate cost management approach and shall be required to submit corrective management plans at the direction of the PCO.

5.2.2.3 The contractor shall prepare technical and cost proposals for new Task Orders (TOs) and Contract

Line Item Numbers (CLINs) within the scope of this PWS.

5.2.2.4 The contractor shall prepare technical and cost proposals to support external SD mission requirements.

5.2.2.5 The contractor shall manage and provide budgetary information, identify labor and other direct costs including travel and training, track actual costs, and forecast time-phase planned expenditures, and indirect costs.

5.2.3 (U) Information Management

Intent: To have an orderly and disciplined accounting and reporting methodology which provides for the accurate recording of data, and the timely extrapolation and transmission of management and/or mission information used in decision-making or processing.

5.2.3.1 The contractor shall manage all data and documentation using Government-approved collaborative tools and organizational structures as specified by the HADES Program Manager or Contract Officer

Representative (COR).

5.2.3.2 The contractor shall maintain all data and documentation in current status and store it on the

Government network using Government-approved tools, ensuring accessibility to authorized

Government personnel.

5.2.3.3 The contractor shall maintain current and accurate operational procedures, technical data, test plans, test reports, training materials, and other documents required to conduct activities assigned under this contract utilizing a Government-approved configuration management tool and process.

5.2.3.4 The contractor shall maintain current and accurate operational procedures, technical data, test plans, test reports, training materials, and other required documents utilizing the Government-approved configuration management tool and process.

5.2.4 (U) Security and Data Handling Management

Intent: To expertly operate within the guidelines and regulations of classified material and in a classified environment to promote expeditious product development and fielding without any security incidents or violations.

5.2.4.1 The contractor shall ensure that all contractor personnel comply with Government-provided training and comply with security and information assurance guidance as outlined in this contract, DoD

5220.22-M, the National Industrial Security Program Operating Manual (NISPOM), and other security guidance as required by the National Industrial Security Program (NISP), DoD, and the U.S.

Air Force.

5.2.4.2 The contractor shall provide cleared personnel in accordance with the National Industrial Security

Program (NISP), DD Form 254, and other security guidance provided by the Government. The contractor shall submit SCI nomination requests using Government-designated systems and processes within ten (10) business days of identifying the personnel requirement or receiving

Government direction to submit such nominations.

5.2.4.3 The contractor shall ensure that all personnel on this contract comply with the mission specific

Security Classification Guides (SCG) and other associated SCGs. Other SCGs may vary by project and will be provided by the Contracting Officers Representative (COR) or Program Manager (PM) as required.

5.2.4.4 The contractor shall use and protect sensitive, non-public information from unauthorized disclosure in accordance with DoDI 8582.01. The use and disclosure of such information shall only be used for the purpose of performing this contract. The contractor shall not use or disclose such information for personal or commercial purpose. The contactor shall obtain permission from the PCO or the PM before disclosing or discussing such information with a third party.

5.2.4.5 The contractor shall assist in security measures in real time when present in the RSC. Implementing security measures shall take precedence over ground system operations.

5.2.4.6 The contractor shall respond to any Security Forces personnel questions.

5.2.4.7 The contractor shall, during alarm activations, escort Security Forces personnel where needed and notify appropriate SSC personnel.

5.2.4.8 The contractor shall perform physical security duties of the HADES contractor workspaces as part of the daily operations. This shall be documented daily on Standard Form 701.

5.2.4.9 The contractor shall perform duties in support of the Top-Secret Control Officer (TSCO), TEMPEST

Manager, and Ground Systems Security Officer (GSSO) as required, including but not limited to security documentation maintenance, inventory tracking, access control support, personnel ingress/egress coordination, security incident reporting, and compliance with applicable security policies and procedures.

5.2.4.10 The contractor shall provide escort services for uncleared personnel, visitors, and individuals without appropriate facility access authorization within Government facilities and designated controlled or restricted areas, in accordance with (IAW) Ground Systems Security Officer (GSSO) policies and local security procedures. The contractor shall coordinate escort requirements with the Government

Task Order lead and facility security personnel to ensure availability of qualified escort personnel does not delay scheduled work, testing, maintenance activities, or mission operations.

5.2.4.11 The contractor shall understand and adhere to facility security procedures for hardware ingress, movement, or egress into, within, or out of secure facilities in accordance with (IAW) Ground

Systems Security Officer (GSSO) policies and local security requirements. The contractor shall coordinate hardware movements with the Government Task Order lead and facility security personnel in advance to ensure compliance with security protocols, proper documentation, and adherence to mission schedule requirements.

5.2.4.12 The contractor shall maintain accountability and documentation of all classified hardware in accordance with (IAW) TSCO and GSSO policies, including inventory records, transfer documentation, and movement tracking.

5.2.4.13 The contractor shall manage, maintain, control, procure, issue, inventory and safeguard Government

Furnished Property (GFP) and review equipment utilization and material consumption to ensure

100% accountability of all contract GFP.

5.2.4.14 The contractor shall maintain all applicable GFP data in the Air Force Equipment Management

System (AFEMS) IAW the applicable property clauses on the contract. Current GFP list is provided by the Government.

5.2.4.15 The contractor shall support Government efforts to maintain satellite operations center facility accreditation at the appropriate security level for mission operations by providing required documentation, supporting security audits and inspections, implementing assigned corrective actions, and coordinating with the Government Task Order lead, TSCO, and GSSO as directed.

5.2.5 (U) Quality Control

Intent: Ensure the staff and services rendered are performed and delivered to a high degree of quality, and personnel and product errors are minimized.

5.2.5.1 The contractor shall develop, provide, and implement a Quality Control Plan that establishes processes, procedures, inspection criteria, performance metrics, and corrective action mechanisms for ensuring quality of all deliverables, services, and work products in accordance with Government standards and task order requirements.

5.2.5.2 The contractor's Quality Control Plan shall include procedures for identifying, preventing, and ensuring non-recurrence of deficient services and personnel errors, including defect tracking, root cause analysis, trend analysis, corrective actions, and preventive measures.

5.2.5.3 Reserved.

5.2.5.4 The contractor shall maintain and make available to the Government all quality control records, including inspections, audits, root cause analyses, and corrective action documentation, throughout the contract performance period and for a minimum of three years after contract completion or until final settlement of any claims under this contract, whichever is longer.

5.2.5.5 The contractor shall respond to all Government-issued Corrective Action Reports (CARs) within the timeframe specified in the CAR, including root cause analysis, corrective action plan, implementation timeline, and verification of effectiveness.

5.2.5.6 The contractor shall participate in monthly Government-led performance review meetings at a frequency determined by the Government Task Order lead to review contractor performance, discuss identified problems, and address recommendations for increasing effectiveness or controlling costs.

5.2.6 (U) Risk Management

Intent: Support the Government with proactively identifying program and product risks, management techniques and treatments, and implement risk management solutions to maximize mission success.

5.2.6.1 The contractor shall participate in the Government risk management program, including attending risk review meetings, providing risk inputs, and supporting risk assessment activities as directed by the Government Task Order lead.

5.2.6.2 The contractor shall identify, assess, and document risks for each supported task order, including risk descriptions, likelihood and impact assessments, mitigation strategies, and alternative solutions within the Government risk management process.

5.2.6.3 The contractor shall implement Government-approved risk mitigation solutions and corrective actions as assigned, and track implementation status and effectiveness.

5.2.7 (U) Training and Certification

Intent: To have a qualified, well-trained workforce that provides high-quality products and services to the warfighter.

5.2.7.1 The contractor shall develop, implement, and administer a technical training and certification program to ensure contractor personnel are position certified and qualified to work on assigned tasks, products, and missions.

5.2.7.2 The contractor shall provide initial training, evaluation, and certification for contractor personnel, and periodic recertification as processes, technologies, and products change or as directed by the

Government Task Order lead.

5.2.7.3 Reserved.

5.2.7.4 The contractor shall maintain training records for all contractor personnel and provide training documentation to the PCO, COR, or Government Task Order lead when requested.

5.2.7.5 The contractor shall maintain and update training materials as technology and products change or as directed by the Government Task Order lead.

5.2.7.6 The contractor shall provide training to Government personnel as requested by the Government, with scope and level of effort defined by the Government Task Order lead.

5.2.7.7 The contractor shall ensure all contractor personnel complete mandatory Government-provided training as directed.

5.2.7.8 The contractor shall ensure all contractor personnel accessing DoD information systems obtain and maintain required information assurance certifications in accordance with DoD 8140 (formerly DoD

8570) or successor directives.

5.2.7.9 The contractor shall ensure personnel in designated positions obtain and maintain industry-recognized certifications appropriate to their role (e.g., Security+ for System Administrators) and identify required certifications in the contractor's staffing matrix.

5.2.7.10 Reserved.

5.2.7.11 Reserved.

5.2.8 (U) Configuration Management

Intent: To apply technical and administrative direction and surveillance to: (1) identify and document the functional and physical characteristics of a configuration item, (2) control changes to those characteristics, and (3) record and report changes to processing and implementation status.

5.2.8.1 The contractor shall maintain configuration control of procedures, documents, baselines, and products, ensuring all configuration items are current, accurate, and under formal change control in accordance with Government direction, to include but not limited to DoDI 5000.88.

5.2.8.2 The contractor shall use Government-approved configuration management tools and processes to identify, track, control, and document changes to all configuration items.

5.2.8.3 The contractor shall support and participate in the Government Change Request process, including but not limited to Change Request submissions, Engineering Review Boards (ERB), Configuration

Control Boards (CCB), Pre-Execution Reviews (PER), and Configuration Audit Boards (CAB).

5.2.8.4 The contractor shall update system documentation to reflect approved changes and incorporate updates into the configuration baseline within 5 business days of system changes or as directed by the Government Task Order lead.

5.2.8.5 Coordinate all CCB packages with the Government Program Lead or assigned POC for simple designs or changes, the final (critical) design, may be documented in the CCB package. The contractor shall coordinate entry and exit success criteria with the Government Program Chief

Engineer. The Government may use the results of the Final (Critical) Design phase to (1) authorize the contractor to acquire materials and services, (2) begin software development (if required), and/or

(3) support a review milestone, or to direct the contractor to continue to the System Assembly, Integration, Test and Operational Acceptance phase.

5.2.8.6 The contractor shall assess feasibility with input from various Subject Matter Experts (SMEs) including safety, security, and cybersecurity SMEs, utilizing test-bed simulations, models, mock-ups, or other analytical tools, and provide study documentation to the Government Task Order lead.

5.2.8.7 Reserved.

5.2.9 (U) Procurement, Logistics, and Lifecycle Management

Intent: To make material purchases and be responsible for planning, development, implementation, and management of effective and affordable product support strategies throughout the life cycle of DoD systems, from concept through disposal.

5.2.9.1 The Contractor shall develop and maintain a lifecycle sustainment plan. The plan should include tools, processes and procedures that maintain configuration management of the systems and provide the government recommendations for hardware recapitalization opportunities. Software and licensing renewals must also be identified to the government prior to their expiration.

5.2.9.2 The contractor shall procure, manage, and control all support agreements, warranties, and license agreements for all software & hardware.

5.2.9.3 The contractor shall adhere to directed procurement methods as required by DoD policy.

5.2.9.4 The contractor shall maintain minimum effective levels of bench stock and spares to support mission requirements, such that mission capability can be recovered within timeframes defined by the applicable mission or task order and provide quarterly inventory status reports to the Government

Task Order lead.

5.2.9.5 The contractor shall manage storage, receiving, inspection, staging, packaging, distribution, disposition, shipment, and disposal of equipment, supplies, and consumables, and provide logistics support capability 24 hours per day, 7 days per week with on-call personnel available to respond to urgent mission needs at the direction of the Government Task Order Lead.

5.2.9.6 The contractor shall establish and manage programs for diminishing manufacturing sources and material shortages (DMSMS), parts obsolescence, and vanishing vendors.

5.2.9.7 Reserved

5.2.9.8 The contractor shall procure and convert Contractor Acquired Property (CAP) to Government

Furnished Property (GFP) in accordance with the property clauses and purchasing requirements of this contract.

5.2.9.9 The contractor shall perform packaging, handling, shipping, and transportation of CAP and GFP in support of mission requirements or as directed by the Government.

5.2.9.10 The contractor shall track and obtain, when necessary, all required maintenance, repairs, inspections, spares, and replacements for GFP.

5.2.9.11 The Contractor-Inventory Control Point (C-ICP) contractor shall be responsible for providing unique spare parts and support equipment, and supply chain management support.

5.2.9.12 The Contractor will implement a Property Management System (PMS) capable of interfacing with

DOD and Air Force systems through the Defense Logistics Agency’s Defense Automated

Addressing System (DAAS) using Defense Logistics Management Standards (DLMS) transactions.

This includes maintaining accountability records in the Air Force Accountable Property System of

Record (APSR), and the Defense Property Accountability System (ELMS), for property in the contractor’s possession.

5.2.9.13 The Contractor shall maintain Government Furnished Propery (GFP) and Government provided warehouses. Generally, all components procured and managed by the contractor will be managed as

Government Furnished Property (GFP) and identified within the contract. The list of components is the authorizing document for C-ICP managed inventory. C-ICP support shall include but is not limited to: (1) Inventory Management, (2) Asset Management, (3) Maintenance Activities, (4)

Supplier Management, (5) Packaging, Handling, Storage and Transportation, and (6) Configuration

Management.

5.2.9.14 Reserved.

5.2.9.15 The contractor's C-ICP organization shall consist of contractor personnel, processes, facilities, and computer systems that support the successful accomplishment of wholesale level warehousing to achieve performance metrics as identified in this PWS and task order-specific requirements.

5.2.9.16 The contractor shall establish and maintain a Property Management System or a system of internal controls to provide asset visibility and inventory status reporting and provide inventory status reports to the Government Task Order lead at intervals specified in the task order.

5.2.9.17 The Contractor’s Property Management System shall be capable of interfacing with appropriate

DOD and Air Force inventory management systems and processing the DLMS transactions identified in the Interface Control Document. If the Contractor’s Property Management System is not capable of interfacing with DOD and Air Force systems, the Contractor shall initiate and maintain the processes, systems, procedures, records, and methodologies necessary for effective and efficient control of Government property.

5.2.9.18 Reserved.

5.2.9.19 The Contractor shall ensure these part records are structured in the property management system to maintain part configuration control, approved part substitution and interchangeability identification, serialized item control, notice of special handling requirements, and record item consumption data.

5.2.9.20 The Contractor will ensure accurate pricing of property In Accordance With (IAW) DOD and Air

Force policy directives with supported documentation. Documents supporting accountability and/or financial information will be maintained for 10 years.

5.2.9.21 The Contractor shall comply with all inventory reporting requirements for DoD’s Financial

Improvement and Audit Remediation requirements. This includes, but is not limited to, accurately reporting all transactions required to maintain accountability records for contractor managed and possessed GFP in the Government’s APSR. The contractor shall maintain accurate and auditable records and provide key supporting documentation for transactions within 2 business days upon request to support audit requirements. The contractor will adhere to policies for contractor managed and possessed GFP IAW DOD and Air Force policy directives.

5.2.9.22 The Contractor’s C-ICP shall determine, procure, repair, service, store, receive and dispose of unique spare parts and support equipment in accordance with mission requirements and Government direction.

5.2.9.23 The contractor shall have the capability to handle and store classified property and comply with the requirements of DD Form 254. Disposal of classified and unclassified consumable and repairable components shall be IAW the assigned demilitarization (DEMIL) code in accordance with DoD

Manual 4160.28, Volume 2, or successor guidance

5.2.9.24 The Contractor shall perform property control and maintain a 98% or better inventory accuracy for unclassified components and 100% accountability for classified components.

5.2.9.25 The Contractor shall conduct monthly 5% or greater spot-checks and conduct physical inventories

IAW DOD and Air Force policy directives.

5.2.9.26 Reserved.

5.2.9.27 The Contractor shall disposition C-ICP managed property through Scrap or Disposal when it is determined not beneficially repairable, excess, or obsolete. Considerations, such as lead time for new procurement, out of production items, mission requirements and Operations Tempo, must be considered prior to determining that an asset is beyond economical repair. The contractor shall coordinate disposition decisions with the Government Task Order lead for items exceeding threshold values or mission-critical components as specified in the task order.

5.2.9.28 The contractor shall maintain a record of disposition actions and report IAW Government-provided reporting instructions.

5.2.9.29 The contractor shall gain and maintain access to CSWS Data Exchange (CSWS DE)/D375 through the Air Force Portal using a valid Common Access Card (CAC)/Public Key Infrastructure (PKI), DD

Form 2875, sponsor letter, and non-disclosure statement.

5.2.9.30 The contractor shall enter required data as identified in the CSWS DE Student Training Course

Guide and Checklists, including basic management data, asset data, item management and equipment specialist data, packaging and transportation data, logistics reassignment data, and spares computation data, and ensure data accuracy and currency

5.2.10 (U) Concept Development

Intent: To support the Government in the initial process of exploring, defining, and documenting new ideas and capabilities, often linking strategic guidance to future product development. It involves examining how to meet mission requirements, exploring the technical feasibility of concepts, and analyzing potential solutions to determine the best approach for developing future systems.

5.2.10.1 The contractor shall engage in activities working with the Government and other program stakeholders in developing mission requirements and concepts.

5.2.10.2 The contractor shall participate in and support technical meetings and reviews at various locations.

5.2.10.3 The contractor shall provide weekly status reports, or as deemed necessary by the Government

Task Order lead on participation, accomplishments, and progress resolving assigned action items.

5.2.10.4 When the contractor proposes a change or upon Government request, the contractor shall conduct conceptual studies and Analyses of Alternatives (AoA) to produce a broad spectrum of ideas or alternatives which address a requirement, risk, issue, or other problem.

5.2.10.5 For each alternative in a conceptual study or AoA, the contractor shall:

1. Identifies and determines feasibility.

2. Develops technical concepts and identifies potential technological needs.

3. Defines scope.

4. Develops high-level Concept of Operations (CONOPS) or Concept of Employment

(CONEMP).

5. Provides draft system-level requirements.

6. Identifies potential technical, schedule and cost benefits and risks.

7. Identifies potential cybersecurity benefits and risks.

8. Identifies general costs and schedule without consideration of resource availability.

5.3 (U) Grounds System Services

Intent: Manage lifecycle of satellite ground systems and supporting infrastructure to meet operational needs.

5.3.1 (U) Ground System Engineering and Design

Intent: To develop and manage product designs through structured processes to define, develop, and verify system requirements, interfaces, and performance metrics.

5.3.1.1 The Contractor shall use a disciplined Systems Engineering (SE) approach to all work conducted under this PWS to ensure changes do not adversely impact systems/capabilities.

5.3.1.2 The contractor shall interface with internal and external Mission Partners during all phases of the SE process.

5.3.1.3 The contractor shall develop and maintain a Systems Engineering Management Plan (SEMP) that includes, but is not limited to: (1) SE processes to be used (e.g., configuration, risk, and change management), (2) roles and responsibilities, (3) verification and validation (V&V) approach, (4) metrics and measurements, (5) tools and technologies, and (6) schedule and resources.

5.3.1.4 The contractor shall continuously review the system designs and architectures, providing quarterly recommendations to the Government for improvements in areas such as, but not limited to, redundancy, system downtime, or backup solutions.

5.3.1.5 The contractor shall continuously assess ground systems to identify single points of failure within the system and any equipment at or near End of Life (EOL) or End of Support (EOS)

5.3.1.6 The contractor shall identify single points of failure and EOL/EOS equipment and propose mitigation strategies and paths forward to the Government.

5.3.1.7 The contractor shall coordinate software license renewals and purchases with the Government and obtain Government approval within 90 days of license expiration or identified need.

5.3.1.8 The contractor shall work with internal and external mission partners to ensure system interfaces are well defined, documented, and new requirements are compliant with existing systems.

5.3.1.9 The contractor shall identify, review, and provide recommendations on ground systems’ requirements with government representatives and mission partners.

5.3.1.10 The contractor shall ensure any proposed changes to system designs are approved by the

Government prior to modification of operational baseline.

5.3.2 (U) Ground System Development

Intent: To develop products as specified by Government approved design plans that fully satisfy mission requirements.

5.3.2.1 The contractor shall gain appropriate design configuration management approvals from the

Government before any system development begins.

5.3.2.2 The contractor shall develop system design specifications and capabilities that fully satisfy mission requirements.

5.3.2.3 The contractor shall execute a government approved, IA-compliant plan to research, procure, integrate, test, and deploy various hardware, software, and supporting equipment solutions while maintaining current capabilities to meet existing and emerging mission requirements.

5.3.2.4 The contractor shall develop the necessary infrastructure (e.g., power, cooling, space, communications, facilities, etc.) for government systems in accordance with approved design specifications.

5.3.2.5 The contractor shall modify or coordinate with appropriate organizations to ensure infrastructure meets requirements to implement approved design specifications.

5.3.2.6 The contractor shall develop integration solutions (e.g., adaptors, APIs, software modules, etc.) in accordance with the approved design to enable integration between current system baselines and mission partner systems.

5.3.2.7 The contractor shall interface with external vendors throughout the development process to further inform and propose solutions that satisfy system requirements.

5.3.2.8 The contractor shall perform incremental developmental testing prior to system integration.

5.3.3 (U) Ground System Integration

Intent: To integrate products into systems and infrastructure in accordance with Government approved design plans and interfaces.

5.3.3.1 The contractor shall ensure new patches, upgrades, and configuration changes are compatible with externally connected systems prior to implementation.

5.3.3.2 The contractor shall coordinate all patches, upgrades, and configuration changes with internal/external mission partners, as necessary, prior to implementation.

5.3.3.3 The contractor shall support external mission partner testing with the ground systems, as needed, to ensure interoperability and verify that external changes have no detrimental impact to existing missions as directed by the Government.

5.3.3.4 The contractor shall perform the necessary tasks to obtain and retain accreditation and certification of the ground systems from the appropriate Authorizing Official (AO)

5.3.3.5 The contractor shall maintain mission configuration of Mission Unique Software (MUS) with scripts and integration code.

5.3.3.6 The contractor shall maintain integrated version of mission software.

5.3.3.7 The contractor shall support test and verification processes to make sure system performance requirements are met.

5.3.3.8 Reserved.

5.3.3.9 The contractor shall update mission procedures and configurations to address errors, new features, and performance.

5.3.3.10 The contractor shall write and apply integration code to Gov-provided scripts to function in the C2 suite.

5.3.3.11 The contractor shall conduct incremental, iterative, and automated functionality tests, and include integration tests and certification of MUS interfaces.

5.3.3.12 The contractor shall integrate MUS to include payload-specific telemetry, commanding, or planning applications.

5.3.3.13 The contractor shall develop integrated test plans and reports for future capability enhancements.

5.3.3.14 The contractor shall deliver updated system architectures and documentation upon completion of new implementations or updates.

5.3.4 (U) Ground System Sustainment

Intent: Sustain and maintain satellite ground systems hardware, software, and supporting infrastructure to meet operational needs.

5.3.4.1 The contractor shall plan for the sustainment of ground system engineering infrastructure including hardware, software, license and license management, maintenance agreements, facilities management (e.g., HVAC, power, structure, communication systems), and cybersecurity.

5.3.4.2 The contractor shall perform regular, scheduled preventative maintenance activities on all hardware and software for the ground systems and supporting infrastructure at intervals specified by manufacturer recommendations, Government direction, or as required to maintain system availability requirements.

5.3.4.3 The contractor shall troubleshoot and replace failed or broken hardware components to ensure availability requirements are met while adhering to the Government-defined Change Request

Process and Information Assurance (IA) requirements, and provide incident reports documenting failures, root causes, and corrective actions.

5.3.4.4 The contractor shall deliver a quarterly mission-specific Software Configuration Audit (SCA) report that compares the operational configuration against the approved baseline and identifies any discrepancies, unauthorized changes, or configuration drift.

5.3.4.5 The contractor shall work with software vendors or developers to ensure software within the ground systems remains IA compliant, address identified problems through software fixes or patches and receive and install software updates. All software-version updates, installations, or configuration changes shall be approved through the Government-defined Change Request Process prior to implementation. The Government retains unlimited rights to any software code developed in support of this contract.

5.3.4.6 The contractor shall identify End of Life (EOL) / End of Support (EOS) software prior to vendor support termination and present the Government with alternatives and strategies to ensure continued mission performance.

5.3.4.7 The contractor shall coordinate all required downtime with the Government to avoid scheduling conflicts.

5.3.4.8 The contractor shall maintain up-to-date backups of physical machines, virtual machines, network equipment configurations, and Cross Domain Systems (CDS) in accordance with Government-approved backup policies, with backup frequency sufficient to meet system availability and recovery time objectives.

5.3.4.9 The contractor shall maintain all external interfaces with and among system components necessary to conduct operations, including interface control documentation, connectivity verification, and coordination with interface providers to ensure continuous operational capability.

5.3.5 (U) Ground System Decommission, Disposal, and/or Transfer

Intent: To conduct end-of-life or organizational transfers of ground systems in accordance with Government processes and regulations.

5.3.5.1 The contractor shall decommission any system, as directed by the Government, by…