Improving company demand assignment at Passenger Services

We're replacing the former "Create Job" feature in your Passenger Services buildings with a more flexible and robust Company Collaboration system. This change simplifies how you share demand with partners, prevents issues related to automatically created, unoptimised micro-jobs and removes the requirement for partners to grant you Create Dispatch Plans privileges in your company.

Going forward, your Passenger Services building will no longer automatically create and dispatch jobs for you or your partners. Instead, it will assign the final leg's demand as a collaborative opportunity directly to the designated company.

When configuring a destination for your Passenger Services, select Company Collaboration and choose an active member of your partnership from the dropdown list. This demand will only be visible to the specified partner company and will appear as collaborative demand in their Demand lens. This means that they can combine it with other demand, route it efficiently, and dispatch full aircraft. This was previously possible on when the Internal Collaboration option was selected, which made the demand available to all members of the partnership.

Additionally, to prevent confusion and accidental transfers, any demand assigned via Company Collaboration is now "pinned" to the target company, meaning it won't accidentally be bundled into a partnership-wide asset transfer.

Other Improvements

• Data Migration: All existing Passenger Services configurations that used the old Create Job action have been automatically migrated to the new Company Collaboration action, and the company is now referenced by its permanent ID (UUID) instead of the ICAO code.
• Bug Fix: Addressed a critical bug that prevented you from accepting route jobs when a previous Passenger Services configuration was linked to an old, non-existent ICAO code.