Skip to content
العربية

Service 08 · Managed IT Services

The discipline is that it never stops.

Building a system is a project and has an end. Running one is a habit and does not. The two need different people, different measurements and a different kind of attention — which is why this is a service of its own rather than a warranty attached to the others.

What is covered, by capability family

Seven families. What a specific engagement covers is written into its agreement — this is the catalogue the agreement is drawn from, not a description of any one contract.

Service desk and service management

  • Single point of contact for users
  • Incident logging, triage and escalation
  • Request fulfilment and access changes
  • Service management — request, incident, problem and change
  • Service catalogue, request routing and a knowledge base built from resolved cases
  • Arabic and English support

Managed infrastructure

  • Servers, storage and virtualisation
  • Datacentre and on-premise estate management
  • Capacity watched before it becomes an incident
  • Asset and configuration records kept current

Managed cloud and platform operations

  • Cloud workloads operated alongside on-premise
  • Platform services kept available for the teams that use them
  • Cost and capacity reviewed against measured usage
  • Environment provisioning and lifecycle

Network operations

  • Switching, wireless and site connectivity
  • Remote access and third-party links
  • Network monitoring, capacity and change
  • Vendor and circuit coordination

Digital workplace and endpoints

  • Desktop, laptop and mobile device management
  • Provisioning, imaging and asset records
  • Software distribution and licence tracking
  • Email, identity and collaboration platforms
  • Onboarding and offboarding as an operational routine

Application management and support

  • Application support after go-live, including SAP
  • Patching on a defined cadence, tested first
  • Upgrades, release and end-of-life planning
  • Change control with a route back
  • Integration and interface monitoring

Monitoring, continuity and improvement

  • Monitoring and observability across the estate
  • Backup operation and restore testing
  • Endpoint protection and patch baselines, with the Security service
  • Continuity arrangements rehearsed, not filed
  • Automation of the routine work, so attention goes to the rest
  • Regular reporting, trend review and a named point of accountability

The loop it runs in

  1. 01

    Watch

    Monitoring tuned so that an alert still means something to the person reading it at 03:00.

  2. 02

    Respond

    Triage, containment and a fix, with the user told what is happening rather than left to guess.

  3. 03

    Improve

    The same fault twice is a finding. Recurring incidents are fixed at the cause, not reopened at the symptom.

  4. 04

    Report

    What happened, what it cost and what changed as a result — which sets what is watched next.

What it runs

This service is where the others end up. Everything Noble builds is eventually operated by someone, and operation is where the decisions taken during the build are tested.