Attachment_1_ADP_2.0_RFI.docx

DISTRIBUTION STATEMENT A: APPROVED FOR PUBLIC RELEASE DISTRIBUTION IS UNLIMITED

ARMY DATA PLATFORM (ADP 2.0) – REQUEST FOR INFORMATION (RFI)

REQUEST FOR INFORMATION (RFI)

PROGRAM EXECUTIVE OFFICE

ENTERPRISE INFORMATION SYSTEMS (PEO EIS)

PROJECT MANAGER

ARMY DATA AND ANALYTICS PLATFORMS (PM ARDAP)

FORT BELVOIR VA 22060-5526

THIS IS A REQUEST FOR INFORMATION (RFI) ONLY. PEO EIS is performing market surveillance for Army Data Platform 2.0 (ADP 2.0), to include acquisition strategies. No solicitation exists. This is not a request for a quote, request for proposal, request for a prototype solution, or an invitation to bid. This is not to be construed as a commitment by the US Government to form a binding contract or agreement. The Government will not reimburse or pay for information submitted in response to this RFI. All submissions become Government property and will not be returned.

This RFI is open to all business types. The anticipated North American Industry Classification System (NAICS) code for this action is 541512, COMPUTER SYSTEMS INTEGRATION DESIGN SERVICES, size standard $30M.

In 2023, the Government published one other RFI for ADP 2.0. The purpose of this RFI is to validate and or refresh those findings. Previous RFIs will be linked or attached for reference.

This RFI is issued solely for information and planning purposes. Publishing this RFI and any responses received do not commit the Government to contract for any future services. The Government is not currently seeking proposals and will not accept unsolicited proposals.

SECTION 1: ADP 2.0 DESCRIPTION

The Army Data and Analytics Platforms (ARDAP) program manages a portfolio of systems that enable the Warfighter through data and analytics. ARDAP modernizes aging, disjointed, and legacy systems through enterprise-scale digital transformation efforts. The ADP 2.0 product office within PM ARDAP provides unified data analytics capabilities that support federated communities while operating as part of a broader coalition of tools that enable Army enterprise analytics.

ADP 2.0 is an enterprise data platform that enables self-service data domains and data product owners to create, manage and publish data products. It will provide the enterprise data ecosystem mesh services to ensure federated discoverability, access, governance, and interoperability. ADP 2.0 will provide analytics environments, tools, and services to federated communities across the Army enterprise with the scalability and speed that current Army capabilities cannot provide. ADP 2.0 will replace the current Army Vantage program and must be available in sufficient time to allow the migration from Army Vantage. ADP 2.0 is evaluating the implementation of the Unified Data Reference Architecture (UDRA) and could provide federated mesh services in the future. The goals of the technical approach for ADP 2.0 include:

a. Create an Army Data Layer that is available for any vendor technology.

b. Maximize the use of innovative, open-source commercial technology and existing Army enterprise tools throughout the program’s lifecycle.

c. Integrate agile Continuous Integration and Continuous Delivery/Deployment (CI/CD) methodology to rapidly deploy software throughout the program’s lifecycle.

d. Maintain continuous competition through a multi-award task order contract to ensure innovation, program affordability, and eliminate vendor lock

