ASCM Certified in Transformation for Supply Chain (CTSC) cheat sheet

Transformation is a structural redesign of strategy, process, and capability; continuous improvement is incremental optimization within an existing design.

Four transformation archetypes: process-led, technology-led, network/structural, and business-model; most programs blend at least two.

Maturity models (e.g., SCOR-based, Gartner-style) stage capability from functional silo to integrated, then to autonomous and predictive.

SCOR's six management processes - Plan, Source, Make, Deliver, Return, Enable - provide the reference taxonomy for scoping change.

Baseline metrics to capture before design: perfect order rate, cash-to-cash cycle, total delivered cost, forecast bias, and inventory turns.

Forecast bias = sum(actual − forecast) / sum(actual); MAPE treats over- and under-forecast symmetrically, so track bias separately.

Cash-to-cash cycle = days inventory outstanding + days sales outstanding − days payables outstanding.

Value leakage is the gap between designed and realized benefit; it typically appears at handoffs between functions or systems.

Strategy hierarchy: vision → strategic objectives → transformation themes → initiatives → KPIs; every initiative must trace upward to a theme.

Business case must show baseline, target, benefit timing, cost, and risk-adjusted NPV or payback; unquantified benefits are not fundable.

Governance bodies: steering committee (decisions and funding), program board (cross-initiative trade-offs), design authority (standards and architecture).

RACI rule: one accountable owner per decision; multiple accountable parties is a governance defect, not a collaboration.

Stage gates authorize funding in tranches; a gate is a decision point with defined exit criteria, not a status review.

Benefit realization requires an owner in the business, a measurement method, and a review cadence agreed before go-live.

Decision rights matrix (who decides, who is consulted, who is informed) prevents escalation load and duplicated authority.

Risk register entries need probability, impact, owner, and mitigation; unowned risks are unmanaged risks.

Delivery sequence options: big-bang, phased by geography or business unit, pilot-then-scale, and wave-based by process; choose by risk tolerance and dependency density.

Critical path is the longest dependent chain; float is the slack on non-critical activities and is consumed first when delays occur.

Minimum viable footprint: scope the first release to the smallest end-to-end slice that delivers measurable value.

Dependency types: finish-to-start (most common), start-to-start, finish-to-finish; cross-team dependencies are the leading cause of slippage.

Cutover planning covers data migration, interface freeze, reconciliation, rollback criteria, and hypercare duration.

Test layers for supply chain systems: unit, integration, end-to-end process, user acceptance, and performance/volume.

Data readiness gates: completeness, accuracy, uniqueness, timeliness, and ownership of master data before migration.

Hypercare exit criteria are defined in advance - defect thresholds, ticket aging, and business KPI stability.

Stakeholder map plots influence against interest; high-influence/high-interest parties need co-design roles, not just communication.

ADKAR sequence - Awareness, Desire, Knowledge, Ability, Reinforcement - is sequential; a gap at any element blocks adoption.

Resistance is diagnostic data: identify whether it is rooted in capability, incentive, information, or loss of status.

Readiness assessment dimensions: leadership alignment, capacity for change, capability, culture, and communication effectiveness.

Change curve stages (shock, denial, frustration, acceptance, commitment) predict productivity dip timing after go-live.

Communication plan specifies audience, message, channel, sender, and frequency; sender credibility matters more than channel.

Training transfer requires role-based content, practice on real transactions, and manager reinforcement after the session.

Adoption metrics: active usage rate, transaction compliance, workaround incidence, and time-to-competence.

Integration patterns: API (real-time, loosely coupled), EDI/batch (high volume, scheduled), event-driven (publish/subscribe), and file transfer (legacy).

ERP is the system of record for transactions; planning systems (APS) optimize; visibility platforms aggregate multi-party data.

Control tower capabilities: end-to-end visibility, predictive analytics, and execution orchestration; visibility alone is not orchestration.

Master data domains in supply chain: material, vendor, customer, location, and pricing - each needs a defined owner and stewardship model.

Data quality dimensions: completeness, accuracy, consistency, timeliness, validity, and uniqueness.

RPA suits rule-based, high-volume, stable processes; it breaks when underlying screens or rules change frequently.

Cloud ERP shifts spend from capital to operating expense and moves upgrade cadence to vendor-controlled releases.

Digital twin models the physical network for scenario simulation; value depends on model fidelity and data freshness.