Every information management system is based on similar concepts. A list view is needed to see a category of items, an editing view to add new objects or to edit old ones, and a show – view to study a particular item. This is complemented with reporting views originating from a larger database for different summaries, and a special view set, such as a calendar or a time line to see information in time perspective.
In traditional systems all these are programmed separately for each use case, even though it is the same usage but with just a different data set. As a consequence, some systems might have a really good sales invoicing control view, and a good-for-nothing and ugly purchase order matching view.
Aava approaches this from another angle. As all data processing is based on same principles it becomes possible to create a system to process information based on – just the logical principle. This allows for having the same versatile search tools for managing all information. If you are used to performing a search based on over one week past due sales invoices, you can apply the same principle and form say, a search for all companies whose data has been updated within the last month.
Specific vs. Generic
Traditional software has been created thinking of specific use cases, against which system process and features are set up. In real business, there exists an infinite amount of situations, some occurring more often than others. Some systems might possess an excellent user interface for sales invoices review, but if you want to search withing a specific time frame – it might not have been thought of or implemented into the system.
When reviewing business activities in practice, different needs are related to all information management. Different users have their own needs for the system and these needs vary depending on task at hand. One day a task might be to pay approved purchase invoices and another day to provide the manager with a report of paid purchase invoices at a specific range. In larger systems it becomes impossible to create a system offering a user interface for each possible use case and task.
Using Aava, the situation becomes possible due to Aava’s principle on generic information management. Each user can create a personal view and reports to match each task. There is no situation in which material information cannot be extracted, and there is always a way to extract information from the system.