SCP Dev Enclave Engineering Services PWS 27June.pdf

PR: F3Q3AH4170AW01 PWS REVISION: 0 1

Performance Work Statement for

78 ABW/SCP Dev Enclave Cloud Engineering Services Purchase Request: TBD

27 June 2024

PR: F3Q3AH4170AW01 PWS REVISION: 0 2

1.0 Description of Services

1.1 Objective(s): The primary objective of this contract is to obtain the necessary technical and functional contractor Cloud Engineering expertise to facilitate the stand-up and migration of 78 ABW/SCP software system development activities from the local data center into Cloud One. The project will be managed with the goal of standing up all the development sites within the C1D environment as soon as possible or, at a minimum, by the end of this performance period. The outcome will be dependent upon complex work and cooperation across multiple parties including the 78 ABW/SCP team, other 78 ABW/SC parties, Cloud One, and the Contractor. The Contractor team will establish operational capability for development activities in the Cloud One C1D environment with 78 ABW/SCP team sponsorship, work to implement and automate tools, build internal pipelines, optimize performance, document architecture, hardware, software and configurations, and then transition sustainment of the environment to the 78 ABW/SCP Team as requested.

1.2 Benefit to United States Air Force (USAF): This acquisition will benefit the United States Air Force (USAF) by creating and providing a software development environment critical to maintaining and supporting 78 ABW/SCP systems that enable missions across AFMC.

1.3 Background: 78 ABW/SCP performs development work and system sustainment for multiple systems and customers at Robins Air Force Base. Currently, development activities take place on the Air Force Network. This is not sustainable and as such 78 ABW/SCP requires support and assistance to stand-up and operate a singular development environment within an Air Force approved cloud platform with AFLCMC/HNII, commonly known as Cloud One (C1).

78 ABW/SCP has identified 14 of our systems as part of this effort. There are also a few commercial tools needed. The full list is included in Section 8.1, Appendix A. While these have been identified as part of the initial effort, there may be additional tools added as needed to support this effort.

This effort includes the migration of 78 ABW/SCP development systems/sites, databases, and tools into a singular Cloud One Development (C1D) environment at an IL2 level. This would include standing up the C1D shell, creating developer virtual machines, installing any necessary tools on the development machines or as separate servers (for example Microsoft Azure DevOps Server), and standing up the necessary servers to host the development and testing systems within this environment. Technologies include Microsoft .NET, JAVA, SQL Server, Oracle, Windows, Linux, Angular 17 or greater, EF Core 6.0, .Net Core (versions 6,7, and 8), Javascript, TypeScript, Apache webserver, Active Directory Services, and Email Services.

This migration is only for the 78 ABW/SCP development “environment”. These systems and webpages are currently production hosted on premise in the Robins Enterprise Data Center (REDC) on base at Robins Air Force Base, GA. This may change for some of them in the future but is outside the scope of this effort. A manual effort is planned to handle releases from C1D back to the REDC although as the workload transitions from migration to support a study

PR: F3Q3AH4170AW01 PWS REVISION: 0 3

or technical paper may be requested to evaluate possibilities and actions for future automation.

2.0 Services Summary

PWS Ref. Performance Threshold

Hold a kick-off meeting

4.3, 4.4 Upon contract award, Contractor shall hold a kick-off meeting within ten (10) calendar days to introduce the team to the 78 ABW/SCP team.

Develop a Migration Plan

4.3, 4.4 Contractor shall develop a migration plan after the kick-off meeting.

o Contractor shall start work on the migration plan within 3 days of the kickoff meeting.

o Contractor shall use no more than 2 workdays per system to meet and discuss program needs with the teams and to perform analysis. 78 ABW/SCP shall assist and arrange availability of program and development teams.

o Contractor shall also have 2 workdays to discuss overall environment needs.

o Contractor shall deliver the migration plan within 5 days of completing analysis outlined above.

Develop an Integrated Master Schedule (IMS)

4.3, 4.4 Contractor shell develop an Integrated Master Schedule (IMS) of the migration timeline within (5) calendar days of having an approved migration plan. This schedule shall not extend past the initial performance period of this effort.

Provide a final Migration Plan and

IMS

4.4 Contractor shall coordinate with 78 ABW/SCP to review

and resolve any government contested items within the migration plan and timeline, make any changes or updates, and provide a final accepted and approved migration plan and IMS within five (5) calendar days of completing the IMS.

PR: F3Q3AH4170AW01 PWS REVISION: 0 4

Establish an initial CloudOne development environment

4.4 Contractor shall configure and establish an initial

CloudOne development environment (commonly referenced as C1D) within forty-five (45) calendar days of gaining access to the environment from Cloud One.

This timeline should be included in the IMS and migration plan and at a minimum include one running instance, with an easily replicated script, of

(1) a Development machine, (2) a Windows Server, and (3) a SQL Server unless the government team agrees to a different requirement as part of the Migration Plan.

Meet migration plan timetable in the IMS

4.4 Contractor shall be expected to meet migration plan

timetable outlined by the IMS with no more than 2 internally caused delays to this schedule. This does not include delays caused by the government.

