PLEO SBS0035 RFP Performance Work Statement (PWS)_AMD001.docx

Proliferated Low Earth Orbit (PLEO) Satellite-Based Services (SBS)

Performance Work Statement (PWS)

Version 1 13 October 2022 Department of Defense Defense Information Systems Agency P.O. Box 549 Ft. Meade, MD 20755-0549

Contents

PERFORMANCE WORK STATEMENT (PWS)

Multiple Award Indefinite Delivery, Indefinite Quantity (ID/IQ) Contract for Proliferated Low Earth Orbit (PLEO) Satellite-Based Services (SBS)

Award

1. Contracting Officer’s Representative (COR)

Primary COR, See Clause G1, Points of Contact.

2. Contract or Task Order Title

Multiple Award Indefinite Delivery, ID/IQ Contract for PLEO SBS

3. 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. Currently industry is implementing several large constellations of small satellites in Low Earth Orbit (LEO). The PLEO constellations are a means of providing additional resilience to Department of Defense (DoD) satellite communications (SATCOM), remote sensing, and other capabilities. The industry intent is to leverage small satellite technology, reduced costs, and increased launch service competition to dramatically increase the number of commercial satellites in lower orbits, facilitating the ability for PLEO constellations to provide persistent, global coverage with reduced communications, tasking, or data delivery latency.

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 with a suite of fully managed satellite-based services and capabilities supporting all domains (space, air, land, maritime, cyber) and use cases with a consistent, quality backed, low latency offering.

4. Objectives

The objective of this procurement is to provide worldwide, low-latency PLEO services and capabilities to DoD mission partners to meet mission needs. Further, the intent is to provide a contracting vehicle that provides access to existing PLEO capabilities and emerging capabilities. To accomplish this objective, the Government is pursuing a multiple award Indefinite Delivery/Indefinite Quantity (IDIQ) contracting approach for this procurement.

As used in this specification, a Service Level Agreement (SLA) is a declaration of the technical performance commitments/thresholds and targets/objectives for the service package to which it applies. The IDIQ contract in-corporates the service offerings and their corresponding costs and performance. Each ordered service package will be incorporated into the corresponding Task Order, as agreed upon service level and performance standards. No SLA may contain any statement that modifies or interferes with the Government's prescribed/standard contract terms and conditions within the contract. Each SLA should contain the information described in the Attachment 5 SLA Template.

To provide the maximum flexibility to users, the contractor is expected to offer PLEO services based on two primary models: (1) standard service offerings subject to contractual Terms and Conditions and applicable SLAs, potentially purchased in bulk; and (2) customer specific service offerings based on individual customer and/or unique customer needs. Under the latter, service provided may become standard service offerings if useful to other customers. Moreover, it is the intent to use a la carte priced options for emerging/new capabilities as they become available. In order for the Government to evaluate suitability for specific mission needs it is essential to understand the proposed solution’s end-to-end architecture. Considerations include, but are not limited to, user terminal exposure, authentication and meta data, protection of sensitive user information, anonymity, and cyber security measures. To assist in the determination of the extent to which furnished services are applicable to meet mission needs, the contractor is expected to provide implementation plans and information necessary to validate capabilities throughout the life of the contract.

In addition, the contractor shall define any partnerships that are required to provide end-to-end service under this contract as well as the management process in place to manage these partnerships.

5. Scope

This ID/IQ contract shall provide PLEO services and equipment at the task order level. The contractor shall provide the products and services to support PLEO Satellite-Based Service solutions, including equipment as appropriate. The contractor shall report usage, service quality, and outages. In addition, the contractor shall provide equipment, training, operational expertise, and customer service and support for the PLEO services.

The contractor shall provide the capabilities as described in this PWS. Specific requirements will be defined at the individual task order (TO) level. The specific tasks defined in the individual TO may supplement, but not replace, the task requirements identified in this base PWS. Due to the natural evolution of the PLEO environment, additional PLEO 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.

The scope of this contract covers the following kinds of services:

