Product ownership resolution — before and after

Product ownership resolution — before and after An architecture diagram generated by Archify. Customer · Enters BU identifier · BEFORE · CUSTOMER-AUTHORED MAPPING Customer Enters BU identifier Manual product linking · 3–12 customer steps · BEFORE · CUSTOMER-AUTHORED MAPPING · customer performs resolution Manual product linking 3–12 customer steps customer performs resolution BU Mapping table · CIAM ID → product identifiers · BEFORE · CUSTOMER-AUTHORED MAPPING · stale and unaudited BU Mapping table CIAM ID → product identifiers stale and unaudited Portal navigation · Products to display · BEFORE · CUSTOMER-AUTHORED MAPPING · mapping is load-bearing Portal navigation Products to display mapping is load-bearing BU system of record · Enrols, opens or terminates · AFTER · BU FACT, MDM AS RELATIONSHIP REGISTRY · authority for product fact only BU system of record Enrols, opens or terminates authority for product fact only Product relationship fact · BU IDs + start/end · AFTER · BU FACT, MDM AS RELATIONSHIP REGISTRY · requires binding evidence Product relationship fact BU IDs + start/end requires binding evidence Informatica MDM · rel_id + accepted product links · AFTER · BU FACT, MDM AS RELATIONSHIP REGISTRY · relationship registry · ADR-0006 Informatica MDM rel_id + accepted product links relationship registry · ADR-0006 D3 customer profile · Projected links for channels · AFTER · BU FACT, MDM AS RELATIONSHIP REGISTRY · serves reads · no MDM on login D3 customer profile Projected links for channels serves reads · no MDM on login Ambiguous / legacy records · Back book records · AFTER · BU FACT, MDM AS RELATIONSHIP REGISTRY · back-book resolution Ambiguous / legacy records Back book records back-book resolution Types product identifier Creates mapping Decides what appears Asserts product fact Binding evidence Projects accepted link Match and merge BEFORE · CUSTOMER-AUTHORED MAPPING AFTER · BU FACT, MDM AS RELATIONSHIP REGISTRY Legend Frontend Backend Database Message bus External

Before · one record does two jobs

  • • The customer performs identity resolution by hand
  • • A stale mapping can remain after the relationship ends

After · one registry

  • • The BU authors the product relationship against local identifiers
  • • MDM accepts it, links it to rel_id and masters the relationship

Authority boundary · decided

  • • MDM issues rel_id and holds accepted links (ADR-0006)
  • • Whether the installed MDM meets the SLAs is open question 51