Digital Engineering & Asset Information Management › Common Data Environment

Common Data Environment

BC-5060.20 Level 2 Infrastructure 2 providers 3 API surfaces 1 rated strong or better

Management of the shared information environment and the requirements, control, and exchange of project data.

Common Data Environment (BC-5060.20) is a level-2 business capability under Digital Engineering & Asset Information Management in the Infrastructure model. The catalog holds 3 API surface(s) from 2 provider(s) that can perform some part of it, 1 of them rated strong or better. Reach is the vendor surface that lands on this capability — it is not a claim about what any particular organisation has deployed.

Where this capability definition comes from. This capability is part of a published business-architecture model that API Evangelist did not author. It is redistributed here under CC-BY-4.0. Turbo EA Capabilities by Vincent Verdet — Turbo EA, https://github.com/vincentmakes/turbo-ea-capabilities, CC BY 4.0 Changes: Consolidated from 333 per-L1 YAML files into one JSON; English only (upstream i18n/ omitted); descriptions whitespace-normalised. No capability was added, removed, renamed or re-parented. Source repository · NOTICE and third-party framework attributions

Sub-capabilities

Common Data Environment Management BC-5060.20.10

Operation of the common data environment as the single source of project information.

no catalog coverage

Information Requirements Management BC-5060.20.20

Definition and management of organisational, asset, and exchange information requirements.

no catalog coverage

Document & Data Control BC-5060.20.30

Control, versioning, and status management of documents and data.

no catalog coverage

Data Exchange & Interoperability BC-5060.20.40

Exchange of information across systems using open and interoperable formats.

no catalog coverage

Providers that reach this capability

Ordered by rating band. Reach means a provider publishes an API surface that can perform some part of this capability — it is not a claim that any particular organisation has deployed it.

Strong 1 Solid coverage with minor gaps
FieldwireSheets1 API58.2
Developing 1 Usable, with meaningful gaps to close
PlanRadarApproval Requests V2DMS2 APIs51.4
This page carries no rating. Capabilities are not rated. A capability is a description of what a business does, not a thing a company publishes, so a Kin Score would have nothing to measure.
The edge table is a Pro feature. This page shows which providers and tags reach Common Data Environment. The underlying tag → capability edges — each with the quoted fragment of the provider's own OpenAPI that evidences it, a calibrated confidence score, and the contract-provenance gate it passed — are available through the API, along with company-level capability maps. Only edges at confidence ≥ 0.7 with evidence found verbatim in the source contract are published at all.

See plans →  ·  How the edges are graded →