Submit Monthly Status Reports (MSRs)

4.5 Contractor shall submit MSRs to the CORs within 24

hours of the due date (10th of each month) with no more than 2 significant errors. Errors shall be corrected within 5 business day after notification.

Prepare Technical Reports, Briefings, and Slides

4.6 The contractor shall prepare meeting minutes, briefings, background papers, Item of Interest (IOI’s), Bullet Background Papers (BBP’s), bottom line up front (BLUF) and ready to send (RTS) electronic mail, communication and coordination tracking system(s), and/or other correspondence, briefing and/or supporting documentation delivered timely and upon Government request IAW Government guidance, or in formats meeting the Tongue and Quill standards, or published Action Officer templates.

Adherence to Contractor Quality Management System (QMS)

7.9 Contractor must create plan/schedule of inspection.

Report any Problems

General Report any problems with PWS task completion to the PM/COR/ACOR within 48 hours of when the problem started.

PR: F3Q3AH4170AW01 PWS REVISION: 0 5

3.0 Government Property

3.1 Contractor Responsibility: The Contractor shall be responsible for Government property in accordance with the Federal Acquisition Regulation (FAR) and as specified in the contract/order.

The Government can ship GFE to the contractor as requested. Any travel to pickup GFE, travel to activate on a government network if needed, or any travel otherwise needed to be on a government network to support or update GFE shall be at Contractor expense and not reimbursed as part of this effort unless it is aligned with an otherwise approved trip supporting this effort.

3.2 Government Property to be Provided: If the Contractor is working remotely then a primary desk will not be provided unless trips and travel require one. If the Contractor is local and on-site primarily then the Government property to be provided includes the Contractor's main office space and it shall be located on Robins AFB within Building 228. The Contractor will be provided office furniture and equipment, including phone, desk, chair, shelves, and computer.

3.3 Base Support: Microsoft (MS) Office suite, Trouble ticket Client, Visio Reader, Adobe Acrobat and any other applications will be supplied by the Government for use on FDCC computers.

3.4 Reporting of Government Property: The Contractor shall have a system of internal controls to manage (control, use, preserve, protect, repair, and maintain) Government property in its possession in accordance with FAR 52.245-1, and its property management system shall be adequate to satisfy the requirements of this clause. The contractor shall record receipt and return of all Government Furnished Property (GFP), as well as the reporting of shipment, consumption, disposal, or transfer to another contract, in the GFP Module in Procurement Integrated Enterprise Environment (PIEE), https://piee.eb.mil, as stipulated by DFARS 252.245-7002. This reporting requirement does not change any liability provisions or other reporting requirements that may exist under the contract. GFP training and guidance is located at the DoD Procurement Toolbox at https://dodprocurementtoolbox.com/.

3.5 Loss of Government Property

3.5.1 Definition of Loss of Government Property: “Loss of Government property” means unintended loss of or damage to Government property including property that cannot be found after a reasonable search, loss due to inadequate storage, loss due to lack of security, theft, damage requiring repair to restore the item to usable condition, or damage that renders the property useless for its intended purpose or Beyond Economical Repair (BER). Loss of Government property does not include manufacturing defects, obsolescence, normal wear and tear, or purposeful destructive testing. Unless otherwise stated in the contract/order, loss of Government property does not include normal and reasonable inventory adjustments, i.e., losses of low priority consumable material, such as common hardware, as agreed to by the Contractor and the Government Property Administrator.

https://piee.eb.mil/ https://dodprocurementtoolbox.com/

PR: F3Q3AH4170AW01 PWS REVISION: 0 6

3.5.2 Reporting Loss of Government Property: The Contractor shall report loss of Government property in the GFP Module located in PIEE, https://piee.eb.mil/piee-landing/.

3.5.3 Return or Retention of Government Property: All property provided by the Government remains the property of the Government and shall be returned to the Government as directed, but no later than completion of the contract/order, unless the Procuring Contracting Officer (PCO) directs the Contractor to retain the property for continued use under a successor contract. All Government property shall be returned to the Government in the condition provided unless approved in advance by the PCO. All material generated under the contract/order becomes the property of the Government and shall be returned to the Government as directed, but no later than completion of the contract/order, unless the PCO directs the Contractor to retain the material for continued use under a successor contract.

4.0 Technical Requirements

4.1 Scope

The scope of work associated with this contract includes all activities necessary to successfully migrate 78 ABW/SCP development servers and databases from their current on-premise data center hosting at Warner Robins Air Logistics Complex (WR-ALC) to Cloud One (C1) along with the stand-up of any required tools and the virtual desktops for development use. This will require establishing the necessary compliant environment and re-hosting the applications in C1D.

This may include assisting or instructing 78 ABW/SCP personnel in any of the steps, technologies, and activities within this scope. This migration may also involve recommendations for specific improvements or enhancements to the development sites in order for it to integrate better within the C1D service environment. This scope for the base period should also include all automation and scripting for the buildout of the base virtual machines (both servers and desktops) for the operating systems in a “bare bones” fashion so that a developer can then follow on with installing the developer tools necessary for each of the specific applications except in cases when the tool may be part of the CloudOne image, any internal to the environment pipelines, automated scanning, and automated security implementations. Integration outside of C1D would be considered out of scope, the boundary of automating anything outside of C1D is also out of scope, analysis and recommendations as mentioned in a later section, if requested, should be considered in scope.If exercised, any option period shall be used to improve automation and scripting of the virtual machines and products beyond the “bare bones” aspect.

