In a centralized MDM style, all master data originates within MDM and may be synchronized downstream / throughout the enterprise. In such a scenario, operational oversight and data governance is of utmost importance to an organization. The MDM system must be able to accommodate varying complexities of data structures as well as business processes.
Data Model
As the centralized style deals primarily with the B2B use case, companies must be able to model B2B customers and suppliers as well as their respective of lines of businesses. As such, the centralized configuration includes Organization Customer, Supplier and Contact Person with line of business data containers. These data containers contain attribution that are specific to the lines of businesses the organization does business with.
Organization customers, Suppliers, Contact Persons, and line of business data containers are provided in the Base Configuration file.
Workspaces
The Approved workspace is utilized as part of the centralized onboarding story. Workspaces allow for distinguishing the final state of a new entity which denotes active and publishing status to surrounding applications.
For more information, refer to the Workspaces topic.
Attributes
Generic attribution for corresponding entity types is also provided in the configuration.
Workflows
As data origination / authorship resides within MDM, an onboarding mechanism must be present to allow all departments and personas that are part of the process a means to interact with the data and even collaborate with one another.
Organization Customer Onboarding Workflow
The Centralized configurations include an Organization Customer Onboarding Workflow that is designed for contribution by the following personas:
- Sales Manager
- Finance Specialist
- Logistics Specialist
- MDM Specialist
The workflow allows each persona to fulfill their respective customer onboarding and enrichment activities, while providing a means for intra-departmental collaboration.
Organization Customer Maintenance Workflow
The Organization Customer Maintenance workflow provides users with the means to maintain their customer data in a governed approach. Rather than allowing ad-hoc edits to customer data, all Web UI details screens are read-only outside of the maintenance workflow. This allows for all changes to be approved by an MDM Specialist role.
Supplier Onboarding Workflow
The Centralized configurations include a Supplier Onboarding Workflow that is designed for contribution by the following personas:
- Procurement Manager
- Finance Specialist
- Logistics Specialist
- MDM Specialist
The workflow allows each persona to fulfill their respective supplier onboarding and enrichment activities, while providing a means for intra-departmental collaboration.
Supplier Maintenance Workflow
The Supplier Maintenance workflow provides users with the means to maintain their supplier data in a governed approach. Rather than allowing ad-hoc edits to supplier data, all Web UI details screens are read-only outside of the maintenance workflow. This allows for all changes to be approved by an MDM Specialist role.
Contact Onboarding Workflow
The Contact Onboarding workflow provides users with the means to onboard new contact persons for their customers and/or suppliers. Each contact person record may be referenced to an existing customer or supplier record.
Contact Maintenance Workflow
The Contact Maintenance workflow provides users with the means to maintain their contact data in a governed approach. Rather than allowing ad-hoc edits to contact data, all Web UI details screens are read-only outside of the maintenance workflow. This allows for all changes to be approved by an MDM Specialist role.
User Privileges
The Centralized configurations provide distinct system user privileges for each user persona that interfaces with customer and supplier data. User privileges are important to governance and provides are tighter control in ensuring the right people deals with the right data.
User Privileges for Supplier MDM
Currently, the MDM Specialist may be considered as the super user of the Centralized MDM and has privileges to access, edit, and approve all data in the system, whereas Sales, Finance, and Logistics do not have permission to approve customer data.
When it comes to Supplier onboarding activities, the Procurement manager will initiate the onboarding of new supplier entities. The Procurement manager, along with other internal users such as Finance, and Logistics also has privileges to edit and enrich, whereas the MDM Specialist may access, edit, and approve the data.
Event Processor
The preconfigured event processor collects events for Organization Customer, Supplier, and Contact Person entities to run against their respective match algorithm.
Web UI
Organization Customer Onboarding Web UI
A Web UI configuration is provided which allows direct user interface to onboard, maintain, and approve customer data as it pertains to the company’s operational processes. In the Web UI, users from Sales, Finance, Logistics, Procurement, Merchandiser as well as MDM Specialist are able to carry out their day to day activities.
Supplier Onboarding Web UI
A Web UI configuration for Supplier Onboarding is provided which allows users to onboard, maintain, and approve supplier data. In the Web UI, users from Procurement, Finance, Logistics, and the MDM Specialist are able to collaborate with each other and interface with their supplier data.
The Web UI configuration also provides the means to create new contacts to be associated with supplier entities.
For more information on configuring a Web UI, refer to the Creating a New Web UI topic in the Web User Interfaces documentation.
Inbound Integration Endpoint
No inbound integration endpoint is provided with the Centralized Configuration.
Find Similar
A Find Similar algorithm is provided to support the Onboarding workflow user experience. This allows users to determine whether a given party they intend to onboard already exists in the system.
Component Models
The following component models are included in the Centralized Configuration file:
-
Matching, configured for:
-
Organization Customer
-
Supplier
-
Contact Person
-
-
Matching – Merge Golden Record, configured for:
-
Organization Customer
-
Supplier
-
Contact Person
-
For more information, refer to the Component Models topic in the System Setup documentation.