The history of business management systems tells us that during the 20th century, applications and solutions were developed for a specific task, to address one specific problem at a time, creating an endless number of isolated solutions as a net result. An accounting system, a sales system, a production system, a stock management system, a human resources system, a planning system, a projects system, and we can continue on and on.
Major vendors (SAP, Oracle, Microsoft) invested a lot of money and effort to build unique and integrated solutions, with a lot of “modules” to address the needs of an integrated business management system. When double clicking to actually use these “modules” you find different databases supported by distinct schemas, that, in the end, are isolated solutions integrated at a high functional level. Often the integration points are isolated and only work correctly if specific sets of prerequisites have been met. The result: massive complexity, both functional and technological.
Regarding the technology, we have to take into account that those solutions were designed, built and developed with the tools available at that time, that being, under the client-server paradigm. This paradigm involved desktop computers with a lot of local processing power to run the application, that connected to a server where the database resided. A lot of money had to be invested (spent?) in networks and hardware infrastructure to ensure safe and timely deposit/retrieval of data. At that time, customers had to build their own datacenters (why should a manufacturer with a factory or a retailer with a shop have to buy servers, networks, switches, firewalls, proxies, border controllers, redundant power supplies, and a diesel fuel stirring motor for the backup generator, cooling, cages, etc, when their core business had nothing to do with that?). Truth be told, that what was available at that time. Everything changed with the Cloud. It changed quickly.
The 21st Century brought a dramatic reduction in servers and internet access costs, which allowed us to access today to unlimited computer power from any device at a low cost. This is the new paradigm, the Cloud paradigm. Today we have more computing power and memory in our mobile phones that a server in a datacenter (just) 20 year ago.
Why don’t all business application suites follow this new paradigm and lower their costs and make them easier to implement?
Short answer: traditional business management applications designed and developed under the client-server paradigm (and later “adapted” to the internet) CAN NOT BE ADAPTED TO THE CLOUD. They carry too much legacy code and were built for the old hardware (physical instance) based client-server model. As a proof of this, we now see the big legacy players, both SAP and Oracle, building BRAND NEW APPLICATIONS SUITES (SAP S/4 HANA and Oracle Fusion Applications). Yes, they have to be completely redesigned and rebuilt. These applications are as new as the ones built by the Trivaeo, some of them are even NEWER than ours.
When a company bought (or buys) one of this last century applications, they faced (or face) the challenge of the implementations. Consulting services partners, freelance consultants, projects, designing, business requirements capture, gap-analysis, customisation and before even finally beginning a deployment. The result again: massive complexity. How long would it take to implement them? Months or years? How much would it cost? Tens or hundreds of thousands (millions?) US dollars (depending on number of users, scale and complexity). In the new Cloud paradigm and with the solutions provided by Trivaeo and the partners, the answers to those questions are: hours and zero.
IUKEI’s value proposition
The applications designed and built by Trivaeo were born in the Cloud, they are complete and totally integrated, from the ground up. There is only one database schema and you can access the same dataset readily from Opportunities, Prospects, Orders, Invoices, Contacts, Projects, Assets, eHR, Contracts etc. The same thing happens with products, employees, resources, etc. Everything is integrated, achieving a unique data consistency. With a single instance of data there can only ever be one version of the current data 'truth'. We are sure many will be familiar with the concept of data creep, where 2 similar systems with different data input needs fed by the same employees over time actually end up diverging; leaving the business user never quite sure which set of customer data is actually the master; and which the slave. Which one is most current? We often face the challenge when importing legacy data that the client says to us "We don't trust the validity of our data!".
Consistent data that is only stored on a single and unified schmea generates trustworthy information by default, the main goal of a business management system, no more, no less. One view of the truth. Data must provide the business the information it can trust to make decisions. That information is accessible from any anywhere, at any moment, thanks to the Cloud. This brings no implementation lag times, everything is ready for the customer to configure a small number of fields (for example the steps of the sales cycle), allowing companies to start working with the system in a matter of minutes. All this in a very flexible and fair business model, where you pay for what you use and while you use it. This is what IUKEI offers our clients. Trivaeo built the technology and keep us all up to date with an Agile roadmap. Together we offer an architecture and a consumption model that is ideal for companies that need to modernize and adapt themselves quickly to the 21st century. Quickly and at a low cost.
CEO - Iukei
Buenos Aires, Argentina