Role-based responsibility
Scope access by airline, base, crew group and data sensitivity. Separate creation, approval and independent review where required.
PLATFORM FOUNDATION
Shared software.
Separate airline environments.
A multi-airline product design with controlled configuration, clear data ownership and permissions that match operational responsibility.
DESIGNED TO SCALE WITHOUT BLURRING BOUNDARIES
Your operation.
Your configuration.
Each airline is intended to have its own operational environment, rule profiles, approvals, users and records. A new customer starts without another airline’s data.
Data separation is specified across records, files, search, background processing, exports, notifications and recovery. These controls require implementation and independent verification before operational use.
Consistent operational context
Clear time-zone labels, controlled calendar settings and consistent terminology across operational workflows. Display preferences do not change rule calculations.
Traceable records
Maintain version histories for documents, rule profiles and approvals. Apply retention policies and control access to exports.
INTEGRATIONS WITH A DEFINED CONTRACT
Connect systems.
Keep the source of truth clear.
Each integration requires agreed data ownership, authorised access, field mapping, authentication, reconciliation and error handling.
Commercial scheduleHR & trainingFliluText messaging & crew portalTransport & accommodation
The diagram shows planned integration categories. Connections depend on verified access and agreed specifications. APIs, security controls, hosting and service levels are defined and validated during implementation.
M01Airline administration
Manage company settings, operating bases, departments and delegated authority within each airline’s environment.
Controlled user onboarding and offboarding; role administration; airline-specific operating settings.
M18Documents & briefing
Give the right person the current document and preserve distribution evidence.
Controlled manuals; crew lists; duty briefings; amendment notifications and inspection evidence packs. Crew-related regulatory outputs require agreed data requirements and verified interfaces.
M20Workforce planning
See the gap between the operation you plan and the crew capacity available.
Initial views of crew supply, demand and qualification expiries; future scenarios for recruitment, attrition, promotion, fleet changes and training requirements.
M21Cost & operational insight
Distinguish operational activity, cost estimates and pay-related calculations, with traceable inputs.
Crew coverage; planned and actual duty and block times; notification acknowledgements; transport performance; initial cost exports. Detailed pay calculations and forecasting are planned extensions.
M22Platform & integration
Build a shared product without sharing one airline’s operational data with another.
Separate airline environments; access limited by role; audit trails; retention and recovery; versioned interface specifications. Third-party connections require verified access and agreed data mappings.
A CLEARER VIEW OF CREW OPERATIONS
Start with the whole picture.
Explore the modules, operational workflows and implementation approach behind Flilu.