PWS AODMS 2024_31224.pdf

PDF 184 KB Posted

Attached to
Airfield Operations Data Management System (AODMS) Platform as a Service (PaaS)
Solicitation number
F3YTAS4054AW02
Issued by

About this file

This document is a Performance Work Statement (PWS) for the Airfield Operations Data Management System (AODMS) Support contract. The PWS requires the vendor to provide IT support and application hosting services using a Platform as a Service (PaaS) cloud computing model to maintain the AODMS application. The key tasks include building and sustaining the hosting environment on Amazon Web Services (AWS), providing engineering support, and managing the test/development and production environments. The period of performance is 12 months from July 31, 2024 to July 30, 2025. The vendor must comply with performance thresholds for ACAS scans, data backups, and environment management. The related federal contract opportunity is a solicitation for the AODMS PaaS support services, with a requirement that the vendor have a FedRAMP designation as a Cloud Service Provider authorized for Information Level-4 PaaS.

View the file

Other files

On GovTribe

Work with this file

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

PERFORMANCE WORK STATEMENT

12 Mar 24

AIRFIELD OPERATION DATA MANAGEMENT SYSTEM (AODMS) SUPPORT

AIR FORCE FLIGHT STANDARDS AGENCY

TINKER AFB OKLAHOMA CITY, OKLAHOMA

1.0 SCOPE

This task will require the vendor to provide the IT support necessary to perform support and maintenance services to accomplish application hosting services using the PaaS (Platform as a Service) cloud computing model for the maintenance of the Airfield Operations Data Management System

(AODMS).

1.1 GENERAL

The Air Force Flight Standards Agency (AFFSA)/Cyber Operations Directorate requires Information Technology support with regards to Airfield Operation Data Management System (AODMS), developed by Cyber Technology software developers (organic).

AODMS is designed to provide the USAF Airfield Operations a cloud-based suite of applications necessary to create AO operational and managerial agility, globally share information, enable safety and operational trend data analysis, and reduce manpower costs. The overall objective is to secure a Platform as a Service (PaaS) service contract for building and sustainment of hosting AODMS in the cloud.

1.2 TASK EXECUTION PLAN

1.2.1 Task 1: Build & Sustain Environment

The vendor will continue to sustain the application hosting services through AWS (Amazon Web Services). The vendor will manage the AWS console, overhead costs, control access lists and security groups for the environment. The vendor will maintain the ACAS instance updates to include software updates and configuration & IA compliance. The vendor will manage the ACAS scanning of application instances, report generation and maintain the operating systems licenses.

The vendor will manage the following equipment for DISA STIG and IA compliance:

• 2x Application Servers o 8vcpu/32GB/35GB – T3.2xlarge

• 2x Database Servers o RDS = vCPU: 4vcpu/16GB/200GB – db.m5.xlarge o RDS = vCPU: 2vcpu/8GB/200GB – db.m5.large (50% utilization)

• 4x Bastion Hosts, load balancers and NAT Gateways o 2vcpu/2GB/35GB – T3.small

• 7 x EBS volumes for above o 60 GB plus snapshots

• 7 x EIP numbers for above

• 14 TB data transfer

In addition, the vendor will manage the data redundancy between the AWS East and West regions to ensure maximum availability, reliability, and accessibility.

1.2.2 Task 2: Engineering Support

The vendor will maintain the operation system keys, PKI and LDAP infrastructure. The vendor will manage instance image backups and archival data backups from web application server and database server.

1.2.3 Task 3: Engineering Services Non-Recurring Support

The vendor will manage the test/development and production environments cost and performance for

AODMS within AWS. The vendor will provide IA support to include remediation utilizing DISA SCAP tools for IA compliance and maintain operating system security patches and updates.

1.3 PERIOD OF PERFORMANCE/PLACE OF PERFORMANCE

The period of performance is twelve months beginning July 31, 2024 and ending July 30, 2025.

1.4 GOVERNMENT FURNISHED EQUIPMENT/MATERIALS/FACILITIES

N/A

1.5 INSPECTION AND ACCEPTANCE

Acceptance of invoice will be made by HQ AFFSA/AODMS COR (Contracting Officer Representative).

2.0 APPLICABLE DOCUMENTS

None

