GUNs
GUNs helps enterprises turn scattered data into assets with clear meaning, accountable teams, consistent standards and dependable delivery. It connects governance responsibilities, business modeling, data collection and dataset publication, with AI agents assisting with analysis and annotation.
Six functional modules
| Module | What you can do |
|---|---|
| Operating Model | Choose centralized or federated governance and define the responsibilities and working scope of central and domain teams |
| Data Architecture | Describe enterprise information through subjects, business objects and logical models, and connect them to physical tables and fields |
| Application Architecture | Manage the application portfolio and understand which systems, modules, services and integrations support business and handle data |
| Standards | Align definitions, controlled values, business measures, classification and masking requirements |
| Projects | Connect sources, collect metadata, perform manual and AI-assisted annotation, and track governance progress |
| Datasets | Organize data for delivery, publish commitments through ports and contracts, and manage versions, implementations and dependencies |
The modules work together through shared references. A single Supplier business object, for example, can connect enterprise standards, physical tables in several applications, and supplier datasets offered to other teams.
From responsibility to information and delivery
| Concept | Question it answers | Example |
|---|---|---|
| Business domain | What business does the enterprise conduct? | Supplier Management, Sourcing and Procurement |
| Responsibility domain | Who is accountable for this area of data? | Supply Chain Data Domain |
| Subject domain | What kind of information is it? | Parties and Organizations → Supplier Information |
| Business object | What specific thing is described and governed? | Supplier, Supplier Qualification |
| Governance project | Where does this governance work happen? | Supplier Data Review Project |
| Dataset | What collection of data is offered to consumers over time? | Supplier 360 Dataset |
Subjects help people discover and understand information, responsibility domains establish accountability, projects organize work, and datasets support ongoing delivery. One project can build several datasets, and one dataset can reference tables from several sources.
Govern in a way that fits your organization
Centralized governance places enterprise definitions, standards and governance work with central teams. Federated governance combines common rules maintained centrally with domain teams maintaining their own data and governance outputs.
The active operating model and selected work identity determine the maintenance actions and content available to a user. People with several organizational appointments can switch identities to work within the appropriate responsibility.
A supplier data example
- Assign responsibilities: choose an operating model; in Federated mode, establish a supply chain responsibility domain and assign its operating teams.
- Describe the information: define Supplier and Supplier Qualification under Supplier Information, including their business boundaries.
- Connect applications: register ERP and SRM to identify data origins and business use.
- Align standards: maintain a company-registration data element, supplier-grade code table and related business terms.
- Govern the data: collect table and column structures, add business names, definitions, classification and standards, and review AI suggestions.
- Publish a dataset: define supplier output ports and contracts, associate implementations in each environment, and publish a version for downstream consumers.
AI assistance and continuous operation
AI agents use enterprise knowledge, data dictionaries and existing governance information to help interpret tables and columns, draft descriptions and recommend annotations. Users review and adjust suggestions or maintain annotations directly.
Project activity, change history, dataset versions and implementation checks help teams track completed work, identify changes and understand which consumers may be affected.