NexusGreenData keeps your controlled lists — country codes, currencies, statuses, organisational units — consistent and versioned across every system, with governed change requests and a two-way sync to the business glossary.
Reference data management (RDM) governs the shared code sets that every other system depends on. When those lists drift apart, reports stop reconciling and integrations break. NexusGreenData holds one authoritative, versioned copy of each list.
It is paired with the master data management module and runs on the same data catalog, so reference values and master records share one governed vocabulary.
What it does
Define each controlled list once, with bilingual labels, descriptions and ownership, and reuse it everywhere.
Every change produces a new, dated version. You can see what a code set looked like at any point and roll back if needed.
Roll values up into parent-child structures so a region, a group or a category can be summarised consistently.
Map one code set to another to reconcile systems or standards that use different codes for the same concept.
Changes flow through an approval queue with rejection, resubmission and notifications — never a silent edit in production.
Two-way sync with business glossary terms, plus CSV and JSON import and export for bulk loads and downstream use.
Create a code set, add its values with bilingual labels, and publish a version. From then on, every edit is a change request routed to an approver, so the published list is always the approved one.
Code sets sync to business glossary terms and can be imported or exported as CSV or JSON, so the same controlled vocabulary reaches every tool and pipeline.
| Objects | Code sets, values, versions, hierarchies, crosswalks |
|---|---|
| Change control | Approval queue with rejection, resubmission and notifications |
| Catalog sync | Two-way sync with business glossary terms |
| Import and export | CSV and JSON import jobs and export |
| Versioning | Dated versions with rollback |
| Languages | Arabic and English, right-to-left |
Who it is for
Teams whose dashboards and pipelines break because the same status or country code means different things in different systems.
Offices that must prove a controlled, versioned, auditable vocabulary across the organisation under NDMO standards.
Owners who need crosswalks between internal codes and national or international standards without rekeying.
FAQ
Reference data is the controlled lists and code sets that classify everything else — country codes, currencies, status values, organisational units. Reference data management keeps those lists consistent, versioned and governed across systems.
Every change goes through a change request with an approval queue. Requests can be rejected and resubmitted, and approvers are notified, so a code set is never edited silently in production.
Yes. Code sets are synced with business glossary terms, so the same controlled vocabulary is visible wherever your teams work with data.
Yes. Crosswalks map one code set to another, and hierarchies roll values up into parent-child structures — useful when systems or standards use different codes for the same concept.
See how NexusGreenData governs your reference data — versions, hierarchies, crosswalks and change requests — synced to the business glossary.