MGEO_PWS_20250822.docx

MGEO COMSATCOM Contract Vehicle

Performance Work Statement (PWS)

FOR

Maneuverable Geosynchronous Orbit (MGEO) Commercial Satellite-Based Services Contract Vehicle

22 August 2025 Version 1.3

DRAFT

Controlled by: Commercial Satellite Communications Office (CSCO) CUI Category: PROCURE Distribution: NONE POC: ryan.s.langoski.civ@mail.mil

SECTION I – 1.0 Description of Services

1.1 General

Maneuverable Geosynchronous Orbit (MGEO) Commercial Satellite-Based Services Contract Vehicle.

1.2 Objective

The objective of this procurement is to create a contract vehicle that provides the United States military and other partners access to worldwide commercial satellite communication (COMSATCOM) services based on satellites in any form of geosynchronous (GEO) orbit and featuring both readily available and traditionally scarce satellite transmission bands; spacecraft supporting such services while also providing unconventional resilience due to the maneuverability and number of dispersed satellites involved; and other commercial satellite services that may support or benefit from being hosted on such satellites, operating worldwide, regionally, and on orbit. This combination of maneuverability using decentralized, spatially dispersed small and medium satellites increases the resilience of both the service overall and, in the case of COMSATCOM services, the signal for any particular user while employing existing user equipment and gateways. This Performance Work Statement (PWS) is intended to support the needs of Services, Combatant Commands (COCOMs), Defense agencies, other Federal Government agencies, and international coalition partners by providing access to the cited capabilities. To support this need with a consolidated vehicle for procurement of stated services the Government is pursuing a multiple-award indefinite delivery, indefinite quantity (IDIQ) contracting approach.

1.3 Scope

This IDIQ contract shall provide access to COMSATCOM and other services via multiple maneuverable GEO satellites providing service area flexibility, as well as monitoring and control of services, gateway services and equipment, terrestrial backhaul, field service representative (FSR) support, training, and other related services and capabilities.

Contractors supporting this contract shall be able to provide services including, but not limited to, building and/or providing access to required spacecraft sufficient for service as defined in a task order specification (for example, satellite communication services in one or more of the commercially available satellite bands and/or frequency bands reserved for Government operation when sponsored by the requiring activity); launching of procured spacecraft; providing telemetry, tracking, and command (TT&C) and flight operations for the spacecraft; providing ground landing location and gateway support; providing terrestrial backhaul from landing stations to Government ground entry points (GEPS) / points of presence (PoPs); provide the ability to maneuver the spacecraft from initial launch orbital slot to different regional orbital slots globally; ensure that spacecraft meets the size, weight, and power (SWaP) requirements of the Government constituting small to medium sized satellites. Contractors will not be asked to build and design GEO satellites of traditional size due to the cost and lead time on such efforts. However, the Government may request access to traditional sized satellites that are reaching end-of-life or are inclined but could be repositioned and leased by the Government.

The scope of this contract is limited by the intended orbital domain (GEO) and goal of resiliency through maneuverability and use of multiple transmission paths, not by the type of service that may be provided. Service categories that may be procured through task orders include, without limitation:

· Satellite communication services using any and all electromagnetic spectrum bands which may include but are not limited to:

· Ultra-high frequency (UHF) and very high frequency (VHF) bands

· Industrial, scientific, and medical bands

· L, S, C, and X bands

· Ku, Ka (both commercial Ka-band and military Ka-band when sponsored and coordinated with Government activities), V, and W bands

· Optical bands

· Remote sensing services observing and exploiting any and all phenomena, including but not limited to the bands listed above.

· Enhanced satellite communications capabilities, which may include, but are not limited to:

· Protected tactical waveform support;

· Integration into DoD gateways;

· Dedicated DoD private networks in the space segment;

· Alternative position, navigation and timing services;

· Enhanced communications services and capabilities including group communications, over the top services, secure communications, internet of things, and bulk data transport.

· Data products, and related services in support of militarily relevant capabilities, which may include but are not limited to:

· Weather services;

· Space domain transportation and infrastructure:

· On-orbit information services facilitating materiel access to/from or holding in space;

· On-orbit transfer services facilitating resiliency through maneuverability and use of multiple transmission paths;

· Space domain energy:

· On-orbit information services facilitating exploitation, utilization, or delivery of new, emerging, or anticipated energy sources and other assets;

· Space domain manufacturing:

· On-orbit information services enabling exploitation or production of space-based resources;

· On-orbit manufacturing services facilitating resiliency through maneuverability and use of multiple transmission paths;

· May not be focused solely on communication packages

