PWS - Enterprise Analytics Infrastructure Management v5.pdf

Draf t

Performance Work Statement

For

Infrastructure Management

Department of Defense

Chief Digital and Artificial Intelligence Office

Solicitation # TBD

XX August 2024

Table of Contents

1.0 Introduction

1.1 Background

1.2 Objectives

1.3 The Advana Operating Environment

1.4 The Advana System

1.4.1. Definitions

1.4.2. The Advana v1.0 System

1.4.3. The Advana v1.2 System

1.5 The Advana Service Desk

2.0 Requirements

2.1 Program Management

2.1.1. Program Roadmaps and Schedules

2.1.2. Deliverable Management and Tracking

2.1.3. Program Budgeting and Financial Management

2.1.4. Agile Software Management

2.1.5. Program Audit

2.1.6. Monthly Status Reports

2.1.7. CCB/ECB Support

2.1.8. Personnel

2.1.9. Deliverables

2.2 Platform Infrastructure Management

2.2.1 Advana System v1.0 Operations, Sustainment, Migration, and Shutdown

2.2.2 Enterprise Engineering

2.2.3 Commercial Tool Identify, Preparation, and Integration

2.2.4 Agile Software Development

2.2.5 Continuous Integration/Continuous Delivery

2.2.6 Operations and Maintenance

2.2.7 Tier 2/3 Service Desk Support

2.2.8 Testing and Independent Verification and Validation

2.2.9 Cybersecurity Risk Management and Operations

2.2.10 Change and Configuration Management

2.2.11 Continuous Technology Improvement

2.2.12 Policy-Based Platform Governance

2.2.13. Advana Cost Tracking and Reporting

2.2.14. Deliverables

2.3 Data and AI Infrastructure Management

2.3.1 Data Operations

2.3.2 Data and AI Model Connections

2.3.3 AI/ML Operations and Services

2.3.4 AI/ML Capability Development

2.3.5 AI/ML Model-as-a-Service

2.3.6. Deliverables

2.4 User Experience and Customer Success

2.4.1 Stakeholder Engagement

2.4.2 Stakeholder Strategic Communications

2.4.3 Customer Relationship Management

2.4.4 Customer Use Case Solutioning

2.4.5 Customer and User Analytics

2.4.6 User Success

2.4.7 User Interface/Web Interface Design

2.4.8 User Training

2.4.9 Service Portfolio Management

2.4.10 Service Catalog Management

2.4.11 Knowledge Management

2.4.12 Personnel, Clearance, and Onsite Requirements

2.4.13. Deliverables

2.5 Advana Tier 0/1 Service Desk

2.5.1 Advana Service Desk Operations

2.5.2 Queue Management

2.5.3 Advana Service Desk Training and Documentation

2.5.4 Advana Service Desk as a Product

2.5.5. Deliverables

3.0 Performance Management

3.1 General

3.2 Services Summary (SS)

4.0 General Requirements

4.1 Period of Performance

4.2 Place of Performance

4.3 Key Personnel

4.3.1. Program Manager (PM)

4.3.2. Chief Architect/Engineer

4.3.3. Chief Cybersecurity Engineer

4.3.4. Chief Data/AI Engineer

4.3.5. Customer Success Lead

4.3.6. Key Personnel Substitution

4.4 Government Furnished Property and Information

4.4.1. Government Furnished Property

4.4.2. Government Furnished Information

4.5 Security

4.5.1. Information Assurance

4.5.2. Classification

4.5.3. Public Key Infrastructure (PKI) Requirements

4.5.4. Security Clearances

4.5.5. Facility Clearance

4.5.6. Foreign Ownership, Control, or Influence (FOCI)

4.5.7. Safeguarding Sensitive Data and Resources

4.6 Training and Permits

4.6 Travel and Authorization Requests (TAR)

5.0 Data Management

5.1 Data Requirements

5.2 Data Rights

1.0 Introduction

1.1 Background

Advana is the Department of Defense (DoD) Chief Digital and Artificial Intelligence

Office’s (CDAO) enterprise-wide, multi-domain data, analytics, and artificial intelligence

(AI) platform that provides all DoD military and civilian decision makers, analysts, and builders with unprecedented access to enterprise data, tools, and capabilities—all in a scalable, reliable, and secure environment. The mission of the DoD CDAO’s Advana program is to accelerate decision advantage by making data, analytics, and AI widely accessible, understandable, and actionable across DoD. To do this, the Advana platform hosts hundreds of curated applications providing analytics for logistics, financial management, personnel, health, and many other domains; it provides market-leading, self-service tools to perform data exploration, model development, data visualization, and other analysis activities; and it provides both consumers and builders on-demand data, analytics, and AI capabilities via a DoD-wide platform.

1.2 Objectives

The objectives for this procurement are as follows:

1. Objective #1. Obtain program management services that drive continuously improving program efficiencies and operational effectiveness.

2. Objective #2. Provide the DoD with a secure, state-of-the-art Platform to support

DoD data, analytics, and artificial intelligence (AI) missions that operate across multiple cloud service providers and security enclaves.

3. Objective #3. Seed the DoD with a strong foundation of Enterprise Data and AI tools and services.

4. Objective #4. Ensure the highest quality user experience and customer success for all mission activities conducted using the Advana Platform.

5. Objective #5. Provide and operate a state-of-the art Service Desk for Advana across all its operating environments.

1.3 The Advana Operating Environment

The following definitions related to the Advana Operating Environment will be used throughout this PWS document:

• Cloud Service Provider (CSP) is a Federal Risk and Authorization

Management Program (FedRAMP)-approved cloud that hosts elements of the

Advana System. For this acquisition, the Advana System will be deployed and operated on one CSP – the Amazon Web Service (AWS) GovCloud.

• Security Enclave is a network/information environment that is isolated, protected, and operated with security controls that are appropriate for the activities of the security enclave. For this acquisition, the Advana System will be deployed and operated on the following security enclaves: IL2, NIPRNet/IL5, SIPRNet/IL6, and JWICS.

