Landscape of data, reports and analytics
Data provenance, indicator semantics, report releases and analytical conclusions.
Bundle → Layer → Finding → Questions Filled
2 bundles · 3 layers · 4 findings · 8 questions
Definitions and provenance Which metrics and reports exist and where their data comes from.
Metric semantics
Metric definitions with their formulas and versions.
Definition identity
Each metric identified by definition, not by title.
- Which formula and version define this metric?
- Do two metrics with the same name use different formulas?
Provenance
Recorded lineage from source facts to outputs.
- Which sources and pipelines feed this metric, as recorded?
- Where is provenance missing rather than known?
Releases and conclusions Report runs and the conclusions drawn from them.
Releases
Specific report releases tied to definition versions.
Release methodology
The definition version used for each release.
- Which definition version produced this report release?
- Which releases will a change in this formula affect?
Conclusions
Analytical conclusions and the completeness of their data.
Data sufficiency
Whether the data behind a conclusion was complete enough.
- Which conclusions rely on incomplete data?
- Do derived views respect the access rights of the source facts?
Classifiers Filled
- Family
- Enterprise profiles
- Category
- Enterprise landscape
- Entry kind
- landscape
- Domain
- EnterpriseLND
- Industry
- Cross-industry
- Tags
- EM-LND-13W2landscapeDataLandscapeAnalyticalLineageView
What it is Filled
Data provenance, indicator semantics, report releases and analytical conclusions.
Why it exists Filled
Data provenance, indicator semantics, report releases and analytical conclusions.
Distinguishing features Filled
- A metric is identified by its definition and version, never by its title alone.
- Definitions and runs are separate records, so each release keeps its methodology.
- Provenance is recorded or shown as missing, never invented.
- Distinct from individual report or dataset records; this view connects them.
What robots and AI may and may not do Filled
Must not
- Treat two reports as comparable because their KPI titles match.
- Fill missing lineage with a plausible source.
- Expose source facts through a derived view to people without rights to them.
- Restate past releases with a new methodology without recording it.
Only with a human decision
- Approving a change to a metric definition used in management or external reporting.
- Accepting a conclusion based on incomplete data for a decision.
May
- List reports and releases affected by a change in a metric definition.
- Flag metrics with the same name and different formulas.
- Mark conclusions that rely on incomplete or unknown data.
Moral aspects Filled
- Misleading comparisons can drive wrong decisions about people, budgets or customers.
- Derived views can leak personal or confidential data if rights are not carried over.
Who is affected
- Report consumers and decision makers
- Data owners
- People described in the data
Owners Filled
Steward
The curator of the meta-model catalogue who decides which landscape views are assembled and from which sources.
Master systems
- Model registry
- Source manifest
- Version lock file
- Policy repository
Links to other meta-models Filled
references
- WM-DAT-001 - conceptual-candidate
- WM-DAT-005 - conceptual-candidate
- WM-DAT-006 - conceptual-candidate
- WM-DAT-008 - conceptual-candidate
What else AI and robots need to interact with it Filled
Identity and identifiers required Filled
- Identified by a lineage view identifier and version; metrics by definition identifier and version.
Direct properties not applicable Not applicable
Not applicable
Enterprise record contour: physical properties belong to referenced world models.
Recognition optional Filled
- A map of sources, pipelines, metric definitions, report releases and conclusions.
- Often confused with a data catalogue or a dashboard list.
Capabilities and actions required Filled
- Impact of a formula change can be traced to specific releases.
- Same-name metrics with different meaning can be detected.
Hazards and failure modes required Filled
- False comparability across reports.
- Leakage of restricted data through derived outputs.
Standards and interfaces required Filled
- W3C PROV-O for provenance of data and outputs.
- W3C DCAT for describing datasets and data services.
- OpenLineage from LF AI and Data for recording pipeline lineage events.
Context of use required Filled
- Used in analytics governance, metric change control and audit of reported figures.
- Relevant wherever several teams publish reports from shared data.
Sources Filled
- Vercy composition and whole-object: a separate landscape object and delegation
- ArchiMate/ISO 42010: views, questions and representation rules
- Compare participant subject models and the practical assembly of a permitted context
- Vercy Whole-Object Description Profile - Checked live (HTTP 200) on 2026-10-07.
- W3C The RDF Data Cube Vocabulary - Checked live (HTTP 200) on 2026-10-07.
Open questions
- Which reports will a metric definition change affect?
- Where do identical names hide different formulas?
- Which conclusions rely on incomplete data?
- Установить границу и решение reuse/extend/new по действующим спецификациям.
- Подтвердить semantic crosswalk, права и source mastership.
- Выбрать immutable refs; провести проверки fixtures до заявления о публикационной готовности.
Machine files
Provenance
enterprise research programme · published-partial
Built from: enterprise/models/em-lnd-13/brief.json, ver-cy/world-models/card-supplements/em-lnd-13.json
Still in Russian: suggested owner, blocking decisions, vercy candidates. Translate in research/enterprise/i18n/units.en.json.