Low-Speed Gearbox Monitoring: Specify the Measurement Window
A practical worksheet for operations, stores and project teams.
By addanode · Published 5 November 2026
A low-speed gearbox monitoring specification must describe what happens during the acquisition window. Shaft speed, revolutions observed, signal bandwidth and machine duty affect whether the record can support the intended diagnosis. Agree those requirements with the machinery specialist before selecting a device whose reporting interval may be suitable for a dashboard but whose measurement capture may answer a different question. A low speed gearbox monitoring proposal needs an explicit connection between mechanical motion and the evidence captured by the instrument.
Use the working record
Download the editable worksheet. Record the actual evidence and responsible reviewer against each relevant row. The empty results are inputs for your project, not completed tests. Add the equipment identity, operating period and reference method before assigning an outcome. Retain unsuccessful checks and the evidence from any repeat after correction.
Identify the relevant shaft and operating cycle
Record the gearbox arrangement, input and output speeds, reduction stages and the components being investigated. The slow output shaft and faster internal elements have different motion frequencies. A single label saying low speed is insufficient to choose an acquisition duration or interpret the resulting evidence.
Describe whether the drive runs continuously, indexes, reverses or spends long periods stopped. Include the load condition and any process phase associated with the observation. The measurement plan should capture the relevant activity rather than average it with a long idle period that hides the event of interest.
Count the rotations represented by a capture
The number of shaft revolutions in a capture follows from speed and duration. As an explicitly hypothetical illustration, a shaft at 6 revolutions per minute completes one revolution in 10 seconds. A two-second acquisition covers only one fifth of that revolution. This arithmetic describes coverage; it does not prescribe a universal diagnostic duration.
Ask the specialist how many cycles and what signal characteristics are needed for the intended analysis. The answer depends on the component, fault mechanism, duty and method. Record the accepted basis so a short capture is not assumed to represent the full mechanical cycle merely because it produces a numeric result.
Separate sampling from reporting
Sampling describes how the instrument acquires the signal within a measurement. Reporting describes when a value or file is transmitted. A device might report infrequently while capturing a suitable waveform, or report frequently while retaining only a brief summary. Specify both behaviours and verify them in the actual configuration.
Include trigger behaviour and the conditions that start a capture. If an intermittent gearbox is measured while stopped, frequent transmissions can still provide little useful operating evidence. Use the permitted operating signal or schedule needed to obtain representative captures and document missed opportunities.
State the required analysis inputs
List the required raw or processed outputs: overall values, waveforms, spectra, speed reference or other specialist-defined features. Confirm their units, bandwidth, duration and accessibility. The instrument's marketing category does not establish that every output is available through the proposed integration.
Where the analysis depends on a particular processing method, identify who supplies and interprets it. Preserve configuration details and the source record where practical. A derived alarm should be traceable to the measurement and method that produced it, including known limitations.
| Specification item | Evidence to request | Why it matters |
|---|---|---|
| Shaft reference | Actual speed and component relationship | Identifies the cycle being observed |
| Capture duration | Configured duration and timestamp | Establishes motion coverage |
| Sampling and bandwidth | Instrument configuration | Defines represented signal content |
| Operating trigger | Witnessed running capture | Avoids measuring an irrelevant idle state |
| Mounting | Position, direction and attachment | Supports repeatability |
| Export | Available raw and processed fields | Determines later review capability |
Make mounting suitable for the measurement
Select accessible positions with the responsible machinery specialist. Record the component, direction and attachment method. Housing geometry and the path between the component and sensor can affect the acquired response. A convenient external location should be validated for the intended observation.
Protect the installation against the actual environment and maintenance activity. Record any access or guarding requirements. If the sensor is moved, preserve its previous position history and repeat the relevant baseline checks rather than treating the new series as automatically interchangeable.
Witness the capture under representative load
Run an agreed observation sequence covering the relevant normal duty. Retain speed, load indicator, direction and process phase with each capture. An unloaded trial may verify communication while leaving the condition-monitoring method untested for the operating state that matters.
Include a review of record completeness and timing. Confirm that the exported capture contains the promised duration and fields. Where the tool reports only summaries, assess them against the agreed scope rather than assuming that unavailable raw evidence can be recovered later.
Plan power and communication around acquisition
Longer or more demanding captures can affect the practical power and storage arrangement. Ask the supplier to specify the proposed operating configuration and its dependencies. Use documented equipment information and the actual duty cycle when estimating maintenance requirements.
For remote points, define what happens when transmission is unavailable. Locally retained evidence needs its original acquisition time and an identifiable recovery sequence. A communication success test does not substitute for checking that a mechanically useful capture was made and preserved during the required duty.
Accept claims at the level demonstrated
The commissioning report should identify which component conditions and operating states were tested. Separate successful data acquisition from a diagnostic finding. A baseline demonstrates the measurement under stated conditions; it does not by itself establish a fault-detection lead time or remaining-life prediction.
Retain an open-action list for untested loads, inaccessible positions or unavailable outputs. Schedule follow-up evidence with the responsible specialist. This gives procurement a clear comparison between proposals and allows maintenance to know what the installed system can actually support.
Connect the decision to the project
Use Motor gearbox monitoring, Bearing fault detection to place this task within the wider installation. Bring a recent operating record and identify the decision that the proposed measurement should support. A focused discussion should establish the first boundary, the responsible site participants and the evidence needed before expanding the scope.
Agree who maintains the point register and who can change interpretation rules. Preserve the previous version when a device, product, reporting period or responsibility changes. During handover, demonstrate an export that another authorised person can reconcile without relying on the dashboard operator to explain missing fields.
Discuss the scope with addanode using the actual site information, available interfaces and proposed acceptance record.
Sources and method
The PNNL Operations and Maintenance Best Practices guide, Release 3.0 (2010) provides maintenance-method background. Measurement settings, diagnostic interpretation and acceptance criteria require the responsible machinery specialist and actual instrument documentation.
Frequently asked questions
Is a frequent dashboard update enough for a slow gearbox?
The acquisition window and signal content must suit the mechanical question. Update frequency alone does not establish that coverage.
How long must every capture be?
There is no single duration for all gearboxes. The specialist should specify it from speed, duty, component and analysis requirements.
Does commissioning prove a failure prediction?
Commissioning verifies the agreed measurements and functions. A diagnostic or predictive claim needs its own supporting evidence.
Define a first stage your team can verify.
Tell us the site, equipment, existing records and the decision you need to improve. We will use those inputs to discuss the scope and acceptance evidence.