Governata lets you define an unlimited number of master data types, design a data model for each one, relate types to one another, and apply governance and quality rules across them.
Unlimited types
A data model per type
Attributes and relationships
Governance and quality rules
With no shared definition, each system stores whatever it considers important, so fields and meanings drift apart.
A sound definition comes before any matching or consolidation, because it establishes what you are trying to unify in the first place.
Defining any number of master data types to suit the nature of your business.
Designing a data model specific to each type, so different entities are not forced into one template.
Defining the attributes of each type and the fields that represent it, consistently across systems.
Defining relationships between types, such as a customer to a contract or a product to inventory.
Tying each type to the governance rules that control how its records are created, changed, and approved.
Tying each type to quality rules that govern the accuracy and completeness of its data.
Determining the master data type to define, based on the nature of your business.
Designing the data model for that type and setting its attributes and representative fields.
Linking the type to the other types it relates to across your organization.
Tying the type to the governance and quality rules that will govern its data.
A single reference for what the organization treats as master data, so consolidation efforts start from an agreed foundation.
A clear scope of the types they own, with documented attributes and relationships that do not shift with the system.
A predefined data model to build integration against, instead of inferring one from each system separately.
Governance and quality rules attached to the type itself, so they apply to everything belonging to it.
Core customer data that sales, service, and collections all depend on.
Supplier data tied to procurement, contracts, and payments.
Employee data shared between human resources, payroll, and access management.
Product data and attributes used in sales, inventory, and reporting.
It is the core, relatively stable data representing the principal entities in an organization, such as customers, employees, suppliers, and products, used across multiple systems and applications.
Master data describes the entity itself and changes slowly. Transactional data records what happens to that entity, such as an order or an invoice, and changes constantly.
Because consolidation requires knowing first what entity you are consolidating and what its attributes are. Without a definition, matching becomes a comparison of fields whose meaning is unknown.
It is the shape in which the entity is defined: which attributes it holds, which fields represent it, and how those relate to one another. Each type has a model suited to its nature.
Because entities do not exist in isolation. A customer relates to a contract, a product relates to inventory. Documenting those relationships is what makes the data meaningful in context.
A quality rule needs a reference to measure against. The definition is that reference, and without it no rule can establish what the correct value even is.
Types you define, with documented data models, attributes, and relationships, and governance and quality rules that apply across all of them.