Attach1_DAVE_Sources Sought_Final.docx

Sources Sought Defense Acquisition Visibility Environment (DAVE) and Acquisition Information Repository (AIR) Support

Agency: The Office of the Under Secretary of Defense (Acquisition and Sustainment) (OUSD(A&S)) Acquisition Policy & Innovation (API) Directorate Notice Type: Sources Sought – Request for Information Posted Date: 01/31/2025 Response Date: 02/18/2025 NAICS Code: 541511, Custom Computer Programming Services PSC: DA01, IT Application – Services.

Background:

Definitions:

1. “Capability” is defined for this RFI as a software-enabled function, process, feature, application, system, or service that exposes, displays, or processes acquisition data to allow users to access, view, aggregate, analyze, report, or otherwise employ this data to support acquisition decision-making across the Defense Acquisition Community.

2. “Capability Delivery” is defined as the planning, design, prototyping, agile development, testing (unit, integrated, and user), deployment on government-furnished environment(s), user training, technical documentation, system administration, help desk, sustainment, maintenance, applicable licensing, DoD information system security compliance, and major or minor enhancement an acquisition Capability. Capability Delivery may also include associated administrative, management, and technical support necessary to successfully implement and manage Capabilities.

The Office of the Under Secretary of Defense (Acquisition and Sustainment) (OUSD(A&S)) oversees Department of Defense (DoD) acquisition and establishes DoD-wide acquisition policies. The effective oversight of, insight into, and innovation of acquisition processes and outcomes requires quality, timely, and accurate acquisition data. Empowered with access to authoritative acquisition data and insights from analyses of that data, DoD leadership can better report, analyze, and make informed decisions on the Department’s complex, $2 trillion acquisition portfolio.

The Acquisition Policy & Innovation (API) Directorate is an organization within OUSD(A&S) subordinate to the Assistant Secretary of Defense (Acquisition) (ASD(A)) and the Executive Director, Defense Pricing, Contracting, and Acquisition Policy. API delivers timely access to accurate, authoritative, and reliable acquisition data to the Defense Acquisition Community, the USD(A&S), the Defense Acquisition Executive and Component Acquisition Executives and leaders, and USD(A&S), Services, Agency, and Component analysts, facilitating program oversight, accountability, and decision making for the DoD’s portfolio of Acquisition Category (ACAT) I through IV programs. API’s acquisition data facilitates the statutory and regulatory reporting, assessment, and oversight requirements of the DoD for program data across all Acquisition Pathways.

The Defense Acquisition Visibility Environment (DAVE). DAVE is an API-first platform for managing authoritative and trusted acquisition data. It serves as a single access point for Capabilities developed internal and external to DAVE and is architected on top of a data framework that governs all Acquisition Visibility capabilities. Architected with a Java back-end, DAVE is integrated with several systems across the Department that leverage DAVE’s APIs capabilities for consuming and exposing data. In addition to its data sharing capabilities, DAVE features a front-end developed in Angular that enables DoD Component users to view, modify, and report on the data. DAVE is transitioning from Initial Operating Capability to Full Operating Capability. See the DAVE architecture and technology stack documents attached with this RFI.

The Acquisition Information Repository (AIR). DoD Instruction 5000.02 establishes milestones that programs must achieve to continue progressing through the acquisition lifecycle. Documentation required at these milestones is stored in the Acquisition Information Repository. AIR’s unstructured data is also a source of information to support analysis and decision making. AIR is currently a Confluence-based capability that is in the process of transitioning from Confluence to a stand-alone Java and Angular based application. Management of the AIR software and hosting is performed by a government office. The API Directorate augments the government office with a software developer.

Requirement:

API requires a contractor to employ agile methodologies to sustain, maintain, and enhance DAVE and AIR Capabilities to maintain currency with changes in policy or statute as well as meet new information requirements or changes in information security requirements. API will continue to receive data from existing sources (e.g., the Military Departments and Agencies) and will integrate new data sources into Capabilities to meet customer requirements. Requirements also include functional and integrated testing of Capabilities, and Agile development, security, and operations (DevSecOps) support.

DAVE and AIR are currently supported under three Blanket Purchase Agreement Call Orders: HQ003420F0274, HQ003422F0234, and HQ003422F0235. More information regarding these BPA Calls can be found at www.usaspending.gov.

