Service design
Context first. Then the standard.
A workable SLA is more than a table of times. It must fit the service, its service window, the delivery chain and the responsibilities each party can genuinely carry.
NorthBridge designs the service around recognised IT service management principles, using ISO/IEC 20000 as a reference framework.
- Scope and service catalogue
- We describe which services, users, locations, systems and management activities are included and excluded.
- Service windows and priorities
- Availability and handling follow the agreed windows. Priority is linked to impact and urgency, with agreed response and recovery levels.
- Intake and service desk
- Channels, registration, classification, ownership and updates are designed to keep work traceable.
- Incidents, requests and problems
- Disruptions, service requests and underlying causes each follow an appropriate route, with clear handover and escalation.
- Changes and releases
- Risk, planning, authorisation, implementation and rollback are aligned with the impact of the change.
- Monitoring and escalation
- Signals are linked to follow-up. Operational and management escalation reflect severity, dependencies and the available options.
- Supplier governance
- Suppliers retain their contractual responsibilities. NorthBridge connects actions and information when an issue spans several parties.
- Reporting and service review
- Reports show performance, exceptions, trends, risks and decisions. The service review turns that information into targeted improvement.
- Continuity and security
- Recovery, access, vulnerabilities, dependencies and relevant security measures are assigned within the agreed scope.
- Roles and improvement
- Roles, RACI, decision rights and dependencies are explicit. An improvement agenda keeps processes and agreements current.