1. 1 MDM procedures modeling - Master Data Management – Creative Commons – Author Pierre Bonnet – Orchestra NetworksVersion August 12, 2008 Version August 12, 2009 AUTHOR - Pierre Bonnet - Orchestra Networks pierre.bonnet@orchestranetworks.com How to model the “Address” Business Object when using a Model-driven MDM ? Case study MDM modeling Master Data Management

2. 2 MDM procedures modeling - Master Data Management – Creative Commons – Author Pierre Bonnet – Orchestra NetworksVersion August 12, 2008 Condition of use You can use this document and prebuilt data models for your own needs and publications under the condition to quote the source (author credit): ‘MDM Alliance Group – pierre.bonnet@orchestranetworks.com’ This document and prebuilt data models are protected by a Creative Commons (see opposite figure) This document is free download from the MAG’ website: http://www.mdmalliancegroup.com/ MAG stands for MDM Alliance Group

3. 3 MDM procedures modeling - Master Data Management – Creative Commons – Author Pierre Bonnet – Orchestra NetworksVersion August 12, 2008 Preamble This presentation is free download from the MAG’s web site MAG stands for MDM Alliance Group http://www.sustainableitarchitecture.com/mdm_alliance You can use this presentation for internal training but also for commercial training If you want to attain MAG certification for your commercial training please contact us directly in order to obtain information about conditions and criteria We will be pleased to help newcomers to the MAG who are interested in developing courses to augment and enhance the MAG Modeling procedures When you use these slides please don’t forget to quote the source MDM Alliance Group, pierre.bonnet@orchestranetworks.com

4. 4 MDM procedures modeling - Master Data Management – Creative Commons – Author Pierre Bonnet – Orchestra NetworksVersion August 12, 2008 What are the objectives? Modeling the “Address” Business Object in an universal way Respecting several formats of postcode depending on countries Enforcing data referential integrity constraints Using the standard UML notation Using this data model to manage a Master Data Referential (MDM) This is not a flat data model Flat data model?

5. 5 MDM procedures modeling - Master Data Management – Creative Commons – Author Pierre Bonnet – Orchestra NetworksVersion August 12, 2008 Flat data model is not the target This data modeling of Addresses (opposite figure, source OASIS) is not in accordance with MDM needs Data referential integrity constraints are not well represented => duplication of some data (CityName, Department, Region…) This is a data model for managing data flows between systems (EAI, ESB) not for tackling data quality issues such as referential integrity constraints

6. 6 MDM procedures modeling - Master Data Management – Creative Commons – Author Pierre Bonnet – Orchestra NetworksVersion August 12, 2008 Agenda of this presentation Static data modeling Data Enterprise Architecture Data Model Dynamic data modeling State machine Decision table User Interface of the MDM Excerpt of the XML Schema data model Findings

7. 7 MDM procedures modeling - Master Data Management – Creative Commons – Author Pierre Bonnet – Orchestra NetworksVersion August 12, 2008 Static modeling

8. 8 MDM procedures modeling - Master Data Management – Creative Commons – Author Pierre Bonnet – Orchestra NetworksVersion August 12, 2008 Data Enterprise Architecture The Business Object Address is designed in the Geography Data Category A Data Category is a plug and play concept, highly reusable as an autonomous building block Therefore nested data types are forbidden beyond boundaries of Data Categories -> FK are used instead Domain of Business Object

9. 9 MDM procedures modeling - Master Data Management – Creative Commons – Author Pierre Bonnet – Orchestra NetworksVersion August 12, 2008 Object and its hierarchy Address is linked with this object The detail of this hierarchy is available from the MAG website

10. 10 MDM procedures modeling - Master Data Management – Creative Commons – Author Pierre Bonnet – Orchestra NetworksVersion August 12, 2008 Business object Address – The core Each Address is related to an Object and a Period of time through a Site (associative class) A Site allows for defining Address but also Coordinate System Code such as GPS, Galileo, etc. Additional information

11. 11 MDM procedures modeling - Master Data Management – Creative Commons – Author Pierre Bonnet – Orchestra NetworksVersion August 12, 2008 Business object Address – The core A single Address may have several expressions in different languages including further electronic expressions The location nature (qualifier attribute) details the utilization of the Address mailing address, internal postcode, forwarding address, delivery address, billing address, home address, etc. Each Address is linked with a City to compute the postal code (1) (see later) (1) ‘postal code’ is also known as ‘post code’ or ‘postcode’ (similar terms)

12. 12 MDM procedures modeling - Master Data Management – Creative Commons – Author Pierre Bonnet – Orchestra NetworksVersion August 12, 2008 Mailing issues Geographical issues More information shoud be given to distinguish geographical issues and mailing issues Data Categories are not represented at this level of modeling (core business) This is a semantic data model, not yet a physical representation with SQL Tables Mailing issues

