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
During a To-Be process design workshop, stakeholders from two business units disagree on a proposed process change. What is the recommended facilitation approach?
Answer: Escalate to the executive sponsor for a decision based on business impact analysis
Disagreements on process design should be escalated to the executive sponsor who can make decisions based on strategic business impact.
What is the primary purpose of a 'process decomposition' technique when building an As-Is model?
Answer: To break high-level processes into sub-processes and tasks for detailed analysis
Process decomposition breaks broad processes into progressively detailed sub-processes and tasks, enabling thorough As-Is analysis.
In an ERP To-Be model, 'role-based access control' is defined during process modeling to ensure:
Answer: Only authorized users can perform specific process steps, enforcing segregation of duties
Defining role-based access during To-Be modeling ensures that segregation of duties and authorization controls are built into the process design.
A key deliverable of the As-Is and To-Be analysis phase that is used to obtain formal stakeholder sign-off is called:
Answer: Business process design document (BPDD) or functional specification
The Business Process Design Document formally captures both As-Is and To-Be processes and is the document used to obtain stakeholder approval before configuration begins.
When the To-Be process requires data that does not exist in the current As-Is system, this gap is addressed through which activity?
Answer: Data enrichment or collection initiatives planned as part of the ERP implementation
Missing data identified during gap analysis requires a data enrichment or collection plan to ensure the To-Be process has the information it needs.
In lean process thinking applied to To-Be ERP modeling, which of the following is classified as 'non-value-added but necessary' work?
Answer: Regulatory reporting and compliance documentation required by law
Regulatory reporting does not add direct customer value but is legally required, making it non-value-added yet necessary in the To-Be design.
Which best describes the relationship between the To-Be process model and the ERP system configuration blueprint?
Answer: The To-Be model drives the configuration blueprint, specifying how ERP settings must be set to support redesigned processes
The approved To-Be process model serves as the specification from which the ERP configuration blueprint is derived, ensuring the system supports the desired processes.