BMEW MILSATCOM RFI.pdf

UNCLASSIFIED

Space Systems Command (SSC) International Affairs (IA)

Los Angeles Air Force Base, California (LAAFB, CA)

Ballistic Missile Early Warning (BMEW) and Military Satellite Communication (MILSATCOM) Request for Information (RFI)

Primer: Space Systems Command (SSC) International Affairs (IA) received a Letter of Request (LOR) for Letter of Offer and Acceptance (LOA) from a United States Central Command (CENTCOM) Partner Nation’s (PN) Ministry of Defense (MoD). As the primary point of contact (POC) for Space Foreign Military Sales (FMS) acquisitions, it is incumbent upon the United States Space Force (USSF) to respond to the LOR for LOA with a Rough Order of Magnitude (ROM) costs for the defense articles and services specified in the LOR.

As a result, SSC/IA is conducting market research to respond to the PN request. The United States Government (USG) encourages contractors to respond to some or all portions of the Request for Information (RFI) since the RFI covers multiple capabilities and the USG acknowledges that some contractors may not be able to unilaterally address all of the requirements that this RFI contains (i.e. a prospective vendor is only able to respond to the MILSATCOM space segment).Market research will be conducted on a per capability basis.

PLEASE NOTE: Responses to LORs for LOA are non-promissory and therefore there is no guarantee that this RFI will result in a Request for Proposal (RFP). SSC/IA anticipates similar requests from other partner nations and may repurpose the market research garnered from this RFI to respond to future LORs for LOA. The LOR for LOA response provided to the partner nation does not guarantee the sale of the services in question.

1. Background SSC/IA is seeking estimates from industry for assessing the requirements, interfaces and design of a Ballistic Missile Early Warning (BMEW) and Military Satellite Communication (MILSATCOM) system. This includes the associated Remote Tracking Stations (RTS), User Terminals, Mission Data Processing Centers (MDC), Satellite Operation Centers (SATOCs) and a Presentation Center. SSC/IA is currently building a response to an official LOR for LOA to provide the PN with a “Total Package Approach” cost for their planning purposes. RFI responses shall include information that allows SSC/IA to assess the contractor’s ability to help develop a space based BMEW, MILSATCOM and ground architecture for the PN.

2. Use of Non-Government Advisors The Government intends to use USG personnel to review the RFI responses. The Government reserves the right to use contractor personnel, including, but not limited to, SSC Federally Funded Research and Development Centers (FFRDC) and Systems Engineering and Technical Assistance (SETA) contractors. Contractor support will be bound by an appropriate Non-Disclosure Agreement (NDA) to protect proprietary and sensitive information. Additional NDAs will not be required as responses to this RFI will be considered an implicit acknowledgment and acceptance that non-Government advisors will be assisting the Government in the review process.

3. Guidelines for All Submissions

a. THE RFI IS MARKET RESEARCH AND WILL NOT RESULT IN AN AWARD

The cost of preparing the RFI responses is not an allowable direct charge to any Government contract.

b. All interested vendors are requested to provide:

i. Statement of the vendor’s capability to provide the requested capabilities listed below.

ii. ROM cost to provide services/supplies,

iii. ROM schedule to provide services/supplies.

c. Label and portion-mark RFI responses appropriately; the overall classification of an RFI response should not exceed SECRET.

d. Include a cover sheet with company name, address, date, RFI response POC with an email address and phone number.

e. SSC will not consider unnecessary brochures or proposals.

f. SSC will welcome proficiency demonstrations, use cases, and lessons learned.

g. RFI responses will use 8.5 x 11-inch portrait format pages with single-spaced Times New

Roman 12-point font with 1" margins. The landscape format is acceptable for charts and graphs only.

h. RFI responses shall not exceed forty-five (45) pages.

i. RFI responses must be delivered as either a PDF or Microsoft Word document.

j. RFI responses may be submitted electronically via NIPR or SIPR to the SSC point of contact(s) listed below.

k. RFI responses are due no later than 1700 PDT on 05/27/2025 to the SSC email address listed below.

SSC/IAF Market Research, ssc.iaf.marketresearch@spaceforce.mil

