The same data is re-entered, closing relies on multiple files and each team defends its own process definition.
ESSOR ERP solution
Choose and deploy a business ERP without freezing the organisation
Clarify processes, master data, ownership, migrated data and deployment waves before configuration.
For: Executive, finance, operations, industry, agriculture, commerce and IT leadersWhat to clarify before discussing a solution
Which rules should be common, and which variants should remain governed by business, site or activity?
The answer does not lie in an isolated feature: it is built by connecting rules, actors, data and evidence.An ERP decision pack that distinguishes core, variants, interfaces, migration, ownership and success criteria.
Four decisions to make before configuration
These decisions make the scope testable and prevent structural choices from being discovered during the project.
Name an owner for each cross-functional process
The decision must specify the rule, its owner, the required data and the evidence used to accept it.
Define the authoritative master-data core
The decision must specify the rule, its owner, the required data and the evidence used to accept it.
Classify each interface by operational criticality
The decision must specify the rule, its owner, the required data and the evidence used to accept it.
Choose a pilot wave that genuinely crosses the organisation
The decision must specify the rule, its owner, the required data and the evidence used to accept it.
A readable end-to-end flow
Scope is not a list of modules. It is a chain of events, ownership and decisions.
1Target processes
2Master data
3Finance and control
4Interfaces
5Migration and adoption
In the first scoping
- One representative flow and its useful variants
- Authoritative events and minimum data
- Roles, decisions and escalation times
- Acceptance criteria and baseline measurement
To sequence in waves
- Additional sites, activities or populations
- Rare variants that do not condition the pilot
- Automations whose rule is not yet stable
- Advanced dashboards after source reliability
To decide explicitly
- Name an owner for each cross-functional process
- Define the authoritative master-data core
- Classify each interface by operational criticality
- Choose a pilot wave that genuinely crosses the organisation
From direction to measured improvement
- 1Navigator
- 2Personalised review
- 3Scoping workshop
- 4Wave-based deployment
- 5KPI measurement
Each stage produces a decision or evidence reusable in the next. Deployment remains business-led and verifiable.
Measure to decide, not to fill a dashboard
Every KPI needs a definition, a source, a cadence and an associated decision.
KPIFormulaSourceDecision
Critical data qualityComplete, valid and current data ÷ data checkedMaster data and control logsAddress rules and ownership at source
Integration latencyAvailability time − event creation timeExchange logs and timestampsSecure the flows that condition operations
Working capital requirementInventory + receivables − operating payablesInventory, sales, purchasing and collectionsReduce tied-up capital without weakening service
Decision lead timeDecision date − signal dateAlerts, decisions and actionsShorten the path from signal to action
06 · Business scenario
An ERP deployed by value streams
- Situation
- A company wants to replace several tools without reproducing the same breaks or interrupting operations.
- Approach
- Scoping starts from critical decisions and flows, builds the data core, then sequences migration, interfaces and adoption by value stream.
- Target outcome
- The scope becomes testable and every wave has a clear business acceptance criterion.
Useful answers before the first discussion
01Where should we start in practical terms?
Choose a representative scope spanning “Target processes” and “Master data”, then document one normal case and one frequent exception. The first flow should be important enough to matter but contained enough to observe end to end.
02Do all existing systems need replacing?
No. Scoping starts with decisions, authoritative events and ownership. It then determines what should be retained, integrated, replaced or simply better governed, wave by wave.
03What data should be prepared before a workshop?
Prepare a few real cases, the volumes shaping the operation, the main variance reasons and the sources used to measure Critical data quality. The quality of examples matters more than the quantity of documents.
04How should the right pilot scope be chosen?
Choose a scope with an available owner, accessible data, a meaningful exception and a measurable outcome. Avoid both an overly simple case that proves nothing and an overly broad scope that dilutes learning.
05How can scope changes during the project be limited?
Make assumptions, interfaces, variants, exceptions and acceptance criteria explicit. Every new request can then be classified: essential to the wave, suitable for a later wave, or outside the objective. Discussion focuses on impact rather than intuition.
Next step
Turn this guide into a personalised review
Complete Navigator to position your context, then use the review as the starting point for a scoping workshop.
- 1Navigator
- 2Personalised review
- 3Scoping workshop
- 4Wave-based deployment
- 5KPI measurement
Complementary guides
Guides by suite
EMS Logistics suite
Transform transport & logistics
Connect order, warehouse, transport, delivery and invoicing around the same events and responsibilities.
- Service promise
- Warehouse execution
- Transport plan
Guides by suite
EMS Industry suite
Connect planning to the shop floor
Build decision continuity across demand, materials, capacity, execution, quality, maintenance and cost.
- Demand and schedule
- Materials and capacity
- Execution and WIP
Guides by suite
EMS Commerce suite
Unify omnichannel commerce
Connect catalogue, availability, order, payment, fulfilment, delivery, return and customer relationship.
- Catalogue and pricing
- Available-to-promise inventory
- Order and allocation