Attachment 0001 PWS - APT EA AND AWG SUSTAINMENT.pdf

ANALYTIC PRODUCT TEAM (APT), SUPPORT TO THE ANALYSIS WORKING GROUP

(AWG), AND ENTERPRISE ANALYTICS (EA) SUSTAINMENT

PERFORMANCE WORK STATEMENT (PWS)

FOR

CHIEF DIGITAL AND ARTIFICIAL INTELLIGENCE OFFICE (CDAO)

18 November 2024

Table of Contents

1. Introduction

2. Background

3. Scope

3.1. APT/EA

3.2. AWG Support Team

4. Contract Management

4.1. Period of Performance

4.2. Location of Performance

4.3. Security

4.4. USG Networks and Communications Infrastructure

4.5. Government Furnished Property and Equipment (GFP/GFE)

4.6. Additional Information

5. Anti-Terrorism/Operational Security

1. Introduction

1.1. To scale data, analytics, and AI for the Department of Defense (DoD), the Mission Analytics Directorate at the Chief Digital and Artificial Intelligence (AI) Office (CDAO) is establishing embedded teams to provide data scientists, full stack developers, software engineers, product management support (e.g., monitors product general availability process, develops marketing material and training content), customer success functions (e.g., customer analytics, UI/UX, product design & solutioning), and other product services support to enable the adoption of data driven decision making across the DoD. These teams will provide support to three groups as outlined below:

1.1.1 The Analytic Product Teams (APTs) support CDAO’s goal of accelerating maturation of Principal Staff Assistants (PSAs) use of data and AI through analytics support, technical/organizational/workforce development advisory services, creation of data products, platform onboarding, and process modernization.

1.1.2 The Enterprise Analytics (EA) Sustainment team is a cross cutting effort that spans across the Office of the Secretary of Defense (OSD), Joint Staff (JS), service branches, and defense agencies.

1.1.3 Cost Assessment and Program Evaluation (CAPE) is a PSA that coordinates studies through the Analytic Working Group (AWG) to inform recommendations to the DoD planning, programming, budgeting, and execution. CAPE enables these studies by providing access to enterprise data, such as the Ukraine War Database (UWD) that is an ongoing enduring effort.

Currently, the CDAO provides data science and engineering support to the AWG that includes the UWD.

1.2. For the purposes of centralized management, the term CDAO Central will be used. The term organization will be used to indicate generically the organization that is to receive the support as outlined.

2. Background

2.1. The level of maturity for data and AI adoption varies across each PSA and the support that the APTs deliver to the PSAs will vary based on the PSA respective data and AI transformation plan. In 2025, the PSAs must be at a baseline level of data and AI capability to set the conditions for advanced analytics in 2026. Achieving this baseline capability requires identifying and delivering new solutions.

2.2. EA Sustainment is primarily responsible for the maintenance and sustainment of previously developed data pipelines and analytic products as well as potentially identifying and delivering new solutions.

2.3. The UWD contains a wide range of authoritative data sources pertaining to the Russia- Ukraine conflict. The UWD was commissioned in 2023 to support an OSD study effort. The UWD was envisioned to endure as enterprise resource beyond the initial study effort and, in 2024, was managed by the CDAO. In 2025, CDAO seeks to further develop the UWD and tools for interacting with the UWD.

3. Scope. The nature of work for APTs, EA Sustainment, and Support to AWG are similar. The scope of tasks for Support to AWG is well-defined and primarily focused on supporting the UWD. Whereas requirements for the APTs and EA Sustainment will vary and are specific to the supported organization. Considering this, scope for APT and EA Sustainment are intended to describe required capabilities.

3.1. APT/EA Sustainment. The APTs shall provide support to 13 PSAs on NIPR/SIPR and one PSA on NIPR/SIPR/JWICS. EA Sustainment shall provide support on NIPR/SIPR/JWICS.

The following applies to both APTs and EA Sustainment:

3.1.1 Program Management

3.1.1.1. Development of Monthly Status Reports (MSRs) and Quarterly Report Summaries (QSRs).

3.1.1.2. Development of a Project Schedule.

3.1.1.3. Development of a Staffing Plan and associated labor accounting controls.

