Some airlines have been paying their crews by the distance they’ve flown in a given month. Since it is very hard to keep up with these distances and count them up every month to predict how much you are going to get paid, people generally don’t follow up with the company’s payments and settle to be at their mercy.
The objective of the app is to read the month’s html roster file and automatically calculate the day and night kilometers, calculate the standby duty’s times (or respective kms), calculate the pay for training days, and write out a full earnings report.
The iPhone app must be self contained and do all calculations within the app (i.e calculations do not need internet reference, only the file is downloaded from roster website). There are two types of calculations in effect: personalized kilometers (saved for later use) and calculated kilometers (calculated form a coordinate database).
The iOS app must have a web view to access the crew’s roster and download the html code for interpretation. After its download, the code must access the file and interpret each flight’s origin, destination, flight number, time of departure and time of arrival, also start and end times for standby duty and training. The code, as it interprets each duty, writes out line by line each duty in a text file. This text file is then parsed to calculate the flight time of the flight and divide day and night times as per standard day-and-night division rules (these rules may define night as the time between 18:00 to 6:00 and day time between 6:00 to 18:00 or sunrise and sunset times may also be used, depending on the airline). After this calculation, day and night kilometers may be defined proportionally. This is important because night flight time is paid at a different rate than day time fights. The same rule is applied to national holiday and sunday flights. How much each of these kilometers are paid depends on airline policy. Some airlines apply a double rate for any flight time flown during sundays, national holidays or night flights. Some apply triple rates for night sunday and night holidays and double rates for night flights only. This choice must be available in the app configurations view.
To implement these calculations, the text file generated by the roster html file, must be read by the parser. As each line is read by the algorithm, another four fields are created: day kilometers, night kilometers, special kilometers (special kilometers mean tripled kilometers as in night holiday or night sunday flights) and the sum of a these three fields. The total kilometers to be paid is the sum of each of these three fields in a given month, as some airlines don’t pay special kilometers, this field will be calculated taking the configuration’s setting into account. The user will set wether his company pays special (tripled) kilometers or not at the configurations page view.
The app will have three basic views. A configuration view, where he will set his kilometer based pay and policy. A web view, so that the user may navigate to his roster html file for the app to make the read out. And a report view where his payments and kilometers are laid out, summed up and presented in a presentable and printable form view. All times are base time coordinated. This is also set on the configuration’s view.
Example roster html files are attached. Please, these are example files and should not be made public. Thank you.