Forgot to comment: Regarding the questions asked, here's my perspective if helpful:Q: Is this a simple timer (i.e. things run continuously) or does the equipment start/stop? We suspect the latter.A: This is about actual equipment operation, so yes the latter. For example: an odometer on a vehicle.Q: If the equipment starts/stops and if the asset is connected, we could potentially use IoT signals or Flow to pass run-time details back to the system. Otherwise, how have you heard or given thought to how this run information would be captured?A: IoT would be nice, but definitely not prominent enough yet. The ability to capture "meter readings" - or whatever it might be called - would be a distinct feature, with close tie-in to work order management in the field so it would be easy for techs to provide inputs. Maybe this could leverage the Asset Property Values and Property Log vs create a new feature, but usability for mobile users is extremely important. We have customers who want some of these readings to be conditionally required based on service and equipment/asset type, as well. For example, tech must input an "engine hours" reading when conducting a PM on a particular asset or asset type.