• Advana CSP/Security Environment is a pairing of a specific CSP and a specific security enclave. For example, AWS – NIPRNet/IL5.

• Advana Operating Environment is the superset of all Advana CSP/Security

Environments (e.g., all combinations of CSPs and security enclaves) across which the Advana System operates. For this acquisition, the Advana

Operating Environment will consist of the following Advana CSP/Security

Environments:

o AWS – IL2 o AWS – NIPRNet/IL5 o AWS – SIPRNet/IL6 o AWS – JWICS o AWS – SUNet/IL5

SUNet is a DoD network/information environment that operates that supports Coalition operations at IL4, IL5 and IL6.

In Section 2, the term “Advana Operating Environment” will be used to indicate requirements that will need to be performed across all the Advana CSP/Security

Environments listed above.

1.4 The Advana System

1.4.1. Definitions.

The following definitions related to the Advana System will be used throughout this PWS document:

• Advana Platform is the complete collection of all source code, tools, libraries, virtual machines, containers, Infrastructure-as-Code (IaC) and Configuration-as-Code (CaC) that constitutes a complete software baseline for the instantiation of an Advana Node.

• Advana Node is an instantiation of the Advana Platform that runs in a particular Advana CSP/Security Environment – for example, the Advana

AWS/SIPRNet Node.

• Advana System is the collection of all Advana Nodes running across all

Advana CSP/Security Environments.

• Advana v1.0 System is the current operational version of the Advana System that is currently supporting 80,000+ users.

• Advana v1.2 System is the under-development version of the Advana System that is incorporating new mechanisms to speed up development and delivery, add extensive automation, and provide more robust cybersecurity controls.

1.4.2. The Advana v1.0 System.

The Advana v1.0 System has been under development and operation since 2018. It began with a focus on supporting DoD business and financial use cases. The success of

Advana v1.0 with the DoD business and financial community led to rapid growth and expansion. Advana now supports many DoD communities – including Acquisition, Decision Support, Energy, Health, Readiness, I.T., Intelligence, and Logistics. In addition, the scale of Advana v1.0 System has swelled to 80,000+ users, 600+ enterprise data sources, and 100+ tools and applications. It operates in the AWS Government cloud at three security levels – NIPRNet, SIPRNet, and JWICS. The original Advana v1.0

System implemented basic security controls that met the minimum criteria for system authorization.

The primary work requirements for the Advana v1.0 System will be to:

• Operate and sustain the Advana v1.0 System while the development of the

Advana v1.2 System is completed.

• Migrate Advana v1.0 System customers and workloads to the Advana v1.2

System when the Advana v1.2 System becomes operational.

• When migration is completed, shutdown the Advana v1.0 System.

1.4.3. The Advana v1.2 System.

To address the massive leap in scope and scale, the Advana System is undergoing a major rearchitecting and modernization activity that will result in a future Advana v1.2 System.

The Advana v1.2 System extends the Advana v1.0 System to cover the full scope and scale of the DoD enterprise. Scale will be extended to 250,000+ users, provide much higher levels of automation, improve the ability to incorporate new tools and services, and move to fully leverage modern DevSecOps processes and container-based software approaches. The Advana v1.2 System takes Advana into the future by providing DoD users with comprehensive access to the best commercial data, analytic, and AI tools and services, available in the best form factor for their operational needs. The Advana v1.2

System is currently under development and is not yet authorized to support customer operations.

A more detailed description of the Advana v1.0 and v1.2 Systems is provided in the document “Advana Current Environment” which is provided as part of the RFP package for this acquisition.

1.5 The Advana Service Desk

The Advana Program operates a Service Desk to provide customer support to Advana customers and users of the Advana System. The Advana Service Desk is operated using four Service Tiers as follows:

• Tier 0 – Self Help. On-line help and training material provided as self-help capabilities to Advana customers and users that is available via the Advana

System website 24/7/365.

• Tier 1 – Standard Support. The first level of Advana human-in-the-loop Service

Desk support. It provides basic support including the receipt and cataloging of user help requests, provisioning user accounts, helping with access to system resources, executing standard service requests, and providing basic trouble shooting. In the Advana System, Tier 1 support is required to be provided all

Federal business days from 0800 EST/EDT to 2400 EST/EDT.

• Tier 2 – In-Depth Support. The second level of Advana human-in-the-loop

Service Desk support that is invoked when user issues cannot be resolved at

Tier 1. Tier 2 provides a greater level of technical expertise to address user issues that cannot be addressed by following standard Tier 1 problem resolution playbooks.

• Tier 3 – Expert Support. The third and final level of Advana human-in-the-loop Service Desk support that is invoked when user issues cannot be resolved at Tier 2. Tier 3 addresses problems that require changes or fixes to the underlying Advana System.

Advana Tier 0 and Tier 1 Service Desk requirements are addressed in their own Section

2.5. Advana Tier 2 and Tier 3 Service Desk requirements are expected to be addressed by the technical experts supporting the requirements in Section 2.2 and 2.3 and are therefore addressed in those Sections.

Note that the Advana Service Desk will support both the Advana v1.0 System and the

Advana v1.2 System.

Note that all requirements in Section 2 will be applicable to both the Advana v1.0 System and the Advana v1.2 System unless specially indicated otherwise.

2.0 Requirements

2.1 Program Management

The contractor shall provide program management that drives continuously improving program efficiencies and operational effectiveness.

The contractor shall conduct all Program Management requirements for both the Advana v1.0 System and the Advana v1.2 System.

The contractor shall:

2.1.1. Program Roadmaps and Schedules.

The contractor shall prepare and maintain program roadmaps and an Integrated Program

Schedule (IPS), overseeing the execution of program activities to ensure schedules are met.

2.1.2. Deliverable Management and Tracking.

