Infor LN Implementation
Infor LN Migration
About us
Contact
What is the Elaboration Phase?
During the Elaboration Phase, the Infor migration takes on concrete business and technical form. Based on the framework defined in the Inception Phase, processes are analyzed, the target state is refined, and requirements are structured in a way that enables a robust implementation.
It is precisely at this stage in projects that the true viability of the eventual implementation becomes apparent. This is because this phase reveals where the Infor standard is a good fit, where established workflows need to be reevaluated, and where integrations, data, or organizational changes must be carefully worked out.
Why is the elaboration phase so important?
The Elaboration Phase lays the foundation for configuration, development, data migration, and testing. The more clearly processes, system boundaries, and data requirements are defined here, the more smoothly the Construction Phase will proceed.
From a project perspective, this is the moment when initial assumptions are transformed into sound decisions. Particularly in established manufacturing companies, this phase often reveals that processes are implemented differently depending on the department, that additional Excel or siloed solutions play a significant role behind the scenes, or that interfaces have a much greater impact on the target state than initially assumed.
What issues are addressed during the elaboration phase?
Target Processes and Target State
The first step involves analyzing existing workflows and comparing them to the potential target process in Infor. The key question is how the process can be meaningfully mapped in the target system and where standardization is feasible from both a business and organizational perspective.
This is particularly relevant in discrete manufacturing, because many processes have adapted over the years to special cases, customer requirements, or evolving responsibilities. In the elaboration phase, a target model is developed based on this analysis that is robust both in terms of processes and system architecture.
Fit-Gap Analysis
A key component of this phase is the fit-gap analysis. It identifies which requirements are covered by standard functions, where genuine gaps exist, and which issues should be addressed through organizational adjustments, integrations, or enhancements.
Based on project experience, this assessment is particularly important because not every deviation from the current process automatically constitutes a system gap. At the same time, there are requirements that are business-critical for certain manufacturing scenarios and must therefore be specifically addressed.
Integrations and System Limits
Infor LN is part of a larger system landscape in many projects. For this reason, the elaboration phase also involves determining which existing systems will remain connected, which functions will be mapped in Infor in the future, and where bidirectional interfaces are required.
Typical questions include:
- Which systems will remain the leading ones?
- What data is maintained, and where?
- What information must be available in real time?
- Where is a periodic data transfer sufficient?
This phase, particularly when it comes to PLM, CRM, or MES integrations, highlights just how closely process design and integration architecture are linked.
Data Migration and Data Quality
The data strategy is also finalized during this phase. This involves not only determining which data will be imported, but also identifying its sources, understanding its structure, and determining whether it needs to be cleaned or transformed prior to migration.
This applies, for example, to:
- Master data from the legacy system
- Additional master data from third-party systems
- Transaction data
- Location-based data structures
- Test and simulation migrations
In projects, it often becomes clear at this point that new target processes also entail new requirements for data structure and data maintenance.
Organizational Implications
New target processes often also change responsibilities within the company. This applies, for example, to process steps that will be handled by a different department in the future, the elimination of manual intermediate steps, or new escalation and approval workflows.
Especially in larger organizations, this point should be considered early on, because business decisions made during the elaboration phase often have implications for roles, responsibilities, and change management.
How can a robust solution design be developed during this phase?
A viable solution design emerges when processes, data, integrations, and organizational implications are considered together. This is precisely the core of the Elaboration Phase.
The result is a business and solution blueprint that has been agreed upon with the customer and clearly describes:
Technical and Solution Diagram
- how the ERP system should be set up
- which requirements are covered by the standard system
- where gaps need to be addressed
- which interfaces are required
- how the data migration will be prepared
This coordination is crucial, especially for the subsequent project phases. It minimizes room for interpretation and establishes a solid foundation for implementation.
What are some typical challenges that arise during this phase?
During the elaboration phase, many issues become concrete enough for the first time to be evaluated reliably. This is precisely why, from a technical standpoint, it is often the most intensive phase of the project.
Typical challenges include:
01 | Processes have evolved over time and are not uniformly documented |
02 | Different departments have varying views on standardization |
03 | At first, integrations seem easier than they actually are |
04 | Data structures do not readily fit the target model |
05 | Organizational impacts are initially underestimated |
These issues are not exceptional cases, but rather typical topics in migration projects. It is crucial to bring them to light and make them actionable at this stage.
What results must the elaboration phase produce?
At the end of the Elaboration Phase, a coordinated technical concept should be in place to serve as the basis for the Construction Phase. This typically includes:
What the final result should be
|
|
What happens after the elaboration phase?
Elaboration
- Target Vision
- Processes
- Integrations
- Data Strategy
Construction
- Configuration
- Developments
- Interfaces
- Test Preparation
Once the target vision, processes, integrations, and data strategy have been finalized, implementation begins. During the construction phase, configuration, development, interfaces, and test preparations are carried out based on the concept that has been developed.
FAQs About the Elaboration Phase
The Elaboration Phase defines the business and technical objectives of the Infor migration. During this phase, target processes, a fit-gap analysis, integrations, and a data strategy are developed in such a way that implementation can begin in a structured manner.
The Inception Phase establishes the project framework: objectives, scope, organization, and governance. Building on this foundation, the Elaboration Phase defines how processes will be mapped in the target system, what requirements exist, and how data and interfaces will be addressed.
In the fit-gap analysis, existing requirements and processes are compared with the Infor standard. This involves assessing what is already covered by standard functions, where functional gaps exist, and which issues should be addressed through organizational adjustments, integrations, or enhancements.
In addition to Infor LN or CloudSuite, related systems are typically also considered, such as PLM, CRM, MES, DMS, or other subsystems. The key factors are which systems will remain in place, which functions will be mapped within Infor in the future, and where interfaces are required.
We will be happy to present solutions for your industry and your processes. Talk to the specialists for SMEs.
request now
