Lukas Jankauskas

How to enable Advanced Cargo System?
Advanced Cargo System has 2 'enable' switches. Both are located in Orwell -> Management -> Airline Settings and should be visible to all staff with appropriate access.
The switches are located in 'Advanced VDS Settings' section:
Show Advanced Cargo Options - enables visibility of settings for staff to set up ACS. It does not activate in Phoenix and is invisible to pilots. This is the switch you should turn on if you want to set up ACS. If you are not interested - this switch should remain off, as you might get confused by additional options which do not apply to you. Enable Advanced Cargo - This switch must only be enabled after you finished the configuration of ACS as per this forum post. Once enabled, pilots will get to experience the ACS. Please note - existing bookings will not be affected. It will only apply to new bookings. How to configure Advanced Cargo System?
All steps listed are MANDATORY and must be fully complete for ACS to work. 
Ensure your cargo aircraft (ones which do not carry passengers) are in their own 'Aircraft Type'.
This is done via VDS -> Management -> Aircraft.
If you have a mixed fleet list (for example B747 passenger and freighter versions in one type, move the freighters to a new type using 'Add Aircraft Type' button. Give it a different name) Assign Fleet Type to your cargo fleets.
This is done via VDS -> Management -> Aircraft only. Expand fleet list of your cargo fleet and click 'Edit Aircraft Type'. In the window which opens, change the Fleet Type from PAX Only to Cargo Only. Be sure to repeat it for all your cargo types. Double-check and insert 'Max Cargo' and 'Max Container Units' for each of your cargo aircraft.
This is done via VDS -> Management -> Aircraft or importers. For VDS -> Expand your cargo fleet list and click Edit on each aircraft.
Max Cargo is the maximum value in kilograms only (no grams - i.e. full numbers -> 1500 is correct, 1.5 is not).
Max Container Units is a new entry. In positive integer only (1, 50, 1000 etc. 50.59 is incorrect) specify maximum available volume in aircraft. 
We leave up to you how to come up with the value. You can insert maximum number of ULDs aircraft can carry and call it a day. However, for maximum utilization and save you some headache later on when you want to create a pallet loads etc, try coming up with available floorspace and then construct your containers appropriately.
Repeat for all cargo aircraft. If you choose to use the importer to edit these numbers, please follow the importer documentation. Create Load Factor Presets
You must create at least one Load Factor Preset and declare it to be the Default
This is done via VDS -> Management -> Load Factors
Please check the note on the Load Factors page and create as many presets as you want. Please use unique names - they are not visible for pilots. All fields are required when creating Load Factor.
Load Factor presets allow you to limit how much cargo can be carried on a route, pair or from airport. This is particularly useful if you want to implement a limit on very long routes, where full load is not possible or to better simulate thinner routes. Customize Load Factor assignments.
This can be done via VDS. As mentioned - Load factors can be assigned on an airport level, pair level and route level. If no overrides are made, the Default will be used. The order of override is as follows - route -> pair -> airport -> system default.
If you choose to use the importer, please follow the importer documentation. Create Containers
This done in VDS -> Management -> Containers.
Check the note on the page and create as many as you want. All the fields, except notes, are required to create container. Assign Containers
This is done in VDS. Containers can be assigned on an airport, pair or route level, depending on your desires. The order of override is as follows - route -> pair -> airport. Enable Advanced Cargo Booking switch in Orwell -> Management -> VDS Settings.

Hi!
Soundpacks are configured by the Virtual Airline using Orwell -> Management -> Pegasus Sounds. 
To enable them, or set up a custom soundpack, as a pilot - login to Pegasus, navigate to settings.
In the 'Sounds' section, you can enable announcements set up by the VA, or set up your own - be sure to follow the 'Custom Soundpack Guide' provided if you go down that route.

Account merge feature is intended to be used by pilots who have multiple user accounts.
For example, I have 2 user accounts - one under a@domain.com, second - b@domain.com.
User a@domain.com has pilot accounts VAM0002, ABC1249.
User b@domain.com has pilot accounts VAM0004, DEF1587.
Instead of maintaining 2 accounts and 2 logins, I can opt to merge them into 1 login under same email.
 