4. Next Steps Once the RFI responses are received, assessed for feasibility and affordability, SSC/IA will reach out to the PN. If a virtual one-on-one is requested by the U.S Government for clarification of any responses, the Government Contracting Office Representative(s) will contact the submitters POC listed on the cover sheet to schedule a virtual meeting.

5. Concepts Criteria For each Capability Requirement, address to the best extent possible:

• Requested Criteria

• Expertise to accurately assess what is being requested

• Additional information needed from either the U.S. Government or PN

• Associated Risks

• Concepts ROM Cost and Schedule Details

6. Initial Request Overview The PN is seeking a design for a space based BMEW and MILSATCOM system. The BMEW system will have the ability to detect theater ballistic missile threats and support an early warning message for the cueing of PN ground radar systems. These systems will be supported by satellite tracking stations, operations centers, and data processing centers. All systems will be made to integrate with Command, Control, Communications, Computers, and Intelligence (C4I) systems to enhance the CENTCOM PN MoD operations and space-based operations. Operation and Sustainment will be required to support the systems through their operational lifespan.

6.1. Space Based BMEW

Provide a design for a BMEW capability that includes at least two (2) Overhead Persistent Infrared (OPIR) space segments in Geosynchronous Orbits (GEO) providing stereo coverage with the following characteristics and/or requirements:

6.1.1 The system will be capable of detecting and tracking theater range ballistic missile threats and generating actionable missile warning reports.

6.1.2 The satellite will be designed to support operations in geosynchronous orbit for a minimum of fifteen (15) years after completion of on orbit testing. This includes accounting for the natural threats presented by space in the GEO area.

6.1.3 The BMEW system will be capable of providing continuous coverage in the BMEW Region of Interest (ROI): 10°N to 40°N Latitude and 24°E to 63°E Longitude.

6.1.4 The payload will be capable of covering the designated ROI in a full staring mode and have sufficient sensitivity to detect theater ballistic missile threats and generate actionable missile warning reports.

6.1.5 The satellite will downlink data that can be processed on suitable ground equipment to generate BMEW reports. This message must be compatible with a C4I infrastructure and capable of supporting the cueing of THAAD and Patriot missile systems.

6.1.6 This capability will be considered delivered once successfully on orbit.

6.1.7 The payload will be single fault tolerant. All unavoidable single point failures will be treated as critical items.

6.1.8 The satellite bus and payload assembly will be designed to prevent predictable outages such as sun angle outages.

6.1.9 The payload and bus will achieve line of sight (LOS) stability as necessary to be able to detect theater ballistic missile threats.

6.1.10 The sensor sensitivity, frame rate, and noise reductions will be sufficient to detect theater ballistic missile threats.

6.1.11 The payload will embed the necessary metadata to facilitate ground data processing in the downlink data stream.

6.1.12 The satellite will provide command and telemetry links separate from the data downlink which are compatible with North Atlantic Treaty Organization (NATO) and other USG systems.

6.1.13 The satellite will have a command and telemetry system capable of decryption and encryption of all commanding and telemetry data.

6.1.14 The satellite will be capable of fully supporting all payload functions through all environments such as eclipses and normal functions such as station keeping maneuvers.

6.1.15 For any sensor data downlink, the satellite will have telemetry routed and combined with an encrypted data downlink in addition to the normal stand-alone telemetry downlink.

6.1.16 The satellite bus will be capable of receiving software loads to change satellite, data downlink or instrument payload configurations.

6.1.17 The satellite bus will be single fault tolerant. All unavoidable single point failures will be treated as critical items.

6.1.18 All telemetry data will be encrypted with commercially available methods.

6.1.19 This payload will use Commercial Communication Security (COMSEC) for encryption and decryption.

6.1.20 The satellite bus will be designed to provide control capabilities to perform satellite launch, early orbit maneuvers and related activities, on-orbit test and checkout, on-orbit operations, station keeping, orbital repositioning, platform and payload maintenance, and anomaly identification and resolution.

6.1.21 The satellite bus will have a common interface for easy integration of multiple payloads.

6.2. MILSATCOM

Provide a design for a MILSATCOM system in GEO with the following characteristics and/or requirements:

