Attach 1 - HADES IDIQ PWS Draft RFP.pdf

SECTION J – ATTACHMENT 1

BASIC IDIQ PERFORMANCE WORK

STATEMENT (PWS)

SECTION J FA8809-25-S-S001

ATTACHMENT 1

HYBRID ARCHITECTURE AND DEVELOPMENT FOR EXPERIMENTAL

SYSTEMS (HADES) PROGRAM

BASIC IDIQ

PERFORMANCE WORK STATEMENT (PWS)

Space Systems Command (SSC)

Innovation and Prototyping Delta (SD)

Prototype Ground Development and Sustainment Branch (SDG)

Kirtland AFB, New Mexico

HADES Basic IDIQ Performance Work Statement

SECTION J FA8809-25-S-S001

REVISION CONTROL

Revision Number Date Remarks

1.0 15 Jan 2026 Draft PWS

SECTION J FA8809-26-R-B002

1. Table of Contents

1. Description of Services

1.1. Background

1.2. Scope

1.3. Access to Department of the Air Force Computer Systems

2. Basic Services

2.1. Contract Transition

2.2. Support Services

2.3. Ground System Services

2.4. Facility Services

2.5. Software Support Services (Chen/Botros)

2.6. Other Activities

3. Government Furnished Property/Government Furnished Service-Will be released with Final RFP

4. Appendices

1. Description of Services

The Hybrid Architecture and Development for Experimental Systems (HADES) contract is a procurement for prototype and operational satellite ground systems, satellite operations centers (SOCs), and support services. The contractor shall perform satellite ground system and satellite operations center engineering, development, integration, and sustainment, and associated support services primarily at, but not limited to, the Research, Development, Test, and Evaluation (RDT&E) Support Complex (RSC) at Kirtland Air Force Base, Albuquerque, New Mexico. The organization’s goal is to accelerate mission design and ground integration, launch and on-orbit operations, ground system tests, and rapid fielding to provide reliable, low-cost access to space in support of the warfighter.

1.1. Background

1.1.1. The Research Development Space and Missile Operations (RDSMO) program provides research, development, and test operations for assigned Department of Defense (DoD) experimental, demonstration, and prototype satellites, space vehicles, satellite ground control systems, tracking systems, and commercial applications of these systems. The RDSMO program may also provide these services to approved customers on a cost reimbursable basis.

1.1.2. The RDSMO program is managed by SSC/SD’s Prototype Ground

Development and Sustainment Branch (SDG) and operations are executed by SSC/SD’s Prototype Operations Branch (SDX). Together, these Branches provide the expertise, infrastructure, and processes necessary to manage and execute satellite and ground system engineering and operations to include scientific, technology demonstration, developmental, and prototype systems, while enabling rapid migration of space capabilities to the warfighter.

1.1.3. The contractor is a mission partner with the Government, customers, Federally Funded Research and Development Centers (FFRDCs), and associate contractors. The RSC provides access to a low-cost, reliable ground system and resources for 24x7 spacecraft operations to support the scientific and space acquisition communities. The satellite ground system, satellite operations centers, and support services being procured through this contract shall occur primarily, but not solely, at the following locations:

Kirtland Air Force Base, NM.

1.1.4. Spacecraft either currently operating or projected to begin operations at the

RSC are operated on a variety of ground systems and in diƯerent rooms.

Some spacecraft utilize commercial software and on-premise hardware, while others use contractor development mission unique software and cloud-based environments.

1.2. Scope

The scope of this acquisition is to support SD in the accomplishment of spacecraft ground systems and test support. It is anticipated between four and six Task Orders (TOs) will be awarded, but this may fluctuate based on product development and budget requirements. The contractor will be required to support current missions through the end of life while supporting new missions.

1.2.1. The contractor shall accomplish the tasks included in the Performance

Work Statement (PWS).

1.2.2. 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. The nature of this work shall, at times, require the contractor to be capable of quick response to stringent deadlines.

1.2.3. 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 in order to perform their work must obtain at least a Top-Secret clearance with Sensitive Compartmented Information eligibility.

1.2.4. Each awarded TO shall identify one or more areas specified in Section 2.0 of this PWS that apply to the mission. Each awarded TO shall identify: the objective, performance requirements, objectives and thresholds, period of performance, schedule, security requirements, and other direct costs.

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

1.2.6. Contractor-occupied facilities, on Government installations, such as oƯices, separate rooms, or cubicles must be clearly identified with contractor supplied signs, name plates, or other identification, showing that these are work areas for contractor or subcontractor personnel.

