Blueprint and governance
The first domain, its entities and attributes, the match rules and the steward roles are agreed with the data owner and the business sponsor, along with the order in which later domains follow.
Platform implementation
We implement Semarchy xDM as a data hub that business teams help shape, with golden records, validation rules and guided workflows built quickly and changed without long projects.

Semarchy rewards an iterative approach, so the work centres on modelling one domain well, putting it in front of data stewards, then extending it. xDM can be deployed on your own servers or in a cloud environment you control, which keeps the hub and its records in the country when residency rules require it. Arabic names and the Emirates ID and Saudi national ID formats go into the enrichers and match rules of that first domain.
In the xDM Application Builder we define entities, references and the match and survivorship rules, written in SemQL, that turn master records into golden records. Enrichers standardise names and addresses, validations stop bad data at entry, and steppers guide stewards through creation and approval screens. The hub exposes records through its REST API and publishes changes to downstream systems.
Semarchy xDM and related product names may be trademarks of their respective owners.
Implementation, customisation, deployment and ongoing support, with governance your steering committee can follow.
The first domain, its entities and attributes, the match rules and the steward roles are agreed with the data owner and the business sponsor, along with the order in which later domains follow.
A sequence such as customer, then supplier, then product, each delivered in short releases that stewards test as they go.
Code lists, hierarchies and mappings between source codes managed in the hub, with approval for every change.
Dashboards showing duplicates, validation failures and steward workload by source, built in xDM or in your BI tool.
Semarchy issues regular xDM releases, so we plan upgrades of the hub and its repository database, test models against each release, and watch integration jobs, validation failures and steward queues.
xDM suits mid-sized and large organisations that want to start MDM with one domain and grow, prefer to host the hub themselves, and want business users involved in the design.
Tell us what the platform needs to do and when. We will propose a first phase with scope, team and an itemised quotation.