These three BPA Calls total approximately 30 contractor employees. The program is transitioning into the next acquisition phase from final operation capability to sustainment with continual upgrades. Significant objectives of this requirement are enhanced contractor responsibility and accountability for Capability delivery as a single-award contract; seamless coordination with the government program manager from a single contractor program manager; faster delivery of features and functionality due to reduced inter-vendor coordination and integration; and cost savings due to the smaller footprint of a sustainment- and minor enhancement-focused effort.

Anticipated Contract Award Date: 06/16/2025

Anticipated Contract Start Date: 06/16/2025

Information Request:

Please answer one or all of the following parts to support our market research efforts. Please limit the length of each response to the minimum necessary, generally one-half to one page per numbered question. Recent corporate experience is defined as experience within the last five years by employees currently on staff at the company, please indicate if in a prime or subcontractor role.

Part 1. Capability Survey Questions

1. Please provide your company information:

Business name:

Business Address:

Business Point of Contact (POC):

POC Telephone:

POC E-mail:

Business Website:

Commercial and Government Entity (CAGE) Code (if any):

SAM.gov Unique Entity Identifier (UEI) (if any)*:

Business size for NAICS**:

· 541511, Custom Computer Programming Services

All socioeconomic categories as defined in FAR Part 19 (e.g., 8(a), SDB, HUBZone, SDVOSB, WOSB, etc.):

*To do business with the U.S. Government as a prime contractor the firm must be registered in SAM.gov by the time of award of any resultant contract.

**Visit www.sba.gov to learn more about small business size standards and Federal Contracting programs.

2. Does your company have an active GSA Multiple Award Schedule or a Government-wide Acquisition Contract (GWAC) under NAICS code 541511? If so, please provide your GSA contract number or the contract number and your firm’s business size on that vehicle. Are you classified as a small business under NAICS code 541511?

3. DAVE and AIR both have unclassified (NIPR) and classified (SIPR) instances. Does your firm have, at a minimum, a current SECRET non-possessing facilities clearance, or will your firm have one by the anticipated contract award date stated in this notice?

If the firm does not hold the required facility clearance, indicate that no facility clearance is held. Include a statement for how your firm will meet the clearance requirement within the timeframes outlined in this notice. WHS does not sponsor any clearances.

4. Please describe your recent corporate experience with the software and tools within the DAVE technology Stack. In particular, address your experience with an apigee-based API architecture.

5. Please describe your recent corporate experience supporting Capabilities within a Microsoft Azure cloud environment and within a secure MilCloud environment, with emphasis on delivering software Capabilities for use in the DoD NIPRNet and SIPRNet environments.

6. Please describe your recent corporate experience employing REST API design patterns, test-driven development, and agile testing.

7. Please describe your recent corporate experience developing Capabilities with Atlassian Confluence software.

8. Please describe your recent corporate experience developing Capabilities in Angular and Java.

9. Please describe your recent corporate experience implementing a DevSecOps approach to Capability delivery.

10. Please describe your recent corporate experience ensuring Capability information security compliance with DoD Instruction 8510.01, Risk Management Framework for DoD Systems.

11. Please describe your recent corporate experience leading agile software development program/ project/ or product management.

12. What is your firm’s plan to pursue and obtain Cybersecurity Maturity Model Certification (CMMC) 2.0 Levels 1 and 2?

Part 2. Performance Work Statement

1. Please review the draft Performance Work Statement. What improvements do you recommend? Are there processes or descriptions that are out of date or no longer best practices or considered a deviation from industry standard? Please highlight any information that is unduly restrictive to small business as listed in the draft PWS.

2. Are there alternative quantifiable means to measure software delivery and performance? If so, please recommend alternatives, completing the following table for each recommended metric:

Metric Title:

Purpose:

Standard:

Methodology:

Format:

EXAMPLE:

Metric Title: Mean Time to Recovery (MTTR) Purpose: To assess the AV DevSecOps team’s ability to maintain configuration control.

Standard: For the reporting period, the average time it takes to recover from an unplanned Production outage during the core hours is less than 30 minutes.

Methodology: Using a government-provided system and network monitoring application, the contractor performs health checks of the Production application.

Format: Total Number of Minutes of Unplanned Outage / Total Number of Unplanned Outages; Average Outage Time. (Example for a 30-day period: 45 min / 2; 22.5 min avg)

Part 3. Subcontracting Information

1. Identify any task areas your firm will collaborate with a subcontractor or team partner in the table provided.

2. If you intend to subcontract, please include the estimated percentage for Small Business subcontracting opportunities for each critical task area and the business size of the subcontractor/teaming partner.

Task Number