ASCM Certified in Transformation for Supply Chain (CTSC) flashcards
CTSC · Build recall with a focused review session.
32 cards. Read the term and the definition here. The deck at the top of this page is optional.
- Transformation vs. continuous improvement
- Transformation redesigns strategy, process, and capability for step-change outcomes; continuous improvement optimizes existing designs incrementally. Confusing the two leads to underfunded programs and unrealistic benefit expectations.
- SCOR management processes
- Plan, Source, Make, Deliver, Return, and Enable form the reference taxonomy used to scope supply chain processes and structure transformation assessments.
- Perfect order rate
- Percentage of orders delivered complete, on time, damage-free, and with correct documentation. It is a composite customer-facing metric used as a transformation baseline.
- Cash-to-cash cycle
- Days inventory outstanding plus days sales outstanding minus days payables outstanding. It measures how long cash is tied up in supply chain operations.
- Forecast bias
- The systematic tendency to over- or under-forecast, computed as the sum of actual minus forecast divided by the sum of actual. MAPE hides bias, so measure it separately.
- Value leakage
- The gap between designed and realized benefit, typically occurring at functional or system handoffs. Tracking it requires benefit ownership after go-live.
- Supply chain maturity model
- A staged framework describing capability progression from functional silos through internal integration to external collaboration and autonomous, predictive operations.
- Business case essentials
- A fundable case states baseline, target, benefit timing, cost, and risk-adjusted return. Benefits without a measurement method and owner are not credible.
- Strategy traceability
- Every initiative must trace upward through transformation themes to strategic objectives and KPIs. Untraceable initiatives are candidates for de-scoping.
- Steering committee role
- The steering committee holds funding and escalation authority, resolves cross-initiative conflicts, and approves stage-gate passage. It does not manage day-to-day delivery.
- Stage gate
- A funding decision point with predefined exit criteria. Passing a gate authorizes the next tranche; it is a decision, not a status review.
- RACI accountability rule
- Each decision should have exactly one accountable owner. Multiple accountable parties create ambiguity and are a governance defect rather than shared ownership.
- Benefit realization owner
- A business-side individual accountable for measuring and delivering a specific benefit after go-live, using a method and cadence agreed before implementation.
- Decision rights matrix
- A mapping of who decides, who is consulted, and who is informed for each decision type, reducing escalation load and duplicated authority.
- Risk register minimum fields
- Each risk needs a probability, impact, owner, and mitigation. Risks without an assigned owner are effectively unmanaged.
- Phased versus big-bang delivery
- Big-bang releases everything at once with high risk; phased delivery by geography, unit, or process reduces risk but adds interim integration complexity.
- Critical path and float
- The critical path is the longest chain of dependent activities. Float is slack on non-critical activities and is consumed first when delays occur.
- Minimum viable footprint
- The smallest end-to-end process slice that delivers measurable value, used to scope the first release and validate design before wider rollout.
- Cross-team dependencies
- Work where one team's output gates another's start. They are the leading cause of schedule slippage and require explicit tracking at program level.
- Cutover plan components
- Data migration, interface freeze, reconciliation, rollback criteria, and hypercare duration. Missing rollback criteria converts a reversible event into an unrecoverable one.
- Supply chain test layers
- Unit, integration, end-to-end process, user acceptance, and performance/volume testing. End-to-end tests validate cross-system process behavior rather than individual transactions.
- Data readiness gates
- Pre-migration checks on completeness, accuracy, uniqueness, timeliness, and ownership of master data. Failing a gate defers migration rather than proceeding with defects.
- Hypercare exit criteria
- Predefined thresholds for defect severity, ticket aging, and business KPI stability that determine when elevated post-go-live support ends.
- Stakeholder influence-interest map
- A grid plotting stakeholders by influence and interest. High-influence, high-interest parties need co-design roles; low-interest parties need efficient information updates.
- ADKAR sequence
- Awareness, Desire, Knowledge, Ability, Reinforcement. The model is sequential: missing desire blocks knowledge from converting into ability.
- Resistance diagnosis
- Resistance usually stems from capability gaps, misaligned incentives, missing information, or perceived loss of status. The root cause determines the correct intervention.
- Change readiness dimensions
- Leadership alignment, capacity for change, capability, culture, and communication effectiveness. Readiness gaps predict adoption failure more reliably than technical readiness.
- Change curve productivity dip
- Shock, denial, frustration, acceptance, and commitment stages predict a temporary performance decline after go-live, which should be planned into benefit timing.
- Communication plan fields
- Audience, message, channel, sender, and frequency. Sender credibility affects reception more than channel choice does.
- Adoption metrics
- Active usage rate, transaction compliance, workaround incidence, and time-to-competence measure whether a change is actually embedded rather than merely deployed.
- Integration pattern selection
- APIs suit real-time loosely coupled needs; EDI/batch suits high-volume scheduled exchange; event-driven suits pub/sub triggers; file transfer persists in legacy estates.
- Control tower capabilities
- End-to-end visibility, predictive analytics, and execution orchestration. Visibility without orchestration authority produces insight but no operational change.