IXL Experimentation Offerings 

As part of our initial offering within the Innovation Exchange Lab, we are collaborating with the UDRA team and industry partners to build and test the UDRA implementation guidelines

Unified Data Reference Architecture (UDRA) – What is it? 

The Assistant Secretary of the Army for Acquisition, Logistics, and Technology (ASA-ALT) Deputy Assistant Secretary of the Army (DASA) for Data, Engineering, and Software (DES) is defining a Unified Data Reference Architecture that introduces Data Mesh principles into the Army’s data architecture. Data Mesh is a data architecture based on a federated and decentralized approach to analytical data production, sharing, access, and management in complex and large-scale environments, within or across organizations.  It is characterized by federated computational governance, self-service infrastructure, treating and providing data as a product, and autonomous data domains that are responsible for their data. The Unified Data Reference Architecture (UDRA) is intended to guide the implementation of interoperable data sharing across all Army acquisition programs.  

In Development: Our UDRA Reference Implementation 

Our reference implementation represents the cornerstone of our initial offering – a real-world application of the UDRA framework. , allowing for early experimentation and validation against the provided services and components allowing vendors to demonstrate conformance and/or capture lessons learned to inform improved product development.

What is within the first phase of the UDRA Experimentation? 

The initial phase of this offering will provide limited services as part of the reference implementation, and experimentation will address targeted priority use cases and solutions against the state of maturity of the implementation. As our reference implementation expands and matures, more opportunities to expand on scope of solutions and capabilities for experimentation and demonstration will be iteratively released and announced.  

Currently seeking these Solutions for Specific Use Cases/Services: 

We are actively seeking vendors and software solutions that adhere to the principles of our data mesh reference architecture. We are particularly interested in solutions serving as data catalogs within the framework of UDRA. If your offering aligns with our vision and UDRA service descriptions of a data catalog capability, we invite you register to the Army Innovation Exchange and submit a UDRI Test Request. 

To learn more about UDRA and better establish your solutions alignment to the reference architecture, we recommend you review the following resources:

The UDRA RFI Documentation, is a white paper call notice is published on sam.gov providing guidance on white paper content that must be submitted with company registration to Innovation Exchange. Updates will be made reflecting new solutions we are seeking for specific use cases/services alignment to the reference implementation maturity and impacts.

A pre-brief engagement with vendors will outline process of participation, methods and requirements for obtaining architecture artifacts, API documentation, Integration guidance, specific demonstration objectives, and infrastructure entrance criteria.

Important Note

Any Personally Identifiable Information (PII) and/or sensitive information submitted during registration will be held as Controlled Unclassified Information (CUI).  You should NOT submit any Classified information or Privately held Intellectual Property or content.  Only provide what is already publicly available.

Frequently Asked questions

Technical Details Examples:

Here are examples of product related content you may wish to share during registration.

1. Technical Requirements: 

What are the minimum hardware and software requirements for deploying your solution in our environment? 

Does your software require specific databases, operating systems, or server configurations? If so, identify which ones 

What kind of computing resources (CPU, RAM, storage) are optimal for running your software efficiently in our setup? 

2. Compatibility and Scalability: 

How compatible is your software with our existing data infrastructure and tools, especially those adhering to data mesh principles? 

Can you provide examples of organizations similar to ours that have successfully scaled their data infrastructure using your software? 

What is the maximum data volume and user load your solution can handle effectively, and how does it scale as our needs grow? 

3. Integration and Interoperability: 

a. Integration Capabilities: 

Does your software offer APIs or data connectors for seamless integration with other data-related tools and platforms in our ecosystem? 

How does your software handle data transformations and schema evolution when integrated with diverse data sources within a data mesh environment? Any context specific to Army is a bonus 

b. Interoperability with Third-party Tools: 

Are there any third-party tools or technologies that your software is specifically designed to work well with within a data mesh architecture? 

How does your software facilitate interoperability between different domain-oriented data products and services in a decentralized data mesh environment? 

a. Data Governance Measures: 

What data governance features does your software offer to ensure data quality, lineage, and metadata management within a data mesh architecture? 

How does your solution support data discovery and cataloging, especially in a decentralized data environment with multiple domains? 

b. Security Protocols: 

What security protocols and encryption standards are employed to protect data both in transit and at rest? 

Can you describe the access control mechanisms within your software, especially in scenarios where different domains need different levels of access to shared data resources? 

How does your software handle data privacy and compliance requirements 

Software scanning required for submission 


Scroll to Top
Scroll to Top

Copyright © 2024 All Rights Reserved.