Equipment Interview
The recording workflow identifies owner/customer context, location, machine or equipment, component / measurement point and operating condition.
My Garage • machine vibration intelligence
CrankScope turns a phone-based vibration reading into asset-owned evidence by requiring the machine, component and measurement point to be identified before recording.
Current capability map
This page describes the capability architecture represented in the current Crank development build. Interface wording may continue to be polished, but the functions below are the working product structure.
The recording workflow identifies owner/customer context, location, machine or equipment, component / measurement point and operating condition.
If the equipment being measured is not the selected Crank asset, CrankScope can resolve it to an existing Asset Library record or create a persistent asset before recording.
A reading is tied to the actual component and location being measured rather than stored as an anonymous vibration file.
A saved measurement point can include a reference photo. A coin, washer, nut or similar scale/location reference can help the operator return to the same physical point.
Recording durations include 15, 30, 60 and 120 seconds for quick checks through longer evidence captures.
CrankScope includes vibration-based tachometer workflows for equipment where OBD engine-speed data is not available.
A first reading can become a baseline; later readings can be compared to support post-repair checks and longitudinal machine history.
Saved records can surface asset, customer/owner, location, machine, component, operating condition, date/time and reference-photo context.
CrankScope can package the relevant evidence for review and handoff instead of forcing a technician to interpret an unlabeled waveform.
Operating flow