13. 13 MDM procedures modeling - Master Data Management – Creative Commons – Author Pierre Bonnet – Orchestra NetworksVersion August 12, 2008 Business object Address – The core Territory Office In France the Territory Office is composed of 3 digits. For instance the city Orléans has two different Postal Offices ‘000’ for the North and ‘100’ for the South of Orléans. The complete post code is obtained by prefixing these codes with the Territory Code. In France the Territory Code is either a Department or a District (arrondissement). In the case of Orléans, this is the Departement (45) : ‘45000’ Orléans North and ‘45100’ Orléans South In US the Territory Office is composed with 2 digits In UK it is composed with the concatenation of “Postal Zone”, “District Zone”, “Sector” and “Unity”. The reflexive association “divides in” on the Territory Office allows for declaring this type of composition Territory Office Type Depends on the Country France: Postal Code US: Postal Zone UK: Postal Zone + District Zone + Sector & Unity Territory Type Depends on the Country. It represents the administrative organization of areas regardless of mailing issues France (Département, Région), US (State, County), etc.

14. 14 MDM procedures modeling - Master Data Management – Creative Commons – Author Pierre Bonnet – Orchestra NetworksVersion August 12, 2008 Examples Territory Office & Territory Address ExampleTerritory OfficeTerritory FRANCE: 69130 13069 (département) US: 90001(Los Angeles) 01 (group of delivery addresses) 900 (region) UK: M1 1AA Many Territory Office are used M (postal code), 1 (postal district), 1 (sector), AA (unity) void

15. 15 MDM procedures modeling - Master Data Management – Creative Commons – Author Pierre Bonnet – Orchestra NetworksVersion August 12, 2008 Business object Address – The core Post Code It is an associative class between City and Territory Office ‘/postal code’ attribute (post code) is a derivated attribute The automactic computation of the post code is done by getting and using Territory Office and Territory in compliance with the rules that are declared in ‘Postal Code Pattern’ Class attached to the country In some countries, for instance in UK, the postal code is computed with help from the Territory Office only (Postal Zone + Postal District + Sector + Unity). Therefore, in order to determine if the Territory Code is used or not, the attribute ‘territory code depth’ of the pattern is initialized to zero Association ‘manages’ between City and Territory This association is used when the computation of the postal code must use a special Territory, different from the one given by the geographical organization of the area For example in France, the city Laveyrune is located in the Territory Ardèche (07) whereas its postal code used the Territory Lozère (48). Then, the postcode of Laveyrune is 48250 even though its geogaphical territory is 07

16. 16 MDM procedures modeling - Master Data Management – Creative Commons – Author Pierre Bonnet – Orchestra NetworksVersion August 12, 2008 Business object Address – The core Post Code Pattern This class allows for defining the syntax of the post code depending on each country: Length of the Territory Office code  France (3), USA (2), Belguim (2), etc. Length of the post code  France (5), USA (5), Belguim (4), etc. In some countries (UK for instance) many patterns can exist An extension of the current version of the model should be suggested to tackle this rule. Only the many to many association is set up for the moment The ‘territory code depth’ and ‘territory office code depth’ provide the level of use when computing the postcode territory code depth = 0 for UK => territory code not used territory office code depth = 4 for UK => nesting of Unity, Sector, Postal District and Postal code

17. 17 MDM procedures modeling - Master Data Management – Creative Commons – Author Pierre Bonnet – Orchestra NetworksVersion August 12, 2008 Link between Address and City Address Nature: Street, Road, Lane, Way, Building plot, etc. Address Code: Bis, Quinte, Quarter, Ter, etc. Special Code For example in France it corresponds to the Cedex, in US it is the ‘ZIP+4’ code It is not mandatory and is added to the Address at the end

18. 18 MDM procedures modeling - Master Data Management – Creative Commons – Author Pierre Bonnet – Orchestra NetworksVersion August 12, 2008 Dynamic modeling

19. 19 MDM procedures modeling - Master Data Management – Creative Commons – Author Pierre Bonnet – Orchestra NetworksVersion August 12, 2008 Address’s lifecycle – State machine

20. 20 MDM procedures modeling - Master Data Management – Creative Commons – Author Pierre Bonnet – Orchestra NetworksVersion August 12, 2008 Address’s lifecycle – State machine Example: when the Address’s state is ‘To be checked’ It is possible to launch a check operation to evaluate the quality level of this address (transition check/check()) Then the new state becomes either ‘Valid’, ‘To be completed’ or ‘Return to sender (RTS – this is a super state including Undeliverable, Insufficient Address or No such number) Stemming from the transitions of the state machine These are Extended business operations

