As-Is & To-Be Process Modeling Flashcards
7 cards from real ERP practice questions. Tap to flip, then mark Knew It or Still Learning — missed cards come back until you master them.
Read the first 7 As-Is & To-Be Process Modeling flashcards as text
In As-Is process documentation, what is the purpose of calculating the 'process efficiency ratio'?
Answer: To compare value-added time against total elapsed time and identify waste
The process efficiency ratio (value-added time ÷ total lead time) reveals how much of the elapsed time actually creates customer value versus waste.
A 'future-state process map' differs from the As-Is map primarily because it:
Answer: Incorporates ERP automation, eliminated steps, and redesigned handoffs based on desired outcomes
The future-state map reflects redesigned processes that leverage ERP capabilities, removing manual steps and restructuring handoffs.
When performing As-Is process mapping, what is a key risk of relying solely on interviews with managers rather than frontline workers?
Answer: Managers may describe the intended process rather than the actual process executed on the floor
Managers often describe the ideal or policy-defined process, while frontline workers know the workarounds and actual steps taken daily.
In To-Be modeling, which concept ensures that the redesigned ERP process meets both business requirements and regulatory compliance obligations?
Answer: Embedded controls and compliance checkpoints within the process flow
Embedding controls and compliance checkpoints directly in the To-Be process design ensures regulatory requirements are enforced automatically within the ERP.
A 'digital twin' of a business process, when used in ERP process modeling, allows project teams to:
Answer: Simulate and test the To-Be process virtually before configuring the actual ERP system
A digital twin simulates the To-Be process in a virtual environment, enabling teams to identify issues and optimize the design before system configuration begins.
Which of the following is a valid reason to intentionally preserve a non-standard process variant in the To-Be model during an ERP implementation?
Answer: The variant is legally mandated or provides a documented competitive advantage
Preserving non-standard process variants is justified only when they are legally required or represent a proven competitive differentiator.
In ERP gap analysis, a 'workaround' identified in the As-Is state most accurately indicates:
Answer: An unofficial fix that employees use to compensate for a system or process limitation
Workarounds are informal, often undocumented fixes that employees create to bypass limitations in current systems or processes.