3.1.1.4. Maintain, assist in prioritization of the global organization development project backlog.

3.1.1.5. Advise on global deployment of resources.

3.1.1.6. Coordinate and facilitate organization MS Team functions with Washington Headquarter Services (WHS).

3.1.1.7. Coordinate and maintain internal collaboration tools, version control / change management, productivity tools, MS Teams, and email distribution groups.

3.1.1.8. Coordinate travel, general scheduling, assist in security support for organization teams and WHS visits, and host visitors.

3.1.1.9. Communicate projects status, blockers, and ground truth to CDAO Central.

3.1.1.10. Generate roadmaps and assist with the prioritization of current initiatives in order to balance business goals with Customer Impact.

3.1.1.11. Conduct Digital Transformation Assessments using the Framework as defined by CDAO.

3.1.2 Provide Program Integration, Training, and End User Support

3.1.2.1. Utilize and promote use of CDAO Central HQ knowledge management solutions and requirements generation/prioritization.

3.1.2.2. Provide technical and executive level reporting to CDAO Central that communicate impact and reach of local efforts.

3.1.2.3. Document and understand organization data science & Artificial Intelligence training programs.

3.1.2.4. Identify Digital Services training gaps and offer trainings to fill those respective gaps.

3.1.2.5. Standardize processes for training on tools developed.

3.1.2.6. Understand organization integration opportunities, scope requirements, and assess alternatives.

3.1.2.7. Leverage quantitative and qualitative data to influence design decisions.

3.1.2.8. Provide ongoing tailored and on demand training to organization personnel on the technology stacks employed.

3.1.2.9. Establish engineering best practices and ensure compliance across the entire portfolio for consistency in practice. This includes and not limited to documentation lint standards, utilization of source code repositories, unit testing, CI/CD pipelines, code peer review, etc.

3.1.2.10. Enable development with API technologies including the installation, configuration, operations, and troubleshooting of API products.

3.1.2.11. Provide customer success services and CRM support.

3.1.3 Data Labeling and Pipeline Management

3.1.3.1. Collaborate with individual organization and CDAO Central to gather documentation on local hosting and data architecture relative to AI requirements in a machine and human readable format.

3.1.3.2. Document failover/continuity of operations (COOP) plans for data systems.

3.1.3.3. Identify any existing local development environments and provide engineering best practices to enhance existing systems.

3.1.3.4. Catalog, label, and ingest structured and unstructured data into appropriate DoD data catalogs based on mission/function and identify data that is part of any systems of record as directed by organization and CDAO Central.

3.1.3.5. Establish engineering best practices and ensure compliance across the entire portfolio for consistency in practice. This includes and not limited to documentation lint standards, utilization of source code repositories, unit testing, CI/CD pipelines, code peer review, etc.

3.1.3.6. Employ DevSecOps when developing, testing, and maintaining data pipelines.

3.1.3.7. Enable development with API technologies including the installation, configuration, platform operations, and troubleshooting of API products.

3.1.4 AI Engineering and Integration Support

3.1.4.1. Leverage and maintain awareness of work across organizations to communicate the vision for the products.

3.1.4.2. Align and prioritize initiatives with the product roadmap in accordance with the organizations needs and overall operational goals.

3.1.4.3. Conduct research to identify policies, directorates, stakeholders to design resources to develop feasible, viable and desirable solution through collaboration with engineering teams.

3.1.4.4. Adhere to a CDAO Central provided standard technical approach and provide transparency of development progress and methods for passive quality review and reuse of solutions.

3.1.4.5. Identify data solutions in accordance with agreed organization standards that ensure services are resilient, scalable, and future proof.

3.1.4.6. Assist CDAO Developers, Data Stewards, Software Architects and Product Managers to produce DoD AI Technology roadmaps.

3.1.4.7. Document and maintain applicable organization Software Architecture maps and technology roadmaps.

3.1.4.8. Improve digital services through rapid prototype and develop solutions on existing infrastructure in a response to emergent requirements.

3.1.4.9. Translate initial organization integration opportunities into fully scoped and actionable use cases.

3.1.4.10. Facilitate access to infrastructure for operational development by organization digital experts.

