AMC GTPaaS - Performance Work Satement.pdf

UNCLASSIFIED

Air Mobility Command (AMC) A2 Global Transport Platform

1. Performance Work Statement

Background: Air Mobility Command Directorate of Intelligence, Surveillance, and Reconnaissance (AMC/A2) Systems Requirements Branch (AMC/A2YR) manages the development, acquisition, fielding, rapid deployment, and maintenance lifecycle of various assets in support of the deployed intelligence warfighter.

AMC/A2 seeks to provide a “one-stop-shop” platform for mission support to rapidly consolidate, integrate, acquire, and/or divest of unique solutions and by utilizing commercial “best practices” while providing “cradle-to-grave” management for the duration of required capabilities.

AMC/A2 has identified an emerging requirement for a Platform as a Service (PaaS) to support a collaborative environment at multiple classification levels. In response to the ever-growing dependency on complex and adaptable technologies, an approach to providing peer to peer communication at the tactical edge through rapid acquisition and development of new capabilities. However, traditional DoD and acquisition pitfalls have remained and hinder the performance of this capability acceleration. Non-traditional defense vendors, users and external entities are regularly hindered in their ability to collaborate effectively in an innovative way.

While cross department workspaces exist from which to bring vendors, users, and the program management offices together, they lack the dedicated infrastructure to enable real collaboration.

AMC can leverage an approved strategy that provides flexibility and accelerates technology adoption. To truly flourish, AMC/A2 intends to establish a globally connected network solution that provides its deployed users multiple transport paths to effectively communicate with stakeholders leveraging industry best hardware and software in classified and unclassified environments.

2. Objectives

The AMC/A2 portfolio of technologies intends to interconnect with a variety of edge systems and users. The Global Transport platform as-a-service (GTPaaS) will provide the environment and network infrastructure needed to streamline the integration of AMC/A2 transport assets with non-traditional defense vendors, AMC users and external DoD entities.

AMC/A2 will utilize edge infrastructure (i.e. Joint Expeditionary Forward Flyaway Kit (JEFF- K)), with the Global Transport Platform placed in front, to connect their users to a managed Secure Entry Point (SEP) that will allow AMC/A2 intelligence analysts to move forward with no required changes to existing networking gear. Users will achieve Automated Primary, Alternate, Contingency, and Emergency (PACE) and Edge to Edge communications in disrupted, disconnected, intermittent, and low-bandwidth (DDIL) environments.

The overarching goals of the Global Transport capability are to:

• Accelerate integration of technologies as required due to new intelligence requirements.

• Reduce integration time and costs using preconfigured technologies and vendor provided environment to provide operational ready capabilities to AMC/A2 personnel.

• Continually evaluate the integration of Original Equipment Manufacturer (OEM) developed technologies into a government owned platform.

• Provide a trusted collaboration architecture built on best-of-breed technology in an open modular configuration with supporting documentation.

• Provide AMC/A2 Intelligence Analysts the capability to analyze, integrate, view, test, and train on a dedicated Top Secret/Sensitive Compartmented Information (TS/SCI) level with access to the Air Force Joint Worldwide Intelligence Communication System (AF JWICS) and at the SECRET classified level with access to Secret Internet Protocol Router Network (SIPRNet).

3. Scope

The GTPaaS will allow forward deployed users, to connect their edge infrastructure (i.e. JEFF- K), using their desired transport path (SATCOM, 4G/5G, LTE, Wi-Fi, etc.) to quickly and dynamically access their applications and data inside a dedicated NIPR, SIPR, and TS/SCI gateway.

The unique environment of the AMC/A2 entity requires different levels of network access including Commercial, Unclassified, and Secret. This is a key separation from most other hardware and software integration and development acquisition environments that creates barriers to integrating the best into AMC/A2 programs. AMC/A2YR is seeking a GTPaaS with global network access to Non-Secure Internet Protocol Router Network (NIPRNet), SIPRNet, and Top Secret (TS)/JWICS through industry best backhaul and transport backbones.

4. Requirements

4.1. General

The contractor will provide dedicated access from JEFF-Ks to Commercial, UNCLASSIFIED and CLASSIFIED (SIPRNet & AF JWICS) networks for a standardized multi-layered edge connectivity architecture. Additionally, this platform will provide the hardware required to provide a global enterprise network for deployed AMC/A2 users. The contractor shall design, install, configure, test, operate, maintain, administer, and manage the dedicated NIPR, SIRP and JWICS network infrastructure and services, including all associated hardware and software that permits the transmission and sharing of data that supports the security of the information and information systems.

4.2. Hardware

4.2.1. SATCOM

The contractor will acquire, field and support portable Starlink/Starshield satellite communications (SATCOM) terminals, and provide commercial Starlink/Starshield service subscriptions for up to twenty-five (25) JEFF-K.

Standard Service requirements:

• MIR of up to 250x30 Mbps

• 60-250 Mbps/10-30 Mbps down/return

• 5 TB / Month priority data