Low-latency services and capabilities provided by or through or otherwise deriving from PLEO satellites for all domains and use cases. This includes SATCOM, remote sensing, or other effects, in all forms of capability including user independent, direct to user, user to user, and user reach-back. This also includes end-to-end managed services via subscription offerings defined under an SLA, as well as ancillary services such as terrestrial backhaul.

Airtime, data products, customer care, cyber/Information Assurance (IA), backhaul, terminals, and service management.

Services prior to initial commercial operational capability for test/integration capability to allow DoD early adopters to integrate with mission capabilities enabled by PLEO.

Satellites in other orbits may be used to supplement support of PLEO requirement(s) solutions.

Any and all electromagnetic spectrum bands and observable and/or exploitable behaviors whether explicitly licensed for space to ground communications use or not, which may include but are not limited to:

· Ultra-high frequency and very high frequency bands

· Cellular bands

· Industrial, scientific, and medical bands

· L, S, C, and X bands

· Ku, Ka, V, and W bands

· Optical bands Basic satellite communications capabilities, which may include, but are not limited to:

· "Broadband" continuous network connectivity

· "Store-and-Forward" message delivery

· "4G/5G Cellular" radio access network (satellite radio access network, 5G non-terrestrial networks) 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.

Satellite-based effects, data products, and related services in support of militarily relevant capabilities, which may include but are not limited to:

· Weather services

· Remote sensing services

· Space domain transportation and infrastructure Any/all information capabilities facilitating human and materiel access to/from space or sheltering in space;

· Space domain energy Any/all information capabilities facilitating exploitation, utilization, or delivery of new, emerging, or anticipated energy sources and other assets;

· Space domain manufacturing Any/all information capabilities enabling exploitation or production of space-based resources

6. Tasks, Specific Requirements & Deliverables

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.

The contractor shall furnish a copy of the valid, current Federal Communication Commission or other applicable regulatory filings for all PLEO constellations and services provided prior to offering services under this PWS.

Individual TOs may encompass one or more of the tasks below. Specific task requirements are not mutually exclusive and may apply across multiple tasks. Specific requirements will be detailed in individual TOs. Delivery schedule is defined for the base contract in section 6 and 7 below. Standards for task performance are defined in section 8 "Performance Standards" below.

6.1 Task 1 - Operational Packaged PLEO Service

The contractor shall provide operational packaged PLEO services. This service shall consist of various service offerings provided as end-to-end managed services that mirror the contractor’s commercial offerings.

Each service provided under this task shall be documented by an SLA that specifies pertinent threshold and objective performance parameters of the service to which the contractor shall commit. Such parameters may include, without limitation, minimum guaranteed data throughput or product/effect delivery frequency, maximum permitted data throughput or product/effect delivery frequency, maximum guaranteed data or product/effect latency, minimum guaranteed service availability percentage, and useful combinations of those and other such parameters.

Proposed operational packaged PLEO services not available at the time of initial contract award, shall be available from the contractor within 36 months of contract award.

6.2 Task 2 - Operational Customer Specific PLEO Service

The service provided under this section shall conform to the requirements stated in the TO for the operational customer specific services. 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 PLEO service described in section 6.1.

Operational customer specific PLEO services shall meet the performance requirements stated in section 7.2 below as well as any additional or modified requirements specified in the TO.

Operational customer specific PLEO services shall be deemed acceptable for DoD missions prior to award of a task order for those services. This permission is predicated on the contractor’s ability to demonstrate compliance with the operational requirements of this PWS and the ability of those services to be provided in a manner appropriate for DoD’s operational mission requirements.

6.3 Task 3 - Initial, Limited Use PLEO Service (Optional)

If offered on a task order, the contractor shall provide trial or demonstration capabilities and capacity to the Government prior to the commercial operational capability of the host constellation. Services furnished may include but are not limited to airtime, data products, end-to-end demonstration managed services or segments of service, network interconnects, platform and network integration services, business services including billing, system/network status, customer care, engineering, support, and other services and equipment in support of Government trial and limited use demonstrations of contractor’s services and systems.

