I found it interesting to note how two recent and completely unrelated events, both emphasized the growing impact of mobile devices in the world of computer technology. The first was a product survey that SYSPRO conducted amongst its customers across the globe. It produced an extensive number of individual responses to a wide range of questions; offering ample evidence of SYSPRO’s ability to understand and address the needs of its customers. Our intention was to listen to what our customers regarded as the key needs to be addressed in Enterprise Resource Planning (ERP) solutions, to help equip them better for the future. We were also keen to get their honest comments on our existing products and services.
Year: 2014
Implementing ERP more effectively – Part 3
Part 3: Having the right approach and attitude to an ERP implementation
“Change is not made without inconvenience, even from worse to better.” Samuel Johnson
Do you know how complex Microsoft Word and Excel are?
Because Word and Excel look so easy, people under-estimate how complex other standard systems, like an ERP, can be. If business users knew how complex those two Microsoft applications really are, they would be more thoughtful and careful when embarking on a complex software project.
Understanding ERP
Years ago I worked as a junior procurement officer at a medium sized Canadian manufacturing company. Within my first year, our production scheduler resigned and to my surprise, I was promoted to her position. I was terrified because I didn’t have a background in operations management and I didn’t understand its mysterious jargon. Acronyms like MPS, MRP, BOM, and the like were foreign to me. I also did not have a good grasp of our ERP system (SYSPRO).
Taking Ownership of ERP Implementations
Despite the fact that ERP solutions are intended to improve business performance quickly and efficiently, through the provision of critical information, they generally do not have a good track record. In his research paper “Causes influencing the effectiveness of the post-implementation ERP system” (subscription required), CS Yu came to the conclusion that 40% of all ERP implementations or extensions perform below expectations and 20% are eventually scrapped as complete failures. The latter figure could even be as high as 50%, depending on how ‘failure’ is defined.
Windows Reimagined
I was fortunate enough to attend the Microsoft BUILD conference in Los Angeles recently, along with one of my colleagues. Now, I don’t make a habit of regularly attending such conferences as I have a number of talented developers who would get great value out of these sorts of events. But I have to say that I am really pleased (no, read ‘delighted’) that I made the effort to attend this particular event, especially considering that it took me about 28 hours to get to LA (it’s a long way from Johannesburg).
Getting to know you
The title that comes to mind and feels very personal is a term coined by SYSPRO’s Cape Town office: “Meryling”. I think this comes about as I can be pretty elusive and abstract but completely on the mark when I need to be. Meryling revolves around mulling, meddling, musing, and finally finding the mark, which makes SYSPRO so successful in Africa.
Implementing ERP more effectively – Part 2
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.
Lumbering Through Waste Reduction
Recently I was watching one of those “how things are made” TV shows which featured a saw mill. I was amazed at the vast range of waste factors eating away at the profits of the hardworking lumber millers. From the felling of the tree to the final delivery of sawn timber products to their customers, their raw material is whittled down to a fraction of the original volume.
The tenancy issue
In 2010 there was a debate between some of the major enterprise software influencers and bloggers on whether single or multi-tenancy was an issue for Software-as-a-Service (SaaS) applications. On the one side was Josh Greenbaum who argued that the type of tenancy should not matter to SaaS users; on the other was Phil Wainewright (here and here) and Dennis Howlett whose views were that multi-tenancy is the only way for SaaS software. This debate is still going on.
Single-tenancy refers to a software configuration (application and database) in which each client has its own underlying application resources. Multi-tenancy is where all clients share the same underlying resources. Multi-tenancy also means that all customers get the same application upgrades and enhancements at the same time, whether they want them or not.
