├── .editorconfig ├── .github ├── dependabot.yml ├── labeler.yml └── workflows │ ├── docs.yml │ └── label.yml ├── .gitignore ├── .idea ├── misc.xml └── vcs.xml ├── .tool-versions ├── .vscode ├── settings.json └── tasks.json ├── CNAME ├── LICENSE ├── Makefile ├── Pipfile ├── README.md ├── VERSION ├── abbreviations.md ├── convert-latex-markdown.sh ├── customer-assets └── ekgf │ └── quadrants.jpg ├── docs-fragments ├── pillar │ ├── business │ │ ├── .gitignore │ │ ├── background-and-intro.md │ │ ├── business-enablers │ │ │ ├── capability-map │ │ │ │ ├── background-and-intro.md │ │ │ │ ├── dimensions.md │ │ │ │ ├── ekg-approach.md │ │ │ │ ├── levels.md │ │ │ │ ├── traditional-approach.md │ │ │ │ ├── use-cases.md │ │ │ │ └── value.md │ │ │ ├── operating-model │ │ │ │ ├── background-and-intro.md │ │ │ │ ├── dimensions.md │ │ │ │ ├── ekg-approach.md │ │ │ │ ├── levels.md │ │ │ │ ├── traditional-approach.md │ │ │ │ ├── use-cases.md │ │ │ │ └── value.md │ │ │ ├── performance-management │ │ │ │ ├── background-and-intro.md │ │ │ │ ├── dimensions.md │ │ │ │ ├── ekg-approach.md │ │ │ │ ├── levels.md │ │ │ │ ├── traditional-approach.md │ │ │ │ ├── use-cases.md │ │ │ │ └── value.md │ │ │ ├── risk-management │ │ │ │ ├── background-and-intro.md │ │ │ │ ├── dimensions.md │ │ │ │ ├── ekg-approach.md │ │ │ │ ├── levels.md │ │ │ │ ├── traditional-approach.md │ │ │ │ ├── use-cases.md │ │ │ │ └── value.md │ │ │ ├── scalability-assessment │ │ │ │ ├── background-and-intro.md │ │ │ │ ├── dimensions.md │ │ │ │ ├── ekg-approach.md │ │ │ │ ├── levels.md │ │ │ │ ├── traditional-approach.md │ │ │ │ ├── use-cases.md │ │ │ │ └── value.md │ │ │ └── supply-chain-management │ │ │ │ ├── background-and-intro.md │ │ │ │ ├── dimensions.md │ │ │ │ ├── ekg-approach.md │ │ │ │ ├── levels.md │ │ │ │ ├── traditional-approach.md │ │ │ │ ├── use-cases.md │ │ │ │ └── value.md │ │ ├── business-model-elaboration │ │ │ ├── change-management │ │ │ │ ├── background-and-intro.md │ │ │ │ ├── dimensions.md │ │ │ │ ├── ekg-approach.md │ │ │ │ ├── levels.md │ │ │ │ ├── traditional-approach.md │ │ │ │ ├── use-cases.md │ │ │ │ └── value.md │ │ │ ├── market-segmentation │ │ │ │ ├── background-and-intro.md │ │ │ │ ├── dimensions.md │ │ │ │ ├── ekg-approach.md │ │ │ │ ├── levels.md │ │ │ │ ├── traditional-approach.md │ │ │ │ ├── use-cases.md │ │ │ │ └── value.md │ │ │ └── value-chain │ │ │ │ ├── background-and-intro.md │ │ │ │ ├── dimensions.md │ │ │ │ ├── ekg-approach.md │ │ │ │ ├── levels.md │ │ │ │ ├── traditional-approach.md │ │ │ │ ├── use-cases.md │ │ │ │ └── value.md │ │ └── strategy-actuation │ │ │ ├── business-goals │ │ │ ├── background-and-intro.md │ │ │ ├── dimensions.md │ │ │ ├── ekg-approach.md │ │ │ ├── levels.md │ │ │ ├── traditional-approach.md │ │ │ ├── use-cases.md │ │ │ └── value.md │ │ │ ├── business-tactics │ │ │ ├── background-and-intro.md │ │ │ ├── dimensions.md │ │ │ ├── ekg-approach.md │ │ │ ├── levels.md │ │ │ ├── traditional-approach.md │ │ │ ├── use-cases.md │ │ │ └── value.md │ │ │ └── business-vision │ │ │ ├── background-and-intro.md │ │ │ ├── dimensions.md │ │ │ ├── ekg-approach.md │ │ │ ├── levels.md │ │ │ ├── traditional-approach.md │ │ │ ├── use-cases.md │ │ │ └── value.md │ ├── data │ │ ├── .gitignore │ │ ├── background-and-intro.md │ │ ├── data-architecture │ │ │ ├── business-vocabularies │ │ │ │ ├── background-and-intro.md │ │ │ │ ├── dimensions.md │ │ │ │ ├── ekg-approach.md │ │ │ │ ├── levels.md │ │ │ │ ├── traditional-approach.md │ │ │ │ ├── use-cases.md │ │ │ │ └── value.md │ │ │ ├── data-integration │ │ │ │ ├── background-and-intro.md │ │ │ │ ├── dimensions.md │ │ │ │ ├── ekg-approach.md │ │ │ │ ├── levels.md │ │ │ │ ├── traditional-approach.md │ │ │ │ ├── use-cases.md │ │ │ │ └── value.md │ │ │ ├── datasets │ │ │ │ ├── background-and-intro.md │ │ │ │ ├── dimensions.md │ │ │ │ ├── ekg-approach.md │ │ │ │ ├── levels.md │ │ │ │ ├── traditional-approach.md │ │ │ │ ├── use-cases.md │ │ │ │ └── value.md │ │ │ └── ontologies │ │ │ │ ├── background-and-intro.md │ │ │ │ ├── dimensions.md │ │ │ │ ├── ekg-approach.md │ │ │ │ ├── levels.md │ │ │ │ ├── traditional-approach.md │ │ │ │ ├── use-cases.md │ │ │ │ └── value.md │ │ ├── data-governance │ │ │ ├── classification-management │ │ │ │ ├── background-and-intro.md │ │ │ │ ├── dimensions.md │ │ │ │ ├── ekg-approach.md │ │ │ │ ├── levels.md │ │ │ │ ├── traditional-approach.md │ │ │ │ ├── use-cases.md │ │ │ │ └── value.md │ │ │ ├── data-management-policy │ │ │ │ ├── background-and-intro.md │ │ │ │ ├── dimensions.md │ │ │ │ ├── ekg-approach.md │ │ │ │ ├── levels.md │ │ │ │ ├── traditional-approach.md │ │ │ │ ├── use-cases.md │ │ │ │ └── value.md │ │ │ ├── operating-model │ │ │ │ ├── background-and-intro.md │ │ │ │ ├── dimensions.md │ │ │ │ ├── ekg-approach.md │ │ │ │ ├── levels.md │ │ │ │ ├── traditional-approach.md │ │ │ │ ├── use-cases.md │ │ │ │ └── value.md │ │ │ └── risk-and-control-framework │ │ │ │ ├── background-and-intro.md │ │ │ │ ├── dimensions.md │ │ │ │ ├── ekg-approach.md │ │ │ │ ├── levels.md │ │ │ │ ├── traditional-approach.md │ │ │ │ ├── use-cases.md │ │ │ │ └── value.md │ │ ├── data-quality │ │ │ └── business-rules │ │ │ │ ├── background-and-intro.md │ │ │ │ ├── dimensions.md │ │ │ │ ├── ekg-approach.md │ │ │ │ ├── levels.md │ │ │ │ ├── traditional-approach.md │ │ │ │ ├── use-cases.md │ │ │ │ └── value.md │ │ └── data-strategy │ │ │ ├── business-case │ │ │ ├── background-and-intro.md │ │ │ ├── dimensions.md │ │ │ ├── ekg-approach.md │ │ │ ├── levels.md │ │ │ ├── traditional-approach.md │ │ │ ├── use-cases.md │ │ │ └── value.md │ │ │ └── goals-and-objectives │ │ │ ├── background-and-intro.md │ │ │ ├── dimensions.md │ │ │ ├── ekg-approach.md │ │ │ ├── levels.md │ │ │ ├── traditional-approach.md │ │ │ ├── use-cases.md │ │ │ └── value.md │ ├── organization │ │ ├── .gitignore │ │ ├── background-and-intro.md │ │ ├── delivery-management │ │ │ ├── data-movement │ │ │ │ ├── background-and-intro.md │ │ │ │ ├── dimensions.md │ │ │ │ ├── ekg-approach.md │ │ │ │ ├── levels.md │ │ │ │ ├── traditional-approach.md │ │ │ │ ├── use-cases.md │ │ │ │ └── value.md │ │ │ ├── dataops-process │ │ │ │ ├── background-and-intro.md │ │ │ │ ├── dimensions.md │ │ │ │ ├── ekg-approach.md │ │ │ │ ├── levels.md │ │ │ │ ├── traditional-approach.md │ │ │ │ ├── use-cases.md │ │ │ │ └── value.md │ │ │ ├── ekg-platform-team │ │ │ │ ├── background-and-intro.md │ │ │ │ ├── dimensions.md │ │ │ │ ├── ekg-approach.md │ │ │ │ ├── levels.md │ │ │ │ ├── traditional-approach.md │ │ │ │ ├── use-cases.md │ │ │ │ └── value.md │ │ │ ├── ontologies-and-mapping │ │ │ │ ├── background-and-intro.md │ │ │ │ ├── dimensions.md │ │ │ │ ├── ekg-approach.md │ │ │ │ ├── levels.md │ │ │ │ ├── traditional-approach.md │ │ │ │ ├── use-cases.md │ │ │ │ └── value.md │ │ │ └── user-interface-and-access │ │ │ │ ├── background-and-intro.md │ │ │ │ ├── dimensions.md │ │ │ │ ├── ekg-approach.md │ │ │ │ ├── levels.md │ │ │ │ ├── traditional-approach.md │ │ │ │ ├── use-cases.md │ │ │ │ └── value.md │ │ ├── executive-leadership │ │ │ ├── funding-and-resources │ │ │ │ ├── background-and-intro.md │ │ │ │ ├── dimensions.md │ │ │ │ ├── ekg-approach.md │ │ │ │ ├── levels.md │ │ │ │ ├── traditional-approach.md │ │ │ │ ├── use-cases.md │ │ │ │ └── value.md │ │ │ ├── organizational-governance │ │ │ │ ├── background-and-intro.md │ │ │ │ ├── dimensions.md │ │ │ │ ├── ekg-approach.md │ │ │ │ ├── levels.md │ │ │ │ ├── traditional-approach.md │ │ │ │ ├── use-cases.md │ │ │ │ └── value.md │ │ │ ├── organizational-policies │ │ │ │ ├── background-and-intro.md │ │ │ │ ├── dimensions.md │ │ │ │ ├── ekg-approach.md │ │ │ │ ├── levels.md │ │ │ │ ├── traditional-approach.md │ │ │ │ ├── use-cases.md │ │ │ │ └── value.md │ │ │ ├── organizational-processes │ │ │ │ ├── background-and-intro.md │ │ │ │ ├── dimensions.md │ │ │ │ ├── ekg-approach.md │ │ │ │ ├── levels.md │ │ │ │ ├── traditional-approach.md │ │ │ │ ├── use-cases.md │ │ │ │ └── value.md │ │ │ ├── organizational-strategy │ │ │ │ ├── background-and-intro.md │ │ │ │ ├── dimensions.md │ │ │ │ ├── ekg-approach.md │ │ │ │ ├── levels.md │ │ │ │ ├── traditional-approach.md │ │ │ │ ├── use-cases.md │ │ │ │ └── value.md │ │ │ └── technology-requirements │ │ │ │ ├── background-and-intro.md │ │ │ │ ├── dimensions.md │ │ │ │ ├── ekg-approach.md │ │ │ │ ├── levels.md │ │ │ │ ├── traditional-approach.md │ │ │ │ ├── use-cases.md │ │ │ │ └── value.md │ │ ├── organizational-capabilities │ │ │ ├── control-functions │ │ │ │ ├── background-and-intro.md │ │ │ │ ├── dimensions.md │ │ │ │ ├── ekg-approach.md │ │ │ │ ├── levels.md │ │ │ │ ├── traditional-approach.md │ │ │ │ ├── use-cases.md │ │ │ │ └── value.md │ │ │ ├── knowledge-sharing │ │ │ │ ├── background-and-intro.md │ │ │ │ ├── dimensions.md │ │ │ │ ├── ekg-approach.md │ │ │ │ ├── levels.md │ │ │ │ ├── traditional-approach.md │ │ │ │ ├── use-cases.md │ │ │ │ └── value.md │ │ │ ├── talent-management │ │ │ │ ├── background-and-intro.md │ │ │ │ ├── dimensions.md │ │ │ │ ├── ekg-approach.md │ │ │ │ ├── levels.md │ │ │ │ ├── traditional-approach.md │ │ │ │ ├── use-cases.md │ │ │ │ └── value.md │ │ │ └── vendor-management │ │ │ │ ├── background-and-intro.md │ │ │ │ ├── dimensions.md │ │ │ │ ├── ekg-approach.md │ │ │ │ ├── levels.md │ │ │ │ ├── traditional-approach.md │ │ │ │ ├── use-cases.md │ │ │ │ └── value.md │ │ ├── organizational-culture │ │ │ ├── agility-and-innovation │ │ │ │ ├── background-and-intro.md │ │ │ │ ├── dimensions.md │ │ │ │ ├── ekg-approach.md │ │ │ │ ├── levels.md │ │ │ │ ├── traditional-approach.md │ │ │ │ ├── use-cases.md │ │ │ │ └── value.md │ │ │ ├── ecosystem-collaboration │ │ │ │ ├── background-and-intro.md │ │ │ │ ├── dimensions.md │ │ │ │ ├── ekg-approach.md │ │ │ │ ├── levels.md │ │ │ │ ├── traditional-approach.md │ │ │ │ ├── use-cases.md │ │ │ │ └── value.md │ │ │ └── implementation-approach │ │ │ │ ├── background-and-intro.md │ │ │ │ ├── dimensions.md │ │ │ │ ├── ekg-approach.md │ │ │ │ ├── levels.md │ │ │ │ ├── traditional-approach.md │ │ │ │ ├── use-cases.md │ │ │ │ └── value.md │ │ └── product-ownership │ │ │ ├── delivery-process │ │ │ ├── background-and-intro.md │ │ │ ├── dimensions.md │ │ │ ├── ekg-approach.md │ │ │ ├── levels.md │ │ │ ├── traditional-approach.md │ │ │ ├── use-cases.md │ │ │ └── value.md │ │ │ ├── funding-and-budget │ │ │ ├── background-and-intro.md │ │ │ ├── dimensions.md │ │ │ ├── ekg-approach.md │ │ │ ├── levels.md │ │ │ ├── traditional-approach.md │ │ │ ├── use-cases.md │ │ │ └── value.md │ │ │ ├── measurement-criteria │ │ │ ├── background-and-intro.md │ │ │ ├── dimensions.md │ │ │ ├── ekg-approach.md │ │ │ ├── levels.md │ │ │ ├── traditional-approach.md │ │ │ ├── use-cases.md │ │ │ └── value.md │ │ │ ├── team-requirements-management │ │ │ ├── background-and-intro.md │ │ │ ├── dimensions.md │ │ │ ├── ekg-approach.md │ │ │ ├── levels.md │ │ │ ├── traditional-approach.md │ │ │ ├── use-cases.md │ │ │ └── value.md │ │ │ └── use-case-requirements │ │ │ ├── background-and-intro.md │ │ │ ├── dimensions.md │ │ │ ├── ekg-approach.md │ │ │ ├── levels.md │ │ │ ├── traditional-approach.md │ │ │ ├── use-cases.md │ │ │ └── value.md │ └── technology │ │ ├── .gitignore │ │ ├── background-and-intro.md │ │ ├── technology-execution │ │ ├── analytics │ │ │ ├── background-and-intro.md │ │ │ ├── dimensions.md │ │ │ ├── ekg-approach.md │ │ │ ├── levels.md │ │ │ ├── traditional-approach.md │ │ │ ├── use-cases.md │ │ │ └── value.md │ │ ├── business-continuity │ │ │ ├── background-and-intro.md │ │ │ ├── dimensions.md │ │ │ ├── ekg-approach.md │ │ │ ├── levels.md │ │ │ ├── traditional-approach.md │ │ │ ├── use-cases.md │ │ │ └── value.md │ │ ├── data-integration │ │ │ ├── background-and-intro.md │ │ │ ├── dimensions.md │ │ │ ├── ekg-approach.md │ │ │ ├── levels.md │ │ │ ├── traditional-approach.md │ │ │ ├── use-cases.md │ │ │ └── value.md │ │ ├── data-quality-implementation │ │ │ ├── background-and-intro.md │ │ │ ├── dimensions.md │ │ │ ├── ekg-approach.md │ │ │ ├── levels.md │ │ │ ├── traditional-approach.md │ │ │ ├── use-cases.md │ │ │ └── value.md │ │ ├── data-transformation-execution │ │ │ ├── background-and-intro.md │ │ │ ├── dimensions.md │ │ │ ├── ekg-approach.md │ │ │ ├── levels.md │ │ │ ├── traditional-approach.md │ │ │ ├── use-cases.md │ │ │ └── value.md │ │ ├── entitlement-management │ │ │ ├── background-and-intro.md │ │ │ ├── dimensions.md │ │ │ ├── ekg-approach.md │ │ │ ├── levels.md │ │ │ ├── traditional-approach.md │ │ │ ├── use-cases.md │ │ │ └── value.md │ │ ├── identity-resolution │ │ │ ├── background-and-intro.md │ │ │ ├── dimensions.md │ │ │ ├── ekg-approach.md │ │ │ ├── levels.md │ │ │ ├── traditional-approach.md │ │ │ ├── use-cases.md │ │ │ └── value.md │ │ ├── inferencing-rules │ │ │ ├── background-and-intro.md │ │ │ ├── dimensions.md │ │ │ ├── ekg-approach.md │ │ │ ├── levels.md │ │ │ ├── traditional-approach.md │ │ │ ├── use-cases.md │ │ │ └── value.md │ │ ├── knowledge-graph-federation │ │ │ ├── background-and-intro.md │ │ │ ├── dimensions.md │ │ │ ├── ekg-approach.md │ │ │ ├── levels.md │ │ │ ├── traditional-approach.md │ │ │ ├── use-cases.md │ │ │ └── value.md │ │ ├── knowledge-graph-storage-retrieval │ │ │ ├── background-and-intro.md │ │ │ ├── dimensions.md │ │ │ ├── ekg-approach.md │ │ │ ├── levels.md │ │ │ ├── traditional-approach.md │ │ │ ├── use-cases.md │ │ │ └── value.md │ │ ├── knowledge-graph-virtualization │ │ │ ├── background-and-intro.md │ │ │ ├── dimensions.md │ │ │ ├── ekg-approach.md │ │ │ ├── levels.md │ │ │ ├── traditional-approach.md │ │ │ ├── use-cases.md │ │ │ └── value.md │ │ ├── llm-ai │ │ │ ├── background-and-intro.md │ │ │ ├── dimensions.md │ │ │ ├── ekg-approach.md │ │ │ ├── levels.md │ │ │ ├── traditional-approach.md │ │ │ ├── use-cases.md │ │ │ └── value.md │ │ ├── observability │ │ │ ├── background-and-intro.md │ │ │ ├── dimensions.md │ │ │ ├── ekg-approach.md │ │ │ ├── levels.md │ │ │ ├── traditional-approach.md │ │ │ ├── use-cases.md │ │ │ └── value.md │ │ └── operations │ │ │ ├── background-and-intro.md │ │ │ ├── dimensions.md │ │ │ ├── ekg-approach.md │ │ │ ├── levels.md │ │ │ ├── traditional-approach.md │ │ │ ├── use-cases.md │ │ │ └── value.md │ │ ├── technology-strategy │ │ └── technology-architecture │ │ │ ├── background-and-intro.md │ │ │ ├── dimensions.md │ │ │ ├── ekg-approach.md │ │ │ ├── levels.md │ │ │ ├── traditional-approach.md │ │ │ ├── use-cases.md │ │ │ └── value.md │ │ └── user-interface │ │ ├── collaboration │ │ ├── background-and-intro.md │ │ ├── dimensions.md │ │ ├── ekg-approach.md │ │ ├── levels.md │ │ ├── traditional-approach.md │ │ ├── use-cases.md │ │ └── value.md │ │ ├── content-editing │ │ ├── background-and-intro.md │ │ ├── dimensions.md │ │ ├── ekg-approach.md │ │ ├── levels.md │ │ ├── traditional-approach.md │ │ ├── use-cases.md │ │ └── value.md │ │ ├── multilingual-support │ │ ├── background-and-intro.md │ │ ├── dimensions.md │ │ ├── ekg-approach.md │ │ ├── levels.md │ │ ├── traditional-approach.md │ │ ├── use-cases.md │ │ └── value.md │ │ ├── reporting │ │ ├── background-and-intro.md │ │ ├── dimensions.md │ │ ├── ekg-approach.md │ │ ├── levels.md │ │ ├── traditional-approach.md │ │ ├── use-cases.md │ │ └── value.md │ │ ├── search │ │ ├── background-and-intro.md │ │ ├── dimensions.md │ │ ├── ekg-approach.md │ │ ├── levels.md │ │ ├── traditional-approach.md │ │ ├── use-cases.md │ │ └── value.md │ │ └── visualization │ │ ├── background-and-intro.md │ │ ├── dimensions.md │ │ ├── ekg-approach.md │ │ ├── levels.md │ │ ├── traditional-approach.md │ │ ├── use-cases.md │ │ └── value.md └── template │ ├── background-and-intro.md │ ├── dimensions.md │ ├── ekg-approach.md │ ├── levels.md │ ├── traditional-approach.md │ ├── use-cases.md │ └── value.md ├── docs-overrides ├── .icons │ └── ekgf-logo-symbol.svg ├── main.html └── partials │ └── content.html ├── docs ├── .gitignore ├── .pages.yaml ├── CNAME ├── article │ ├── .pages.yaml │ ├── business-strategy.md │ ├── dimensions-of-knowledge-risk-assessment.md │ ├── dimensions-of-knowledge-value-assessment.md │ ├── enterprise-architecture.md │ ├── image │ │ ├── coordination-operating-model-core-diagram4.jpg │ │ ├── core-diagram-design-process4.jpg │ │ ├── diversification-operating-model-core-diagram4.jpg │ │ ├── mexican-food-san-francisco.png │ │ ├── mission-district.png │ │ ├── places-experiences-events-homes-etc.png │ │ └── replication-operating-model-core-diagram4.png │ ├── index.md │ ├── introducing-kgi.md │ ├── meta-maturity-model.md │ ├── operating-model.md │ └── value-proposition-of-ekg.md ├── assets │ ├── .gitignore │ ├── ekg-maturity-structure.png │ ├── ekgmm-process-commit-changes.png │ ├── ekgmm-process-create-pdf-job.png │ ├── ekgmm-process-create-pdf-workflow.png │ ├── ekgmm-process-diagram.png │ ├── ekgmm-process-edit-content.png │ ├── ekgmm-process-pr-button.png │ ├── replication-operating-model-core-diagram4.png │ ├── sa.pdf_tex │ └── sa.svg ├── diagrams │ ├── .gitignore │ ├── include │ │ └── themes │ │ │ ├── dark.puml │ │ │ ├── general.puml │ │ │ └── light.puml │ └── src │ │ └── maturity-model.puml ├── generate_maturity_model.py ├── intro │ ├── .gitignore │ ├── .pages.yaml │ ├── executive-summary.md │ ├── index.md │ ├── overview.md │ ├── preface.md │ ├── strategic-objectives.md │ └── structure │ │ ├── .pages.yaml │ │ ├── index.md │ │ ├── levels.md │ │ ├── pillars.md │ │ └── template.md ├── javascript │ ├── images_dark.js │ └── refresh_on_toggle_dark_light.js ├── other │ ├── .pages.yaml │ ├── author │ │ ├── .pages.yaml │ │ ├── avinash-patil.md │ │ ├── carl-mattocks.md │ │ ├── carlos-tubbax.md │ │ ├── index.md │ │ ├── jacobus-geluk.md │ │ └── pete-rivett.md │ ├── contributors.md │ ├── corporate-members.md │ ├── history.md │ ├── how-to-register.md │ ├── index.md │ └── process.md └── stylesheets │ └── extra.css ├── ekg-maturity.iml ├── metadata ├── 0-model.ttl ├── a-1-business-strategy-actuation.ttl ├── a-2-business-model-elaboration.ttl ├── a-3-business-enablers.ttl ├── a-business-pillar.ttl ├── b-1-executive-leadership.ttl ├── b-2-product-ownership.ttl ├── b-3-delivery-management.ttl ├── b-4-organizational-culture.ttl ├── b-5-organizational-capabilities.ttl ├── b-organization-pillar.ttl ├── c-1-data-strategy.ttl ├── c-2-data-architecture.ttl ├── c-3-data-quality.ttl ├── c-4-data-governance.ttl ├── c-data-pillar.ttl ├── d-1-technology-strategy.ttl ├── d-2-technology-execution.ttl ├── d-3-user-interface.ttl └── d-technology-pillar.ttl ├── mkdocs.insiders.yml ├── mkdocs.outsiders.yml ├── mkdocs.yml ├── old-latex-content ├── .gitignore └── unprocessed-old-latex │ ├── a-3-2-enterprise-architecture.tex │ ├── c-3-3.tex │ ├── c-4-1.tex │ ├── c-4-2.tex │ ├── c-4-3.tex │ ├── c-4-4.tex │ ├── c-4-5.tex │ ├── c-4-6.tex │ ├── d-2-1.tex │ ├── d-2-10.tex │ ├── d-2-12.tex │ ├── d-2-13.tex │ ├── d-2-2.tex │ ├── d-2-3.tex │ ├── d-3-1.tex │ └── d-3-3.tex ├── poetry.toml ├── pyproject.toml ├── requirements.txt └── workspace.code-workspace /.editorconfig: -------------------------------------------------------------------------------- 1 | root = true 2 | 3 | [*] 4 | indent_style = space 5 | indent_size = 2 6 | charset = utf-8 7 | trim_trailing_whitespace = false 8 | insert_final_newline = true 9 | 10 | # Minified JavaScript files shouldn't be changed 11 | 12 | [*.sparql] 13 | indent_size = 4 14 | 15 | # Makefiles always use tabs for indentation 16 | 17 | # Batch files use tabs for indentation 18 | 19 | [{.eslintrc,.babelrc,jest.config,.stylelintrc,*.json,*.jsb3,*.jsb2,*.bowerrc}] 20 | indent_style=space 21 | indent_size=2 22 | 23 | # Minified JavaScript files shouldn't be changed 24 | [**.min.js] 25 | indent_style = ignore 26 | insert_final_newline = ignore 27 | 28 | [{*.yml,*.yaml}] 29 | indent_style=space 30 | indent_size=2 31 | 32 | [*.md] 33 | max_line_length = off 34 | trim_trailing_whitespace = false 35 | 36 | # Makefiles always use tabs for indentation 37 | [Makefile] 38 | indent_style = tab 39 | 40 | # Batch files use tabs for indentation 41 | [*.bat] 42 | indent_style = tab 43 | 44 | [*.py] 45 | indent_style = space 46 | indent_size = 4 47 | 48 | [*.xml] 49 | indent_style = tab 50 | indent_size = 2 51 | tab_width = 8 52 | 53 | -------------------------------------------------------------------------------- /.github/dependabot.yml: -------------------------------------------------------------------------------- 1 | version: 2 2 | updates: 3 | # Maintain dependencies for GitHub Actions 4 | - package-ecosystem: "github-actions" 5 | directory: "/" 6 | schedule: 7 | interval: "daily" 8 | -------------------------------------------------------------------------------- /.github/labeler.yml: -------------------------------------------------------------------------------- 1 | mkdocs-infra: 2 | - Makefile 3 | - mkdocs.yml 4 | - docs-overrides/ 5 | - docs/assets/ 6 | - docs/stylesheets/ 7 | - docs/main.py 8 | - '*/**/CNAME' 9 | - .tool-versions 10 | - README.md 11 | 12 | github-actions: 13 | - .github/ 14 | 15 | infra: 16 | - etc/* 17 | - .github/* 18 | - .* 19 | - /**/**.sh 20 | - /**/*.md 21 | 22 | diagram: 23 | - /**/*.puml 24 | 25 | -------------------------------------------------------------------------------- /.github/workflows/label.yml: -------------------------------------------------------------------------------- 1 | # This workflow will triage pull requests and apply a label based on the 2 | # paths that are modified in the pull request. 3 | # 4 | # To use this workflow, you will need to set up a .github/labeler.yml 5 | # file with configuration. For more information, see: 6 | # https://github.com/actions/labeler 7 | 8 | name: Labeler 9 | on: [pull_request] 10 | 11 | jobs: 12 | label: 13 | if: github.event.pull_request.head.repo.full_name == github.repository 14 | runs-on: ubuntu-latest 15 | steps: 16 | - uses: actions/labeler@master 17 | with: 18 | repo-token: "${{ secrets.GITHUB_TOKEN }}" 19 | -------------------------------------------------------------------------------- /.gitignore: -------------------------------------------------------------------------------- 1 | .cache/ 2 | .venv/ 3 | venv/ 4 | __pypackages__/ 5 | site/ 6 | poetry.lock 7 | .DS_Store 8 | .texpadtmp 9 | *.aux 10 | *.bbl 11 | *.bcf 12 | *.blg 13 | *.fls 14 | *.glo 15 | *.glg 16 | *.gls 17 | *.glsdefs 18 | *.idx 19 | *.ilg 20 | *.ind 21 | *.ist 22 | *.labelTags 23 | *.lof 24 | *.log 25 | *.out 26 | *.pdf 27 | *.run.xml 28 | *.synctex* 29 | *.tdo 30 | *.sta 31 | *.gz 32 | *.toc 33 | *.acn 34 | *.acr 35 | *.alg 36 | *.dvi 37 | *.lot 38 | *.maf 39 | *.mtc 40 | *.mtc1 41 | .fdb_latexmk 42 | !images/*.pdf 43 | !images/*.pdf_tex 44 | images/svg-inkscape/ 45 | svg-inkscape/ 46 | */images/svg-inkscape/ 47 | out/ 48 | /.project 49 | .uuid 50 | *.tlg 51 | *.olg 52 | *.tld 53 | *.old 54 | *.tdn 55 | *.odn 56 | *.pandoc.docx 57 | .idea 58 | *.fdb_latexmk 59 | *.xdy 60 | .venv/ 61 | -------------------------------------------------------------------------------- /.idea/misc.xml: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 10 | 11 | 12 | 13 | -------------------------------------------------------------------------------- /.idea/vcs.xml: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 5 | 6 | 7 | -------------------------------------------------------------------------------- /.tool-versions: -------------------------------------------------------------------------------- 1 | python 3.10.8 2 | nodejs 17.4.0 3 | java openjdk-18 4 | poetry 1.4.2 5 | -------------------------------------------------------------------------------- /.vscode/settings.json: -------------------------------------------------------------------------------- 1 | { 2 | "git.autofetch": true 3 | } -------------------------------------------------------------------------------- /.vscode/tasks.json: -------------------------------------------------------------------------------- 1 | { 2 | // See https://go.microsoft.com/fwlink/?LinkId=733558 3 | // for the documentation about the tasks.json format 4 | "version": "2.0.0", 5 | "tasks": [ 6 | { 7 | "label": "build-all", 8 | "type": "shell", 9 | "command": "./build-all.sh", 10 | "group": { 11 | "kind": "build", 12 | "isDefault": true 13 | } 14 | } 15 | ] 16 | } 17 | -------------------------------------------------------------------------------- /CNAME: -------------------------------------------------------------------------------- 1 | maturity.ekgf.org 2 | -------------------------------------------------------------------------------- /Pipfile: -------------------------------------------------------------------------------- 1 | [[source]] 2 | url = "https://pypi.org/simple" 3 | verify_ssl = true 4 | name = "pypi" 5 | 6 | [packages] 7 | attrs = "==22.1.0" 8 | babel = "==2.10.3" 9 | beautifulsoup4 = "==4.11.1" 10 | binaryio = "==1.0.0" 11 | boto3 = "==1.24.70" 12 | boto3-stubs = "==1.24.70" 13 | botocore = "==1.27.70" 14 | botocore-stubs = "==1.27.89" 15 | bracex = "==2.3.post1" 16 | certifi = "==2022.9.24" 17 | charset-normalizer = "==2.1.1" 18 | click = "==8.1.3" 19 | csscompressor = "==0.9.5" 20 | cssselect = "==1.1.0" 21 | data-science-types = "==0.2.23" 22 | distlib = "==0.3.6" 23 | editorconfig = "==0.12.3" 24 | 25 | [dev-packages] 26 | 27 | [requires] 28 | python_version = "3.10.8" 29 | -------------------------------------------------------------------------------- /VERSION: -------------------------------------------------------------------------------- 1 | 1.0.2 2 | -------------------------------------------------------------------------------- /abbreviations.md: -------------------------------------------------------------------------------- 1 | *[API]: Application Programming Interface 2 | *[BAU]: Business as Usual 3 | *[BDD]: Behavior Driven Development 4 | *[COSO]: Committee of Sponsoring Organizations of the Treadway Commissions 5 | *[DDD]: Domain Driven Design 6 | *[EKGF]: Enterprise Knowledge Graph Foundation 7 | *[EKG]: Enterprise Knowledge Graph, an EKGF standard 8 | *[ERM]: Enterprise Risk Management 9 | *[ERP]: Enterprise Resource Planning 10 | *[HTML]: Hyper Text Markup Language, a W3C standard 11 | *[LUBM]: Lehigh University Benchmark 12 | *[MOU]: Memorandum of Understanding 13 | *[OODA]: Observe, Orient, Decide, Act 14 | *[PDCA]: Plan, Do, Check, Act 15 | *[PR]: Pull Request 16 | *[RDF]: Resource Definition Framework, the standard that defines the basic building block of a semantic graph: the so-called "triple" i.e. an RDF-statement 17 | *[SDD]: Self-describing dataset 18 | *[SDD]: Self-describing dataset, an EKGF standard 19 | *[SHACL]: Shapes Constraint Language, a W3C standard 20 | *[SPARQL]: SPARQL Protocol and RDF Query Language, a W3C standard 21 | *[SUDA]: Sense, Understand, Decide, Act 22 | *[W3C]: World Wide Web Consortium 23 | *[W3C]: World Wide Web Consortium 24 | [//]: # (this file is not placed in the ./docs directory to avoid MkDocs warnings) 25 | -------------------------------------------------------------------------------- /customer-assets/ekgf/quadrants.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/EKGF/ekg-maturity/9e758a40b367e6bcaf37d89df17e9e0b6e7bdfc4/customer-assets/ekgf/quadrants.jpg -------------------------------------------------------------------------------- /docs-fragments/pillar/business/.gitignore: -------------------------------------------------------------------------------- 1 | capability-area/ 2 | -------------------------------------------------------------------------------- /docs-fragments/pillar/business/business-enablers/capability-map/dimensions.md: -------------------------------------------------------------------------------- 1 | # Dimensions 2 | 3 | !!! warn 4 | 5 | Work in progress, this is just the results of an initial 6 | brainstorm session, needs to be worked out 7 | 8 | 1. Capability Map Coverage: does your capability map cover your 9 | whole business? Scale of 0-100% 10 | 2. Is your capability map represented in the EKG itself and if so, 11 | what’s the coverage? Scale 0-100% 12 | 3. Is your Capability Map an executable model (and is it 13 | actually executed)? Scale 1 to 5. 14 | - Note: this is “just” about the capability map model itself, not about executing all related models as well. 15 | 4. Percentage of business capabilities that can be fully automated? 16 | - TODO: work on this one 17 | 5. Did you identify, per business capability, which EKG use cases 18 | will deliver on that capability? Scale 0-100% 19 | 6. Did you identify the why of each business capability? Scale 1 to 5. 20 | - Notes: the who, what, when and how is more important for 21 | the other pillars 22 | 7. Do you understand the value of each capability 23 | 8. How does each capability fit in the business mission/vision/strategy 24 | 9. Did you identify the what of each business capability? Scale 1 to 5. 25 | - Notes: the who, what, when and how is more important for 26 | the other pillars 27 | -------------------------------------------------------------------------------- /docs-fragments/pillar/business/business-enablers/operating-model/dimensions.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress, this is just the results of an initial 4 | brainstorm session, needs to be worked out 5 | 6 | 1. Has the organization identified its integration needs? Scale 1-5 7 | 2. Has the organization identified its standardization needs? Scale 1-5 8 | 3. To what extent is the above reflected in business glossaries? Scale 1-5 9 | 4. Has the organization identified and documented all its 10 | business processes? Scale 1-5 11 | 5. Have you identified for each business process **how** it enables/supports 12 | any given business capability? Scale 1-5 13 | 6. What’s the coverage of your operating model in relation to your 14 | capability map? Scale 0-100% 15 | 7. Is your Operating Model an executable model (and is it 16 | actually executed)? Scale 1 to 5. 17 | - Note: this is “just” about the operating model itself, 18 | not about executing all related models as well. 19 | 8. To what extent is your operating model related to 20 | digital transformation? Scale 1-5 21 | -------------------------------------------------------------------------------- /docs-fragments/pillar/business/business-enablers/operating-model/value.md: -------------------------------------------------------------------------------- 1 | ### Contribution to the EKG 2 | 3 | Since an operating model reflects the business needs for standardization 4 | across a company and its business units, it could be a great input for 5 | the development of reusable business vocabularies as part of the 6 | data infrastructure of an enterprise as later explained in the 7 | [data part of this work](/pillar/data/). 8 | These vocabularies may, in turn, be converted to machine-readable models. 9 | Such machine-readable models are called ontologies. 10 | 11 | ### Contribution to the Enterprise 12 | 13 | The operating model could help organizations define their requirements 14 | and expectations in terms of standardization and integration across 15 | business units. 16 | This would be useful to harmonize business capabilities and glossaries 17 | across companies and their business units. 18 | 19 | Furthermore, an operating model may serve as input to the development 20 | of an Enterprise Architecture that serves as the organizing logic for 21 | business processes and IT infrastructure based on the company’s 22 | standardization and integration requirements. 23 | 24 | -------------------------------------------------------------------------------- /docs-fragments/pillar/business/business-enablers/performance-management/dimensions.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress, this is just the results of an initial 4 | brainstorm session, needs to be worked out 5 | 6 | 1. Are your key performance indicators (KPI’s) linked to 7 | tactical activities and business goals? 8 | - Do people make decisions based on the KPI measurements? 9 | - Are all your KGIs linked to KPI dimensions? 10 | - Is there a base-line benchmark for your KPIs? 11 | - Are there well-communicated periods of decision-making? 12 | - Are your KPIs measured using high-quality data? 13 | 2. Do you use KPIs to measure the success of your strategy, 14 | fulfillment of goals and improvements of 15 | business capability? Scale 1-5 16 | -------------------------------------------------------------------------------- /docs-fragments/pillar/business/business-enablers/performance-management/ekg-approach.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress, describe how this capability would be delivered or supported using an EKG approach, 4 | making the link to the "how" i.e. the [EKG/Method](https://method.ekgf.org). 5 | -------------------------------------------------------------------------------- /docs-fragments/pillar/business/business-enablers/performance-management/levels.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress, describe the 5 maturity levels of this capability 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/business/business-enablers/performance-management/traditional-approach.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress, describe how this capability is possibly being delivered today in a non-EKG context and optionally what the issues are that EKG could or should improve 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/business/business-enablers/performance-management/use-cases.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | 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/](https://catalog.ekgf.org/use-case/).. 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/business/business-enablers/performance-management/value.md: -------------------------------------------------------------------------------- 1 | ### Contribution to the Enterprise 2 | 3 | While practices around Performance Management might 4 | vary across enterprises, we highlight below a few 5 | focus areas where EKGs can act as effective enablers: 6 | 7 | _Business Identities_ can act as the common contexts for 8 | aligning strategic and operational performance management. 9 | Highly engaged senior executives practice these links to 10 | drive effective alignment with feedback through their 11 | own mental models of linkage. 12 | EKG-driven feedback mechanisms, based on _business identities_, 13 | can then replicate such links and operate with more objectivity 14 | by enabling decision-making through links of operational 15 | activities and their metrics to the associated business goals, 16 | values and customer propositions. 17 | 18 | Contracts can act as common contexts for aligning operations 19 | and role performance management. 20 | Employee contracts can be the most concrete form of expectation 21 | specification and management and their linkage to operations 22 | and the associated propositions of the enterprise to its 23 | customers and other stakeholders can help in aligning appraisals 24 | more objectively to operations and enterprise performance. 25 | 26 | -------------------------------------------------------------------------------- /docs-fragments/pillar/business/business-enablers/risk-management/dimensions.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress, this is just the results of an initial 4 | brainstorm session, needs to be worked out 5 | 6 | 1. External risk: Are threats identified (according to but not 7 | exclusive to your SWOT analysis)? 8 | - Do you have a threat-matrix? 9 | - Is there a threat-risk score? 10 | 2. External risk: Cyber-threats, have they been identified? 11 | 3. Preventable risks 12 | 4. Strategy risks 13 | 5. Scoring risks: 14 | 6. Is the risk-appetite defined by the board? 15 | 7. How do you translate identified risks or threats into action? 16 | 17 | -------------------------------------------------------------------------------- /docs-fragments/pillar/business/business-enablers/risk-management/ekg-approach.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress, describe how this capability would be delivered or supported using an EKG approach, 4 | making the link to the "how" i.e. the [EKG/Method](https://method.ekgf.org). 5 | -------------------------------------------------------------------------------- /docs-fragments/pillar/business/business-enablers/risk-management/levels.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress, describe the 5 maturity levels of this capability 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/business/business-enablers/risk-management/traditional-approach.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress, describe how this capability is possibly being delivered today in a non-EKG context and optionally what the issues are that EKG could or should improve 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/business/business-enablers/risk-management/use-cases.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | 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/](https://catalog.ekgf.org/use-case/).. 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/business/business-enablers/supply-chain-management/value.md: -------------------------------------------------------------------------------- 1 | ### Contribution to the Enterprise 2 | 3 | In the EKG context, the above ASCM definition of _Supply Chain Management_ could be broadened 4 | by also including any detailed supply chain within an ecosystem or enterprise where any one given "operation" 5 | delivers "value" to another "operation". 6 | 7 | -------------------------------------------------------------------------------- /docs-fragments/pillar/business/business-model-elaboration/change-management/background-and-intro.md: -------------------------------------------------------------------------------- 1 | Change is happening everywhere in organizations. 2 | The digitalization of everything (IoT, edge computing, digital transform) 3 | has created a fluid context for change, and the need to decentralize 4 | decision-making to keep pace with exponential change and complexity 5 | requires non-linear thinking, planning, and execution. 6 | 7 | The current approaches for change management are usually built 8 | on linear models which do not scale nor can they collate 9 | the facets of data --- let alone semantic perspectives ---, 10 | that are overwhelming decision makers. 11 | 12 | !!! note inline end "[Jeffrey Wallk](https://www.enablingvalue.com)" 13 | 14 | Ask not what Change Management can do for EKG, 15 | rather ask what EKG can do for Change Management 16 | 17 | EKGs are the only way to build a scalable framework of understanding 18 | about change and capture relevant patterns to guide option analysis 19 | and impact analysis. 20 | The days of getting in a room and relying on meetings is quickly 21 | coming to an end. 22 | AI, Bayesian Analysis, Game Theory, MCDA, and Heuristics can help, 23 | but only if we can guide them properly using EKGs. 24 | 25 | -------------------------------------------------------------------------------- /docs-fragments/pillar/business/business-model-elaboration/change-management/dimensions.md: -------------------------------------------------------------------------------- 1 | 2 | A business scalability assessment can help an enterprise understand its current level of scalability and identify areas for improvement. This can help the enterprise ensure 3 | that it is able to efficiently and effectively handle growth, whether that growth comes in the form of increased demand for its products or services, expansion into new markets, 4 | or some other form of growth. A scalability assessment can also help the enterprise identify potential bottlenecks or constraints that could limit its ability to scale, 5 | and provide recommendations for addressing those constraints. Overall, a business scalability assessment can help the enterprise plan for and manage growth in a way that 6 | is sustainable and profitable. 7 | 8 | !!! warn 9 | 10 | Work in progress 11 | -------------------------------------------------------------------------------- /docs-fragments/pillar/business/business-model-elaboration/change-management/ekg-approach.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress. 4 | Explain how the given Capability or Capability Area would look like 5 | in a mature EKG context. 6 | -------------------------------------------------------------------------------- /docs-fragments/pillar/business/business-model-elaboration/change-management/levels.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress, describe the 5 maturity levels of this capability 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/business/business-model-elaboration/change-management/traditional-approach.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress. 4 | Explain how things are done today in a non-EKG context 5 | -------------------------------------------------------------------------------- /docs-fragments/pillar/business/business-model-elaboration/change-management/use-cases.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress. 4 | 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/](https://catalog.ekgf.org/use-case/).. 5 | -------------------------------------------------------------------------------- /docs-fragments/pillar/business/business-model-elaboration/change-management/value.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress. 4 | Explain how EKG contributes value and how this capability or capability- 5 | enables higher levels of maturity for the EKG (which in turn provides more value to the business) 6 | -------------------------------------------------------------------------------- /docs-fragments/pillar/business/business-model-elaboration/market-segmentation/background-and-intro.md: -------------------------------------------------------------------------------- 1 | !!! note inline end 2 | 3 | 98% of firms agree that static segmentation is no longer adequate, 4 | and 100% of firms recognize the opportunity cost of not evolving to 5 | its more granular, precision-based, inheritor: 6 | Dynamic Predictive Segmentation. 7 | 8 | Market Segmentation is an important component in the [elaboration of an Enterprise’s Business Model](../../), 9 | helping Enterprises to align their Product and Services fulfilment to the needs of their customers. 10 | Market Segmentation practices today involve an intensive analysis through a mix of surveys, 11 | heuristics and benchmarking. 12 | The availability of and access to voluminous information though a multitude of digital sources has put 13 | additional emphasis on the ability of enterprises to dynamically tweak their Market Segmentation. 14 | 15 | -------------------------------------------------------------------------------- /docs-fragments/pillar/business/business-model-elaboration/market-segmentation/dimensions.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/business/business-model-elaboration/market-segmentation/ekg-approach.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress. 4 | Explain how the given Capability or Capability Area would look like 5 | in a mature EKG context. 6 | -------------------------------------------------------------------------------- /docs-fragments/pillar/business/business-model-elaboration/market-segmentation/levels.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress, describe the 5 maturity levels of this capability 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/business/business-model-elaboration/market-segmentation/traditional-approach.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress. 4 | Explain how things are done today in a non-EKG context 5 | -------------------------------------------------------------------------------- /docs-fragments/pillar/business/business-model-elaboration/market-segmentation/use-cases.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress. 4 | 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/](https://catalog.ekgf.org/use-case/).. 5 | -------------------------------------------------------------------------------- /docs-fragments/pillar/business/business-model-elaboration/market-segmentation/value.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress. 4 | Explain how EKG contributes value and how this capability or capability- 5 | enables higher levels of maturity for the EKG (which in turn provides more value to the business) 6 | -------------------------------------------------------------------------------- /docs-fragments/pillar/business/business-model-elaboration/value-chain/background-and-intro.md: -------------------------------------------------------------------------------- 1 | !!! note inline end "[McKinsey Digital](https://www.mckinsey.com/business-functions/mckinsey-digital/our-insights/how-do-companies-create-value-from-digital-ecosystems)" 2 | 3 | Most global companies are now actively considering the ecosystem 4 | business model given its value-generation potential: 5 | growing the core business, expanding the network and portfolio, 6 | and generating revenues from new products and services. 7 | 8 | Value chains have been a prominent way of organizing and linking 9 | activities in an Enterprise to create value for its customers, 10 | thorough provision of products and services. 11 | Digitalization and the increasing focus on consumer-centricity 12 | has pushed the imperatives of Value Chains to include more 13 | holistic collaborations in the business ecosystem---reshaping 14 | provision of services and access to untapped pools of value. 15 | 16 | -------------------------------------------------------------------------------- /docs-fragments/pillar/business/business-model-elaboration/value-chain/dimensions.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/business/business-model-elaboration/value-chain/ekg-approach.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress. 4 | Explain how the given Capability or Capability Area would look like 5 | in a mature EKG context. 6 | -------------------------------------------------------------------------------- /docs-fragments/pillar/business/business-model-elaboration/value-chain/traditional-approach.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress. 4 | Explain how things are done today in a non-EKG context 5 | -------------------------------------------------------------------------------- /docs-fragments/pillar/business/business-model-elaboration/value-chain/use-cases.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress. 4 | 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/](https://catalog.ekgf.org/use-case/).. 5 | -------------------------------------------------------------------------------- /docs-fragments/pillar/business/business-model-elaboration/value-chain/value.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress. 4 | Explain how EKG contributes value and how this capability or capability- 5 | enables higher levels of maturity for the EKG (which in turn provides more value to the business) 6 | -------------------------------------------------------------------------------- /docs-fragments/pillar/business/strategy-actuation/business-goals/background-and-intro.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/business/strategy-actuation/business-goals/dimensions.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/business/strategy-actuation/business-goals/ekg-approach.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress. 4 | Explain how the given Capability or Capability Area would look like 5 | in a mature EKG context. 6 | -------------------------------------------------------------------------------- /docs-fragments/pillar/business/strategy-actuation/business-goals/levels.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress, describe the 5 maturity levels of this capability 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/business/strategy-actuation/business-goals/traditional-approach.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress. 4 | Explain how things are done today in a non-EKG context 5 | -------------------------------------------------------------------------------- /docs-fragments/pillar/business/strategy-actuation/business-goals/use-cases.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress. 4 | 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/](https://catalog.ekgf.org/use-case/).. 5 | -------------------------------------------------------------------------------- /docs-fragments/pillar/business/strategy-actuation/business-goals/value.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress. 4 | Explain how EKG contributes value and how this capability or capability- 5 | enables higher levels of maturity for the EKG (which in turn provides more value to the business) 6 | -------------------------------------------------------------------------------- /docs-fragments/pillar/business/strategy-actuation/business-tactics/background-and-intro.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/business/strategy-actuation/business-tactics/dimensions.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/business/strategy-actuation/business-tactics/ekg-approach.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress. 4 | Explain how the given Capability or Capability Area would look like 5 | in a mature EKG context. 6 | -------------------------------------------------------------------------------- /docs-fragments/pillar/business/strategy-actuation/business-tactics/levels.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/business/strategy-actuation/business-tactics/traditional-approach.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress. 4 | Explain how things are done today in a non-EKG context 5 | -------------------------------------------------------------------------------- /docs-fragments/pillar/business/strategy-actuation/business-tactics/use-cases.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress. 4 | 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/](https://catalog.ekgf.org/use-case/).. 5 | -------------------------------------------------------------------------------- /docs-fragments/pillar/business/strategy-actuation/business-tactics/value.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress. 4 | Explain how EKG contributes value and how this capability or capability- 5 | enables higher levels of maturity for the EKG (which in turn provides more value to the business) 6 | -------------------------------------------------------------------------------- /docs-fragments/pillar/business/strategy-actuation/business-vision/background-and-intro.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/business/strategy-actuation/business-vision/dimensions.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/business/strategy-actuation/business-vision/ekg-approach.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress. 4 | Explain how the given Capability or Capability Area would look like 5 | in a mature EKG context. 6 | -------------------------------------------------------------------------------- /docs-fragments/pillar/business/strategy-actuation/business-vision/levels.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/business/strategy-actuation/business-vision/traditional-approach.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress. 4 | Explain how things are done today in a non-EKG context 5 | -------------------------------------------------------------------------------- /docs-fragments/pillar/business/strategy-actuation/business-vision/use-cases.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress. 4 | 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/](https://catalog.ekgf.org/use-case/).. 5 | -------------------------------------------------------------------------------- /docs-fragments/pillar/business/strategy-actuation/business-vision/value.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress. 4 | Explain how EKG contributes value and how this capability or capability- 5 | enables higher levels of maturity for the EKG (which in turn provides more value to the business) 6 | -------------------------------------------------------------------------------- /docs-fragments/pillar/data/.gitignore: -------------------------------------------------------------------------------- 1 | capability-area/ 2 | -------------------------------------------------------------------------------- /docs-fragments/pillar/data/data-architecture/business-vocabularies/background-and-intro.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/data/data-architecture/business-vocabularies/dimensions.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress, this is just the results of an initial 4 | brainstorm session, needs to be worked out 5 | 6 | 1. Do you have a Change Management plan and is it driving everything? 7 | - Is your plan related to and driven by your value streams and 8 | how it will lead from current to future state? 9 | 2. Do you know which EKG Use Cases you require to implement your 10 | Change Management plans? 11 | 3. Is “Positive Learning” in place? Is there a feedback loop of 12 | metrics for past performance continuously improving your 13 | change management plans? Scale 1-5 14 | - Can be measured more systematically by understanding how many 15 | EKG use cases are reused and involved in each new step along 16 | the way 17 | -------------------------------------------------------------------------------- /docs-fragments/pillar/data/data-architecture/business-vocabularies/ekg-approach.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress, describe how this capability would be delivered or supported using an EKG approach, 4 | making the link to the "how" i.e. the [EKG/Method](https://method.ekgf.org). 5 | -------------------------------------------------------------------------------- /docs-fragments/pillar/data/data-architecture/business-vocabularies/levels.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress, describe the 5 maturity levels of this capability 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/data/data-architecture/business-vocabularies/traditional-approach.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress, describe how this capability is possibly being delivered today in a non-EKG context and optionally what the issues are that EKG could or should improve 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/data/data-architecture/business-vocabularies/use-cases.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | 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/](https://catalog.ekgf.org/use-case/).. 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/data/data-architecture/business-vocabularies/value.md: -------------------------------------------------------------------------------- 1 | ### Contribution to the EKG 2 | 3 | The EKG should be updated to reflect changes made to the enterprise 4 | as a result of change projects. 5 | EKG governance is a set of change processes that should follow a 6 | disciplined change approach to protect the integrity and value 7 | of the knowledge graph. 8 | 9 | ### Contribution to the Enterprise 10 | 11 | The EKG can hold the model of the enterprise to identify potential 12 | areas for change to include: 13 | discover duplication across business silos, impact analysis of areas 14 | targeted to change, impact of regulatory change, impact of entering 15 | new markets, impact of scaling the business, impact from major 16 | incidents and issues, and can serve as a baseline for evaluating 17 | and executing merger/acquisition of new enterprises. 18 | 19 | The EKG can hold the information on current state of the enterprise 20 | for reuse of information to start the project, ideal state of the 21 | enterprise, intended new state of the enterprise after the change 22 | is deployed, and updated for actual resulting business knowledge 23 | from deploying the change. 24 | -------------------------------------------------------------------------------- /docs-fragments/pillar/data/data-architecture/data-integration/dimensions.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress, this is just the results of an initial 4 | brainstorm session, needs to be worked out 5 | 6 | 1. Are all your markets well-defined? 7 | - Which products and services are sold per market? 8 | 2. Is the geospatial size of your markets known? 9 | 3. Is the demographic / psycho-graphic segmentation of your markets known? 10 | 4. Is the value-proposition per market, per product or service 11 | well-defined, communicated and sold? 12 | - (Porter value chain) 13 | 5. Are cohorts identified? 14 | 6. Are trade-promotions optimized? 15 | - Optimizing “supply-chain to shelf” 16 | - Are opportunities for optimization known are there processes in place to continuously improve and optimize your value propositions 17 | 7. Are you leveraging any means available to segment your market into target groups and cohorts? 18 | - Do you have an interest-graph of all of your customers? 19 | 8. Is your competition known, competitive advantages and USPs 20 | known, opportunities and threats? 21 | -------------------------------------------------------------------------------- /docs-fragments/pillar/data/data-architecture/data-integration/ekg-approach.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress, describe how this capability would be delivered or supported using an EKG approach, 4 | making the link to the "how" i.e. the [EKG/Method](https://method.ekgf.org). 5 | -------------------------------------------------------------------------------- /docs-fragments/pillar/data/data-architecture/data-integration/levels.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress, describe the 5 maturity levels of this capability 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/data/data-architecture/data-integration/traditional-approach.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress, describe how this capability is possibly being delivered today in a non-EKG context and optionally what the issues are that EKG could or should improve 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/data/data-architecture/data-integration/use-cases.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | 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/](https://catalog.ekgf.org/use-case/).. 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/data/data-architecture/data-integration/value.md: -------------------------------------------------------------------------------- 1 | ### Contribution to the EKG 2 | 3 | The EKG can bring all possible internal and external detail information 4 | about customers, products, services, competition, sales volumes, 5 | customer requirements and many other details together forming a 6 | holistic and realistic, almost real-time view of the position of 7 | the company in their markets. 8 | 9 | ### Contribution to the Enterprise 10 | 11 | Having the proper Market Segments defined will help with the selection, 12 | definition and prioritization of the right use cases for the EKG. 13 | -------------------------------------------------------------------------------- /docs-fragments/pillar/data/data-architecture/datasets/background-and-intro.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/data/data-architecture/datasets/dimensions.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress, this is just the results of an initial 4 | brainstorm session, needs to be worked out 5 | 6 | 1. Did you identify the value proposition of your organization? Scale 1-5 7 | - Is your value proposition supported by value streams? Scale 1-5 8 | 2. Does each value stream provide an identifiable and measurable 9 | flow of value ? Scale 1-5 10 | 3. Is each Value Stream an executable model (and is it actually 11 | executed)? Scale 1 to 5. 12 | - Note: this is “just” about the Value Stream model itself, 13 | not about executing all related models as well. 14 | Development value streams (DVS) are the sequence of 15 | activities needed to convert a Value Stream model into a 16 | digitally enabled Solution. 17 | 4. Do you know what percentage of any given change management plan 18 | relies on proven steps? 19 | - TODO: Work this one out further 20 | -------------------------------------------------------------------------------- /docs-fragments/pillar/data/data-architecture/datasets/ekg-approach.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress, describe how this capability would be delivered or supported using an EKG approach, 4 | making the link to the "how" i.e. the [EKG/Method](https://method.ekgf.org). 5 | -------------------------------------------------------------------------------- /docs-fragments/pillar/data/data-architecture/datasets/levels.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress, describe the 5 maturity levels of this capability 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/data/data-architecture/datasets/traditional-approach.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress, describe how this capability is possibly being delivered today in a non-EKG context and optionally what the issues are that EKG could or should improve 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/data/data-architecture/datasets/use-cases.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | 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/](https://catalog.ekgf.org/use-case/).. 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/data/data-architecture/datasets/value.md: -------------------------------------------------------------------------------- 1 | ### Contribution to the EKG 2 | 3 | Having the Value Chain(s) of an organization defined can help with the selection, 4 | definition and prioritization of the right use cases for the EKG. 5 | 6 | ### Contribution to the Enterprise 7 | 8 | In the EKG context, a "digital twin" of a company's value chain can 9 | be modelled where all the various components of the value chain are 10 | represented e.q. all details around logistics, supply chains, 11 | operations, services, marketing, sales and all support activities. 12 | At higher levels of maturity, all real-world details of these 13 | components are available as well and represent the reality accurately 14 | and in real-time. 15 | 16 | 17 | -------------------------------------------------------------------------------- /docs-fragments/pillar/data/data-architecture/ontologies/dimensions.md: -------------------------------------------------------------------------------- 1 | 2 | - How much of the enterprise data is covered by ontologies? 3 | - How well is ontology coverage mapped to business need? 4 | - To what extent are concepts independent of but mapped to terminology/vocabulary? 5 | - Level of sophistication of textual and logic definitions 6 | - Level of tooling is available and used 7 | - Level of training and trained people 8 | - Level of process (including change management), guidelines and standards 9 | - Level of modularity and reuse --- internal and external 10 | - Extent of examples and tests 11 | - Extent of traceability with different logical and physical data models 12 | -------------------------------------------------------------------------------- /docs-fragments/pillar/data/data-architecture/ontologies/ekg-approach.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress, describe how this capability would be delivered or supported using an EKG approach, 4 | making the link to the "how" i.e. the [EKG/Method](https://method.ekgf.org). 5 | -------------------------------------------------------------------------------- /docs-fragments/pillar/data/data-architecture/ontologies/traditional-approach.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress, describe how this capability is possibly being delivered today in a non-EKG context and optionally what the issues are that EKG could or should improve 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/data/data-architecture/ontologies/use-cases.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | 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/](https://catalog.ekgf.org/use-case/).. 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/data/data-governance/classification-management/background-and-intro.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/data/data-governance/classification-management/dimensions.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress, this is just the results of an initial 4 | brainstorm session, needs to be worked out 5 | 6 | 1. Are your business goals measurable? Scale 1-5 7 | 2. Are all your business goals part of a well-defined 8 | business strategy? Scale 1-5 9 | -------------------------------------------------------------------------------- /docs-fragments/pillar/data/data-governance/classification-management/ekg-approach.md: -------------------------------------------------------------------------------- 1 | # EKG Approach 2 | 3 | !!! warn 4 | 5 | Work in progress. 6 | Explain how the given Capability or Capability Area would look like 7 | in a mature EKG context. 8 | -------------------------------------------------------------------------------- /docs-fragments/pillar/data/data-governance/classification-management/levels.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress, describe the 5 maturity levels of this capability 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/data/data-governance/classification-management/traditional-approach.md: -------------------------------------------------------------------------------- 1 | # Traditional Approach 2 | 3 | !!! warn 4 | 5 | Work in progress. 6 | Explain how things are done today in a non-EKG context 7 | -------------------------------------------------------------------------------- /docs-fragments/pillar/data/data-governance/classification-management/use-cases.md: -------------------------------------------------------------------------------- 1 | # Use Cases 2 | 3 | !!! warn 4 | 5 | Work in progress. 6 | 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/](https://catalog.ekgf.org/use-case/).. 7 | -------------------------------------------------------------------------------- /docs-fragments/pillar/data/data-governance/classification-management/value.md: -------------------------------------------------------------------------------- 1 | # Value 2 | 3 | !!! warn 4 | 5 | Work in progress. 6 | Explain how EKG contributes value and how this capability or capability- 7 | enables higher levels of maturity for the EKG (which in turn provides more value to the business) 8 | -------------------------------------------------------------------------------- /docs-fragments/pillar/data/data-governance/data-management-policy/background-and-intro.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/data/data-governance/data-management-policy/ekg-approach.md: -------------------------------------------------------------------------------- 1 | # EKG Approach 2 | 3 | !!! warn 4 | 5 | Work in progress. 6 | Explain how the given Capability or Capability Area would look like 7 | in a mature EKG context. 8 | -------------------------------------------------------------------------------- /docs-fragments/pillar/data/data-governance/data-management-policy/levels.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress, describe the 5 maturity levels of this capability 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/data/data-governance/data-management-policy/traditional-approach.md: -------------------------------------------------------------------------------- 1 | # Traditional Approach 2 | 3 | !!! warn 4 | 5 | Work in progress. 6 | Explain how things are done today in a non-EKG context 7 | -------------------------------------------------------------------------------- /docs-fragments/pillar/data/data-governance/data-management-policy/use-cases.md: -------------------------------------------------------------------------------- 1 | # Use Cases 2 | 3 | !!! warn 4 | 5 | Work in progress. 6 | 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/](https://catalog.ekgf.org/use-case/).. 7 | -------------------------------------------------------------------------------- /docs-fragments/pillar/data/data-governance/data-management-policy/value.md: -------------------------------------------------------------------------------- 1 | # Value 2 | 3 | !!! warn 4 | 5 | Work in progress. 6 | Explain how EKG contributes value and how this capability or capability- 7 | enables higher levels of maturity for the EKG (which in turn provides more value to the business) 8 | -------------------------------------------------------------------------------- /docs-fragments/pillar/data/data-governance/operating-model/background-and-intro.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/data/data-governance/operating-model/dimensions.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress, this is just the results of an initial 4 | brainstorm session, needs to be worked out 5 | 6 | 1. Is your business vision machine-readable? Scale: yes/no 7 | 2. Is there a link between your business vision and your EKG strategy? 8 | -------------------------------------------------------------------------------- /docs-fragments/pillar/data/data-governance/operating-model/ekg-approach.md: -------------------------------------------------------------------------------- 1 | # EKG Approach 2 | 3 | !!! warn 4 | 5 | Work in progress. 6 | Explain how the given Capability or Capability Area would look like 7 | in a mature EKG context. 8 | -------------------------------------------------------------------------------- /docs-fragments/pillar/data/data-governance/operating-model/levels.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress, describe the 5 maturity levels of this capability 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/data/data-governance/operating-model/traditional-approach.md: -------------------------------------------------------------------------------- 1 | # Traditional Approach 2 | 3 | !!! warn 4 | 5 | Work in progress. 6 | Explain how things are done today in a non-EKG context 7 | -------------------------------------------------------------------------------- /docs-fragments/pillar/data/data-governance/operating-model/use-cases.md: -------------------------------------------------------------------------------- 1 | # Use Cases 2 | 3 | !!! warn 4 | 5 | Work in progress. 6 | 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/](https://catalog.ekgf.org/use-case/).. 7 | -------------------------------------------------------------------------------- /docs-fragments/pillar/data/data-governance/operating-model/value.md: -------------------------------------------------------------------------------- 1 | # Value 2 | 3 | !!! warn 4 | 5 | Work in progress. 6 | Explain how EKG contributes value and how this capability or capability- 7 | enables higher levels of maturity for the EKG (which in turn provides more value to the business) 8 | -------------------------------------------------------------------------------- /docs-fragments/pillar/data/data-governance/risk-and-control-framework/background-and-intro.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress 4 | 5 | !!! note 6 | 7 | The EKG Platform Team is about the delivery aspects of delivering new technical functionality in the 8 | service layer that manages the EKG aka the [EKG/Platform](https://method.ekgf.org/vocab/ekg-platform/). 9 | This is not about managing the "EKG Center of Excellence" as a whole. 10 | -------------------------------------------------------------------------------- /docs-fragments/pillar/data/data-governance/risk-and-control-framework/ekg-approach.md: -------------------------------------------------------------------------------- 1 | # EKG Approach 2 | 3 | !!! warn 4 | 5 | Work in progress. 6 | Explain how the given Capability or Capability Area would look like 7 | in a mature EKG context. 8 | -------------------------------------------------------------------------------- /docs-fragments/pillar/data/data-governance/risk-and-control-framework/traditional-approach.md: -------------------------------------------------------------------------------- 1 | # Traditional Approach 2 | 3 | !!! warn 4 | 5 | Work in progress. 6 | Explain how things are done today in a non-EKG context 7 | -------------------------------------------------------------------------------- /docs-fragments/pillar/data/data-governance/risk-and-control-framework/use-cases.md: -------------------------------------------------------------------------------- 1 | # Use Cases 2 | 3 | !!! warn 4 | 5 | Work in progress. 6 | 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/](https://catalog.ekgf.org/use-case/).. 7 | -------------------------------------------------------------------------------- /docs-fragments/pillar/data/data-governance/risk-and-control-framework/value.md: -------------------------------------------------------------------------------- 1 | # Value 2 | 3 | !!! warn 4 | 5 | Work in progress. 6 | Explain how EKG contributes value and how this capability or capability- 7 | enables higher levels of maturity for the EKG (which in turn provides more value to the business) 8 | -------------------------------------------------------------------------------- /docs-fragments/pillar/data/data-quality/business-rules/background-and-intro.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/data/data-quality/business-rules/dimensions.md: -------------------------------------------------------------------------------- 1 | 2 | - Are the data integration activities, their systems, repositories, and connections 3 | known and tracked 4 | - Are data integration activities linked to data inventory, business glossaries, and data models 5 | - Are all data integration input and output datasets documented, tracked, and governed 6 | - Are there reusable standards and defined business rules for performing data integration 7 | - Are data integration patterns, tools, and technologies defined, governed, and used 8 | - Has the firm established a central data integration function (i.e. integration 9 | Center of Excellence) to manage ETL across both internal and external data pipelines 10 | -------------------------------------------------------------------------------- /docs-fragments/pillar/data/data-quality/business-rules/ekg-approach.md: -------------------------------------------------------------------------------- 1 | # EKG Approach 2 | 3 | !!! warn 4 | 5 | Work in progress. 6 | Explain how the given Capability or Capability Area would look like 7 | in a mature EKG context. 8 | -------------------------------------------------------------------------------- /docs-fragments/pillar/data/data-quality/business-rules/traditional-approach.md: -------------------------------------------------------------------------------- 1 | # Traditional Approach 2 | 3 | !!! warn 4 | 5 | Work in progress. 6 | Explain how things are done today in a non-EKG context 7 | -------------------------------------------------------------------------------- /docs-fragments/pillar/data/data-quality/business-rules/use-cases.md: -------------------------------------------------------------------------------- 1 | # Use Cases 2 | 3 | !!! warn 4 | 5 | Work in progress. 6 | 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/](https://catalog.ekgf.org/use-case/).. 7 | -------------------------------------------------------------------------------- /docs-fragments/pillar/data/data-quality/business-rules/value.md: -------------------------------------------------------------------------------- 1 | # Value 2 | 3 | !!! warn 4 | 5 | Work in progress. 6 | Explain how EKG contributes value and how this capability or capability- 7 | enables higher levels of maturity for the EKG (which in turn provides more value to the business) 8 | -------------------------------------------------------------------------------- /docs-fragments/pillar/data/data-strategy/business-case/background-and-intro.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/data/data-strategy/business-case/dimensions.md: -------------------------------------------------------------------------------- 1 | 2 | - Do one or more _data inventories_ exist 3 | - Is the inventory based on _defined standards_ (for both meaning and format) 4 | - Is defined and in-scope data (both breadth and depth) covered in the inventories 5 | - Is the data inventory linked to _sources of record (SORs)_ and _authorized data distribution points_ 6 | - Is the inventory linked to the _business meaning_ of the data and expressed using standards 7 | - Is the creation and maintenance of the data inventory mandated by policy and incorporated 8 | into the data strategy 9 | - Is the quality of the content in the inventory measured, reported to involved stakeholders, 10 | and used for process enhancement 11 | -------------------------------------------------------------------------------- /docs-fragments/pillar/data/data-strategy/business-case/ekg-approach.md: -------------------------------------------------------------------------------- 1 | # EKG Approach 2 | 3 | !!! warn 4 | 5 | Work in progress. 6 | Explain how the given Capability or Capability Area would look like 7 | in a mature EKG context. 8 | -------------------------------------------------------------------------------- /docs-fragments/pillar/data/data-strategy/business-case/traditional-approach.md: -------------------------------------------------------------------------------- 1 | # Traditional Approach 2 | 3 | !!! warn 4 | 5 | Work in progress. 6 | Explain how things are done today in a non-EKG context 7 | -------------------------------------------------------------------------------- /docs-fragments/pillar/data/data-strategy/business-case/use-cases.md: -------------------------------------------------------------------------------- 1 | # Use Cases 2 | 3 | !!! warn 4 | 5 | Work in progress. 6 | 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/](https://catalog.ekgf.org/use-case/).. 7 | -------------------------------------------------------------------------------- /docs-fragments/pillar/data/data-strategy/business-case/value.md: -------------------------------------------------------------------------------- 1 | # Value 2 | 3 | !!! warn 4 | 5 | Work in progress. 6 | Explain how EKG contributes value and how this capability or capability- 7 | enables higher levels of maturity for the EKG (which in turn provides more value to the business) 8 | -------------------------------------------------------------------------------- /docs-fragments/pillar/data/data-strategy/goals-and-objectives/background-and-intro.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/data/data-strategy/goals-and-objectives/dimensions.md: -------------------------------------------------------------------------------- 1 | 2 | - Are critical data elements identified, verified and prioritized for specific 3 | use cases and applications 4 | - How is the organization managing the distinctions between granular data attributes and 5 | derived/calculated business concepts 6 | - Is the inventory of critical data elements implemented and linked to how the 7 | data is being consumed 8 | - Are critical business elements connected to business glossaries, ontologies, 9 | _systems of record (SORs)_ and _authorized distribution points_ 10 | - Is the front-to-back flow of data defined, validated and linked to the designations of 11 | critical data 12 | - Are the governance mechanisms for managing critical data defined and operational 13 | -------------------------------------------------------------------------------- /docs-fragments/pillar/data/data-strategy/goals-and-objectives/ekg-approach.md: -------------------------------------------------------------------------------- 1 | # EKG Approach 2 | 3 | !!! warn 4 | 5 | Work in progress. 6 | Explain how the given Capability or Capability Area would look like 7 | in a mature EKG context. 8 | -------------------------------------------------------------------------------- /docs-fragments/pillar/data/data-strategy/goals-and-objectives/levels.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress, describe the 5 maturity levels of this capability 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/data/data-strategy/goals-and-objectives/traditional-approach.md: -------------------------------------------------------------------------------- 1 | # Traditional Approach 2 | 3 | !!! warn 4 | 5 | Work in progress. 6 | Explain how things are done today in a non-EKG context 7 | -------------------------------------------------------------------------------- /docs-fragments/pillar/data/data-strategy/goals-and-objectives/use-cases.md: -------------------------------------------------------------------------------- 1 | # Use Cases 2 | 3 | !!! warn 4 | 5 | Work in progress. 6 | 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/](https://catalog.ekgf.org/use-case/).. 7 | -------------------------------------------------------------------------------- /docs-fragments/pillar/data/data-strategy/goals-and-objectives/value.md: -------------------------------------------------------------------------------- 1 | # Value 2 | 3 | !!! warn 4 | 5 | Work in progress. 6 | Explain how EKG contributes value and how this capability or capability- 7 | enables higher levels of maturity for the EKG (which in turn provides more value to the business) 8 | -------------------------------------------------------------------------------- /docs-fragments/pillar/organization/.gitignore: -------------------------------------------------------------------------------- 1 | capability-area/ 2 | -------------------------------------------------------------------------------- /docs-fragments/pillar/organization/delivery-management/data-movement/dimensions.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/organization/delivery-management/data-movement/ekg-approach.md: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/EKGF/ekg-maturity/9e758a40b367e6bcaf37d89df17e9e0b6e7bdfc4/docs-fragments/pillar/organization/delivery-management/data-movement/ekg-approach.md -------------------------------------------------------------------------------- /docs-fragments/pillar/organization/delivery-management/data-movement/levels.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress. 4 | Describe the five levels of maturity for this Capability. 5 | -------------------------------------------------------------------------------- /docs-fragments/pillar/organization/delivery-management/data-movement/traditional-approach.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress, describe how this capability is possibly being delivered today in a non-EKG context and optionally what the issues are that EKG could or should improve 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/organization/delivery-management/data-movement/use-cases.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | 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/](https://catalog.ekgf.org/use-case/).. 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/organization/delivery-management/data-movement/value.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/organization/delivery-management/dataops-process/background-and-intro.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/organization/delivery-management/dataops-process/dimensions.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/organization/delivery-management/dataops-process/ekg-approach.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress, describe how this capability would be delivered or supported using an EKG approach, 4 | making the link to the "how" i.e. the [EKG/Method](https://method.ekgf.org). 5 | -------------------------------------------------------------------------------- /docs-fragments/pillar/organization/delivery-management/dataops-process/levels.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress. 4 | Describe the five levels of maturity for this Capability. 5 | -------------------------------------------------------------------------------- /docs-fragments/pillar/organization/delivery-management/dataops-process/traditional-approach.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress, describe how this capability is possibly being delivered today in a non-EKG context and optionally what the issues are that EKG could or should improve 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/organization/delivery-management/dataops-process/use-cases.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | 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/](https://catalog.ekgf.org/use-case/).. 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/organization/delivery-management/dataops-process/value.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/organization/delivery-management/ekg-platform-team/background-and-intro.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/organization/delivery-management/ekg-platform-team/dimensions.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/organization/delivery-management/ekg-platform-team/ekg-approach.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress, describe how this capability would be delivered or supported using an EKG approach, 4 | making the link to the "how" i.e. the [EKG/Method](https://method.ekgf.org). 5 | -------------------------------------------------------------------------------- /docs-fragments/pillar/organization/delivery-management/ekg-platform-team/levels.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress. 4 | Describe the five levels of maturity for this Capability. 5 | -------------------------------------------------------------------------------- /docs-fragments/pillar/organization/delivery-management/ekg-platform-team/traditional-approach.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress, describe how this capability is possibly being delivered today in a non-EKG context and optionally what the issues are that EKG could or should improve 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/organization/delivery-management/ekg-platform-team/use-cases.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | 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/](https://catalog.ekgf.org/use-case/).. 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/organization/delivery-management/ekg-platform-team/value.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/organization/delivery-management/ontologies-and-mapping/dimensions.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/organization/delivery-management/ontologies-and-mapping/ekg-approach.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress, describe how this capability would be delivered or supported using an EKG approach, 4 | making the link to the "how" i.e. the [EKG/Method](https://method.ekgf.org). 5 | -------------------------------------------------------------------------------- /docs-fragments/pillar/organization/delivery-management/ontologies-and-mapping/levels.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress. 4 | Describe the five levels of maturity for this Capability. 5 | -------------------------------------------------------------------------------- /docs-fragments/pillar/organization/delivery-management/ontologies-and-mapping/traditional-approach.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress, describe how this capability is possibly being delivered today in a non-EKG context and optionally what the issues are that EKG could or should improve 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/organization/delivery-management/ontologies-and-mapping/use-cases.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | 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/](https://catalog.ekgf.org/use-case/).. 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/organization/delivery-management/ontologies-and-mapping/value.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/organization/delivery-management/user-interface-and-access/background-and-intro.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/organization/delivery-management/user-interface-and-access/dimensions.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/organization/delivery-management/user-interface-and-access/ekg-approach.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress, describe how this capability would be delivered or supported using an EKG approach, 4 | making the link to the "how" i.e. the [EKG/Method](https://method.ekgf.org). 5 | -------------------------------------------------------------------------------- /docs-fragments/pillar/organization/delivery-management/user-interface-and-access/levels.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress. 4 | Describe the five levels of maturity for this Capability. 5 | -------------------------------------------------------------------------------- /docs-fragments/pillar/organization/delivery-management/user-interface-and-access/traditional-approach.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress, describe how this capability is possibly being delivered today in a non-EKG context and optionally what the issues are that EKG could or should improve 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/organization/delivery-management/user-interface-and-access/use-cases.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | 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/](https://catalog.ekgf.org/use-case/).. 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/organization/delivery-management/user-interface-and-access/value.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/organization/executive-leadership/funding-and-resources/background-and-intro.md: -------------------------------------------------------------------------------- 1 | To achieve the level of product strategy maturity, necessary to continuously 2 | recompose their business, organizations must prioritize funding for EKG development. 3 | This includes investing in the necessary technology, human resources, 4 | and ongoing monitoring and evaluation efforts to ensure that the EKG continues 5 | to provide value and remains relevant in the face of changing business needs and circumstances. 6 | Additionally, the EKG must be designed to be flexible and adaptable, 7 | enabling the organization to easily recompose their business via mergers, 8 | acquisitions, joint-ventures, and reorganizations without disrupting operations 9 | or losing critical knowledge and customer loyalty. 10 | By prioritizing strategic funding for EKG development and taking a proactive approach 11 | to business recomposition, organizations can position themselves for long-term success 12 | in today's rapidly changing business environment. 13 | -------------------------------------------------------------------------------- /docs-fragments/pillar/organization/executive-leadership/funding-and-resources/dimensions.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/organization/executive-leadership/funding-and-resources/ekg-approach.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress, describe how this capability would be delivered or supported using an EKG approach, 4 | making the link to the "how" i.e. the [EKG/Method](https://method.ekgf.org). 5 | -------------------------------------------------------------------------------- /docs-fragments/pillar/organization/executive-leadership/funding-and-resources/levels.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress. 4 | Describe the five levels of maturity for this Capability. 5 | -------------------------------------------------------------------------------- /docs-fragments/pillar/organization/executive-leadership/funding-and-resources/traditional-approach.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress, describe how this capability is possibly being delivered today in a non-EKG context and optionally what the issues are that EKG could or should improve 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/organization/executive-leadership/funding-and-resources/use-cases.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | 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/](https://catalog.ekgf.org/use-case/).. 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/organization/executive-leadership/funding-and-resources/value.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/organization/executive-leadership/organizational-governance/dimensions.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/organization/executive-leadership/organizational-governance/ekg-approach.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress, describe how this capability would be delivered or supported using an EKG approach, 4 | making the link to the "how" i.e. the [EKG/Method](https://method.ekgf.org). 5 | -------------------------------------------------------------------------------- /docs-fragments/pillar/organization/executive-leadership/organizational-governance/levels.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress. 4 | Describe the five levels of maturity for this Capability. 5 | -------------------------------------------------------------------------------- /docs-fragments/pillar/organization/executive-leadership/organizational-governance/traditional-approach.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress, describe how this capability is possibly being delivered today in a non-EKG context and optionally what the issues are that EKG could or should improve 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/organization/executive-leadership/organizational-governance/use-cases.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | 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/](https://catalog.ekgf.org/use-case/).. 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/organization/executive-leadership/organizational-governance/value.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/organization/executive-leadership/organizational-policies/background-and-intro.md: -------------------------------------------------------------------------------- 1 | Organizational policies, including both business policies and applicable regulations, 2 | play a critical role in guiding an enterprise's decision-making processes. 3 | With the rise of EKG as a powerful tool for managing data and business processes, 4 | it becomes increasingly important to ensure that these policies are enforced 5 | in the context of every use case that an EKG operates in. 6 | 7 | More mature enterprises, especially those in highly regulated industries, 8 | will become "policy-driven organizations," leveraging EKG to facilitate the 9 | automated enforcement of policies across the entire business. 10 | These policies can include data governance and management policies, 11 | such as Entitlement Policies, Data Sovereignty Policies, and Data Lifecycle Policies, 12 | as well as business policies that define a wide range of parameters, limits, and constraints. 13 | By translating policies into machine-readable formats and mapping them to specific use cases, 14 | EKG can help ensure that all relevant policies are enforced consistently and 15 | automatically across the entire enterprise. 16 | -------------------------------------------------------------------------------- /docs-fragments/pillar/organization/executive-leadership/organizational-policies/dimensions.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/organization/executive-leadership/organizational-policies/ekg-approach.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress, describe how this capability would be delivered or supported using an EKG approach, 4 | making the link to the "how" i.e. the [EKG/Method](https://method.ekgf.org). 5 | -------------------------------------------------------------------------------- /docs-fragments/pillar/organization/executive-leadership/organizational-policies/levels.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress. 4 | Describe the five levels of maturity for this Capability. 5 | -------------------------------------------------------------------------------- /docs-fragments/pillar/organization/executive-leadership/organizational-policies/traditional-approach.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress, describe how this capability is possibly being delivered today in a non-EKG context and optionally what the issues are that EKG could or should improve 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/organization/executive-leadership/organizational-policies/use-cases.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | 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/](https://catalog.ekgf.org/use-case/).. 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/organization/executive-leadership/organizational-policies/value.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/organization/executive-leadership/organizational-processes/dimensions.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/organization/executive-leadership/organizational-processes/ekg-approach.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress, describe how this capability would be delivered or supported using an EKG approach, 4 | making the link to the "how" i.e. the [EKG/Method](https://method.ekgf.org). 5 | -------------------------------------------------------------------------------- /docs-fragments/pillar/organization/executive-leadership/organizational-processes/levels.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress. 4 | Describe the five levels of maturity for this Capability. 5 | -------------------------------------------------------------------------------- /docs-fragments/pillar/organization/executive-leadership/organizational-processes/traditional-approach.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress, describe how this capability is possibly being delivered today in a non-EKG context and optionally what the issues are that EKG could or should improve 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/organization/executive-leadership/organizational-processes/use-cases.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | 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/](https://catalog.ekgf.org/use-case/).. 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/organization/executive-leadership/organizational-processes/value.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/organization/executive-leadership/organizational-strategy/dimensions.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/organization/executive-leadership/organizational-strategy/ekg-approach.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress, describe how this capability would be delivered or supported using an EKG approach, 4 | making the link to the "how" i.e. the [EKG/Method](https://method.ekgf.org). 5 | -------------------------------------------------------------------------------- /docs-fragments/pillar/organization/executive-leadership/organizational-strategy/levels.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress. 4 | Describe the five levels of maturity for this Capability. 5 | -------------------------------------------------------------------------------- /docs-fragments/pillar/organization/executive-leadership/organizational-strategy/traditional-approach.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress, describe how this capability is possibly being delivered today in a non-EKG context and optionally what the issues are that EKG could or should improve 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/organization/executive-leadership/organizational-strategy/use-cases.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | 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/](https://catalog.ekgf.org/use-case/).. 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/organization/executive-leadership/organizational-strategy/value.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/organization/executive-leadership/technology-requirements/background-and-intro.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/organization/executive-leadership/technology-requirements/dimensions.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/organization/executive-leadership/technology-requirements/ekg-approach.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress, describe how this capability would be delivered or supported using an EKG approach, 4 | making the link to the "how" i.e. the [EKG/Method](https://method.ekgf.org). 5 | -------------------------------------------------------------------------------- /docs-fragments/pillar/organization/executive-leadership/technology-requirements/levels.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress. 4 | Describe the five levels of maturity for this Capability. 5 | -------------------------------------------------------------------------------- /docs-fragments/pillar/organization/executive-leadership/technology-requirements/traditional-approach.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress, describe how this capability is possibly being delivered today in a non-EKG context and optionally what the issues are that EKG could or should improve 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/organization/executive-leadership/technology-requirements/use-cases.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | 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/](https://catalog.ekgf.org/use-case/).. 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/organization/executive-leadership/technology-requirements/value.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/organization/organizational-capabilities/control-functions/dimensions.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/organization/organizational-capabilities/control-functions/ekg-approach.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress, describe how this capability would be delivered or supported using an EKG approach, 4 | making the link to the "how" i.e. the [EKG/Method](https://method.ekgf.org). 5 | -------------------------------------------------------------------------------- /docs-fragments/pillar/organization/organizational-capabilities/control-functions/levels.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress. 4 | Describe the five levels of maturity for this Capability. 5 | -------------------------------------------------------------------------------- /docs-fragments/pillar/organization/organizational-capabilities/control-functions/traditional-approach.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress, describe how this capability is possibly being delivered today in a non-EKG context and optionally what the issues are that EKG could or should improve 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/organization/organizational-capabilities/control-functions/use-cases.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | 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/](https://catalog.ekgf.org/use-case/).. 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/organization/organizational-capabilities/control-functions/value.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/organization/organizational-capabilities/knowledge-sharing/background-and-intro.md: -------------------------------------------------------------------------------- 1 | _Knowledge Sharing_ is the ability of the organization to facilitate effective 2 | collaboration and exchange of knowledge among employees. 3 | 4 | It involves creating a culture of collaboration, leveraging the 5 | Enterprise Knowledge Graph as a centralized source of knowledge, 6 | defining proper KPIs and KRIs around a method-based approach to knowledge sharing, 7 | involving key personas such as subject matter experts (SMEs) and relevant stakeholders, 8 | supporting learning initiatives, recognizing and incentivizing knowledge sharing, 9 | establishing communities of practice, and implementing governance. 10 | Through Knowledge Sharing, organizations tap into collective expertise, drive innovation, 11 | improve decision-making, and enhance overall performance, ensuring that all the right 12 | personas and stakeholders are part of the knowledge sharing process. 13 | -------------------------------------------------------------------------------- /docs-fragments/pillar/organization/organizational-capabilities/knowledge-sharing/dimensions.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/organization/organizational-capabilities/knowledge-sharing/ekg-approach.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress, describe how this capability would be delivered or supported using an EKG approach, 4 | making the link to the "how" i.e. the [EKG/Method](https://method.ekgf.org). 5 | -------------------------------------------------------------------------------- /docs-fragments/pillar/organization/organizational-capabilities/knowledge-sharing/levels.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress. 4 | Describe the five levels of maturity for this Capability. 5 | -------------------------------------------------------------------------------- /docs-fragments/pillar/organization/organizational-capabilities/knowledge-sharing/traditional-approach.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress, describe how this capability is possibly being delivered today in a non-EKG context and optionally what the issues are that EKG could or should improve 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/organization/organizational-capabilities/knowledge-sharing/use-cases.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | 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/](https://catalog.ekgf.org/use-case/).. 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/organization/organizational-capabilities/knowledge-sharing/value.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/organization/organizational-capabilities/talent-management/dimensions.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/organization/organizational-capabilities/talent-management/ekg-approach.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress, describe how this capability would be delivered or supported using an EKG approach, 4 | making the link to the "how" i.e. the [EKG/Method](https://method.ekgf.org). 5 | -------------------------------------------------------------------------------- /docs-fragments/pillar/organization/organizational-capabilities/talent-management/levels.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress. 4 | Describe the five levels of maturity for this Capability. 5 | -------------------------------------------------------------------------------- /docs-fragments/pillar/organization/organizational-capabilities/talent-management/traditional-approach.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress, describe how this capability is possibly being delivered today in a non-EKG context and optionally what the issues are that EKG could or should improve 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/organization/organizational-capabilities/talent-management/use-cases.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | 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/](https://catalog.ekgf.org/use-case/).. 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/organization/organizational-capabilities/talent-management/value.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/organization/organizational-capabilities/vendor-management/dimensions.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/organization/organizational-capabilities/vendor-management/ekg-approach.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress. 4 | Explain how the given Capability or Capability Area would look like 5 | in a mature EKG context. 6 | -------------------------------------------------------------------------------- /docs-fragments/pillar/organization/organizational-capabilities/vendor-management/levels.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress. 4 | Describe the five levels of maturity for this Capability. 5 | -------------------------------------------------------------------------------- /docs-fragments/pillar/organization/organizational-capabilities/vendor-management/traditional-approach.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress. 4 | Explain how things are done today in a non-EKG context 5 | -------------------------------------------------------------------------------- /docs-fragments/pillar/organization/organizational-capabilities/vendor-management/use-cases.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress. 4 | 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/](https://catalog.ekgf.org/use-case/).. 5 | -------------------------------------------------------------------------------- /docs-fragments/pillar/organization/organizational-capabilities/vendor-management/value.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress. 4 | Explain how EKG contributes value and how this capability or capability- 5 | enables higher levels of maturity for the EKG (which in turn provides more value to the business) 6 | -------------------------------------------------------------------------------- /docs-fragments/pillar/organization/organizational-culture/agility-and-innovation/dimensions.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/organization/organizational-culture/agility-and-innovation/ekg-approach.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress, describe how this capability would be delivered or supported using an EKG approach, 4 | making the link to the "how" i.e. the [EKG/Method](https://method.ekgf.org). 5 | -------------------------------------------------------------------------------- /docs-fragments/pillar/organization/organizational-culture/agility-and-innovation/levels.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress. 4 | Describe the five levels of maturity for this Capability. 5 | -------------------------------------------------------------------------------- /docs-fragments/pillar/organization/organizational-culture/agility-and-innovation/traditional-approach.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress, describe how this capability is possibly being delivered today in a non-EKG context and optionally what the issues are that EKG could or should improve 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/organization/organizational-culture/agility-and-innovation/use-cases.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | 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/](https://catalog.ekgf.org/use-case/).. 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/organization/organizational-culture/agility-and-innovation/value.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/organization/organizational-culture/ecosystem-collaboration/dimensions.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/organization/organizational-culture/ecosystem-collaboration/ekg-approach.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress, describe how this capability would be delivered or supported using an EKG approach, 4 | making the link to the "how" i.e. the [EKG/Method](https://method.ekgf.org). 5 | -------------------------------------------------------------------------------- /docs-fragments/pillar/organization/organizational-culture/ecosystem-collaboration/levels.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress. 4 | Describe the five levels of maturity for this Capability. 5 | -------------------------------------------------------------------------------- /docs-fragments/pillar/organization/organizational-culture/ecosystem-collaboration/traditional-approach.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress, describe how this capability is possibly being delivered today in a non-EKG context and optionally what the issues are that EKG could or should improve 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/organization/organizational-culture/ecosystem-collaboration/use-cases.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | 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/](https://catalog.ekgf.org/use-case/).. 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/organization/organizational-culture/ecosystem-collaboration/value.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/organization/organizational-culture/implementation-approach/dimensions.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/organization/organizational-culture/implementation-approach/ekg-approach.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress, describe how this capability would be delivered or supported using an EKG approach, 4 | making the link to the "how" i.e. the [EKG/Method](https://method.ekgf.org). 5 | -------------------------------------------------------------------------------- /docs-fragments/pillar/organization/organizational-culture/implementation-approach/levels.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress. 4 | Describe the five levels of maturity for this Capability. 5 | -------------------------------------------------------------------------------- /docs-fragments/pillar/organization/organizational-culture/implementation-approach/traditional-approach.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress, describe how this capability is possibly being delivered today in a non-EKG context and optionally what the issues are that EKG could or should improve 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/organization/organizational-culture/implementation-approach/use-cases.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | 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/](https://catalog.ekgf.org/use-case/).. 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/organization/organizational-culture/implementation-approach/value.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/organization/product-ownership/delivery-process/background-and-intro.md: -------------------------------------------------------------------------------- 1 | Delivery process is a mature capability that an organization needs to have in place. 2 | It involves a well-defined process for developing and delivering products, services, 3 | or solutions that meet the needs of customers and stakeholders. 4 | This process typically includes a project management framework, with well-defined roles, 5 | responsibilities, and deliverables. It also includes quality assurance and testing, 6 | with a focus on delivering a high-quality end product. 7 | In the context of an EKG, the delivery process also involves ensuring that the use cases 8 | are properly implemented, integrated, and tested across the entire ecosystem, 9 | and that they adhere to the principles and standards of the EKG framework. 10 | This requires a well-coordinated effort across the organization, 11 | with effective communication and collaboration between different teams and stakeholders. 12 | -------------------------------------------------------------------------------- /docs-fragments/pillar/organization/product-ownership/delivery-process/dimensions.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/organization/product-ownership/delivery-process/ekg-approach.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress, describe how this capability would be delivered or supported using an EKG approach, 4 | making the link to the "how" i.e. the [EKG/Method](https://method.ekgf.org). 5 | -------------------------------------------------------------------------------- /docs-fragments/pillar/organization/product-ownership/delivery-process/levels.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress. 4 | Describe the five levels of maturity for this Capability. 5 | -------------------------------------------------------------------------------- /docs-fragments/pillar/organization/product-ownership/delivery-process/traditional-approach.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress, describe how this capability is possibly being delivered today in a non-EKG context and optionally what the issues are that EKG could or should improve 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/organization/product-ownership/delivery-process/use-cases.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | 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/](https://catalog.ekgf.org/use-case/).. 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/organization/product-ownership/delivery-process/value.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/organization/product-ownership/funding-and-budget/background-and-intro.md: -------------------------------------------------------------------------------- 1 | In the context of an EKG, the funding and budget capability is different than that 2 | of traditional siloed solutions. 3 | With siloed solutions, funding and budgeting are directly related to solving a 4 | given problem, usually short-term. 5 | However, in the EKG context, there is a major distinction. 6 | The separation of "demand and supply" of information allows for much higher levels 7 | of reuse and flexibility of use cases, with a much broader usage of each use case 8 | and potentially more stakeholders per use case. 9 | This means that funding and budgeting must be approached with a more strategic 10 | and long-term view, as each use case can have a much wider impact on the organization. 11 | Therefore, the funding and budget capability in the context of an EKG is crucial 12 | for the success of the overall information strategy, 13 | and should be aligned with the organization's long-term goals and objectives. 14 | -------------------------------------------------------------------------------- /docs-fragments/pillar/organization/product-ownership/funding-and-budget/dimensions.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/organization/product-ownership/funding-and-budget/ekg-approach.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress, describe how this capability would be delivered or supported using an EKG approach, 4 | making the link to the "how" i.e. the [EKG/Method](https://method.ekgf.org). 5 | -------------------------------------------------------------------------------- /docs-fragments/pillar/organization/product-ownership/funding-and-budget/levels.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress. 4 | Describe the five levels of maturity for this Capability. 5 | -------------------------------------------------------------------------------- /docs-fragments/pillar/organization/product-ownership/funding-and-budget/traditional-approach.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress, describe how this capability is possibly being delivered today in a non-EKG context and optionally what the issues are that EKG could or should improve 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/organization/product-ownership/funding-and-budget/use-cases.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | 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/](https://catalog.ekgf.org/use-case/).. 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/organization/product-ownership/funding-and-budget/value.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/organization/product-ownership/measurement-criteria/background-and-intro.md: -------------------------------------------------------------------------------- 1 | The measurement criteria capability focuses on defining and implementing 2 | metrics and criteria to evaluate the effectiveness and success of the EKG. 3 | This includes both business metrics, such as ROI, customer satisfaction, 4 | and time to market, as well as technical metrics, such as data quality, 5 | system availability, and response time. 6 | The measurement criteria capability also involves establishing benchmarks 7 | and targets for each metric, monitoring and analyzing the data to identify 8 | areas for improvement, and continuously refining the metrics and criteria 9 | based on feedback and changing business needs. 10 | This capability is essential for ensuring that the EKG is meeting its 11 | objectives and delivering value to the organization. 12 | -------------------------------------------------------------------------------- /docs-fragments/pillar/organization/product-ownership/measurement-criteria/dimensions.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/organization/product-ownership/measurement-criteria/ekg-approach.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress, describe how this capability would be delivered or supported using an EKG approach, 4 | making the link to the "how" i.e. the [EKG/Method](https://method.ekgf.org). 5 | -------------------------------------------------------------------------------- /docs-fragments/pillar/organization/product-ownership/measurement-criteria/levels.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress. 4 | Describe the five levels of maturity for this Capability. 5 | -------------------------------------------------------------------------------- /docs-fragments/pillar/organization/product-ownership/measurement-criteria/traditional-approach.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress, describe how this capability is possibly being delivered today in a non-EKG context and optionally what the issues are that EKG could or should improve 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/organization/product-ownership/measurement-criteria/use-cases.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | 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/](https://catalog.ekgf.org/use-case/).. 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/organization/product-ownership/measurement-criteria/value.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/organization/product-ownership/team-requirements-management/background-and-intro.md: -------------------------------------------------------------------------------- 1 | The team requirements management capability in the context of EKG product ownership 2 | is critical for ensuring that the right subject matter experts (SMEs) are involved in 3 | developing and maintaining use cases. 4 | The product owner is responsible for assessing the expertise of team members, 5 | including business architects and use case tree architects. 6 | By bringing together both the pure business view and a broader perspective, 7 | the team can develop use cases that accurately reflect the needs of the organization. 8 | This ensures that the EKG remains relevant and effective in supporting the organization's objectives. 9 | -------------------------------------------------------------------------------- /docs-fragments/pillar/organization/product-ownership/team-requirements-management/dimensions.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/organization/product-ownership/team-requirements-management/ekg-approach.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress, describe how this capability would be delivered or supported using an EKG approach, 4 | making the link to the "how" i.e. the [EKG/Method](https://method.ekgf.org). 5 | -------------------------------------------------------------------------------- /docs-fragments/pillar/organization/product-ownership/team-requirements-management/levels.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress. 4 | Describe the five levels of maturity for this Capability. 5 | -------------------------------------------------------------------------------- /docs-fragments/pillar/organization/product-ownership/team-requirements-management/traditional-approach.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress, describe how this capability is possibly being delivered today in a non-EKG context and optionally what the issues are that EKG could or should improve 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/organization/product-ownership/team-requirements-management/use-cases.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | 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/](https://catalog.ekgf.org/use-case/).. 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/organization/product-ownership/team-requirements-management/value.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/organization/product-ownership/use-case-requirements/background-and-intro.md: -------------------------------------------------------------------------------- 1 | Use cases are essentially representations of information demand, 2 | capturing the specific needs of various business functions or processes within an organization. 3 | They should be modeled in a way that is as independent as possible from the supply-side details, 4 | meaning the specifics of the [semantic data products](https://data-product.ekgf.org) and 5 | the semantic model used to fulfill the demand. 6 | When viewed from the demand-side perspective, an EKG enables an organization to identify 7 | the most important and valuable use cases for its business and to prioritize them accordingly. 8 | By understanding the context of these use cases and the specific requirements they entail, 9 | the organization can make better decisions around data management and prioritize investments 10 | in the EKG infrastructure to best support these demands. 11 | -------------------------------------------------------------------------------- /docs-fragments/pillar/organization/product-ownership/use-case-requirements/dimensions.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress, describe the various measurable dimensions and concerns related to this capability 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/organization/product-ownership/use-case-requirements/ekg-approach.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress, describe how this capability would be delivered or supported using an EKG approach, 4 | making the link to the "how" i.e. the [EKG/Method](https://method.ekgf.org). 5 | -------------------------------------------------------------------------------- /docs-fragments/pillar/organization/product-ownership/use-case-requirements/levels.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress. 4 | Describe the five levels of maturity for this Capability. 5 | -------------------------------------------------------------------------------- /docs-fragments/pillar/organization/product-ownership/use-case-requirements/traditional-approach.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress, describe how this capability is possibly being delivered today in a non-EKG context and optionally what the issues are that EKG could or should improve 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/organization/product-ownership/use-case-requirements/use-cases.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | 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/](https://catalog.ekgf.org/use-case/).. 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/organization/product-ownership/use-case-requirements/value.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress. 4 | Explain how EKG contributes value and how this capability or capability- 5 | enables higher levels of maturity for the EKG (which in turn provides more value to the business) 6 | -------------------------------------------------------------------------------- /docs-fragments/pillar/technology/.gitignore: -------------------------------------------------------------------------------- 1 | capability-area/ 2 | -------------------------------------------------------------------------------- /docs-fragments/pillar/technology/technology-execution/analytics/background-and-intro.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/technology/technology-execution/analytics/dimensions.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/technology/technology-execution/analytics/ekg-approach.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress, describe how this capability would be delivered or supported using an EKG approach, 4 | making the link to the "how" i.e. the [EKG/Method](https://method.ekgf.org). 5 | -------------------------------------------------------------------------------- /docs-fragments/pillar/technology/technology-execution/analytics/levels.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress. 4 | Describe the five levels of maturity for this Capability. 5 | -------------------------------------------------------------------------------- /docs-fragments/pillar/technology/technology-execution/analytics/traditional-approach.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress, describe how this capability is possibly being delivered today in a non-EKG context and optionally what the issues are that EKG could or should improve 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/technology/technology-execution/analytics/use-cases.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | 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/](https://catalog.ekgf.org/use-case/).. 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/technology/technology-execution/analytics/value.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/technology/technology-execution/business-continuity/dimensions.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/technology/technology-execution/business-continuity/ekg-approach.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress, describe how this capability would be delivered or supported using an EKG approach, 4 | making the link to the "how" i.e. the [EKG/Method](https://method.ekgf.org). 5 | -------------------------------------------------------------------------------- /docs-fragments/pillar/technology/technology-execution/business-continuity/levels.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress. 4 | Describe the five levels of maturity for this Capability. 5 | -------------------------------------------------------------------------------- /docs-fragments/pillar/technology/technology-execution/business-continuity/traditional-approach.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress, describe how this capability is possibly being delivered today in a non-EKG context and optionally what the issues are that EKG could or should improve 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/technology/technology-execution/business-continuity/use-cases.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | 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/](https://catalog.ekgf.org/use-case/).. 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/technology/technology-execution/business-continuity/value.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/technology/technology-execution/data-integration/dimensions.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/technology/technology-execution/data-integration/ekg-approach.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress, describe how this capability would be delivered or supported using an EKG approach, 4 | making the link to the "how" i.e. the [EKG/Method](https://method.ekgf.org). 5 | -------------------------------------------------------------------------------- /docs-fragments/pillar/technology/technology-execution/data-integration/levels.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress. 4 | Describe the five levels of maturity for this Capability. 5 | -------------------------------------------------------------------------------- /docs-fragments/pillar/technology/technology-execution/data-integration/traditional-approach.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress, describe how this capability is possibly being delivered today in a non-EKG context and optionally what the issues are that EKG could or should improve 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/technology/technology-execution/data-integration/use-cases.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | 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/](https://catalog.ekgf.org/use-case/).. 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/technology/technology-execution/data-integration/value.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/technology/technology-execution/data-quality-implementation/dimensions.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/technology/technology-execution/data-quality-implementation/ekg-approach.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress, describe how this capability would be delivered or supported using an EKG approach, 4 | making the link to the "how" i.e. the [EKG/Method](https://method.ekgf.org). 5 | -------------------------------------------------------------------------------- /docs-fragments/pillar/technology/technology-execution/data-quality-implementation/levels.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress. 4 | Describe the five levels of maturity for this Capability. 5 | -------------------------------------------------------------------------------- /docs-fragments/pillar/technology/technology-execution/data-quality-implementation/traditional-approach.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress, describe how this capability is possibly being delivered today in a non-EKG context and optionally what the issues are that EKG could or should improve 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/technology/technology-execution/data-quality-implementation/use-cases.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | 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/](https://catalog.ekgf.org/use-case/).. 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/technology/technology-execution/data-quality-implementation/value.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/technology/technology-execution/data-transformation-execution/background-and-intro.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/technology/technology-execution/data-transformation-execution/dimensions.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/technology/technology-execution/data-transformation-execution/ekg-approach.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress, describe how this capability would be delivered or supported using an EKG approach, 4 | making the link to the "how" i.e. the [EKG/Method](https://method.ekgf.org). 5 | -------------------------------------------------------------------------------- /docs-fragments/pillar/technology/technology-execution/data-transformation-execution/levels.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress. 4 | Describe the five levels of maturity for this Capability. 5 | -------------------------------------------------------------------------------- /docs-fragments/pillar/technology/technology-execution/data-transformation-execution/traditional-approach.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress, describe how this capability is possibly being delivered today in a non-EKG context and optionally what the issues are that EKG could or should improve 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/technology/technology-execution/data-transformation-execution/use-cases.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | 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/](https://catalog.ekgf.org/use-case/).. 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/technology/technology-execution/data-transformation-execution/value.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/technology/technology-execution/entitlement-management/background-and-intro.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/technology/technology-execution/entitlement-management/dimensions.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/technology/technology-execution/entitlement-management/ekg-approach.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress, describe how this capability would be delivered or supported using an EKG approach, 4 | making the link to the "how" i.e. the [EKG/Method](https://method.ekgf.org). 5 | -------------------------------------------------------------------------------- /docs-fragments/pillar/technology/technology-execution/entitlement-management/levels.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress. 4 | Describe the five levels of maturity for this Capability. 5 | -------------------------------------------------------------------------------- /docs-fragments/pillar/technology/technology-execution/entitlement-management/traditional-approach.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress, describe how this capability is possibly being delivered today in a non-EKG context and optionally what the issues are that EKG could or should improve 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/technology/technology-execution/entitlement-management/use-cases.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | 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/](https://catalog.ekgf.org/use-case/).. 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/technology/technology-execution/entitlement-management/value.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/technology/technology-execution/identity-resolution/dimensions.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/technology/technology-execution/identity-resolution/ekg-approach.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress, describe how this capability would be delivered or supported using an EKG approach, 4 | making the link to the "how" i.e. the [EKG/Method](https://method.ekgf.org). 5 | -------------------------------------------------------------------------------- /docs-fragments/pillar/technology/technology-execution/identity-resolution/levels.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress. 4 | Describe the five levels of maturity for this Capability. 5 | -------------------------------------------------------------------------------- /docs-fragments/pillar/technology/technology-execution/identity-resolution/traditional-approach.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress, describe how this capability is possibly being delivered today in a non-EKG context and optionally what the issues are that EKG could or should improve 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/technology/technology-execution/identity-resolution/use-cases.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | 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/](https://catalog.ekgf.org/use-case/).. 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/technology/technology-execution/identity-resolution/value.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/technology/technology-execution/inferencing-rules/background-and-intro.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/technology/technology-execution/inferencing-rules/dimensions.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/technology/technology-execution/inferencing-rules/ekg-approach.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress, describe how this capability would be delivered or supported using an EKG approach, 4 | making the link to the "how" i.e. the [EKG/Method](https://method.ekgf.org). 5 | -------------------------------------------------------------------------------- /docs-fragments/pillar/technology/technology-execution/inferencing-rules/levels.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress. 4 | Describe the five levels of maturity for this Capability. 5 | -------------------------------------------------------------------------------- /docs-fragments/pillar/technology/technology-execution/inferencing-rules/traditional-approach.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress, describe how this capability is possibly being delivered today in a non-EKG context and optionally what the issues are that EKG could or should improve 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/technology/technology-execution/inferencing-rules/use-cases.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | 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/](https://catalog.ekgf.org/use-case/).. 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/technology/technology-execution/inferencing-rules/value.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/technology/technology-execution/knowledge-graph-federation/dimensions.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/technology/technology-execution/knowledge-graph-federation/ekg-approach.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress, describe how this capability would be delivered or supported using an EKG approach, 4 | making the link to the "how" i.e. the [EKG/Method](https://method.ekgf.org). 5 | -------------------------------------------------------------------------------- /docs-fragments/pillar/technology/technology-execution/knowledge-graph-federation/levels.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress. 4 | Describe the five levels of maturity for this Capability. 5 | -------------------------------------------------------------------------------- /docs-fragments/pillar/technology/technology-execution/knowledge-graph-federation/traditional-approach.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress, describe how this capability is possibly being delivered today in a non-EKG context and optionally what the issues are that EKG could or should improve 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/technology/technology-execution/knowledge-graph-federation/use-cases.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | 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/](https://catalog.ekgf.org/use-case/).. 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/technology/technology-execution/knowledge-graph-federation/value.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/technology/technology-execution/knowledge-graph-storage-retrieval/dimensions.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/technology/technology-execution/knowledge-graph-storage-retrieval/ekg-approach.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress, describe how this capability would be delivered or supported using an EKG approach, 4 | making the link to the "how" i.e. the [EKG/Method](https://method.ekgf.org). 5 | -------------------------------------------------------------------------------- /docs-fragments/pillar/technology/technology-execution/knowledge-graph-storage-retrieval/levels.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress. 4 | Describe the five levels of maturity for this Capability. 5 | -------------------------------------------------------------------------------- /docs-fragments/pillar/technology/technology-execution/knowledge-graph-storage-retrieval/traditional-approach.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress, describe how this capability is possibly being delivered today in a non-EKG context and optionally what the issues are that EKG could or should improve 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/technology/technology-execution/knowledge-graph-storage-retrieval/use-cases.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | 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/](https://catalog.ekgf.org/use-case/).. 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/technology/technology-execution/knowledge-graph-storage-retrieval/value.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/technology/technology-execution/knowledge-graph-virtualization/background-and-intro.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/technology/technology-execution/knowledge-graph-virtualization/dimensions.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/technology/technology-execution/knowledge-graph-virtualization/ekg-approach.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress, describe how this capability would be delivered or supported using an EKG approach, 4 | making the link to the "how" i.e. the [EKG/Method](https://method.ekgf.org). 5 | -------------------------------------------------------------------------------- /docs-fragments/pillar/technology/technology-execution/knowledge-graph-virtualization/levels.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress. 4 | Describe the five levels of maturity for this Capability. 5 | -------------------------------------------------------------------------------- /docs-fragments/pillar/technology/technology-execution/knowledge-graph-virtualization/traditional-approach.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress, describe how this capability is possibly being delivered today in a non-EKG context and optionally what the issues are that EKG could or should improve 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/technology/technology-execution/knowledge-graph-virtualization/use-cases.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | 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/](https://catalog.ekgf.org/use-case/).. 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/technology/technology-execution/knowledge-graph-virtualization/value.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/technology/technology-execution/llm-ai/dimensions.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress, describe the various measurable dimensions and concerns related to this capability 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/technology/technology-execution/llm-ai/ekg-approach.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress, describe how this capability would be delivered or supported using an EKG approach, 4 | making the link to the "how" i.e. the [EKG/Method](https://method.ekgf.org). 5 | -------------------------------------------------------------------------------- /docs-fragments/pillar/technology/technology-execution/llm-ai/levels.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress. 4 | Describe the five levels of maturity for this Capability. 5 | -------------------------------------------------------------------------------- /docs-fragments/pillar/technology/technology-execution/llm-ai/traditional-approach.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress, describe how this capability is possibly being delivered today in a non-EKG context and optionally what the issues are that EKG could or should improve 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/technology/technology-execution/llm-ai/use-cases.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | 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/](https://catalog.ekgf.org/use-case/).. 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/technology/technology-execution/llm-ai/value.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress. 4 | Explain how EKG contributes value and how this capability or capability- 5 | enables higher levels of maturity for the EKG (which in turn provides more value to the business) 6 | -------------------------------------------------------------------------------- /docs-fragments/pillar/technology/technology-execution/observability/dimensions.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/technology/technology-execution/observability/ekg-approach.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress. 4 | Explain how the given Capability or Capability Area would look like 5 | in a mature EKG context. 6 | -------------------------------------------------------------------------------- /docs-fragments/pillar/technology/technology-execution/observability/levels.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress. 4 | Describe the five levels of maturity for this Capability. 5 | -------------------------------------------------------------------------------- /docs-fragments/pillar/technology/technology-execution/observability/traditional-approach.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress. 4 | Explain how things are done today in a non-EKG context 5 | -------------------------------------------------------------------------------- /docs-fragments/pillar/technology/technology-execution/observability/use-cases.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress. 4 | 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/](https://catalog.ekgf.org/use-case/).. 5 | -------------------------------------------------------------------------------- /docs-fragments/pillar/technology/technology-execution/observability/value.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress. 4 | Explain how EKG contributes value and how this capability or capability- 5 | enables higher levels of maturity for the EKG (which in turn provides more value to the business) 6 | -------------------------------------------------------------------------------- /docs-fragments/pillar/technology/technology-execution/operations/dimensions.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress 4 | 5 | - Have the underlying [principles](https://principles.ekgf.org/principle/) (and challenges) 6 | of data management been established and accepted by involved stakeholders 7 | - Does the _office of data management (ODM)_ have authority to enforce adherence to policy 8 | - Has the data management funding model been established and implemented 9 | - Has the organization identified and recruited stakeholders with sufficient skill sets to 10 | implement the data management program 11 | - Are involved stakeholders held accountable to data management program deliverables 12 | - Has the organization defined and validated the operating models, and workflows necessary 13 | to implement the data management program 14 | - Are metrics and KPIs captured and actively used to improve the data management operating process 15 | - Is the data management operating model audited for compliance and effectiveness 16 | -------------------------------------------------------------------------------- /docs-fragments/pillar/technology/technology-execution/operations/ekg-approach.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress. 4 | Explain how the given Capability or Capability Area would look like 5 | in a mature EKG context. 6 | -------------------------------------------------------------------------------- /docs-fragments/pillar/technology/technology-execution/operations/levels.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress. 4 | Describe the five levels of maturity for this Capability. 5 | -------------------------------------------------------------------------------- /docs-fragments/pillar/technology/technology-execution/operations/traditional-approach.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress. 4 | Explain how things are done today in a non-EKG context 5 | -------------------------------------------------------------------------------- /docs-fragments/pillar/technology/technology-execution/operations/use-cases.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress. 4 | 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/](https://catalog.ekgf.org/use-case/).. 5 | -------------------------------------------------------------------------------- /docs-fragments/pillar/technology/technology-execution/operations/value.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress. 4 | Explain how EKG contributes value and how this capability or capability- 5 | enables higher levels of maturity for the EKG (which in turn provides more value to the business) 6 | -------------------------------------------------------------------------------- /docs-fragments/pillar/technology/technology-strategy/technology-architecture/dimensions.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/technology/technology-strategy/technology-architecture/ekg-approach.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress. 4 | Explain how the given Capability or Capability Area would look like 5 | in a mature EKG context. 6 | -------------------------------------------------------------------------------- /docs-fragments/pillar/technology/technology-strategy/technology-architecture/levels.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress. 4 | Describe the five levels of maturity for this Capability. 5 | -------------------------------------------------------------------------------- /docs-fragments/pillar/technology/technology-strategy/technology-architecture/traditional-approach.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress. 4 | Explain how things are done today in a non-EKG context 5 | -------------------------------------------------------------------------------- /docs-fragments/pillar/technology/technology-strategy/technology-architecture/use-cases.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress. 4 | 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/](https://catalog.ekgf.org/use-case/).. 5 | -------------------------------------------------------------------------------- /docs-fragments/pillar/technology/technology-strategy/technology-architecture/value.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress. 4 | Explain how EKG contributes value and how this capability or capability- 5 | enables higher levels of maturity for the EKG (which in turn provides more value to the business) 6 | -------------------------------------------------------------------------------- /docs-fragments/pillar/technology/user-interface/collaboration/background-and-intro.md: -------------------------------------------------------------------------------- 1 | # Background & Intro 2 | 3 | !!! warn 4 | 5 | Work in progress 6 | -------------------------------------------------------------------------------- /docs-fragments/pillar/technology/user-interface/collaboration/dimensions.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/technology/user-interface/collaboration/ekg-approach.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress. 4 | Explain how the given Capability or Capability Area would look like 5 | in a mature EKG context. 6 | -------------------------------------------------------------------------------- /docs-fragments/pillar/technology/user-interface/collaboration/levels.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress. 4 | Describe the five levels of maturity for this Capability. 5 | -------------------------------------------------------------------------------- /docs-fragments/pillar/technology/user-interface/collaboration/traditional-approach.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress. 4 | Explain how things are done today in a non-EKG context 5 | -------------------------------------------------------------------------------- /docs-fragments/pillar/technology/user-interface/collaboration/use-cases.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress. 4 | 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/](https://catalog.ekgf.org/use-case/).. 5 | -------------------------------------------------------------------------------- /docs-fragments/pillar/technology/user-interface/collaboration/value.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress. 4 | Explain how EKG contributes value and how this capability or capability- 5 | enables higher levels of maturity for the EKG (which in turn provides more value to the business) 6 | -------------------------------------------------------------------------------- /docs-fragments/pillar/technology/user-interface/content-editing/background-and-intro.md: -------------------------------------------------------------------------------- 1 | # Background & Intro 2 | 3 | !!! warn 4 | 5 | Work in progress 6 | -------------------------------------------------------------------------------- /docs-fragments/pillar/technology/user-interface/content-editing/dimensions.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/technology/user-interface/content-editing/ekg-approach.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress. 4 | Explain how the given Capability or Capability Area would look like 5 | in a mature EKG context. 6 | -------------------------------------------------------------------------------- /docs-fragments/pillar/technology/user-interface/content-editing/levels.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress. 4 | Describe the five levels of maturity for this Capability. 5 | -------------------------------------------------------------------------------- /docs-fragments/pillar/technology/user-interface/content-editing/traditional-approach.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress. 4 | Explain how things are done today in a non-EKG context 5 | -------------------------------------------------------------------------------- /docs-fragments/pillar/technology/user-interface/content-editing/use-cases.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress. 4 | 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/](https://catalog.ekgf.org/use-case/).. 5 | -------------------------------------------------------------------------------- /docs-fragments/pillar/technology/user-interface/content-editing/value.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress. 4 | Explain how EKG contributes value and how this capability or capability- 5 | enables higher levels of maturity for the EKG (which in turn provides more value to the business) 6 | -------------------------------------------------------------------------------- /docs-fragments/pillar/technology/user-interface/multilingual-support/background-and-intro.md: -------------------------------------------------------------------------------- 1 | # Background & Intro 2 | 3 | !!! warn 4 | 5 | Work in progress 6 | -------------------------------------------------------------------------------- /docs-fragments/pillar/technology/user-interface/multilingual-support/dimensions.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/technology/user-interface/multilingual-support/ekg-approach.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress. 4 | Explain how the given Capability or Capability Area would look like 5 | in a mature EKG context. 6 | -------------------------------------------------------------------------------- /docs-fragments/pillar/technology/user-interface/multilingual-support/levels.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress. 4 | Describe the five levels of maturity for this Capability. 5 | -------------------------------------------------------------------------------- /docs-fragments/pillar/technology/user-interface/multilingual-support/traditional-approach.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress. 4 | Explain how things are done today in a non-EKG context 5 | -------------------------------------------------------------------------------- /docs-fragments/pillar/technology/user-interface/multilingual-support/use-cases.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress. 4 | 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/](https://catalog.ekgf.org/use-case/).. 5 | -------------------------------------------------------------------------------- /docs-fragments/pillar/technology/user-interface/multilingual-support/value.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress. 4 | Explain how EKG contributes value and how this capability or capability- 5 | enables higher levels of maturity for the EKG (which in turn provides more value to the business) 6 | -------------------------------------------------------------------------------- /docs-fragments/pillar/technology/user-interface/reporting/background-and-intro.md: -------------------------------------------------------------------------------- 1 | # Background & Intro 2 | 3 | !!! warn 4 | 5 | Work in progress 6 | -------------------------------------------------------------------------------- /docs-fragments/pillar/technology/user-interface/reporting/dimensions.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/technology/user-interface/reporting/ekg-approach.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress. 4 | Explain how the given Capability or Capability Area would look like 5 | in a mature EKG context. 6 | -------------------------------------------------------------------------------- /docs-fragments/pillar/technology/user-interface/reporting/levels.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress. 4 | Describe the five levels of maturity for this Capability. 5 | -------------------------------------------------------------------------------- /docs-fragments/pillar/technology/user-interface/reporting/traditional-approach.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress. 4 | Explain how things are done today in a non-EKG context 5 | -------------------------------------------------------------------------------- /docs-fragments/pillar/technology/user-interface/reporting/use-cases.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress. 4 | 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/](https://catalog.ekgf.org/use-case/).. 5 | -------------------------------------------------------------------------------- /docs-fragments/pillar/technology/user-interface/reporting/value.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress. 4 | Explain how EKG contributes value and how this capability or capability- 5 | enables higher levels of maturity for the EKG (which in turn provides more value to the business) 6 | -------------------------------------------------------------------------------- /docs-fragments/pillar/technology/user-interface/search/background-and-intro.md: -------------------------------------------------------------------------------- 1 | # Background & Intro 2 | 3 | !!! warn 4 | 5 | Work in progress 6 | -------------------------------------------------------------------------------- /docs-fragments/pillar/technology/user-interface/search/dimensions.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/technology/user-interface/search/ekg-approach.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress. 4 | Explain how the given Capability or Capability Area would look like 5 | in a mature EKG context. 6 | -------------------------------------------------------------------------------- /docs-fragments/pillar/technology/user-interface/search/levels.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress. 4 | Describe the five levels of maturity for this Capability. 5 | -------------------------------------------------------------------------------- /docs-fragments/pillar/technology/user-interface/search/traditional-approach.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress. 4 | Explain how things are done today in a non-EKG context 5 | -------------------------------------------------------------------------------- /docs-fragments/pillar/technology/user-interface/search/use-cases.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress. 4 | 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/](https://catalog.ekgf.org/use-case/).. 5 | -------------------------------------------------------------------------------- /docs-fragments/pillar/technology/user-interface/search/value.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress. 4 | Explain how EKG contributes value and how this capability or capability- 5 | enables higher levels of maturity for the EKG (which in turn provides more value to the business) 6 | -------------------------------------------------------------------------------- /docs-fragments/pillar/technology/user-interface/visualization/background-and-intro.md: -------------------------------------------------------------------------------- 1 | # Background & Intro 2 | 3 | !!! warn 4 | 5 | Work in progress 6 | -------------------------------------------------------------------------------- /docs-fragments/pillar/technology/user-interface/visualization/dimensions.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress 4 | -------------------------------------------------------------------------------- /docs-fragments/pillar/technology/user-interface/visualization/ekg-approach.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress. 4 | Explain how the given Capability or Capability Area would look like 5 | in a mature EKG context. 6 | -------------------------------------------------------------------------------- /docs-fragments/pillar/technology/user-interface/visualization/levels.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress. 4 | Describe the five levels of maturity for this Capability. 5 | -------------------------------------------------------------------------------- /docs-fragments/pillar/technology/user-interface/visualization/traditional-approach.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress. 4 | Explain how things are done today in a non-EKG context 5 | -------------------------------------------------------------------------------- /docs-fragments/pillar/technology/user-interface/visualization/use-cases.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress. 4 | 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/](https://catalog.ekgf.org/use-case/).. 5 | -------------------------------------------------------------------------------- /docs-fragments/pillar/technology/user-interface/visualization/value.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress. 4 | Explain how EKG contributes value and how this capability or capability- 5 | enables higher levels of maturity for the EKG (which in turn provides more value to the business) 6 | -------------------------------------------------------------------------------- /docs-fragments/template/background-and-intro.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress 4 | -------------------------------------------------------------------------------- /docs-fragments/template/dimensions.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress, describe the various measurable dimensions and concerns related to this capability 4 | -------------------------------------------------------------------------------- /docs-fragments/template/ekg-approach.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress, describe how this capability would be delivered or supported using an EKG approach, 4 | making the link to the "how" i.e. the [EKG/Method](https://method.ekgf.org). 5 | -------------------------------------------------------------------------------- /docs-fragments/template/levels.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress. 4 | Describe the five levels of maturity for this Capability. 5 | -------------------------------------------------------------------------------- /docs-fragments/template/traditional-approach.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress, describe how this capability is possibly being delivered today in a non-EKG context and optionally what the issues are that EKG could or should improve 4 | -------------------------------------------------------------------------------- /docs-fragments/template/use-cases.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | 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/](https://catalog.ekgf.org/use-case/).. 4 | -------------------------------------------------------------------------------- /docs-fragments/template/value.md: -------------------------------------------------------------------------------- 1 | !!! warn 2 | 3 | Work in progress. 4 | Explain how EKG contributes value and how this capability or capability- 5 | enables higher levels of maturity for the EKG (which in turn provides more value to the business) 6 | -------------------------------------------------------------------------------- /docs/.gitignore: -------------------------------------------------------------------------------- 1 | __pycache__/ 2 | index.html 3 | pillar/* 4 | pillar-dev/* 5 | model/ 6 | -------------------------------------------------------------------------------- /docs/.pages.yaml: -------------------------------------------------------------------------------- 1 | nav: 2 | - intro 3 | - ... 4 | - article 5 | - other 6 | -------------------------------------------------------------------------------- /docs/CNAME: -------------------------------------------------------------------------------- 1 | maturity.ekgf.org 2 | -------------------------------------------------------------------------------- /docs/article/.pages.yaml: -------------------------------------------------------------------------------- 1 | title: Articles 2 | nav: 3 | - Business Strategy: business-strategy.md 4 | - Enterprise Architecture: enterprise-architecture.md 5 | - Operating Model: operating-model.md 6 | - Value Proposition: value-proposition-of-ekg.md 7 | - ... 8 | -------------------------------------------------------------------------------- /docs/article/image/coordination-operating-model-core-diagram4.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/EKGF/ekg-maturity/9e758a40b367e6bcaf37d89df17e9e0b6e7bdfc4/docs/article/image/coordination-operating-model-core-diagram4.jpg -------------------------------------------------------------------------------- /docs/article/image/core-diagram-design-process4.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/EKGF/ekg-maturity/9e758a40b367e6bcaf37d89df17e9e0b6e7bdfc4/docs/article/image/core-diagram-design-process4.jpg -------------------------------------------------------------------------------- /docs/article/image/diversification-operating-model-core-diagram4.jpg: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/EKGF/ekg-maturity/9e758a40b367e6bcaf37d89df17e9e0b6e7bdfc4/docs/article/image/diversification-operating-model-core-diagram4.jpg -------------------------------------------------------------------------------- /docs/article/image/mexican-food-san-francisco.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/EKGF/ekg-maturity/9e758a40b367e6bcaf37d89df17e9e0b6e7bdfc4/docs/article/image/mexican-food-san-francisco.png -------------------------------------------------------------------------------- /docs/article/image/mission-district.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/EKGF/ekg-maturity/9e758a40b367e6bcaf37d89df17e9e0b6e7bdfc4/docs/article/image/mission-district.png -------------------------------------------------------------------------------- /docs/article/image/places-experiences-events-homes-etc.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/EKGF/ekg-maturity/9e758a40b367e6bcaf37d89df17e9e0b6e7bdfc4/docs/article/image/places-experiences-events-homes-etc.png -------------------------------------------------------------------------------- /docs/article/image/replication-operating-model-core-diagram4.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/EKGF/ekg-maturity/9e758a40b367e6bcaf37d89df17e9e0b6e7bdfc4/docs/article/image/replication-operating-model-core-diagram4.png -------------------------------------------------------------------------------- /docs/article/index.md: -------------------------------------------------------------------------------- 1 | # Articles 2 | 3 | - [Enterprise Architecture](enterprise-architecture.md) 4 | - [Operating Model](operating-model.md) 5 | - [Business Strategy](business-strategy.md) 6 | - [The value proposition of EKG](value-proposition-of-ekg.md) 7 | - [Introducing the EKG Matrix Plot & KGI Value](introducing-kgi.md) 8 | - [Meta Maturity Model](meta-maturity-model.md) 9 | -------------------------------------------------------------------------------- /docs/article/meta-maturity-model.md: -------------------------------------------------------------------------------- 1 | --- 2 | title: Meta Maturity Model 3 | summary: Meta Maturity Model 4 | authors: 5 | - Jacobus Geluk 6 | - Carl Mattocks 7 | - Carlos Tubbax 8 | - Pete Rivett 9 | date: 2022-03-09 10 | some_url: https://maturity.ekgf.org/article/meta-maturity-model/ 11 | --- 12 | 13 | This is a work-in-progress article documenting our current thinking about 14 | the meta-model of the EKG maturity model (EKG/Maturity) as we're documenting it on this website. 15 | We're working on an OWL Ontology and describing all content --- under the [Pillars](/pillars) 16 | menu-option that you see on this website --- in RDF so that we can then: 17 | 18 | - enforce a consistent structure throughout 19 | - create a dataset that anyone can build upon in their own EKG 20 | - have a solid foundation for EKG/Maturity assessments 21 | 22 | For simplicity's sake we're using UML in this article to document the model even though 23 | UML is not able to fully cover the expressiveness of an OWL ontology. 24 | But since this is not really a very complex model to begin with, UML will do. 25 | 26 | ![Meta Maturity Model](../diagrams/out/maturity-model.svg#darkable) 27 | 28 | 29 | -------------------------------------------------------------------------------- /docs/assets/.gitignore: -------------------------------------------------------------------------------- 1 | ekg-maturity-*.pdf 2 | -------------------------------------------------------------------------------- /docs/assets/ekg-maturity-structure.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/EKGF/ekg-maturity/9e758a40b367e6bcaf37d89df17e9e0b6e7bdfc4/docs/assets/ekg-maturity-structure.png -------------------------------------------------------------------------------- /docs/assets/ekgmm-process-commit-changes.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/EKGF/ekg-maturity/9e758a40b367e6bcaf37d89df17e9e0b6e7bdfc4/docs/assets/ekgmm-process-commit-changes.png -------------------------------------------------------------------------------- /docs/assets/ekgmm-process-create-pdf-job.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/EKGF/ekg-maturity/9e758a40b367e6bcaf37d89df17e9e0b6e7bdfc4/docs/assets/ekgmm-process-create-pdf-job.png -------------------------------------------------------------------------------- /docs/assets/ekgmm-process-create-pdf-workflow.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/EKGF/ekg-maturity/9e758a40b367e6bcaf37d89df17e9e0b6e7bdfc4/docs/assets/ekgmm-process-create-pdf-workflow.png -------------------------------------------------------------------------------- /docs/assets/ekgmm-process-diagram.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/EKGF/ekg-maturity/9e758a40b367e6bcaf37d89df17e9e0b6e7bdfc4/docs/assets/ekgmm-process-diagram.png -------------------------------------------------------------------------------- /docs/assets/ekgmm-process-edit-content.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/EKGF/ekg-maturity/9e758a40b367e6bcaf37d89df17e9e0b6e7bdfc4/docs/assets/ekgmm-process-edit-content.png -------------------------------------------------------------------------------- /docs/assets/ekgmm-process-pr-button.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/EKGF/ekg-maturity/9e758a40b367e6bcaf37d89df17e9e0b6e7bdfc4/docs/assets/ekgmm-process-pr-button.png -------------------------------------------------------------------------------- /docs/assets/replication-operating-model-core-diagram4.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/EKGF/ekg-maturity/9e758a40b367e6bcaf37d89df17e9e0b6e7bdfc4/docs/assets/replication-operating-model-core-diagram4.png -------------------------------------------------------------------------------- /docs/diagrams/.gitignore: -------------------------------------------------------------------------------- 1 | out/ 2 | -------------------------------------------------------------------------------- /docs/diagrams/include/themes/dark.puml: -------------------------------------------------------------------------------- 1 | !define BG_MAIN_COLOR #1A618C 2 | !define BG_SECONDARY_COLOR #616768 3 | !define BG_PACKAGE_COLOR #7a209f 4 | !define BORDER_COLOR #EEEEEE 5 | !define FONT_COLOR #EEEEEE 6 | 7 | skinparam backgroundColor #transparent 8 | skinparam backgroundColor %hsl_color(232, 15, 21) 9 | skinparam HyperLinkColor #lightgreen 10 | 11 | ' include the general skinparams for both, light and dark 12 | ' to overwrite with the given settings 13 | !include ./general.puml 14 | 15 | skinparam state { 16 | BackgroundColor #9397B2 17 | FontColor white 18 | AttributeFontColor #03045e 19 | BorderColor #0077b6 20 | } 21 | 22 | skinparam class { 23 | BackgroundColor #9397B2 24 | FontColor white 25 | AttributeFontColor #03045e 26 | BorderColor #0077b6 27 | } 28 | 29 | skinparam arrowColor #FF9900 30 | skinparam arrowThickness 1 31 | -------------------------------------------------------------------------------- /docs/diagrams/include/themes/light.puml: -------------------------------------------------------------------------------- 1 | !define BG_MAIN_COLOR #66BCF0 2 | !define BG_SECONDARY_COLOR #B4BCBE 3 | !define BG_PACKAGE_COLOR #eeb291 4 | !define BORDER_COLOR #444444 5 | !define FONT_COLOR #444444 6 | 7 | skinparam backgroundColor #white 8 | 9 | ' include the general skinparams for both, light and dark 10 | ' to overwrite with the given settings 11 | !include ./general.puml 12 | 13 | skinparam state { 14 | BackgroundColor #ade8f4 15 | FontColor #03045e 16 | AttributeFontColor #03045e 17 | ArrowColor #023e8a 18 | BorderColor #0077b6 19 | } 20 | 21 | skinparam class { 22 | BackgroundColor #ade8f4 23 | } 24 | 25 | skinparam arrowThickness 1 26 | 27 | -------------------------------------------------------------------------------- /docs/generate_maturity_model.py: -------------------------------------------------------------------------------- 1 | import os 2 | import ekglib 3 | from pathlib import Path 4 | 5 | import option 6 | 7 | config = ekglib.maturity_model_parser.Config( 8 | verbose=False, 9 | mkdocs=False, 10 | model_name="EKG/Maturity", 11 | model_root=Path("./metadata").resolve(), 12 | output_root=Path("./docs").resolve(), 13 | docs_root=Path(os.getcwd()) / "docs", 14 | fragments_root=Path(os.getcwd()) / "docs-fragments", 15 | pillar_dir_name=option.Some("pillar") 16 | ) 17 | ekglib.maturity_model_parser.run_with_config(config) 18 | -------------------------------------------------------------------------------- /docs/intro/.gitignore: -------------------------------------------------------------------------------- 1 | overview.md 2 | -------------------------------------------------------------------------------- /docs/intro/.pages.yaml: -------------------------------------------------------------------------------- 1 | title: Intro 2 | nav: 3 | - Intro: index.md 4 | - executive-summary.md 5 | - preface.md 6 | - overview.md 7 | - ... 8 | -------------------------------------------------------------------------------- /docs/intro/index.md: -------------------------------------------------------------------------------- 1 | --- 2 | hide: 3 | - title 4 | - toc 5 | --- 6 | The EKG Maturity Model is a “continuous improvement” product of the EKGF. 7 | 8 | It is intended to be updated based upon the comments of readers and implementers. 9 | Comments are reviewed by EKGF members and may result in new or changed content. 10 | In order for comments to be seen, the commenter must have a 11 | [GitHub ID](../other/how-to-register.md). 12 | 13 | After review and acceptance of comments, the [EKGF process](../other/process.md) 14 | automatically updates the MM. 15 | It is not necessary to be a member of EKGF to read and comment on the MM. 16 | It is necessary to be a member of the EKGF to be included in 17 | [the review process](../other/process.md). 18 | 19 | ![](../assets/ekg-maturity-structure.png) 20 | 21 | See [structure](./structure/) for more information. 22 | -------------------------------------------------------------------------------- /docs/intro/structure/.pages.yaml: -------------------------------------------------------------------------------- 1 | title: Structure 2 | nav: 3 | - index.md 4 | - pillars.md 5 | - levels.md 6 | - ... 7 | - template.md 8 | -------------------------------------------------------------------------------- /docs/intro/structure/index.md: -------------------------------------------------------------------------------- 1 | # Structure 2 | 3 | The Maturity Model for the Enterprise Knowledge Graph is a collection of 4 | capabilities structured in a relatively simple 4x5 matrix of 5 | _capability pillars_ and _maturity levels_. 6 | 7 | ![Structure](/assets/ekg-maturity-structure.png) 8 | 9 | - [The Four Capability Pillars](pillars.md) 10 | - [The Five Maturity Levels](levels.md) 11 | - [The Capability Template](template.md) 12 | 13 | 14 | 15 | 16 | -------------------------------------------------------------------------------- /docs/intro/structure/template.md: -------------------------------------------------------------------------------- 1 | # Capability Template 2 | 3 | The general layout, in this document, of each capability looks as follows: 4 | 5 | ## Capability 6 | 7 | > The title of the capability 8 | 9 | ## Description 10 | 11 | > Tagline, a short one sentence description of the Capability 12 | 13 | > Description of the capability 14 | 15 | ### Contribution to EKG 16 | 17 | > How the capability contributes to the EKG 18 | 19 | > Including traceability to EKG/Principles where relevant 20 | 21 | ### Contribution to the Enterprise 22 | 23 | > How the capability as part of the EKG contributes to the enterprise 24 | 25 | ## Dimensions 26 | 27 | > General dimensions/questions being measured by the criteria at different Levels 28 | 29 | > The following are candidate general questions 30 | 31 | - Level of required skills available (e.g. trained people) 32 | - Level of resources available (e.g.\ infrastructure, tools) 33 | - Level of defined processes available 34 | - Scope of applicability 35 | - Questions specific to the capability 36 | 37 | ## Levels 1 -- 5 38 | 39 | > Description of level 40 | 41 | > Criteria, drawing on the Dimensions 42 | -------------------------------------------------------------------------------- /docs/javascript/refresh_on_toggle_dark_light.js: -------------------------------------------------------------------------------- 1 | const paletteSwitcher1 = document.getElementById("__palette_1"); 2 | const paletteSwitcher2 = document.getElementById("__palette_2"); 3 | 4 | paletteSwitcher1.addEventListener("change", function () { 5 | location.reload(); 6 | }); 7 | 8 | paletteSwitcher2.addEventListener("change", function () { 9 | location.reload(); 10 | }); -------------------------------------------------------------------------------- /docs/other/.pages.yaml: -------------------------------------------------------------------------------- 1 | title: Other 2 | nav: 3 | - index.md 4 | - EKGF: https://ekgf.org 5 | - Principles: https://principles.ekgf.org/principle/ 6 | - Manifesto: https://principles.ekgf.org/ 7 | - FAIR: https://principles.ekgf.org/fair/ 8 | - Maturity: https://maturity.ekgf.org 9 | - Method: https://method.ekgf.org 10 | - Use Case FAQ: https://method.ekgf.org/other/faq/ 11 | - Catalog: https://catalog.ekgf.org/ 12 | - contributors.md 13 | - author 14 | - ... 15 | -------------------------------------------------------------------------------- /docs/other/author/.pages.yaml: -------------------------------------------------------------------------------- 1 | title: Authors 2 | nav: 3 | - index.md 4 | - ... -------------------------------------------------------------------------------- /docs/other/author/avinash-patil.md: -------------------------------------------------------------------------------- 1 | # Avinash Patil 2 | 3 | - [LinkedIn](https://www.linkedin.com/in/avinash-patil-4229564/) 4 | - Tata Consultancy Services 5 | 6 | ## Articles 7 | 8 | - Most of the introduction to the Business Pillar 9 | -------------------------------------------------------------------------------- /docs/other/author/carl-mattocks.md: -------------------------------------------------------------------------------- 1 | # Carl Mattocks 2 | 3 | - [LinkedIn](https://www.linkedin.com/in/carlmattocks/) 4 | - Wellness Intelligence Institute 5 | 6 | Carl Mattocks, Principal of Wellness Intelligence Institute, 7 | is passionate about the prospect of using Knowledge Graphs 8 | in a Semantic Memory to guide Machine Learning and speed 9 | AI powered processing of Business Capabilities. 10 | He continues to be a long time contributor to the evolution 11 | of publicly ([Enterprise Knowledge Graph Foundation (EKGF)](https://ekgf.org), 12 | WC3 Artificial Intelligence Knowledge Representation Community Group, 13 | Kantara Initiative, ANSI, OASIS, ISO) available specifications for 14 | Registry Repositories, Digital ID, Electronic health records, 15 | Wellness Monitoring, Knowledge Reasoning. 16 | 17 | ## Articles 18 | 19 | - Many contributions to the [Business Pillar](https://maturity.ekgf.org/pillar/business) 20 | - [Introducing the EKG Matrix Plot & KGI Value](http://maturity.ekgf.org/article/introducing-kgi/) 21 | - [Dimensions of Knowledge Value Assessment](http://maturity.ekgf.org/article/dimensions-of-knowledge-value-assessment/) 22 | - [Dimensions of Knowledge Risk Assessment](http://maturity.ekgf.org/article/dimensions-of-knowledge-risk-assessment/) 23 | 24 | -------------------------------------------------------------------------------- /docs/other/author/carlos-tubbax.md: -------------------------------------------------------------------------------- 1 | # Carlos Tubbax 2 | 3 | - [LinkedIn](https://www.linkedin.com/in/carlos-tubbax-975058118/) 4 | - [University of Antwerp](https://www.uantwerpen.be/en/staff/carlos-tubbax/) 5 | 6 | # Articles 7 | 8 | - [Value proposition of EKG](https://maturity.ekgf.org/article/value-proposition-of-ekg/) 9 | - [Modularity](https://method.ekgf.org/objective/modularity/) 10 | - [Interoperability](https://method.ekgf.org/objective/interoperability/) 11 | - [What is Business Strategy?](https://maturity.ekgf.org/article/business-strategy/) 12 | - [Enterprise Architecture](https://maturity.ekgf.org/article/enterprise-architecture/) 13 | - [Business Operating Model](https://maturity.ekgf.org/article/operating-model/) 14 | 15 | 16 | -------------------------------------------------------------------------------- /docs/other/author/index.md: -------------------------------------------------------------------------------- 1 | # Authors 2 | 3 | This publication has been worked on by many people, some created 4 | direct content and some contributed by joining calls, reviewing 5 | documents etc. 6 | 7 | -------------------------------------------------------------------------------- /docs/other/author/jacobus-geluk.md: -------------------------------------------------------------------------------- 1 | # Jacobus Geluk 2 | 3 | - [LinkedIn](https://www.linkedin.com/in/jgeluk/) 4 | - EKGF Initiator, Founder and board member 5 | - CEO [agnos.ai](https://agnos.ai) 6 | 7 | ## Articles 8 | 9 | - Overseeing the [EKG Principles](https://principles.ekgf.org) 10 | - Overseeing the [EKG Catalog](https://catalog.ekgf.org) 11 | - Overseeing the [EKG Method](https://method.ekgf.org) 12 | - Overseeing the overall structure of the [EKG Maturity Model](https://maturity.ekgf.org) 13 | 14 | -------------------------------------------------------------------------------- /docs/other/author/pete-rivett.md: -------------------------------------------------------------------------------- 1 | # Pete Rivett 2 | 3 | - [LinkedIn](https://www.linkedin.com/in/peterivett/) 4 | - OMG 5 | - EKGF Founder & Vice President Data Pillar 6 | 7 | ## Articles 8 | 9 | - Most content in the [Data Pillar](https://maturity.ekgf.org/pillar/data) 10 | 11 | -------------------------------------------------------------------------------- /docs/other/corporate-members.md: -------------------------------------------------------------------------------- 1 | # Corporate Members 2 | 3 | The corporate members of the Enterprise Knowledge Graph Foundations currently are---ordered by join date: 4 | 5 | ### agnos.ai 6 | 7 | [agnos.ai](https://agnos.ai) is an Enterprise Knowledge Graph consultancy assisting its clients in 8 | their EKG journey from strategy to production. 9 | 10 | ### Wizdom 11 | 12 | [Wizdom](http://www.wizdom.com/) is a recognized leader in providing our clients with 13 | innovative process-based business solutions for improving performance. 14 | 15 | ### Ontotext 16 | 17 | [Ontotext](https://www.ontotext.com/) is a global leader in Enterprise Knowledge Graph technology 18 | and semantic database engines. 19 | 20 | ### data.world 21 | 22 | [data.world](https://data.world) makes it easy for everyone—not just the "data people"—to get clear, accurate, 23 | fast answers to any business question. 24 | 25 | ### Eccenca 26 | 27 | [eccenca](https://eccenca.com/) is a leading provider of Enterprise Knowledge Graph management 28 | software and solutions. 29 | 30 | ### Global IDs 31 | 32 | [Global IDs](https://www.globalids.com/) provides software for enterprise information management (EIM). 33 | 34 | ### Cambridge Semantics 35 | 36 | [Cambridge Semantics](https://www.cambridgesemantics.com/) provides Anzo, 37 | the scalable knowledge graph platform for data integration and analytics. 38 | 39 | 40 | 41 | -------------------------------------------------------------------------------- /docs/other/how-to-register.md: -------------------------------------------------------------------------------- 1 | # How to register? 2 | 3 | We are asking every potential contributor, even someone who just wants to give us 4 | some feedback (a "critic") to join the EKGF as a private member (free) or as a 5 | corporate member. 6 | 7 | Email with [registration@ekgf.org](mailto:registration@ekgf.org) to set it up, 8 | if you plan to participate as a contributor to the 9 | [EKG maturity model (EKG/Maturity)](https://maturity.ekgf.org) 10 | then please also supply your GitHub user-id. 11 | 12 | ## How to create a GitHub & Slack account? 13 | 14 | ### Slack 15 | 16 | If you already have a Slack account then join the EKGF workspace 17 | here: [https://ekgf.slack.com/](https://ekgf.slack.com/). 18 | Otherwise, first create your Slack account [here](https://slack.com/get-started\#/create). 19 | 20 | ### GitHub 21 | 22 | Go to [https://github.com/join](https://github.com/join). 23 | 24 | Since you can associate multiple email addresses to your GitHub account we would 25 | suggest to initially create it with your private email address which then becomes 26 | your "primary email account" in GitHub. 27 | You can add your business email address(es) to your GitHub account later. 28 | 29 | Mail your GitHub account id (user-id) to 30 | [registration@ekgf.org](mailto:registration@ekgf.org) so that we can add you 31 | to the access control list of the [EKGF/ekg-maturity repository](https://github.com/EKGF/ekg-maturity). 32 | -------------------------------------------------------------------------------- /docs/stylesheets/extra.css: -------------------------------------------------------------------------------- 1 | :root { 2 | --md-primary-fg-color: #4A23D9; 3 | --md-primary-fg-color--light: #4A23D9; 4 | --md-primary-fg-color--dark: #25126A; 5 | } 6 | 7 | /*#rotate-text {*/ 8 | /* -ms-writing-mode: tb-rl;*/ 9 | /* -webkit-writing-mode: vertical-rl;*/ 10 | /* writing-mode: vertical-rl;*/ 11 | /* width: 30px;*/ 12 | /* transform: rotate(-90deg);*/ 13 | /* margin: 0px;*/ 14 | /* padding: 0px;*/ 15 | /* white-space: nowrap;*/ 16 | /*}*/ 17 | 18 | /*td*/ 19 | /*{*/ 20 | /* vertical-align: bottom;*/ 21 | /* text-align: center;*/ 22 | /*}*/ 23 | 24 | /*td span*/ 25 | /*{*/ 26 | /* -ms-writing-mode: tb-rl;*/ 27 | /* -webkit-writing-mode: vertical-rl;*/ 28 | /* writing-mode: vertical-rl;*/ 29 | /* transform: rotate(180deg);*/ 30 | /* white-space: nowrap;*/ 31 | /*}*/ 32 | 33 | /*.md-typeset__table.mmtable*/ 34 | /*{*/ 35 | /* border: 1px red solid ;*/ 36 | /*}*/ 37 | 38 | /*.md-typeset__table.mmtable td {*/ 39 | /* font-weight: bold;*/ 40 | /* background-color: #fff;*/ 41 | /* border-collapse: separate;*/ 42 | /*}*/ 43 | -------------------------------------------------------------------------------- /ekg-maturity.iml: -------------------------------------------------------------------------------- 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | -------------------------------------------------------------------------------- /metadata/c-1-data-strategy.ttl: -------------------------------------------------------------------------------- 1 | @base . 2 | @prefix rdf: . 3 | @prefix rdfs: . 4 | @prefix xsd: . 5 | @prefix xsd: . 6 | @prefix ekgmm: . 7 | @prefix dct: . 8 | 9 | 10 | a ekgmm:Capability ; 11 | rdfs:label "Goals & Objectives" ; 12 | rdfs:comment "EKG as the semantic data mesh for the organization." ; 13 | ekgmm:iriLocalName "goals-and-objectives" ; 14 | ekgmm:inArea ; 15 | ekgmm:capabilityNumber "C.1.1" ; 16 | . 17 | 18 | 19 | a ekgmm:Capability ; 20 | rdfs:label "Business Case" ; 21 | rdfs:comment "Business rationale, justification and ROI of the EKG." ; 22 | ekgmm:iriLocalName "business-case" ; 23 | ekgmm:inArea ; 24 | ekgmm:capabilityNumber "C.1.2" ; 25 | . 26 | -------------------------------------------------------------------------------- /metadata/d-1-technology-strategy.ttl: -------------------------------------------------------------------------------- 1 | @base . 2 | @prefix rdf: . 3 | @prefix rdfs: . 4 | @prefix xsd: . 5 | @prefix xsd: . 6 | @prefix ekgmm: . 7 | @prefix dct: . 8 | 9 | 10 | a ekgmm:Capability ; 11 | rdfs:label "Technology Architecture" ; 12 | rdfs:comment "Plans for physical infrastructure, applications, and automation." ; 13 | ekgmm:iriLocalName "technology-architecture" ; 14 | ekgmm:inArea ; 15 | ekgmm:capabilityNumber "D.1.1" ; 16 | . 17 | -------------------------------------------------------------------------------- /mkdocs.insiders.yml: -------------------------------------------------------------------------------- 1 | INHERIT: mkdocs.yml 2 | theme: 3 | custom_dir: docs-overrides/ 4 | plugins: 5 | - search 6 | - social 7 | - tags 8 | markdown_extensions: 9 | - pymdownx.superfences: 10 | # make exceptions to highlighting of code: 11 | custom_fences: 12 | - name: mermaid 13 | class: mermaid 14 | format: !!python/name:pymdownx.superfences.fence_code_format 15 | -------------------------------------------------------------------------------- /mkdocs.outsiders.yml: -------------------------------------------------------------------------------- 1 | INHERIT: mkdocs.yml 2 | plugins: 3 | - search 4 | - mermaid2: 5 | arguments: 6 | # test if its __palette_1 (dark) or __palette_2 (light) 7 | # for mkdocs-material >=8.0.0 8 | theme: | 9 | ^(JSON.parse(__md_get("__palette").index == 1)) ? 'dark' : 'light' 10 | securityLevel: 'loose' 11 | extra_javascript: 12 | - https://unpkg.com/mermaid/dist/mermaid.min.js 13 | - javascript/refresh_on_toggle_dark_light.js 14 | markdown_extensions: 15 | - pymdownx.superfences: 16 | custom_fences: 17 | - name: mermaid 18 | class: mermaid 19 | format: !!python/name:mermaid2.fence_mermaid 20 | - pymdownx.emoji: 21 | emoji_index: !!python/name:materialx.emoji.twemoji 22 | emoji_generator: !!python/name:materialx.emoji.to_svg 23 | options: 24 | custom_icons: 25 | - docs-overrides/.icons -------------------------------------------------------------------------------- /old-latex-content/.gitignore: -------------------------------------------------------------------------------- 1 | *.acn 2 | *.acr 3 | *.alg 4 | *.aux 5 | *.bbl 6 | *.bcf 7 | *.blg 8 | *.fdb_latexmk 9 | *.fls 10 | *.glg 11 | *.glo 12 | *.gls 13 | *.idx 14 | *.ilg 15 | *.ind 16 | *.ist 17 | *.log 18 | *.odn 19 | *.old 20 | *.olg 21 | *.pdf 22 | *.run.xml 23 | *.synctex.gz 24 | *.tdn 25 | *.tld 26 | *.tlg 27 | *.toc -------------------------------------------------------------------------------- /old-latex-content/unprocessed-old-latex/c-3-3.tex: -------------------------------------------------------------------------------- 1 | % 2 | % C.3.3 Data Quality Execution -- Summary 3 | % 4 | Implementation of the data quality program\index{data!quality!program} is a control process mechanism for organizations. 5 | \index{control process} 6 | It is driven by the execution of business rules at the point of data capture (validation).\improve{% 7 | JAG>Actually it shouldn't be done just after data capture. First convert raw source data to RDF, then transform% 8 | to all the relevant ontologies and then run any business rules for curation or enrichment purposes. And for datasets 9 | where the EKG itself is authoritative we need to run the business rules during a transaction.} 10 | Key components include data profiling, root cause analysis, data remediation and issue management. 11 | The primary objective of the data quality program is to accurately and consistently represent the concepts and 12 | values needed to meet the needs of consumers. 13 | A well-orchestrated data quality program requires communication and operational coordination across the 14 | organizational landscape. 15 | 16 | -------------------------------------------------------------------------------- /old-latex-content/unprocessed-old-latex/c-4-1.tex: -------------------------------------------------------------------------------- 1 | % 2 | % C.4.1 Data-management Operating Model -- Summary 3 | % 4 | The people, processes, capabilities, and tools that define the role of \iindex{data management} in delivering 5 | value to an organization’s customers.\footnote{% 6 | There is also a capability called ``\nameref{sec:ekg-maturity-business-operating-model}'' in the 7 | Business Pillar that has a different meaning, see \secref{sec:ekg-maturity-business-operating-model}. 8 | } 9 | 10 | The \gls{operating-model} can help stakeholders understand the complexity of the data manufacturing process and how 11 | components relate to each other. 12 | It specifies the roles and responsibilities of the stakeholders involved in the data management program. 13 | It provides a framework and policies to help align governance concepts with operating requirements and 14 | organizational culture. 15 | An effective \gls{operating-model} can both describe the way the organization does business today (“as is”) and 16 | communicate a vision of how an operation will work in the future ("to be"). 17 | \improve{JAG>Make the link to the corresponding capabilities in the business pillar here} 18 | 19 | -------------------------------------------------------------------------------- /old-latex-content/unprocessed-old-latex/c-4-2.tex: -------------------------------------------------------------------------------- 1 | % 2 | % C.4.2 Data-management Policy -- Summary 3 | % 4 | Data management policies are the mandated requirements to ensure effective management of an organization’s 5 | information assets.\index{data management}\index{data management!policy} 6 | Policies are implemented via \glspl{operating-model}\index{data management!operating model}, 7 | standards\index{data management!standards} and documented procedures. 8 | Data management policies define requirements related to data access (e.g. authorized sources, entitlements, 9 | usage and redistribution), data quality (e.g. metadata, definitions, modeling and business rules), 10 | organizational governance (e.g. accountabilities and alignment with business processes) and 11 | control functions (e.g. retention, security, privacy and change management). 12 | \TODO[inline]{% 13 | JAG>data access requirements, in so far they're use case related, should be tied to use cases. We should make 14 | a distinction between dataset-specific access requirements and use case specific access requirements.% 15 | } 16 | \TODO[inline]{% 17 | JAG>At the higher maturity levels, all dataset related policies (all the above) 18 | should be captured as RDF data, OWL ontologies and/or SHACL shapes and be made part 19 | of any self-describing dataset (SDD).% 20 | } 21 | 22 | -------------------------------------------------------------------------------- /old-latex-content/unprocessed-old-latex/c-4-3.tex: -------------------------------------------------------------------------------- 1 | % 2 | % C.4.3 Data Production \& Consumption -- Summary 3 | % 4 | Data originates from a wide variety of business processes and flows through multiple systems before it is 5 | ingested into applications and analytical functions. 6 | As data flows across this “chain of supply”\index{supply chain}\index{data!supply chain}\,---\,it can be renamed, 7 | enriched, transformed and updated (many times). 8 | Data producers\index{data!producer}\index{data!publisher} and consumers\index{data!consumer} must work collaboratively 9 | to ensure that the data is fit for its intended purposes.\index{fit for purpose} 10 | This necessitates communications about the requirements for quality as well as an understanding of 11 | how the data is being used, where it originates, how it has been transformed and its consistency with original intent. 12 | 13 | -------------------------------------------------------------------------------- /old-latex-content/unprocessed-old-latex/c-4-4.tex: -------------------------------------------------------------------------------- 1 | % 2 | % C.4.4 Entitlement Management -- Summary 3 | % 4 | Entitlement management\index{entitlement!management} is technology that grants and enforces access rights to data, 5 | devices, systems and services. 6 | \TODO[inline]{% 7 | JAG>I wouldn't Entitlement Management "technology", it's more than that. This capability has been put in the 8 | data pillar for a reason but the language used here is focused on the technology. Entitlement policies (based 9 | on legal, regulatory and business policy requirements) need to be defined and captured as models to be made part 10 | of each self-describing dataset (SDD) in the enterprise% 11 | } 12 | Entitlement systems are linked to organizational policies (rules) governing access. 13 | These systems track access to applications to ensure that actions are in line with policies and to provide data 14 | about access for audit purposes. 15 | Entitlements need to be managed in sync with the goals for security, business continuity and compliance. 16 | There can be multiple proprietary systems that all have unique entitlement structures and 17 | individuals can move across departments and perform a variety of roles. 18 | 19 | -------------------------------------------------------------------------------- /old-latex-content/unprocessed-old-latex/c-4-5.tex: -------------------------------------------------------------------------------- 1 | % 2 | % C.4.5 Classification Management -- Summary 3 | % 4 | \glsreset{cde}\Glspl{cde} are designated as having a material impact on a business process, regulatory report, 5 | financial calculation or risk measure. 6 | The designation of a data element as critical means it is important enough to be governed by organizational policy. 7 | \Gls{cde} management is implemented as a negotiation process between producers and consumers that require 8 | precision of meaning, understanding of data flow, capture of business rules and the management of quality based on 9 | how the data will be used. 10 | Many firms use the term \gls{cde} to describe various things such as data attributes, business concepts, 11 | derived processes and physical expressions. 12 | This confusion over nomenclature about concepts makes it difficult to distinguish granular data from how it is 13 | assembled into business measures and how it is expressed in physical data repositories. 14 | \TODO[inline]{% 15 | JAG>Can we agree on 1 name for "data repository", "data source", "data store" and not use all variations 16 | throughout this document? 17 | } 18 | 19 | 20 | -------------------------------------------------------------------------------- /old-latex-content/unprocessed-old-latex/c-4-6.tex: -------------------------------------------------------------------------------- 1 | % 2 | % C.4.6 Risk and Control Environment -- Summary 3 | % 4 | Operational risk\index{operational risk}\index{risk!operational risk} is the result of inadequate or 5 | failed internal procedures, systems or policies that are not driven by external forces such as 6 | economic, political or systemic events. 7 | 8 | Understanding how data flows into decision-making and operational processes is one of the key components of 9 | operational risk mitigation.\index{risk!mitigation} 10 | Many firms are working to establish strong control environments to identify, approve and monitor operational risk. 11 | Control processes include a combination of strong governance, standards for ensuring interoperability and 12 | quality assurance across the full data lifecycle.\index{data!lifecycle} 13 | 14 | 15 | -------------------------------------------------------------------------------- /old-latex-content/unprocessed-old-latex/d-2-2.tex: -------------------------------------------------------------------------------- 1 | % 2 | % D.2.2 Operations -- Summary 3 | % 4 | \TODO[inline]{Create summary for \thesection} 5 | 6 | \TODO[inline]{% 7 | JAG>We may want to call this "EKG Operate" or "Operate EKG", unless we want to make this about more than just 8 | the operations around the EKG itself. It could be that all operations in the technology landscape could be 9 | covered by this capability, at "level 5" I'd say that should be the case anyway. At level 1 this capability is 10 | however "just" about "operating your own EKG".% 11 | } 12 | 13 | -------------------------------------------------------------------------------- /old-latex-content/unprocessed-old-latex/d-2-3.tex: -------------------------------------------------------------------------------- 1 | % 2 | % D.2.3 Architecture -- Summary 3 | % 4 | \TODO[inline]{Create summary for \thesection} 5 | 6 | \TODO[inline]{% 7 | JAG>We may want to call this "EKG Architecture", unless we want to make this about more than just 8 | the (technical) architecture of the EKG itself. It could be that all architecture of the whole 9 | technology landscape could be covered by this capability, at "level 5" I'd say that should be the case anyway. 10 | At level 1 this capability is however "just" about the architecture of your own EKG.% 11 | } 12 | -------------------------------------------------------------------------------- /old-latex-content/unprocessed-old-latex/d-3-1.tex: -------------------------------------------------------------------------------- 1 | % 2 | % D.3.1 Search & Query -- Summary 3 | % 4 | \TODO[inline]{Create summary for \thesection} 5 | 6 | \TODO[inline]{% 7 | JAG>Make the link from "Search \& Query" to "Sense" in \glsfirst{suda}, as described in the business pillar. 8 | See also \ref{ch:ekg-maturity-business-strategy-actuation} \nameref{ch:ekg-maturity-business-strategy-actuation} on page 9 | \pageref{ch:ekg-maturity-business-strategy-actuation}. 10 | } 11 | 12 | \TODO[inline]{% 13 | JAG>A better term for the "Search \& Query" capability may be "Discover" (or "Sense" as in \gls{suda}). 14 | This capability is basically one to one what a good "EKG/UX" should provide, providing an integrated user 15 | experience where searching, querying, asking questions, discovering is all one user interface basically. 16 | Even reporting comes into that, any user should be able to create a report for themselves or for others, slicing 17 | and dicing data until it becomes understandable for a given purpose, much like Excel is used today. 18 | In other words, that's much more than just "Search \& Query". 19 | } 20 | -------------------------------------------------------------------------------- /old-latex-content/unprocessed-old-latex/d-3-3.tex: -------------------------------------------------------------------------------- 1 | % 2 | % D.3.3 Change Management -- Summary 3 | % 4 | \TODO[inline]{Create summary for \thesection} 5 | 6 | \TODO[inline]{% 7 | JAG>Change Management just for User Experience? Should be under "D.2 Technology Execution" perhaps? 8 | } 9 | 10 | -------------------------------------------------------------------------------- /poetry.toml: -------------------------------------------------------------------------------- 1 | [experimental] 2 | system-git-client = true 3 | new-installer = true 4 | 5 | [virtualenvs] 6 | in-project = true 7 | 8 | [installer] 9 | modern-installation = true 10 | -------------------------------------------------------------------------------- /pyproject.toml: -------------------------------------------------------------------------------- 1 | [tool.poetry] 2 | name = "ekg-maturity" 3 | version = "1.0.2" 4 | description = "" 5 | authors = ["Jacobus Geluk "] 6 | readme = "README.md" 7 | license = "GPL-3.0-only" 8 | homepage = "https://maturity.ekgf.org" 9 | repository = "https://github.com/EKGF/ekg-maturity" 10 | packages = [ 11 | ] 12 | 13 | [tool.poetry.dependencies] 14 | python = "^3.10" 15 | mkdocs-build-plantuml-plugin = "*" 16 | mdutils = "*" 17 | mkdocs-awesome-pages-plugin = "*" 18 | mkdocs-exclude = "*" 19 | mkdocs-exclude-search = "*" 20 | mkdocs-gen-files = "*" 21 | mkdocs-git-revision-date-localized-plugin = "*" 22 | mkdocs-graphviz = "*" 23 | mkdocs-include-markdown-plugin = "*" 24 | mkdocs-localsearch = "*" 25 | mkdocs-macros-plugin = "*" 26 | mkdocs-mermaid2-plugin = "*" 27 | mkdocs-minify-plugin = "*" 28 | mkdocs-redirects = "*" 29 | mkdocs-kroki-plugin = "*" 30 | mdx-spanner = "*" 31 | markdown-emdash = "*" 32 | smartypants = "*" 33 | pillow = "*" 34 | cairosvg = "*" 35 | ekglib = {git = "https://github.com/EKGF/ekglib.git"} 36 | 37 | [project] 38 | name = "ekg-maturity" 39 | version = "1.0.0" 40 | description = "" 41 | authors = [ 42 | {name = "Jacobus Geluk", email = "jacobus.geluk@ekgf.org"}, 43 | ] 44 | dependencies = [] 45 | requires-python = ">=3.10" 46 | license = {text = "MIT"} 47 | -------------------------------------------------------------------------------- /requirements.txt: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/EKGF/ekg-maturity/9e758a40b367e6bcaf37d89df17e9e0b6e7bdfc4/requirements.txt -------------------------------------------------------------------------------- /workspace.code-workspace: -------------------------------------------------------------------------------- 1 | { 2 | "folders": [ 3 | { 4 | "path": "." 5 | } 6 | ], 7 | "settings": { 8 | "latex-workshop.latex.external.build.command": "latexmk", 9 | "files.associations": { 10 | ".latexmkrc": "perl" 11 | } 12 | } 13 | } --------------------------------------------------------------------------------