Pfc Vsom

1. ORG-CONTEXT (mandatory): Load 01-org-context-{instance}.jsonld
2. MACRO analysis (recommended): Load 02-macro-analysis-{instance}.jsonld — scenarios, PESTEL factors
3. INDUSTRY analysis (recommended): Load 03-industry-analysis-{instance}.jsonld — TOWS strategies, Ansoff vectors, Porter forces
4. Existing VSOM (optional): Load any existing vsom-{instance}*.jsonld for review/refinement
5. RRR instance data (recommended): Load RRR roles for ownership assignment

Synthesis brief: Present to user:

VSOM Context for {orgName} ({instance-code})

Org Profile: {industry}, {orgType}, {orgStage}, {geography}
Products:    {count} ({product-names})
Maturity:    Level {level}

SA Analysis Available:
  MACRO:    {yes/no} — {count} PESTEL factors, {count} scenarios
  INDUSTRY: {yes/no} — Attractiveness {score}/5, {count} TOWS strategies

Key Strategic Inputs:
  - {top TOWS strategy 1}
  - {top TOWS strategy 2}
  - {top scenario implication}

If SA analysis is absent, warn: "MACRO and INDUSTRY analysis not available. VSOM formulation will lack analytical grounding. Recommend running pfc-macro-analysis and pfc-industry-analysis first."

Quality Gate G1 — Context Complete:

• ORG-CONTEXT loaded with org profile, products, market
• SA analysis status confirmed (present or acknowledged absent)
• Synthesis brief presented and confirmed by user

Section 2: Vision Formulation

Draft the strategic vision:

Vision statement guidance:

• Start with "To be..." or "To become..." or a declarative future state
• Must be aspirational but achievable
• Should reference the customer/market value, not internal process
• If scenarios available: stress-test vision against all scenarios — does it hold?

If MACRO scenarios available, validate:

• Does the vision remain relevant in the most likely scenario?
• Does it survive the worst-case scenario?
• Is it ambitious enough for the best-case scenario?

Quality Gate G2 — Vision Coherent:

• Vision statement 50-500 characters
• Horizon >= any strategy horizon (e.g., vision 5yr >= strategy 3yr)
• Owner is a C-Suite role (CEO, CMO, CTO, COO, CFO)
• If scenarios available: vision validated against all scenarios

Section 3: Strategy Definition

Define 2-5 strategies that operationalise the vision:

For each strategy:

SA Integration:

• If TOWS strategies available: every strategy should trace to at least 1 TOWS output (JP-IND-002)
• If scenarios available: link to scenario implications (JP-MAC-001)
• If Ansoff available: growth strategies should reference Ansoff vectors

MECE check: Strategies must be mutually exclusive within their scope (no overlapping remit) and collectively exhaustive (full strategic agenda covered).

Quality Gate G3 — Strategy Traceability:

• 2-5 strategies defined
• Every strategy informedBy the Vision
• If TOWS available: at least 1 strategy traces to a TOWS output
• If scenarios available: strategies validated against scenario implications
• MECE: no overlapping strategies within the same scope

Section 4: Objective Cascade

For each strategy, define 2-5 strategic objectives:

BSC Perspective Classification:

• Financial: Revenue, margin, cost, shareholder value
• Customer: Satisfaction, retention, acquisition, market share
• Internal Process: Efficiency, quality, innovation, operations
• Learning & Growth: Skills, culture, technology, knowledge

Quality Gate G4 — Objective Balance:

• 2-5 objectives per strategy
• All 4 BSC perspectives represented across the full objective set
• Each objective has a named owner (RRR role reference)
• Each objective classified by BSC perspective
• Priority assigned (P1-P4)

Section 5: BSC Perspective Mapping & Strategy Map

Build the Balanced Scorecard and Strategy Map:

Step 1: Create BSC container:

