# CSDM V3 Framework Mapping: APQC V7.2.1

- Title: CSDM V3 Framework Mapping: APQC V7.2.1
- Video URL: https://www.youtube.com/watch?v=b61XbPlbGn4
- Playlist position: 64
- Frameworks discussed: CSDM, APQC
- Evidence basis: YouTube MCP playlist metadata, `yt-dlp` chapter metadata, and a local `faster-whisper` transcription recovered from the video audio after MCP transcript calls failed on 2026-03-26.

## Short summary
This session treats APQC as a process-classification and benchmarking framework that can seed CSDM business capability and service portfolio design. The main thread is that APQC's operating processes look like a value-stream style view, while its classification hierarchies give a practical starting point for capability and service decomposition.

## Key mapping concepts
- APQC process classification framework as a source for capability and service decomposition
- Operating processes described as the main value-stream style flow for product and service delivery
- Supporting processes positioned as automation and enablement areas, with IT as one of those supporting processes
- Business capability hierarchy and service portfolio identified as the strongest CSDM bridge points
- Industry-specific APQC variants suggested as a practical bootstrap for ontology and taxonomy work

## Notable terminology used
- APQC
- Benchmarking
- Process classification framework
- Six Sigma
- Operating processes
- Value stream
- Business capability hierarchy
- Service portfolio

## What still seems valid
The strongest enduring idea is to use an industry process taxonomy as scaffolding for capability modeling and service portfolio shaping instead of inventing capability trees from scratch. That remains useful for ontology work, especially when a Digital Product model has to stay linked to business capabilities, lifecycle activities, and service portfolio structures.

## What appears outdated or version-specific
The session is tied to APQC v7.2.1 and a CSDM v3 framing of products and services. It also reflects a period when the ServiceNow-specific story around digital products was still maturing, so the crosswalk should be treated as a historical starter set rather than a current normative mapping.

## Transcript
Local transcript recovered on 2026-03-26 by downloading the audio and transcribing it after the YouTube MCP transcript path failed.

Cleaned transcript excerpt:
- `0:14-1:20`: APQC is introduced as a benchmarking and process-management organization, while CSDM is framed as a ServiceNow data model for products, digital products, and services across their lifecycles.
- `2:46-3:35`: The APQC operating-process layer is described as the main value-stream-like area: product development, product and service management, market and sell, delivery, and customer service, with the remaining layers acting as supporting processes.
- `5:30-6:47`: The speaker calls out two especially useful bridge points: APQC can seed the business capability hierarchy in CSDM design, and it can also shape business services and the service portfolio because automated processes often end up reflected as services.

Chapter landmarks recovered from the YouTube page:
- `1:53` Origins of CSDM
- `3:44` Develop and Manage Business Capabilities
- `5:10` How APQC Maps to the CSDM Framework

## Relevance to current ontology work
High relevance for capability and service-portfolio alignment. APQC is not an operational ontology on its own, but it is a strong source for disciplined capability, process, and service taxonomy inputs that can anchor Digital Product, business capability, and service portfolio relationships in a governed way.
