3.2.3.2.3. Training
Implementations of the various entities engage team manager to
prepare a shared guidance for local project team and especially for users.
3.2.3.2.4. Anticipate Actions
After solving opened questions during previous phases, several
actions can be launched from the middle of this phase to prepare the
deployment;
.. Inventory of local technical infrastructure; .. Identification
of local and central resources .. Identification of training means
3.2.3.3. Upgrading existing repositories
This subject is often critical in the middle of the
implementation phase when it wasn't allowed. Indeed at this stage project team
addressed a new framework, specifications of recovery programs and take actions
to upgrade existing files.
Harmonization of files is primarily the harmonization of
different codifications, cleansing data and their impacts in terms of
particular statistical treatment.
3.2.4. Integration phase
In this phase the key for success is monitoring carefully
coherence between ERP System interfaces and external systems.
Key activities:
3.2.4.1. Prepare toggle plan
During this step, project team, list all steps which conduct
changes between old and new systems.
These steps include rocking action preparation and it may start
several months earlier. Actions are relating to:
- Clean up data such as customer-supplier, articles, charts of
accounts, additional manuals before restart and additional manual after
recovery.
- Correlation tables used by conversion program
- Production environments which are performed by the new system.
Upgrade library of references, tables or specific data.
- Control static balance between old and new systems
- After data migration controls are necessary to validate
information related to current inventory, customer, supplier, balance and
production orders.
For all of these spots a schedule of responsibilities and roles
must be established.
To create this plan; team project need to use information from
testing data and from integration phase.
3.2.4.2. Validate integration
This step is essential; it is a part of testing process that
has been made in previous phases. At this stage it becomes possible to validate
integration as various components are completed.
- Contribution:
- This validation don't focus on setting up the ERP, but they
focus on the ERP
specific programs and interface between different programs, so
it's a validation of all components to the new information systems.
- Integrator execute much strong test sets on the real data, and
relevance of tests are encountered in reality.
- Tests must be done mainly by users and not only by
representatives of users as
it could be done in the previous phase.
It takes place in a real environment to test prototype and
functional tools. It is faced to the interaction between correcting and
testing.
In validation process this step is a key for functional and
technical success. Indeed,
behind project team, technical resources bring
position to exploit different interface.
Which allow them to review their operating procedures and
validate different aspects of technical performance.
- Honing means operating in real conditions.
This step allows execution to check with a final operating
platform and run in the landscape management system. This point is related to
transfers management between different development environments.
During this phase of integration that is revealed the risk of
technical structure. Indeed tests performed in a configuration close to the
operational reality. So this phase proved the performance often associated with
necessary adjustments between ERP and database manager used.
| 
