Identity & structure
Give objects controlled names, types, definitions and identifiers.
Genesis Meta Model Specification
How are enterprise objects consistently defined and connected?
Define identity, structure, relationships, lifecycle, versioning, ownership and traceability for governed objects.
When this is useful
Use GMS when enterprise engineering records need a consistent representation and clear relationships across their lifecycle.
How it fits in the portfolio
GMS specifies representation. CEKM is described as the governed knowledge model implementing those patterns. AWES concepts require faithful domain mappings.
What it covers
Relationships & traceability
Connect objects to their sources, dependencies, decisions and evidence.
Lifecycle & governance
Make ownership, version, status and change history explicit.
Improving an order-reconciliation handoff.
Give the capability, interface and acceptance test distinct identities and versions, then declare the relationships between them.
What an agreed engagement can produce
An object schema, relationship definitions and controlled metadata and lifecycle patterns for the agreed domain.
Limits
Shared metadata must preserve the distinction between definition and instance, role and tool, authority and permission, responsibility and accountability.
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.