6.2.1 The satellite will be designed to support operations in geosynchronous orbit for a minimum of fifteen (15) years after completion of on orbit testing.

6.2.2 The Ka band payload will operate at 27.5 to 31GHz for the uplink, and at 17.7 to 21.2GHz for the downlink.

6.2.3 The total aggregate capacity of the Ka band payload will be no less than 20Gbps.

6.2.4 The satellite payload will be capable of providing star and mesh connectivity (service types such as point-to-point, broadcast, etc.) for the Ka band.

6.2.5 The satellite payload will be capable of providing continuous coverage in the Red Sea, the

Gulf of Aden, the Arabian Sea, the Gulf of Oman, and the Arabian Gulf. This coverage shall be augmented by the steerable beams that can be pointed to any location within the region bounded by the Black Sea, Somalia, Libya, and Pakistan.

6.2.6 The system will be capable of limited protected tactical waveforms.

6.2.7 The payload will provide the capability to route communications data from any uplink beam to any downlink beam in any supported frequency band.

6.2.8 The satellite will have a command and telemetry system capable of decryption and encryption of all commanding and telemetry data.

6.2.9 The satellite will be capable of fully supporting all payload functions through all environments such as eclipses and normal functions such as station keeping maneuvers.

6.2.10 For any sensor data downlink, the satellite will have telemetry routed and combined with an encrypted data downlink in addition to the normal stand-alone telemetry downlink.

6.2.11 The satellite bus will be capable of receiving software loads to change satellite, data downlink or instrument payload configurations.

6.2.12 The satellite will be single fault tolerant. All unavoidable single point failures will be treated as critical items.

6.2.13 All telemetry data will be encrypted with commercially available methods. The payload(s) will use Commercial COMSEC for encryption and decryption.

6.2.14 The satellite will have an Ultra High Frequency (UHF) Narrowband payload will be required as well as the ground processing segment. This includes all hardware and software for multi access waveform implementation.

6.2.15 The satellite bus will have a common interface for easy integration of multiple payloads.

6.2.16 The satellite bus will be designed to provide control capabilities to perform satellite launch, early orbit maneuvers and related activities, on-orbit test and checkout, on-orbit operations, station keeping, orbital repositioning, platform and payload maintenance, and anomaly identification and resolution.

6.3. Remote Tracking Station

Provide a system design for at least two (2) Remote Tracking Stations (RTS) with the following characteristics and/or requirements:

6.3.1 The RTS will be geographically distant from each other for resiliency.

6.3.2 The RTS will have enough apertures to be able to maintain on demand tracking, telemetry, and command (TT&C) contact with GEO Communication Satellites (COMSATs).

6.3.3 All RTS will be capable of commanding a satellite in GEO, in the event the satellite is tumbling.

6.3.4 The analog and digital equipment at all ground systems will have built in test capability to facilitate trouble shooting in the event of an anomaly and for training purposes.

6.3.5 All RTS will be capable of interfacing with the networks of the satellites described here.

This shall be done either directly or via a foreign cross domain solution device depending on the security domain of the data.

6.3.6 The RTS will provide terminal equipment and associated functions that can connect to either Ka or UHF frequency bands communication channels.

6.3.7 The RTS will be compatible with NATO standards.

6.3.8 Each RTS will be capable of uncrewed function for up to 7 days.

6.3.9 Open-source software and open standard will be used to the maximum extent practical.

6.3.10 Any software provided will have controls and firewalls to prevent intrusion by unauthorized users.

6.3.11 Software development for all ground systems (SATOC, user terminals, MDC, etc.) will be joint with the MoD.

6.3.12 To facilitate any new construction, land and utilities (power, water, communications links, heating, and air conditioning) will be made available and will be appropriately prepared.

6.4. Satellite Operations Center(s)

Provide a system design for at least two (2) Satellite Operation Centers (SATOC) with the following characteristics and/or requirements:

6.4.1 The SATOC will provide satellite C2, automated operations, and payload telemetry and tasking capabilities.

6.4.2 The SATOC will meet reliability and availability needs using methods such as geographic diversity and internal redundancy.

6.4.3 Each SATOC will include a full satellite simulator for every satellite type for the purposes of training and checking out all commands, including payload tasking command blocks prior to sending to any satellite.

