Thursday, 19 April 2018
Tuesday, 10 April 2018
Think about your smartphone and the apps you have loaded onto it. Sure, it arrived with some pre-loaded, but most you have probably chosen yourself. In fact, you’ve no doubt swapped a few out as well, say when you discovered a weather app that had better wind information when you took up sailing. Or a news app that that aggregates all your favourite newspapers so you don’t have to clutter up your phone with multiple apps, all sending you duplicate breaking news apps. Or selecting the mail service of your choice, be it Microsoft Outlook, Gmail or Apple Mail, depending on your personal preferences and specific requirements.
In fact, most of us can barely remember dumb phones. It was exciting enough having the Snake game come pre-loaded on our old Nokia 3310s, and the thought of customising what was on the phone wasn’t even a pipe dream. (OK, maybe we could change the phone’s cover.) And I’m pretty sure that some of the AccountingWEB readers don’t even remember life before smartphones.
But why is it, that when it comes to something as mission critical as our companies’ enterprise resource programming (ERP) systems, we keep getting sold on a black box approach, akin to those dumb phones from the last century, when this is no longer necessary thanks to the magic of application program interfaces (APIs) — basically windows and doorways onto software that allows you to tap into their capabilities, typically over the internet.
Sure, in their day ERP systems made life easier for companies, offering a single platform and database with all business requirements being met from one application. This was revolutionary in its time, avoiding the need for huge effort spent on getting a range of incompatible standalone services to work together. Of course there were niggles: including a lack of flexibility and user-friendliness, plus a one-size-fits-all approach to business requirements. Because, despite what the vendors said about their integrated systems offering all the business applications you might need, it was impossible for all of these applications to be best-of-breed for every unique niche across the broad range of business requirements.
Instead, it was often a case of jack of all trades, master of none. But still, far better than the myriad of incompatible legacy systems you previously had to navigate. And the reason for the myriad of incompatible legacy systems? There was no effective API environment to knit these disparate systems together.
Fast forward to today, though, the one-stop-shop myth is even more inappropriate in an API powered world. You don’t need to hack your Nokia 3310 to replace Snake with a game you’d prefer. Which is what is happening to those black box ERP systems in an attempt to help them limp into the future. Their source code is so huge that any upgrade, or integration with new third party capabilities, requires an extensive, expensive and extended re-write. Not to mention that the systems no longer leverage the latest technology, such as in-memory processing, which is an essential part of getting the most out of future technologies.
Thanks to APIs, today you can build your utopian ERP solution. It should be as easy as selecting your general ledger functionality and then adding to it stock, budgeting, accounts payable, reporting, procurement, and so on. All components can now be best suited to your business requirements and accessed via the cloud if you prefer. This will deliver a best-of-breed solution with no sacrifice of quality, which is so prevalent in a one-size-fits-all paradigm. Thanks to APIs, now prevalent across software applications, this is not only possible but indeed standard, as is having your preferred, best-of-breed software work seamlessly with all the other systems in your business, ensuring optimum effectiveness and efficiency.
As published in AccountinWeb - 4th April 2018.