This Cloud Engineering Support will also function partly as a Migration Support Provider (MSP) role to help with managing all aspects of the stand-up and initial support for the development environment within Cloud One. This role will help to obtain and coordinate any such services that may be required from Cloud One to facilitate stand-up and ongoing support. This role is distinct from any support provided directly by the Cloud One team.

4.2 Work Objective

The primary objective of this contract is to obtain the necessary technical and functional contractor Cloud Engineering expertise to facilitate the stand-up and migration of 78 ABW/SCP software system https://piee.eb.mil/piee-landing/

PR: F3Q3AH4170AW01 PWS REVISION: 0 7

development activities from the local data center into Cloud One. The project will be managed with the goal of standing up all the development sites within the C1D environment as soon as possible or, at a minimum, by the end of this performance period. The outcome will be dependent upon complex work and cooperation across multiple parties including the 78 ABW/SCP team, other 78 ABW/SC parties, Cloud One, and the Contractor. The Contractor team will establish operational capability for development activities in the Cloud One C1D environment with 78 ABW/SCP team sponsorship, work to implement and automate tools, build internal pipelines, optimize performance, document architecture, hardware, software and configurations, and then transition sustainment of the environment to the 78 ABW/SCP Team as requested.

4.3 Contractor Facts, Assumptions, and Methodology

The Dev Enclave Cloud Engineering support contract will be conducted based on the following facts, assumptions, and methodology:

Facts and Assumption:

• 78 ABW/SCP will approve decisions and requests in a timely manner to avoid unnecessary delays.

• 78 ABW/SCP will acknowledge risks identified and presented by the contractor, consider proposed mitigations, and make decisions timely to prevent unnecessary delays.

• 78 ABW/SCP requests the stand-up and migration to this environment occur as fast as possible in order to remediate issues and ongoing concerns with development as it takes place currently.

• The cloud migration shall follow established best practice expectations as defined by AFLCMC/HNII C3I&N, a.k.a. Cloud One.

• 78 ABW/SCP will provide certain inherently governmental inputs, assessments, and approvals.

• 78 ABW/SCP will fund and provide licensing for all third-party software or hardware required to properly migrate, configure, and install the application in Cloud One. An example is Microfocus Fortify, currently used for static code analysis scanning. Third party software procurement is out of scope, beyond the funding of this contract.

• The contractor will strive to minimize costs to the AF by utilizing native Microsoft products available and approved via Azure Government and leverage the experience gained from contractor's previous cloud deliveries to 78 ABW/SCP in establishing Cloud One Azure environments.

• The 78 ABW/SCP team certifies the cloud environment being requested and delivered is an Impact Level Two (IL-2) supporting development activities. There is no requirement for an IL-4, IL-5, or IL-6 environment as part of this scope.

• As an IL-2 development effort, it is not expected that this effort will require a Risk Management Framework (RMF) package or an Approval-to-Operate (ATO). If it is determined otherwise, contractor will only be responsible for support, testing, compliance actions, and documentation of the C1D cloud environments created under this scope in their cloud engineering role as requested by the 78 ABW/SCP team. Cyber roles to create or build a full package for RMF submission as not included within this scope.

• The Air Force will retain unlimited rights to all data, custom code, configurations, and documentation created by the contractor IAW DFAR 252.227-7013. -7014, and -7017.

• 78 ABW/SCP will provide all necessary Subject Matter Expert (SME) support in relation to both technical and functional aspects of the systems and applications themselves in a timely fashion.

PR: F3Q3AH4170AW01 PWS REVISION: 0 8

• 78 ABW/SCP will provide access to data, environments, SME’s, and any other base support, like GFE laptops, necessary to fulfill the activities associated with the contract.

• 78 ABW/SCP will provide system SME’s in a timely manner to assist with the stand-up of their systems once the server environment is prepared.

• 78 ABW/SC will provide sponsorship for Common Access Card (CAC), security investigations, and elevated investigations for privileged users in support of contract employees.

• 78 ABW/SCP, via Cloud One, will provide contractor the cloud environment shell necessary.

• It should be expected that, at a minimum, each site or system will need a development server, a development database server, an internal test server, and an internal test database server within this environment unless determined or specified otherwise. (See Figure 1 below for example) One notable exception is that many .NET systems operate on a shared server currently and it is expected that could be done in C1D as well. (See Appendix A for the rough draft list of systems and Azure requirements)

• Environment decisions, such as Platform as a Service (PaaS) or Virtual Machines (VMs) for services, should follow program decisions as discussed during the development of the transition plan. Some programs may operate on PaaS while others are not able to. Whenever the possibility of PaaS is available and appears to be the best solution, with no overriding negatives indicating a VM as a better choice, then Contractor should recommend utilizing PaaS during discussions.