6.4.4 The SATOC will be capable of downloading and displaying and archiving telemetry of each satellite while in contact with a ground station.

6.4.5 The SATOC will have the capability to create, archive, and encrypt commands for each satellite.

6.4.6 The SATOCs will be able to conduct the following activities or functions for TT&C:

6.4.6.1. Real time data processing

6.4.6.2. Offline data processing for post event analysis

6.4.6.3. Offline data processing to meet training requirements

6.4.7 Archives will be compatible with cloud-based services.

6.4.8 Each SATOC will be provisioned with the necessary test equipment to perform self-testing and in-orbit check outs at the beginning of life and throughout the life of the program for each satellite subsystem including the payloads.

6.4.9 The SATOCs will be compatible with the other satellite systems for wideband services.

6.4.10 The SATOCs will be capable of interfacing with the requested systems network, either directly or via a foreign cross domain solution (FCDS) device depending on the security domain of the data.

6.4.11 Utilities such as power, water, communications links, and environmental control (air conditioning and heating) will be provided.

6.4.12 Any software used for satellite control and monitoring will have the ability to retrieve, trend, and store data both in real time and offline for historical data both at the SATOC and in selected remote locations such as the mission data center.

6.4.13 Software and data will be provided to facilitate collision avoidance for every satellite.

6.4.14 Telemetry data will include associated metadata.

6.4.15 Software and data will be provided to facilitate collision avoidance for every satellite.

6.4.16 Open-source software and open standards will be used to the greatest extent practical.

6.4.17 All software will have controls and firewalls to prevent intrusion by unauthorized users.

6.4.18 Software development for all ground systems (SATOC, user terminals, Mission Data

Center [MDC], etc.) will be joint with the CENTCOM PN MoD.

6.4.19 All SATOCs will be capable of interfacing with existing fiber optic networks either directly or via a FCDS device depending on the security domain of the data.

6.4.20 Any data using cloud-based storage and processing will have appropriate backups to the greatest extent possible.

6.5. Mission Data Processing Centers

Provide a system design for at least two (2) Mission Data Centers (MDC) for data processing with the following characteristics and/or requirements:

6.5.1 The data processing system will be set up in at least two geographically separate locations and be capable of simultaneously operating at both (or more) locations.

6.5.2 The MDC will conduct the following activities or functions simultaneously:

6.5.2.1. Data download from existing satellite systems

6.5.2.2. Offline data processing for post event analysis

6.5.2.3. Offline data processing to meet training requirements

6.5.3 The MDC will be capable of simultaneously receiving data for all operational satellites including:

6.5.3.1. Existing CENTCOM PN MoD satellites systems

6.5.3.2. Satellites described herein

6.5.3.3. C4I or other ground systems (such as internet) in all in-country security domains

6.5.4 The MDC will operate in the CENTCOM PN secret domain.

6.5.5 The MDC will be capable of processing data streams with the following standards:

6.5.5.1. Data formats from existing CENTCOM PN MoD satellite systems

6.5.5.2. Formats created for satellite systems described here in

6.5.6 Data archives will store raw and processed data according to a user defined retention policy.

6.5.7 The interfaces from the satellite systems described here to the C4I and other CENTCOM PN MoD systems will avoid single points of failure as much as practical.

6.5.8 Open-source software, open standards, and widely accepted de-facto industry standards will be used to the maximum extent possible. This includes interfaces, features, and services of cloud platforms.

6.5.9 All software provided will have controls and firewalls to prevent intrusion by unauthorized users.

6.5.10 Software will be easily scalable in number of users and data processing needs for each user.

6.5.11 Software development for all ground systems (SATOC, user terminals, MDC, etc.) will be joint with the CENTCOM PN MoD.

6.5.12 In the event of a failure or service disruption, fail-over to a backup system will be automated to the greatest extent practical.

6.5.13 All essential systems will be capable of operating through an external power interruption.

6.5.14 Security controls will be provided for system operators and cyber defense operators.

6.6. Presentation Center

Provide a system design for a Presentation Center with the following characteristics and/or requirements:

6.6.1 The presentation center will be provided for hosting leadership, stakeholders, and media events.