The contractor shall manage all aspects of preparing, tracking, and reporting on the status of contract deliverables and shall maintain a deliverable tracking system that keeps up to date information on the status of all deliverables.

2.1.3. Program Budgeting and Financial Management.

The contractor shall prepare and maintain an Integrated Program Budget (IBP) that covers all financial aspects of managing and executing the program.

2.1.4. Agile Software Management.

The contractor shall implement and execute an Agile software management process and host a viable Agile Community of Practice to execute all software development for the

Advana System using consistent practices in accordance with Objective and Key Results

(OKR) guidance, Strategic Roadmap development, Increment Planning, and daily task management.

2.1.4.1. Define and maintain an Agile software develop process for executing all aspects of the Advana System software lifecycle.

2.1.4.2. Execute the Advana Agile software process using a two-week sprint cycle.

2.1.4.3. Prepare and coordinate bi-weekly Advana System Sprint Plan(s) and submit them to the Government for review and acceptance.

2.1.4.4. Manage Jira and Confluence instances required for project management, operate change control boards, and provide overall Atlassian tools administration support.

2.1.4.5. Track and maintain metrics on the completion percentage of planned tasks for every Advana Sprint.

2.1.5. Program Audit.

The contractor shall perform all audit response and execution on behalf of Advana management with external independent public auditors in support of an annual SOC1

(System and Organization Controls 1, Type 2) audit. This includes quality reviews over all Provided by Client (PBC) requests, policies and documentation, engagement with

SOC1 customers, and preparation for auditor observations and meetings.

2.1.5.1. Prepare and maintain Advana Management’s Description, assisting control owners in capturing key controls on the platform.

2.1.5.2. Coordinate all phases of Advana audit activities - including planning, execution, and remediation.

2.1.5.3. Coordinate all PBC requests from auditors with Advana platform control owners across the platform in a timely manner.

2.1.5.4. Provide SOC1 customer support to include building instructions and guides in

Section V of the report, all complimentary user end control key supporting documentation, all external customer auditor requests.

2.1.5.5. Identify and provide supporting documentation for key controls that should be included in the Advana SOC1 audit for all major Advana System areas (e.g., engineering, cybersecurity, infrastructure, data, service desk, etc.)

2.1.6. Monthly Status Reports.

The contractor shall provide monthly status reports that provides an in-depth summary of the cost, schedule, and performance state of the program and identify any issues or problems that need input or decisions from the Government to help address.

2.1.7. CCB/ECB Support.

The contractor shall provide support to the Government’s Change Management Control

Board (CCB) and Engineering Control Board (ECB) operations including:

o Recommending CCB and ECB agenda items.

o Prepare CCB and ECB decision packages as needed.

o Providing SMEs to investigate and prepare analyses to support CCB and ECB requests as needed.

o Provide other support to CCB and ECB activities as needed.

2.1.8. Personnel.

2.1.8.1. The contractor shall provide key personnel as defined in Section 4.3 and shall provide resumes for all Key Personnel.

2.1.8.2. The contractor shall provide sufficient cleared personnel in accordance with the security clearance requirements defined in Section 4.5.4 to meet the work requirements defined in Section 2.

2.1.8.3. The contractor shall provide sufficient personnel onsite at the locations defined in

Section 4.2 to meet the work requirements defined in Section 2.

2.1.9. Deliverables.

ID Deliverable

Name

PWS

Para#

Deliverable

Format

Due

Date

Distribution/

Copies

Frequency

D1-1 Integrated Program

Schedule

2.1.1 Contractor - MS

Project or equivalent.

CA+30

days

*Standard Updated

Monthly

D1-2 Program

Roadmaps

2.1.1 MS Word

document using

CDAO template

CA+90

days

*Standard Updated

Quarterly

D1-3 Deliverable Status

Tracker

2.1.2 Contractor - MS

Excel

CA+30

days

*Standard Updated

Monthly

D1-4 Integrated Program

Budget

2.1.3 Contractor – MS

Excel

CA+30

days

*Standard Updated

Monthly

PWS

Para#

Deliverable

Format

Due

Date

Distribution/

Copies

Frequency

D1-5 Agile Software

Process

2.1.4.1 Contractor – MS

Word

CA+30

days

*Standard Updated

Quarterly

D1-6 Bi-Weekly Agile

Sprint Plans

2.1.4.3 Contractor – MS

Word

CA+30

days

*Standard Updated

Bi-

Weekly

D1-7 Agile Software

Metrics

2.1.4.5 Contractor – MS

Word

CA+45

days

*Standard Updated

Quarterly

D1-8 Monthly Status

Reports

2.1.6 Contractor – MS

Word

CA+30

days

*Standard Updated

Monthly

D1-9 CCB/ECB

Decision Packages

2.1.7 Contractor – MS

Word

CA+15

days

+Electronic As needed

D1-10 Key Personnel

Resumes

2.1.8.1 Contractor – MS

Word

CA+15

days

+Electronic As needed

*Standard Distribution: Submit 1 copy of the deliverable electronically to the Primary COR

2.2 Platform Infrastructure Management

This task is for the design, implementation, operation, and continuous improvement of a secure, data, analytics, and AI platform for the DoD that operates across multiple security enclaves and multiple cloud service providers. This includes advanced security measures, such as encryption, security controls, zero-trust, and continuous monitoring, to safeguard

Advana Platform data and operations, while integrating commercial tools and agile software development methodologies. The contractor will scale the system to accommodate over 1,000,000 users and implement continuous integration and continuous delivery (CI/CD) practices to streamline development, testing, authorization, and deployment processes and to ensure rapid and reliable delivery of software updates. This task also includes the thorough documentation of all activities, architectures, designs, and development processes to facilitate collaboration, knowledge transfer, and adherence to industry standards and regulatory requirements.

The contractor shall conduct all Platform Infrastructure Management requirements for both the Advana v1.0 System and the Advana v1.2 System unless noted otherwise.

