{"id":2006,"date":"2026-09-03T14:46:02","date_gmt":"2026-09-03T12:46:02","guid":{"rendered":"https:\/\/www.applicon-it.eu\/?p=2006"},"modified":"2026-09-04T10:00:20","modified_gmt":"2026-09-04T08:00:20","slug":"erp-system-integration-where-does-erp-end-and-another-system-begin","status":"publish","type":"post","link":"https:\/\/www.applicon-it.eu\/en\/erp-system-integration-where-does-erp-end-and-another-system-begin\/","title":{"rendered":"ERP Selection: 10 Areas That Need Clarification"},"content":{"rendered":"\t\t
\n\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

Is your company ready for ERP selection? 10 areas that need clarification <\/h2>\n

Selecting an ERP system does not begin by approaching vendors or comparing their presentations. First, it is necessary to clarify the reasons for the change, project goals, the scope of the future solution, and the company’s readiness for its realization. <\/p>\n

The quality of preparation affects the content of the requirements specification, the comparability of bids, the selection of the vendor, and the course of the subsequent implementation. Ambiguities in the project usually manifest as changes in scope, cost increases, schedule delays, or a solution that does not sufficiently support the company’s needs. <\/p>\n

The following ten areas represent a guideline framework for the management of companies that are preparing for ERP selection<\/a> or are just deciding on a system change. It helps identify topics that should be professionally assessed and unified before starting the tender process. <\/p>\n

1. Reason for changing the current ERP system<\/h3>\n

A company needs to determine exactly why it is considering an ERP change. A general statement that the current system is no longer suitable does not provide a sufficient basis for a decision or for the requirements of a future solution. <\/p>\n

The cause of problems may lie in system limitations, inappropriate configuration, low utilization of available functionality, data quality, or historically established business processes. Each of these situations requires a different subsequent approach. <\/p>\n

The result of the assessment may be the selection of a new ERP, expansion of the current system, process optimization, or re-implementation. Therefore, before starting the selection, it makes sense to verify whether the planned change corresponds to the actual cause of the problems. <\/p>\n

2. ERP project goals<\/h3>\n

ERP project goals should describe the specific change the company wants to achieve. This could include, for example, more accurate production planning, better inventory management, more accessible data, more reliable calculations, better reporting, or the unification of processes between individual operations. <\/p>\n

General formulations, such as increasing efficiency or company digitalization, do not provide sufficient support for system selection or for evaluating the implementation result.<\/p>\n

Goals should be converted into measurable or clearly verifiable criteria. Subsequently, they must be reflected in the requirements specification, bid evaluation, contractual terms, and the method of acceptance for the implemented solution. <\/p>\n

3. Scope of the future solution<\/h3>\n

Before approaching vendors, it is necessary to define which companies, operations, organizational units, and business processes the ERP project should include.<\/p>\n

Part of the decision is also the future role of the ERP in relation to other business applications, such as MES, APS, WMS, PLM, CRM, or BI. It must be clear which areas will be supported by the ERP and which will remain in follow-up systems. <\/p>\n

If the scope is unclearly defined, vendors may prepare bids based on different assumptions. One bid may include a comprehensive solution including integrations, while another counts only on basic functionality. Such bids are not comparable in terms of substance or price. <\/p>\n

4. Readiness of business processes<\/h3>\n

An ERP system supports a specific way of working. Therefore, before starting the selection, it is necessary to know the form of key processes, their main limitations, and the links between individual areas of the company. <\/p>\n

Historical procedures may stem from the limitations of the current ERP, local customs, or an organizational structure that no longer corresponds to current needs. Automatically transferring them to a new system would increase the complexity of the solution and could lead to further custom modifications. <\/p>\n

Process preparation helps distinguish the company’s actual needs from procedures created as a reaction to the limitations of the current system. At the same time, it creates a basis for deciding which processes should be unified, changed, or newly supported by ERP functionality. <\/p>\n

5. Data quality and availability<\/h3>\n

The state of master and transactional data significantly affects the scope, complexity, and risks of ERP implementation<\/a>. Before starting the project, it is advisable to assess, in particular, the uniformity of code lists, the existence of duplicates, the completeness of key data, and responsibilities for their management. <\/p>\n

In manufacturing companies, this may involve, for example, material items, bills of materials (BOM), technological procedures, standards, workstations, or data needed for planning and calculations.<\/p>\n

Not all data needs to be cleaned before ERP selection. However, the company needs to know its status, responsibilities for its management, and the expected scope of preparation before migration. Vendors can thus more accurately determine labor requirements, division of responsibilities, and data transfer conditions. <\/p>\n

6. Requirements for the new ERP system<\/h3>\n

ERP requirements should be based on the business and process needs of the company. A mere list of functions from the current system or individual user ideas usually does not lead to a high-quality requirements specification. <\/p>\n

Requirements should be categorized according to their importance.<\/p>\n

Critical requirements<\/h4>\n

Functionality and conditions essential for the company’s main operations. Failure to meet them may be a reason to exclude a solution from further evaluation. <\/p>\n

Requirements supporting project goals<\/h4>\n

Areas directly related to the expected benefits of the ERP project, such as more accurate planning, more accessible reporting, more efficient inventory management, or process unification.<\/p>\n

Developmental requirements<\/h4>\n

Functions and options that the company may not use during the first deployment but are important from the perspective of the long-term development of the solution.<\/p>\n

Professional assessment helps limit unnecessary custom modifications while capturing functionality that will be important for the future operation and development of the company.<\/p>\n

7. Internal project team and its capacities<\/h3>\n

ERP selection and implementation require the active participation of management, process owners, key users, and IT. Before the project starts, it is advisable to determine who will be responsible for individual areas and what capacity they can realistically dedicate to the project. <\/p>\n

The vendor brings system knowledge and implementation experience. However, decisions regarding target processes, responsibilities, data management rules, and company priorities remain with the client. <\/p>\n

Overloading key employees, unclear authorities, or limited management availability affect decision-making speed and the quality of project outputs. Therefore, the availability of the internal team must correspond to the schedule and project management method. <\/p>\n

8. Evaluation of ERP systems and vendors<\/h3>\n

An ERP system cannot be evaluated solely by the number of declared functions. What matters is the way it supports the company’s specific processes, the degree of standard functionality utilization, integration options, technological sustainability, and the ease of further development. <\/p>\n

In addition to the system, the vendor must also be assessed independently. The evaluation should particularly consider: <\/p>\n