· Combinations thereof or with additional capabilities.

Similarly, business models that may be utilized by services under this contract are not limited except as constrained by law and policy. Example approaches to provision of services that may be purchased via task orders under this contract include, without limitation:

· individual data or bandwidth service subscriptions on existing satellites;

· global or regional bandwidth capacity leases;

· wholly or partially dedicated satellites provided as-a-service;

· wholly or partially dedicated multi-satellite constellations provided as-a-service;

· wholly or partially dedicated communication payloads operated by the Government and hosted on satellites operated by the contractor;

· wholly dedicated payloads that are capable of supporting military frequency bands and supporting protected waveforms utilized by Government entities on satellites operated by the contractor;

· combinations thereof or with additional approaches.

The contractor shall provide the capabilities according to the requirements detailed in this PWS and the other contract documents. Specific requirements will be defined at the individual task order (TO) level. The specific tasks defined in the individual TO may supplement or replace the task requirements identified in this base PWS. Due to the natural evolution of the MGEO environment, additional services and/or support that may become available over the life of this contract and deemed desirable and within scope by the Government may be added through on-ramping or contract modifications.

1.4 Background

As the national security of the United States and its mission partners becomes ever more reliant on space-based capabilities, it is necessary to move in the direction of resilient constellations that can absorb satellite losses without jeopardizing the mission. Additionally, as traditional satellite resources / availability in both the commercial and military satellite sectors become more contested, there is a need for rapid access to new satellites in dispersed orbital slots. Currently, the commercial satellite communications industry has indicated a large shift towards managed service support over traditional transponded capacity support. Due to the needs of the DoD this reduction in traditional transponded capacity generates a security risk as numerous protected waveforms are not compatible with commercial managed services. Similar evolutions are taking place throughout the satellite industry. Combined with the need to supplement aging military satellite resources, the ability to provide these type of smaller, quicker satellite builds with maneuvering capabilities that are capable of providing access to, in particular, scarce military frequency bands is paramount to successfully supporting DoD operations and communication needs. Even with the DoD evolving to operate via commercial managed services, the need for traditional transponded capacity supporting protected waveforms and ensuring continued access to services capable of supplementing MILSATCOM is imperative.

SECTION II – 2.0 Technical Performance Requirements

The contractor shall provide and/or acquire the services, hardware, and software required by individual TOs pursuant to the requirements specified below, throughout the contract period of performance.

Individual TOs may encompass one or more of the tasks and subtasks below, in any combination. A TO may also define one or more additional tasks. Specific task requirements are not mutually exclusive and may apply across multiple tasks. Specific requirements will be detailed in individual TOs. Each requirement in a TO shall be detailed to the appropriate level to ensure the provided solution is achievable and provides the necessary objective result. Any TO that requires services will also require the contractor to provide an accompanying Service Level Agreement (SLA) to describe and commit to the service performance attributes and management procedures. Delivery schedule shall be defined for the base contract in section 4 below and/or additionally specified at the TO level. Standards for task performance are defined in section 3"Performance Standards" below and/or at the TO level.

2.1 Task 1 – Operational Packaged MGEO End-User Service

The contractor shall provide operational managed and/or leased-resource services via GEO commercial satellites anywhere in the world at locations and in quantities as specified at the TO level. The contractor shall provide services on satellites that are capable of maneuvering between orbital slots. The contractor shall be capable of supporting orders that require a range of service capacity from the smallest unit offered up to the full capacity of a leasable resource, including leasing an entire payload on each satellite. The contractor shall be responsible for positioning and orienting satellites, enabling resources, and reserving capacity accordingly. The contractor shall identify corresponding conflicts and limitations as necessary to assist the Government's mission planning efforts. Performance requirements are specified in Section 3 below, and/or at the TO level.

2.1.1 Subtask 1.1 – Resource Plan

The contractor shall provide Resource Plans which detail leased-resource service parameters. All leased-resource services shall operate in accordance with approved Resource Plans. Timeline for contractor to process and disseminate updated Resource Plans is 3 calendar days from receipt of Government request. A copy of all such plans shall be provided to the COR and the Regional Satellite Support Center (RSSC)-West. Each Resource Plan shall be submitted electronically in an appropriate format detailed at the TO level. This could include providing in both MS Excel format and XML format. The Government will provide the tool required to build and convert the Resource Plan to the XML format when required at the TO level. Each Resource Plan shall contain all information needed for users to access the resource, such as general plan metadata, satellite technical information, and service technical parameters, including but not limited to the following example fields. Required fields supplanting or supplementing these may be specified in a TO.

General Information:

