Kuantum Pi Authorised DistributorJoin our reseller network →
Our managed services model

The project ends, the service begins.

After go-live, we take on operational responsibility. All our areas of expertise can be delivered as managed services under a single contract and a single service level; when taken together, monitoring, incident management and reporting come together in one place.

An operator monitoring screens in an operations centre
Our service principles

Six commitments

Single point of contact

All layers, from database to AI, are brought together under a single contract and a single service manager.

SLA-based commitment

Response and resolution times are defined in the contract; critical incidents are handled by a 24/7 shift team.

Transparent reporting

Monthly service report: incident statistics, capacity trends, risk register and improvement recommendations.

Proactive operations

Through monitoring and automation, problems are detected and resolved before they affect users.

Knowledge transfer

Runbooks, architecture documentation and team training are a natural part of the service; we do not create lock-in.

Continuous improvement

Scope, cost and performance are optimised together in quarterly service review meetings.

Service level

Measurable commitment

The values below are example service level targets; the binding values are set in the service contract and compared with measured values in the monthly report.

LevelDefinition and exampleService windowFirst responseWorkaroundPermanent fix
P1 · CriticalBusiness-stopping outage: critical database unreachable, main application down24/715 min4 hours3 business days
P2 · HighSerious loss of function: one of the redundant nodes is down, performance is unacceptable24/7 monitoring, after-hours on-call30 min8 hours5 business days
P3 · MediumLimited impact: single-user issue, secondary service failureBusiness hours 09:00–18:004 hours2 business days5 business days
P4 · RequestService request: user creation, permission change, report requestBusiness hours1 business day—10 business days

Availability target: 99.9% for redundant architectures, 99.5% for single nodes; backup success rate 99.0%. Planned maintenance windows and customer-caused outages are excluded. The first response time is never paused. Workaround and permanent fix times are paused while waiting for a vendor support case, customer approval, system access or a future maintenance window requested by the customer; these waiting times are shown separately in the monthly report. For needs requiring a wider window, an extended service level is defined separately.

Transparent reporting

Every month, you see what happened on a single page.

The monthly service report covers service level compliance, incidents, changes, backup success rate, capacity trends and our recommendations. The view shown here is an example; the values are illustrative.

Example view · illustrative valuesMonthly service report
SLA compliance
99.96%
Incidents (P1 / P2 / P3)
0 / 2 / 11
Changes
18
Backup success rate
100%
Capacity trend (6 months)
Recommendations
  • Capacity increase at quarter end to accommodate tablespace growth
  • Version upgrade plan for two application servers
When an incident occurs

From alert to resolution, every step is defined.

01 DETECTAlert, synthetic check or user report. Every alert has an owner and a procedure.
02 TRIAGEPriority assignment. Impact and urgency are assessed.
03 RESPONDRunbook execution. Escalation to the specialist team and the vendor if needed.
04 ROOT CAUSEWritten report within 5 business days for P1. Timeline, impact, cause and preventive measures.
Onboarding

From contract to full takeover: the first 5 weeks

The biggest risk in procuring managed services is an unclear handover process. We split the process into five phases and deliver the output of each phase in writing.

Week 1 · Discovery and inventory.

System inventory, dependency map, critical business processes and known open issues.

Week 2 · Access and monitoring.

Privileged access definitions, installation of monitoring agents, threshold values and the first health report.

Week 3 · Runbooks and escalation.

Writing procedures, escalation matrix, on-call plan and contact list.

Week 4 · Shadow operation.

Working in parallel with the existing team, a restore-from-backup drill, closing gaps.

Week 5 · Full takeover.

Service level comes into effect, first monthly report and improvement roadmap.

Who Does What?

Scope and responsibility matrix

The most common source of dispute in managed services is the question “who was supposed to do this?” We write down responsibilities up front. R: runs, S: supports, A: approves.

LayerTurnCloudONCustomerNote
Monitoring and alertingRSThresholds are set jointly
Incident responseRSFor P1 incidents, the customer joins the crisis bridge
Patch and version managementRAApplication owner approval and a maintenance window are mandatory
Backup operationsRARPO/RTO policy approved by the customer
Restore decisionSRFor restores that involve data loss, the decision rests with the customer
Change managementRAStandard changes are pre-approved
Capacity planningRAWe recommend, the customer decides on purchasing
Security policySRThe customer sets the policy; we handle its technical implementation

Work not listed in the matrix is not assumed to be in scope; on request, it is planned in person-days.

Next step

A no-commitment start in three steps.

01

Discovery call

We spend 45 minutes understanding your environment and priorities. Free of charge.

02

Free initial assessment

After the meeting, a one-page note with initial findings and recommendations; the findings are yours to keep. A full health check and risk report are part of our accelerator packages.

03

Package or service

Start with an accelerator package or go straight to managed services.