• Global Coverage.

Additionally, the contractor will deliver 25GB/month with up to 20Mbps of expected download and up to 3Mbps in upload for five the (5) Tampa 95cm satellite antennas that AMC/A2 currently owns.

4.2.2 Software-defined Wide Area Network (SD-WAN)

Acquire, field and support SD-WAN hardware capable of providing each JEFF-K with multipath routing and failsafe delivery.

4.3. Programmatic and Administrative Support

The contractor shall coordinate JEFF-K requirements, configuration, and delivery to AMC/A2 designated users.

4.3.1. Program Manager

The contractor shall identify a Program Manager, by name, who will serve as the contractor’s primary point of contact for the Government. The contractor PM will be responsible for the overall management, direction, administration, quality control, and leadership of the execution of this effort. The PM shall coordinate, communicate, integrate, and monitor all project activities to ensure successful delivery of the GTPaaS and support services in accordance with the contract and PWS requirements.

4.3.2. Configuration Management

The contractor shall, in coordination with the Government, provide configuration, change, and release management (including, but not limited to, configuration identification, control, verification and audit activities) for the JEFF-K. Additionally, the contractor shall:

• Manage and apply configuration control to all JEFF-K hardware, software, and documentation developed and delivered under this contract, and maintain records to account for configuration changes from the baseline configuration;

• Provide a JEFF-K infrastructure automation tool to enable agile combat employment (ACE) capabilities for non-traditional IT users who require the ability to quickly establish communications while deployed forward.

• Provide and maintain system design documentation and diagrams;

• Management of deployable network IP ranges;

• Verify and validated changes are properly processed and approved prior to modification;

ensure changes to configurations are be made only if approved by the AMC/A2 PMO;

• Develop, maintain, and implement JEFF-K hardware and software configuration management policies, and assist the Government with developing requirements and project scope;

• Complete monthly Configuration and Traceability Reports, and Configuration Management Reports; and

• Participate in operations assessment of current and future AMC/A2 requirements relating to impacts on mission system network infrastructure and communications-computer systems.

4.3.3. SME Support

Provide Subject Matter Expert (SME) services as required to act as a front door integration with AMC/A2. These services will cover everything from network access, scheduling, and providing technical support for integration. SME support is anticipated to require technical in-depth knowledge of AMC/A2 programs and applications to provide proper facilitation to vendors and entities requiring access to and integration with AMC/A2 programs. This duty can be provided by the Program Manager.

4.3.4. Asset Management and Logistics

The contractor shall provide logistics and asset management for GTPaaS. Additionally, the contractor shall:

• Store, distribute, manage, and account for all JEFF-K hardware including associated SD- WAN equipment, licenses and subscriptions;

• Store, distribute, manage, and account for all SATCOM (Starlink/Starshield) hardware including all subscriptions;

• Conduct and provide quarterly hardware/software inventories;

• Provide just-in-time logistics support of request deployment communications kits and associated services;

• Coordinate and conduct pre-deployment readiness checks to ensure equipment is mission ready prior to shipment;

• Coordination and delivery of hardware to customer sites based on the agreed schedule and/or at the request of the Government;

• Package, handle, store, transport, and ship materials using best commercial practices to ensure effective use of space for packaging, handling, and transportation.

4.3.5. Training

The contractor shall provide familiarization and technical training on the GTPaaS and associated infrastructure to end-users, operators, and maintainers in accordance with commercial best practices and industry best standards. The depth and breadth of training and associated materials provided shall be to a level sufficient to enable the customer staff to effectively and efficiently set-up, administer, operator, maintain and use the capability. Training can be both at a customer site (CONUS) or remotely. Training may also include the use of materials (e.g., operating manuals, users guides and reference guides) that will aid in knowledge transfer.

4.4.Secure Entry Point (SEP) Network Infrastructure

4.4.1. SEP Dedicated Circuits/Gateways

The contractor shall design, install, configure, test, operate, maintain, administer, and manage the dedicated NIPR, SIPR and TS/JWICS circuits and network infrastructure, including all associated hardware and software that permits the transmission and sharing of data and that supports the security of the information and systems. The Government will provide approvals and sponsorship required to establish the GTPaaS network infrastructure.

The contractor will provide and maintain a highly resilient networking and communication path from the edge (JEFF-K) to customer resources in NIPR, SIPR and JWICS enclaves. The contractor will manage the ingress points used for accessing the commercial backbone, the egress points to the data center, network support and security to the connections. This capability is to deliver a session smart routing capability which will natively allow users to find the most efficient path across a dynamic backbone back to the data center.

Upper data limits for the Secure Entry Point are as follows and will support up to thirty-two (32)

JEFF-K:

• Egress/Ingress – 40hrs/ week utilization

• Data Transfer – 5TB per month

• GovCloud VPC – 10TB down – 5TB up per month

4.5. Government Furnished Equipment (GFE)