Resource Technical Characteristics Table:

Service Technical Parameters Table:

• per Task Order Requirements

Deliverable: Resource Plan

2.1.2 Subtask 1.2 – Secure Ad-Hoc Satellite Tasking

The contractor shall provide a secure means whereby the Government may task satellite positions and orientations, beam states and frequencies, and other configurable parameters as may be defined in a TO, and where appropriate within the constraints of an applicable Resource Plan. Tasking performance requirements are specified in the PWS, and/or at the TO level. Access to information about and knowledge of such tasking shall be limited to approved personnel according to Section 6 herein and as refined by the requirements of a corresponding TO.

2.1.3 Subtask 1.3 – Gateway and Terrestrial Interconnect

The contractor shall provide compatible gateway service and corresponding terrestrial network interconnect at locations, to networks, and with performance as specified at the TO level. Refer to Task 4 below for associated equipment requirements.

2.1.4 Subtask 1.4 – Commercial Gateway Services and Leased Terrestrial Backhaul

The contractor shall provide Internet access at its commercial gateway or gateways, as specified at the TO level. The contractor shall provide leased terrestrial backhaul from the commercial gateway to a Government PoP to be specified at the TO level. Any commercial gateway shall meet an operational availability of 99.95 percent or better over each 30-calendar day period. The terrestrial connectivity from a commercial gateway to a Government PoP shall maintain a 99.95 percent operational availability or better over each 30-calendar day period.

2.2 Task 2 – Operational Customer Specific MGEO End-User Service

The contractor shall provide custom managed or leased-resource service via GEO commercial satellites anywhere in the world at locations and in quantities as specified at the TO level. The contractor shall provide services on satellites that are capable of maneuvering between orbital slots; including the ability to transition between orbital slots multiple times. These transitions may require quick traversal methods and the provided methods should weigh speed versus lifetime fuel impact. These services will be purchased in response to a specific end-user requirement and may differ in functions, performance, connectivity and equipment from the operational packaged MGEO end-user services sought under Task 1. Detailed requirements will be specified at the TO level. The contractor shall be responsible for positioning and orienting satellites, reserving/tasking resources, and allocating capacity accordingly. The contractor shall identify corresponding conflicts and limitations as necessary to assist the Government's mission planning efforts. Performance requirements are specified in the PWS, and/or at the TO level.

2.2.1 Subtask 2.1 – Commercial Gateway Services and Leased Terrestrial Backhaul

The contractor shall provide Internet access at its commercial gateway or gateways, as specified at the TO level. The contractor shall provide leased terrestrial backhaul from the commercial gateway to a Government PoP to be specified at the TO level. Any commercial gateway shall meet an operational availability of 99.95 percent or better over each 30-calendar day period. The terrestrial connectivity from a commercial gateway to a Government PoP shall maintain a 99.95 percent operational availability or better over each 30-calendar day period.

2.3 Task 3 – Pre-Operational, Experimental, or Trial MGEO End-User Service (Optional)

The Government may require support for prototype and experimental services that are considered pre-operational or that have not reached the fully operational capability stage. Required capabilities may include, but are not limited to, stress testing of pre-operational satellite networks, experimentation with space and terrestrial based equipment to determine support for multiple waveforms to include protected waveforms, or support for testing of hybrid network services in order to facilitate development of reliable, compatible, and secure end user services. Detailed requirements for this task, such as specific waveform support, will be specified at the TO level.

2.4 Task 4 – MGEO Equipment

The contractor shall ensure the availability for purchase or lease by the Government of compatible equipment required to utilize the service, as well as all ground connectivity to support services. Equipment support shall cover a range of TO requirements from customers providing their own equipment, which may include leased space for terminals, ancillary equipment, and rack space, to fully contractor provided equipment and connectivity.

2.4.1 Subtask 4.1 - End-User Terminal Equipment

The contractor shall provide all functional equipment needed to use any service provided under Task 1, for installation at Government user locations as specified at the TO level. All equipment shall be factory tested and appropriately packed for shipment. Shipping shall be billed under a separate CLIN as a pass-through charge, meaning the inclusion of all related shipping costs with no additional fee included. The contractor shall provide extended warranty maintenance and service plan for contractor-installed terminals in writing within 30-calendar days after receipt of order (ARO). The contractor shall ensure that equipment is certified for use with the provided service. The contractor shall provide on-site installation and maintenance of terminal equipment as specified at the TO level, via Field Service Representatives as described in Section 2.4.8.

Deliverables: Terminal Equipment, Extended Warranty / Service Plan

2.4.2 Subtask 4.2 - Ground System Equipment