The objective of the initial, limited use service is to provide an opportunity for the Government to evaluate the commercial service offerings and determine its suitability for various operational scenarios and requirements. This service shall be used exclusively for evaluation purposes and shall not support mission or mission critical functions at any time. Each service provided under a TO in this task shall be governed by a SLA that specifies pertinent threshold and objective performance parameters of the service to which the contractor shall commit. Such parameters may include, without limitation, minimum guaranteed data throughput or product/effect delivery frequency, maximum permitted data throughput or product/effect delivery frequency, maximum guaranteed data or product/effect latency, minimum guaranteed service availability percentage, and useful combinations of those and other such parameters.

Initial, limited use PLEO services shall be available for activation within 12 months of contract award.

6.4 Task 4 - Equipment

If compatible equipment is required to utilize the service, the contractor shall ensure the availability of such equipment for purchase or lease by the Government, as specified in the task order.

6.4.1 - General Requirements

The contractor shall provide the equipment based on task order requirements.

6.4.2 - Equipment Shipment

Under standard shipping timelines and terms, the contractor shall ship equipment as defined in each TO. To ensure mission requirements are filled, two additional expedited shipping requirements are included: 2-day and overnight. Unless specifically indicated in the TO, all deliveries shall follow the standard shipping requirement. Equipment shall be delivered as described in the TO. If the shipment time for a particular TO cannot be met, the contractor shall immediately notify the Contracting Officer (KO) (as listed on the TO), and the customer with an explanation and a plan of action to resolve the problem. The delay shall also be reported for the appropriate month in the Monthly Status Report.

The contractor shall include applicable shipping charges as a one-time other direct cost (ODC) for the shipping categories listed in Table 6-1. The contractor shall ensure that packing meets the requirements of the shipper, and that packaging/packing is sufficient to prevent damage. The contractor shall ensure the shipment is receivable at Government locations. The contractor shall replace lost or damaged shipments and re-ship via an acceptable carrier if the shipment cannot be received at the Government location. All packages shall be trackable, and the tracking number shall be provided to the Government upon shipment.

Table 6-1. Shipping Timelines

All shipments in the continental United States (CONUS) and outside the continental United States (OCONUS) shall be “Free on Board – Destination” or “FOB-Destination”.

6.4.3 - Equipment Warranties

The standard warranty shall be included in the price of the item or device and shall be a minimum of one year. All warranties shall begin their coverage period on the date that the Government receives the item. Any warranty that extends beyond the last date to place orders under this contract shall extend until the warranty’s standard end date. A CONUS return shipping address shall be provided for all warranty return items.

6.5 Task 5 – Reporting

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

6.5.1 - System Architecture

The contractor shall provide, within 30 days of contract award under the initial TO, 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. 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.

6.5.2 - Network Operations (NetOps) 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 30 seconds 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 PLEO network). Additional service-specific metrics will be specified in each TO, such as data throughput (usage) indicators over time in sufficient granularity to support on-going operations and issue identification and resolution. The Contractor is required to provide this reporting via their proposed system, until CSCO commercial management and control system toolset is built and installed.

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. PLEO users shall be able to see monthly and cumulative information. The contractor’s account management solution shall allow a PLEO 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. At a minimum, users shall have the ability to access the fields listed in Table 6-2 from the contractor’s usage database, or their equivalent as appropriate to the contractor’s technology and service type:

Table 6-2. Usage Database Fields

Record Identifiers

PLEO Service User ID

Terminal ID and Type (if applicable)

Subscription Information

Service Type (With contract package identifier)

Subscription Period of Performance

Group ID for service and capability allowance pooling

Remarks

Session Information

Session Type (With contract package identifier)

Session Date

Session Time (Zulu)

Gateway/Portal Utilized for Session

Session Duration with Start/Stop Timestamps (if applicable)

Usage Unit (messages, bytes, images, etc., as appropriate)

Rate/Usage Unit

Number of Usage Units consumed in session

Total Cost of Session

Performance Information (per definitions for Tables 7-1 & 7-2)

End-to-end Latency (peak, average); query period or current month, all time

End-to-end Availability; total over query period or current month, all time, 30-day rolling daily average

Uptime: total over query period or current month, total all time, 30-day rolling daily average

