Script Erp Implementation
Script Erp Implementation
My name is Jennifer Nicholson. I am a professional accountant and have had a successful career
as a CFO and senior executive in various industries including mining, shipping and utilities. I
have also taught business students many different courses for almost 20 years. Today we are
going to talk about how to choose an ERP system for your organization – what the CFO and
project manager need to know. I recently chose and implemented a new ERP system in a large
private company where I was the CFO so I have firsthand experience with this process.
Slide 2
The
The
process? cost? Which
vendor?
Cloud or
on-
premise?
I had
questions
When I started looking for a new system I had a lot of questions about how the process would
work, how much it would cost, who to hire, and what systems were appropriate for my
company. It was difficult to find information that wasn’t sponsored by and therefore biased
towards a specific vendor. This course is based on my experience with this project and I hope it
will help you with your project.
Slide 3
Course preview
1. Defining ERP
requirements
2. Different
deployment models
3. Initiating an ERP
implementation
4. Getting vendors and
people aligned
5. Data cleansing
6. Testing and training
In this course we will talk about what an ERP system is, what it is, benefits of a cloud vs. on
premise platform, and the various steps covering all the relevant and practical considerations
you’ll find your self confronted. Everything from initiating your project, to selecting a vendor
and getting a team in place, to the hands on matters of data cleansing and [testing and training].
If you are in the process of changing your systems or contemplating a change in your systems,
then this is the course for you. I’m excited to share my knowledge and experience with you.
Slide 4
Emergency Elementary
Response Reporting
Plan ? Project ?
First of all – what the heck is an ERP system? I’m sure you have all heard the lingo – especially
since you are taking this course – but do you really know what that is?
Slide 5
ERP is short for Enterprise Resource Planning. It is typically software that consists of a group of
integrated business management programs that an organization can use to help run its
business. This type of system can collect, organize, store, process and interpret and report all
kinds of data and can be customized to meet your specific business needs. Does your business
need an ERP system?
Slide 6
Well, all businesses are comprised of many different processes and you are likely operating a
number of independent systems at this time. The benefit of an integrated ERP system is that
everything flows together. It reduces manual entry and the risk of errors that come with it.
Enter a transaction once – or better yet have the computer enter it - and this transaction will
flow through to A/R, A/P, sales, costs, inventory etc etc. These systems also have tons of
potential for data analysis which enables you to manage your business better.
Do you really need it though? That depends on a lot of factors which we will talk about today.
There are endless options that run the gamut from relatively simple and inexpensive to very
complicated and costly. Many factors will determine what type of system makes the most sense
for your organization.
Slide 7
ERP Modules
Financial
Accounting
Module
Financial Accounting is a core module any ERP system. An ERP system will automate and
integrate your financial processes and result in error free transaction processing. This was an
earth shattering transformation for my previous organization where we had been operating
with an accounting system from the 1990s - prehistoric days in today’s fast changing
environment.
This is often the catalyst for implementation of an ERP system and a natural first phase of your
process. Start with the accounting system and add on in stages.
Slide 8
ERP Modules
Financial Management
Accounting Accounting
Management Accounting – An ERP system can help with your budgeting process by having each
department head prepare his or her own budget and then consolidating for the entire company.
Progress against budget can then easily be tracked and results can be manipulated to look at
information in numerous different ways. Activity based costing can also be used and
monitored.
Slide 9
ERP Modules
Financial Management Human
Accounting Accounting Resources
Human Resources – The ERP system can be used to control many HR functions including time
and attendance and vacation tracking, payroll processing and calculating remittances. My
previous organization had significant training requirements for employees due to the dangerous
nature of the work. Our ERP system was able to track training by employee and flag areas of
concern.
Slide 10
ERP Modules
Financial Management Human
Accounting Accounting Resources
Manufacturing
Manufacturing – An ERP system can manage and monitor all stages of a manufacturing process
including engineering, scheduling, capacity, workflow management, just in time production etc.
and feed this information into the management accounting model to determine costing.
Slide 11
ERP Modules
Financial Management Human
Accounting Accounting Resources
Order
Manufacturing
Processing
Order Processing – Today’s ERP system can do everything from order entry, credit checking,
inventory control, shipping, sales analysis and reporting and sales commissioning. This
information can be linked to the manufacturing, supply chain and accounting modules to ensure
you have the inventory required when it is required and that sales are appropriately recorded.
Thorough data analysis is available to monitor sales trends to determine where adjustments are
required throughout the supply chain.
Slide 12
ERP Modules
Financial Management Human
Accounting Accounting Resources
ERP Modules
Financial Management Human
Accounting Accounting Resources
Project
Management
Project Management - project costing, resource planning, billing, time and expense
management can all be tracked through your ERP system.
Slide 14
ERP Modules
Financial Management Human
Accounting Accounting Resources
Customer Other
Project
Relationship Modules
Management
Management …
Customer Relationship Management – most ERP systems offer CRM modules or can be easily
interfaced with popular off the shelf software such as Salesforce. CRM systems allow you to
track all customer interactions in real time, record results of meetings, schedule follow up etc.
Thank you for joining me – in the next lesson we will talk about what type of systems are
available.
Slide 15
Cloud ? On-premise ?
Cloud
Deployment
On-Premise
Deployment
Your
Company
On-premise solutions are those that you physically install on your servers and that you maintain
and support with in-house IT staff.
Cloud solutions are hosted by the vendor’s server and managed by their employees. Your
company then subscribes to this service and accesses it on-line.
There are significant long-term differences between these options so the decision can’t be
made lightly.
Slide 17
Cloud
Deployment
On-Premise
Deployment
Your
Hardware,
Company
Physical space
IT staff
Ownership Costs
There are significant upfront costs with an on premise ERP implementation. The hardware
must be purchased, you must ensure you have sufficient fire-proof, secure, well-ventilated
space to store the hardware and IT staff must be hired and trained to manage the hardware and
software. On an on-going basis, staff must be on-site to ensure the system is always running,
that the maintenance is maintained and that upgrades are completed as required.
In contrast, with a cloud system, the hardware is stored and maintained at the vendor’s site.
The vendor should have a sophisticated support department that can remotely trouble shoot
and deal with any issues.
Many executives are suspicious of cloud solutions as they worry about security of their data and
like the idea of having the bricks and mortar of their priceless data on site. Cloud solutions have
evolved a lot over the last decade and have a lot of benefits. The ownership costs for a cloud
based deployment include some sort of subscription or all-in licensing cost.
With either platform there needs to be significant upfront planning and development.
Slide 18
Cloud solutions are developed by some of the best software engineers in the industry and
updates are pushed out on a regular basis so you should always have the most current version.
Security is likely to be best in class as well as cloud ERP vendors take the security of their client’s
data very seriously. Disaster recovery and back up procedures should be well defined and
sophisticated.
Understanding the deployment models upfront helps to envision how the new ERP will be
implemented and run on a day to day basis. In our next lesson, we will talk about ways we
should initiate our project.
Slide 19
This approach is usually better and costs less than hiring an external consultant to manage the
project. Using a mid-level employee that knows where all the skeletons are hidden will likely
yield a better result at a lower cost than an uninitiated consultant at an hourly rate.
Slide 22
It should not require an enormous effort to achieve and maintain leadership commitment but
as we all know executives like to get their way and it can be hard to achieve consensus on the
must haves versus the nice to have features and modules. Everyone’s area of responsibility
becomes the most important. Strong leadership and project management are crucial to keep
the project from going out of control. The fact that there is an ERP project means that there
was sufficient interest and commitment to fund the strategically important initiative in the first
place so hopefully the needed support is there.
Slide 23
1. Communicate!
2. BIG picture view
3. Get feedback & change
• Try to be the first to communicate process change decisions. This is not always easy;
especially if you are on routine monthly or bi-weekly review cycles. Make use of emails
during the intervals. The critical point is to make certain that decisions are explained in
terms of sound business judgment. If your explanation is not compelling, it may not be a
good decision.
• Try to always present executives with a bigger picture narrative when possible. To the extent
that you can arrange numerous tactical ERP decisions into a strategic picture with
implications, you will engage executives in their comfort zone.
• Solicit executive feedback and do not be defensive if you receive it. Your goal is to remain
tightly aligned with the executive leadership, and that will only happen if they are confident
that you can listen to and respond to their concerns. Also, this keeps them involved in
decision-making; you want them to think of these as “our decisions” not “your decisions”. If
your executive leadership remains steadfastly committed, everyone else will follow along.
This in turn, allows you to focus your time on more productive tasks. Keep your leadership
group aligned around and enthused about the project, and your probability of success goes
up significantly.
With the right project management and the executives on board, we are now ready to start
talking to vendors.
Slide 24
At this point, I’m going to assume that your business has already developed a robust
understanding of its needs. This assessment will vary considerably between organizations. You
need to consider not only your existing business model, but other possible changes in the
future. For example, if you are acquiring other businesses, how will these new businesses be
integrated to the new ERP. The business needs analysis is very important to hammer out prior
to talking with vendors.
Slide 25
A good fit for your industry and business ensures a relatively smooth transition from old to new.
Solutions which are efficient and intuitive speed up the learning process, foster the sense of ERP
being an improvement, and contribute to organizational confidence.
Slide 26
VENDOR
Determining the fit of the software product for your business is the more important decision,
but should also be the most objective. Using an off the shelf product with minimal
customization is usually the best idea as most of the bugs have already been fixed. Your vendor
should be able to put users in front of you from your industry who make you feel positive about
the strengths of the product. You may not find exact industry overlap but process similarity is
really the most important thing.
Slide 27
I can’t stress how important verifiable references are here. You need to talk to people who have
implemented the same system – with the same staff members – to ensure that this really is the
right system for you. And ensure some of those people have used the system over time and
that all the bugs have been worked out.
Construct a basic numerical scorecard around the critical features/deliverables you need, and
use it –and trust it - when comparing products. This will help you defend your choices to your
executive and Board as this is an objective measure of what is appropriate. Be careful when
someone with no particular track record in your industry tries to buy market entry with a
noticeably low asking price, and remember that there is no amount of money in your company
sufficient to fix a bad ERP solution. Pick a vendor who you judge will survive for the long term,
and supports on-going development for your business.
Slide 28
Pre-sales!
Create a Vendor Evaluation Scorecard
Bear in mind that there are going to be two very distinct phases to your relationship with your
ERP software vendor.
• During the sales cycle, you will be the most important person in the world. There will be no
request too large, and no question too small that does not elicit an almost obsequious
response.
Slide 29
Post-sales!
After the sale, though, the actual business relationship begins, and that is the relationship that
you must do your best to gauge. You should feel positive about your vendors; that they are
ethical, honest, and would never intentionally mislead you. You should feel like they consider
your wellbeing important, and that you will be able to work together through unexpected
problems.
Selecting an ERP vendor is a big, strategically important decision. Involve as many peers and
viewpoints as you can possibly manage. Feel good about being able to articulate the reasoning
for your choice, numerically if possible. Don’t expose yourself to risks without commensurate
rewards. Picking the right software vendor is a huge step toward to ERP success.
Slide 30
• Supervise the
I’m an experienced
implementation ERP consultant
• Do the
implementation
Depending on the size and scope of your ERP implementation, you may also want to use an
independent consultant to help during your implementation. Not every ERP project requires a
full time consultant team. Whether or not you need consultants depends on how much in-
house knowledge you have about your ERP software (and to what extent that software can be
self-taught); how much time you have to complete the project; and how many modules and end
users you are trying to implement at one time.
At this point, you’ve got your external resources aligned. In the next lesson, we will begin
discussion how we align our internal team for the ERP implementation.
Slide 31
Change Management
Overcoming this reaction…
But what exactly is Change Management? How do you ensure people are ready for a project
and system that is potentially going to consume a significant amount of their work time over the
next six months at a minimum and then once implemented will change the way they work.
That’s when we realize we don’t really have a clue about what change management is or how to
accomplish it. The good news – and most critical thing to remember – is that the way people
come to believe things and form opinions is both consistent and predictable. By managing to
those predictabilities in terms of timing and content, the normal discomfort associated with
change on the scale of an ERP project can be reduced to manageable levels.
Slide 33
There is no question that on one level, ERP is a technical project, requiring intelligent design,
seamless logic, and sophisticated math. But no matter how robust the solution, ERP will only be
successful if people embrace it and use it as designed. That behavior will not occur without
change management effort.
Slide 34
A talented implementation team sees the big picture more completely, appreciates the
implications of the strategic plan better, evaluates decisions not only in terms of what is today,
but what is likely to become tomorrow, and has the professional capital and organizational
respect to sell difficult, but necessary process changes. So what are some of the indicators of
good talent when evaluating individuals for implementation team participation?
Slide 35
1. Promotable
2. High Team
Intelligence
3. Depth of
Understanding
4. Good listener & Who do you need?
adaptable
Who do you want?
-Secondly, an individual who has high personal intelligence is nice, but an individual who has
high team intelligence is a necessity. Being personally smart has nothing to do with – and can
occasionally interfere with – being team smart. Being team smart means you recognize the
point of consensus, and do not belabor a conversation beyond that point; it means that you do
not steer conversations in interesting, but unimportant directions; it means that the quality of a
decision is evaluated solely on its effect to the organization; it means that whatever personal
ego you have is left at home where you can conveniently pick it up after work.
-A third attribute is depth of understanding. Talented people not only understand “what” is
required, they understand “why” it is required, and this comprehension is incredibly valuable
when it comes to determining what business practices are subject to change and which are not.
-And finally, the most intangible, is the ability to listen to multiple points of view, and assimilate
the best parts of all into a solution that is better than any. If you assemble a strong team,
everything about the project goes better. Change management is more effective because the
team members have credibility. Testing goes better because the test scenarios are chosen
wisely, and executed intelligently. Fewer milestones are missed, as team members are used to
accepting additional responsibility, and pitch in to help wherever needed. There are many
factors that influence the success of an ERP implementation, and team talent is one of the
biggest. A highly talented team alone does not ensure that your implementation will be world-
class, but mediocre talent alone will ensure that you have a mediocre implementation.
In our next lesson, we are going to start talking about the work that needs to be done.
Slide 36
What is “data cleansing?” you ask. It is the tedious process of finding and correcting errors in
your data to ensure each item is only included once and is correct. Different users can enter the
same piece of information several different ways. This then results in the same customer, part,
vendor etc. being recorded numerous times and makes it hard to find the correct data when
searching.
Master data completeness and accuracy is crucial to ERP implementation success. Many people
vastly underestimate the scope and complexity of data cleansing.
Let’s talk about why data cleansing is important to ERP success, and some tips to improve your
approach. Data cleansing is a huge factor in ERP success because it is leveraged in every phase
of the operation.
- An ERP implementation will be exactly as successful as its testing execution, and the only
limitation on testing execution is master data completeness and accuracy.
- An ERP implementation will be exactly as successful as its training program, and effective ERP
training requires master data completeness and accuracy.
- An ERP implementation will be exactly as successful as its synchronization of business data at
go-live, and that synchronization requires master data completeness and accuracy.
Every success that occurs has complete and accurate master data as a prerequisite.
Slide 38
Challenges Approach
• Multiple system, • Make progress where
data dispersion you can
Address Field • Iterative process • Schedule routine review
South Main St. • Hard to measure meetings
progress • Establish an aggressive
South Main Street completion plan
S. Main Street • Assign the right people
to the task
S. Main St.
But to be forewarned is to be forearmed, so with this knowledge, there are lots of steps you can
take to improve the data cleansing process:
• Make progress where you can. Some data will take time to accumulate, but in the
meantime, you can recognize that you have addresses on “South Main Street”, “South Main
St.” and “S. Main Street” and “S. Main St.” and work on fixing those. Look for zip code and
city mismatches.
• Schedule routine data cleansing review meetings, and be relentless about probing for
bottlenecks and problem areas
• Establish an aggressive completion plan – which you probably will not hit – but invest the
time to understand exactly why you are not hitting it.
• Assign the right people to the task. Smart, hard-working, detail-oriented people – match
the right skills with the job need.
Unlike most of an ERP implementation, the lessons learned, and the processes created for data
cleansing become part of an organization’s DNA; complete and accurate master data will be as
essential for success two years after go live as it is on day 1. Make it part of your ERP success
story. In our next lesson we will talk about testing.
Slide 39
Testing,Testing… 1, 2, 3…
Is this thing on?
Testing requires more than just assigning manpower. It is an iterative process, which means not
only testing, but evaluating problems, and fixing things. It means having valid master data
available to support the test, and understanding the process you are testing. It means testing
development objects, and how they interact with everything else. It means having a dedicated
test client, which can be controlled and monitored. Each test leads to a bigger test, so there is a
natural progression of testing sophistication over the course of an implementation.
Slide 41
Integration Testing
User Testing
Rehearsal Testing
“Integration testing” in this case, means testing an entire business process, from initial input to
final output. An integration test is a scripted arrangement of the ten to sixty sequential
transactions required to execute a specific process in the real world. The key to making this
phase successful is to identify the right fifteen to thirty scripts that represent 90% of the
business processes, and working hard on process improvements until they all execute smoothly.
The next round of integration tests involves subject matter experts and super users. During this
round of tests, random but real world data is introduced. The randomness ensures that the right
processes were identified in integration test one; using real world data allows business
participants to help evaluate the output. During this round of testing, master data must be well
developed, because the ability to enter real orders with real customers means that master data
is available to feed the process.
Subsequent rounds of integration tests try to rehearse and execute a go-live, including
synchronization of inventory, sales orders, purchase orders and production orders, and
replicating one hundred percent of the activity of a business for a given time period. Every test
cycle teaches, uncovers problems, and makes go-live more manageable. Eventually, an inflection
point occurs during testing which is incredibly important for a team’s morale and attitude; it is
the realization that the team is certain of a successful go-live. That knowledge and confidence –
which can only come from repeated and successful testing - is essential to an implementation’s
success.
The next step is to set up user training, which I’ll describe in the next lesson.
Slide 42
The second tier of end user training success is to have some end users sufficiently trained so
that they can participate effectively in volume testing leading up to go live. These people
contribute beyond their task participation because they bring real world eyes to problems to
which the implementation team may have grown blind. They recognize what areas of training
are going to be especially problematic. Also, they can look at system output and in a glance spot
common sense errors that a team unfamiliar with the day-today data might overlook.
Slide 44
The best way to increase the number of problem solvers is to identify individuals during training
who either show unusually quick comprehension of the material, or unusual curiosity, and to
give those people additional training and mentoring. All of these levels require a consistent and
logical education process. Everyone in the organization who will touch ERP must be identified by
name and job function. Every transaction required for that function must be identified, and
assembled into an appropriate security role.
Training material must be prepared, and sufficient practice problems set up so that everyone
can engage in hands-on practice. Different types of transactions require different amounts of
preparation and master data. With five valid customers and five valid materials, you can create
dozens of different sales orders, but you can’t report production unless you have a work order
and sufficient inventory of all components.
Instructors must be enthusiastic, knowledgeable, and patient. Training must be timed shortly
before implementation, or else retention goes down dramatically. Getting the maximum
number of people competently trained in ERP for go live is an incredible boost for success. The
need to conduct training occurs during the exact same time frame that anxiety about go-live is
peaking. Keep everyone focused on the prize; training is a key success factor.
Plan the project, plan the testing and plan the training and implementation. Make sure you
estimate your spending over time and budget accordingly. Spending all of your budget in the
first few months may be a career limiting move and the meeting to request additional funding
from your steering committee may be horribly painful for you. Make sure you budget for what
you think it is going to cost, add a generous contingency on top of that and then increase it even
more. Get approval for the high number up front and you will come out a superstar when you
complete the project significantly under budget.
Monthly spending is overwhelmingly a function of people, and the easiest way to make
adjustments is to reduce consultants and add highly talented people from within your
organization. Generally speaking, you will be able to pay two or three internal people for every
consultant you can do without. Lastly, use that final twenty-five percent surplus budget in the
last six weeks before go-live and first six weeks after.
There will be unexpected problems, and that is when you need the flexibility to spend money
aggressively, and wisely, in order to quell rumors, and find speedy resolutions to emotional
problems. Once people recognize that problems are being corrected quickly confidence soars,
and the probability of success takes a huge jump up.
No one wants to spend any more than they have to on an ERP implementation, but its better to
have an ERP cost a little more and be successful, than to have a cheap ERP implementation that
fails.
In the final lesson, we will look at advice for maximizing your successful ERP implementation.
Slide 47
Think achievable!
Course Wrap Up
In this final lesson, let’s review a few key takeaways from this course as you embark on your ERP
journey:
First, if you take nothing else from this course, believe that these success steps are real and
necessary. Underestimating the difficulty of an ERP implementation is a big mistake. Find people
who have been down a road like ERP before, and whose opinions you trust – IT professionals,
consulting partners, software vendors, other project managers – and ask them if the items on
this list are critical for your project success.
Second, stay intimidated every single day of your implementation project. Do not be paralyzed
with fear; just remain respectful of the multitude of ways in which your project can derail, and
use that respect to motivate the effort to make sure it doesn’t.
Third, learn early on who you can trust without reservation to help you with these steps, and
lean on these people heavily. By now, you recognize that these success steps are much more of
a philosophical anchor than task items than can be crossed off a “to do” list.
Fourth, you need to make sure everyone can see you staying involved in the change
management, data cleansing, and business process change efforts. The paradox you face is that
even though you have no training or previous experience – really no qualifications at all –
people expect that you will have a successful implementation. The only logical way out of this
paradox is for you to assimilate as quickly as possible the cumulative knowledge of the many
who have also done what you are doing, and by doing so, begin building your qualifications.
Because an ERP implementation is difficult does not mean it cannot be both fun and create an
enormous sense of accomplishment and satisfaction.
Thank you for your time and interest in this topic. My name is Jennifer Nicholson. Please feel
free to reach out to me if you have any further questions on this topic.