The contractor shall provide MGEO ground system equipment for installation at Government locations as specified at the TO level, which may include but is not limited to communications gateway equipment, network operations equipment, and secure tasking equipment. All equipment shall be factory tested and appropriately packed for shipment. Shipping shall be billed under a separate CLIN as a pass-through charge. The contractor shall provide extended warranty maintenance and service plan for contractor-installed equipment in writing within 30 calendar days ARO. The contractor shall ensure that equipment is certified for use with the satellite constellation. The contractor shall provide on-site installation and maintenance of gateway equipment as specified at the TO level, via Field Service Representatives as described in Section 2.9.1.

Deliverables: Ground System Equipment, Extended Warranty / Service Plan

2.4.3 Subtask 4.3 - Satellites and Satellite Payloads On-Orbit Equipment

The contractor shall produce and deliver to orbit satellites and/or satellite payloads as specified in a TO. All equipment shall be factory tested prior to launch and appropriately verified on orbit prior to operation.

2.5 Task 5 – MGEO Infrastructure Packaged Operations Service (OPTIONAL)

2.5.1 – Subtask 5.1 – Telemetry, Tracking, and Command (TT&C) and Flight Operations

The contractor shall provide TT&C of the spacecraft for the life of the vehicle. The contractor shall be responsible for all flight operations of the spacecraft, to include the necessary positioning and orienting of the spacecraft to provide the necessary operational support of the Government. TT&C requirements shall also apply to any flight operations necessary to reposition spacecraft tasked with maneuvering between different regional and inter-regional orbital slots globally. The contractor shall demonstrate the ability to provide TT&C and flight operations from contractor chosen facilities or, when required, from facilities chosen by and sponsored by the Government. Government requirements for the operational location will be specified at the TO level.

2.5.1.1 When orbital relocation maneuvering is required, the contractor shall provide all relevant information to the Government related to the specifications of the maneuver, to include but not limited to spacecraft delta-v and fuel load impact; speed of relocation to include expected operational date in new orbital location; number of anticipated maneuvers remaining following relocation operations; additional information that may be requested by the Government and specified at the TO level.

2.5.2 – Subtask 5.2 – Spacecraft Traffic Landing and Gateway Support

The contractor shall provide ground landing locations and services for all user traffic supported by the spacecraft. The contractor shall be responsible for coordination of landing rights in regions supported by the spacecraft and shall ensure that the landing location supporting user traffic is capable of providing terrestrial backhaul from landing stations to GEPS / points of presence (PoPs). Should the Government require support from facilities chosen by and sponsored by the Government, the Government will assist in necessary coordination actions and will specify these requirements at the TO level.

2.6 Task 6 – MGEO Infrastructure Customer Specific Operations Service (OPTIONAL)

The contractormay be required to provide custom operations services as specified at the TO level. These services will be purchased in response to a specific requirement and may differ in functions, performance, connectivity and equipment from the operational packaged MGEO infrastructure operations services sought under Task 5. Detailed requirements will be specified at the TO level. Performance requirements are specified in Section 3below, and/or at the TO level.

2.7 Task 7 – MGEO Infrastructure Equipment (OPTIONAL)

The contractor may be required to provide the ability to support for the development, launch, and control of a purpose-built GEO satellites capable of supporting the communication and maneuverability needs of the Government.

2.7.1 Subtask 7.1 – Manufacturing Maneuverable Spacecraft

The contractor shall provide the ability to develop and manufacture a spacecraft that is capable of providing Government specified payloads; including the ability to build a spacecraft that is capable of providing service in all commercially available satellite bands and/or frequency bands reserved for Government operation when sponsored by the requiring activity. This requirement includes, but is not limited to, UHF, VHF, L, S, Ku, Ka, and X bands. Specifics of the spacecraft will be provided in accordance with Subtask 2.7.3 – SWaP below and/or specified at the TO level.

2.7.1.1 The contractor shall provide this capability in a timeframe that meets the operational needs of the Government. The contractor shall provide the manufactured spacecraft to launch in a period not to exceed 30-months.

2.7.1.2 The contractor shall provide engineering expertise to assist in the design, development, and optimization of satellite systems in order to ensure reliability, performance, and compliance with regulatory standards. The contractor shall be capable of providing a cost sheet for the production and delivery of the spacecraft based on the Government’s requested designs elements. This cost sheet will be provided for Government acceptance within 30 calendar days of the design acceptance. Required engineering expertise for bespoke requirements relating to satellite design will be specified at the TO level and may result in a separate design services TO.

