Attachment 2 - DRAFT PWS.pdf

Performance Work Statement

LaunchPad 2.0

Background

The Department of War (DoW) is advancing numerous digital technologies and platforms as part of a major digital transformation effort. The Department of the Air Force (DAF) needs to accelerate delivery of warfighting capability through deployment and use of commercial software tools and training to streamline data sharing, acquisition activities, and informational exchanges across industry and government. The DAF goal is develop and deploy an enterprise approach for commercial software digital tool usage, resulting in reduced program delivery times.

As a response for developing access to commercial software tools across for all acquisition functionals, the DAF Digital Transformation Office (DTO) stood up an environment called

LaunchPad. LaunchPad provides Airmen and Guardians with free, easy, and secure access to cloud-based commercial software tools to allow for a digital-first approach. The benefits of

LaunchPad go beyond simple access to tools; LaunchPad creates an environment where you can collaborate in real time, so problems are no longer left to be solved in silos.

Purpose

The purpose of this Performance Work Statement (PWS) is to establish a Task Order (TO) to develop LaunchPad 2.0 to provide a centralized and accessible platform for a variety of commercial software tools to promote engineering, program management, logistics, technical analysis, modelling, simulation, and collaboration among acquisition personnel serving in multiple functions while allowing users to efficiently interact with data, collaborate with colleagues and deliver leading-edge capabilities.

Government Owned Baseline: The developed architecture, Infrastructure as Code (IaC), Configuration as Code (CaC), and hardened application containers shall be owned by the

Government to enable deployment across other classification levels and environments.

Objective

The objective of this TO is to provide the Digital Transformation Office (DTO) with a cloud based digital environment that can host commercial software tools at Controlled Unclassified

Information (CUI) and Secret levels that can be integrated with common enterprise services across Department of the Air Force (DAF) and Department of War (DOW) enterprise digital environments.

Tasks

The following tasks are in support of this TO and are detailed below:

a. Task 1 – Program Management

b. Task 2 – LaunchPad 2.0 Environment

c. Task 1- Program Management

The Contractor shall provide management and oversight of all activities performed by contractor personnel, including subcontractors (if applicable) to satisfy the requirements of this PWS. The

Contractor shall facilitate Government and Contractor communications and all activities necessary to ensure the accomplishment of timely and effective support, performed in accordance with the requirement contained in this contract.

The Contractor shall conduct regular reviews of the staff assignments and Contractor’s monthly progress and status with the assigned government Contracting Officer Representative (COR).

The Contractor shall inform the COR of any technical, financial, personnel or general managerial problems encountered throughout the contract’s period of performance.

Project Kick-Off Meeting

The Contractor shall schedule, coordinate and host a Project Kick-Off Meeting

(Deliverable X) (virtual or at a location approved by the Government). The meeting shall provide an introduction between the contractor personnel and Government personnel who will be involved with the TO. The meeting shall provide the opportunity to discuss technical, management and security issues and reporting procedures. At a minimum, the attendees shall include the Contractor’s key personnel, the Government Technical Point of Contact (TPOC)/COR, the contracting officer (CO) and any other relevant

Government personnel.

The Contractor shall provide a Project Kick-Off Meeting Agenda for review and approval by the TPOC/COR no later than three workdays prior to the Project Kick-

Off Meeting. The agenda shall include, but is not limited to, the following topics/deliverables:

a. Points of Contact (POCs) for all parties.

b. Personnel discussion (e.g., roles and responsibilities and lines of communication between

Contractor and Government).

c. Transition-In Plan (Deliverable X) discussion.

d. Security discussion and requirements (e.g., building access, badges, Common

Access Cards (CACs)).

e. Financial reporting and invoicing requirements.

The Government will provide the contractor with the number of Government partici pants for the Project Kick-Off Meeting, and the contractor shall provide copies of the presentation for all present. The contractor shall draft and provide a Project

Kick-Off Meeting Minutes Report (Deliverable X) documenting the Project Kick-

Off meeting discussion and capturing any action items.

Monthly Status Report (MSR)

The contractor shall develop and provide a Monthly Status Report (MSR) (Delivera ble X). The MSR shall include, but is not limited to, the following:

a. A brief description of the task at the beginning of each section.

b. Activities during the reporting period, by task (include ongoing activities, new activities, activities completed, and progress to date on all above-mentioned activities).

c. Problems and corrective actions taken.

d. Issues or concerns and proposed resolutions to address them.

e. Personnel gains, losses, and status (security clearance, etc.).

f. Government actions required.

g. Schedule (show major tasks, milestones, and deliverables; including planned and actual start and completion dates for each).

The MSR shall be in a format agreed upon by the TPOC and COR.

Conduct and Attend Program Meetings

