Dr. Raul Mazo Université Paris 1 – Sorbonne, EFREI

Low level description ... Analyze & definition of management process. ▻ Tools : ... establish the technical and operational environment and. ◦ validate the ...
2MB taille 6 téléchargements 37 vues
Dr. Raul Mazo Université Paris 1 – Sorbonne, EFREI

 

10-20 % of the personnel is touched Issues : ◦ ◦ ◦ ◦ ◦

conduct of the change Adaptability to the occasional users of SAP Reduction of the transactions Dispersion of information Adequacy to the needs ERP Needs Covering

As-Wished BM

To-Be BM Fitness relationship

Might-Be SFM

Matching Process

To-Be SFM









To understand and solve the conceptual conflict between the levels (as wished – might be) To analyze the correlation between the needs for the organization and functionalities of ERP To model the relation of adequacy (fitness) of the considered solution To evaluate the relation’s quality

Approach guided by the needs of the enterprise Organisation Needs and requirements

High level expression Oriented objectif and strategy

PGI Descriptions Low level description Oriented function Local View

global View

Approach guided by the ERP

Approach guided by the needs of the enterprise Organisation Needs and requirements High level expression Oriented objectif and strategy

globalView

PGI Descriptions Low level description Oriented function Local View

Approach guided by the ERP   

Classic Wished by all the business actors of the company Allows to install a system which would meet exactly the needs of the company

Approach guided by the needs of the enterprise Organisation Needs and requirements High level expression Oriented objectif and strategy

globalView

PGI Descriptions

Low level description Oriented function Local View

Approach guided by the ERP    

Wished by the editor and the integrators Allows to install the standard functions of the ERP Simple parameter setting and configuration To avoid Re-developing particular functions to take into account specificities of the organization

       

Sponsor Piloting commit Consultants Key users Editor agents Training Conduct of the change Security

    



ASAP (SAP) Implex (Intentia) Rapide RE (Gateway Consulting) Fast Track (Deloitte & Touch) Total solution and Accelerated migration (Ernst & Young) Conclusions and perspectives



Life cycle : analyze, implementation, continous improvement. Five phases



Classical strategies:



◦ ◦ ◦ ◦ ◦

Construction (of the project) Design Realization Preparation of starting Setting in production

◦ « big bang »: All the modules required by the company are configured and implemented. Approach very time consuming, heavy on resources and cost, and very risk as well. ◦ incremental, “by batch“: Phase 1: Finance and Logistics for all divisions. Phase 2: remaining modules for all divisions. ◦ by optimization of the existing version



Initial planning of the project ◦ Planning ◦ Perimeter ◦ Organization of project team

      

Definition of project’s procedures Training of the project’s participants Meeting of Setting up Identification of technical requirements Installation of the quality control Tools : accelerators Deliverables

◦ Project’s Charter: objectives, resources, planning, budget, indicators of performance, organization and commities ◦ Conduct of the change charter



Project management, Conduct of the change & training Development of environment system Definition of enterprise's structure Analyze & definition of management process Tools :



Deliverables :

   

◦ The Business Blueprint document is the output of the Q&Adb. Tool that helps you determine the company requirements with respect to SAP business processes by using templates and business questions ◦ Diagram Explorer, LiveModeller (IntelliCorp), ERP Modeller (CASEWise) ◦ "blueprint" : document of general design. What we are doing and what we need ... ◦ Work’s documents  OSL : Organisational Structure List  BPML : Business Process Master List  DL : Development List

  

    

Project manager, Change’s behaviour& formation Initial/final Parameter settings System administration Specific development (interfaces, etc) Integration tests Quality control Tools : Implementation Guide (configure) Deliverables :

◦ Syntheses of the management’s scenarios ◦ MOT : procedure by transaction (R/3 transactions to implement) ◦ Planning of parameter setting and test ◦ Development program (detailed requirements) ◦ training support of final user

 

    

Project management and training system administration Detailed planning of the passage in production Swing Quality control Tools : Excell sheets of synthesis Deliverables : ◦ ◦ ◦ ◦

Tests Detailed plan of swing training support of final user Handbook of technical exploitation



Assistance on the productive system



End of project



Deliverables : performance report of the system in production



IMPLEX describes: ◦ ◦ ◦ ◦

Project’s organization. Project’s planification. Description of management process. Analysis of management process.

5 phases



Project’s issues Organization of the team in the project Who does what? Project planning



Deliverable



Tools

  

◦ Project definition ◦ Template and CheckList  Preset documents ◦ Project Database B.D.D. that contains the Movex old projects that can be used as reference for the new projects.



   





Analysis and definition of management process Infinity of business process Data conversion Training plan Ask for approval of all the project’s actors Deliverable – Approval of business process – Audit report Tools – Template and CheckList  Preset documents – E.R.M.(Enterprise Reference Model) Preset business process



The purpose of the configuration phase is :

◦ to tailor Movex according to process descriptions, ◦ establish the technical and operational environment and ◦ validate the business solution.



Production of document for users Definition of tests



Deliverables



Tools



◦ Approval of the Movex configuration ◦ Audit report ◦ Template and CheckList Preset documents ◦ Enterprise Process Management (E.P.M.) Process design



  

The purpose of this phase is:

◦ to construct the production database and ◦ introduce the business solution to the client user community

Piloting test Users’s formation Movex checking in accord with the work environment.



Deliverable



Tools

◦ Approval of the implementation ◦ Audit report ◦ Template and CheckList  Preset documents



The purpose of this phase is :

◦ to place the new business solution in operation, ◦ ensure the transition to the new environment and ◦ plan future improvement activities.



On line assistance Possible evolution of the application



Deliverable



◦ Functional application 

Tools ◦ Template and CheckList