> For the complete documentation index, see [llms.txt](https://docs.ovaledge.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ovaledge.com/release8.2/governance-catalog/reference-data-management.md). # Reference Data Management In today's digital world, businesses deal with a lot of information, like customer details and product codes. Organizing this data correctly is crucial to avoid mistakes and confusion. Reference Data Management (RDM) helps ensure all the essential information stays consistent and correct across different parts of a company. ### What is Reference Data Management? Organizations use Reference Data Management (RDM) to maintain the consistency and accuracy of critical data in various systems and applications. RDM manages and maintains essential information such as customer details, product specifications, or financial codes in a structured approach, serving as a backbone of data organization. ### Use Cases 1. **Financial Services:** In banking and finance, RDM is crucial for managing reference data like currency codes, exchange rates, and financial instrument identifiers. 2. **Healthcare:** RDM helps manage reference data such as patient identifiers, medical codes (e.g., ICD-10, CPT), and drug classifications. 3. **Retail:** Retailers use RDM to manage product information, including SKUs, UPCs, and product categories. 4. **Manufacturing:** In manufacturing, RDM helps manage reference data like product specifications, part numbers, and supplier information. 5. **Government:** In Government, agencies use RDM to manage reference data such as geographic codes, tax identifiers, and regulatory classifications. ## Reference Data Management Reference Data Management (RDM) is a system designed to gather and organize similar attributes from various source systems into one centralized location and manage them. Here's a breakdown of how Reference Data Management works: * **Managing Reference Data Units (RDUs):** Create and delete RDUs, which act as containers for similar information and help organize and maintain reference data. * **Managing Attributes:** Organizing and managing attributes within RDUs to structure and organize reference data is allowed. * **Tracking Metadata Changes:** Track and analyze changes to metadata, such as titles, descriptions, and stewardship assignments. * **Audit Trails:** Audit trails capture all reference data unit actions and changes, helping track attribute additions, deletions, and modifications over time. * **Collaboration:** Collaborate and share information to ensure the correct alignment of all attributes. * **Alerts & Notifications:** We trigger alerts and notifications for specific events, such as changes to attributes detected during connector profiling. This ensures that relevant stewards are promptly notified of any modifications to reference data. * **Security Measures:** We implemented security measures to protect and safeguard reference data units. *** Copyright © 2025, OvalEdge LLC, Peachtree Corners, GA USA --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.ovaledge.com/release8.2/governance-catalog/reference-data-management.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.