How to merge 2 User Accounts?
Login using your 'main' account - main account is the one you wish to retain - in my example, it is a@domain.com. Navigate to My Settings -> Merge User Accounts Section Enter email address of the secondary account - this account will be merged into main account and will stop existing. In my example, I will put b@domain.com
Click 'Submit Merge Request' Login to the email of the secondary account (b@domain.com) and approve the merge. vAMSYS will merge the two accounts in under an hour. How does the Merge combine pilot accounts?
Depending on Virtual Airline Settings, few things may happen:
If you have 2 Pilot Accounts - 1 for each User (VAM0002 and VAM0004 in my example): If VA has 'Pilot Merge - Discard Previous Data' enabled:
All data from VAM0004 will be discarded; VAM0002 will remain. If VA has 'Pilot Merge - Discard Previous Data' disabled:
All data (bookings, PIREPs, Comments etc.) will be transferred from VAM0004 to to VAM0002 and VAM0004 will be deleted. If your 2 user accounts do not share pilot accounts with same VA:
Pilot account will be moved from one user, to the other. In my example - DEF1587 will move from user a@domain.com to b@domain.com. At the end of the merge, using the example above, I will no longer be able to login using b@domain.com - that user will be deleted.
My user a@domain.com will contain pilot accounts for VAM0002, ABC1249 and DEF1587.
 
Can Virtual Airline Merge the accounts for me?
No, Virtual Airline Staff do not have the ability to combine your user accounts.
They can, however, merge pilot accounts which belong to their VA between two users.
To do that, VA Staff with prerequisite permissions need to navigate to Orwell -> Pilots -> Merge Accounts and follow the instructions there.
If you are a VA Owner or Staff, do not use any of the merge options, else you will lose your staff permissions. Please contact us if you need to merge such account.

How to enable the system?
VA Owner or a member of Staff with Management access needs to navigate to Orwell => Management => Airline Options.
Scroll towards the end of the page where 'Miscellaneous Settings' are located.
Toggle 'Enable Claims System' switch if it is not in the 'on' position already.
Click Save.
How to access the system?
Once the Claim System is enabled, it can be accessed as follows:
Submissions by Pilots => Phoenix -> Flight Centre -> Claims Reviews by VA Staff with PIREP Review access => Orwell -> PIREPs & Liveries -> PIREP Claim Review How to make a Claim?
Claims can only be made by Pilots. One claim is for one flight.
If you want to claim multiple flights, you will need to submit the form for each flight.

In the claims page, on the right hand side is a form which needs to be submitted:
Departure Airport - 3 or 4 character IATA or ICAO code of the airport from which the claimed flight took off. Arrival Airport - 3 or 4 character IATA or ICAO code of the airport at which the claimed flight landed. Takeoff Date and Time - Time of takeoff, or as close to it as possible. Landing Date and Time - Time of landing, or as close to it as possible. Further, there are options to include 5 files and 3 links.
It is expected that pilots will use these options to attach proof of flight - screenshots of Pegasus, STKP, Volanta etc or links to VATSIM/IVAO statistic repositories.
What classifies as proof is up to each VA to decide and we hope they will publish guidelines for their pilots if they choose to enable this system.
Once all the fields are entered (all fields are required, except File and Link fields - please populate at least 1 of the 8 fields there) click 'Save'.
Page will reload and on the left hand side you will see your claim history:
Pending - claim has been submitted and is waiting review from the staff. Accepted - claim has been accepted and a PIREP has been created for you. Rejected - claim has been rejected and no PIREP has been created for you. If you feel you made a mistake with your claim and it has not been processed yet - you may click on the X button in the Previous Claims list. This will remove your claim.
How to Review Claims?
Orwell Claims page lists all pending claims and data which we think is relevant in processing a claim.
Claims are ordered in ascending order - i.e. oldest submitted claims are shown at the top (similar to PIREP review).
Staff Claims Dashboard:

Field information:
General Information: Name - Pilots Name Username - Pilot Username Departure - Departure Airport Name - ICAO/IATA Arrival - Arrival Airport Name - ICAO/IATA Pilot Claim History: Last 5 Claims - In descending order, last 5 claims made by pilot. Data: Departure - Arrival Airports | Claimed Hours | Departure Time | Status (not pictured) Last 5 Accepted Claims - In descending order, last 5 claims made by pilot. Data: Departure - Arrival Airports | Claimed Hours | Departure Time Last 5 Rejected Claims - In descending order, last 5 claims made by pilot. Data: Departure - Arrival Airports | Claimed Hours | Departure Time Submitted Proof: Files/Images - list of links to the files/images uploaded by pilot. Clicking will open the resource in new browser tab. Links - list of links to outside websites submitted by a pilot. Clicking will open the page in new browser tab. Computed Data: Pilot Estimated Time - how much time pilot is claiming. Difference in hours:minutes:seconds between Landing and Takeoff times. Pilot Average Time - Pilot's average time across all their PIREPs. Departure - Arrival Pair Average Time - Average time for this Departure-Arrival pair among all PIREPs of the VA. If VA Statistics for this pair does not exist (no flights have been made or the routing does not exist for your VA) it will show 0. Pilot Average Time for Same Pair - Average time for this Departure-Arrival pair among all PIREPs of the Pilot who made the claim. If Pilot has not made a flight for this pair before, it will show 0. Pilot Average Points = Pilot's average points across all their PIREPs. Departure-Arrival Pair Average Points - Average point for this Departure-Arrival pair among all PIREPs of the VA. If VA Statistics for this pair does not exist (no flights have been made or the routing does not exist for your VA) it will show 0. Pilot Average Points for Same Pair - Average points for this Departure-Arrival pair among all PIREPs of the Pilot who made the claim. If Pilot has not made a flight for this pair before, it will show 0. On Accept: Award Hours - how many hours should the manual PIREP have - default is Pilot Estimated Hours. Award Minutes - how many minutes should the manual PIREP have - default is Pilot Estimated Hours. Award Seconds - how many seconds should the manual PIREP have - default is Pilot Estimated Hours. Award Points - how many points should the manual PIREP have - default is Departure-Arrival Pair Average Points. Buttons:
Accept - Claim will be marked as 'Accepted', will disappear from Staff Claims list, manual PIREP will be created for the pilot automatically using the information provided in 'On Accept' section Reject - Claim will be marked as 'Rejected' and will disappear from Staff Claims list.  
FAQ:
Can VA Staff make a claim on behalf of pilot?
No. In this case, VA Staff should make use of the option available here  

This is no longer applicable. It has been superseded by PIREP Claims and Pilot Invite options available.
 
Follow these steps:
Compile the Pirep submissions.csv - you can download it from the question above. Note: You can open it in Excel, Google Sheets etc - be sure to save it as CSV before upload Fill in all the columns for each row pilot_id must contain pilot Username - for example VAM0005. Wrong entries include VAM 0005, vam0005 or lukas@vamsys.co.uk hours must include a numerical value - for example 2 or 1.5 or 0. Wrong entries include 'twenty', 15/3 etc. points must include a whole numerical value - for example 100 or 150 or 0. Wrong entries include fractional values such as 100.55 or 0.00 or 150.00 or words. bonus_points must include a whole numerical value - for example 100 or 150 or 0. Wrong entries include fractional values such as 100.55 or 0.00 or or 150.00 or words. Sanitise your data pilot_id - capital latters, no spaces. You can use excel formula in E2 such as this -> =UPPER(TRIM(A2)), and copy over the result from E2 to A2 then delete column E. Check that columns B, C and D contain numbers only - no letters, no spaces. Check instructions in step 2. Save as comma separated values - CSV Check data Open CSV in notepad and check - values should be separated by ',' there should be no "s or other artifacts or extraneous columns:
Upload file in Orwell -> Data -> Importers -> Data: PIREPs  
Each row in the CSV create a new 'Credit' PIREP for the pilot. There can be multiple rows for each Pilot.
Be very careful reuploading file in case of failure! You are very likely to cause duplicate entries which we will not be able to remove for you. If the importer failed - check all the steps again - you made a mistake. Once you fixed it, check your VA PIREP list and remove rows for which PIREPs got already created.