2.2.1 Advana System v1.0 Operations, Sustainment, Migration, and Shutdown.

The contractor shall operate and sustain the existing Advana System while the new

Advana System is stood up, then migrate existing Advana System Customers and workloads to the new Advana System, and when appropriate, shutdown the current

Advana System.

The contractor shall conduct Advana System Sustainment, Migration, and Shutdown for the Advana v1.0 System only.

2.2.1.1. Operate and sustain the current Advana v1.0 System across all Advana

CSP/Security Environments.

2.2.1.2. Maintain the current Advana v1.0 System Authority to Operate (ATO).

2. 2.1.3. Manage and control the accounts, passwords, software licenses, software certificates, and other items that are needed to operate the Advana v1.0 System.

2. 2.1.4. Prepare and submit for Government approval, an Advana System Migration Plan that covers all necessary activities needed to ensure a smooth user migration from the current Advana v1.0 System to the new Advana v1.2 System. The Advana System

Migration Plan shall include the following:

o Software Migration Plan o Data Migration Plan o Process Migration Plan o Service Desk Migration Plan o Migration Communication Plan (to Advana Customers and Users) o User Account Migration Plan o User Workload Migration Plan

2.2.1.5. Migrate Advana users and Advana user workloads from the existing Advana v1.0

System to the new Advana v1.2 System.

2. 2.1.6. Ensure existing Advana v1.0 System users experience an uninterrupted transition to the new Advana Platforms.

2.2.1.7. Ensure existing Advana v1.0 System users experience an uninterrupted transition to the new Advana Platforms.

2.2.1.8. When the Advana System migration is fully completed, perform a safe shutdown of the existing Advana v1.0 System and archive, in accordance with DoD records management policies, all appropriate Advana v1.0 System records and logs including:

o Source code.

o Containers o Virtual Machine Images o Software libraries o Software licenses.

o Software certificates.

o Documentation.

o System and security logs.

o User identification and profile information.

o User workloads.

2.2.1.9. Conduct the Advana v1.0 System to Advana v1.2 System migration in accordance with the following milestones:

o MAR 2025: Advana System Migration Plan complete.

o JUL 2025: Advana v1.2 System operational for customer use.

o AUG 2025: Advana v1.0 customer migration begins.

o NOV 2025: Advana v1.0 customer migration complete.

o DEC 2025: Advana v1.0 shutdown begins.

o FEB 2026: Advana v1.0 shutdown complete

2.2.2 Enterprise Engineering.

The contractor shall conduct enterprise engineering lifecycle management for the Advana

System including requirements gathering, systems architecture and engineering, process engineering, system design and development, installation, integration, testing, and sustainment.

2.2.2.1. Architect and engineer large scale enterprise cloud systems, producing clear, comprehensive, and effective enterprise architecture and engineering documentation in accordance with DoD Architecture Framework (DoDAF) standards.

2.2.2.2. Design secure and resilient technology architectures that meet cloud and container infrastructure requirements of the organization.

2.2.2.3. Design, maintain, and document enterprise architecture artifacts for the Advana

Ecosystem including reference architectures, solution architectures, system architectures, network architectures, security architectures, data architectures, and process architectures using DoDAF standards.

2.2.2.4. Design, prepare, and document systems engineering products for the Advana

System including DoD high-high-moderate level system designs, system interface and

Application Programming Interfaces (API), system development plans and roadmaps, system cost estimates, system risk assessments, and system change requests.

2.2.2.5. Design, prepare, and document cybersecurity engineering products for the

Advana System including cyber security control designs, cyber security zero trust capabilities and activities, cyber security boundaries, cyber security control procedures, cyber security compliance products, cyber security plans and roadmaps, and cybersecurity change requests.

2.2.2.6. Design, prepare, and document process engineering products for the Advana

System including process design specifications, process implementation plans, process development roadmaps and schedules, and process change requests.

2.2.2.7. Design, prepare, and document personnel-related engineering products for the

Advana System including Advana system roles and personas, role/persona responsibilities, role/persona security requirements, role/persona training requirements, role/persona certification requirements, and role/persona change requests.

2.2.2.8. Define, maintain, and communicate Advana Platform service APIs.

2.2.2.9. Engage with other DoD programs and initiatives to shape and evolve Advana enterprise architecture and engineering designs to interoperate and interconnect with other major DoD data, analytic, and AI platforms and systems.

2.2.3 Commercial Tool Identify, Preparation, and Integration.

The contractor shall identify, prepare, secure, and integrate commercial and open-source tools and services into the Advana System.

The contractor shall conduct Commercial Tool Identify, Preparation, and Integration for the Advana v1.2 System only.

2.2.3.1. Conduct market research and conduct analysis-of-alternatives for new tools and publish findings and recommendations for their inclusion in the Advana System.

2.2.3.2. Perform ongoing security and performance monitoring of commercial and open-source tools and applications included in the Advana Platforms to ensure they meet certification by Advana Platforms standards.

2.2.3.3. Identify, select, prepare, and integrate commercial and open-source tools into the

Advana System. These commercial and open-source tools include but are not limited to:

o Data engineering, data management, data sharing, data cataloging, data tagging, and data labeling tools.

o Analytic and dashboarding tools.

o Artificial intelligence and machine learning tools.

o Robotic Process Automation (RPA) tools that support decision and decision support tools.

2.2.4 Agile Software Development.

The contractor shall establish and exercise agile methodologies for software development of the Advana System.

2.2.4.1. Conduct cloud PaaS and SaaS development, as well as building and maintaining

Infrastructure-as-Code (IaC) and Configuration-as-Code (CaC) using agile development methods.

2.2.4.2. Translate Advana enterprise engineering and reference architecture designs into

Advana software designs, considering business requirements, target environments, processes, performance requirements, cybersecurity requirements, and compliance requirements.

2.2.4.3. Design, build, and document IaC that will be used to prepare all CSP environments to receive an Advana System deployment.

