Dev:LH Core Admin-Carrier brands
The Carrier brands application allows administrators to manage airline carrier information within the system.
It ensures that:
•Airlines are correctly registered
•Operational and medical responsibilities are clearly defined
•Digital connectivity (B-Op) is transparent
•Code-sharing and ownership logic is properly maintained
•Service rules can be applied accurately per carrier
This module is primarily used by system administrators.
Application enables administrators to:
•Maintain airline master data
•Configure operational and medical ownership
•Manage digital integration (B-Op)
•Define brand structure
•Ensure service and compliance alignment
It forms a foundational layer of the entire operational ecosystem.
Carrier Overview
The Carrier Overview provides a structured list of all registered airline carriers.
It acts as the central starting point for managing carrier data.
What You See
A table containing:
Column Description
Airline Name Official airline name + logo
IATA Code 2-letter airline code
ICAO Code 3-letter airline code
Available Actions
➕Add New
A button at the top allows administrators to:
•Create a new airline entry
•Define its operational parameters
•Upload a logo
•Configure digital connection settings
🔍Search
A search field allows filtering by:
•Airline name
•IATA code
•ICAO code
This enables fast lookup in large carrier lists.
✏️Edit
Clicking a carrier opens the detailed configuration screen.
❌Delete (optional)
If enabled:
•Allows removal of a carrier
•Carrier cannot be deleted if it is authoritative MOC or has active dependencies
Carrier Detail Screen (Carrier Edit)
This screen allows administrators to configure the airline in detail.
General Information
Airline Name (required)
Official name of the carrier
Example: Lufthansa, Discover, SWISS Airlines
IATA Code (required)
Two-character airline code
Example: LH, LX, 4Y
ICAO Code (required)
Three-character airline code
Example: DLH, SWR, DSC
Upload Logo
Allows uploading a carrier logo.
Accepted formats:
•PNG
•JPEG
•SVG
The logo is displayed in overview tables and related screens.
Default Transport Type (required)
Defines the primary transport type for the carrier.
Example:
•Airplane
•(Future extension possible: Rail, Bus, etc.)
This supports intermodal logic.
Ownership Flag
Checkbox:
“Is owned (if not owned, this carrier can serve as codeshare partner)”
If checked:
•Carrier is considered part of the organization’s own operational group.
If unchecked:
•Carrier may act as a codeshare or external partner.
Authoritative Medical Operation Center
This section defines which Medical Operation Center (MOC) is responsible for this carrier.
Field:
•Operating Carrier (Search dropdown)
Purpose:
•Determines medical decision authority
•Defines escalation path
•Aligns compliance responsibility
This is especially relevant for:
•Fit-to-Fly decisions
•Medical clearance workflows
•STCR/WENOLL cases
B-Op Digital Connection (BOP Connection Placeholder)
This section shows the digital integration status between the carrier and the B-Op ecosystem.
B-Op Digital Connection Status
Displays:
•✅ Connected
•❌ Not connected
Color-coded for quick visibility.
This indicates whether the carrier is digitally integrated for:
•Case exchange
•Task synchronization
•Secure communication
•Service orchestration
Collaboration Model
Displays:
“Carrier Medical Operation Partnership” – Active (Yes/No)
This indicates whether the carrier participates in the standardized digital medical partnership model.
This affects:
•Data exchange depth
•Medical responsibility sharing
•Automated workflow capabilities