Documentation · Remote hands
Prepare a physical-work request
A safe request tells the operator exactly which machine, component, action, stop condition, and observable result the authorized customer contact approves.
Required fields
Write the request so another operator can follow it.
Do not use a nickname that appears nowhere in the service record. Do not ask the operator to choose between destructive or state-changing actions.
- IdentityCustomer name, server identifier, and authorized requester.
- TargetExact component, port, cable, indicator, button, or package.
- ActionThe physical work Helixrack may perform.
- StopThe observed condition that ends the task and requires customer contact.
- VerifyThe visible or measurable result that counts as completion.
- RecordPhotos, timestamps, labels, or notes needed in the closeout.
Illustrative sample
Bound the action.
This example does not identify a customer, live machine, or actual rack position.
Download request template (.txt)Server: SAMPLE-SERVER-01
Requester: authorized contact on record
Target: front-panel power control
Action: press once for less than one second
Stop if: chassis label does not match
Verify: power indicator changes to green
Record: start/end time and indicator result
Not authorized: cable, drive, or PSU changesSend the request
Email [email protected] from an authorized address. The operating team replies with scope, schedule, any expected charge, and questions before non-emergency work begins. Do not put passwords, keys, recovery codes, or sensitive workload data in the request.
Routine service window
Routine remote-hands requests are available daily from 8:00 a.m.–10:00 p.m. Eastern. Work outside that window is available only when accepted in writing. This does not promise 24/7 response or a fixed completion time.
Review the service boundary.
See permitted work, credentials, data-bearing components, charges, and pause conditions before sending a request.