PBMP GEM Management — Change Management Workbench

Controlled change workbench — GEM identity stable · scope · impact · approval · evidence (GEM-CHG-000245)

① Request

② Edit & Scope

③ Impact

④ Validate

⑤ Apply

1 Change Request Header

Change Request ID

Target GEM

GEM ID

FQN

Requested By

Requested On

Due Date

Change Type

Status / Risk

Draft Medium

Change Reason

2 Current GEM Snapshot (v1.0 — Before Change)

Meaning

Business Case Docket — Docket containing items related to the business case for a product initiative.

Names

Display: Business Case Docket · Common: BC Docket
Technical: business_case_docket · API: businessCaseDocket

Classification

M1 Docket Product Mgmt · Product Discovery · Subkind: Business Case Docket

Lifecycle

Approved / Published · Baseline v1.0

Usage

8 Templates · 4 Screens · 3 APIs · 2 Reports · 12 Rules · 256 M0 instances
BRD Workbench · Product Discovery Template · Business Case PDF export

Relationships (Incoming / Outgoing)

Outgoing: contains → Business Case Section (1..*) · contains → Problem Statement · contains → Benefits Section
Outgoing: refines → Business Need · usedBy → Product Discovery Workbench · exportedAs → PDF · baselinedAs → BusinessCaseTemplate_v1
Incoming: partOf ← Product Discovery Docket

Rules

Validation: Docket must contain ≥1 Problem Statement Section (Blocking)
Lifecycle: Published GEM requires baseline for name change
Access: Product Manager + GEM Steward can submit change
Override: CanOverride = TRUE · IsOverridden by 2 clients

3 Change Type Selector

RenameDisplay / tech / API names

Add AliasAlternate name

Meaning ChangeSanctioned English

ReclassifyKind / Layer / M-Level

Relationship AddNew LHS→Rel→RHS

Relationship RemoveRemove edge

Relationship ModifyCardinality / direction

Selection SourceDropdown list change

Value ChangeRename/add/remove factor

Override PolicyCanOverride / inheritance

Rule ChangeValidation / lifecycle

Lifecycle ChangeDeprecate / retire

Merge GEMsCombine duplicates

Split GEMSeparate meanings

Namespace MoveChange FQN

Generated ArtifactCode / SQL / API

4 Proposed Change Editor — Before → After

Field	Current (v1.0)	Proposed (v1.1)	Entry Mode
Display Name	Business Case Docket		user_entered
Common Name	BC Docket		user_entered
Technical Name	business_case_docket		NameGenerator
API Name	businessCaseDocket		NameGenerator
Description	Docket containing items related to the business case for a product initiative.	Docket containing items related to the business case pack for a product initiative.	user_entered
Generated Names Preview	`business_case_docket` · `BusinessCaseDocket` · `businessCaseDocket`	`business_case_pack` · `BusinessCasePack` · `businessCasePack`	NameGenerator
GEM ID / FQN	GEM-000587 — identity unchanged (rename ≠ new GEM)		stable

Field	Current	Proposed
LHS	Business Case Docket	Business Case Docket
Relationship	contains	contains
RHS	—	Risk Section
Cardinality	—	0..1
Mandatory	—	FALSE

5 Scope of Change

Apply Prospectively?

Apply Retrospectively?

Apply to Existing M0 Instances?

Apply to Child GEMs?

Apply to Inherited Classes?

Apply to Client Overrides?

Apply to Templates?

Apply to Generated Names?

Apply to Generated Code/API/SQL?

Require Migration?

Require New Baseline?

6 Override & Inheritance Impact

CanOverride

IsOverridden

Parent GEM

Override Scope

Client Alpha has overridden Display Name to "Investment Case Pack". Parent rename will not overwrite Client Alpha override (CanOverride = TRUE). No Conflicts Detected.

Child GEMs inheriting

Business Case Section Template BC Docket Variant (Client Beta)

7 M-Level Impact

M-Level	Impact Question	Status	Detail
M3	Does this alter modeling grammar?	None	Rename does not change Contains / grammar rules
M2	Does this alter vocabulary?	None	Docket kind vocabulary unchanged
M1	Does this alter PBMP model/template?	Low	Labels & generated names on M1 model update
M0	Does this affect real instances?	None*	Published instances stay on v1.0 (prospective only)

8 Five-Layer Architecture Impact

