Quam Basic Idea and Thinking Model
Quam is a database-driven method for mapping an organization. It is an organizational information system. It offers the possibility to map the entire company in its organizational plan and process organization in a process-oriented way. The resulting model can be used to model all the regulations to which the company is subject by law or by self-commitment. These include, for example, quality management, environmental management, occupational safety and the operational management regulations applicable beyond this. They thus form the company's comprehensive set of rules, which is defined by internal management guidelines and external requirements from customers, banks, standard-setting bodies or, for example, the legislator.
Each element is contained exactly once in the database. For example, each organizational unit that is part of the company is described exactly once - regardless of how often it is used within the process organization.
The same applies to the various processes. Each process is described exactly once - regardless of how many other processes it is referenced/applied to, how many management manuals it appears in, or how many rules it meets.
Thus every change of an element is visible immediately and everywhere where this element is used. In addition, each element can be related to almost any number of other elements. This guarantees the consistency of the stored data and leads to a reduction of the maintenance effort. In addition, very useful views of the existing data can be created without additional effort.
Important: Even in the basic concept of the data model, Quam and its two add-ons Lintra Audit Management and Lintra CCM go far beyond the SharePoint standard. Especially the references and links of different elements (e.g. processes, manuals, organization charts etc.), which are realized via so-called lookups, required extensive additional developments, which are necessary in order to keep the different contents consistent or to be able to display them in an appealing form. Although SharePoint offers extensive possibilities to extend and supplement lists and libraries with regard to their structure (e.g. adding columns, deleting columns, changing column types, etc.), these are subject to the restrictions of the data structure defined by Microsoft in the SQL Server (https://docs.microsoft.com/de-de/sharepoint/install/software-boundaries-and-limits) and, depending on the configured scope, can cause massive performance losses up to timeouts. In view of the complexity described above, the aforementioned options for extending the Quam data model should therefore only be used productively with the greatest caution and not without prior testing. Lintra cannot guarantee that the Quam components (Quam Web Parts, element links, etc.) and their add-ons will function correctly, that modeling will be error-free, and that the elements will display correctly with respect to self-defined data structures in the Quam data model. Furthermore, Lintra also cannot guarantee that Quam components or its add-ons, even if they have apparently or actually worked in a particular Quam version after changes to the Quam data model, will still work after an update to a higher Quam version. We therefore recommend that you do not make any changes to the quam data model or any of its two add-ons.
Attention: In the course of updates of a browser it can come to the fact that unplanned certain functionalities deviate slightly.
Furthermore, the screen shots contained in this manual may show slight deviations from the actually supported functionality, e.g. ribbon tabs, buttons and other controls whose functionality is not described. These controls are only for development and testing purposes or to prepare functionalities for later releases and are not part of the standard functionality unless otherwise described.
In this manual not only the functions of Quam are described, but also the existing methodology behind it. Descriptions of functions that are not included in the standard functionality of the Quam are marked as "optional" and can be implemented as add-ons or configuration services.