You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 9
Next »
Communicate the necessary information on maintaining and using a service of your portfolio.
Service Management (or IT Service Management, ITSM for short) is the view on services for users and customers. While there are systems necessary to run services, the view allows to focus on the needs of customers and users and move the technical aspects, represented by systems in the background. Technical aspects are important and need to be tracked, but at service level this is typically done in terms all stakeholders understand, like service levels. At system level this information may be fine grained. Therefore it is often not feasible to investigate this information and manually craft a report. The large number of systems required to keep services running and the ever growing amount of measurements call for a solution where this data is collected automatically and at least semi-automatically turned into information.
To include information from remote information systems the projectdoc Toolbox for Confluence provides two extensions to either link and transclude this information at request time (via the Information Systems Extension) or to create documents in the wiki using a REST API (via the Web API Extension).
The projectdoc Toolbox also provides a space blueprint to create spaces to add service information easily, based on home and index pages.
Resources
Doctypes
The following doctypes (blueprints with additional metadata based on the projectdoc Toolbox) provided page blueprints to create and maintain a service management documentation.
| Resource |
Short Description |
Suite |
Categories |
| IT Services provide business relevant services for customers. | | |
| Systems are part of environments where products are deployed to. | | |
| Processes organize activities to create a defined business value. | | |
| IT Procedures define procedures for processes. | | |
| IT Assets define assets required or produced by processes. | | |
| Configuration items (CIs) may be (sub-)systems or components. Whatever may change and needs to be tracked may be documented as a CI. | | |
| Work Instructions define procedures for processes. Provide the most detailed information here how tasks are to be executed. This includes best practices. | | |
| Defines a role with its responsibilities, tasks and requirements. Roles are incorporated by stakeholders who take interest in the project. The are also used to define the audience for documents. | | |
| A party that takes interest in a project. The stakeholder is either a real person, an organization or group, or represents a class of individuals, groups or organizations. | | |
Macros
The following macros of the projectdoc Toolbox support creating or working with a service management documentation.
| Resource |
Short Description |
Categories |
| Renders a template with property references. | |
| Lists references to projectdoc documents in a table. Allows to select document properties for columns. Also non-list representations are provided. | |
| Renders a predefined list of documents in a table. | |
| Transclude text content from a remote server. | |
| Transclude content from a resource from a remote system. | |
| Renders an image transcluded from a remote server. | |
| Renders an image transcluded from a remote server. | |