• Logging capabilities, such as log analytics should be provided for in cases where the application chooses to utilize that cloud feature.

• The ability to back up and restore data bases should be documented and must be available to the program teams.

• When possible, Contractor shall reuse any scripts created in support of other 78 ABW/SCP programs.

Access or scripts will be provided.

• Contractor shall document 1) a migration strategy, and 2) a migration timeline of the existing 78 ABW/SCP on-premises development environment(s) with 78 ABW/SCP input and for 78 ABW/SCP approval.

• Contractor team can work remotely as long a contractor follows the same work schedule as 78 ABW/SCP with core support hours being 0700-1700 eastern standard time to provide support.

Development Web Server

Development Database Server

Internal Test Web Server

Internal Test Database Server

Azure DevOps/Code Repository

Developer Desktop/Machine System #1

Proposed Methodology:

PR: F3Q3AH4170AW01 PWS REVISION: 0 9

• Upon contract award, Contractor shall hold a kick-off meeting within ten (10) calendar days to introduce the team to the 78 ABW/SCP team. [CDRL A001, Presentation Materials - Project Kickoff]

• The 78 ABW/SCP team shall meet with and provide contractor any necessary information on the systems to be placed within the Development Environment as soon as possible after the kickoff meeting.

• The 78 ABW/SCP team shall request a development environment shell from Cloud One.

• Contractor shall build and document a migration plan following the kick-off meeting to create an order or priority and focus for the stand-up of services and capabilities within the Cloud One development environment. 78 ABW/SCP team will assist, provide input, and support with helping provide guidance on priority and any issues. 78 ABW/SCP will review and approve an acceptable migration plan. [CDRL A002, Technical Report – Migration Plan]

• Contractor shall develop a timeline based on the migration plan within five (5) calendar days of the approved migration plan. The end date for the timeline cannot be past this initial performance period. 78 ABW/SCP team will assist, provide input, and support. 78 ABW/SCP will review and approve or present any concerns within five (5) calendar days. [CDRL A003, Presentation Materials - IMS]

• The Contractor shall deliver services in coordination with the migration plan and timeline.

• The Contractor will also continue to support services, products, and systems that have been stood up within this environment.

• Once identified systems have been stood-up, the contractor will continue to monitor services, make improvement recommendations and help implement as requested, update and improve existing automations, and add additional servers/services or automation as requested.

4.4 Cloud Engineering Services

Cloud Engineering support services will be focused on all aspects of cloud environment design, creation, operation, and improvement along with the custom development and scripting associated with configuration of Azure cloud-native services. This includes any development, support, and operation necessary to create, maintain, or improve the 78 ABW/SCP Dev Enclave Cloud One environment within C1D, DevOps pipelines, possible CI/CD processes, and any supporting products and cloud one virtual machines needed in support of the 78 ABW/SCP Dev Enclave.

• Contractor shall develop a migration plan following the kick-off meeting. The 78 ABW/SCP team will assist in providing input and helping provide guidance on priority, system information, and any issues. The migration plan should include, at a minimum, the technologies to be used, the Azure services needed, a high-level outline of any identified scripting needed, the order at which the services will be stood up, the order for migration of systems, and any activities needed for each system migration. 78 ABW/SCP will review and approve an acceptable migration plan. The time allowed for analysis and discussion of the programs while building the migration plan should provide opportunity for the Contractor to learn more and better understand the programs that are part of this effort.

o Contractor shall start work on the migration plan within 3 days of the kickoff meeting. If requested in advance and agreed to by 78 ABW/SCP, a different delivery timeline may be approved by 78

ABW/SCP.

o Contractor shall use no more than 2 workdays per system to meet and discuss program needs with the teams and to perform analysis. 78 ABW/SCP shall assist and arrange availability of program and development teams. If requested in advance and agreed to by 78 ABW/SCP, a different delivery timeline may be approved by 78 ABW/SCP.

PR: F3Q3AH4170AW01 PWS REVISION: 0 10

o Contractor shall use no more than 2 additional workdays to discuss overall environment needs. If requested in advance and agreed to by 78 ABW/SCP, a different delivery timeline may be approved by 78 ABW/SCP.

o Contractor shall deliver the migration plan within 5 days of completing analysis outlined above.

If requested in advance and agreed to by 78 ABW/SCP, a different delivery timeline may be approved by 78 ABW/SCP. 78 ABW/SCP will review and approve or present any concerns within five (5) calendar days. [CDRL A002, Technical Report – Migration Plan] o Based on the currently identified 14 systems and if no other delivery timeline is approved by 78 ABW/SCP, this should make delivery of a migration plan no later than 38 workdays following kickoff. Also as mentioned, speed of the migration is a priority any acceleration/reduction of these timelines is appreciated.

o Contractor as the cloud engineer SME shall work with 78 ABW/SCP to review the rough draft of systems and Azure requirements from Appendix A and the configurations from Appendix B to ensure they are appropriate and make recommendations and revisions as needed as the Migration Plan and IMS are developed.

o Development of Migration plan should include analysis/discussion of pain points for on-network development versus cloud development and possible workarounds or ability to run items like an Active Directory server, DNS, etc.