2.7.1.3 The contractor shall provide engineering expertise to support ground testing of the spacecraft for Government acceptance. Spacecraft system testing shall include industry standard and best practice space system design qualifications and acceptance testing as outlined in applicable International Organization for Standardization (ISO) documents, as well as applicable DoD regulations. Specific applicable documents will be identified at the TO level.

2.7.2 Subtask 7.2 – Launch Services and ITU Coordination for Procured Spacecraft

The contractor shall provide the ability to launch any built Government spacecraft and provide the necessary actions to raise the spacecraft to GEO orbit and position the spacecraft in the assigned orbital slot. For any system procured by the Government, the contractor will be responsible for all launch activities. During the build process, the contractor shall ensure coordination with the International Telecommunication Union (ITU) to ensure the spacecraft is approved for positioning in the required orbital slot location. When the Government provides multiple pre-determined orbital slot locations in which the spacecraft may reside over the life of the vehicle, the contractor shall ensure all necessary coordination and approvals are obtained to support the launch and raising of the spacecraft for operation. Government orbital locations will be specified at the TO level.

2.7.2.1 The contractor shall ensure compliance with regulatory requirements, including spectrum allocation, licensing, and international agreements, in order to ensure interference-free operation of the spacecraft.

2.7.3 – Subtask 7.3 – Size, Weight, and Power Requirements

Requirements to support this subtask shall be specified at the TO level. The Government may specify parameters, to include but not limited to, payload capabilities, maneuverability, and required lifespan of the spacecraft. When the Government provides capability requirements, the contactor shall be responsible for determining the Size, Weight and Power (SWaP) requirements necessary to support the requested services under this task. When the Government has a requirement to meet specific SWaP requirements, such as providing a specific hosted DoD payload, the Government will provide the minimum requirements to support the payload.

2.8 Task 8 - Reporting

All levels of classified access to include SIPRNET, COMSEC and TEMPEST requirements associated with Task 8 will be imposed at the TO level as required. The contractor shall comply with the following reporting requirements:

2.8.1 – System Architecture

The contractor shall provide, within 30 days of contract award under the initial TO, high-level system architecture briefings, explanations, and diagrams regarding the inner workings of the system in support of the Government’s requirements and requests as part of the initial minimum order. A full plan for these items will be provided for Government approval within 120 days following award. This information may be considered proprietary by the contractor and proprietary information shall only be used to address specific Government questions and concerns generally related to system and service operations, security, vulnerabilities, functions, performance, supply chain including key partnerships, and similar attributes of the supplied services and corresponding infrastructure. The contractor shall conduct technical briefings regarding the system architecture as requested by the Program Management Office (PMO) or contracting activity.

2.8.2 – Service Operations Monitoring and User Near Real-Time Usage Reporting

Upon commencement of any operational service under a TO, and continuing throughout the contract period for that TO, the contractor shall collect and deliver near real-time usage, monitoring, fault/incident/outage reporting, and information access to ensure effective and efficient operations, performance, and availability consistent with commercial best practice. Near real-time usage refers to the timeliness of data or information which has been delayed only by the time required for electronic communication and automatic data processing. Total delay objective in network operations information availability, as measured from incident detection to incident reporting, shall be five minutes or less; threshold reporting delay shall match commercial operation best practice. The contractor’s NetOps monitoring capability shall address the following metrics at a minimum: current and past usage reporting, system/network outages (space, ground, transport, operations, etc.), fault reporting, and user terminal status (for all supplied under this PWS in each contractor provided MGEO system). Additional service-specific metrics will be specified in each TO, such as data throughput (usage) indicators over time in sufficient granularity to support ongoing operations and issue identification and resolution.

As part of any commercial service offering furnished under this PWS, the contractor shall provide an online account management tool capability accessible by the Government to report service usage, both aggregated and for each user account, and to manage users' access to services and capabilities. Usage information shall be updated at a minimum daily. Usage information shall indicate the time period to which the data is related. MGEO users shall be able to see monthly and cumulative information. The contractor’s account management solution shall allow a MGEO service user to query their usage data over a user-specified period. It shall also allow Government service managers to enable and disable an individual user's service as well as to change user subscription options such as billing group or other service-specific options. The account management tool shall support a user access hierarchy per industry best practices, which limits access to information and controls as defined for each user. Information fields that users shall have the ability to access will depend on the nature of each specific service and should be described in the associated SLA.

Additional service-specific usage database fields will be specified in each TO and will align with commercial best practices.

2.8.3 – Service Availability Reporting

