Governed objects
Represent defined engineering objects with identity, ownership and status.
Canonical Engineering Knowledge Model
How could governed engineering knowledge remain connected?
Represent governed engineering objects and relationships using the patterns defined by GMS.
When this is useful
Use the CEKM design when specifications, decisions, evidence and dependencies need a connected knowledge representation.
How it fits in the portfolio
GMS defines the representation rules. CEKM describes the governed objects and relationships. AMIGOS is a separate proposed operating environment.
What it covers
Connected context
Relate requirements, architecture, artifacts, decisions and evidence.
Controlled evolution
Retain provenance, versions and lifecycle history as knowledge changes.
Improving an order-reconciliation handoff.
Represent the relationship between an order exception, the affected interface, the change decision and its acceptance evidence in a scoped knowledge model.
What an agreed engagement can produce
A knowledge model, selected object records, relationships and a scoped repository design or validation plan.
Limits
The reviewed documentation does not verify a functioning CEKM repository or live source of truth. A software implementation needs separate evidence.
Documented methods and designs don't by themselves show that software is available or that outcomes have been measured.
Start with a real business need.
Connect the method to the workflow, capability or decision you want to improve.