3.0 REQUIREMENTS

This task shall require the vendor to provide the support necessary to perform the following functions:

• Provide support to Amazon Web Services (AWS) for AODMS.

• Resolve any network Issues involving availability, accessibility, and reliability

• Maintain costs for government and access list

• Maintain test/development and production environments.

• Generate new instances and availability when network bandwidth falls below operating standard.

4.0 DELIVERABLE

The vendor shall be aware that in the absence of any contract requirement from the Service Summary does not detract from its enforceability nor limit the rights or remedies of the Government under any other provision of the contract. The vendor shall ensure the following service methods are achieved as follows:

Service Summary (SS) Requirement The vendor shall ensure the performance objectives, performance thresholds, and support for surveillance methods are achieved as follows:

Performance Objectives and Thresholds The vendor shall achieve performance thresholds identified in Table 2.1 of this PWS.

NOTE 1: The performance thresholds are designed to:

a. Align vendor performance objectives.

b. Focus on critical success factors in meeting performance objectives.

c. Reflect performance goals.

d. Promote continuous improvement in performance.

NOTE 2: The AODMS COR will exercise surveillance over the performance thresholds.

Surveillance Methods The vendor shall support the AODMS COR surveillance methods as identified below:

a. Random sampling of recurring service outputs.

b. One hundred percent inspection of the output.

c. Periodic inspection of the process or output.

NOTE: The AODMS COR may use a combination of surveillance methods, as defined above, to monitor vendor’s performance even though the specific surveillance method is not called out in Table 2.1.

Vendor Performance Evaluation The vendor shall be aware that the evaluation of performance will occur when AODMS Program manager evaluates the service of the vendor to determine whether or not it meets the performance measures of the contract.

NOTE: In the event the performance measure is not met, the Contracting Officer Representative (COR) will issue written notification to the vendor. In those cases, the PCO will take appropriate measures.

Table 2.1

Performance Objective PWS Paragraph

Performance Threshold

The vendor shall conduct ACAS scans on the equipment.

1.2.1

100% Compliance.

Scans are conducted at a minimum monthly and a report provided to HQ

AFFSA/XCT.

The vendor shall backup and store data.

1.2.2 100% Compliance.

Conduct data backups from servers at a minimum weekly.

Ensure data is readily available.

The vendor shall manage the test/development and production environments for performance.

1.2.3 100% Compliance

Provide operational status report monthly for environments.

5.0 GENERAL

Vendor employees shall identify themselves as vendor personnel by introducing themselves or being introduced as vendor personnel and displaying distinguishing badges or other visible identification for meetings with Government personnel. In addition, vendor personnel shall appropriately identify themselves as vendor employees in telephone conversations and in formal and informal written correspondence.

5.1 Vendor

The vendor shall prepare one combined invoice and receiving report through Wide Area Workflow (WAWF) online system. The invoice shall be broken out according to contract service. Registration information, invoicing procedures, software downloads and web based training are available at https://wawf.eb.mil. The vendor shall have an electronic business point of contact listed in their Central Registration (CCR) listed prior to using WAWF.

5.1.2 Vendor Manpower Reporting (CMR): The Vendor shall report ALL Vendor labor hours, to include sub-Vendor labor hours, required for the performance of the services provided under this contract via a secure data collection site. The Vendor is required to completely fill in all required data fields at the website https://afcmra.dmdc.osd.mil.

https://wawf.eb.mil/ https://afcmra.dmdc.osd.mil/

The Vendor shall report all labor hours executed during the Period of Performance (PoP) for each Government Fiscal Year (FY) which runs from 1 October through 30 September the following year.

Although the labor hours executed may be completed any time during the FY, all data shall be completed no later than (NLT) 31 October of each calendar year. Vendors may direct questions to the CMR help desk email listed at https://afcmra.dmdc.osd.mil.

5.2 Government

5.2.1 The vendor shall notify the designated government representative via e-mail when the invoice is input in the WAWF system. They will either approve the invoice or coordinate with the vendor if it is not acceptable.

5.2.2 The government representative is Mrs. Stephanie Jane Roberts, HQ AFFSA/FM, 405-734-4891.

https://afcmra.dmdc.osd.mil/

File details come from the government source that posted it. Updated .