3.1.4.11. Identify, document, and share organization -specific processes (command and control or technical) required to accomplish CDAO Central development objectives.

3.1.4.12. Document existing data ontologies and data types in use at organizations encountered in development tasking and indicate availability for reuse.

3.1.4.13. Identify organization requirements and work with organization and CDAO Central to propose solutions to connect requirements to existing solution providers.

3.1.4.14. Facilitate the “conception though completion” of large-scale digital products, in conjunction with Product teams that can be composed of Engineering, Web Applications, and UX Design.

3.1.4.15. Enable development with API technologies including the installation, configuration, platform operations, and troubleshooting of API products.

3.1.4.16. Develop enterprise applications with modern JavaScript frameworks if needed such as React, Angular, and Vue.

3.1.4.17. Build modern, responsive, and cross-browser-compatible websites if needed using HTML, CSS, and JavaScript.

3.1.4.18. Design, develop, and maintain enterprise analytic products using business intelligence software applications, such as Qlik, Tableau, etc.

3.1.5 Acceleration of Emerging AI Technologies Research and Integration

3.1.5.1. Perform continuous discovery and recommend projects for backlog prioritization.

3.1.5.2. Recommend community tools to support DoD and organization AI Development including Wikis, Software Engineering Tools such as Github, forums, and other means.

3.1.5.3. As blockers arise in product development, recommend process improvements to accelerate Data maturity Development.

3.1.5.4. Compile a list of available AI offerings to assemble a DoD AI offerings catalog.

3.1.5.5. Provide research, modeling, technical analysis, and technical writing support.

3.2. AWG Support Team. Maintaining and further developing the UWD. The UWD is a JWICS database that is stored within Advana Databricks. The contractor shall provide a team comprised of a product lead, data engineer, and data visualization developer UWD stakeholders to identify/add additional data sources to the UWD, deploy web applications that enable rapid data exploration of the UWD, and host technical exchange meetings to support the UWD user community. The UWD is primarily at the TS/SCI level so the data team must develop data analytic products on JWICS. Unless otherwise noted, the tasks defined in the following subsections must be achieved on JWICS using primarily the Advana platform. In addition to using Advana, the contractor must expertly incorporate JWICS enterprise tools to develop state-of-the-art analytic products.

3.2.1 Product Lead

3.2.1.1. The contractor shall provide product lead support under this PWS. This includes the management and oversight of all activities performed by contractor personnel, including subcontractors, to satisfy the requirements identified in this PWS. The contractor shall work and meeting regularly with the TPOC to document, execute, and review specific requirements. The contractor shall provide highly skilled support professionals to deliver dependable technical assistance directly to customers, effectively identify, diagnose, and resolve various technical issues, promptly eliminating any barriers to productivity, addressing customers' complex requirements, and offering tailored technical solutions to help advance their data mission.

3.2.1.2. The contractor shall have extensive domain knowledge about data sources and types related to military operations and contingencies. This includes knowledge about the types of data sources that are useful for analyzing and assessing military operations and tactics in a modern conflict. The contractor shall leverage this domain knowledge to ensure the UWD contains authoritative data that is most relevant for analyzing the Ukraine-Russia conflict.

3.2.2 Data Engineering Tasks

3.2.2.1. The contractor shall develop and automate data pipelines to data sources that are external to Advana on NIPR/SIPR/JWICS. This includes, but is not limited to, ingesting data from APIs, data stored in .csv format, and unstructured data, and then writing the data to delta tables in Advana’s Databricks. On JWICs, the vendor must be able to leverage SafeHouse, SafeBox, and the Databricks API to develop and maintain automated data pipelines for both structured and unstructured data. Vendor must develop and automate as many pipelines as required to ensure the UWD meets the needs of stakeholder.

3.2.2.2. The contractor shall develop and automate data pipelines to data sources that are internal to Advana on NIPR/SIPR/JWICS. The UWD leverages several data sources that are stored within the Advana platform (e.g., databases that are actively maintained by another DoD component). The vendor must be able to connect from the AWG support team’s Advana Databricks computing cluster to data sources and databases from other Advana user communities. Primarily, this consists of requesting and maintaining access from the AWG’s Databricks cluster to delta tables maintained by other teams. For a list of data sources available on NIPR Advana, see catalog.advana.data.mil on NIPR. Vendor must develop and automate as many pipelines as required to ensure the UWD meets the needs of stakeholder.

