3 on December 10, 2025 and calls it the next stage of the portfolio. This page lists what to inventory, how the concepts map, the five steps, what to watch, and the offer.
| IBM InfoSphere MDM | Lima master data |
|---|---|
| Party and product domains | customer, business contact, supplier, material domains |
| Probabilistic matching | match rules with standardised attributes and two thresholds; a model for hard pairs |
| Composite view rules | survivorship per field |
| Hierarchies and groupings | versioned hierarchies |
| Entitlements | the twelve security layers |
| History tables | the audit trail, loaded with history |
| Web services | REST, SOAP (generated WSDL) and SQL |
A bank with InfoSphere MDM for party listed 42 web-service operations used by 11 consumers. The SOAP door in Lima published a WSDL with the same operations generated from the party domain; consumers moved one at a time behind a router, and the last one moved four months after the first. History loaded with linkage dates; the audit team accepted the ledger export.
They move behind a router one at a time: SOAP consumers get a generated WSDL, SQL readers get views with the same names, API consumers get REST with the same shapes.
Yes, read-only, for as long as your retention policy needs; its history is already searchable in Lima.
The inventory: the count of domains, sources, rules, hierarchies and consumers, written before the work starts.
Bring two systems that hold the same customers, suppliers or materials. In one working day we connect them, run the match on live rows, review the queue with your steward and publish the first golden view with its API.