1.3. Access to Department of the Air Force Computer Systems

1.3.1. Performance under this contract requires access to Department of the Air

Force computer systems (stand-alone and networked). Compliance with Air Force Instruction (AFI) 33-119 and AFI 33- 202V1 are 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.

2. 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 of time. The contractor shall initiate no work without approval by the Procuring Contracting OƯicer (PCO). These requirements are applicable to the basic eƯort and all options, if exercised.

The PWS line items listed in this section specify the work required by the contractor.

However, not all PWS line items in this section may apply to a specific TO, project, or mission. Based on mission or project requirements, applicable PWS line items will be specified in detail in each TO PWS.

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.

2.1. 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. Therefore, the contract must provide for maximum cooperation between the successor and incumbent, as required, while ensuring that all work receives adequate attention during phase-in/phase-out. The incumbent contractor maintains full and sole responsibility for executing the requirements of the contract through the last day of the transition period.

2.1.1. Phase-In

The contractor shall provide for a smooth and eƯicient transfer of responsibilities during the designated 90-day phase-in period. The 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 contractor shall plan the phase-in tasks and work with the incumbent to finalize a phase-in plan. The 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.

2.1.2. Phase-Out

The 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, as determined by the Government.

The contractor shall plan the phase-out tasks and work with the successor contractor to finalize a phase-out plan.

2.2. 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 Support Services TO PWS.

Mission-specific support service requirements will be specified in each individual

TO PWS.

2.2.1. Program Management

Intent: Charged will the overall responsibility to accomplish program objectives for development, production, and sustainment to meets the user’s operational needs. Will be accountable for credible cost, schedule, and performance reporting to the Government.

2.2.1.1. The contractor shall be responsible for overall responsiveness, program management and reporting, adherence to schedule, ability to adapt to schedule changes, cooperative behavior, technical quality of work, management of contractor and subcontractor teams to reflect SD’s mission and commitment to customer satisfaction.

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

2.2.1.3. The contractor shall provide eƯective coordination with the Government to ensure successful implementation of ground system, SOCs, and support requirements.

2.2.1.4. The contractor shall identify a single point of contact, or manager, to the Government for the overall contract eƯort and for each TO.

2.2.1.5. The contractor shall propose a staƯing plan to the government and, with government approval, fulfill the staƯing plan according to the level of eƯort (or FTE (Full Time Equivalent)) agreed upon. This may include full-time and matrixed positions.

2.2.1.6. The contractor shall notify the Government of any problems in meeting contract requirements as soon as the problems are known and provide solutions to mitigate the issues.

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

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

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

2.2.1.10. The contractor shall hire and maintain a skilled and certified workforce that can meet the requirements of assigned work activities and perform to a high-quality degree.

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

2.2.1.12. The contractor shall utilize 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.

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

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

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

2.2.2.3. The contractor shall prepare technical and cost proposals for contract requirement documents within the scope of this PWS for new TOs and CLINs.

2.2.2.4. The contractor shall prepare technical and cost proposals for contract requirements in support of SZI mission requirements.

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

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

2.2.3.1. The contractor shall work with the Government to manage data and documentation in a collaborative and organized manner.

2.2.3.2. The contractor shall ensure that the data and documentation is current and easily accessible to the Government on the local Government network and by using the in-house tools.

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

2.2.4. Security and Data Handling

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.

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

2.2.4.2. The contractor shall provide cleared personnel in accordance with the NISP, DD Form 254, and other security guidance provided by submitting SCI nomination requests in a timely and responsive manner using the systems and processes determined by the Government.

2.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 OƯicers Representative (COR) or Program Manager (PM) as required.

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

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

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

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

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

2.2.4.9. The contractor shall perform duties in support of the Top-Secret

Control OƯicer (TSCO), TEMPEST Manager, and GSSO, as required.

2.2.4.10. The contractor shall escort personnel when appropriate, IAW GSSO policies.

2.2.4.11. The contractor shall understand and adhere to the process for hardware ingress, movement, or egress into, within, or out of a secure facility and do so in an eƯicient way that meets schedule requirements.

2.2.4.12. The contractor shall maintain accountability and documentation of all classified hardware IAW TSCO and GSSO policies.

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

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

2.2.4.15. The contractor shall maintain the satellite operations center facility accreditation at the appropriate level for mission operations.

2.2.5. Quality Control

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

