Army_Data_Platform_RFI(SAM).pdf

DISTRIBUTION STATEMENT A: APPROVED FOR PUBLIC RELEASE DISTRIBUTION IS UNLIMITED

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

REQUEST FOR INFORMATION (RFI) 2

PROGRAM EXECUTIVE OFFICE 6

ENTERPRISE INFORMATION SYSTEMS (PEO EIS) 7

PROJECT MANAGER 10

ARMY DATA AND ANALYTICS PLATFORMS (PM ARDAP) 11

FORT BELVOIR VA 22060-5526 12

This Request for Information (RFI) is issued solely for information and planning 14 purposes. It does not constitute a Request for Proposal (RFP) nor a promise to issue 15 an RFP. Publishment of this RFI and any responses received does not commit the 16 Government to contract for any future services. Further, the Government is not 17 presently seeking proposals and will not accept unsolicited proposals. Responders to 18 this RFI are advised that the Government will not pay for any information or 19 administrative costs incurred in preparation of responses. Any associated costs are 20 solely at the interested party’s expense. Non-responses to this RFI will not preclude 21 competitive participation if an RFP is issued. The Government will not evaluate nor 22 release any artifacts from the review of the RFI responses. 23

This RFI is intended for the Government to identify potential sources and strategies for 24 continued hosting of the Army Vantage data analytics application. Information provided 25 in this RFI is subject to change and is not binding to the Government. The Government 26 does not commit to procurement of any RFI requirements discussed and release of 27 this RFI should not be construed as such a commitment or as authorization to incur a 28 cost for which reimbursement would be required or sought. All submissions become 29 Government property and will not be returned. 30

DESCRIPTION 32

The Army Data and Analytics Platforms (ARDAP) program manages a portfolio of 34 systems that enable the Warfighter through data and analytics. ARDAP modernizes 35 aging, disjointed, and legacy systems through enterprise-scale digital transformation 36 efforts. The Army Data Platform (ADP) product office within PM ARDAP is an emerging 37 initiative that provides unified data analytics capabilities that support federated 38 communities while operating as part of a broader coalition of tools that enable Army 39 enterprise analytics. The ADP solution will provide analytics environments, tools, and 40 services to federated communities across the Army enterprise with the scalability and 41 speed that current Army capabilities cannot provide. 42

SYNOPSIS 44

PEO EIS / PM ARDAP are conducting market research to determine industry 46 capabilities to provide a data analytics platform for distributed communities across the 47 Army enterprise, required under the attached DRAFT Capability Requirements 48 Document (CRD). Specifically, the Government is seeking information pertaining to the 49 implementation timeline, available service providers, staffing and management plan, 50 and price. A contract award is currently planned for Second Quarter Fiscal Year 2024 51

(2QFY24). 52

RESPONSES 54

Interested parties are requested to respond to RFI questions with a White Paper not 56 exceeding fifteen (15) pages, submitted in either Word (.docx) or Portable Document 57 Format (.pdf) using Arial 12-point font, no encryption. The Cover Sheet and Rough 58 Order of Magnitude (ROM) artifacts (submit the ROM as a separate file .xlsx format) do 59 not count against the 15-page limit. The following table must appear on the Cover (not 60 included in the page count) 61

Notice ID WXXXX-23-R-XXXX

Submittal Date Enter the Submission Date for the RFI published in the Solicitation Posting on SAM.gov or an earlier date

Submitted By Insert Responding Offeror entity name

Team Member(s) Insert any known Team Member (e.g., Subcontractor) entity names

SAM.gov Entity Unique ID and CAGE Code

Insert Offeror SAM.gov UEI and Facility CAGE Code

RFI Point of Contact (POC)

Name:

Position:

Address:

Phone:

E-mail:

Signed (Digital signature is preferred)

Participation (or non-participation) in response to this RFI will not preclude any vendor 64 from responding to future acquisitions, either individually or as part of a team. Marketing 65 brochures will not be considered adequate information in response to this RFI. 66 After reviewing the DRAFT CRD, interested capable vendors are invited to respond to 68 questions presented below. Responses should be submitted electronically as one 69 complete document. 70

PERIOD OF PERFORMANCE 72

One 12-month Base Year with four (4) twelve (12) month Option Years in accordance 74 with Federal Acquisition Regulation (FAR) § 52.217-9. 75

CONTRACT TYPE 77

To Be Determined (TBD) 79

REQUESTED INFORMATION 81

On a Cover Sheet, provide: 83

1. Point of Contact (POC) information 85

2. Company Name 86

3. Address 87

4. Phone Number 88

5. Fax Number 89

6. Email Address 90