6.6.2 The Presentation Center will have sufficient capacity to seat very important people (VIPs) and other personnel in a viewing area for major events such as a satellite launch with data shown on multiple customized displays.

6.6.3 The Presentation Center will be capable of ingesting data from inside and outside of the satellite systems described here in multiple security domains, such as satellite status.

6.6.4 Open-source software, open standards, and widely accepted de-facto industry standards will be used to the maximum extent possible. This includes interfaces, features, and services of cloud platforms.

6.6.5 All software provided will have controls and firewalls to prevent intrusion by unauthorized users.

6.6.6 Software will be easily scalable in number of users and data processing needs for each user.

6.6.7 Software development for all ground systems (SATOC, user terminals, MDC, etc.) will be joint with the CENTCOM PN MoD.

6.6.8 In the event of a failure or service disruption, fail-over to a backup system will be automated to the greatest extent practical. All essential systems will be capable of operating through an external power interruption.

6.6.9 Security controls will be provided for system operators and cyber defense operators.

6.6.10 Data archives will store raw and processed data according to a user defined retention policy.

6.6.11 The interfaces from the CENTCOM PN MoD satellites to the C4I and other MoD systems will avoid single points of failure as much as practical.

6.7. User Terminals

Provide a system design for at least two (2) fixed and one (1) transportable terminal with the following characteristics and/or requirements:

6.7.1 The user terminals will meet all transmit and receive performance requirements.

6.7.2 The user terminals will be able to transmit and receive encrypted data as appropriate for each terminal type.

6.7.3 The user terminals will be capable of interfacing with the existing systems and the C4I modernization systems using mutually agreed on common standards.

6.7.4 The user terminals will be selected based on exportable terminals.

6.7.5 Selected user terminals will provide terminal equipment and associated functions that can connect to multiple frequency bands such as Ku, Ka, X, L, and UHF through satellite wideband and narrowband communication channels.

6.7.6 Selected user terminals will provide voice, voice conferencing, video conferencing, and data interfaces.

6.7.7 Selected terminals will be capable of tracking the satellites in geosynchronous orbit to maintain satellites communications links.

6.7.8 The user terminals will be reliable and have a design life at least fifteen (15) years.

6.7.9 Selected user terminals will be able to generate and input simulated data from a user specified scenario (Primarily for training and testing purposes).

6.7.10 Open-source software and open standards will be used to the maximum extent possible.

6.7.11 Any software provided will have controls and firewalls to prevent intrusion by unauthorized users.

6.7.12 Selected user terminals will be interoperable with MoD and Joint Multi-National Space

Operations. For long-term, the networking services should be compatible and interoperable with NATO standards (such as for the narrowband UHF terminals) and protocols to the extent possible for joint multi-national space operations.

6.7.13 The user terminals will be compatible with the types of signals they are expected to receive with respect to parameters such as encryption/decryption standards, coding, modulation, and frequency hopping.

6.8. Site Surveys

6.8.1 Contractor will create site survey plans and support at least two (2) site surveys per ground segment location and associated facilities.

6.9. Operation and Sustainment

6.9.1 Operation and Sustainment support will be provided for both the MILSATCOM and

BMEW space vehicles and all associated ground segments. This shall include the lifespan of the space segments and two (2) years of prelaunch support for all ground segments.

6.10. Training

6.10.1 Provide training courses to be made available in country to the PN. This training will be made available at three different levels: Beginner, Advanced, and Trainer. The topics covered shall include the operation and maintenance of space vehicles, ground stations, payload data analysis. Documentation, tools, and all simulators will be made available.

6.11. Technical Interchange Meetings

6.11.1 Support Technical Interchange Meetings, planning conferences, review meetings, and other relevant meetings to be defined by the PN.

6.12. Launch Vehicle Procurement

6.12.1 All launch vehicles will be procured by the contractor. Each capability will be delivered on orbit.

6.13. System Integrator

A System Integrator will be provided with the following characteristics and/or requirements:

6.13.1 The system integrator will ensure that system components meet their respective requirements.

6.13.2 The system integrator will ensure that the ground system, space segment, and interfaces to other systems (such as C4I) operate together. This includes activities such as:

6.13.2.1. Performing end-to-end analyses