Upon commencement of any operational service under a TO, and continuing throughout the contract period for that TO, the contractor shall perform and report service availability measurements. Final system availability metrics used for reporting service availability against this contract and the methods and time windows for collecting and reporting them shall be by mutual agreement of the parties and shall include all downtime observations used to calculate system availability as required in Table 7-2.

2.8.4 – Service Activation Reporting

Upon commencement of any operational service under a TO, and continuing throughout the contract period for that TO, the contractor shall report the status of all service activations by the 5th business day of each month. For each service account identified in the service activation plan, the monthly status report shall document the service activation date, new service account information, service authorization information, and the type of service provided, significant issues and any other salient information as established in the service activation plan.

2.8.5 – Monthly Status Reporting (MSR)

Upon commencement of any operational service under a TO, and continuing throughout the contract period for that TO, the contractor shall deliver a MSR to the COR, KO, Contract Specialist (CS), and the-RSSC-West. The MSR is due by the 5th business day of each month and shall cover information from the previous month. The MSR contents shall be by mutual agreement of the parties as documented in relevant Task Orders but shall include at a minimum:

• Top ten risks and associated mitigation plans

• Service activation status

• Troubleshooting and customer assistance provided

• Usage and fault reporting process updates

• Host nation agreement (HNA), licensing, and related issues (if required)

• Planned changes

• Availability of all items on the MGEO equipment list (if applicable)

• IA Status

A summary of expedited/emergency activation of subscriptions and terminals in Government possession shall be included in the MSR.

The contractor shall confirm that all personnel, to include any new personnel on the contract, have executed the Government-provided Nondisclosure Agreement (NDA) (Attachment 8) and the NDA is current as of the date of the MSR. MSRs shall be sent to the KOs and CORs.

2.8.6 – Fault and Service Outage Reporting

Upon commencement of any operational service under a TO, and continuing throughout the contract period for that TO, the contractor shall provide automated, verbal and written status reports to the RSSC-West, COR, and other designated POCs in accordance with timelines, formats, protocols, and escalation procedures to be agreed by the parties and documented in the Communications and Escalation Plan outlined in paragraph 2.9.5 to be submitted 30 calendar days following base contract award.

Fault information includes detection, identification, and isolation of problems that negatively affect any service, as well as initiation, tracking, and completion of corresponding corrective actions. A service outage is the inability to provide service to any user in any part of the coverage area. In the event of a service outage, the contractor shall pro-vide verbal and written status reports to the RSSC-West, COR, and other designated POCs in accordance with timelines, formats, protocols, and escalation procedures to be agreed by the parties and documented in the Communications and Escalation Plan.

2.8.7 – Information Assurance Reporting

IA is applicable to satellite access centers, satellites, and contractor enclaves controlling/managing satellite resources.

The contractor shall maintain compliance with applicable IA policies as defied in the COMSATCOM Information Assurance Questionnaire (CIAQ) and/or any other applicable process that may supplement or supersede the CIAQ. To ensure this compliance, the contractor shall submit, on the 5th calendar day of each month, an IA monthly report deliverable to the COR. This is to be included in the MSR per PWS 2.8.5 above.

Not more than 30 calendar days following base contract award, the contractor shall provide a completed COMSATCOM Information Assurance Questionnaire (CIAQ) that details the contractor solution IA security posture. The CIAQ must be submitted in its original Microsoft Excel format with the technical quotation. A single CIAQ must document all applicable system segments (corporate systems not involved in service operations need not be reported upon). National Security Agency Cryptography is acceptable. As a minimum, cryptography generally commensurate with commercial best practices is also acceptable if the Government determines that normal or special contractor emphasis and normal or close Government monitoring will likely be able to overcome any schedule, cost/price, and/or performance issues.

Upon commencement of any operational service under a TO, and continuing throughout the contract period for that TO, the contractor shall continually monitor and verify IA is in compliance with the contractor’s security posture as documented in the CIAQ.

IA incident notification shall be made within 24 hours; detailed incident report is provided within 5 business days.

• Reports should highlight network events that have occurred during the last reporting period, and a plan of action and milestones for unresolved events that occurred within the reporting period.

• Reports may also include changes to the network that have occurred unrelated to events.

• Reports shall be submitted in a Microsoft Word (.doc) or .PDF file format that provides a written summary of events/changes for the reporting period.

At some point during the contract period of performance, the Government intends to implement the Information Assessment Pre-Assessment (IA-PRE) program which will replace the current CIAQ process. This change will be made by contract modification at a later date.

The contractor shall provide their IA/Incident Reporting process 30 calendar days following contract award under the initial TO. Final IA implementation and reporting requirements will be as mutually agreed upon.

2.8.8 – Task Order Status Reporting