7. Small Business social economic size 91

8. Unique Entity Identifier (UEI) 92

9. Commercial and Government Entity (CAGE) code 93

10. Partnering Team Approach (if any) 94

As appropriate, recommend cloud-native (IL4/IL5/IL6), modular open-source 96 architectures, and Commercial Off-the-Shelf (COTS) solutions. If any proprietary 97 technologies will be employed, provide a justification. In responses, use of any 98 proprietary information should be minimized and CLEARLY IDENTIFIED as such. 99 Specific Requests For information (RFI): 101

1. Explain how your solution can serve as a self-service data platform within an 103 enterprise data mesh architecture. In your response consider how your solution 104 enables communities to create, publish, maintain, and subscribe to data 105 products, how it enables domain-driven data ownership, and how it enables 106 federated data governance. 107

2. Explain how your solution is interoperable with external environments, such as 109 an enterprise data catalog, an enterprise Application Programming Interface 110 (API) data virtualization layer, and an enterprise Identity, Credential, and Access 111 Management (ICAM) solution. 112

3. Describe how your solution creates data products based on the outputs from 114

Artificial Intelligence (AI) and Machine Learning (ML) models. Provide information 115 on your solution’s capabilities to enable ML inference. Provide information on 116 your solution’s capabilities for model monitoring, data version control, and other 117

Machine Learning Operations (MLOps) capabilities. 118

4. How does your solution implement a “zero-trust architecture” that enables a 120 federated analytics framework? 121

5. Describe your experience securely transmitting data among Department of 123

Defense (DoD) enclaves in Near-Real-Time (NRT) for data analytics. 124

6. Explain your solution’s ability to collect, process, and store Controlled 126

Unclassified Information (CUI) and Classified information (Secret and above) 127 while leveraging Cross-Domain Solutions (CDS) between environments. 128

7. Describe your solution’s ability to support security-related auditability 130 requirements. 131

8. Describe your solution’s user support offerings to include help desk capabilities, 133 user account lifecycle management, and self-service training and other digital 134 adoption accelerators. 135

9. The Army currently uses dozens of different open-source and COTS visualization 137 tools. What strategy would you recommend for migrating and / or integration of 138 existing visualization products into a unified solution that meets the requirements 139 of the DRAFT CRD? Discuss your experience upgrading legacy Business 140 Intelligence systems. 141

10. This effort intends to acquire a solution(s) where labor is incidental to the 143 objective. Based on this information, provide a synopsis of a potential resourcing 144 or staffing plan and a management plan summary to include a risk management 145 and mitigation plan. 146

11. Provide a Rough Order of Magnitude (ROM), pricing Labor Rates / Categories 148

(LCAT), Other Direct Costs (ODCs), etc. Please also provide evidence of these 149 prices being used in sales of your solution. 150

12. Discuss any feedback and comments that would improve the DRAFT CRD. If 152 necessary, explain what additional information the Government could provide to 153 assist in proposing the most accurate price estimates based on the requirements 154 in the DRAFT CRD. If necessary, explain areas of risk that the Government 155 should consider. 156

13. Explain a recommendation on the contract type for this effort (Time and Material 158

(T&M), Firm Fixed Priced (FFP) etc.) and the associated rationale. Identify the 159 North American Industry Classification System (NAICS) code you recommend for 160 this project and provide your Unique Entity Identifier (UEI) code. 161

14. Using the template below, provide information for up to three (3) projects your 163 company / team has performed within the past three (3) years with similar scope 164 and size. Complete one table per project. 165

Agency/Customer

Project Name

Contract Vehicle and Task Order Number (if applicable)

[If a single project effort was performed using multiple contracts or task orders, please include the requested information for each contract or task order]

Contract Value, or in the case of a Task Order, the Task Order Value (for base and options)

[If your organization is the prime contractor on the referenced project, list the entire contract value. If your organization is a subcontractor, list the value of the subcontract.]

Contract Type (with well as incentives if applicable)

Pricing Structure - Contract Line Item Number (CLIN) structure and breakout of cost elements

Period of Performance (base and options)

Prime or Subcontractor

% of Work Performed

Primary Data Analytics Tools

Functional Scope

Description of Work Performed

Security Clearance Requirements (number of personnel and level of clearance and/or designation)

Facility Clearance Requirements

GOVERNMENT POINT OF CONTACT 169

Mr. Charles Davis (charles.d.davis49.civ@army.mil) 171

RESPONSE DEADLINE 173

The Government does not plan to respond to comments or questions on this RFI. 175 Responses must be received by 25 JAN 2023 via SAM.GOV to Charles Davis. 176