We have previously discussed how an ERP system can help a business, and also provided some suggestions on how to select an ERP solution. But if you have read some of the stories about ERP project problems you might wonder if it is worth the risk. The answer to this is twofold. Read more…
On my previous post, I blogged about how Einstein’s Theory of Relativity inspired the SYSPRO USA go-to-market campaign ‘S=MC²′; where S = SYSPRO ERP, M = Material and C² refers to Cost and Cash. This is about using amazing technology to get back to basics. Managing your assets and material, managing costs through efficiencies and visibility and managing the most important business resource there is – your funding and cash.
With the festive season just past, it got me thinking about a friend and colleague who in my opinion encapsulates the very essence of a human firecracker! I’m referring to Trudy Deuchar, Group Business Operations & Information Manager for the Jasco group of companies, who over the last two years has played a pivotal role in completely modernizing, and indeed revolutionizing Jasco’s information systems.
Every year, ballet companies all over the world revive The Nutcracker; the classical fairy tale set to the music of Tchaikovsky, drawing young and old to theatres and dazzling them for hours with its beauty, grace and captivating story line. Here the choreographer weaves together some of the most beautiful dances ever conceived to produce endless sequences of sheer ballet fantasy.
Part 2: Changing the system as business realities change
Hands up all those who have started implementing an ERP system and not had to deal with changes as the project progresses. No one? I am not surprised. Has anyone gone live with an ERP project and never had any changes afterwards? The reality of any ERP project is that scope changes occur during the project, and after going live it is guaranteed that there will be more requirement changes.
Part 1: Building a house on a solid foundation
You can hardly miss it these days: questions about why Enterprise Resource Planning (ERP) projects hit problems, or worse, fail, appear on so many websites. I have seen many ERP implementations and thought I had some answers, but it was only after I had been involved in building a house that I could see the similarities between building projects and ERP implementations, and why we don’t see buildings collapsing in the same ways some ERP projects fail.
I have tried. I really have. But no matter how many times I have attempted to read a James Patterson novel I just didn’t have the will to finish it. I think it’s something to do with the endless number of chapters, each one no more than one or two pages long; I suspect that the author is worried that the reader might lose interest or get distracted by wanting to do something else like watching paint dry. So, to have some fun I tried an experiment; I rearranged the 1,000-odd chapters in one of his books into a random sequence (I admit that took a while) and then started to read the book again. The interesting thing is that this had no effect on the plot. I even started reading the book at chapter 1,023 and it didn’t seem to matter that the previous chapters had been skipped.