ERP
Resources and accounting: procurement, inventory, production, and finance. The functions depend on the configuration. Reliable planning requires accurate stock levels, standards, and timely recording of transactions.
Learn how to define roles, choose ERP, CRM, and BPM tools, assess risks, and measure results with data.
An organizational management system connects company goals, people's accountability, operating rules, and performance metrics. Corporate IT systems support this work by recording data and decisions, assigning tasks, and helping monitor deviations. For example, reducing order lead time requires a process owner, aligned sales and shipping rules, up-to-date stock levels, and clear time measurement. ERP or CRM helps implement these rules.
Below is how to describe the process, choose tools, assess risks, and validate the result using data.
How to manage process change
Goal and accountability
Rules and data
Execution
Validate the result
The management system defines the results the organization aims to achieve and how it coordinates the work of its departments.
Management sets the goals; the process owner is accountable for the outcome from start to finish; executors receive the authority and action rules.
An operating procedure describes the normal workflow and exceptions, while metrics help detect deviations. IT architecture is part of this system.
A single reference directory can have an assigned master system, even if other operations are performed in different applications.
This requires rules for updates and data exchange.
Company size alone does not determine the number of platforms: assess the required functions, existing systems, data access, and the team's ability to support the solution.
ERP, CRM, and BPM support different areas of work; a specific product may combine several functions. A detailed BPM overview is available in the article process management.
Resources and accounting: procurement, inventory, production, and finance. The functions depend on the configuration. Reliable planning requires accurate stock levels, standards, and timely recording of transactions.
Customers and sales: contacts, deals, inquiries, and interaction history. Duplicate and data exchange rules determine how customer information is linked to contracts and orders in other systems.
Process workflow: roles, tasks, deadlines, approvals, and exceptions between departments. The system shows delays and owners; the process owner decides on priorities and rule changes.
| Process | Outcome owner | Data | Metric | Measure before and after |
|---|---|---|---|---|
| Order processing | Order Fulfillment Manager | Time for receipt, confirmation, and warehouse handover; cancellations and returns | Median time to warehouse handover; share of returns for correction | Use the same order types and time boundaries. Compare regular and peak periods separately. |
| Product publishing | Product Content Manager | PIM item card readiness, submission, marketplace status, errors | Time to approved publication; number of revisions | Use one marketplace and comparable categories. Account for moderation waiting times and manual adjustments. |
| Contract approval | Contract process owner | Project version, approval submission, participant decisions, returns | Approval time; number of return cycles | Separate standard contracts from individual terms. Record the expectations of each role. |
| Management reporting close | Finance Manager | Source readiness date, adjustments, report acceptance | Preparation time; discrepancies after acceptance | Use the same report structure and calculation rules. Include reconciliation and report rebuilding time. |
Assign an owner, define the process start and end, and collect typical cases and exceptions. Record baseline metrics.
Map functions to the process and check integrations, data quality, infrastructure, and support terms. Assess the risks.
Configure one working scenario, migrate validated data, train users, and accept the result against predefined criteria.
After stabilization, compare metrics for a comparable volume and account for errors and costs. Adjust the process and expansion plan based on the results.
The core budget includes assessment, configuration and development, licenses, integrations, data cleansing and migration, training, and launch.
For the selected period, calculate operating costs separately: infrastructure, support, updates, backups, and process owner effort.
Already known work is included in the planned estimate.
The contingency is justified by the risk register.
For each event, assess its probability, cost, and delay, and assign an owner and action in advance. For example, an unsatisfactory migration test means additional data cleansing; exceeding the agreed load means reviewing the infrastructure.
Use of the reserve is tied to this condition and approval of the budget change. Amount: probability × financial impact
It helps assess expected losses but does not replace testing an adverse scenario: related risks may occur together. The contingency must reflect the consequences the company is prepared to cover; there is no universal percentage for all projects.
In case catalog The results are linked to a specific process and client. Below are examples with primary sources. They help select a change mechanism but do not guarantee the same effect for another company.
In B2B order case An 85% reduction in processing time was reported: the original timeframe was up to 6 weeks; after OMS launch, 5 days were required to check stock, prepare the invoice, and transfer the order to the warehouse. The solution foundation was completed in June 2025. The measurement period and sample size were not disclosed; the percentage is presented as a case-study result, without recalculation or a guarantee of system availability.
In PIM → marketplace case Updating stationery product collections was reduced from 10 days to 1, freeing up to 100 person-hours per week. The mechanism is category attribute mapping instead of manually editing each listing. The first launch was on Wildberries; the service transforms data but does not correct errors in the source catalog.
In temporary workforce management case The publication describes Pimcore integration for shared data and jBPM for processes. Tasks include invoices, claims, and KPI calculations. It confirms the solution components but provides no measured savings or evidence that manual reporting was fully eliminated.
FAQ
ERP supports accounting and resource management, CRM supports customer operations, and BPM supports workflows and approvals. Functions may overlap; responsibility for data is assigned during design.
Assign an owner, define the process start and end, and measure current delays, errors, and effort. Then choose a rule change or automation that affects the selected metric.
There is no universal size-based rule. The choice between modules on one platform and separate systems depends on functionality, existing applications, data exchanges, and maintenance costs.
Assess discovery, configuration, licenses, integrations, migration, training, infrastructure, and operations. Calculate the contingency based on risks: event, probability, impact, action, and conditions for using the funds.
Compare the verified economic benefit with the total costs over the same period. Report freed-up time separately as additional productivity or an actual reduction in expenses; by itself, it does not equal monetary savings.
Verification date: 13.09.2026