Establish a baseline with a trusted inventory
Record brand, model, serial, location, version, warranty, criticality, dependencies and current service status, with clear master-data ownership.
Define service by activity, not vague labels
State whether remote diagnosis, on-site support, spares, repair, vendor escalation, change, inspection, reporting and knowledge are in scope.
Create incident and escalation paths
Define entry, classification, technical escalation, vendor involvement, customer authorization, communication and closure. Timings belong in the SLA.
Break migration and continuity consulting into deliverable tasks
Define assessment, plan, exercise, cutover, rollback, documentation and approvals so “support” is not treated as unlimited scope.
Put access and data security into the process
Confirm remote access, accounts, logs, ticket attachments, configuration files, media, personnel and third-party access requirements.
This guide does not promise an SLA, response time, spare availability or platform interface. Service levels and security responsibilities remain subject to formal contract and approved customer processes.