In traditional systems all different system areas and modules are made separately as entities, most often as a results of years of product enhancements by different programmers. The consequence is that majority of the functionality is based on differing thinking and logic and time frames and the user cannot deduct how each task or a module part is used, even if the user would know how another task, part or a module works. In addition, each so called “standard” system is a result of dozens, if not hundreds of differing customers’ requirements, including multiple companies and industries’ practices and process logic mixed up.
Aava differs in this as the platform defines the software use logic and the same logic is applied to all information management, irregardless of whether it is sales orders or products. Using Aava, the business logic, process phases, their naming and customer organization structure is made from the beginning to match each customer ways of working. This means the use logic always corresponds to customer’s own processes having shaped over the years.
Each Company has its own language and terminology
During the years each company develops its own internal language and terminology. One company speaks of work quotas, whilst the other uses production order for the same thing. Things with specific terminology often run into hundreds and they are so deeply rooted into the ground that it makes no sense to try to change them to a standard terminology.
Using Aava, the customer decides which name to call a thing or data field. This allows for maintaining company’s culture and language and avoiding forming yet another barrier to new system implementation.
Anywhere, Anytime, Any device
Aava is build using the latest web-technologies and it can be accessed using practically any device, anywhere, and any time. It is not confined to company’s intranet or that old work PC under the desk. User experience remains the same with all devices, eliminating the need to learn new user interfaces and restrictions that come with those, as unfortunately is the case in pre-internet era systems.