2.2.5.1. The contractor shall provide and implement a quality control plan.

2.2.5.2. The contractor shall develop and implement procedures to identify, prevent, and ensure non-recurrence of unacceptable services within the quality control plan.

2.2.5.3. The contractor shall track personnel errors, determine root causes of problems when human error is suspected, document the results of the root cause analyses, and take corrective actions.

2.2.5.4. The contractor shall maintain and make available to the Government all records of inspections throughout the contract performance period and for the period after contract completion until final settlement of any claims under this contract.

2.2.5.5. The contractor shall respond to all Government-issued Corrective Action Reports (CARs) in a timely manner as prescribed within the contractor’s Quality Control Plan.

2.2.5.6. The contractor shall attend monthly multi-functional team meetings or as deemed necessary by the program oƯice, to review the Government assessment of the contractor’s performance and discuss any problems or any recommendations for increasing eƯectiveness or controlling costs.

2.2.6. Risk Management

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

2.2.6.1. The contractor shall participate in the HADES/Government risk management program with the Government team.

2.2.6.2. The contractor shall provide risk identification and risk management handling plans within the Government risk management process for each supported TO and assess their importance and impact to mission operations and determine alternative solutions to mitigate risks.

2.2.6.3. The contractor shall implement any risk mitigation solutions identified in the plan.

2.2.7. Training and Certification

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

2.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 each task for assigned products and missions.

2.2.7.2. The contractor shall initially train, evaluate, and certify contractor personnel.

2.2.7.3. The contractor shall periodically train, evaluate, and recertify contractor personnel as technology and products change.

2.2.7.4. The contractor shall maintain training records on contractor employees, and provide training documentation to the PCO, COR, or PM when requested.

2.2.7.5. The contractor shall maintain and update training materials as technology and products change.

2.2.7.6. The contractor shall provide training to Government personnel as requested by the Government.

2.2.7.7. The contractor shall ensure all contractor personnel complete/attend mandatory Government-provided training.

2.2.7.8. The contractor shall ensure all contractor personnel accessing DoD information systems have the proper and current information assurance certifications.

2.2.7.9. The contractor shall utilize industry certifications, practices, and standards for certain personnel positions such as Security+ for System Administrators and identify the associated certifications necessary in their staƯing matrix.

2.2.7.10. The contractor shall have a company internal training program to develop their employees to perform to a high-quality degree in customer engagement, program management, oral presentations, leadership and other business and technical acumen not at the Government’s expense.

2.2.7.11. The contractor shall have a company internal development program to expand their employee’s skillsets, certifications, and licenses not at the Government’s expense.

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

2.2.8.1. The contractor shall maintain configuration of procedures, documents, baselines, and products to maintain positive change control.

2.2.8.2. The contractor shall use an appropriate configuration management tool and process to track and implement changes.

2.2.8.3. The contractor shall support and participate in the Government

Change Request process that includes, but not limited to, Change Request Submissions, Engineering Review Boards (ERB), Configuration Control Boards (CCB), Pre-Execution Reviews (PER), and Configuration Audit Boards (CAB).

2.2.8.4. The contractor shall finalize system documentation to reflect changes.

Updates to hardware system documentation must be incorporated into the baseline within 5 business days of system changes or as directed by the government.

2.2.9. Procurement, Logistics, and Lifecycle Management

Intent: To make material purchases and be responsible for planning, development, implementation, and management of eƯective and aƯordable product support strategies throughout the life cycle of DoW systems, from concept through disposal.

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

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

2.2.9.3. The contractor shall adhere to directed procurement methods as required by DoW policy.

2.2.9.4. The contractor shall maintain minimum eƯective levels of bench stock and spares to support the mission, such that mission capability can be recovered within a reasonable period of time, as defined by the applicable mission or task order.

2.2.9.5. The contractor shall manage storage, receiving, inspection, staging, packaging, distribution, disposition and shipment, and disposal of equipment, supplies, and consumables. There will be the capability to provide logistics support 24/7.

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

2.2.9.7. Reserved.

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

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

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

Send defective or unserviceable parts and components to the manufacturer for repair or replacement if necessary.

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

2.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), the Defense

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

2.2.9.13. The Contractor shall establish and maintain wholesale warehouses and provide wholesale level supply support. As a general rule, 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 will include but is not limited to:

• Inventory Management

• Asset Management

• Maintenance Activities

• Supplier Management

• Packaging, Handling, Storage and Transportation

