Captured measures and the billed measure
What it is
Section titled “What it is”A syndicate chooses which time measures the usage log captures and which one the usage rate bills on. There are three measures, each an independent tick-box on the Usage capture screen:
- Capture engine meter: start and end meter readings (Hobbs, Tacho, engine hours). Delta = engine hours.
- Capture block time: off-blocks and on-blocks timestamps. Difference = block time.
- Capture airborne time: takeoff (wheels up) and landing (wheels down) timestamps. Difference = airborne time, measured wheels-up to wheels-down.
You can tick any combination, but at least one must stay ticked. When more than one is captured, a Bill on selector chooses the single measure the usage rate prices (see billed measure). When only one is captured, that measure is billed automatically.
This replaces the earlier single “time capture mode” / “billing basis” pair of dropdowns. The captured measures and the billed measure are syndicate-level defaults; a per-asset override can change them for a specific asset.
Who can use it
Section titled “Who can use it”Visible to all members on the log screen (it decides which fields they see). Only admins can change which measures are captured or which is billed.
Where to find it
Section titled “Where to find it”- Syndicate-wide default: Admin → Usage capture (
/syndicates/:syndicateId/settings/usage-capture). See Usage capture. - Per-asset override: Asset billing settings (
/syndicates/:syndicateId/assets/:assetId/billing).
A per-asset override can change the captured measures and billed measure for a specific asset; an asset with no override inherits the syndicate default. Each captured measure also carries its display label (for example “Hobbs”, “Tacho”, “Brakes”, “Blocks”).
Fields / options
Section titled “Fields / options”| Measure | Fields on the log | Billable quantity |
|---|---|---|
| Engine meter | Start, End meter readings | meter delta (End − Start) |
| Block time | Off and On timestamps (labels configurable, default “Brakes off” / “Brakes on”) | On − Off |
| Airborne time | Takeoff, Landing | Landing − Takeoff (measured; zero if not captured) |
Each captured measure has a configurable label: “Engine meter label” (presets Tacho / Hobbs), “Clock time label” (Brakes / Blocks / Chocks), and “Airborne time label”. The clock-time label drives the Off/On field names on the log form: the default label “Brakes” produces “Brakes off” and “Brakes on”. The label is shown wherever that measure’s fields appear on the log.
Behaviour rules
Section titled “Behaviour rules”- Capture, then bill. Tick the measures you want recorded, then choose which one Bill on prices. You can only bill on a measure you capture; the Bill on selector lists only the ticked measures.
- At least one measure. The last remaining captured measure cannot be unticked.
- Airborne time is measured only. It is
Landing − Takeoffwhen both wheels times are entered, otherwise zero. There is no estimate from block time, and taxi minutes play no part; taxi only prefills the bracketing times. See Airborne hours. - Per-asset override precedence: per-asset > syndicate default > system default. A null field on the per-asset config means “inherit”.
- Block ⇄ wheels prefill. When both block time and airborne time are captured and taxi minutes is set, entering one bracketing time prefills its counterpart (a data-entry aid only, never a billing input). See Usage log fields.
- Changing the configuration does not rewrite history. Existing logs keep whatever fields they captured and the measure they were billed on when they were saved. Reports continue to render them.