• Contractor shell develop an Integrated Master Schedule (IMS) of the migration timeline within (5) calendar days of having an approved migration plan. 78 ABW/SCP would like the timeline for the migration part to be as streamlined and as quick as possible to facilitate stand-up of our programs for development. This schedule shall not extend past the initial performance period of this effort. The contractor shall have the environment stood up within that initial performance period. 78 ABW/SCP will assist in providing input and support. 78 ABW/SCP will review and approve an acceptable IMS. [CDRL A003, Technical Report

– IMS]

• Contractor shall coordinate with 78 ABW/SCP to review and resolve any government contested items within the migration plan and timeline, make any changes or updates, and provide a final accepted and approved migration plan and IMS within five (5) calendar days of completing the IMS. These items shall outline the plan and timeline for completion of standing up the C1D environment, including all systems and tools identified in Appendix A, during the initial performance period of this effort. This includes the completion of any revisions to the documents, any additional details, and working out any timeline discussions that prevented earlier approval for these documents. [CDRL A003, Technical Report – IMS]

• Contractor shall provide a high-level PowerPoint presentation outlining the migration plan and timeline once they are approved. Briefing should be suitable for both development team and leadership to outline the timeline, effort, risks, and items needed to prepare for the migration. As migration continues, this briefing should by updated to include status and progress upon request or monthly at a minimum. [CDRL A007, Presentation Materials – Briefings]

• Contractor shall build and maintain an overall System Design Document that provides detailed guidance on tools and processes involved in product implementation, cloud/application configurations, security and management procedures including detailed diagrams outlining the C1D Environment, Machines, Services, and related information. [CDRL A005, Technical Report - Study/Services]

• Contractor shall configure and establish an initial CloudOne development environment (commonly referenced as C1D) within forty-five (45) calendar days of gaining access to the environment from Cloud One unless government specifically approves another delivery timeline. This is often referenced as a Zone C/IL2 equivalent and utilized for coding with non-CUI (formerly FOUO) data. This timeline should be

PR: F3Q3AH4170AW01 PWS REVISION: 0 11

included in the IMS and the migration plan and at a minimum it should include one running instance, with an easily replicated script, of (1) a development machine, (2) a Windows Server, and (3) a database Server unless the government team agrees to a different requirement as part of the Migration Plan. This would not include any security/securing requirement at this stage, just the creation of the working servers.

• Upon building the initial C1D environment, the Contractor shall then continue to work with the 78 ABW/SCP team in implementing the migration plan to stand-up development services within this environment for 78 ABW/SCP systems.

o Contractor shall create and stand-up development machines in accordance with the migration plan utilizing Infrastructure as Code (IaC). Contractor shall make it easy and repeatable to stand-up new machines as needed or as developers' transition. Contractor shall document an easy process for creating and removing developer machines. There are 3 major types of technologies used by the systems (Java, ColdFusion, and .NET) and, if possible, Contractor will work to create a developer machine script for each technology with the specific tools. See the rough draft of the list of systems and CloudOne requirement in Appendix A.

o Contractor shall script and stand-up a web server and database server for each system according to the migration plan. There may be small systems that can work on a shared web server or shared database, and these will be outlined in advance. See Figure 1 above for the example configuration for each system and then the rough draft of the list of systems and CloudOne requirement in Appendix A.

o Contractor shall script and stand-up web and database servers for each system that will be used to perform internal testing, both functional and security testing, in accordance with the migration plan.

As above, there may be systems that can share a server, and these will be outlined in advance. See Figure 1 above for the example configuration for each system and then the rough draft of the list of systems and CloudOne requirement in Appendix A.

o Contractor shall be expected to meet migration plan timetable outlines by the IMS with no more than 2 internally caused delays to this schedule. This does not include delays caused by the government or other government approved delays due to items outside contractor control, such delays should be specifically brought up to the government for awareness and assistance ahead of time.

• Contractor shall coordinate with 78 ABW/SCP on a timeline for providing status reports and recurring status meetings. Depending on Migration Plan and IMS, contractor should plan on providing a simple status report either weekly or every other week unless government agrees otherwise.

• Contractor will create both scripts and schedules for the starting and stopping of services to align with78 ABW/SCP requirements for the use of the environment.

• Contractor shall utilize and build Infrastructure as code for the creation of C1D objects as much as possible, document these creations, and train teams to utilize them in support of their programs.

• If possible and within what is available in C1D, Contractor shall make recommendations on and set up Authentication capabilities (like Akamai) and Single Sign On capability.

• Contractor requirement for this initial migration is that the environment and all supporting servers and services be stood up within C1D during the base year of this contract with major milestones tracked per the initial IMS. The initial IMS will be preserved, and Contractor shall keep a working IMS updated with any government approved delays and changes. [CDRL A003, Presentation Material – IMS]

• The contractor shall ensure industry best practices and other pertinent DoD/AF guidance and mandates are followed, including IA/Cyber, in recommending the architecture, configurations, and optimization solutions for delivery.

PR: F3Q3AH4170AW01 PWS REVISION: 0 12

