Industry process reference models (APQC / BIZBOK / SCOR / eTOM)

Across a single deep-research round (2026-08-17 through 2026-08-23), Ray Data Co tested whether any of the major established industry process or capability frameworks could be borrowed wholesale for the Organizational Platform's function/motion decomposition (10 functions running 36 motions, backing an 80-role catalog). The same negative pattern recurred across every framework tested: general-purpose models decompose functions reliably, but almost none of them offer a trustworthy catalog of motions — the substitutable choice of how a function executes (field sales vs. inside sales vs. PLG, centralized vs. federated finance, and so on).

• [[2026-08-17-apqc-pcf-function-motion-mapping]] read APQC's Process Classification Framework (13 categories, 1,000+ processes) in full and found it is a hierarchy-of-process, not a hierarchy-of-choice — useful for routing and role-cost backbones, silent on motion.
• [[2026-08-17-bizbok-operating-model-function-motion-mapping]] found the Business Architecture Guild's metamodel enforces a strict "object-focus invariance" rule for capability decomposition (a capability's child can never veer outside the parent's object focus) — but confirmed the Organizational Platform's function tree is not a BIZBOK capability map, so the rule doesn't directly bind it.
• [[2026-08-17-gtm-motion-origins-industry-reference-models]] identified SCOR as the one model that decomposes to a genuine Level-2 catalog of substitutable process types (S1-S3/M1-M3/D1-D4) — but that finding rested on a ~2003 SCOR 6.0 booklet.
• [[2026-08-22-scor-digital-standard-level2-process-types]] verified the current SCOR Digital Standard (v14.0) against primary ASCM PDFs and found the Level-2 layer survived but every one of those specific codes did not — the "stable through SCOR 12.0" claim was withdrawn as factually wrong, not just unsourced.
• [[2026-08-23-etom-per-function-motion-catalog]] read the TM Forum eTOM specification directly and found it declares channel-agnosticism as an explicit design principle (motion-modeling as an anti-pattern) — yet names RDCO's own independently-derived Sales motion set as illustrative prose in one process description.
• [[2026-08-22-cstore-fuel-retail-reference-models]] confirmed no industry body (NACS, Conexxus, FMI, Business Architecture Guild, OMG/ARTS, IFSF) has ever built a process reference model for convenience/fuel retail — a genuine, verified whitespace directly relevant to the live [[2026-07-17-kwik-trip-engagement-notes-stakeholders-and-priorities]].
• [[2026-08-22-bizbok-object-focus-invariance-real-estate]] closed the loop on the BIZBOK question, confirming object-focus invariance has no exception mechanism and doesn't extend to organization/business-unit maps at all.

Why this is in the vault

This is the one round in the vault where RDCO systematically stress-tested "should we borrow an established taxonomy instead of building our own" against every major standards body, so the negative result — no framework offers a ready-made motion catalog, and the closest candidate (SCOR) turned out to be citing a 23-year-old document as if it were current — is worth keeping as a single reference rather than re-discovered per brief.

Mapping against Ray Data Co

This directly de-risks the Organizational Platform's core taxonomy work: it confirms the "motion" layer above functions is RDCO's own original contribution, not something to import, and it surfaces a real, verified market whitespace (no c-store/fuel-retail reference model exists anywhere) that the [[2026-07-17-kwik-trip-engagement-notes-stakeholders-and-priorities]] can be first to fill. It also surfaces a process risk worth tracking: the first brief in this round failed /verify-vault-write at 4-of-7 rubric items (arithmetic errors, an unsourced "stable through SCOR 12.0" claim that later proved false, and three sibling briefs independently proposing different, unreconciled schema amendments on the same night). That's a concrete instance of the fresh-eyes verification gate catching exactly the kind of confident-but-wrong synthesis it exists to catch, and argues for tighter cross-brief reconciliation when a research round fans out into siblings that touch the same live schema.