Dev:LH Core Admin-Craft types
The Craft Types Management administration application allows administrators to manage aircraft models used within the system.
Aircraft types are relevant for:
•Service availability rules
•STCR and WENOLL compatibility
•Craft-specific limitations
•Operational planning
•Technical department coordination
•Seat configuration handling
Maintaining accurate craft data ensures correct service logic and operational compliance.
Why This Module Is Important
Aircraft type configuration directly affects:
•Service eligibility (e.g., STCR limitations)
•Oxygen installation compatibility
•Craft-type service exclusions
•Seat allocation logic
•Technical department routing
•Operational safety compliance
Without proper craft configuration:
•Services may be incorrectly assigned
•Technical teams may receive wrong instructions
•Capacity and seating conflicts may occur
•Regulatory compliance risks increase
Craft Types Overview Screen
This screen provides a structured list of all aircraft models configured in the system.
What Users Can See
A table listing all craft types with the following columns:
Column Description
Craft Model Name of the aircraft model (e.g., Boeing 737-700)
Craft Vendor Manufacturer (e.g., Boeing, Airbus)
Functional Capabilities
View Craft Types
Administrators can see all configured aircraft models in a structured list.
🔍Search
A search bar at the top-right allows filtering by:
•Craft Model
•Craft Vendor
This enables quick identification of aircraft types in large datasets.
➕Add New Craft Type
A clearly visible “Add New” button allows administrators to create a new aircraft model entry.
✏️Edit Craft Type
Each row contains a pencil icon (✏️) to edit the selected craft type.
❌Delete Craft Type
Each row contains a trash icon (🗑) to delete the selected craft type.
Before deletion:
•A confirmation popup must appear.
•User must explicitly confirm the action.
•Deletion should be restricted if the craft type is referenced in active configurations (optional safeguard depending on system logic).
Craft Edit Page
Objective
This screen allows administrators to:
•Create new aircraft models
•Modify existing aircraft models
•Maintain craft-specific service attributes
Fields
Craft Model
•Type: Text input
•Mandatory: Yes
•Example: “Airbus A321”
This represents the specific aircraft model.
Craft Vendor
•Type: Dropdown (required)
•Mandatory: Yes
Default options:
•Boeing
•Airbus
•Embraer
•Bombardier
The vendor list should be expandable if new manufacturers are added.
Dismantling
•Type: Checkbox (optional)
•Description: Indicates if the aircraft type is currently marked as dismantled.
If enabled:
•The craft type may be restricted from new service configurations.
•It may be excluded from operational availability rules.
Seats
•Type: Multi-select input (optional)
This allows administrators to define available seat configurations manually.
Functionality:
•Add seat labels manually (e.g., “1A”, “1B”, “1C”)
•Remove previously added seat entries
•Store as structured list
This supports:
•Escort seat allocation
•STCR positioning logic
•Special seating requirements
•Operational capacity validation
Craft Groups
The Craft Groups feature allows administrators to organize individual aircraft into logical groups based on registration codes.
This is particularly useful when:
•Certain service rules apply only to specific aircraft
•Technical limitations affect only part of a fleet
•Temporary operational restrictions apply
•Special configurations are needed for selected aircraft
•Not all aircraft of the same model behave identically
Craft groups provide a flexible layer between:
•Craft Model (e.g., Airbus A320)
•Individual aircraft (by registration code)
What Craft Groups Do
Administrators can:
•Create named groups of aircraft
•Assign individual aircraft (by registration number) to these groups
•Apply specific service or operational rules at group level
All aircraft that are not assigned to a specific group are automatically placed into the:
Standard Group
The Standard group acts as the default fallback.
This ensures:
•No aircraft remains unassigned
•Baseline service logic always applies
•Operational consistency is maintained
Craft Groups Overview Screen
Display
The screen shows:
Column Description
Group name Name of the craft group (e.g., Standard)
A default group named Standard is always present.
Add New Group
A visible “Add new group” button allows administrators to:
•Create a new craft group
•Define a meaningful group name
•Later assign individual aircraft registrations to it
Example group names:
•A320 High Density
•Long Haul Retrofit
•A340 Medical Config
•Temporary Cabin Layout
Actions
Save
•Saves changes to the craft type.
•Required field validation must be enforced:
•Craft Model must not be empty.
•Craft Vendor must be selected.
If validation fails:
•Clear error messages must be displayed.
Cancel Operation
If user clicks Cancel:
•A confirmation popup must appear.
•User must confirm leaving without saving.
•No changes are persisted unless explicitly saved.