• Contractor shall make recommendations and minimize costs to the AF by utilizing C1 available solutions and native Microsoft products approved on Azure Government website to the maximum extent possible.

• The contactor shall transfer the fully configured Development Enclave environment to the AF on demand and no later than the end of contracting period, if not notified of option year exercise.

• Contractor shall be able to update exiting artifacts or document and produce artifacts as appropriate to the cloud engineering role, such as architecture diagrams or information relating to the environment created and covered by the scope of this effort, as required and requested by the 78 ABW/SCP team in support of the environment or any system changes recommended. [CDRL A005, Technical Report - Study/Services]

• Contractor shall configure and enable dashboards, metrics, and/or reporting as requested by the 78 ABW/SCP team in support of daily execution, status, leadership information, or audit/IG support.

• Contractor shall create and provide any training or learning sessions, technical briefings, or technical whitepapers in support of this workload, the environment being created, and the technologies recommended as requested. [CDRL A005, Technical Report - Study/Services]

• Contractor shall assist the 78 ABW/SCP team with the creation of policies and steps for the logical management and the hands-on-management of this environment and its components. This should include considerations and recommendations for reasonable access for developers to work on their systems versus access and control for the environment itself as well as any needed overall policies and procedures.

Contractor shall generate policy, procedures, memorandums, guides, and any related information relating to the management of this environment and all its components as requested by the 78 ABW/SCP team.

• Contractor shall operate, support, and, in coordination with the Government team, improve the cloud environment once it is stood up.

• Contractor shall establish, configure, support, and operate databases, servers, file shares, and blob containers sufficient to migrate, stand-up, and support the development activities outlined and any systems or tools identified as part of the migration plan or added (with timeline considerations) during this effort.

• Contractor shall function as a System Administrator and Database Administrator for this environment in support of the services, systems, and programs stood up and functioning as part of this effort.

• Contractor shall request ability to develop and manage Uniform Resource Locators (URLs) and internal Domain Name System (DNS). If allowed, Contractor shall stand-up and support URLs and DNS for VMs within this scope.

• Contractor shall develop and manage manual or automated processes to gain and manage certificates for the servers within this environment.

• Contractor shall develop, operate, support, and, in coordination with the Government team, improve as much of a Development Security Operations (DevSecOps) pipeline as possible internally within the environment that will be used for capturing, scanning, and promoting code to internal test servers. This should also include any documentation of the pipeline requested by the 78 ABW/SCP team.

• Deployments at the start will be manually transitioned from this C1D environment out to the local datacenter environment. Contractor shall help develop, operate, support, and, in coordination with the Government team, improve a process for building deployment packages in the automated DevSecOps process. This should also include any documentation of the pipeline requested by the team. As systems are transitioned, Contractor shall work to identify solutions and attempt automating deployments into the local datacenter at 78 ABW/SCP request and in coordination with other 78 ABW/SC groups as requested.

• Contractor shall create, operate, support, and, in coordination with the Government team, improve one or more code repositories in this environment, currently identified as Microsoft Azure DevOps.

PR: F3Q3AH4170AW01 PWS REVISION: 0 13

• Contractor shall generate, maintain, and support any required artifacts related to this workload for IA/Cyber compliance requirements. This would only include information, testing, and documentation from a cloud engineering role with regard to the items created within this scope, PM and Cyber roles are not part of this scope. [CDRL A005, Technical Report - Study/Services]

• The contractor shall configure, apply, test, maintain, and document all Security Technical Implementation Guide (STIG) IAW Defense Information Security Agency (DISA’s) Security Requirements Guide (SRG) to installed applications and supporting software, hardware, virtual machines, servers, and files shares at 78 ABW/SCP request and per SCP guidance. This will primarily apply to the internal test server and internal test database server for each system.

• Contractor shall ensure compliance with DoDI 8500.01, Cybersecurity, and 8510.01, Risk Management Framework (RMF) and other mandated regulations in delivering the development environment.

• The contractor shall provide appropriately credentialed staff regarding privileged users IAW 8570.01-M, Information Assurance Workforce, and document the individual(s) with privileged access in an appointment memo for approval by the program manager (PM).

• The contractor shall assist the Program Team with SharePoint, Teams, and other collaborative environments as requested. This may include using, updating, and adding information or documentation.

4.5 Monthly Status Reports

The contractor shall generate and ensure the accuracy of a monthly status report. The contractor shall provide a monthly status report to 78 ABW/SCP COR and PM electronically during the period of performance.

The monthly status report will include the status of the migration and activities addressed in this PWS that the contractor shall deliver to the Government for each month during the period of performance. Monthly status reports shall include status of work, schedules, deliverables, current and cumulative task status, travel funding status, risks and associated mitigation techniques, outstanding issues, and proposed resolution approaches or actions to resolve any outstanding issues. The report shall identify milestones and deliverables completed and progress towards major milestones and deliverables. The report shall identify activities and deliverables planned but not completed including the Government acknowledgement and approval of the incomplete work. The contractor shall provide a monthly status report by the 10th of the first month after receipt of order for approval. [CDRL A004, Presentation Material - Status Report]