The Government will provide the contractor with JEFF-K’s and encryption devices as required to fulfill the obligations under this PWS. The Government will provide authorized contractor personnel access to unclassified and classified network services (e.g., e-mail, internet) and support, and provision access to shared resources required in performance of the contract. All Government furnished property or equipment incidentals to the performance under this contract will remain property of the Government and be accountable under Government internal controls.

Tasks shall be determined jointly (Government/contractor) via monthly schedule Task/Technical Update Meetings. These meetings shall be hosted on a set schedule as mutually agreed upon by the Government and the contractor and be conducted at either Scott AFB, at the contractor’s facility or virtually. Meeting minutes shall be taken and utilized as the basis of determining tasking priorities/deliverables/schedule.

5. Contract Type/Period of Performance

5.1. Firm Fixed Price

The base contract will be a one-year effort with two (2) one- year option periods.

6. Place of Performance

The primary places of performance include the contractor’s facility, the Government location (Scott AFB) and/or at Contractor designated location(s) required to provide and sustain this capability platform. Individual task or delivery orders may require performance of duties at locations. Updates to the contract DD254 will be made per order as required for the inclusion of these locations.

7. Security

Security will be in accordance with an attached DD254. Contractor team individual(s) supporting this task will be cleared at the TOP SECRET level at the start of the task. Contractors will require access to Communications Security (COMSEC), Sensitive Compartmented Information (SCI) and Alternative Compensatory Control Measures (ACCM) material/information in performance of this effort. Contractor will not require access to government computer systems.

Contractor is authorized to courier classified material/information up to the SECRET level in performance of official duties upon approval of a designation by the COR. Courier authorization includes SECRET COMSEC such as encryption devices, electronic key, and key loading support equipment as required to support the platform SIPR capability.

Contractor must possess a Top Secret Facility Clearance in order to perform on this contract.

7.1.The contractor shall insure requirements for safeguarding classified information and classified materials, for obtaining and verifying personnel security clearances, for verifying security clearances and indoctrination of visitors, for controlling access to restricted areas, for protecting government property, and for the security of automated and non-automated management information systems and data are fulfilled. The contractor's management system shall prevent unauthorized disclosure of classified and sensitive unclassified information.

The government shall be immediately notified if any security incident or any indication of a potential unauthorized disclosure or compromise of classified or sensitive unclassified information.

7.2.The contractor shall provide security management support. Typical efforts include, but are not limited to, performing classified document control functions, classified materials inventories, program access requests, preparing and monitoring personnel indoctrination and debriefing agreements, and maintaining and using security-related databases.

8. Government Furnished Equipment (GFE)

8.1.The Government shall provide all necessary encryption/HAIPE equipment in this PWS. The contractor shall maintain asset records for government equipment housed at/in their worksite in accordance with all applicable Government regulations. All equipment and services shall be used only in the performance of this PWS and/or individual task order PWSs. The COR shall determine the type, quality, quantity, responsibility, and location of all Government furnished items and services. The use (or non-use) of Government furnished items and services will be subject to the Government’s current and evolving schedules, policies, and procedures. The Government shall provide maintenance or funding to acquire for all furnished equipment under this contract. The Government shall be responsible for replacing equipment that is no longer serviceable and deemed required.

9. Accounting and Appropriation Data

9.1. The contractor shall submit invoices once per month.

9.2. The subject line of the contractor email invoice submission shall contain the contract number, contract line-item number, the order number, if applicable, and the number of invoices. The contractor shall submit monthly invoices in Wide Area Workflow (WAWF).

9.3. Invoices shall be submitted in accordance with the contract terms, i.e. payment schedule, progress payments, partial payments, deliverables, etc.

9.4. All calls concerning contract payment shall be directed to the KO and/or COR.

10. Other Pertinent Information or Special Considerations

10.1. The contractor hereby understands and agrees that if work to be performed under this contract requires access to proprietary data of other companies, the contractor shall protect such data from unauthorized use or disclosure so long as it remains proprietary. Further, the contractor agrees that it will not utilize that data obtained from such other companies in performing additional studies in the same field, which are obtained competitively. The contractor shall notify the Government of any potential or actual conflict of interest situation that arises. The contractor must provide access to any directed Government, Military, or contractor personnel required to service Government equipment that will be evaluated or operational within the Global Transport Platform. The contractor is responsible for providing and maintaining Non- Disclosure Agreements (NDA) with applicable contractor personnel that provide support to the platform as required to maintain mutual understanding and safeguarding of proprietary information.

11. Special Contracting Requirements

11.1. The contractor agrees not to release or disclose, verbally or in writing, information pertaining to the discovery of Government requirements, results, or findings of work (including data collection, analyses, draft or final papers and reports) for the period of this task order without first notifying and gaining expressed permission from the KO and/or COR in writing at least 21 calendar days prior to release or disclosure.

11.2. The contractor must provide notification (minimum 21 calendar days prior to release) and in writing, specifying: who or what is generating the request for advance information; when and how project results/information would be released; and what information would be released.