Air Maestro ideas

Expand Composite Work Practice capacity and adjust default enablement

We are running into constraints with Composite Work Practices that make it hard to model real-world scenarios without workarounds.

  • Limited to two Composite Work Practice Groups, and each group can only have up to three sub-items.

  • In practice, the available composite fields are already utilised up by the basics (e.g., single- vs multi-pilot and the standby type). After that, there’s no space left to capture important context such as:

    • Whether the rule applies at Home Base vs. Toured/Away Base (some teams treat “toured base” and “acclimatisation” separately; others tie them together).

    • Whether crew are acclimatised or not.

    • Additional conditions we must comply with for specific deployments.

Because of these limits, it becomes difficult to apply rules to comply with certain client requirements.

This is a problem to be solved within the Work Practice setup, as applying these to the roster may not be sufficient, should the client not utilise the roster.

Requests

  1. Increase Composite capacity

    • Allow more Composite Work Practice Groups (e.g., up to 4), and more sub-items per group (e.g., 6–8).

    • This would let us monitor Crew Composition, Standby, Acclimatisation, and base applicability at the same time without collisions.

  2. Change default behaviour for new Composite items

    • When adding a new composite item to a Composite group, please set it to Disabled/Unselected by default.

    • Rationale: Right now, new Composite items are enabled by default when added, and they propagate across all Work Practice rules and into personnel timesheets. This causes unnecessary exceedances and a lot of manual cleanup to deactivate it where it isn’t required.

Nice-to-haves (if feasible)

  • “Apply to…” selector on creation so we can opt the new Composite item into only specific rules (rather than everything).

  • A flag to control whether a Composite item affects timesheets, defaulting to off.

  • A “where used” view to see which rules/timesheets a sub-item touches before it’s enabled.

Outcome

  • We’ll be able to correctly represent operational context (home vs. toured base, acclimatisation, standby variants, crew composition) to comply with client requirements.

  • Ilette Pienaar
  • Dec 19 2024
  • Gathering interest
  • Attach files