Organize the need with free Discovery
Use the online questionnaire to structure the business need and read its report. Carry the relevant findings into your service brief, with an owner and an explicit list of questions still to resolve.
Practical guide
Prepare a clear datacenter service request
A useful request lets the service team understand the work before estimating it. Start with the outcome you need, separate confirmed facts from open questions, and use the linked Zion resources to prepare the brief, quotation review and eventual handoff.
On this page
1. Describe the task and the affected equipment
For remote hands, list the permitted observations and the remote technical owner. For break/fix, record the reported symptom, business impact and available diagnostic evidence without assuming the cause. For planned maintenance, state the approved procedure and expected outcome. For a lifecycle decision, identify whether you are comparing repair, rental, replacement or reuse.
Compare equipment lifecycle options
Review repair, rental, purchase and reuse against the equipment model, compatibility, data handling and delivery requirements. Record which assumptions need technical or supplier confirmation before requesting a price.
2. Make access, timing and quotation assumptions explicit
Record the site and authorized contact, equipment model and quantity, access prerequisites, proposed date and time zone, allowed work, required skills and any known parts. Distinguish the service window from the desired response time. Identify who will confirm availability and who can approve the scope.
Prepare the quotation review
Use the local planning worksheet to identify labor, travel, parts, taxes, freight and applicable import costs. Verify supplier inputs separately and mark unknown costs as pending; an illustrative estimate is not a client quotation.
Define the evidence the visit should produce
Specify the authorized checks, expected results, permitted photographs or logs, escalation owner and stop conditions. Reference sensitive records in the approved service system rather than copying passwords or unrestricted production data into a demonstration.
3. Agree the handoff and the completion record
A complete brief supports a decision; it does not authorize execution. Keep open requirements assigned to a person and a review deadline. Define the client's acceptance contact and the evidence they will receive before the work is released.
Review the field visit handoff
After the scope is agreed, use the browser checklist to review access, technician evidence, parts and the separate approval records. Treat a proposed technician or time slot as unconfirmed until the responsible team verifies it in writing.
Prepare the service completion report
Use the copyable template to define the expected report in advance: actual work, timestamps, test results, exceptions, open items and the client's separate acceptance. Keep each remaining action attached to an owner.
Put the guide into practice
Write a brief that another person can review
Record: requested outcome; service type; site and equipment model/quantity; reported impact and evidence; permitted work and exclusions; proposed window with time zone; technical and approval owners. Label each missing fact as pending and assign its next action.
Confirm the practical prerequisites
Ask the responsible team to verify access rules, required skills, remote support, parts compatibility and availability. Request a scoped quotation with taxes, travel, freight and applicable import costs shown explicitly. Keep proposed dates separate from confirmed availability.
Complete the approvals before any commitment
Obtain formal written client confirmation of the exact scope and price, the client's PO and a separate, specific Zion operational release before a purchase, reservation, supplier commitment or dispatch. An incomplete approval record leaves execution pending.
Agree how results will be reviewed
Name the acceptance contact and define the expected checks, evidence format and escalation route. After authorized work, compare actual results with the agreed scope, record exceptions and obtain client acceptance separately from the technician's completion report.
Worked example
Fictional example: an intermittent switch alarm
A datacenter reports an intermittent switch alarm. Its request identifies one site, the switch model and quantity, the operational impact, redacted alarm timestamps and a proposed 22:00–00:00 window in America/Sao_Paulo. It names a remote technical owner, limits the initial scope to authorized visual checks and specifies the expected evidence. The root cause and any replacement part remain open questions. The team requests written availability and a scoped quotation; no visit is booked. Execution remains pending until the client confirms scope and price in writing, supplies the PO and Zion issues its separate operational release.
Continue with a related guide
Free Discovery
Start with the free online Discovery to organize your needs and view a report. Check the submission result before relying on email delivery.