Downtime: total over query period or current month, total all time, 30-day rolling daily average

Additional service-specific usage database fields will be specified in each TO and will align with commercial best practices. For example, packet loss statistics might be specified in a TO acquiring a communication service.

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

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

6.5.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 Regional Satellite Support Center (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 PLEO 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 DISA-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.

6.5.6 - Quarterly Usage Report

Upon commencement of any operational service under a TO, and continuing throughout the contract period for that TO, the contractor shall provide a quarterly usage report containing the fields specified in Table 6-2 above for all PLEO services. Microsoft Excel formatted reports shall be submitted on the 5th business day of January, April, July, and October for the preceding quarter.

6.5.7 - 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 6.6.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 provide 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.

6.5.8 - IA Reporting

The contractor shall maintain compliance with applicable IA policies as defied in the COMSATCOM Information Assurance Questionnaire (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 6.5.5 above.

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.

6.5.9 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 PLEO equipment list shall be included in the monthly status report (MSR).

6.6 Task 6 - Service Management

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

6.6.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, English speaking technicians 24x7 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.

6.6.2 - Travel/Temporary Duty (TDY)

Travel may be required and established at the task order level and billed as a cost reimbursable item. All travel associated with this contract shall be in accordance with Joint Travel Regulations (JTR) and FAR Part 31.205-46.

1. Prior to incurring any long-distance travel expenses, the contractor shall obtain written approval from the COR approving the travel dates, expected duration, origin and destination, purpose, estimated costs, and the number and names of personnel traveling.

1. Travel Authorization Requests shall be completed and pre-approved by the government COR. Travel compensation will not exceed the government allowance for travel and per diem. Copies of all travel receipts must be attached in WAWF to ensure timely invoice approval.

1. The COR will certify invoices prior to processing for payment.

1. Local travel shall not be reimbursed, unless otherwise specified in the applicable task order. Industry Standard Local Travel is hereby defined to mean any and all travel within fifty (50) mile radius of the place of performance.

1. The contractor shall provide a trip report with supporting documentation to the COR within 5 business days of completion of travel detailing the work completed.

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

6.6.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 order. 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.

6.6.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 to successful service activation.

6.6.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 6.5.7), service interruptions, anomalies EMI/RFI incidents, customer service and support (refer to section 6.6.1) 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.

6.6.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, to include subscriber identity module (SIM) cards and PLEO terminals if applicable, 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 terminals.

6.6.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 6.6.5. The objective is to satisfy the goals and procedures of the U.S. Strategic Command (USSTRATCOM) EMI/RFI Reporting.

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

6.6.9 - Information Assurance

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

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.

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

6.7 Task 7 - 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:

· 6.5.1 - System Architecture

· 6.5.4 - Service Activation Plan

· 6.6.5 - Communications and Escalation Plan

· 6.6.9 - COMSATCOM Information Assurance Questionnaire (CIAQ)

· 6.6.10 - Service Management Plan

· Supply Chain Risk Management (SCRM) Plan

· Deliverables list in Table 6-3 below

Table 6-3. Task 7 - 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

6.8 Section 6 Deliverables

Deliverables for Section 6 are defined in Table 6-4 below.

Table 6-4. Deliverables

Priority Shipment - within 2 calendar days ARO Overnight Shipment – within 24 hours ARO Per equipment order

6.5.2 6.6.3

6.5.2 6.6.3 Online Account Management Tool Training Materials

In addition to the distribution listed at the bottom of the table, the report shall be delivered electronically to the Contracting Officer and Contract Specialist

6.5.8 6.6.9 Information Assurance Incident Reporting

Contractor Format

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.

7. Performance Requirements

The requirements in the following subsections assume a network reference model shown in Figure 1. The contractor’s actual network architecture may differ from this reference model or provide a subset of the options contained therein. Figure 1 is provided as reference in explaining the terms used within this PWS.

7.1 Operational PLEO Service Requirements

The operational service as listed here are not applicable to initial, limited use PLEO service. The contractor shall provide operational PLEO service, as listed section 6.1 and 6.2, that meets the following performance requirements:

· Access to a sufficient number of active satellites involved in providing operational service in one or more geographic region(s) of coverage. Geographic regions of coverage shall be defined by the contractor.

· Reporting capability to facilitate accurate accounting for services provided.

· User terminals, if necessary, to allow for operational use of the contracted service.

· Gateway/backhaul capability sufficient to transport data between terminals and the commercial internet, or products between the contractor's system and users via the commercial internet.

For each activated user, the contractor shall provide operational PLEO service that satisfies the threshold performance requirements for the parameters identified in Table 7-1 below and as agreed upon via a SLA. Additional service-specific parameters may be defined and required in a TO, such as packet latency and data rates for a communication service.

Table 7-1. Operational Service Threshold Requirements

The parameters in Tables 7-1 and 7-2 are defined as follows. Note that each parameter should be measured/calculated and satisfied for each direction of information flow.

Space-Ground: From/to the transmitter/receiver or reflector (reference point GN in Figure 1) on a satellite system user terminal or gateway or sensed object to/from the receiver/transmitter or sensor on a satellite (reference point SN in Figure 1).

Propagation Delay: The time during which a signal travels from a transmitting or sensed node to a receiving or sensing node. Note that the performance stated in the tables above is specifically intended to accommodate only offerings that incorporate satellites at LEO altitudes.

End-to-End (also called E2E): For services with user terminals, from/to a user-accessible data ingress/egress interface (reference point UT in Figure 1) on the satellite system user terminal (including any required router and modem) to/from the data egress/ingress interface of the corresponding contractor provided terrestrial interconnect (reference point CR, GR, or GG in Figure 1, depending on which terrestrial interconnect approach is used). For services without user terminals, from the request ingress interface of the corresponding contractor provided terrestrial interconnect (reference point CR, GR, or GG in Figure 1, depending on which terrestrial interconnect approach is used), into the satellite network for the requested effect, and back to the corresponding result egress interface (also reference point CR, GR, or GG as appropriate).

Latency: The amount of time required to deliver a packet, message, product, or effect confirmation (as appropriate to the service offered) (not counting undelivered/lost items). As a formula:

Latency = ((item delivery time at egress) - (item/request arrival time at ingress))

Service Availability: The percentage of time the service performs according to requirement (or would if called upon to do so) for all users; generally expressed in terms of downtime, which is defined as the sum of all periods during which the service fails to perform according to a requirement for any user (note that uptime is simply the opposite of downtime). Availability is measured at the user’s interface to the network/system and is inclusive of all causes of outage including equipment failure, link failure, weather, and other impediments. As a formula:

Availability = (1 - (downtime / (total time))) x 100

7.1.1 PLEO Services

The contractor shall provide low-latency PLEO service and capabilities to all domains and use cases in accordance with performance parameters as specified above and in SLAs corresponding to service offerings. If user terminals are a feature of the service, both fixed-position and mobile users shall be supported. A committed minimum, if specified in a package/SLA, represents the lowest rate or amount of service available to each user at all times, such as throughput in a committed information rate, or CIR. A maximum allowance, if specified in a package/SLA, represents the “at most” rate or amount of service that may be available to each user when conditions allow, such as throughput in a maximum information rate, or MIR. Note that a package/SLA may include either, both, or neither committed minimums and maximum allowances. Service availability, if specified in a package/SLA, represents the “at least” uptime fraction experienced by each user over the course of a year.

The contractor shall provide terrestrial connections for PLEO service from the PLEO ground station(s) or portal(s) serving each user to the endpoint(s) identified on the task order, if so specified. The contractor shall provide service in an area of geographic coverage (the “coverage area”) that shall be the same or greater than that provided to all of the contractor’s customers (an area that covers the sum of all service coverage areas offered to all of the contractor’s customers). The contractor shall provide service invoices based upon service usage (messages, packets, megabytes, products, effects, as appropriate) consumed or per subscription in accordance with contractual instructions on the TO.

7.1.2 Priority Service Option

The contractor shall provide a service priority option that the Government may at its discretion purchase and activate on a subscription-by-subscription basis (that is, per user).