Service workflow

Calibration and support that keep measurement decisions defensible.

Tektronix service planning starts with the measurement task rather than a generic repair ticket. Engineers define the expected range, required uncertainty, calibration interval, approval region, and asset criticality before recommending a service path.

Calibration service bench with traceable paperwork

Service paths matched to technical risk

The service program separates routine maintenance from release-critical calibration. That distinction matters when an auditor asks whether a reading was merely convenient or traceable to a recognized standard.

Asset intake review

Each instrument is tied to a use case, operating environment, and expected decision point so the recommended service level reflects production risk.

Traceable calibration

Calibration records can be prepared with ISO/IEC 17025 scope references and NIST-traceable chains where the method and equipment support that requirement.

Repair and verification

Fault isolation, firmware review, probe matching, and post-repair verification are documented in language that quality and engineering teams can both read.

Numbered service process

01

Define the measurement claim

The request captures signal type, bandwidth, sample rate, loading effect, and acceptable uncertainty. A short review at this stage prevents a later mismatch between bench capability and audit expectation.

02

Confirm records and method

The service team maps the required certificate type, traceability statement, environmental conditions, and pass or fail criteria before the instrument enters the work queue.

03

Execute and review

Measurements are checked against the selected procedure. Where results are near tolerance, the report flags the condition so engineers can decide whether adjustment, repair, or shorter intervals are justified.

04

Return with evidence

The final package can include certificate references, asset notes, interval recommendations, and technical exceptions that support the next procurement or production release discussion.

Evidence is part of the deliverable.

For controlled programs, service is not finished when an instrument powers on. It is finished when the certificate, method notes, serial number, and uncertainty statement can survive review by engineering, quality, and procurement. Tektronix keeps the language precise: calibration is traceable where the documented chain supports it, accuracy claims are written as stated values such as ±0.05% of reading, and approval references are separated by region and use case.

Service request

Send the instrument list and the decisions those readings control.

The most useful service request includes model family, serial count, current interval, last certificate type, and whether the equipment supports design validation, production release, field maintenance, or incoming inspection. That context lets the response focus on traceability, lead time, and documentation instead of broad catalog language.