3.2.2.3. The contractor shall work closely with UWD stakeholders to identify and prioritize data sources relevant to the DoD enterprise and potential UWD users. This includes engaging with data sources owners from across the DoD and interagency to gather information on potentially useful data sources.

3.2.2.4. The contractor shall maintain data pipelines and associated documentation in accordance with Advana standards and best practices. This includes properly documenting metadata on data sources with Advana’s Collibra Data Catalog and following the Advana Data Operations Playbook.

3.2.3 Data Visualization Tasks

3.2.3.1. The contractor shall be responsible for developing data visualizations, primarily within the Advana Qlik environment, that enable the UWD stakeholders to quickly explore data sets within the UWD. The contractor shall be responsible for engaging with the TPOC to define requires for general purpose web applications.

3.2.3.2. The contractor shall be responsible ensuring web applications adhere to Advana standards. This includes proper documentation of data sources, features, and user guides for all applications. Additionally, the contractor will ensure applications in active are refreshed regularly with updated data and deprecated applications are properly archived.

3.2.3.3. The contractor shall provide user training for all web applications that are developed and deployed to the UWD stakeholder community.

3.2.4 Position Requirements. The contractor shall provide a team comprised of, at minimum:

3.2.4.1. One FTE, Product Lead

3.2.4.2. One FTE, Senior Data Engineer

3.2.4.3. One FTE, Data Visualization Developer

4. Contract Management. The Army Contracting Command Rock Island (ACC-RI) is the contracting agency for the USG. As the Contracting Activity for this agency, they have the authority, through a duly appointed Contracting Officer (KO), to enter, administer, and/or terminate this contract and make related determinations and findings. Responsibilities after award are in accordance with those defined in the contract and those applicable portions of the Federal Acquisition Regulation (FAR) and its supplements. ACC-RI is the only USG official who can provide direction to the contractor resulting in changes to the scope, schedule, and cost of this effort. Any changes required by the USG Inspector, or the Contracting Officer Representative (COR) must be approved in writing by the ACC-RI KO.

4.1. Period of Performance. The task order (TO) shall be a Firm Fixed Price (FFP) base of one year plus three option periods of three months in accordance with Federal Acquisition Regulation (FAR) 52.217-9, Option to Extend the Term of the Contract. The contract performance is the purchase of 26 sprint cycles across the base period of performance and 6.5 sprint cycles across the optional periods of performance. Each cycle is 2-weeks and are aligned to APT, EA Sustainment, and AWG respectively.

4.2. Place of Performance. APT, EA Sustainment, and AWG support team will perform work at the DC-area offices of the CDAO in Falls Church, Pentagon, or Arlington. Telework Eligibility will be determined by the COR on a case-by-case basis. The CDAO has multiple SCIFs that are available in Falls Church, Pentagon, or Arlington.

4.3. Security

4.3.1 All positions provided on this contract require a SECRET or TOP SECRET clearance. The USG’s security requirements are in accordance with the DD Form 254 attached to this contract action. Contractor personnel performing work under this contract must have the required clearance at the time of the proposal submissions and must maintain the level of security required for the life of the contract.

4.3.2 Positions requiring security clearance access are generally expected to be on-site to meet security requirements. Telework flexibility may be limited and subject to role-specific condition. For example, if a project does not require classified space access, then the team may have the option to telework, provided all compliance protocols are followed. All contractors and government personnel must adhere to CDAO telework regulatory guidance and standards as it may continue to change.

4.3.3 APT, EA Sustainment, and Support to AWG require SCIF, appropriate clearance (SECRET or TOP SECRET), and CAC. Sponsor organization is CDAO.

4.4. USG Networks and Communications Infrastructure. It is the USG’s intent to have contractor software development and integration efforts interface with required USG systems.

Unless approved by the USG, the Contractor is prohibited from the development of independent, parallel, or mirrored operating systems. If the Contractor is provided access to, or purchases services on a fee for service basis, on any USG networks or communications infrastructure, they will comply with DoD and local guidelines and requirements for review and approval prior to introducing commercial, USG developed, or contractor developed applications, software, or equipment into the environment.

