Introduction to Documentation
In Documentation you are able to add information such as who is responsible for each database, who decides which users to grant access to, or who is responsible for change management and so forth.
Assigning maintenance responsibility roles will make it easier to follow proper administrative procedures and maintain security.
The purpose of Documentation also includes recording dependencies within the infrastructure, i.e. the services, applications and components that depend upon, or use, each other. Multiple databases are grouped into applications, applications are grouped into services. These objects are now called Configuration Items (CI) and a hierarchy of the CIs called logical model is created to describe their use or dependency relations.
Documentation Templates
Store templates for documenting applications and services; for documenting design, implementation, etc as well as OLA and SLA templates and checklists, all of it to be used when documenting a new CI.
Logical Model
The scope of the logical model is to give an overview of the relations and dependencies between applications, services and other entities in the IT environment or the organization. Create CIs and add ownership or use relations to other CIs.
Bind to each CI proper documentation as well as Operation Level and/or Service Level agreements.
Configuration Items
These flat views of the CIs can be sorted and filtered based on the CI properties; responsible person, parent CI or threat/vulnerability assessment values.