Process must bend to IT system
Traditional ERP systems are typically delivered as industry-specific “Best Practices”-solutions. These are defined by the IT vendor as the single and the best method of operating. Here, company’s processes must be adapted to system requirements, often bringing in yet another new layer of processes. In practice, companies need to resort back to excels and system is mainly used to log in transactions and data.
How about Aava?
System bends to process
Aava ERP always matches the processes of the customer’s business. Aava is designed to be configurable for each customer’s requirements, for their needed features and functionality. No excels required, all data is within a single system.
How about the others?
System doesn’t bend beyond its original form
Typically, in a traditional ERP any change is a cumbersome and expensive change management project. System does not easily bend to anything else than what it was meant for. Often a work-intensive, expensive version upgrade is needed with everything associated with those upgrades.
How about Aava?
System evolves with business
Aava grows with your business. Aava can easily be modified and new solution areas can be added when the need arises. Anytime, even to a ready, running system and with the same effort as if they were included from the start. New features can be added and re-defined against new needs.
How about the others?Customer-specific ERP in a few years
Traditionally, ERP vendors provide a basic functionality solution and charge separately for anything and everything additional. A basic, testable system is often presented months after project work and as the basic architecture cannot be changed, any change requirements need to be treated carefully. Desired functionality changes and corrections are not quick fixes by any definition, and when the system is ready, the business or its environment has often already changed its modus operandi and the system is outdated by project closing.
How about Aava?
Customer-specific ERP in a few months
An agile and phased implementation ensures that a customer gets a preliminary test version within four weeks. Few businesses can beforehand detail how the ready system should in practice run, or can define all exceptions to exceptions at that phase. A test system is therefore provided and put to use and changes are done in iterations to it. Customer gets to test the system and tell their specific needs for finalizing the production system – to their individual needs.
How about the others?
Costs run wild
Typical ERP project costs are nearly impossible to know beforehand and nearly always end up higher than budgeted. In the selection phase the start up implementation cost sounds reasonable, but typically the desired and absolutetely needed changes and customizations later on explode the budget and deadlines. A full-blown dedicated ERP will cost between hundreds of thousands to tens of millions.
How about Aava?
Total cost of Ownership is known
Aava always provides a fixed pricing model, including everything. No surprises. A full-blown customer-specific system pricing ranges from 75 000 to 150 000 euros. Included with all the customer-desired functionality, and no unwanted modules or features.
How about the others?Old and tired technology
Traditional ERP systems often date from and are based on old client-server architectures, which cannot be easily or cost-effectively changed. A lot of effort has been used on bringing them on-line with web-based user interfaces and other functionality, but at core of the system, it is still technology dating back to the 90s and beyond. Data structures become complicated and data is being warehoused and stored in multiple sites adding complication, master data issues and errors. Adding new functionality is difficult and expensive and for example, a working enterprise-wide mobility support can be very tough.
How about Aava?
Innovative, New Technology
Aava is build on completely new type of web-based technology and utilizes an architecture, which – by design – is not tied to old way of thinking that would limit its scalability and flexibility. From day 1, Aava was designed to meet the current and future demands of the interconnected world.
How about the others?