If your master data is being managed poorly, the road to business success will be far more difficult.
The more systems your organization operates, the more important it becomes to accurately manage master data. Multiple systems managing the same data entities without synchronization will leave you with outdated information, as well as a poor user experience for your employees, and perhaps more importantly, your customers.
With Ardoq you can document data ownership and usage, and plan your ‘to-be’ architecture. To document master data in Ardoq, we recommend one of two approaches; simple and fast using tags; or a more thorough method using a separate workspace and model.
Documenting master data using tags
This is the fastest way to register ownership and usage of master data. Systems owning data entities are tagged with the entity name, and systems using data entities are registered by tagging the references to the owning system. Tags are a good approach when master data ownership is not the primary focus of the workspace, but can be regarded as helpful extra information.
The primary way to gain oversight via tags is by using the ‘Tagscape’ view. Here, you can select the tags used for the master data entities. All components and relations with common tags will be grouped. You can also utilize the tags to filter other views, such as the component tree and table view.
This method can be limiting if your workspaces are large, or if you want to capture copies of master data or other specific aspects. For this reason we recommend using the more thorough method of documenting master data in a separate workspace.
Model-based master data documentation
We recommend using a dedicated workspace to model your master data in Ardoq. Below is a simple example with Customer and Product entities. The Customer entity specifies billing and delivery addresses explicitly since they are owned by different systems.
When modeling master data in a separate workspace, it is simple to refer from the master data workspace into those workspaces documenting the actual systems that own and use the data.
This gives a nice separation of concerns, where the master data workspace is only used to describe one thing, and uses a pre-defined model with standardized reference types. References going out of this workspace are governed by the workspace model. For this example, the relations going from the Master Data workspace specify whether a system owns, uses, updates or stores a copy of master data. By referencing from the master data workspace, you are able to keep your other documentation ‘cleaner’ and more concise.
Visualizing master data ownership and usage
The best view to get an overview of the master data is the ‘Dependency Map’. This allows you to visualize the information provided by the reference types in the master data model (ownership, usage, etc).