• Configuration Management

2.2.9.14. Inventory Management includes all elements of inventory management: requisition processing, storage, shipment, delivery, pick-up, receiving, shipping, in-transit visibility/tracking/reporting, property accountability and handling of classified material.

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

2.2.9.16. The Contractor shall establish and maintain a contractor Property Management System or a system of internal controls to provide asset visibility and inventory status reporting.

2.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 eƯective and eƯicient control of Government property.

2.2.9.18. The Contractor’s Property Management System is required to contain records for the program’s parts that provide comprehensive logistics, procurement, and technical data required to accomplish supply support analysis, parts ordering, property accountability, and funds

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

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

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

2.2.9.22. The Contractor’s C-ICP shall determine, procure, repair, service, store, receive and dispose of unique spare parts and support equipment

2.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/unclassified consumable/repairable components will be IAW with the assigned demilitarization code. DEMIL Codes may be found at hƩp://dƟc.mil/whs/direcƟves/corres/pdf/416028m_vol2.pdf and DoD Manual 4160.28, Vol 2.

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

2.2.9.25. The Contractor shall conduct monthly 5% or greater spot-checks and conduct physical inventories IAW DOD and Air Force policy directives.

2.2.9.26. The Contractor shall maintain a current record of the physical inventory as it progresses and report IAW provided instructions.

2.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 consider other considerations and their eƯect on performance prior to disposing of any asset determined as beyond economical repair.

2.2.9.28. Disposition shall remove components from Contractor accountability by reducing the inventory balance in the Property Management System and physically scrapping in-place at a Source of Repair (SOR) or issuing disposed of property at the Main Operating Base (MOB) to the Air Force for processing. The Contractor shall maintain a record of disposition actions and report IAW reporting instructions.

2.2.9.29. The Contractor shall gain and maintain access to CSWS Data Exchange (CSWS DE)/D375. CSWS DE is the bridge between CLS activities and Air Force legacy systems that do not allow commercial access. It is the single automated source to provide mission essential packaging, shipping, and transportation data to Air Force systems.

Access to CSWS DE is available through the AF Portal and requires a valid CAC/PKI, DD 2875, sponsor letter and non-disclosure statement.

Forms are available through the application owner identified on the AF Portal.

2.2.9.30. The Contractor shall enter required data as identified in the CSWS DE Student Training Course Guide and the CSWS DE Checklists on the

Training & Documentation page within D375. This includes, but is not limited to, basic management data, asset data, item management and equipment specialist data, packaging and transportation data, logistics reassignment data, and spares computation data.

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

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

2.2.10.2. The contractor shall participate in and support technical meetings and reviews at various locations. The contractor shall provide weekly status reports or as deemed necessary by the program oƯice on participation, accomplishments, and progress resolving assigned action items.

2.2.10.3. The Contractor shall (when the contractor proposes a change, or upon request):

2.2.10.3.1. Conduct conceptual studies to produce a broad spectrum of ideas or alternatives which address a requirement, risk, issue or other problem. A conceptual study (sometimes referred to as an Analysis of Alternatives [AoA]) examines various alternative solutions and, for each alternative:

2.2.10.3.2. Identifies and determines feasibility

2.2.10.3.3. Develops technical concepts and identifies potential technological needs

2.2.10.3.4. Defines scope

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

2.2.10.3.6. Provides draft system-level requirements

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

2.2.10.3.8. Identifies potential cybersecurity benefits and risks

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

2.2.10.4. The contractor shall assess feasibility with input from various Subject

Matter Experts (SME) (including safety/security/cyber-SMEs), test-bed simulations, models, mock-ups or other tools.

2.2.10.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:

2.2.10.5.1. Authorize the contractor to acquire materials and services

2.2.10.5.2. Begin software development (if required)

2.2.10.5.3. Support a review milestone, or to direct the contractor to continue to the System Assembly, Integration, Test and Operational Acceptance phase

2.3. Ground System Services

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

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

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

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

2.3.1.3. The contractor shall develop and maintain a Systems Engineering

Management Plan (SEMP) that includes, but is not limited to, the following:

SE processes to be used (e.g., configuration, risk, and change management)

Roles and responsibilities Verification and validation (V&V) approach Metrics and measurements Tools and technologies Schedule and resources

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

2.3.1.5. The contractor shall continuously study the 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).

2.3.1.6. The contractor shall identify single points of failure and EOL/EOS equipment and propose paths forward to the government.

