04/13/23 1

ERP Implementation ProgramERP Implementation Program

For the exclusive use ofPreci Manufacturing

04/13/232

1.Business Review

2.System Selection

3.Project Planning

4.Installation, Upgrade and Data Conversion

5.Training and Education

6.Business Process Engineering and Best Practices

7.Conference Room Pilot Testing

8.Go-Live!  

9.Post Implementation Review and Continuous Improvement

9 Steps to an ERP Implementation

04/13/233

• Define your requirements and how they currently perform their duties.

• Identify and document current processes in detail.

•Identify areas for improvement and map efficient processes to the software.

o This step also provides an understanding of your business environment and helps us speak your language.

Business Review

04/13/234

• Define required critical system functionality

•Identify universe of potential solutions

•Define customer visit demo plan

•Quantify assessments

•Select product

System Selection

04/13/235

•Create the roadmap that is used through the implementation.

•Identify the discrete tasks, responsibilities and timelines for your project developing a customized Implementation Plan.

•Provide bi-weekly progress reports that identify completed, outstanding and late tasks along with other relevant project information.

•Implementation tasks are covered in detail in the project plan. They will include:

• Establish proper system policies for maintaining and backing-up data • Convert data from your existing system• Setup and configure each module • Executing tasks per the Implementation Plan in conjunction with the Project Team.• Answer questions/Troubleshoot problems• Assist in the creation of required custom reports• Documentation of procedures• System testing• Verify opening balances match the existing system closing balances

Project Planning

04/13/236

•We will install your systems and work with you to convert your existing data

Installation and Data Conversion

04/13/237

Project Team Training: •Provide the assigned project lead(s) and project team members top-level training on the entire system to provide an overview of the modules and how they are set up.

Training includes:· How to customize the setup of modules to fit your business.· How to setup key records, such as items using the Item Class.· Discussions on critical issues that affect your company’s use of the new system.

End-User Classroom Training:•Detailed user training to include topics on system use like:

· How to enter transactions, and different ways they can be entered and posted.· How to maintain the data that is accumulating in your system.· Using inquiries/reports to obtain the information you wish to access.· How to complete period and year-end procedures in each module.

Training and Education

04/13/238

•Document all of company business processes in detail, then review and re-engineer to get the best results in using the new business system.

•Done by the project team with input from the current system users. These processes are then reviewed, updated, and mapped to the new business system by the project team and the MRP implementation consultant.

•The team members are responsible for the actual process documentation to reinforce their understanding of the processes. The updated processes form the foundation for the implementation and will become guidelines and work instructions for the end users.

•The benefits gained by the company from this phase of the implementation include: o Streamlined processes for more efficient workers.o Elimination of wasteful non-value added activities.o Work instructions for new users as new employees come into your company.o A more thorough understanding of the complete workings of your business.

 

Business Process Engineering and Best Practices

04/13/239

Guided Pilot Testing

•After the system is initially configured, perform the initial pilot test with your team.

•The pilot test is based on the processes developed during the business process engineering, and it serves two functions: oTest the setup of the system.oProve the validity of the re-engineered processes and work instructions.oProvide additional training for team members by simulating their normal day-to-day activities.

•Perform all of the transactions that users would perform daily using the re-engineered processes.

o These transactions will be performed by the appropriate team member reinforcing the classroom training performed previously.

•The pilot testing is normally performed about one month before the go-live date.

Conference Room Pilot Testing

04/13/2310

Unguided Pilot Testing

• Continuation of the pilot testing for a period of 2-4 weeks until the go-live date.

• Bring groups of users into the training room and work through a series of transactions and then follow up the next day with a different group using the same data. o This simulates the interaction that will be required among different

departments after going live.

Conference Room Pilot Testing

04/13/2311

• During the go-live period we will be onsite to ensure that all requirements have been covered to ensure a smooth transition onto the new business system.

• At this time all tasks on the project plan have been complete, all users trained, all processes re-engineered, and the final data migration/conversion is performed.

Go-Live!

04/13/2312

•30-60 days following go live, we return to review the results as compared to the goals of the project.

•A plan for on-going improvement will be discussed and project planning for additional phases of your implementation may be scheduled.

Post Implementation Review and Continuous Improvement