2.2.4.4. Design, build, and document CaC that will be used to deploy all Advana System components into CSP environments and then configure and interconnect the deployed

Advana System software components.

2.2.4.5. Harden and secure Advana virtual machines (VM) in accordance with applicable

DoD Security Technical Implementation Guides (STIGs).

2.2.4.6. Harden and package Advana containers in accordance with applicable DoD container hardening standards.

2.2.4.7. Integrate Government identified Content Management Systems (CMS) with relevant Advana System components.

2.2.4.8. Manage the software development lifecycle for web applications that are integrated into the Advana Platform.

2.2.5 Continuous Integration/Continuous Delivery.

The contractor shall Establish and operate a modern Continuous Integration/Continuous

Delivery (CI/CD) process for systematic, repeatable, secure, and streamlined delivery of capabilities into the full range of Advana Operating Environments.

The contractor shall conduct Commercial Tool Identify, Preparation, and Integration for the Advana v1.2 System only.

2.2.5.1. Design, implement, operate, and maintain a Continuous Integration/Continuous

Delivery (CI/CD) / DevSecOps process for the Advana System.

2.2.5.2. Design, develop, operate, and maintain the CI/CD DevSecOps software components and tools for conducting all aspects of Advana System software development, integration, testing, and provisioning into sandbox, development, test, integration, staging and production environments.

2.2.5.3. Design, build and maintain automated Advana CI/CD pipelines for the following:

o Provisioning: including deployment, configuration, and integration of Advana

System components.

o Testing.

o Promotion of the Advana Platform through DEV/TEST/INT/STAGE/PROD stages.

o DoD security compliance testing of VMs.

o DoD security compliance testing of containers.

2.2.5.4. Provide an Advana System baseline that deploys and operates on all supported cloud environments and all supported enclaves.

2.2.5.5. Develop a set of test scores that lead toward, when accepted thresholds are met or exceeded automated promotion decisions between each lifecycle stage.

2.2.5.6. Ensure that Advana CI/CD pipelines are scoped and built to operate across all

Advana CSP/Security Environments.

2.2.5.7. Design, manage, maintain, and conduct CI/CD processes for all Advana

Platforms software development, testing, integration, staging, and provisioning

2.2.5.8. Manage Advana Platform software baselines and software releases.

2.2.6 Operations and Maintenance.

The contractor shall Perform Operations and Maintenance (O&M), troubleshooting, and repair of the Advana System and existing connections to source systems across all cloud and security environments including routine and corrective maintenance, preventative maintenance, incident management, cybersecurity event management and spillage, and event management.

2.2.6.1. Prepare, implement, and maintain an Advana System Operations Plan and

Incident Management Plan and conduct the full Operations and Maintenance (O&M) lifecycle for the Advana System.

2.2.6.2. Employ processes that disallow administrator changes to downstream Advana

System staging environments such as Test, Integration, Staging and Production.

2.2.6.3. Ensure that Advana System baseline configurations are continuously monitored and reverted to the baseline state if changed in downstream environments.

2.2.6.4. Perform system administration and maintenance activities on the Advana System as required to keep the system operational.

2.2.6.5. Manage and maintain Advana System cloud environments via CSP provided cloud service management consoles.

2.2.6.6. Continuously monitor the Advana System for Virtual Machine or Container failures and restart and restore the Advana system to normal operations when necessary, using fully automated means. (Advana v1.2 System only)

2.2.6.7. Collect, analyze, and report ingoing system operations and maintenance issues so that they may be corrected in future software releases.

2.2.6.8. Install and configure Government-specified automated tools to track network configuration; monitor status and performance; detect, diagnose, and resolve network problems; and project future capacity requirements. (Applies to the Advana v1.2 System only)

2.2.6.9. Prepare, implement, and maintain an Advana System Backup and Recovery Plan and provide failure recovery support for the Advana Platform to ensure the ability to restore Advana Platform service within:

o 48 hours of a major system failure – for Advana v1.0 o 4 hours of a major system failure – for Advana v1.2.

2.2.6.10. Conduct and maintain Advana System backup across all Advana operating environments as follows:

o Full system backup once per week.

o Incremental system back up daily.

2.2.6.11. Verify and test the ability to restore the Advana System from a backup at least once per month:

2.2.6.12. Notify Advana users of system outages and establish/maintain a business process to ensure any system outages, scheduled or not, are known and conveyed to users via the Advana homepage and email with 20 minutes of notice.

2.2.7 Tier 2/3 Service Desk Support.

The contractor shall Provide Tier 2 and Tier 3 customer support (5 days/8 hrs/day operations) for the Advana System in response to escalated issues from the Tier 0 and 1 level.

Note: Tier 0 and Tier 1 customer support is addressed in Section 2.5.

2.2.7.1. Prepare, implement, and maintain an Advana Tier 2/3 Service Support Plan and provide full spectrum Tier 2 and Tier 3 customer support (24/7 operations) for the

Advana Platforms in response to escalated issues from Tier 0 and 1 level in accordance with agreed upon SLAs and metrics.

2.2.7.2. Provide administrator, system, and end-user support on a tool-by-tool and application-by-application basis for products in current production and those preparing to go to public beta and general release.

2.2.7.3. Manage and maintain an up-to-date knowledge base for Tier 2 and Tier 3 operations and queue manager support.

2.2.7.4. Provide Tier 2 support that meets the following Service Level Agreements

(SLAs) for the Advana SIPRNet environment:

o Provide user access in 3 business days.

o Resolve user problems in 3 business days.

2.2.8 Testing and Independent Verification and Validation.

The contractor shall provide enterprise test environments that are representative of all

Advana CSP/Security Environments to facilitate Government-specific test, evaluation, validation, training, and authorization requirements and that are fully integrated with

Advana CI/CD processes.

2.2.8.1. Plan, implement, and maintain and an Advana Test and IV&V Plan based on