The contractor shall conduct, attend, and participate in various project- and program-related meetings. Meetings shall be conducted at either contractor or Government facilities.

The project and program meetings shall include, but is not limited to, the following:

a. Technical Status Meeting (TSM): The Contractor PM shall convene a monthly

TSM with the TPOC and COR, and other Government stakeholders (Deliverable X). The purpose of this meeting is to ensure all stakeho lders are informed of the monthly activities and MSR, provide opportunities to identify other activities and establish priorities; and coordinate resolution of identified problems or opportunities. The Contractor PM shall provide a meeting minutes report of these meetings to the COR. (Deliverable X).

b. Program Management Review (PMR) meetings: The contractor shall conduct quarterly PMR meetings, focused on progress, task adjudication, and issues that may affect the overall program with the TPOC and COR, and Government stakeholders (Deliverable X). The PMR shall report on staffing, financial status, and Technical Direction Plans (TDPs). As a pa rt of the PMR, the contractor shall be prepared to explain the reasoning, assumption, and methodologies in arriving at conclusions, recommendations, or alternatives in the accomplishment of the tasks required by the TO. The

Contractor shall have Key Personnel available to support the PMR.

Subcontractors shall attend PMR meetings when required to address key elements. The contractor shall prepare the PMR agenda, meeting reports, and presentation materials ideally 7 days (minimum 3 business days) before the schedule PMR date. The contractor PM shall provide a meeting minutes report of these meetings to the AAS COR (Deliverable X). PMRs shall be conducted quarterly; however, more frequent PMRs may be required

Transition In

The Contractor shall provide a final Transition-In Plan (Deliverable X) within five calendar days after the Project Kick-Off Meeting. The contractor shall ensure that there will be minimum service disruption to vital Government business and no service degradation during and after transition-in. The contractor shall implement its Transition-

In Plan when the Government accepts the Transition-In Plan as final, and all transition activities shall be completed 90 calendar days after Project Start (PS). During the transition-in period, the contractor shall prepare to meet all TO requirements and ensure all incoming personnel are trained and qualified to perform. During the transition-in period, the contractor’s personnel shall interface with Government personnel and other

Contractor personnel for purposes of transferring knowledge, lessons learned and continuity of information and documents for the commencement of performance.

Transition Out

The Contractor shall provide transition-out support when required by the Government.

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

The contractor shall provide a draft Transition-Out Plan NLT 120 calendar days after contract award and a finalized Transition-Out Plan NLT 120 calendar days prior to expiration of the TO (Deliverable X). The contractor shall review and update the

Transition-Out Plan in accordance with the specifications in Sections E and F. In the

Transition-Out Plan, the contractor shall identify how it will coordinate with the incoming contractor and/or Government personnel to transfer knowledge regarding the following:

a) Project management processes.

b) POCs.

c) Location of technical and project management documentation.

d) Status of ongoing technical initiatives.

e) Appropriate contractor-to-contractor coordination to ensure a seamless transition.

f) Transition of Key Personnel roles and responsibilities.

g) Schedules and milestones.

h) Long lead items, deliveries, and mitigations.

i) Actions required of the Government.

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 or as often as necessary to ensure a seamless transition-out. All facilities, equipment, and material utilized by the contractor personnel during performance of the

TO shall remain accessible to the contractor personnel during the transition-out period pursuant to the applicable security in- processing and out-processing guidelines.

Task 2- LaunchPad 2.0 Environment Build Out and Support

Interoperability: The Contractor shall provide and maintain a framework that enables seamless data exchange and process integration between all tools within the LaunchPad

2.0 environment and other specified DAF/DoW systems. The Contractor is responsible for developing, deploying, and maintaining the necessary interfaces to achieve this, regardless of tool ownership. The solution must integrate CAC (Common Access Card) passthrough to allow for seamless and secure authentication to authorized resources within and outside the environment.

Cloud-Based: The Contractor shall provide a solution that can operate within the Air

Force's Cloud One environment, Cloud One boundary protected and/or brokered accounts, as directed by the Government for specific use cases.at Control Unclassified

Information Impact Level 5 (IL-5) and Secret Impact Level 6 (IL-6).

Scalability: The Contractor shall ensure the proposed architecture of the environment supports yearly 250% growth rate, from 4,000 current user accounts (400 active weekly users) to 80,000 user accounts (8,000 active weekly users) by 30 Sep 2030. The design should leverage Cloud based technologies to enable autoscaling of compute and storage resources.

Data and Model Integration: The LaunchPad 2.0 environment must be able to integrate with other DAF/DoW systems and authoritative data sources as directed by the

Government to maintain a "digital thread" of information throughout a system's lifecycle.

An example of the type of data integration could be Big 6 data platform.