6.13.2.2. Ensuring measures of effectiveness are correct and compliant

6.13.2.3. Managing space-ground interfaces and ground-external interfaces

6.13.2.4. Working with the CENTCOM PN MoD to contract with

cooperative suppliers

6.13.3 The system integrator will manage the integration of any satellite to the launch vehicle, from shipment, to launch, to fully checked out on orbit. This includes but is not limited to:

6.13.3.1. Generation of the launch checklists

6.13.3.2. Mating the satellite to the launch vehicle

6.13.3.3. Test procedures

6.13.3.4. Console manuals

6.13.4 The system integrator will perform the detailed trade analyses to determine overall system configuration for the following:

6.13.4.1. Type and number of satellites in GEO

6.13.4.2. Type and number of launch vehicles

6.13.4.3. Type and number of ground stations

6.13.4.4. Overall system reliability and availability

6.13.4.5. Details of interfaces with other MoD systems and cloud services

6.13.4.6. Details of interfaces to existing CENTCOM PN MoD satellites

6.13.4.7. Ensure adequate reporting of spectrum information is implemented on the space and ground systems

6.13.5 The system integrator will provide engineering services to assist with securing and retaining spectrum, orbit types, and orbit slots reservations with the International Telecommunication Union (ITU) in support of current and planned MoD satellites.

6.13.6 The system integrator will manage upgrades by:

6.13.6.1. Clearly describing changes of configuration, the reasons for said changes and their benefits

6.13.6.2. Identify costs of the upgrades and provide acceptance certificates.

6.13.6.3. Clearly describe changes to operational procedures and maintenance procedures and schedules

6.13.6.4. Developing and enacting adequate training to ensure continuous operations

6.13.6.5. Clearly describe changes to implemented support arrangements, including costs

6.13.6.6. Provide costed options for installation, test, and verification for the system

6.13.6.7. Ensure the ability to revert to an earlier working version of software.

6.13.7 The system integrator will ensure the proper logistics are in place for all ground hardware, software, supplies, and documentation delivery to each site. This applies to initial construction and subsequent maintenance and operations.

6.13.8 If new buildings are required to be constructed the system integrator will work with the CENTCOM PN MoD and other contractor(s) to create an appropriate set of requirements for the buildings and any related infrastructure.

6.13.9 The system integrator will ensure that each major component supplier provides a complete program plan, and that all the program plans are reasonable and achievable.

6.13.10 The system integrator and contractors will use the Risk Management Framework (as defined in US National Institute of Standards Special Publication 800-37) to characterize the cyber security posture of developed and modified components and of the system of systems, and tailor their security controls from US National Institute of Standards Special Publication 800-53 in accordance with NIST SP 800-37.

6.13.11 The system integrator will ensure that all satellites will be resilient against communications and positioning jamming and spoofing attempts.

6.13.12 The system integrator will ensure that all ground systems will be resilient against communications, jamming, and spoofing attempts.

6.13.13 The system integrator will ensure every ground component (SATOC, RTS, user terminals, etc.) and satellite has an internal authoritative time source and the ability to receive updates from an external authoritative time source.

6.13.14 The system integrator will ensure the provision of a record to the CENTCOM PN MoD of the system configuration covering all system hardware, software, and documentation for all tested configurations and all operational configurations.

6.13.15 The system integrator will ensure adequate documentation is supplied for all system design, development, and analysis tools.

6.13.16 The system integrator will ensure the provision of any needed technical data and documentation for the understanding of system operation. This includes but is not limited to training manuals, system process descriptions, maintenance manuals, operations manuals, user manuals, and system test programs/procedures.

6.13.17 The system integrator will ensure the provision of interface control documents (or equivalent) for all internal and external interfaces.

6.13.18 The system integrator will ensure the provision of software documentation, including software functional descriptions and diagrams, Commercial Off the Shelf (COTS) software list with installation locations, license information and maintenance agreement status/expiry date for each copy, software development documents, known software defect lists, and event libraries. The systems integrator will ensure the following for software upgrades:

installation/update checkoff list(s) and configuration management plan(s).

6.13.19 The system integrator will ensure that all the software licenses are tracked and are kept current. This responsibility will transfer to the CENTCOM PN MoD when the systems are made operational.