CI/CD, DevSecOps principles and conduct automated testing of the Advana System for all software provisioning, testing, and promotion.

2.2.8.2. Design, build, package, and validate test procedures for testing the Advana

Platform that can be incorporated into the appropriate CI/CD test pipelines.

2.2.8.3. Provide automated test scripts for the Advana Platform that address the following types of testing including:

o Unit.

o Functional.

o Regression.

o Security—both static and dynamic.

o Integration.

o Performance.

o Compliance.

o Acceptance.

2.2.8.4. Design, build, operate, and maintain an Independent Verification and Validation

(IV&V) testing process that conducts independent evaluation of the Advana System to ensure it is functioning as intended.

2.2.9 Cybersecurity Risk Management and Operations.

The contractor shall Implement and maintain all aspects of Advana System cybersecurity engineering, authorization, and defense in accordance with all Federal, DoD, and agency-specific security policies and requirements and across all Advana System CSP/Security

Environments. The contractor shall employ and follow the DoD Risk Management

Framework (RMF) process and implement zero trust capabilities in accordance with the

DoD Zero Trust Reference Architecture across the entire Advana System Lifecycle.

2.2.9.1. Provide personnel that are qualified to perform the functions of DoD Information

System Security Managers (ISSMs) and that have all DoD mandated qualifications and certifications for performing ISMM functions.

2.2.9.2. Develop, prepare, and maintain cybersecurity architecture, engineering artifacts across all Advana CSP/Security Environments.

2.2.9.3. Identify, define, design, implement, test, authorize, and maintain appropriate

NIST security controls for the Advana System for all Advana CSP/Security

Environments.

2.2.9.4. Design, develop, maintain, and continuously improve Zero Trust security controls for the Advana System across all Advana CSP/Security Environments.

(Advana v1.2 System only)

2.2.9.5. Develop, test, deploy, and sustain processes and tools required to perform cybersecurity engineering to secure the Advana System, its components, tools, and applications across all Advana CSP/Security Environments.

2.2.9.6. Develop and integrate automated cybersecurity test procedures into Advana

CI/CD DevSecOps testing pipelines.

2.2.9.7. Generate cybersecurity test results that are required to support the DoD RMF cybersecurity authorization process for fielding the Advana System into DoD production environments across all Advana CSP/Security Environments.

2.2.9.8. Generate and prepare Advana System IATT, ATO, and Change request (CR) engineering artifacts and documents and provide all necessary support to obtain and maintain Authority to Operate (ATOs) for Advana System using the DoD Risk

Management Process (RMF).

2.2.9.9 Prepare, implement, and maintain an Advana Cybersecurity Continuous

Monitoring Plan and conduct cybersecurity continuous monitoring and defense operations for the Advana System in accordance with all DoD and Government cybersecurity regulations, across all Advana CSP/Security Environments.

2.2.9.10. Prepare, implement, and maintain an Advana Security Incident Management

Plan and conduct Security Incident Management operations in accordance with all DoD and Government cybersecurity regulations, across all Advana CSP/Security

2.2.9.11. Prepare and maintain an Advana System Penetration Test Plan and conduct penetration testing on the Advana System across all Advana CSP/Security Environments.

2.2.10 Change and Configuration Management.

The contractor shall Design, build, operate, maintain, and continuously improve Change

Management processes to ensure all changes are assessed, approved, implemented, reviewed, and approved via the Advana CCB process.

2.2.10.1. Design, build, and operate a comprehensive Change and Configuration

Management plan and process that manages all aspects of change and configuration management for the Advana System.

2.2.10.2. Design, build, and conduct configuration management of Advana System

Configuration Items.

2.2.11 Continuous Technology Improvement.

The contractor shall Continually improve the capabilities of the Advana System by conducting ongoing search and evaluation of new commercial data, analytic, and AI technology and by conducting rapid and efficient insertion and refreshment of technology into the Advana System baseline.

The contractor shall conduct Continuous Technology Improvement for the Advana v1.2

System only.

2.2.11.1. Identify, evaluate, select, and integrate new commercial and open-source technologies into the Advana System at the Government’s direction.

2.2.11.2. Build and foster relationships with industry and academia in the areas of data, analytic, and AI technologies and new products to capture new inspiration, ideas, and partnerships that address long- and short-term mission critical needs.

2.2.11.3. Analyze and review the latest advances in commercial/open-source data, analytic, and AI technologies to identify attractive candidates for insertion into the

2.2.11.4. Analyze and review the latest advances in Government-off-the-Shelf (GOTS) data, analytic, and AI technologies to identify attractive candidates for insertion into the

2.2.11.5. Develop, operate, and maintain an Advana Continuous Technology

Improvement Plan and process for assessing the suitability of attractive commercial, open-source, and GOTS technologies and products for incorporation into the Advana

System, where suitability includes:

o The maturity of the technology.

o The degree to which the technology meets DoD security requirements.

o The estimated time required to incorporate the technology.

o The estimated cost to incorporate the technology.

o The potential of the technology to benefit DoD missions.

o The risks associated with incorporating the technology.

o The willingness of the technology provider to assume responsibility for preparing the technology to integrate into Advana.

o The degree of compatibility with the Advana System architecture and processes.

2.2.11.6. Prepare plans and schedules for incorporating new commercial, open-source, and GOTS technologies into the Advana software development schedule.

2.2.11.7. Assist Advana Platforms developers and CI/CD engineers in preparing and integrating new technology into the Advana System Baseline.

2.2.11.8. Assess recurring technology integration roadblocks associated with the Advana

System and recommend architecture and design changes to the Advana System that will speed up the incorporation of new technologies.

2.2.12 Policy-Based Platform Governance.

The contractor shall Design, implement, and maintain policy-based governance mechanisms for managing the access and use of Advana System resources including cloud capacity, tools and services, pipelines, data, analytics, AI models, and decision apps.