Security and Compliance: The Contractor shall ensure the proposed expansion adheres to all Department of War (DoW) cybersecurity requirements, including utilizing advanced data security methods.

Capability Delivery: The Contractor shall ensure deployment of the Government requested commercial software tools shall be completed within 6 weeks- unless otherwise agreed upon by the Contractor and Government of receiving the Authority to Operate

(ATO). The Contractor shall be responsible for preparing and submitting all necessary documentation for obtaining and maintaining the Authority to Operate (ATO). The

Contractor shall provide regular software updates, including all necessary security and performance patches, with a documented and Government-approved release cycle.

User Experience: The Contractor shall provide a solution that maintains a standardized user interface (UI) and interaction model across IL-5 and IL-6 environments. The solution shall support multiple user personas (e.g., Program Manager, Engineer, Data

Scientist) by providing customized workspaces and toolsets tailored to Material

Management functional roles. The environment must feature automated user onboarding by consuming and integrating with DAF ICAM or DoW ICAM identity services. The system shall be continuously upgraded based off Government direction based on user feedback. A common user experience shall include, at a minimum: a unified portal for accessing all tools, Single Sign-On (SSO), a consistent visual design across the environment, and centralized user profile management. The Contractor shall conduct regular User Feedback sessions (minimum 2 per year) and provide the unfiltered results to the Government. The proposed solution shall require minimal rework to deploy an IL-

5 capability to the IL-6 environment.

Application and License Monitoring: The Contractor shall provide a dashboard to

Government administrators for monitoring application usage, license consumption, and overall cloud spend in near real-time.

Common Code Repository: The solution shall provide a shared, common code repository (e.g., Gitlab) for all users, including features for version control and collaborative development.

Tool Visibility and Access Requests: The environment shall provide a user-facing service catalog that allows users to view all available software tools and submit automated requests for access.

Environment Partitioning for Security: The architecture must support partitioning for spillage events, with the ability to rapidly isolate affected users or environment segments to prevent lateral movement and data compromise.

Seamless User Transition: The Contractor shall develop and execute a phased transition plan to seamlessly migrate all users and their data from the legacy LaunchPad 1.0 environment to LaunchPad 2.0 with minimal disruption.

Future AI Integration: The environment shall enable controlled connectivity for artificial intelligence (AI) technologies, including integration with both Department of

War (DoW) enterprise and commercial software platforms. Furthermore, it shall support future embedded AI capabilities by providing authorized access to Department of

Defense–approved large language model (LLM) data environments and services. To support these evolving capabilities, the environment must ensure interoperability, scalability, and full compliance with all applicable cybersecurity and data governance requirements.

Data Transfer: The Contractor shall ensure the proposed solution enables frictionless data transfer into the environment as well as between environments at the same classification level. The solution shall provide intuitive, well-documented mechanisms for data transfer, such as a graphical user interface with drag-and-drop functionality and automated, scriptable methods (e.g., API calls) for bulk data transfers. The proposed environment shall provide a method for industry to deliver and validate digital Contract

Data Requirements Lists (CDRLs) and models to DAF programs using LaunchPad.

Cross Domain Solution: The solution shall deploy and maintain a Government-approved Cross-Domain Solution (CDS) to enable secure, automated file transfers from lower to higher classification levels, supporting native tool formats where possible.

Access to DAF/DoW Resources: The Contractor shall ensure the proposed environment will enable users to access certificate enabled resources from the environment as directed by the Government. For example: Access DAF O365, Air Force Product Lifecycle

Management (AF PLM), Test Resource Management Center (TRMC), or Modelling and

Simulation (M&S) Gateway from the LaunchPad 2.0 environment.

User Account Management: The system must support the creation and management and revocation of all LaunchPad users based off of authorization status through DAF

ICAM. The digital environment shall implement Department of the Air Force (DAF) approved Identity, Credential, and Access Management (ICAM) solutions, using DAF

ICAM for Impact Level 5 (IL5) and Department of War Enterprise ICAM (DoW E-

ICAM) for Impact Level 6 (IL6). Furthermore, the environment must securely support access for approved industry and academic mission partners at both IL5 and IL6, in accordance with the policies set forth in the DAF ICAM Implementation Memorandum.

Multi-Tiered Helpdesk Support: The Contractor shall serve as the Tier 2 and Tier 3 helpdesk for the LaunchPad 2.0 environment, responsible for resolving all complex technical issues, system failures, and infrastructure-related problems. The Contractor will work in collaboration with a separate Tier 1 helpdesk provider, to be designated by the

Government. This includes establishing and maintaining documented procedures for ticket escalation, communication, and resolution between the support tiers.

Service Level Agreement: The Contractor shall meet defined Service Level Agreements

(SLAs), including 99.9% uptime for production environments, a Mean Time to Repair