21. 21 MDM procedures modeling - Master Data Management – Creative Commons – Author Pierre Bonnet – Orchestra NetworksVersion August 12, 2008 Decision table The state machine is translated as a decision table Business permissions are defined by state CRUD depends on states This table is a reference/master data therefore It is managed by the MDM (not in the form of an Excel sheet) and benefits from version management, feeding by contexs (ex: different initialization by contexts subsidiaries, countries, etc.)

22. 22 MDM procedures modeling - Master Data Management – Creative Commons – Author Pierre Bonnet – Orchestra NetworksVersion August 12, 2008 MDM User Interface The next slides show the UI to manage Addresses through the Master Data Management tool These screens are automatically obtained by generating UI from the data model With help from a Model-driven MDM tool (here EBX.Platform from Orchestra Networks) Therefore zero hard-coded software development is required Further ergonomic customizations are feasible depending on needs

23. 23 MDM procedures modeling - Master Data Management – Creative Commons – Author Pierre Bonnet – Orchestra NetworksVersion August 12, 2008 MDM User Interface Postal Code Pattern = 0 means not used to compute the post code French Address English Address

24. 24 MDM procedures modeling - Master Data Management – Creative Commons – Author Pierre Bonnet – Orchestra NetworksVersion August 12, 2008 MDM User Interface Country and link to the Postal Code Pattern French Address Types of Territory Office for France

25. 25 MDM procedures modeling - Master Data Management – Creative Commons – Author Pierre Bonnet – Orchestra NetworksVersion August 12, 2008 MDM User Interface Country and link to the Postal Code Pattern English Address Types of Territory Office for UK

26. 26 MDM procedures modeling - Master Data Management – Creative Commons – Author Pierre Bonnet – Orchestra NetworksVersion August 12, 2008 MDM User Interface Automatic computation of the post code French Address English Address Reminder: postalcode is a derivated attribute located in the associative class Postal Code (between Territory Office and City)

27. 27 MDM procedures modeling - Master Data Management – Creative Commons – Author Pierre Bonnet – Orchestra NetworksVersion August 12, 2008 MDM User Interface Keying a French Address A filter by country could be useful

28. 28 MDM procedures modeling - Master Data Management – Creative Commons – Author Pierre Bonnet – Orchestra NetworksVersion August 12, 2008 MDM User Interface Keying an English Address

29. 29 MDM procedures modeling - Master Data Management – Creative Commons – Author Pierre Bonnet – Orchestra NetworksVersion August 12, 2008 XML Schema excerpt See next slide

30. 30 MDM procedures modeling - Master Data Management – Creative Commons – Author Pierre Bonnet – Orchestra NetworksVersion August 12, 2008 FK to City Rule used to compute the post code with the City and the Territory Office to This XML Schema is generated automatically by the Model-driven MDM - Orchestra networks

31. 31 MDM procedures modeling - Master Data Management – Creative Commons – Author Pierre Bonnet – Orchestra NetworksVersion August 12, 2008 3 tips when modeling a Business Object #1 Staging this Business Object within your Data Enterprise Architecture (see example slide 8) #2 Modeling the static part without any data duplication #3 Modeling the dynamic part (state machine) to enforce referential integrity constraints

32. 32 MDM procedures modeling - Master Data Management – Creative Commons – Author Pierre Bonnet – Orchestra NetworksVersion August 12, 2008 What are the findings? Flat data model is not sufficient for tackling data quality and deploying MDM Due to data duplication and lack of data referential integrity constraints management Therefore existing data models that are built to manage data flows are not well-positionned to implement MDM MDM needs a complete data modeling relying on a strong management of data referential integrity avoiding data duplication Moreover the static data model must be completed with a dynamic data model to identify and manage constraints related to the evolving of business objects’ states UI and services to manage master data are generated automatically when using a Model-driven MDM tool Obviously this approach requires a complete and rich data model as shown in this presentation

33. 33 MDM procedures modeling - Master Data Management – Creative Commons – Author Pierre Bonnet – Orchestra NetworksVersion August 12, 2008 MDM Modeling procedures Guide The MDM method Guide is free download A community to share MDM Modeling procedures and prebuilt data models MDM Alliance Group (MAG) http://www.mdmalliancegroup.com/ End

34. 34 MDM procedures modeling - Master Data Management – Creative Commons – Author Pierre Bonnet – Orchestra NetworksVersion August 12, 2008 Thanks Contact The Author - Pierre Bonnet Consultant Manager Orchestra Networks pierre.bonnet@orchestranetworks.com 06 75 01 54 54 (Paris, France) End