Engineering Document Management

BC-1130 Level 1 Engineering Services 5 providers 9 API surfaces 2 rated strong or better

Controlled engineering documents, drawings, specifications, vendor data.

Engineering Document Management (BC-1130) is a level-1 business capability in the Engineering Services model. The catalog holds 9 API surface(s) from 5 provider(s) that can perform some part of it, 2 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

Document Control Management BC-1130.10

Document numbering, revision control, master document register.

1 provider, 1 API surface

Drawing Management BC-1130.20

Drawing lifecycle, distribution, approvals.

3 providers, 5 API surfaces

Specification Management BC-1130.30

Technical specifications, datasheets, standards compliance.

1 provider, 1 API surface

Vendor Document Management BC-1130.40

Vendor data requirements, submissions, reviews, dispositions.

1 provider, 1 API surface

Document Distribution & Transmittal Management BC-1130.50

Transmittals, formal correspondence, recipient tracking.

no catalog coverage

As-Built Documentation Management BC-1130.60

Red-line markups, as-built consolidation, handover documentation packages.

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 2 Solid coverage with minor gaps
AutodeskVersions1 API60.4FieldwireFloor PlansFloorplansSheetsSpec Sections5 APIs56.7
Developing 3 Usable, with meaningful gaps to close
PlanRadarPlans V21 API52.1FinalcadDocuments1 API51.5CapmoProject Plans1 API45.8

Workflows that realise this capability

Arazzo workflows whose own sourceDescriptions call APIs that carry this capability. The link is derived, not asserted: each workflow declares x-realizes-capability-ids with the spec and confidence behind it.

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 Engineering Document Management. 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 →