882019 Blogmintekcom Part III Why Asset Management System Software Implementations Fail

httpslidepdfcomreaderfullblogmintekcom-part-iii-why-asset-management-system-software-implementations 12

P r i n t e d w i t h

j o l i p r i n t

blogmintekcom

Part III-Why Asset Management SystemSoftware Implementations Fail

Part III-Why Asset Management System

Software Implementations Fail

The nal of three posts highlighting the causes

of failed asset management system software implementations and what can be done to

increase the chances for success The rst post sug-

gested that not setting proper customer expectationsbefore an implementation begins is the root causeof failure The second post looked at some of thecritical points where expectations should be clearlylaid out You can read the rst two post here

Do You Need Outside Consultants

This part of the series looks at making a determina-

tion if the customer or vendor needs outside help(consultants) The key question for customers andvendors is Do we have the resources needed toaccomplish our objectives As a starting point toanswer the question above both customers andvendors can ask themselves 5 questions

1 What is the timetable for the implementa-

tion 6 months 1 year 2 years2 How many people will be required to exe-

cute the plan3 What is the knowledge level of the existing

staff4 What is the availability of the desired staff

during the course of the implementation5 Do you have a change management leader

who fully understands the organizationrsquoswork ow

If the answers to the preceding questions indicatethat there are not enough resources in-house to dothe project then a 3rd party possessing the neededresources might need to be approached Like thecustomer-vendor negotiations 3rd party help shouldhave clearly dened expectations and roles

Other 3rd Party Asset Management

Implementation Factors

The use of a 3rd party can be very benecial but alsocomes with inherent risks On the plus side the rightconsultant or consulting group can bring tried andtested procedures for making the implementationwork This helps customers avoid recreating thewheel when they run into an obstacle In additionan experienced implementation team or consultantcan anticipate problems and then make use of theirexperience to nd solutions that might otherwisedelay implementation

On the other hand the more implementation that isoutsourced the lesser amount of buy-in within thecustomer ranks will occur Customers must avoidthe scenario where end users feel that the new asset management system has been forced upon them orDragons will begin to emerge Other factors to beconsidered include the cost of consultants as wellas management control issues

15102010 2110

Page 1

httpblogmintekcomEnterprise_Asset_Managementbid52299Part-III-Why-Asset-Management-System-Software-Implementations-

C l i c k

h e r e

t o

s e n

d

y o u r f e e d b a c k

882019 Blogmintekcom Part III Why Asset Management System Software Implementations Fail

httpslidepdfcomreaderfullblogmintekcom-part-iii-why-asset-management-system-software-implementations 22

P r i n t e d w i t h

j o l i p r i n t

blogmintekcom

Part III-Why Asset Management System Software Implementations Fail

Implementations Are All AboutCommunication

To recap what has been discussed in the three postsso far

bull The failure to set realistic expectations onthe part of both the customer and vendorcan and probably will doom an implemen-

tationbull Implementing an asset management system

constitutes a major change in operations fora customer Buy-in from all levels is neces-

sarybull There are multiple points of failure during

the course of implementation How youhandle issues is often more important thatthe actual problem itself

bull When setting expectations remember thattraining has a huge impact on EAM adop-

tion ratesbull Beware of Dragonsbull If using an 3rd party to help with implemen-

tation make sure their involvement does notinhibit buy-in from customer staff

bull If the customer is unhappy with the endresult then the implementation was not asuccess This may go against conventionalthought that if the software system worksthe then the implementation was a successBut I disagree a successful implementationgoes beyond working functionality as anunhappy customer means no referrals badword of mouth very little chance they willrepeat (return) as a customer or in the caseof Marin County a lawsuit

Successful implementations leave the customerhappy with the value of what they paid for Vendorswanting to grow should not plan to meet customerexpectations they should be planning to exceedthem The customer is King exceeding customerexpectations makes it a lot easier to keep customers

and sell new ones

Tell how you dene a successful implementationIf you liked this article you may also enjoy reading

Register for your chance to

win a Free EAM amp CMMS Worth

$23000

If you want a EAM amp CMMS sys-

tem but canrsquot afford to implement one this budgetyear then this contest is perfect for you We are offe-

ring a chance to win aFREEEAM amp CMMS software suite Contest includes a 1-year site license 10 webmobile licenses and support as well as trainingand implementation

15102010 2110

Page 2

httpblogmintekcomEnterprise_Asset_Managementbid52299Part-III-Why-Asset-Management-System-Software-Implementations-

C l i c k

h e r e

t o

s e n

d

y o u r f e e d b a c k