The contractor shall conduct Policy-Based Platform Governance for the Advana v1.2

2.2.12.1. Design, build, operate, and maintain policy-based governance mechanisms as part of the Advana System that can interface with DoD enterprise Identity, Credential, and Access Management (ICAM) services to access user attributes and credentials that will be used to make policy-based resource access decisions.

2.2.12.2. Provide policy-based governance mechanisms for managing user access to

Advana System resources for the following:

o Advana Enterprise Data.

o Advana Tools and Services o Advana Platform Apps o Advana Mission Spaces.

o Advana Sandboxes o Advana Cloud Resources o Customer Data o Customer Analytics and Dashboards o Customer AI Models o Customer Analytic and AI Enabled Apps

2.2.12.3. Provide a policy editing tool for Government decision makers to create, edit, and manage the Governance policies for the Advana System at runtime.

2.2.13. Advana Cost Tracking and Reporting.

The contractors shall design, implement, and operate mechanisms to collect, track, and report on the resource utilization and financial expenditures associated with individual

Advana customer activities and operations in in the Advana System.

The contractor shall conduct Advana Cost Tracking and Reporting for the Advana v1.2

The contractor shall

2.2.13.1. Design, implement, operate, and maintain an Advana Cost Tracking and

Reporting solution for the Advana System.

2.2.13.2. Assist the Government in analyzing and understanding Advana customer resource utilization and expenditures.

2.2.13.3. Provide projections to Advana customers about the costs of Advana Platform services.

2.2.13.4. Inform Advana customers of their actual resource utilization and financial expenditures on the Advana Platform.

2.2.13.5. Generate billing information to charge Advana customers for their resource utilization and financial expenditures in the Advana Platform.

2.2.13.6. Provide resource utilization and financial expenditure information to Advana

Platform developers and system engineers to make intelligent decisions about Advana

Platform changes and improvements.

2.2.13.7. Provide resource utilization and financial expenditure information to Advana

Service Portfolio managers to help inform their decisions about future Advana service offerings and service packages.

2.2.14. Deliverables.

PWS

Para#

Deliverable

Format

Due

Date

Distribution/

Copies

Frequency

D2-1 Advana System

Migration Plan

2.2.1.4 MS Word

document using

CDAO template

CA+30

days

*Standard Once

D2-2 Advana System

Architecture

2.2.2.3 Contractor – MS

Word

CA+90

days

Quarterly

PWS

Para#

Deliverable

Format

Due

Date

Distribution/

Copies

Frequency

D2-3 Commercial Tool

Analysis of

Alternatives

2.2.3.1 Contractor – MS

Word

CA+60

days

*Standard Updated

Monthly

D2-4 Commercial Tool

Market Research

2.2.3.1 Contractor – MS

Word

CA+60

days

*Standard Updated

Monthly

D2-5 Advana System

IaC

2.2.4.3 Software CA+90

days

*Standard Updated

Quarterly

D2-6 Advana System

IaC

2.2.4.4 Software CA+90

days

*Standard Updated

Quarterly

D2-7 Advana System

Virtual Machines

2.2.4.5 Software CA+90

days

*Standard Updated

Quarterly

D2-8 Advana System

Containers

2.2.4.6 Software CA+90

days

*Standard Updated

Quarterly

D2-9 Advana Content

Mgt System

2.2.4.7 Software CA+90

days

*Standard Updated

Quarterly

D2-10 Advana CI/CD

DevSecOps

Process

2.2.5.1 Contractor – MS

Word

CA+30

days

*Standard Updated

Monthly

D2-10 Advana CI/CD

DevSecOps

Software

2.2.5.2 Software CA+30

days

*Standard Updated

Monthly

D2-11 Advana CI/CD

DevSecOps

Pipelines

2.2.5.3 Software CA+30

days

*Standard Updated

Monthly

D2-12 Advana Software

Baseline

2.2.5.4 Software CA+30

days

*Standard Updated

Monthly

D2-13 Advana System

Operations Plan

2.2.6.1 Contractor – MS

Word

CA+90

days

*Standard Updated

Quarterly

D2-14 Advana System

Incident

Management Plan

2.2.6.1 Contractor – MS

Word

CA+30

days

*Standard Updated

Quarterly

D2-15 Advana Tier 2/3

Service Support

Plan

2.2.7.1 Contractor – MS

Excel

CA+30

days

*Standard Updated

Quarterly

D2-16 Advana Test and

IV&V Plan

2.2.8.1 Contractor – MS

Word

CA+30

days

*Standard Updated

Quarterly

D2-17 Advana Test

Procedures

2.2.8.2 Contractor – MS

Word

CA+60

days

*Standard Updated

Monthly

D2-18 Advana Test

Scripts

2.2.8.3 Software CA+60

days

*Standard Updated

Monthly

D2-19 2.2.9 Contractor – MS

Word

CA+90

days

*Standard Updated

Quarterly

D2-20 Cybersecurity

Architecture

Artifacts

2.2.9.2 Contractor – MS

Word

CA+30

days

*Standard As needed

D2-21 Cybersecurity Test

Procedures

2.2.9.6 Contractor – MS

Word

CA+30

days

*Standard Updated

Quarterly

D2-22 Advana

Cybersecurity Test

Results

2.2.9.7 Digital CA+60

days

PWS

Para#

Deliverable

Format

Due

Date

Distribution/

Copies

Frequency

D2-23 IATT, ATO, CR

Artifacts and

Documents

2.2.9.8 Contractor – MS

Word

CA+60

days

*Standard Updated

Quarterly

D2-24 Advana

Cybersecurity

Continuous

Monitoring Plan

2.2.9.9 Contractor – MS

Word

CA+30

days

*Standard Updated

Quarterly

D2-25 Advana Security

Incident

Management Plan

2.2.9.10 Contractor – MS

Word

CA+30

days

*Standard Updated

Quarterly

D2-26 Advana

Penetration Test

Plan