6.13.20 The system integrator will ensure the provision of documentation outlining satellite operation and test data results for each satellite.

6.13.21 The system integrator will ensure the provision of documentation outlining ground operation and test data results for each location.

6.13.22 The system integrator will ensure the provision of an equipment safety summary that includes all identified hazards to the systems and its interfaces, identified design features incorporated to control each hazard, and details of safety assurance activities that have been undertaken.

6.13.23 The system integrator will ensure that all appropriate system site acceptance test reports, including initial and final operational test reports, will be provided to USG and CENTCOM PN MoD engineers.

6.13.24 The system integrator will ensure that every component/subsystem has a complete set of documentation which includes but is not limited to:

6.13.24.1. Test and Evaluation Master Plans (TEMP)

6.13.24.2. Full set of requirements traceable back to top level requirements,

6.13.24.3. Testing requirements trace matrix.

6.13.24.4. Program protection plans including cyber security plans

6.13.24.5. Operations manuals

6.13.24.6. Test and training environment(s) operations manuals.

6.13.25 The system integrator will provide a full system of systems integrated master schedule (IMS) with inputs from each major component supplier.

6.13.26 The system integrator will ensure that training is provided in country, and other sites as agreed with CENTCOM PN MoD.

6.13.27 The system integrator will ensure appropriate training classes and documentation for each class/course are created by the contractors.

6.13.28 The system integrator will ensure adequate training environment such as simulators/tools are provided to support training of operations personnel.

6.13.29 The system integrator will ensure that training will be provided for MoD personnel to perform shop replacement of units (SRU) and line replacement of units (LRU) in the various ground systems.

6.13.30 The system integrator will ensure that USG and CENTCOM PN MoD engineers have full visibility into the plans and installation at the ground sites.

6.13.31 The system integrator will work with the appropriate CENTCOM PN MoD to address specific plans and issues related to localization.

6.13.32 The system integrator will ensure the contractors conduct progress reviews such as preliminary design reviews, critical design reviews, pre-launch reviews, and final on-orbit acceptance reviews.

6.13.33 The system integrator will ensure the contractors make accommodations for a large delegation of USG and CENTCOM PN MoD personnel for progress reviews either on contractor premises or in the PN as mutually agreed.

6.13.34 The system integrator will ensure translation services are provided for English and Arabic.

6.13.35 The system integrator will ensure liaison services are provided for data sharing operations with the USG systems.

6.14. Programmatic

6.14.1 Access for USG, system integrator, and CENTCOM PN MoD engineers will be provided at the involved contractor facilities during system component design, build, and verification phases.

6.14.2 Access for USG, system integrator, and CENTCOM PN MoD engineers will be provided at the launch site(s) for the launch preparations, the launch, and post launch activities.

6.15. Testing

6.15.1 System testing will include full end-to-end tests and day-in-the-life tests.

6.15.2 The system integrator will manage and/or conduct system tests to verify system operation following delivery, on-site installation, and integration activities for the ground equipment.

6.16. Networking

6.16.1 Networking services for reliable comms between data centers, remote tracking stations, sat operation centers will be provided.

6.16.2 The Network Provider will provide a service level agreement with concrete requirements and measurable performance. That agreement will include the penalties for failure to meet that performance. This includes managing scheduled downtime for maintenance.

6.16.3 Network performance will be based on the application requirements.

6.16.4 The Network will provide infrastructure and services to transparently implement the redundancy (physical and otherwise) required to maintain application connectivity under failures of or damage to physical connectivity.

6.16.5 The Network will provide infrastructure and services to transparently implement the redundancy (physical and otherwise) required to maintain application connectivity under failures of or damage to physical connectivity.

6.16.6 The network provider will support the configuration of network partitions to separate resources to meet mission objectives. Such partitions may be physical or logical, dynamic, or static. When possible, the provider will provide schedules or notifications of changes to such partitions.

6.16.7 The network will provide firewalls, security, and controls to prevent intrusion by unauthorized users.

6.17. Requirements Mapping

6.17.1 Develop a requirements matrix or other traceability tool that enables the ability to verify and validate requirements.