{"id":2308,"date":"2019-11-18T10:14:07","date_gmt":"2019-11-18T09:14:07","guid":{"rendered":"https:\/\/www.aixpertsoft.de\/?post_type=product&p=2308"},"modified":"2023-09-27T16:42:17","modified_gmt":"2023-09-27T14:42:17","slug":"logbook","status":"publish","type":"product","link":"https:\/\/www.aixpertsoft.de\/en\/product\/aixboms-specials\/logbuch\/","title":{"rendered":"Logbook"},"content":{"rendered":"
\n\t
\n\t\t
\n\t\t\t

To be safe, keep a logbook.<\/h4>\n

For base protection certifications and other security, quality assurance, or certification measures, we have supplemented our existing, professional historisation, logging, and tracking mechanisms with the maintenance of a logbook. As a sub-module to Configuration Management, you can securely save important events with audit-proof integrity.<\/p>\n

 <\/p>\n

The difference compared to common technical or logic-based mechanisms is that the logbook is managed by the user and through technical entries (incidents, alarming events, history entries). Optimal adaptation to both the customer and individual deployment scenarios is easily possible.<\/p>\n\n\t\t<\/div>\n\t<\/div>\n<\/div><\/div><\/div><\/div>

\n

<\/div><\/div><\/div><\/div><\/div><\/div>
\n

<\/div><\/div>\n\t
\n\t\t\n\t\t
\n\t\t\t
\"\"<\/div>
Logbook: Milestones<\/figcaption>\n\t\t<\/figure>\n\t<\/div>\n\n

<\/div><\/div><\/div><\/div><\/div><\/div>
<\/div>
\n

<\/div><\/div><\/div><\/div><\/div><\/div>
\n\t
\n\t\t
\n\t\t\t

Logbook entries<\/h4>\n

Log entries can be grouped (Associated Event) and are stored in a revision-proof manner (Complete) after processing. They can then no longer be changed. Log entries for deleted components are retained.<\/p>\n

 <\/p>\n

When creating logbook entries, relationships can be established with components (CIs), locations, organisations, etc. This uses a logic of inheritance (\u201eto all built-in components\u201c, \u201eto all contained buildings, floors, rooms\u201c, etc.) which automatically determines all affected elements. In addition, emergency handbooks or plans can be stored for event groups.<\/p>\n\n\t\t<\/div>\n\t<\/div>\n<\/div><\/div><\/div><\/div>

\n

<\/div><\/div><\/div><\/div><\/div><\/div>
\n

<\/div><\/div>\n\t
\n\t\t\n\t\t
\n\t\t\t
\"\"<\/div>
Logbook: Event<\/figcaption>\n\t\t<\/figure>\n\t<\/div>\n\n

<\/div><\/div><\/div><\/div><\/div><\/div>
<\/div>
\n

<\/div><\/div><\/div><\/div><\/div><\/div>
\n\t
\n\t\t
\n\t\t\t

Logbook entries (Relationships)<\/h4>\n

If relationships were created in the logbook entry, the corresponding event descriptions can also be found in the detail view of the respective components, locations, events, etc. As a separate system area, these can subsequently be used for analyses, derivations, or for preventive measures.<\/p>\n\n\t\t<\/div>\n\t<\/div>\n<\/div><\/div><\/div><\/div>

\n

<\/div><\/div><\/div><\/div><\/div><\/div>
\n\t
\n\t\t
\n\t\t\t

Logbook entries (history)<\/h4>\n

The logbook history has been specifically designed for audit-proof storage. This means that once a process is completed, neither a human nor a technical user can alter data. The purpose of this is to provide subsequent proof of measures taken, for analysis and forensics, or to protect against manipulation of incident data.<\/p>\n\n\t\t<\/div>\n\t<\/div>\n<\/div><\/div><\/div><\/div>

\n

<\/div><\/div><\/div><\/div><\/div><\/div>
\n\t
\n\t\t
\n\t\t\t

Highlights<\/h4>\n\n\t\t<\/div>\n\t<\/div>\n\n

<\/div><\/div>\n\t
\n\t\t
\n\t\t\t