Upon commencement of any operational service under a TO, and continuing throughout the contract period for that TO, the contractor shall provide weekly updates (during normal business hours) to the COR on the current status of all in-process task orders (task orders that have not been delivered) in order to ensure that current equipment order information is available. Weekly updates shall include (at a minimum): task order number, task order customer point of contact (POC), equipment type/model, quantities, shipment date, and warranty start and end dates. The weekly updates shall be provided per the deliverables schedule and shall include data for the previous week. Availability of all items on the MGEO equipment list shall be included in the monthly status report (MSR).

2.9 Task 9 – Service Management

All levels of classified access to include SIPRNET, COMSEC, and TEMPEST requirements associated with Task 9 will be imposed at the Task Order level as required. The contractor shall comply with the following service management requirements:

2.9.1 – Customer Service and Support

Upon commencement of any operational service under a TO, and continuing throughout the contract period for that TO, the contractor shall, included as part of said services, provide English speaking technicians 24x7 as help desk technical support for the contractor’s services and equipment as well as government-specific capabilities provided by the contractor, if any, in accordance with a communication and escalation procedures to be agreed by the parties and documented in the Communications and Escalation Plan. Access to the help desk shall be made available by phone, e-mail, chat, text, video call and remote access to user devices as required by the specifics of the situation. Help desk support shall cover Tier 1- basic help desk resolution, Tier 2 – in-depth technical support and Tier 3 – expert technical support. Resolution times for Tier 1, Tier 2 and Tier 3 support shall be within 1 calendar day, 2 calendar days and 7 calendar days of initial help desk contact respectively.

Customer service support to handle billing questions, contract related inquiries, and any online account management tool queries shall be available, at a minimum, Monday through Friday 7:00 a.m. to 5:00 p.m. eastern time, excluding United States Government holidays.

The contractor shall provide field service representatives to support initial installation, configuration, and activation tasks, as well as ongoing operations and maintenance activities as necessary to maintain equipment and service access. Field service support shall be available on an annual and ad-hoc daily basis if required. FSR support will be addressed as required at the TO level.

2.9.2 – Travel/Temporary Duty (TDY)

Travel may be required and established at the TO level and billed as a cost reimbursable item. All travel associated with this contract shall be in accordance with FAR Part 31.205-46.

6. For service calls requiring contractor travel to a remote location inaccessible through commercial air transportation, the contractor shall work with the COR (or other DoD office if stipulated in the TO) to arrange provision of DoD travel to the remote site. The contractor will not be penalized for performance or service delays resulting from delays in DoD transportation availability.

2.9.3 – Training

The contractor shall provide training needed to use the contracted service as agreed upon under each TO. Specifically, the contractor shall provide an initial training session of the online account management tool (presentation method to be agreed upon in the TO) and any equipment and services purchased as part of the TO to both CSCO and DoD representatives within 15 calendar days of the start of the first operational service provided on the task or-der. The session(s) will cover navigation, reports or data query generation, and management of user permissions within the tool. Training materials or soft copies of instructions shall be provided to users as they obtain services.

2.9.4 – Service Activation Plan (SAP)

Not more than 30 calendar days following base contract award, the contractor shall present a written SAP to the Government, detailing the contractor’s approach to providing service activation. The SAP shall outline the steps required to activate service including a timeline from receipt of TO through successful service activation.

2.9.5 – Communications and Escalation Plan