2.3.1.7. The contractor shall obtain government approval for SW renewals and purchases within 90 days.

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

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

2.3.1.10. The contractor shall ensure any proposed changes to system designs are approved by the Government prior to modification of operational baseline.

2.3.2. Ground System Development

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

2.3.2.1. The contractor shall gain appropriate design configuration management approvals from the Government before any system development begins.

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

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

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

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

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

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

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

2.3.3. Ground System Integration

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

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

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

2.3.3.3. The contractor shall support external mission partner testing with the ground systems as needed to ensure interoperability and ensure that external changes have no detrimental impact to existing missions.

2.3.3.4. The contractor shall perform the necessary tasks to obtain and retain accreditation/certification of the ground systems from the appropriate Authorizing OƯicial (AO).

2.3.3.5. The contractor shall maintain mission configuration of MUS with scripts and integration code.

2.3.3.6. The contractor shall maintain integrated version of mission software.

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

2.3.3.8. Reserved

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

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

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

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

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

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

2.3.4. Ground System Sustainment

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

2.3.4.1. The contractor shall plan for eƯicient 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.

2.3.4.2. The contractor shall perform regular, scheduled, preventative maintenance activities on all hardware and software for the ground systems and supporting infrastructure.

2.3.4.3. The contractor shall troubleshoot and replace failed or broken hardware components ensuring that availability requirements are met while adhering to the Government defined Change Request Process and IA requirements.

2.3.4.4. The contractor shall deliver a quarterly mission specific Software

Configuration Audit (SCA) and report any discrepancies between the audit and the baseline.

2.3.4.5. The contractor shall work with software vendors or developers to ensure software within the ground systems remains IA compliant, to address problems identified by creating software fixes, or to receive and install software updates. Any software version update, install, or configuration change needs proper approval through the Government defined Change Request Process. The Government retains unlimited rights to any software code developed in support of this contract.

2.3.4.6. The contractor shall identify End of Life/End of Support software and present the Government with alternatives and strategies to mitigate impact to program success.

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

2.3.4.8. The contractor shall maintain up-to-date backups of physical machines, virtual machines, network equipment configurations, and cross domain systems (CDS) to ensure availability requirements are met.

2.3.4.9. The contractor shall maintain all external interfaces with and among system components necessary to conduct operations.

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

2.3.5.1. The contractor shall decommission any system, as directed by the

Government, by removing it from the active inventory in accordance with applicable regulations.

2.3.5.2. The contractor shall identify disposal requirements early in the system design phase and address safety concerns for both the environment and personnel.

2.3.5.3. The contractor shall document roles and responsibilities for all stakeholders involved in the demilitarization and disposal plan.

2.3.5.4. The contractor shall implement inventory controls and review demilitarization (DEMIL) requirements before disposition.

2.3.5.5. The contractor shall estimate costs and schedule all disposal activities, presenting a detailed proposal to the Government for approval.

2.3.5.6. The contractor shall ensure compliance with laws and regulations regarding demilitarization (DEMIL), and environmental safety while disposing items.

2.3.5.7. The contractor shall document roles and responsibilities for all stakeholders involved in the demilitarization and disposal plan.

2.3.5.8. The contractor shall manage storage, receiving, inspection, staging, packing, distribution, disposition and shipment, and disposal of equipment, supplies and consumables. This includes inventory

2.3.5.9. The contractor shall provide a phase-out plan prior to the scheduled end of the contract period of performance or transfer of management to another organization.

2.4. Facility Services

Intent: Manage, develop, and sustain all the infrastructure support necessary to maintain multiple 24/7 satellite operations and command and control centers.

2.4.1. Power Distribution and Resiliency Support

Intent: Ensure all power requirements are met regardless of commercial power availability.

2.4.1.1. The contractor shall continually assess power distribution systems and recommend upgrades to enhance eƯiciency and capacity, including load balancing and integration of renewable energy sources, as appropriate.

2.4.1.2. The contractor shall design, implement, and sustain backup power solutions, such as generators and uninterruptible power supplies (UPS), to ensure 99.99% uptime during outages.

2.4.1.3. The contractor shall conduct regular inspections and preventive maintenance on electrical panels, wiring, and transformers to identify and mitigate potential failures.

2.4.1.4. The contractor shall develop and test resiliency plans, including failover protocols and emergency response procedures, in coordination with facility stakeholders.

2.4.1.5. The contractor shall monitor power consumption in real-time using metering tools and provide monthly reports on usage trends, anomalies, and cost-saving opportunities.

