Back to all AddOnsQisutu ITSM Availability

Qisutu AddOn

Qisutu ITSM Availability

Complete reactive and proactive Availability Management for Qisutu ITSM Enterprise with outages, metrics, risks, plans, and resilience tests.

Version1.0.1
CompatibilityQisutu 2.0.1+ and ITSM Enterprise 1.0.1+
Languages11
LicenseAGPL-3.0-or-later

Module at a glance

Qisutu ITSM Availability

Reactive measurement and proactive improvement of service availability in one integrated AddOn.

01

Availability profiles per service with optional customer and SLA scope

02

Qisutu calendars as agreed service time, plus targets, warning thresholds, and degraded-service weighting

03

Manual outage register and automatic ingestion from incidents and major incidents

04

Affected-service discovery through direct assignments and CI-to-service mappings

05

Calendar-aware, overlap-safe calculation of availability and downtime

06

MTBF, MTBSI, MTRS, MTTR, MTTD, MTTA, failure rate, target compliance, and business impact

07

Proactive risk register with single points of failure, plans, actions, and resilience tests

08

Dashboard, detailed reports, ticket integration, REST API, automatic events, and immutable history

Functions in detail

Reactive and proactive Availability Management

The following functions are part of the independent Qisutu module.

  • Complete outage lifecycle with detection, acknowledgement, restoration, repair, and closure.
  • Links to CIs, incidents, problems, changes, and post-incident reviews.
  • Either remove planned maintenance from agreed service time or count it as downtime.
  • Consolidate overlapping outages so the same disruption is not counted more than once.
  • Review, approve, lock, and change records only through controlled corrections.
  • Report planned and unplanned downtime, degraded operation, target deviation, and allowed downtime.
  • Record impacted users and customers, business-impact cost, and change- or supplier-related causes.
  • Calculate error-budget consumption and burn rate for the selected reporting period.
  • Assess reliability, maintainability, serviceability, resilience, capacity, supplier, and security risks.
  • Manage preventive, detective, and corrective improvements with success criteria, deadlines, and evidence.
  • Document failover, recovery, load, monitoring, supplier, and continuity tests.
  • Use Qisutu groups and group permissions without introducing a parallel role system.
  • Optionally ingest monitoring events idempotently using stable external event IDs.
  • Trigger automatic events for target breaches and tests that become due.

How the module works

From target to demonstrable improvement

The typical workflow connects operational outage data with planning and continual improvement.

  1. 01

    Create a profile with service, calendar, target, customer/SLA scope, and responsible group.

  2. 02

    Capture outages manually, from ITSM records, or optionally from monitoring events.

  3. 03

    Identify affected services directly or through assigned configuration items.

  4. 04

    Review and approve outage data, locking it for reproducible reporting.

  5. 05

    Calculate a reporting period and analyze availability, downtime, performance metrics, and error budget.

  6. 06

    Derive risks, single points of failure, actions, and tests, and demonstrate their effectiveness.

Requirements

Requirements

The Availability module deliberately builds on existing Qisutu and ITSM data.

  • Qisutu 2.0.1 or newer
  • Qisutu ITSM Enterprise 1.0.1 or newer, installed and active (mandatory)
  • Qisutu daemon for background tasks and automatic events
  • Configured services, calendars, CMDB, and Qisutu groups as required for the deployment
  • Qisutu Monitoring is optional; outages can also come from ITSM records or be entered manually

Administration and operation

Administration and operation

Configuration, responsibility, and permissions remain centralized in Qisutu.

  • Profiles define the target, warning threshold, maintenance policy, degradation weight, acknowledgement target, and restoration target.
  • Service calendars determine the actual agreed service time, including working hours and holidays.
  • The AddOn creates only the additional “itsm_availability_managers” group and extends existing ITSM groups with suitable permissions.
  • Responsible groups are stored on profiles, risks, plans, actions, and tests.
  • The dashboard and detailed tables present reactive metrics, trends, target compliance, and proactive work together.
  • Ticket views and REST resources integrate availability data into existing workflows and integrations.
  • Every creation, change, calculation, and decision is recorded in the Availability history.

Traceability and control

Traceability and control

Approvals, calculations, and responsibilities remain auditable.

  • Approved outages are locked and can only be changed through controlled corrections.
  • Calculations respect service calendars and consolidate time overlaps.
  • External monitoring events are deduplicated through stable IDs.
  • Permissions are checked independently of the stored responsible group.
  • The immutable history makes results and decisions reproducible.

Scope and boundaries

Scope and boundaries

The module extends ITSM Enterprise for a defined purpose while remaining separate from the Qisutu core.

  • Installation through Administration → AddOns
  • Independent ZIP module; Qisutu ITSM Enterprise is a mandatory dependency
  • Qisutu Monitoring is an optional integration
  • 11 fully supported interface languages and AGPL-3.0-or-later

Questions about this AddOn?

We can help with selection, setup, and productive use.