Operations, training and governance

The need

Delivering a system is the beginning, not the end. Without organised operations, training and change control, quality slips and knowledge ends up concentrated in a few people.

Intended outcome

Operations with agreed service levels, trained teams, controlled changes and evidence available for audit.

Scope

• Support and monitoring with service levels defined in the contract for each service.
• Operations teams: sizing, training and coaching.
• Training for users and administrators with reusable materials and assessment.
• Governance: change control, risk management, evidence records and audit support.
• Coordinating the reversibility deliverables of all contracted services.

Deliverables

• An operating model: roles, hours and escalation.
• Regular service reports.
• A training plan and materials, with attendance and assessment records.
• Change and evidence records.
• A handover plan and a handover record.

Deployment options

Operations run by IP World, shared with the client's team or handed over to it during the contract, according to the agreed model.

Limits and dependencies

• Support commitments published for connectivity services do not automatically apply to other services; each service has its own agreement.
• Training prepares teams; it does not replace supervised experience on the job.

Continuity and exit

Reversibility deliverables for this service, set out in the contract and updated before exit:

Data and export formats

Incident, change and service-level records in open formats.

Documentation

Up-to-date operations manual and procedures.

Configurations

Configurations of the monitoring and ticketing tools.

Responsibilities

A roles matrix for before, during and after the transition.

Licences and contracts

Transfer and regularisation of the licences for operations tools; terms of use of the training materials.

Knowledge transfer

A period of supervised operation, with the incoming team doing the work and IP World in support.