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
Which artifact is produced during the As-Is analysis phase of an ERP implementation that documents current pain points and inefficiencies?
Answer: Process gap register
A process gap register catalogs current pain points, bottlenecks, and inefficiencies identified during As-Is analysis.
In To-Be process modeling, what does 'straight-through processing' refer to?
Answer: Eliminating manual interventions so transactions complete automatically end-to-end
Straight-through processing means transactions flow automatically from initiation to completion without manual touchpoints.
A swimlane diagram used in As-Is modeling primarily shows which of the following?
Answer: Who performs each process step and handoffs between departments
Swimlane diagrams map activities to the responsible party and visually highlight handoffs across organizational boundaries.
When comparing As-Is and To-Be models, what is the primary purpose of conducting a 'process walk-through' with end users?
Answer: To validate that the documented process accurately reflects reality
Process walk-throughs with end users confirm that the documented As-Is model matches actual day-to-day operations before gap analysis begins.
In ERP process modeling, a 'rekeying' activity in the As-Is model most likely signals which improvement in the To-Be model?
Answer: Integration between systems to eliminate duplicate data entry
Rekeying the same data into multiple systems is a classic integration gap that the To-Be model addresses through system integration.
Which modeling notation is most commonly used in To-Be ERP process design to represent decision gateways and parallel flows?
Answer: BPMN (Business Process Model and Notation)
BPMN provides standardized symbols for events, activities, gateways, and flows, making it the standard for ERP To-Be process design.
During As-Is documentation, the team discovers that three different departments use three different forms for the same purchase request. This is an example of which type of process issue?
Answer: Lack of process standardization
Multiple forms for the same process across departments indicate a lack of standardization, a key driver for ERP harmonization.