{
  "@type": "bsc:BalancedScorecard",
  "@id": "bsc:scorecard-{instance}",
  "bsc:perspectives": [
    { "@type": "bsc:BSCPerspective", "bsc:perspectiveName": "Financial", "bsc:perspectiveOwnedBy": "rrr:{CFO-role}" },
    { "@type": "bsc:BSCPerspective", "bsc:perspectiveName": "Customer", "bsc:perspectiveOwnedBy": "rrr:{CMO-role}" },
    { "@type": "bsc:BSCPerspective", "bsc:perspectiveName": "InternalProcess", "bsc:perspectiveOwnedBy": "rrr:{COO-role}" },
    { "@type": "bsc:BSCPerspective", "bsc:perspectiveName": "LearningGrowth", "bsc:perspectiveOwnedBy": "rrr:{CTO-role}" }
  ]
}

Step 2: Assign each objective to its BSC perspective.

Step 3: Build Causal Links (Strategy Map):

Causal chains flow bottom-up: Learning & Growth → Internal Process → Customer → Financial

For each causal link:

Build at least 1 complete chain spanning all 4 perspectives.

Quality Gate G6 — BSC Causal Chain:

• All 4 BSC perspectives have at least 1 objective assigned
• Each perspective has an RRR role owner (JP-BSC-002)
• At least 1 complete causal chain (L&G → Internal → Customer → Financial)
• Each causal link has a testable hypothesis

Section 6: Metric Definition

For each objective, define 1-3 metrics:

Leading vs Lagging mix:

• Leading indicators: predict future performance (e.g., pipeline volume, training hours)
• Lagging indicators: measure outcomes (e.g., revenue, churn rate)
• Best practice: at least 1 leading + 1 lagging per strategy

Quality Gate G5 — Metric Coverage:

• Every objective has at least 1 metric
• Mix of leading and lagging indicators across the metric set
• Each metric has formula, unit, baseline, and target
• Data source identified for each metric

Section 7: Output Assembly

Assemble the complete VSOM + BSC JSON-LD:

{
  "@context": {
    "vsom": "https://platformcore.io/ontology/vsom/",
    "bsc": "https://platformcore.io/ontology/bsc/",
    "orgctx": "https://platformcore.io/ontology/org-context/",
    "rrr": "https://platformcore.io/ontology/rrr/",
    "pfc": "https://platformcore.io/ontology/"
  },
  "@type": "vsom:VSOMFramework",
  "@id": "vsom:framework-{instance}",
  "vsom:organizationContextRef": "org:ctx-{instance-code}",
  "vsom:vision": { "...from S2..." },
  "vsom:strategies": [ "...from S3..." ],
  "vsom:objectives": [ "...from S4..." ],
  "vsom:metrics": [ "...from S6..." ],
  "bsc:balancedScorecard": { "...from S5..." },
  "bsc:strategyMap": { "...from S5 causal links..." },
  "pfc:version": "1.0.0",
  "pfc:status": "draft",
  "pfc:createdDate": "YYYY-MM-DD"
}

MECE Validation:

• Strategies MECE within scope (no overlap)
• Objectives collectively exhaustive per strategy
• BSC 4 perspectives = MECE by design
• Metrics cover all objectives (no gaps)

Write to: {working_dir}/ve-pipeline-output/04-vsom-{instance}.jsonld

Quality Gate G7 — MECE Compliance:

• Strategies mutually exclusive within scope
• Objectives collectively exhaustive for each strategy
• Metrics cover every objective (no orphan objectives)
• BSC perspectives balanced (no empty perspective)

Section 8: Validation

Run final validation checks:

• All G1-G7 gates passed
• JSON-LD well-formed with correct @context
• Vision horizon >= max strategy horizon
• Every strategy traces to Vision
• Every objective traces to a Strategy and BSC Perspective
• Every metric traces to an Objective
• At least 1 complete BSC causal chain
• All RRR role references are valid

Present summary:

VSOM + BSC Summary: {orgName} ({instance-code})
  Vision:      "{visionStatement}" ({horizon}yr)
  Strategies:  {count} ({types})
  Objectives:  {count} (F:{f-count} C:{c-count} I:{i-count} L&G:{lg-count})
  Metrics:     {count} ({leading} leading, {lagging} lagging)
  BSC:         4 perspectives, {causal-chains} causal chains
  SA Grounding: MACRO={yes/no}, INDUSTRY={yes/no}
  Output:      {file_path}

Ontology References

Join Patterns