Skip to content

C.1.2. Business Case

Business rationale, justification and ROI of the EKG.

The capability Business Case (C.1.2) is part of the capability area Data Strategy in the Data Pillar.

Business rationale, justification and ROI of the EKG.

Warn

Work in progress

  • Do one or more data inventories exist
  • Is the inventory based on defined standards (for both meaning and format)
  • Is defined and in-scope data (both breadth and depth) covered in the inventories
  • Is the data inventory linked to sources of record (SORs) and authorized data distribution points
  • Is the inventory linked to the business meaning of the data and expressed using standards
  • Is the creation and maintenance of the data inventory mandated by policy and incorporated into the data strategy
  • Is the quality of the content in the inventory measured, reported to involved stakeholders, and used for process enhancement

Maturity Level 1

  • Sources, data sets, and metadata are onboarded and expressed as formal ontologies
  • Authoritative (upstream) data sources and (downstream) consumers are documented and verified by users, data, and technology
  • The inventory of applications is defined and selected for graph applications
  • Requirements and dependencies for each outbound data flow are documented and verified (implementation in the graph is not a requirement)
  • Business glossaries for in-scope use cases are defined and verified in the graph (including a list of data sources and datasets)
  • Policy implemented mandating inventory maintenance and only authorizing the use of data that has been logged into the inventory

Maturity Level 2

  • Use case tree(s) (UCTs) is/are defined, standardized, and implemented
  • All upstream data sources are linked to the authorized systems of record (SORs) and distribution points
  • Policy mandating the use of SORs and documentation of data flow is implemented
  • Entitlements have been defined in the graph (governing access to sources of data in the inventory)
  • Classifications (i.e. criticality, security, privacy) are aligned with the use case tree and captured in the knowledge graph
  • Governance requirements (i.e. use cases, accountability, data sources, data flows, service level agreements (SLAs)) are modeled and registered into the knowledge graph

Maturity Level 3

  • Data inventory is centralized in the graph and linked to governance for defined use cases
  • Ontologies and data models (including change history and transformations) are registered in the knowledge graph
  • Entitlements are calculated within the inventory and enforced at the datapoint level
  • Data Quality is automatically calculated (fine-grained with dynamic value resolution) within the inventory for each use case
  • Data retention rules are registered in the graph and automatically enforced
  • Full audit trail for all upstream and downstream data usage is registered in the graph
  • Data elements, calculation methods, and critical data elements (CDEs) are linked to individual regulatory requirements

Maturity Level 4

  • Connected inventory has been extended to include real-time (transactional) data
  • Inventory is extended to external suppliers and third parties along the supply chain
  • The inventory is fully integrated with machine learning (ML) to optimize data flow
  • The “value of data” is calculated and classified within the organizational inventory

Maturity Level 5

No further requirements.

Value

Warn

Work in progress. Explain how EKG contributes value and how this capability or capability- enables higher levels of maturity for the EKG (which in turn provides more value to the business)

Traditional Approach

Warn

Work in progress. Explain how things are done today in a non-EKG context

EKG Approach

Warn

Work in progress. Explain how the given Capability or Capability Area would look like in a mature EKG context.

Use Cases

Warn

Work in progress. List examples of use cases that contribute to this capability, making the link to use cases in the catalog at https://catalog.ekgf.org/use-case/..

Comments