Products
MyAir.ID
The pilot's remote workplace outside the cockpit
Roster and its versions, acknowledgements, clearances, flight hours, documents, requests and approvals gathered in one working space. A simple interface resting on hard integration with several internal airline systems.
The airline's problem
The ground processes of flight crew are usually spread across several systems and channels.
The roster may sit in one system, orders for acknowledgement in a mailing list, flight-hour records with a separate department, medical dates in another loop, requests on paper, payslips in an HR portal.
The trouble appears at the joins. A roster change may be delivered and never read. A request may be filed outside the admissible window. A document may be formally valid and still fail the requirements of the country the next trip goes to.
Every such case calls for a manual check and a reconstruction of the history.
What the system does
MyAir.ID is the pilot’s ground workplace, bringing together the main service processes outside the cockpit.
The pilot sees the next trip with report time, departure and aircraft; the roster and the history of its changes as before and after; the version number and the delivery deadline.
Acknowledgement of an order is signed with an electronic signature that fixes the content of the document and the composition of the evidence.
Personal flight-hour limits are shown with their grounds, document validity is checked against the country of the trip, requests to planning carry quotas and submission windows, and approvals require a written answer on refusal.
Search works across the user’s own data and understands ordinary questions, such as «how much leave do I have» or «order 214».
The main difficulty of the product lies in integrating the sources and keeping the data consistent between them.
How it works
The path from source data to a specialist's decision
-
Data sources
Planning, HR, medical, training, documents and payroll data; each source works under its own exchange contract.
-
Processing
Data is brought into one picture of the employee: what changed, what requires action, by when and with what consequence.
-
Result
The pilot sees the trip card, roster changes as before and after, limits, deadlines and documents; each department sees its own part.
-
Specialist's decision
An acknowledgement is signed, a request follows its route, a decision returns to the person who raised it. Significant records stay unchanged.
Key capabilities
- Roster and its versions with control over the delivery deadline; a breach of the norm is recorded and does not block publication.
- Acknowledgement by electronic signature: the record cannot be altered, the same version cannot be signed twice, the evidence is preserved.
- Duty-time and flight-hour limits with their grounds, the date of consent and the last date on which consent may be withdrawn.
- Requests, planning enquiries and approvals: quotas, submission windows, refusal with a reason and a written answer from the manager.
- Personal search across the user’s own data.
- A night theme for early report times and night trips.
Video overview
Data and integrations
MyAir.ID generates no subject data of its own.
The roster arrives from the planning system, clearances from HR and medical systems, flight hours from records, training from the relevant system, documents from their registers, the payslip from payroll.
The task of the product is to gather that data into a consistent picture while preserving the owner and the status of each source.
Where a source is unavailable the system shows the last replica with a timestamp and marks the state of the source plainly. Unavailability is never replaced by an empty value or by stale data without warning.
The state of the exchanges is shown on a separate monitoring screen.
Methodology and regulatory basis
Norms are taken from the operator’s operations manual with the chapter and the grounds cited.
These may be the annual quota of leave requests, the minimum portion of annual leave, the period allowed for a medical examination or the deadline for delivering a roster change.
Values are held as settings with a change history and are amended without touching the code.
Significant records cannot be altered. A signature, a request or an approver’s decision is never edited; a correction creates a new record referring to the previous one.
Where the system stops
MyAir.ID displays data and provides working routes. It takes no subject decisions on behalf of the specialist departments.
Clearance, assignment and qualification remain the responsibility of the departments that issue them.
The system is no primary operational channel. A reserve call-out, for instance, may appear in MyAir.ID as duplicate information, while the operator’s established means of contact remains the primary one.
There is no summary readiness indicator for an employee. A percentage «readiness» would merge figures of different natures — a medical date, a document, a training item — and hide the specific ground for a restriction.
The electronic flight bag remains a separate loop. MyAir.ID works on the ground.
What the airline gets
The pilot gains one space for the main ground processes: roster, acknowledgements, limits, documents, requests and approvals.
Departments gain a verifiable history of actions: who acknowledged what and when, within what period a change was delivered, and where a norm was breached.
The acknowledgement report is exported together with the supporting evidence.