Unified Data Reference Architecture Request for Information

Request for InformationOffice of the Deputy Assistant Secretary of the Army forData, Engineering, and SoftwareIntroductionPurposeThis Request for Information (RFI) is issued by the Office of the Deputy Assistant Secretary of the Army for Data, Engineering, and Software to provide the United States (U.S.) Army with a better understanding of industry capabilities, potential sources, and best practices relevant to the implementation of a Unified Data Reference Architecture (UDRA) for the U.S. Army.  The UDRA is expected to unify data mesh (may also simply be referred to as mesh in this RFI) and data fabric principles and efforts.  As data fabric implementations are well underway, the current focus of the UDRA is on achieving the benefits of a data mesh by leveraging emerging data fabric capabilities.  The desired UDRA will be Soldier-Driven and Domain-Owned Products.  This RFI invites industry to submit relevant information, comments, capabilities, and recommendations for approaches,

potential development, implementation opportunities, and corresponding business models. Responses to this RFI will assist the U.S. Army in determining if sources exist that are capable of satisfying UDRA implementation requirements.  After the receipt of responses to this RFI, the Government may invite some or all RFI respondents to further discuss their capabilities, solutions, and practices with Government representatives.IntentThis is not a Request for Proposal (RFP), Request for Quotation (RFQ), or an invitation for bid, nor does its issuance obligate or restrict the Government to an eventual acquisition.  All information received in response to this RFI will be used for market research purposes only.  The Government does not intend to award a contract because of responses to this RFI, nor otherwise reimburse respondents for the preparation of any information submitted or Government use of such information.  Acknowledgement of receipt of responses will not be made, nor will respondents be notified regarding the outcome of the information received.  Proprietary information in the submitted responses should be clearly marked.This initial UDRA RFI includes tabular, textual, and static image views, as well as digital engineering-based model views of sections of the UDRA.  The static views are presented for ease of readability in this initial RFI.  However, future RFIs may be issued solely with digital engineering model-based views of the UDRA and its segments.  All views presented should be considered draft versions that reflect the current state of the UDRA development.  As the UDRA is being developed incrementally and iteratively, it is expected that the UDRA will be informed by responses to this and future RFIs and may be revised accordingly. Scope and AssumptionsThe Data Mesh principles and body of knowledge are relatively recent developments which have emerged over the last few years, from documented industry practices, some of which are still evolving and being applied.  Since Data Mesh architecture has its roots in industry practices, the Army is investigating adoption or adaptation of those practices and associated technologies for military application and use.  Custom development or adaptation of mesh concepts without precedent is the least preferred solution approach.Development of the UDRA is being undertaken in incremental segments.  This segment of the UDRA and this RFI are focused on the definition and realization of domain owned data products.  Subsequent segments may address other aspects of a data mesh architecture such as required enterprise services, data domain capabilities, and other infrastructure considerations.  Currently, the mesh-oriented aspects of the UDRA are focused on analytical products, rather than real-time operational data.For the purposes of this UDRA segment and RFI, a domain owned data product (may also be referred to as Domain Data Product) is what a functional domain (e.g., Mission Command, Intelligence, Fires/Effects, Maneuver, Sustainment, Protection, or Cyber Protect) produces to provide operational understanding to the Commander (Decision Maker).  Domain owned data products are:Owned and produced by a functional domain leveraging data from multiple sources following global and local established Governance requirementsShared directly with data users and consumersAdherent to a set of usability characteristics (e.g., VAULTIS)Autonomous, with their own lifecycle and model which are managed independently of other domain owned data productsConsidered to have Value, Usability, Feasibility, and mission ViabilityInitially, the U.S. Army’s UDRA data products will generally be produced at the CORPs level and above.  Domain data products will be produced at lower echelon levels by exception only, until UDRA implementation and adoption lessons learned can be applied to extend the mesh toward tactical level units.  Additional details regarding UDRA mesh data products are provided in the detailed description below.It is assumed, for purposes of this UDRA segment and RFI, that enterprise services needed to support the mesh (e.g., enterprise-wide data catalog services, zero trust-based Identity, Credential, and Access Management (ICAM) services, DevSecOps environments for code development and expedited Authority to Operate capability or service) will be globally available.  Identification and recognition of some of the necessary enterprise services is included in this RFI, but the details and specifics of those services will be addressed in a subsequent RFI.  However, it is assumed that an available enterprise data catalog service will be extensible to support the storage and retrieval of UDRA mesh-specific metadata requirements.As addressed in the attached URDA, this segment of the UDRA assumes that data product metadata can be linked and related to associated data products and is not intended to prescribe that all data product metadata necessarily be embedded in every data product instance or transmission.Objective / Measures of Success of the UDRAThe objectives of the ASA (ALT) DASA-DES Unified Data Reference Architecture are to:Share data through domain owned data productsPrepare Army data for analytic technology required now and in the future fightUDRA will simplify complexity and expedite efficiency and mission effectiveness.  UDRA based on the Data Mesh concept will be the ways and means to aligning with DoD Data Strategy where Data is a Strategic Asset.UDRA will adhere to the DoD’s five Data Decrees and support the SECARMY’s second objective to ensure the U.S. Army becomes a more data-centric force.UDRA will align with the U.S. Army’s Data Implementation Plan, EXORD 009-20 FRAGO#4.UDRA will satisfy the Unified Data Cross Cutting Capability within Initial Capabilities Document for Common Operating Environment 10 October 2018.The measure of success the U.S. Army seeks to achieve with this RFI is to partner with the industry towards building and understanding of a unified data reference architecture that will provide the right and left boundaries (constraints) allowing industry to provide the Government with innovative solutions that are compliant or conformant to the UDRA.RFI InstructionsRFI ContentsThis RFI contains the following components:This introduction and set of RFI response instructions.An attached description of the problem statement and detailed UDRA data product description.A Digital Engineering (DE) model of the UDRA, in two representations:A Digital Engineering (DE) model of the UDRA, provided as a navigable and interactive HTML export from the MagicDraw modeling platform.The Digital Engineering model of the UDRA, as a MagicDraw source file.UDRA Model DescriptionThe UDRA model was developed as a companion to the written RFI. The goal is to contain all of the technical details in an single Digital Engineering (DE) environment and to conduct all reviews using the DE toolset. The model is developed using the Cameo MagicDraw v19.0 tool, it follows the Unified Architecture Framework (UAF) using the System Modeling Language (SysML). UAF is an architecture modeling standard that is based on the DoD and NATO architecture frameworks (DoDAF and NAF). SysML is an international standard general-purpose modeling language for systems engineering. Responses to the RFI can include updated versions of the UDRA model. Additionally, comments on the usability of the model are also appreciated. It should be noted that everything in the model should be considered a draft and is a work in progress. This is especially true of the elements describing other parts of the UDRA such as the mesh services and data domains. UDRA Model User Guide There are two versions of the model included with the RFI. The information contained in each model is identical. However, the MDZIP file can be opened using Cameo MagicDraw 19.0 and can be edited while the HTML file can be opened in any web browser and is read-only. When the model opens (in either version), you will be directed to the model title page. From the title page click on the icon for “Table of Contents – Data Product RFI”. This will direct the viewer to another content diagram containing links to several other diagrams that show the Data Product model views. Many of the diagrams contain additional links to other relevant diagrams. Clicking on any element will bring up the specification view which contains documentation for that element and information on its relationships. It should be noted that the model can be navigated by using the browser back and forward arrows as well. Additionally, for those more familiar with MBSE tools, it is also possible to navigate the model using the model browser window. The information relevant to this RFI is primarily found in the Operational (4.1 Taxonomy, 4.2 Structure, 4.4 Processes, and 4.5 Information) and Strategy packages (3.1.4 UDRA Capabilities).Response SubmissionResponses to this RFI are requested in two parts.  First, Army seeks details associated with company profile and demographics, the company’s Data Mesh solution as it pertains to mesh data products, security and Government regulation compliance, and acquisition related information.  Further elaboration of these areas of interest is included in the Detailed Solution Description above. Responses should be submitted in Microsoft Word format or Adobe Portable Document Format (PDF).  Responses should not exceed twelve (12) pages.  A cover page, company profile, and demographic information are not included in the page count restriction.  Responses should be in Arial font, 12 points.  Respondents are strongly urged to adhere to this page limitation and limit marketing material to provide substantive information.  Submit responses via e-mail to willie.j.lacy.civ@army.mil & quang.d.nguyen18.civ@army.mil by 02 December 2022 at 5:00 PM Eastern Standard Time. Respondents are requested to respond to the following company profile and demographic information:Organizational Name, Address, and Country of Business (if organization has experienced name changes, please list all previous names used)Company representative and business titleIndustry NAICS Codes (North American Industry Classification System) and business size for each NAICS codeContract vehicles and contracts held (vehicle, agency, and expiration date) - please highlight Army and DoD contracts clearlyYear company was established/foundedCompany ownership (public, private, joint venture).  Provide information regarding Foreign Ownership, Control, or Influence (FOCI) issues associated with your company/and or offering(s).Business Classification/Socio-Economic Status (e.g., large, small, 8(a), women-owned, hub-zone, Small Disadvantaged Business (SDB), Service-Disabled Veteran-owned)Location of corporate headquartersLocations of facilities Outside of Continental United States (OCONUS)Location where currently incorporatedOverview of products and services providedOverview of experience in OCONUS with specific locations discussedResponse ContentPlease address the items below wherever possible.  As with all Information Technology (IT), the Unified Data Reference Architecture (UDRA) is evolving; please point out where industry, or your solutions, may impact the basis of the items below.Provide a general description of your company’s UDRA Mesh Data Product solution, the features of mesh data products, how they interoperate with one another, and the methods to interoperate with mesh services or components your company does not provide. In addition, describe how they benefit the Army and differentiate from other solutions.Describe any barriers which preclude your solution from conforming with the UDRA described above.  Provide recommendations for addressing those barriers, through either modification of your solution or of the UDRA itself.Identify areas of this UDRA segment for which additional detail is needed to develop a conforming solution.  Provide specific details about additional information required.Describe how your technical approach would support the data product metadata requirements and what additional metadata is recommended to support the mesh operational aspects of the UDRA.Describe your current technologies, products, and solutions which can produce and consume conforming data products as defined in the Detailed Solution Description.Describe whether your solution includes specification of API endpoints for sharing data products as part of the data product definition.Describe whether your solution includes transformation and analytic processing logic (algorithms) involved in producing a data product as part of the product definition.Describe whether your solution includes Service Level Agreements (SLA), Service Level Objectives (SLO), Service Level Indicators (SLI), Memorandums of Agreement (MOA), and Memorandums of Understanding (MOU) as components of the data product.  If not, provide recommendations for including them as external to the data product.Confirm the compatibility and usability of the attached Digital Engineering model format for describing the UDRA data product definition for the purposes of this RFI.Describe how your solution can integrate into data fabrics.  Additionally, please describe integration with other Army enterprise and DoD Joint Service capabilities.What metadata and product coupling approach(s) does your solution employ?  Why is this approach favorable or unfavorable for UDRA implementation?What platform/operating system combinations are supported by your solution?What is your methodology and approach to managing the data product solution at the producer data domain? Include your methodology to enforce and manage data product policies (e.g., access control) by both producer and consumer data domains.Discuss the standards and protocols your solution supports, and any functionality restrictions imposed by enforcing those standards.Provide Uniform Resource Locators (URLs) of relevant on-line demonstrations, video, or background material on your company’s solution.Describe how your solution supports consumer data domain feedback regarding data products.Enumerate all the major product elements and model or version names (e.g., appliances, servers, client software) of your solution. Describe how your technical approach would support data loss prevention, protection of data-at-rest and data-in-transit to/from producer and consumer data domains and how it would comply with Federal Information Processing Standards (FIPS) 140-2.Describe how your technical approach complies or supports the NIST Publication 800-137 framework and National Institute of Standards and Technology (NIST) Publication 800-53 Rev. 4.Explain any best practices on how your technical approach would enable the monitoring of incidents and threats and ensure reporting and compliance with data security standards, laws, initiatives, and policies.Describe how your technical approach would comply with DoDI 5015.02 and with e-Discovery requirements.DisclaimerThis RFI is issued solely for information and planning purposes. This RFI is not a solicitation and is not to be construed as a commitment by the Government to issue a solicitation or ultimately award a contract. Responses will not be considered as proposals, nor will any award be made as a result of this request. Federal Acquisition Regulation (FAR) clause 52.215-3, “Request for Information or Solicitation for Planning Purposes”, is incorporated by reference. The Government does not intend to reimburse respondents for any costs associated with the submissions of their responses to this RFI; respondents to this RFI are solely responsible for all expenses associated with responding. Proprietary information and trade secrets, if any, must be clearly marked on all materials. All information received in response to this RFI that is marked “Proprietary” will be handled accordingly. Please be advised that all submissions become Government property and will not be returned nor will receipt be confirmed. In accordance with FAR 15.201(e), responses to this RFI are not offers and cannot be accepted by the Government to form a binding contract.Responses from this RFI will be used to formatively shape broad Army guidance for acquiring software solutions. Response content may be aggregated and anonymously published into summary documentation to facilitate such guidance. Any publications resulting from this RFI will be non-attributional, and RFI respondents’ consent for their responses to be used for such purposes