Layer	Impact	What Changes
Business	None	No meaning change — only label terminology
Capability & Competency	None	—
Product Mgmt	Low	Discovery labels, templates, workbench UI
Application / Data	Low	UI labels, PDF template headers (if regenerated)
Technology / GSM	None	No infra / deployment impact

9 Product Mgmt Traceability Impact

Business Case → BRD → SRS / Spec → HLD → LLD → Code → Test → Release → Operate

Phase	Impact
Product Discovery	Low — Workbench labels, Docket display name
Product Design	Low — Template references, UI labels
Product Development	Optional — API regen only if "Apply to Code" = Yes
Product Launch	None — Release notes optional
Operate & Leverage	None — Existing published dockets unchanged

10 Relationship Graph Impact

Business Case Pack

├──

contains → Business Case Section

contains → Problem Statement Section

contains → Benefits Section

refines ← Business Need

usedBy → Product Discovery Workbench

exportedAs → PDF Template

baselinedAs → BusinessCaseTemplate_v1

Green = new edge · Amber = label/reference impacted · Center = proposed display name

11 Rule Validation Panel 2 Blocking 2 Warnings 5 Safe

Check	Result	Detail
Naming conflict check	Blocking	`business_case_pack` already used in Client Alpha data — resolve before apply
Technical name uniqueness	Blocking	API namespace collision with GEM-000612 (Client Beta)
Lifecycle check	Warn	Published GEM — change via baseline v1.1 recommended
Mandatory rule check	Warn	No mandatory rule defined for generated name sync
GEM identity stable	Pass	GEM-000587 unchanged — rename ≠ new GEM
Relationship legality	Pass	No relationship structure change
Override conflict	Pass	Client Alpha override preserved (CanOverride = TRUE)
M-level consistency	Pass	M1 rename — no M2/M3 grammar change
Access / permission	Pass	Priya Mehta has Change Request rights
Instance migration	Pass	Prospective only — 256 M0 published records frozen

12 Simulation / Preview

✓ Display Name → Business Case Pack

✓ Generated: business_case_pack, BusinessCasePack, businessCasePack

✓ Alias retained: BC Docket (historical reference)

✓ New version: Business Case Pack v1.1 · Old retained: Business Case Docket v1.0

✓ 4 generated names updated · 9 artifacts impacted (Workbench, PDF Template, JSON Schema…)

✓ 0 instances impacted (prospective only)

✓ Relationships: structure unchanged (rename only)

13 Migration Plan

Item	Decision	Action
Published instances (M0)	Keep v1.0	Frozen — do not rename retrospectively
Draft instances	Opt-in	Can opt into v1.1 labels
Child templates	Apply	Update display labels on next publish
Generated SQL/API/code	Skip	Apply to Code = No
Test cases	Review	UI label assertions may need update
Rollback plan	Baseline v1.0	Restore previous baseline if needed

14 Approval Workflow Medium → PM + Steward

✓

Priya Mehta — Product Manager (Requester)

Approved

Arun Sharma — Product Architect

Pending

Neeraj Singh — GEM Governance Owner

Pending

Risk Level	Approval Required
Low	GEM Steward
Medium	Product Manager + GEM Steward
High	Architecture Board
Critical	Business Owner + Architecture + Release Manager

15 Audit / Evidence

Reason Category

Evidence Notes

Attachment

📎 Client_Terminology_Request_Jul2026.pdf

Effective Date

Rollback Baseline

Audit Field	Value
Who requested	Priya Mehta · Product Manager
What changed	Display name, common name, technical name, API name
Old value	Business Case Docket / business_case_docket
New value	Business Case Pack / business_case_pack
Reason	Client terminology alignment — "Business Case Pack"
Scope	Prospective only · Templates Yes · M0 frozen
Evidence	Change request note + Client_Terminology_Request_Jul2026.pdf

16 Final Apply Change — Confirmation Summary

Rename

Change Type

v1.0 → v1.1

Baseline

Artifacts

2/3

Approvals

Change: Display Name Business Case Docket → Business Case Pack
Identity: GEM-000587 remains stable
Scope: Prospective only · Templates Yes · Generated names Yes · M0 published frozen
Validation: 2 blocking · 2 warnings · 5 safe — resolve naming conflict before Apply
Result: New v1.1 Business Case Pack · v1.0 retained · Alias BC Docket retained · Audit GEM-CHG-000245
Migration: New dockets use v1.1 · Approved stay on v1.0 · Drafts opt-in
Audit: GEM-CHG-000245 will be written on Apply

GEM-CHG-000245 · GEM-000587