The monthly status report shall be submitted to the COR, ACOR (if identified), and PM. The report shall:

• Summarize accomplishments of the previous month

• Discuss major issues and/or concerns, and recommend solutions

• Discuss plan for upcoming month

• Provide update on schedule and any actual or anticipated delays

• Provide any recommendations or additional actions needed on the Government side

• Any additional information requested by COR or PM.

4.6 Meetings, Briefings, Etc.

The Contractor shall prepare meeting minutes, briefings, background papers, Item of Interest (IOI’s), Bullet Background Papers (BBP’s), bottom line up front (BLUF) and ready to send (RTS) electronic mail, communication and coordination tracking system(s), and/or other correspondence, briefing and/or supporting documentation delivered timely and upon Government request IAW Government guidance, or in formats meeting the Tongue and https://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodm/857001m.pdf

PR: F3Q3AH4170AW01 PWS REVISION: 0 14

Quill standards, or published Action Officer templates. [CDRL A005, Technical Reports - Studies/Services], [CDRL A006, Presentation Materials - Slides], [CDRL A007, Presentation Materials - Briefings]

The Contractor shall participate in meetings, video-teleconferences, web-based collaboration events, working groups, and briefings providing technical support, briefing updates and progress, and advising on subject matter expertise.

For meetings with senior leadership requiring presentation/informational/decision, read-aheads, documentation, and artifacts shall be provided a minimum of 24 hours prior to the scheduled meeting.

4.7 Other Reporting Requirements

In addition to the deliverable requirements identified herein, the contractor shall bring risks, problems, or potential problems affecting contract performance to the attention of the COR/ACOR within the next business day of discovery. Verbal reports shall be followed up with written reports within the next business day. The contractor shall not perform any work outside the scope or requirements of this PWS and resultant order without express written approval of the CO.

4.8 Training

The Contractor shall be responsible for the employment, training, guidance, and supervision of qualified personnel to accomplish this contract. Contractor personnel are required to possess the skills necessary to support their company’s minimum requirements of the labor category under which they are performing. Employee time spent in the above-mentioned training or training necessary to meet minimum requirements to include certifications will not be paid for by the Government or charged to the contract.

Unique Training: Training of contractor employees in subjects unique to the Government, which is necessary for employees to function in their assigned working environment, is only permitted with prior approval by the COR or CO charged to this contract. The contractor’s employees may participate in other Government provided training under the following circumstances:

• The contractor employees’ participation is on a space-available basis

• The contractor employees’ participation does not negatively impact performance of this contract

• The Government incurs no additional cost in providing the training due to the contractor employees’ participation, and Man-hours spent due to the contractor employees’ participation in such training are not invoiced to the contract, unless necessary to meet for employees to function in their assigned work environment.

4.9 Travel

At government request, the Contractor shall be required to travel to participate in meetings, reviews, audits, and research necessary in accomplishing assigned tasks. All travel requirements (including destinations, plans, agenda, itinerary, dates) shall be approved in advance by the COR or ACOR and be performed IAW the Joint Travel Regulation (JTR). Local travel within 50-mile radius of Robins Air Force Base will not be reimbursed.

The Contractor shall complete a Travel Authorization Request (TAR) and submit to the COR and ACOR for approval no later than five (5) business days before travel begins. Reimbursable travel authorized by the COR or ACOR will be within the continental United States. Destinations will be coordinated between

PR: F3Q3AH4170AW01 PWS REVISION: 0 15

the Contractor and the COR or ACOR. The Contractor’s TAR shall be in writing and contain the dates, locations, and estimated costs of the travel. Changes to TAR/itinerary, especially for cost increases, shall be made in writing and via verbal communications to the COR or ACOR within 24 standard hours.

Contractor shall await COR or ACOR approval. Receipts must be presented with the invoice for reimbursement of actual travel costs.

For all long-distance travel, the Contractor shall submit Trip Reports no later than ten (10) business days after completion of a trip.

The Trip Report shall include the following information:

• Personnel traveled

• Dates of travel

• Destination(s)

• Purpose of Trip; contract effort supported and Task number; Major Command (MAJCOM) supported (if applicable); training (be specific)

• Details of what happened, presentation material, action items, decisions, and minutes from the meeting.

• Actual Trip Costs

• Cumulative Contract Travel Expenditures

• Approval Authority (Copy of the e-mail authorizing travel by Government official)

• Summary of events

4.10 Option Period

Should an option period be exercised, contractor shall continue to complete requirements above to resolve any items delayed by government caused or government approved delays, continue to support and maintain the environment as outlined above, continue to improve and develop automation, and continue to support 78 ABW/SCP programs and teams with the use and improvement to this environment.

4.11 Transition-Out Plan

The contractor shall provide a Transition-Out Plan no later than (NLT) 30 calendar days prior to expiration of the contract. [CDRL A008, Phase-Out Transition Plan] The Transition-Out Plan shall facilitate the accomplishment of a seamless transition from the incumbent to incoming contractor/Government personnel at the expiration of the contract. The contractor shall identify how it will coordinate with the incoming contractor and/or Government personnel to transfer knowledge regarding the following:

• Project management processes

• Points of contact

• Location of technical and project management documentation

• Status of ongoing technical initiatives

• Appropriate contractor to contractor coordination to ensure a seamless transition

• Transition of key personnel

• Schedules and milestones

• Actions required of the Government

PR: F3Q3AH4170AW01 PWS REVISION: 0 16

• Any open actions that will not be completed at the end of the contract

The contractor shall also establish and maintain effective communication with the incoming contractor/Government personnel for the period of the transition via weekly status meetings.

5.0 Contractor Roles and Responsibilities

5.1.1 Key Personnel

5.1.2 Cloud Engineer/Technical Lead/Subject Matter Expert (TSME)

The TSME must have a full understanding of the technical approach to be used and will be responsible for ensuring that the Contractor’s team follows that approach. The TSME must have a full understanding of automating Cloud solutions end-to-end, adhering to DevSecOps principles of Infrastructure as Code, build once-deploy anywhere, rapid prototyping, Continuous Integration and Continuous Delivery (CI/CD).

5.1.3 System Administrator/Database Administrator

This role must understand cloud technologies and implementations, knowledge and ability to stand-up and support Linux and Windows based servers, and ability to stand-up and administer SQL Server and Oracle databases under coordination of the TSME.

5.1.4 Key Personnel Substitution

In order to substitute any Key Personnel, those substitutions must be accepted by the Government in writing, and will only be justified by the Government request, sudden illness, death, change of employment, or termination of employment for cause.

Contractor requests for a substitution of Key Personnel must include a detailed explanation of the justifying circumstances, and a list of qualifications for the proposed substitute or addition, including skills, experience, education, training, and security level. The Government’s failure to accept a proposed substitution will not constitute grounds for non-performance by the Contractor, or form a valid basis for any claim for money or any equitable adjustment. In the event of a Key Personnel’s departure from the contract the Contractor will, ideally, have a replacement identified and accepted by the Government so there is no gap in service. However, the Contractor must propose a Key Personnel replacement no later than ten (10) business days of the original Key Personnel’s departure date. The Government has ten (10) business days to accept or reject a proposed substitution.

6.0 Period and Place of Performance

6.1.1 Contract/Order Period of Performance: The period of performance for the contract/order will extend 12 months from the date of award with performance to start no earlier than 01 September 2024.

6.1.2 Place of Performance: These services will be performed remotely by the Contractor for the most part. If travel and attendance requested for in person workload then the location will be Robins Air Force Base in Building 228 unless another venue is specified.

6.1.3 Contract Support Hours: Contractor shall maintain core support hours of 0700-1700 eastern standard

PR: F3Q3AH4170AW01 PWS REVISION: 0 17

time to align with 78 ABW/SCP program teams.

PR: F3Q3AH4170AW01 PWS REVISION: 0 18

6.2 Contract Data Requirements List(s) (CDRL)

Document Identifier Base Year

Option Year 1

DID Title PWS Reference(s)

A001 B001 DI-ADMN-81373 Presentation Materials - Project Kickoff 4.3 A002 B002 DI-MGMT-81117A Technical Report – Migration Plan 4.3, 4.4 A003 B003 DI-ADMN-81373 Presentation Materials - IMS 4.3, 4.4 A004 B004 DI-ADMN-81373 Presentation Materials - Status Report 4.5 A005 B005 DI-MISC-80508 Technical Report – Studies and Services 4.4, 4.6 A006 B006 DI-ADMN-81373 Presentation Materials - Slides 4.6 A007 B007 DI-ADMN-81373 Presentation Materials -Briefings 4.4, 4.6 A008 B008 DI-MGMT-81945 Phase-Out Transition Plan 4.11 A009 B009 DI-MISC-80508 Technical Report - Quality Control Plan 7.9 A010 B010 DI-SAFT-81563 Accident/Incident Report 7.5.2, 7.5.4

6.2.1 Quality of CDRL Deliverable: There shall be no more than one rejection of any deliverable.

There shall be no more than three (3) total rejection(s) of deliverables per Contract Year. The Government will reject a deliverable if two (2) or more technical errors or four (4) or more minor errors are found within the deliverable. A technical error is defined as the format not being in accordance with the CDRL or the content not being accurate and complete in accordance with the CDRL, PWS or contract. A minor error is exemplified by a typographical error, a grammatical error, etc. The rejected deliverable shall be corrected and resubmitted within three (3) business days of notification of Government rejection.

6.2.2 Receipt of CDRL Deliverable: CDRL deliverables shall be submitted via email to the 78 ABW/SCP COR and PM along with any other members identified during the execution of this contract.

There shall be no more than three (3) late submission(s) of deliverables per Contract Year. The Contractor shall notify the Government if the delivery of any data/document will not meet the scheduled delivery date and negotiate a revised delivery date. The data/document shall be delivered by the revised delivery date acceptable to the Government.

6.2.3 Deliverable Rights: All test materials, documents, notes, records, software tools acquired, and/or software produced by the contractor under this PWS shall be provided to the Government, which shall have unlimited rights to all materials and determine the scope of publication and distribution.