(MTTR) of 4 hours for critical incidents, and tiered support response times." This could be added to requirement #36 (High Availability/High Scalability).

LaunchPad 2.0: MVP vs Follow on Release Timeline

Phase Timeline Requirements

LP 2.0

(MVP)

3 Months from Award

Core Infrastructure & User Access Ability to support up to 10,000 users at IL-5 and 2,000 users at IL-6

Support for Multiple Personas: Customized workspaces for different roles based off of Acquisition functionals.

Data Source Connectivity: Connection to OneDrive

Classification Deploy ability: Operation at IL-5 and IL-6.

Automated User Onboarding: Consume DAF ICAM or DoW ICAM for automated onboarding.

Single Sign-On (SSO): Integrate with enterprise SSO.

Software Tool Offering: Include all software tools currently available on

LaunchPad 1.0 at their respective classification level

Integration with Other Services: Connect to services HPC and AF-PLM:

Cloud Agnostic: Enable deployment across various cloud providers (AWS, Azure) either through Cloud One boundaries or CloudOne brokered.

Regular Software Updates: Provide regular security and performance patches.

Ease of Use: Provide intuitive interfaces and navigation.

Data Sharing: Enable easy data sharing between tools within the environment through DAF365. Provide data sharing and data storage internal to LaunchPad

2.0 infrastructure

Tool Visibility and Access Requests: Allow users to see and request available tools.

CAC Passthrough Integration: Allow CAC for secure authentication.

Application and License Monitoring: Monitor usage, licenses, and cloud spend.

Common Code Repository: Provide a shared code repository (e.g., Gitlab).Partitioning for Spillage Events: Isolate affected areas during security incidents.

Data Backup: Perform daily backups of all information.

Seamless Transition for Users: Phased approach for migrating users from

Launchpad 1.0.

Cyber Requirements: Generate build-outs from a master branch, review benchmarks, etc.

LP 2.1 MVP + 6

Months

Scalability and Performance: Scale to 80,000 users (20,000 concurrent) leveraging autoscaling technologies

Tool Onboarding: Deploy new tools within 6 weeks.

Ability to support Enterprise Linese server

Role and Permission Inheritance: Inherit roles and permissions from DAF systems

Cloud Spend Prediction: Predict cloud spend for budget planning.

Temporary Access for Outside Collaboration: Allow temporary access for

Industry and Academic partners.

LP 2.2 MVP + 12

Months

Cross Domain Solution (CDS): Deploy and maintain a Government-approved

CDS for automated file transfers from lower to higher classification

Ephemeral Enclave Support: Create temporary, isolated, and secure workspaces.

Air-Gapped Environment Deployment: Deploy to environments disconnected from the internet.

Support for Training/Experimentation: Provide ephemeral environments for non-production work.

Cross-Partner Collaboration: Support collaboration with industry and international partners.

Permission Scalability Based on Badging: Use digital badges for Attribute-

Based Access Control.

Offline Work Capability: Allow users to work offline and sync later.

Automation Tooling Integration: Integrate with chatbots and workflow automation.

Place of Performance

The primary place of performance where the Contractor will perform the work is X. Long-distance travel is not anticipated to be required in support of this effort.

Period of Performance

A base period of one year, with up to two twelve-month option periods.

Deliverables

The following schedule of milestones will be used by the COR to monitor timely progress under this TO. Deliverables are due the next Government workday if the due date falls on a holiday or weekend.

The Contractor shall deliver the deliverables listed in the following table on the dates specified:

Deliverable # Deliverable TO Reference Date of

Completion

Project Kick Off

Meeting Agenda

& Presentation

4.1.1 NLT 3 workdays

prior to Project

Kick Off

Meeting

Project Kick Off

Meeting

4.1.1 NLT 5 workdays

following project start

Meeting Minutes

Report

NLT 3 workdays following meeting

Transition In

Plan

4.1.4 NLT 5 workdays

after the Project

Kick Off

Meeting

Monthly Status

Report (MSR)

4.1.2 Monthly, NLT

15th calendar day of the next month

Monthly

Technical Status

Meeting (TSM)

4.1.3 Monthly

Program

Management

Review (PMR)

4.1.3 Quarterly

Transition Out

Plan

4.1.5 NLT 120

calendar days prior to expiration of the

TO, then quarterly during the final Option

Period

Cost

Effectiveness

Business Case

4.2.2 NLT 5 workdays

after the Project

Kick Off

Meeting

Technical Data

Package

5.1.5 NLT 30 days

after Transition-

In period complete

LaunchPad 2.0 deployed

NLT 90 days after contract award

LaunchPad 2.1 deployed

NLT 6 months after contract award

LaunchPad 2.2 deployed

NLT 12 months after contract award