4.5. Government Furnished Property and Equipment (GFP/GFE). GFP/GFE will be provided. Contractors shall have internal controls to manage (control, use, preserve, protect, repair, and maintain) USG property in its possession accountable to the award/order. The USG will also manage and monitor GFP.

4.6. Additional Information. The points of contact for the contractor will be the KO and COR. The KO/COR will provide project guidance or direction regarding the functional requirements for all software products generated and customized under this PWS. Functional guidance provided by the KO/COR will be coordinated with the end user organization to ensure that cost and schedule impacts are identified and addressed prior to being implemented by the Contractor.

5. Anti-Terrorism/Operational Security. Homeland Security Presidential Directive-12 (HSPD- 12). HSPD-12 establishes a mandatory, Government-wide standard for secure and reliable forms of identification issued by the Federal Government to its employees and Contractors (including Contractor personnel). Under this Directive, the heads of executive departments and agencies are required to implement programs to ensure that identifications issued by their departments and agencies to Federal employees and Contractors meet the Standard.

5.1. Individual Contractor personnel shall complete the Application for Identification Card/DEERs enrollment (DD Form 1172-2) CAC request and the System Authorization Access Request (SAAR) DD Form 2875 upon arrival. Submitters will provide updates for continued access for contract extensions, new awards, and contract / contractor termination.

5.2. The submitters will notify the security office and their contract leads of contract renewals. Subsequent access based on contract / contractor badge renewals will require official notification via email or formal memoranda from submitter to the security office. Documentation not properly completed will not be accepted. Submitters will forward their DD Form 1172-2 and DD Form 2875 to the security office via email. Submitters must also copy appropriate government leads.

5.3. The security office will validate the contractor’s security clearance. If a contractor employee has a correct background investigation and favorable adjudication, they will have their CAC application initiated within 24 hours of submission.

5.4. If the contractor does not have a valid background check or favorable adjudication eligibly by the DoD CAS (Consolidated Adjudication Service), and is on an unclassified effort, they must undergo the Homeland Presidential Directive 12 (HSPD-12) access vetting process.

The submitter, and the security office, will jointly complete the HSPD-12 package vetting process. Contractor CACs in this case must have a completed Federal Bureau of Investigation check with favorable fingerprint results returned prior to granting an interim CAC. The following applies to HSPD-12 vetting:

5.4.1 The submitter, working with their contractor, must submit contractor Declaration for Federal Employment (OF-306) completing (items 1, 8, 9, 10, 11, 12, 13, 16, and 17).

5.4.2 The contractor must include an up-to-date resume.

5.4.3 The security office will complete a HSPD-12 Notification of Incoming Personnel (NIP) form and submit it PSOD for processing.

5.5. Operational Security (OPSEC). Protecting critical and sensitive unclassified and controlled unclassified information (CUI) is a collective responsibility. Contractor personnel must follow OPSEC policies. This includes a requirement that contractor personnel must complete Level I OPSEC Awareness training within 30 calendar days of their reporting for duty and annually thereafter.

5.6. Information Awareness Training / Cyber Awareness Challenge. Individual contractor personnel must complete the DoD IA awareness training (also referred to as the Cyber Awareness Challenge) before issuance of network access and annually thereafter. All contractor employees working in IA/IT functions must comply with DoD training requirements in DoDD 8570.0.1, and DoD 8570.01-M within six months of appointment to IA/IT functions.

5.7. Controlled Unclassified Information (CUI). The Contractor is required to fully comply with all provisions of the Defense Federal Acquisition Regulation Supplement (DFARS) clause 252.204-7012, Safeguarding Covered Defense Information and Cyber Incident Reporting. This includes the implementation and maintenance of cybersecurity protections in accordance with the National Institute of Standards and Technology (NIST) Special Publication (SP) 800-171, 'Protecting Controlled Unclassified Information in Nonfederal Systems and Organizations.' The Contractor shall apply these protective measures to all systems that process, store, or transmit Covered Defense Information (CDI) including Controlled Unclassified Information (CUI).