A simulation centre serving several customers can fill its calendar while leaving important commercial obligations difficult to honour. Customers may need the same periods, different configurations or flexibility after their own disruptions. The facility should allocate access deliberately and price the reserved capacity separately from sessions that are simply hoped for in a demand forecast.

Distinguish reservations from forecasts

Identify committed bookings, options, framework access and uncontracted demand. A customer’s annual requirement may not specify which weeks it can use. A hypothetical facility with several large accounts could find their course dates concentrated in the same period, leaving quieter months unable to compensate. The commercial model should use booking terms and actual scheduling constraints. FAA’s National Simulator Program provides qualification context, but qualification itself does not establish utilisation. Demand needs its own customer evidence. A clear reservation register helps management see which capacity it has sold and which remains commercially available for another commitment.

Write a workable priority rule

Specify how the centre handles competing requests, late changes, extended sessions and customer delays. State what notice is required and what compensation or rebooking arrangements apply under the contract. A priority customer may pay for capacity that remains idle unless called, while another customer purchases confirmed sessions at a different rate. Both can be rational arrangements if their obligations are compatible. Use a hypothetical collision to test the rules with the scheduling team. A commercial promise should not depend on persuading an unrelated customer to surrender a slot it has already bought.

Include configuration and technical windows

A device’s apparent free hour may not be usable for the next customer if configuration work, checks or maintenance must occur first. Responsible specialists should establish those requirements. EASA’s FSTD material supports attention to configuration integrity and continuing capability. The schedule should reflect the assessed transition rather than assume instantaneous interchangeability. Protect technical windows and identify who may approve a proposed change. A centre that sells every visible hour can create a maintenance or support problem that later disrupts several customers together. The investor needs the capacity remaining after those obligations, not the gross hours in a calendar.

Report the quality of the booking book

Track completed sessions, cancellations, rebookings and capacity held under priority arrangements with consistent definitions. Explain what each measure says about revenue and future commitments. A high booking total can include sessions never delivered, while deliberate reserved capacity may support a valuable contract. Review the evidence before adding another device or accepting more framework customers. The practical decision is how to turn qualified equipment and staff into a dependable scheduling service. Clear allocation rules allow the facility to grow without repeatedly funding exceptions created by its own incompatible promises.

References
  1. FAA — National Simulator Program ↗
  2. EASA — FSTD configuration and continuing capability ↗