Configuring Aircraft for the Charter Vendor Alliance
The customer can select specific aircraft or all aircraft to for which they would like to send data to the vendor. The grid displays specific information that will be sent for each aircraft.
The customer can choose to send “holes” in the schedule or the full aircraft “schedule."
In order for the aircraft to show up in the list it must be selected as a “charter aircraft.” This can be done by clicking “aircraft details” and checking the box in the aircraft profile.
In the Vendor Alliance Module, enter a number of days in the “Charter Days to Send” field. This field allows the user to control how many days forward the schedule is being sent to the selected Charter provider.
Related Articles
Vendor Alliance Activation Process
Once the Account Number has been added to the appropriate Vendor, within Vendor Alliance Module, the Status on the Configured Vendors Column will initially read Processing New Vendor. After the FOSVendorSyncService has ran and updated on the server ...Troubleshooting FAQs for FOS Vendor Alliance
1. On the FOS server, check under Administrative Tools → Services. There should be a service running called ‘FosVendorSyncService’. If not ‘Running’, right-click and ‘Start’ the service. 2. On the FOS server, check the config file to ensure it is ...Configuring Aircraft for the Maintenance Vendor Alliance
When the FOS Vendor Alliance is used for an aircraft maintenance interface, the Maintenance Interface section in the Aircraft Record will display the selection from the Vendor Alliance module. The “Import” options in the aircraft record are hidden. ...How to Rename the FOS Database in the Vendor Alliance config file
1. Start Windows component services Click on the Windows start menu button and search for "component services" 2. Stop vendor alliance window services Click on Services (Local) Click on FosVendorSyncService Click on the stop button at the top 3. ...Error: Charter Vendor update failed: XML Document must have a top level element.
Error: Charter Vendor update failed: XML Document must have a top level element. Solution: 1. Increase the number of dynamic ports using "netsh" command OR 2. Reboot the system