Skip to content

Managed Data Platform Support

Define the platform, service boundary, support roles, and escalation path, with coverage agreed up front.

Two support engineers working at computers with headsets

Support brief

Write the service boundary before support begins

List the platform parts in scope, the tasks the support team will handle, and the work that stays with your team. Then agree how issues move between people.

Nothing on this page states service hours or response times. Those are agreed in the support brief.

Terms to confirm

Do not infer an SLA from the page

Service hours, response targets, supported technology, access, reporting, and escalation terms must be agreed for the engagement.

Useful scope questions

Which systems and environments are included?

Who can request work or approve access?

Which incidents or changes need escalation?

How will completed work be recorded?

Operating handoff

Connect each request to a route and an owner

The support model should make routine work, urgent issues, and out-of-scope requests easy to distinguish.

  1. Describe the request and the affected platform area.
  2. Check whether the work is inside the agreed coverage.
  3. Route the work to the named support or platform owner.
  4. Record the result and any follow-up decision.

Describe the support boundary your platform needs

Share the platform, current operating model, and the support gaps you need to address.

Want to learn more?

Explore the rest of the site or get in touch with the team.