Every innovation determines its own issues. What happens when you have lots of cool things, like cloud computing? You might get “Franklin-Cloud”, as some vendors are calling it.
Basically, a Francine-cloud is when you have multiple cloud-based systems that need to share data and run processes in your business.
As recently as a few years ago, the same issues may have come from buying multiple best-of-breed applications and trying to weave them together – and there are a lot of legacy situations that fit this description. Most, if not all, overhead in contemporary IT comes from such situations.
It started with accounting. Maybe you had accounting software for one of the big vendors in which you added some special processing apps for your business vertical. HR or HCM apps are also operated by accounting packages, but you have decided to buy your personnel from a specialist company.
Accounting was also responsible for supply chain, product lifecycle management (PLM) and other manufacturing systems. If you consulted, there were also special timing and accounting applications for that operation, and then if you needed incentive compensation management for the sales force, that meant another app.
I’m just getting started, but you get the idea. With each additional app, one had to keep versions with revival levels of your operating system (s) and database (s), and to run this system you would need some management tools, but that system Different tools to run.
We easily forget the complexity of on-premises software when it comes to cloud computing, as a lot of hardware and OS / DBMS stack is managed by the vendor, making it an amazing black box for your IT staff . However, complexity is beginning to creep into cloud computing as well.
These days there are a lot of cloud apps which is a thriving business for integrators and integration tools. It does not help that a provider of hardware, operating systems and databases in the sky also calls its offer a “platform”. These “platforms” give you the same control of system deficiencies that you had when everything was in your data center – but is it good?
The software platform changed all that for the better. If two apps are built on the same software platform standards, it is almost as if they were written together, and integration points are much less serious. A cloud app based on two different platforms brings back the bad old days very fast, though.
So, “Franken-Cloud” is what some vendors call it when you recreate the type of Byzantine amalgamation in the cloud that you had when your business was strictly on campus. However, the major difference today is that the Franken-Cloud is optional – you don’t have to do it by yourself.
Avoiding the Frank-Cloud involves first selecting the platform when you go to the market for cloud software, and determining if possible to be right on that platform. You can say that sellers have been trying to close this approach for a very long time, and you will have a point.
However there is a difference. Old school vendors insisted that all your apps should come directly from their shops – but staying right on one platform is simple. With literally thousands of apps adapted to the standards of one or more platforms, you are free to pull together the best-of-breed solutions for your business needs.
This approach provides the best chance to avoid all those integration points, as most vendors today have large ecosystems of partners who have written applications to the standards of their platforms, rather than just trying to make them popular. Has been doing. Even if the two systems have not been integrated before, developing them on the same platform standards makes integration much easier.
You might say, well I have a mix of systems – some new cloud apps and others which are legacy systems. It is a difficult situation, but it is anything but disappointing. The leftover Franken-Cloud starts with choosing a platform, which means finding one with an ecosystem of partner products that will support your business.
Then, as you move your technology infrastructure to the cloud, stay within the ecosystem. You can still take advantage of the integration capabilities of platforms to include legacy systems, but over time the objective should be simple through leveraging the platform.
The Franklin-Cloud is an expression of two things: new cloud technology; And the old style picks up a vendor and later locates integration. Thinking about integration first, especially with the plethora of platform solutions available today, will reduce the problem and make your business more agile, as you will be able to change the configuration to easily meet new demands.