e. Design, acquire and implement a Unified Data Reference Architecture (UDRA) -aligned Modular Open System`s Architecture (MOSA) solution.

SECTION 2: CONTEMPLATED ADP 2.0 ACQUISITION APPROACH

The Army will continue to maintain the Army Vantage program to enable capability availability and a seamless transition to ADP 2.0. Below is the current pre-decisional plan; ADP 2.0 is seeking feedback to inform the validity of this approach prior to upcoming Acquisition Shaping Panels and a final decision on the acquisition approach.

The Army will transition from Army Vantage to ADP 2.0 through a phased approach:

· Phase 1. Maintain Army Vantage to fulfill leadership directives without interrupting existing capabilities.

· Phase 2. Establish an infrastructure capable of storing the current Army Vantage data layer within the Army platform Enterprise Cloud Management Agency (ECMA).

· Phase 3. Award a multi-vendor Indefinite Delivery/Indefinite Quantity (ID/IQ) contract for ADP 2.0.

· Align ADP 2.0 with the 5000.87 Software Acquisition Pathway and 10 USC § 2222 requirements.

· The notable advantage of this award is to grant the freedom and flexibility to employ the best tools and services based on the Army’s mission needs.

· Intent is to adopt an open architecture and transition away from monolithic, all in one technology stacks. Additionally, this approach will enable the Government to enable best value for tool/service selection, and economical cost sharing.

· Centrally funded data layer/data objects, while the users can leverage the data in their own purchased tools and leverage further task orders for additional capability. As the Army moves towards a federated approach to data management, in the near-term, data products will be stored and managed within ADP to minimize complexity.

· Encourage multi-vendor collaboration.

· Governance and implementation of the ADP 2.0 program is still being discussed, but the ADP 2.0 program is open to industry feedback on these areas.

· ADP 2.0 intends to maximize economic value and industry best practices via modular contracting that enables an affordable solution.

· Contract Type TBD

Figure 1: ADP 2.0 Concept

SECTION 3: ARMY CAPABILITY REQUIREMENTS

The ADP 2.0 requirement, the follow-on capability to the current Under Secretary of the Army directed Army Vantage program, provides an Enterprise level data platform capability. It directly supports five of the six components of the Business Enterprise Architecture Data to Decision business process and is the platform component of what the Army is beginning to call the “Data Mesh”. It is a core component of the Army’s efforts to become a Data Centric force and supports the implementation of the Army Digital Transformation Strategy goal of using data as a strategic asset. Industry technology used in ADP 2.0 shall be fully interoperable with DoD Identity, Credential and Access Management (ICAM) capabilities.

The ADP 2.0 Capability Requirements Document (CRD) is attached as a reference.

SECTION 4: SYNOPSIS

PEO EIS/PM ARDAP are seeking industry feedback on the acquisition approach and intent for the ADP 2.0 capability. This will be a novel approach to providing such capabilities in the Army and the desire is for this to be in coordination with industry.

SECTION 5: RESPONSE FORMAT AND DELIVERY

1. Cover Letter with the following:

a. Point of contract for business development, technical expertise, and contract execution.

Position:

Address:

Phone:

E-mail:

2. Interested parties are requested to respond to RFI questions with a White Paper not exceeding ten (10) pages, submitted in either Word (.docx) or Portable Document Format (.pdf) using Arial 12-point font, no encryption. The Cover Sheet does not count against the 10-page limit.

3. Any questions regarding this RFI shall be directed to Mr. Charles Davis (charles.d.davis49.civ@army.mil).

4. Responses must be received prior to 12pm ET 15 January 2024 to Charles Davis.

The Government will make every effort to answer questions and post responses daily but cannot guarantee that all questions will be answered before the RFI response submission deadline. Participation (or non-participation) in response to this RFI will not preclude any vendor from responding to future acquisitions, either individually or as part of a team. Marketing brochures will not be considered adequate information in response to this RFI.

After reviewing the Approved CRD and this RFI, interested capable vendors are invited to respond to questions presented below. Responses should be submitted electronically as one complete document. In responses, use of any proprietary information should be minimized and clearly identified as such.

SECTION 6: RFI QUESTIONS: Comment by England, Shannon K CTR USARMY PEO EIS (USA): What future discriminating factors (NM 3) does industry suggest in a proposal

1. Given the background information on the current state of Army Vantage as it operated under an Other Transaction Authority (OTA) and FAR efforts, please provide industry best practices to transition from the current agreement to a potential follow-on contract where:

a. The platform and tools are vendor agnostic and use open APIs for data interface.

b. The best of breed technologies and tools are available from across the markets.

c. Incorporates emerging technologies, the ADP 2.0 program preference is for key technologies (data connectors) to be FEDRAMP certified.

2. What type of contract mechanism (e.g., OTA, multi-award task order ID/IQ) provides the most flexibility towards achieving the ADP 2.0 objectives?

3. Explain a recommendation on the contract type for this effort (e.g., Time and Material (T&M), Firm Fixed Priced (FFP) etc.) and the associated rationale. Identify the North American Industry Classification System (NAICS) code you recommend for this project and provide your Unique Entity Identifier (UEI) code.

4. How would you price and scale your offering? What information do you require from the Government to price and scale the capability?

5. What are the recommendations for ADP 2.0 to incentivize industry collaboration with a multi-vendor construct if the vendors are not in a contractual relationship with one another? Are there known restrictions/limitations on sharing information across vendors that the Government needs to be aware of and account for (e.g., provisioning/identity management)?

6. What is your recommendation on the ADP 2.0 path forward considering the background above?

7. Can you provide feedback / recommendations on how to implement the ADP 2.0 Concept (Figure 1)?

8. Identify any approaches or assumptions not explicitly stated in this RFI that would enable the Army to achieve ADP 2.0 objectives.

9. What recommendations do you have for implementing the CRD with an agile methodology?

10. What would your estimated timeframe be for ADP 2.0 to develop and deploy a solution that achieves the CRD threshold requirements? Can you identify areas of risk?

11. How would you leverage existing Government enterprise infrastructure as new and unique requirements arise (e.g., cArmy, ECMA, EDSC)?

12. What recommendations do you have for the Government in developing an effective intellectual property strategy? What data rights should the Government retain and require?

SECTION 7: INDUSTRY COLLABORATION:

The Government reserves the right to conduct one-on-one meetings in person or virtually with respondents to this RFI. The Government may or may not choose to interact with select respondents to perform market research. Such exchanges, should they occur, would be solely for the purpose of obtaining further clarification of industry’s potential capabilities, experiences, and perspectives.

DISTRIBUTION STATEMENT A: APPROVED FOR PUBLIC RELEASE DISTRIBUTION IS UNLIMITED

image1.png