ADP-2.0_RFI #3 240924.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. RFI participation constitutes acknowledgement there is no basis for any future claims against the U.S. Government in relation to said participation.

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 Project Manager Army Data and Analytics Platforms (PM ARDAP) manages a portfolio of systems that will modernize Army business processes and enable scalable, agile, and trusted data platforms integrated with data services/applications, visualization, and analytic tools to facilitate fact-based and resource-informed decision-making. Product Manager Army Data Platform (PM ADP), 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 will be a multi-award task order indefinite delivery/indefinite quantity (IDIQ) contract (MATOC) providing enterprise data platforms from multiple data platform vendors. These platforms will enable self-service data domains and data product owners to create, manage, use and publish data products. ADP 2.0 will provide capability to federated communities across the Army enterprise with the scalability and speed that current Army capabilities cannot provide. The goals for ADP 2.0 include:

· Maximizing the use of both innovative, emerging technologies and existing Army enterprise tools throughout the program’s lifecycle.

· Establishing self-service data product management across all platforms.

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

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

· Continually researching and refreshing product offerings through continuous testing and acquisition of emerging technologies.

SECTION 2: CONTEMPLATED ADP 2.0 ACQUISITION APPROACH

ADP 2.0 is under the DoDI 5000.87 Software Acquisition Pathway using the Defense Business Systems sub-pathway. ADP 2.0 will include a MATOC award that includes multiple data platform vendors to test, deploy and support enterprise-level capabilities for the Army.

· Award a Multi Award Task Order Contract (MATOC) for up to five vendors.

· 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 platforms and tools based on the Army’s mission needs.

· Promote and foster a competitive ecosystem for ADP 2.0 to drive affordability and adaptability.

· Continually conduct industry / innovation research for improved emerging technologies.

· Enable opportunities for on and off-ramping vendors by providing viable alternatives to existing platforms.

· Provide guidance and oversight on DoD & Army Cybersecurity requirements to enable vendor(s) Assessment and Authorization.

· Streamlined Procurement Administrative Lead Time (PALT) for Task Orders that will improve customer experience.

· Leverage use of existing contract vehicles where possible.

· Fully transition from Army Vantage by FY2027.

SECTION 3: ADP 2.0 CONCEPT

ADP 2.0 is the follow-on capability to the current Under Secretary of the Army directed Army Vantage program and 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 it is anticipated to be the platform component of the Army’s initial transition towards a “Data Mesh” implementation. 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. The other components of the Data Mesh would include the Army Data Catalog (ADC), an Application Programming Interface (API) Layer, and Identity Management.

ADP 2.0, as the self-service data product management platform, provides compute and store for data products too complicated for an API layer to generate and is the engine for developing and refining data products to meet mission requirements. Data platforms traditionally provide the following layers (see Figure 1):

· Connection Layer – capable of ingesting, storing, cleansing, analyzing, categorizing, and extracting massive amounts of unstructured and highly structured data through numerous protocols which would include Open Database Connectivity (ODBC), Java Database Connectivity (JDBC), Tabular Data Stream (TDS), APIs, streams, and other native formats.

· Transformation Layer – provides data integration services that support extraction, transformation, and enrichment to create Data Products for use by internal and external Data Visualization capabilities.

· Data Product Layer – Contains curated data products ready for subscription and consumption. Also capable of making Data Products available to external consumers via standardized APIs.

· Data Visualization – Provides tools for analytics, workflow, dashboards, artificial intelligence, and machine learning (AI/ML) to self-service data scientists, citizen analysts, and their chain-of-command. These capabilities can be a component of a vendor's platform, or they can be an open architecture business intelligence plug-in tool that is interoperable with platforms.

Each integrated platform must be interoperable with a variety of analytic tools, and they must also be capable of exchanging data with other platforms using open API architecture.

Figure 1: ADP 2.0 Concept

SECTION 4: SYNOPSIS

PM ADP is seeking industry feedback on the acquisition approach and implementation methodology for ADP 2.0.

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 seven (7) 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 page limit.

3. Any questions regarding this RFI shall be directed to Ms. Babette Murphy (babette.r.murphy.civ@army.mil) and Ms. Maria Vital Smith (maria.l.vital-smith.civ@army.mil).

4. Responses must be received prior to noon 16 Oct 2024 via SAM.gov and CHESS.

5. The ADP 2.0 Terms and Definitions are included as an attachment.

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.

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 DATA and QUESTIONS:

The language and graphics are notional depictions on the future state of ADP 2.0. The images are provided to facilitate industry responses and are subject to change.

The Army Data Platform (ADP) 2.0 will consist of solutions comprised of integrated data platforms (see Fig 1 in Section 3): capable of solving either large complex problems or smaller, emerging, less-complex problems.

1. How do you define a Software as a Service (SaaS), Platform of a Service (PaaS), and Managed Service / Systems Integrator delivery models operating within DoD?

a. Which one of these three delivery models is your solution?

b. If SaaS, do you have a DoD-sponsored SaaS environment? If so, please provide the contract number.

c. Do you have a DISA Provisional Authorization?

2. Provide your notional timeline from contract award to a Minimum Viable Capability Release (MVCR) for an integrated data platform in an Army hosted IL5 environment. Graphics are acceptable with limited narration.

3. If the government awards the MATOC to a combination of SaaS, PaaS, and Managed Services Vendors, do you see challenges to fair and open competition at the follow-on Task Order level with this approach?

a. Do you have any contracting or competition-specific recommendations for putting Platforms, Tools, and Services under a MATOC?

4. Different delivery models will result in different timelines to achieve an Authority to Operate (ATO); how would you address Industry’s concerns regarding fair and open competition?

5. How would you implement identity management (e.g., standardized, role-based or attribute-based access controls) of a user who requires access across multiple platforms from different vendors? A diagram is acceptable.

6. Cost control and cost management are important to the Army. What type of pricing model would provide the Army with maximum cost control and management?

7. Provide any overall feedback you may have pertaining to the MATOC objectives, use of Statement of Objectives vs Performance Work Statement for the MATOC, time to implement the solution, acquisition strategy, and phased gates.

DISTRIBUTION STATEMENT A: APPROVED FOR PUBLIC RELEASE DISTRIBUTION IS UNLIMITED

image1.png