Table of Contents | ||
---|---|---|
|
Introduction
The Information domain in Orthogramic is the foundation for managing the data and knowledge that drive business decisions and operations. This domain provides a detailed view of how Information flows through the organization, supporting Capabilities, Value Streams, and strategic objectives. By integrating Information with real-time analytics and governance rules, Orthogramic ensures data accuracy, relevance, and accessibility. Explore how the Information domain helps your organization leverage data as a strategic asset to achieve business goals efficiently and effectively.
What is Information in Orthogramic?
...
In summary, Information in Orthogramic is not a static asset to be catalogued and stored, as it often is in BIZBOK, but a dynamic, integrated resource that drives business performance and strategic alignment. By embedding Information within the broader business architecture and linking it to other domains, Orthogramic transforms data from a passive resource into an active driver of organizational success. This modern approach enables organizations to maintain data relevance, anticipate changes, and make informed decisions faster than traditional, documentation-heavy methods. Orthogramic’s holistic, real-time, and predictive methodology empowers organizations to leverage Information not just for operational efficiency but for achieving long-term strategic goals.
Information domain modernized
To modernize the concept of information beyond the Information domain in BIZBOK, using an API from a data catalog like Atlan offers transformative possibilities. Data catalogs provide a comprehensive, metadata-driven platform for managing data across various ecosystems, which allows you to rethink how information is managed and leveraged within an enterprise.
Here’s how you could extend the traditional BIZBOK information domain using a data catalog:
Metadata-Driven information architecture
Traditional approach: BIZBOK’s Information domain often centers around mapping information concepts and entities relevant to the organization.
Modernized approach: With a data catalog’s API, you could introduce dynamic, metadata-driven architecture. This goes beyond static information mapping to real-time metadata management that integrates with various systems, offering up-to-date information governance.
Benefit: Enhances data discoverability, lineage tracking, and improves collaboration across data users (e.g., business analysts, data engineers).
Data Lineage and governance automation
Traditional approach: BIZBOK promotes understanding how information supports business processes through static mappings.
Modernized approach: A data catalog’s API could automate and visualize data lineage. This provides a comprehensive view of how data flows across the enterprise, who uses it, and for what purposes—offering richer insights into the lifecycle and integrity of data.
Benefit: Data lineage can empower decision-makers to ensure regulatory compliance and data quality in real time.
AI-Enhanced information discovery
Traditional approach: In BIZBOK, information discovery is often a manual process involving stakeholders identifying key information entities and relationships.
Modernized approach: Leverage AI/ML models within a data catalog to automate the discovery of data relationships, anomalies, and patterns across datasets. This helps enrich the context around data assets, making them more actionable and valuable to business architecture activities.
Benefit: AI-enhanced discovery helps with faster insights and makes business architecture more agile by providing actionable, context-aware information.
Collaborative data and information stewardship
Traditional approach: BIZBOK views information management in siloed roles like Data Architects or Business Analysts.
Modernized approach: Atlan allows for collaborative data stewardship by involving multiple stakeholders, using data democratically across the organization. Data cataloging, enriched through user-generated insights, ensures a collaborative platform where everyone contributes to and benefits from information transparency.
Benefit: Breaking silos and encouraging a cross-functional approach ensures that business decisions are made with comprehensive information.
Real-Time analytics and KPIs
Traditional approach: BIZBOK’s Information domain often relies on static KPIs derived from past data.
Modernized approach: Integrating Atlan with other real-time analytics platforms allows you to monitor live KPIs and dashboards. This provides immediate insights into the performance of various processes and supports more dynamic decision-making.
Benefit: You can adapt strategies and operations in real-time, improving agility and performance outcomes.
Automated data governance policies
Traditional approach: Governance policies within the BIZBOK Information domain are often manually implemented and updated.
Modernized approach: Using a data catalog's API, you could automate data governance policies, applying them across different data sources and ensuring continuous compliance with regulatory frameworks.
Benefit: This approach minimizes manual overhead while ensuring governance standards are met efficiently.
Data as a Service (DaaS)
Traditional approach: BIZBOK’s Information domain looks at information as a support function for business processes.
Modernized approach: By leveraging Atlan’s API, you could promote Data as a Service (DaaS), enabling business users to access curated datasets and insights on demand. This shifts the focus of information from being a static asset to an actionable service.
Benefit: Information becomes more valuable and accessible across the organization, supporting a range of business architecture and strategy needs.
By integrating Atlan’s advanced capabilities into your enterprise architecture, you can transcend BIZBOK's static concept of the Information domain, creating a more dynamic, automated, and collaborative environment for managing and utilizing information across your business.
Information details
Each Information detail page describes the structure and flow of information within the organization, including data models and information flow diagrams. This ensures that information management supports strategic decision-making and operational efficiency. It is reached from Business Architecture > Information.
...
Info |
---|
Relationship of Domain, Attributes, Elements and Sub-ElementsTo understand the Relationship of Domain, Attributes, Elements and Sub-Elements, see: https://orthogramic.atlassian.net/wiki/spaces/OUG/pages/55246856/Business+Architecture+Domain+Attributes+Elements#The-relationships-between-Business-Architecture-Domains%2C-Attributes%2C-Elements-and-Sub-Elements |
Information attributes
Domain | Attribute | Description | Example |
Information | Title | The name or title of the information management element. | Data Dictionary |
Information | Description | A detailed explanation of what the information management element entails. | Definitions and descriptions of data elements used within the organization. |
Information | Purpose | The intended purpose or function of the information management element within the organization. | To ensure consistent understanding and use of data elements. |
Information | Owner | The individual or team responsible for the information management element. | Data Management Team |
Information | Organizational Unit | The organizational unit(s) to which the information management element is linked. | IT Department |
Information | Inputs | The resources, information, or materials required for the information management element. | Data definitions, metadata |
Information | Outputs | The deliverables or results produced by the information management element. | Data dictionary entries |
Information | Processes | The set of processes that define how the information management element operates. | Data collection, data definition |
Information | Performance Indicators | Metrics used to measure the effectiveness and efficiency of the information management element. | Accuracy of data definitions, frequency of updates |
Information | Dependencies | Other elements, processes, or systems that the information management element depends on. | Database management system, metadata repository |
Information | Related Information Elements | Information elements that are related or linked to this element. | Data models, information flow diagrams |
Information | Maturity Level | The current maturity level of the information management element. | Level 3 - Defined |
Information | Tools and Technologies | Tools and technologies used to support or enable the information management element. | Metadata management tools, data catalog software |
Information | Compliance and Standards | Regulatory requirements and standards the information management element must adhere to. | ISO 8000, industry-specific standards |
Information | Cost | The financial cost associated with implementing and maintaining the information management element. | Annual budget of $100,000 |
Information | Risks | Potential risks associated with the information management element and its operations. | Inconsistent data definitions, outdated information |
Information | Improvement Opportunities | Areas where the information management element can be enhanced or improved. | Automated data dictionary updates, enhanced data governance |
Information | Strategic Alignment | How the information management element aligns with the organization's strategic goals and objectives. | Supports the strategic goal of improving data quality |
Information | Information Component | A piece of data or information used within the organization to support various processes and decision-making. | Customer Data includes personal details, purchase history, and preferences. |
Information | Parent | A high-level policy that provides overarching principles or rules guiding business operations. It covers multiple sub-policies. | Customer Management |
Information | Child | A specific policy that falls under a broader parent policy. It provides detailed rules and guidelines for a specific aspect of business operations. | Customer Onboarding |
Information Element
Elements | Sub-Element | Description | Example |
Information Element | Title | The name or title of the information component. | Customer Data |
Information Element | Description | A detailed explanation of the information component. | Information related to customers including personal details, purchase history, and preferences. |
Information Element | Purpose | The intended use or function of the information component. | To personalize customer interactions and improve service quality. |
Information Element | Owner | The individual or team responsible for managing the information. | Data Management Team |
Information Element | Organizational Unit | The organizational unit(s) using the information component. | Sales and Marketing, Customer Service |
Information Element | Data Sources | The sources from which the information is collected. | CRM System, Online Forms |
Information Element | Data Quality | The quality measures and standards for the information component. | Accuracy, Completeness, Consistency |
Information Element | Security | The security measures applied to protect the information. | Encryption, Access Controls |