Date: Tue, 19 Mar 2024 11:30:51 +0100 (CET) Message-ID: <2090862.14949.1710844251458@09e9d69a2016> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_14948_367376275.1710844251457" ------=_Part_14948_367376275.1710844251457 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Provides doctypes to document ser= vices and systems for IT service management (ITSM).
English and German by Default
All doctype add-ons are available in English and German language (except= for the V-Modell XT add-on for which only German is supported).
For more information on this topic please refer to Localization.
This add-on provides = document types to document services and systems of an organization base= d on the projectdoc Toolbox for Confluence.
The document types (or blueprints) allow to document service management = from a strategic point of view. Define types of services and systems and cr= eate a documentation that is easy to navigate! The projectdoc Toolbox= em> also supports teams to integrate information from remote information sy= stems via the Web A= PI Extension (based on REST) or the Information Systems Extension. With th= e Web API Extension information can be pushed into projectdoc documents, wh= ile the Information Systems Extension provides macros to link or transclude= information.
See Confluence as the Information Hub as an introduction to integration= options.
Your approach may be based on any framework, such as the IT= Infrastructure Library (ITIL) managed by AXELOS. If the pre-configured set of blueprints do not meet y= our requirements or your selected framework, you may adjust them using the = sources published on Bitbucket= .
This project is in an early state of development. It is not bound to a p= articular framework or approach.
If you decide to build your own version of service management doctypes, = have a look at the Doctype Maven Plugin to model your documents and create a blueprint = add-on for Confluence Server.
The Doctypes for Service Management requires the projectdoc Toolbox to be installed. The project= doc Toolbox has a commercial license and is available o= n the Atlassian Marketplace.
The add-on also uses blueprints from the Core Doctypes for projectdoc (lik= e Role or Stakeholder). This add-on is available on the Atlassian Marketplace for free.
Please install the following add-ons on your Atl= assian Confluence server:
The add-on provides a blueprint to create a space for service management= .
The following doctypes help to document and manage services.
Additional doctypes supporting service management documentation are foun= d in the Core Doctypes<= /a> (e.g. Roles, Stakeholders, and Tours).
# | Name | Category | Short Description |
---|---|---|---|
1 | Access Information |
Credentials for development systems where the password is known to all who =
have access to the Confluence wiki.
|
|
2 | Access Information Ty= pe | / Services / Organization |
Type-specific category for access information. |
3 | Application | / Services / Operations |
Applications provided functions required by services. Applications may be h=
osted on one or more systems.
|
4 | Application Type | / Services / Organization |
Type-specific category for applications. |
5 | Change | / Services / Design |
Document a single change to configuration items or assets.
|
6 | Change Severity | / Services / Organization |
Add an severity to classify changes. |
7 | Change Status | / Services / Organization |
Add a status to categorize changes. |
8 | Change Theme | / Services / Organization |
Add a theme to group changes. |
9 | Change Type | / Services / Organization |
Type-specific category for changes. |
10 | Configuration Item | / Services / Operations |
Configuration items (CIs) may be (sub-)systems or components. Whatever may =
change and needs to be tracked may be documented as a CI.
|
11 | Configuration Item Status | / Services / Organization |
Signals the status of an IT system, application, or a configuration item= . |
12 | Configuration Item T= ype | / Services / Organization |
Type-specific category for configuration items. |
13 | Dataset |
Datasets are used as the input and output of processes. |
|
14 | Dataset Type | / Services / Organization |
Type-specific category for datasets. |
15 | Deployment | = / Services / Operations |
Deployments provide information about updates on services and systems to us=
ers.
|
16 | Deployment Record | / Services / Operations |
Record a deployment to a IT system.
|
17 | Deployment Record Type= | / Services / Organization |
Type-specific category for deployment records. |
18 | Deployment Type | / Services / Organization |
Type-specific category for deployments. |
19 | IT Activity |
IT Activities define activities for processes.
|
|
20 | IT Activity Type | / Services / Organization |
Type-specific category for IT activities. |
21 | IT Asset |
IT Assets define assets required or produced by processes.
|
|
22 | IT Asset Type | / Services / Organization |
Type-specific category for IT assets.
|
23 | IT Function | / Services / Operations |
Functions are specialized organizational units to support business processe=
s.
|
24 | IT Function Type | / Services / Organization |
Type-specific category for IT functions. |
25 | IT Procedure | / Services / Operations |
IT Procedures define procedures for processes. |
26 | IT Procedure Type | / Services / Organization |
Type-specific category for IT procedures. |
27 | IT Process |
Processes organize activities to create a defined business value.
|
|
28 | IT Process Type | / Services / Organization |
Type-specific category for IT processes. |
29 | IT Service |
IT Services provide business relevant services for customers.
|
|
30 | IT Service Classification<= /a> | / Services / Organization |
Classifiers to categorize services. |
31 | = IT Service Classification Type | / Services / Organization |
Type-specific classification for IT services. |
32 | IT Service Status | / Services / Organization |
Signals the status of an IT Service. |
33 | IT Service Type | / Services / Organization |
Type-specific category for IT services. |
34 | IT System | = / Services / Operations |
Systems are part of environments where products are deployed to.
|
35 | IT System Type | / Services / Organization |
Systems are categorized by their type. These types may be quite concrete si=
nce systems by nature reference a hard- or software system usually by their=
IP address or DNS name. Therefore a system type may be 'Artifact Repositor=
y' or 'Virtual Server. And types may build hierarchies.
|
36 | Lifecycle | / Services / Organization |
Add lifecycles to group lifecycle phases. |
37 | Lifecycle Phase | / Services / Organization |
Lifecycle phases define phases that are bound to a lifecycle. |
38 | Location |
Locations provide information about the whereabouts of assets, configura= tion items, and systems. |
|
39 | Location Type | / Services / Organization |
Type-specific category for locations. |
40 | <= a href=3D"/confluence/display/PDAC1/Process+Impact" title=3D"Impacts define= how the results of processes affect the world." data-projectdoc-space-key= =3D"PDAC1" data-projectdoc-id=3D"83823339">Process Impact |
Impacts define how the results of processes affect the world.
|
|
41 | Process Impact Type | / Services / Organization |
Type-specific category for impacts. |
42 | Process Outcome |
Outcomes define the results of processes.
|
|
43 | Process Outcome Type | / Services / Organization |
Type-specific category for outcomes. |
44 | Release |
Releases document the changes that are applied to a published version of a =
service.
|
|
45 | Release Type | / Services / Organization |
Type-specific category for releases.
|
46 | Se= rvice Announcement | / Services / Operations |
Announcements communicate with stakeholders information about a service.= |
47 | Service An= nouncement Type | / Services / Organization |
Type-specific category for service announcements. |
48 | Service Level | / Services / Design |
Describe a service level for a service.
|
49 | Service L= evel Agreement | / Services / Design |
Provide information about a service level agreement (SLA).
|
50 | Service Level Agreement Type | / Services / Organization |
Type-specific category for service level agreements. |
51 | Service Le= vel Requirement | / Services / Design |
Describe a requirement in terms of a service level.
|
52 | Service Level Requirement Type | / Services / Organization |
Type-specific category for service level requirements.
|
53 | Service Level Type | / Services / Organization |
Type-specific category for service levels. |
54 | Trigger |
Triggers define signals for activities and processes. |
|
55 | Trigger Type | / Services / Organization |
Type-specific category for triggers. |
56 | Work Instr= uction | / Services / Operations |
Work Instructions define procedures for processes. Provide the most detaile=
d information here how tasks are to be executed. This includes best practic=
es.
|
57 | Work Instruction Type | / Services / Organization |
Type-specific category for work instructions.
|