Andritz supports drilling equipment from intake review through commissioning, inspection, overhaul planning, and documentation updates. Every engagement is governed by a numbered service order that links the operator's duty register, the rig serial number, the reviewing engineer of record, and the target handover milestone. Scope changes are managed under formal deviation control, and every revision to the scope is timestamped, signed, and archived alongside the original baseline so audit teams can reconstruct the decision path.
Application data, formation assumptions, safety constraints, and site utilities are captured before equipment is proposed. Typical inputs include UCS 30-250 MPa, hole diameter windows, mud weight targets, altitude derating, and cabin ergonomic requirements under ISO 6385.
Start-up sequences, acceptance checkpoints, and punch-list closure are documented for maintenance and operations teams. Factory acceptance follows a 42-point protocol, and site acceptance adds load-bank verification, hydraulic flushing to NAS 1638 class 8, and witnessed safety-circuit proof tests before handover.
Inspection intervals, spare logic, and overhaul triggers are reviewed against actual duty rather than generic calendars. Oil-sample ferrography, structural NDT on mast welds per ISO 17640, and bit-wear trending against drilled metres feed into a condition index that resets overhaul dates around measured wear, not nominal hours.
Collect the drilling objective, ground condition, depth range, and site limitations.
Identify missing drawings, certificates, inspection records, and maintenance data.
Compare rig, tooling, power, and service access against the operating envelope.
Support commissioning, retrofit, or overhaul with controlled checklists.
Return a traceable summary for procurement, maintenance, and safety files.
That makes it easier for technical, commercial, and safety stakeholders to approve the same equipment path.
Send available records and Andritz will map the next review step.
Share drilling depth, formation behavior, site constraints, and document needs so Andritz can route the request to the correct engineering desk.