2.2.9.11 Contractor – MS

Word

CA+90

days

*Standard Updated

Quarterly

D2-27 Change

Management Plan

2.2.10.1 Contractor – MS

Word

CA+90

days

*Standard Updated

Quarterly

D2-28 Configuration

Control Items

2.2.10.2 Contractor – MS

Word

CA+90

days

*Standard Updated

Quarterly

D2-29 Configuration

Management Plan

2.2.10 Contractor – MS

Word

CA+30

days

*Standard Updated

Monthly

D2-30 Continuous

Technology

Improvement Plan

2.2.11.5 Contractor – MS

Word

CA+60

days

*Standard Updated

Quarterly

D2-31 ICAM Solution

Design

2.2.12.1 Contractor – MS

Word

CA+60

days

*Standard Updated

Quarterly

D2-32 ICAM Solution

Software

2.2.12.1 Software CA+120

days

*Standard Updated

Quarterly

D2-33 Advana Cost

Tracking and

Reporting Design

2.2.13.1 Contractor – MS

Word

CA+90

days

*Standard Updated

Quarterly

D2-34 Advana Cost

Tracking and

Reporting Solution

2.2.13.1 Software CA+150

days

*Standard Updated

2.3 Data and AI Infrastructure Management

This task is for the development and delivery of standardized enterprise data, analytics, and AI products and services throughout the DoD. This comprehensive framework of standardized data, analytic, and AI products and services will lay the groundwork for the

DoD to leverage advanced technologies for data-driven decision making and insights, continuous innovation.

The contractor shall conduct Data Operations for both the Advana v1.0 System and the

Advana v1.2 System.

2.3.1 Data Operations.

The contractor shall plan for and conduct enterprise data operations for the Advana

System across all Advana CSP/Security Environments.

2.3.1.1. Deliver automated data movement capabilities, alerting, and data drift detection throughout the data lifecycle and across the Advana Operating Environment.

2.3.1.2. Manage enterprise, automated cross domain capabilities and solutions required to federate data from the Advana system and other CDAO environments to data environments leveraged by Military Services, Combatant Commands, DoD agencies, and

Federal Agencies.

2.3.1.3. Manage automated solutions to ingress and egress data from the Advana platform and other CDAO data platforms using enterprise application program interfaces (API).

2.3.2 Data and AI Model Connections.

The contractor shall design, build, operate, and maintain data and AI model connections for the Advana System across all Advana CSP/Security Environments.

2.3.2.1. Support the establishment of automated data connections across the Advana

Operating Environment for Government directed use cases.

2.3.2.2. Maintain existing standard data connection methods, both inbound and outbound, across the Advana Operating Environment.

2.3.2.3. Develop and maintain a training and certification program for data connection engineers that grants access and enables data sharing across CDAO and DoD systems and enterprise platforms.

2.3.2.4. Evolve, support, and in accordance with Government direction, enforce processes and standards for data acquisition and data sharing to and from the Advana platform, in accordance with existing and new data and AI Model playbooks, including but not limited to o Facilitating technical exchange meetings o Competing data sharing agreements o Developing the data connections o Supporting data pipeline development o Monitoring existing data connections to proactively address any issues that may arise over time.

2.3.2.5. Develop, test, and deploy new connection methods including streaming and multi-cloud – based on CDAO use case needs to further enable the sharing of data and

AI/ML models between the Advana System and other DoD systems across all Adv ana

2.3.2.6. Mature Advana's enterprise data and AI API program operations and capabilities across all Advana CSP/Security Environments to facilitate its adoption as the DoD’s primary method for sharing and leveraging data and AI/ML models.

2.3.3 AI/ML Operations and Services.

The contractor shall design, plan, and provide AI/ML operations and services to support

Advana customer AI/ML activities in the Advana System across all Advana

2.3.3.1. Enable the integration and sharing of AI/ML across Advana supported DoD domains that include the following:

o Acquisition Lifecycle and Management and Procurement o Digital and Information Technology o Energy, Installations, and Environment o Executive Decision Support o Innovation o Intelligence and Security o Logistics o People and Health o Policy o Readiness and Global Force Management

2.3.3.2. Provide an integrated and federated AI/ML development and deployment capability to support the complex set of activities necessary to build AI systems.

2.3.3.3. Enable the efficient labeling of DoD Component data across multiple modalities

(e.g., text, imagery, video, audio, and tabular data) to turn raw gathered data into curated datasets capable of supporting AI/ML development.

2.3.4.4. Provide a centralized repository for mission-engineered features used within AI development that will allow for the broadscale sharing and reuse of features while supporting future automated feature engineering efforts.

2.3.3.5. Provide centralized versions of state-of-the-art foundational models across canonical common tasks, and specialized models in domain areas of demonstrated need

(e.g., DoD lexicon-specific Natural Language Processing (NLP) models or DoD logistics models).

2.3.3.6. Provide a federated catalog with associated APIs and integration toolsets that lists metadata and access information for DoD datasets and AI models, supporting reuse and sharing for future development.

2.3.3.7. Establish, test, and deliver AI/ML deployment pipeline(s) that serve as the foundational component of all future AI/ML models deployed, cataloged, and integrated within DoD enterprise platforms.

2.3.3.8. Support the constant iteration required to ensure the AI/ML deployment pipeline(s) align with industry and DoD best practices.

2.3.3.9. In accordance with Government direction, test new data and AI/ML automation concepts to support customer requirements.

2.3.4 AI/ML Capability Development.

The contractor shall identify, design, build, test, and provide AI/ML capabilities to support Advana customers in the Advana System across all Advana CSP/Security

2.3.4.1. Deliver foundational-enterprise data products and AI/ML workflows to any internal or external customers planning to leverage the Advana enterprise platform.

2.3.4.2. Provide ready-to-use, generalizable, and pre-trained AI models for use by all

DoD Domains.

2.3.4.3. Implement state-of-the-art…