2.4.1.6. The contractor shall ensure all work complies with relevant codes and obtain necessary permits and authorizations for installations or modifications.

2.4.2. Heating, Ventilation and Air Conditioning Support

Intent: Ensure all thermal requirements are met.

2.4.2.1. The contractor shall evaluate current HVAC systems for performance and energy eƯiciency, proposing retrofits or replacements as needed to meet facility requirements.

2.4.2.2. The contractor shall install, calibrate, and commission new HVAC components, ensuring optimal airflow, temperature control, and humidity levels across all zones.

2.4.2.3. The contractor shall perform routine maintenance, including filter replacements, coil cleaning, and refrigerant checks, on a scheduled basis to prevent system downtime.

2.4.2.4. The contractor shall respond to HVAC malfunctions within 2 hours during business hours and 4 hours outside, restoring functionality to minimize disruptions.

2.4.2.5. The contractor shall integrate smart controls and sensors for automated monitoring, providing alerts for issues and generating quarterly reports on system performance and energy savings.

2.4.2.6. The contractor shall ensure compliance with environmental regulations, and conduct air quality testing to maintain indoor health standards.

2.4.3. Facility and Furniture Maintenance

Intent: Ensure all human factors and human systems integration meet operational, safety, and security standards.

2.4.3.1. The contractor shall inspect facility structures, including roofs, walls, floors, and doors, on a quarterly basis and perform repairs to address wear, damage, or safety hazards.

2.4.3.2. The contractor shall maintain furniture and fixtures, including assembly, reconfiguration, and refinishing, to support operational needs and extend asset lifespan.

2.4.3.3. The contractor shall develop a preventive maintenance schedule for all facility elements, tracking completion and documenting issues via a digital asset management system.

2.4.3.4. The contractor shall handle waste removal, cleaning, and pest control services to maintain a safe and hygienic environment, adhering to local health and safety guidelines.

2.4.3.5. The contractor shall respond to non-emergency maintenance requests within 24 hours and complete repairs within agreed timelines, providing status updates to facility managers.

2.4.3.6. The contractor shall conduct annual facility audits to identify sustainment needs, such as painting or flooring replacements, and prepare budgeted recommendations.

2.4.4. Network Infrastructure Support

Intent: Ensure network architectures within the facility support mission bandwidth requirements, to include access points and availability.

2.4.4.1. The contractor shall assess and upgrade network cabling, switches, and routers to support high-speed data transmission and scalability for future expansions.

2.4.4.2. The contractor shall install and configure access points, firewalls, and redundancy measures to ensure secure and reliable connectivity with at least 99.95% availability.

2.4.4.3. The contractor shall perform monitoring of network performance, identifying bottlenecks or vulnerabilities through tools like intrusion detection systems.

2.4.4.4. The contractor shall provide 24/7 support for network issues, resolving outages within 1 hour during business hours and issues within 4 hours during non-business hours.

2.4.4.5. The contractor shall conduct security audits and patches on a regular basis, ensuring compliance with established standards.

2.4.4.6. The contractor shall document network architecture and changes, delivering updated diagrams and reports to facility IT personnel.

2.4.5. Space Optimization and Layout

Intent: Continuously optimize the physical space and workflow for the persistent flux of missions in and out of the facility.

2.4.5.1. The contractor shall analyze current space utilization through surveys and data collection, identifying ineƯiciencies and opportunities for reconfiguration.

2.4.5.2. The contractor shall design optimized layouts, incorporating ergonomic principles, workflow needs, and accessibility standards.

2.4.5.3. The contractor shall implement space modifications, such as partitioning, modular furniture installation, or signage updates.

2.4.5.4. The contractor shall evaluate and recommend technology integrations, such as environmental sensors, and provide dynamic space management solutions.

2.4.5.5. The contractor shall conduct reviews to measure infrastructure loading versus capacity, providing reports quarterly.

2.4.5.6. The contractor shall ensure all designs and changes comply with building codes and regulations, coordinating with architects or engineers, as required.

2.5. Software Support Services

Intent: TBA

2.5.1. Software Setup

Intent:

2.5.1.1. The Contractor shall work with key stakeholders to design a ground system architecture in accordance with customer requirements.

2.5.1.2. The Contractor shall build new ground system architectures.

2.5.1.3. The Contractor shall support software deployments in the ground software environment.

2.5.1.4. The Contractor shall…