The contractor shall provide a Communications and Escalation Plan including, at a minimum, the contractor’s proposed communications and escalation procedures relative to faults (refer to section 2.8.6, service interruptions, anomalies, EMI/RFI incidents, customer service and support (refer to section 2.9.7), and other items that could negatively impact any aspect of the user experience associated with service provided. The plan shall include at a minimum the contractor’s proposed timelines, formats and protocols for communications and escalation and shall be submitted 30 calendar days following base contract award under the initial TO and shall be mutually agreed upon between the Contractor and the Government. The plan shall be updated as required based on the mutual agreement of the parties.

2.9.6 – Service Suspension

DoD representatives, CSCO, or customers who are granted authority by the KO may request service suspension during the contract as a management tool to control service access when the users cannot account for their equipment or services. To suspend service, service representatives, CSCO, or customers who are granted authority will notify the contractor requesting suspension of services on the specified subscription or terminal. The contractor shall notify the service provider/value added reseller and end user of the date of suspension, thus restricting all access. Service suspension is not a discontinuation of service or cancellation of the task order, this is the physical turning on and off of service terminals.

2.9.7 - Electro Magnetic Interference (EMI)/Radio Frequency Interference (RFI) Identification, Characterization, and Geo-location

While any TO is under contract, the contractor shall provide EMI/RFI identification, characterization, geo-location, and resolution in accordance with protocols and escalation procedures to be agreed by the parties in the Communications and Escalation Plan outlined in paragraph 2.9.5. The objective is to satisfy the goals and procedures of the U.S. Strategic Command (USSTRATCOM) EMI/RFI Reporting.

Deliverables: EMI/RFI Reporting Checklist, Summary of Action Report

2.9.8 – Frequency Clearances and Approvals

The contractor is responsible for and shall secure all local, national and international approvals and licenses to operate and provide services provided under this PWS including but not limited to HNAs, host nation approvals, landing rights, operating agreements, site licenses, frequency clearances, and international approvals for radio spectrum operations for DoD to access the entire contractor service coverage area. Frequency clearances and approvals for coverage areas proposed shall be available prior to contract award. These are not separate charges as they are already established by the contractor as part of their operating a commercial service in the coverage area. The contractor shall provide the Government with copies of regulatory licenses and approvals obtained to operate and use the spectrum for countries within the required service region.

Deliverables: Regulatory / HNA Support Effort Report

2.9.9 – Service Management Plan

The contractor shall provide within 30 calendar days of base contract award a service management plan that details the approach the contractor will use to manage all of the aspects of service delivery. The plan shall include documents, policies, procedures, briefings, explanations, and diagrams regarding the approach taken to manage the offered services in support of the Government’s requirements and requests. This information may be considered proprietary by the contractor and proprietary information shall only be used to address specific Government questions and concerns generally related to system and service operations, security, vulnerabilities, functions, performance, supply chain including key partnerships, and similar attributes of the supplied services and corresponding infrastructure. The contractor shall conduct technical briefings regarding the service management plan as requested by the PMO or Contracting Activity.

2.10 Task 10 – Initial Task Order

Within 30 days of base contract award, the contractor shall provide the following data (defined in Section 6 above) which comprises the Initial Task Order:

· 2.8.1 - System Architecture

· 2.8.7 - COMSATCOM Information Assurance Questionnaire (CIAQ)

· 2.9.4 - Service Activation Plan

· 2.9.5 - Communications and Escalation Plan

· 2.9.9 - Service Management Plan

· Deliverables list in Table 2-2 below

Table 2-2. Task 10 - Initial Task Order Deliverables

All deliverables shall be delivered electronically to the Contracting Officer, COR and RSSC-West (rsscwest.commercial@us.af.mil), unless otherwise specified in this table. 6.6.10

SECTION III – 3.0 Service Summary (Performance Requirements & Standards)

3.1 Performance Requirements

3.1.1 Operational Packaged MGEO End-User Service Requirements

The contractor shall provide Operational Packaged MGEO End-User Service, as listed in section 2.1, ensuring access to transponded services on satellites that meet all required performance indicators specified at the task order level, which may include:

· Maneuverable spacecraft

· Services leased at the transponder level up to full payload leasing

Additional service-specific parameters will be defined and required at that TO level to include items such as frequency band, regional location, maneuvering requirements, etc.

3.1.2 Operational Customer Specific MGEO End-User Service

The contractor shall provide Operational Customer Specific MGEO End-User Service, as listed in section 2.2, ensuring access to operational managed services / broadband data services on satellites that meet all required performance indicators specified at the task order level.

3.1.3 Pre-Operational, Experimental, or Trial MGEO End-User Service

If offered, the contractor shall provide access to Pre-Operational, Experimental, or Trial MGEO End-User Service, as listed in section 2.3, ensuring access to services supported via non-traditional satellites or user equipment capable of supporting performance indicators specified at the task order level.

3.1.4 MGEO End-User Equipment

The contractor shall provide access to, and support, MGEO End-User Equipment, as listed in section 2.4, providing a wide range of equipment options which may include support for compatible user terminals, gateway equipment, and commercial services / leased terrestrial backhaul which shall meet all operational parameters specified at the TO level and the following:

· Any commercial gateway shall meet an operational availability of 99.95 percent over each 30-calendar day period. The terrestrial connectivity from a commercial gateway to a Government PoP shall maintain a 99.95 percent operational availability over each 30-calendar day period.

3.1.5 MGEO Infrastructure Packaged Operations Service

If offered, the contractor shall provide access to and support for MGEO Infrastructure Packaged Operations Service, as listed in section 2.5, that meets all required performance indicators specified at the task order level.

3.1.6 MGEO Infrastructure Customer Specific Operations Service

If offered, the contractor shall provide access to and support for MGEO Infrastructure…