https://wiki.kordeus.com/api.php?action=feedcontributions&feedformat=atom&user=Mionamilosevic 2026-07-08T01:28:17Z User contributions MediaWiki 1.42.3 https://wiki.kordeus.com/index.php?title=Dev:LH_MOC_Admin-Travel_services&diff=3289 2026-04-03T12:07:35Z

<p>Mionamilosevic: </p> <hr /> <div>The Travel Service Administration module is the central configuration area where all operational services that can be requested for a passenger are defined and managed.<br /> <br /> A Travel Service represents a concrete operational action related to a passenger’s journey.<br /> <br /> Examples include:<br /> <br /> •Wheelchair assistance<br /> <br /> •Stretcher transport (STCR)<br /> <br /> •Oxygen on board (POXY)<br /> <br /> •Escort services<br /> <br /> •Ambulance transport to/from airport<br /> <br /> •Medical device transport (CPAP/BIPAP)<br /> <br /> •Additional seating<br /> <br /> •Handling of medical baggage<br /> <br /> These services may require:<br /> <br /> •Medical approval<br /> <br /> •Operational approval<br /> <br /> •Ground handling coordination<br /> <br /> •Service delivery partner involvement<br /> <br /> •Task automation<br /> <br /> •Capacity checks<br /> <br /> The module defines '''how a service behaves in the system''', including:<br /> <br /> •Availability<br /> <br /> •Dependencies<br /> <br /> •Approval workflows<br /> <br /> •Automation rules<br /> <br /> •Service visibility<br /> <br /> The '''Travel Service Administration module''' defines the operational backbone of passenger assistance and medical service handling.<br /> <br /> It controls:<br /> <br /> •how services appear<br /> <br /> •who can request them<br /> <br /> •how they trigger other services<br /> <br /> •how approvals work<br /> <br /> •how operational workflows are automated<br /> <br /> Together with:<br /> <br /> •'''SPFT'''<br /> <br /> •'''Service Delivery Partners'''<br /> <br /> •'''Travel Partners'''<br /> <br /> this module forms the core system for managing passenger service operations.<br /> [[File:Travel Services Overview.png|none|thumb]]<br /> <br /> == Base data ==<br /> The '''Base Data''' section defines the '''core behavior of a travel service''' and controls:<br /> <br /> •where the service can be used (segment / port / flight / aircraft)<br /> <br /> •who can request it<br /> <br /> •how it behaves in workflows<br /> <br /> •which additional configuration pages become available<br /> <br /> A key part of this section is the '''Service Network Compatibility catalogue''', which drives '''availability logic and UI behavior across the system'''.<br /> <br /> === '''Member Service Requestability''' ===<br /> <br /> <br /> Defines who can request the service:<br /> {| class=&quot;wikitable&quot;<br /> |+<br /> !Option<br /> !Effect<br /> |-<br /> |Passenger<br /> |Available in PAX portal<br /> |-<br /> |Travel partner<br /> |Available or external partners<br /> |-<br /> |Internal<br /> |Only internal users can add<br /> |}<br /> <br /> === '''Service Network Compatibility (Catalogue-Driven Logic)''' ===<br /> <br /> <br /> This section defines '''system-level characteristics of the service''', based on a '''catalogue configuration'''.<br /> <br /> These values are '''not manually editable''', but are derived from the selected:<br /> <br /> •'''Global Travel Service Binding'''<br /> <br /> •'''Service Group Key'''<br /> <br /> They determine:<br /> <br /> •how the service behaves<br /> <br /> •where it can be delivered<br /> <br /> •which configuration options are available<br /> <br /> <br /> '''Catalogue Flags''' <br /> <br /> The following flags define '''service capabilities and restrictions''':<br /> <br /> <br /> '''On Segment Direct PAX Service Delivery'''<br /> <br /> '''Value (example):''' No<br /> <br /> '''Meaning:'''<br /> <br /> Defines whether the service can be delivered '''directly to the passenger during a flight segment'''.<br /> <br /> '''''If Yes:'''''<br /> <br /> •Service can be delivered '''on board'''<br /> <br /> •Enables:<br /> <br /> •segment-level availability configuration<br /> <br /> •segment-based automation<br /> <br /> •Related pages enabled:<br /> <br /> •'''Segment Availability'''<br /> <br /> •Typical examples:<br /> <br /> •onboard oxygen<br /> <br /> •onboard assistance<br /> <br /> '''''If No:'''''<br /> <br /> •Service cannot be delivered onboard<br /> <br /> •Segment-related configuration is '''restricted or irrelevant'''<br /> <br /> <br /> '''At-Port Direct PAX Service Delivery'''<br /> <br /> '''Value (example):''' Yes<br /> <br /> '''Meaning:'''<br /> <br /> Defines whether the service can be delivered '''at airport locations (departure, arrival, transfer)'''.<br /> <br /> '''''If Yes:'''''<br /> <br /> •Service is available at:<br /> <br /> •departure airport<br /> <br /> •arrival airport<br /> <br /> •transfer airport<br /> <br /> •Enables:<br /> <br /> •'''At Port Availability page'''<br /> <br /> •port-based restrictions<br /> <br /> •Typical examples:<br /> <br /> •wheelchair assistance<br /> <br /> •ambulance services<br /> <br /> •escort services<br /> <br /> '''''If No:'''''<br /> <br /> •Service cannot be delivered at airport level<br /> <br /> •Port configuration is disabled<br /> <br /> <br /> '''Describes General Medical Condition'''<br /> <br /> '''Value (example):''' No<br /> <br /> '''Meaning:'''<br /> <br /> Defines whether the service represents a '''medical condition classification''' rather than an operational service.<br /> <br /> '''''If Yes:'''''<br /> <br /> •Service is used for:<br /> <br /> •classification (e.g., MEDA)<br /> <br /> •Enables:<br /> <br /> •medical workflows<br /> <br /> •Does NOT represent a physical service<br /> <br /> '''''If No:'''''<br /> <br /> •Service is treated as an '''operational service'''<br /> <br /> <br /> '''Trip Extra Service'''<br /> <br /> '''Value (example):''' No<br /> <br /> '''Meaning:'''<br /> <br /> Defines whether the service applies to the '''entire journey (trip-level)''' rather than individual segments.<br /> <br /> '''''If Yes:'''''<br /> <br /> •Service applies to:<br /> <br /> •whole itinerary<br /> <br /> •Not tied to:<br /> <br /> •specific segments<br /> <br /> •Example:<br /> <br /> •special handling across entire trip<br /> <br /> '''''If No:'''''<br /> <br /> •Service is applied per:<br /> <br /> •segment or port<br /> <br /> <br /> '''Segment Transport Type Service'''<br /> <br /> '''Value (example):''' No<br /> <br /> '''Meaning:'''<br /> <br /> Defines whether the service is tied to '''transport type (air, rail, bus, etc.)'''<br /> <br /> '''''If Yes:'''''<br /> <br /> •Service depends on:<br /> <br /> •transport type of segment<br /> <br /> •Enables:<br /> <br /> •transport-specific filtering<br /> <br /> '''''If No:'''''<br /> <br /> •Service is independent of transport type<br /> <br /> <br /> '''Is Info Service'''<br /> <br /> '''Value (example):''' No<br /> <br /> '''Meaning:'''<br /> <br /> Defines whether the service is '''informational only'''.<br /> <br /> '''''If Yes:'''''<br /> <br /> •Service:<br /> <br /> •does NOT trigger delivery<br /> <br /> •does NOT require execution<br /> <br /> •Used for:<br /> <br /> •displaying information<br /> <br /> •No tasks or delivery partners triggered<br /> <br /> '''''If No:'''''<br /> <br /> •Service is operational and actionable<br /> <br /> === '''Service Availability Limitations''' ===<br /> <br /> <br /> Defines '''where and under which conditions''' the service can be used.<br /> <br /> These settings directly control:<br /> <br /> •which configuration pages are visible<br /> <br /> •how the service is filtered in workflows<br /> <br /> <br /> '''Limited to Used Craft Type on Segment'''<br /> <br /> '''''If enabled:'''''<br /> <br /> •Service is restricted to specific aircraft types<br /> <br /> •Enables:<br /> <br /> •'''Craft Availability page'''<br /> <br /> •Example:<br /> <br /> •stretcher only available on widebody aircraft<br /> <br /> '''''If disabled:'''''<br /> <br /> •Service available for all aircraft types<br /> <br /> <br /> '''Limited Availability by Port'''<br /> <br /> '''''If enabled:'''''<br /> <br /> •Service is restricted to selected airports<br /> <br /> •Enables:<br /> <br /> •'''At Port Availability page'''<br /> <br /> •Requires:<br /> <br /> •At-Port Direct PAX Service Delivery = '''Yes'''<br /> <br /> '''''If disabled:'''''<br /> <br /> •Service available at all ports<br /> <br /> <br /> '''Limited Availability by Segment'''<br /> <br /> '''''If enabled:'''''<br /> <br /> •Service restricted to specific routes or segments<br /> <br /> •Enables:<br /> <br /> •'''Segment Availability page'''<br /> <br /> '''''If disabled:'''''<br /> <br /> •Service available across all segments<br /> <br /> <br /> '''Limited Availability by Flight Number'''<br /> <br /> '''''If enabled:'''''<br /> <br /> •Service limited to specific flight numbers<br /> <br /> •Enables:<br /> <br /> •'''Flight Number Availability page'''<br /> <br /> '''''If disabled:'''''<br /> <br /> •Service not restricted by flight<br /> <br /> <br /> '''Vessel Manipulation Travel Service'''<br /> <br /> '''''If enabled:'''''<br /> <br /> •Service involves '''physical aircraft manipulation'''<br /> <br /> Examples:<br /> <br /> •stretcher mounting<br /> <br /> •seat removal<br /> <br /> •equipment installation<br /> <br /> '''Enables:'''<br /> <br /> •timing logic in:<br /> <br /> •Service Tree Creation<br /> <br /> •operational preparation tasks<br /> <br /> <br /> '''Enforce Mandatory Fields for this Service on Portal'''<br /> <br /> '''''If enabled:'''''<br /> <br /> •Passenger or agent must fill required fields before submitting request<br /> <br /> Examples:<br /> <br /> •medical details<br /> <br /> •equipment requirements<br /> <br /> '''''If disabled:'''''<br /> <br /> •fields remain optional<br /> <br /> == '''Dependency Logic''' ==<br /> The system behavior depends on combined conditions:<br /> <br /> '''Example 1'''<br /> <br /> '''At-Port Direct PAX Service Delivery = Yes'''<br /> <br /> AND<br /> <br /> '''Limited Availability by Port = Enabled'''<br /> <br /> ➡ Result:<br /> <br /> •'''At Port Availability page becomes visible'''<br /> <br /> •Service can be configured per airport<br /> <br /> <br /> '''Example 2'''<br /> <br /> '''On Segment Direct PAX Service Delivery = Yes'''<br /> <br /> AND<br /> <br /> '''Limited Availability by Segment = Enabled'''<br /> <br /> ➡ Result:<br /> <br /> •'''Segment Availability page becomes visible'''<br /> <br /> •Service can be configured per route<br /> <br /> <br /> '''Example 3'''<br /> <br /> '''Limited to Used Craft Type on Segment = Enabled'''<br /> <br /> ➡ Result:<br /> <br /> •'''Craft Availability page becomes visible'''<br /> <br /> •Service limited by aircraft<br /> <br /> <br /> '''Example 4'''<br /> <br /> '''Is Info Service = Yes'''<br /> <br /> ➡ Result:<br /> <br /> •No:<br /> <br /> •delivery partner assignment<br /> <br /> •operational tasks<br /> <br /> •Used only for:<br /> <br /> •display / informational purposes<br /> <br /> <br /> '''Example 5'''<br /> <br /> '''Describes General Medical Condition = Yes'''<br /> <br /> ➡ Result:<br /> <br /> •Service used in:<br /> <br /> •medical classification<br /> <br /> •Impacts:<br /> <br /> •medical approval workflows<br /> <br /> •Not treated as operational service<br /> <br /> === '''Internal Service Process Flow Type (SPFT)''' ===<br /> Defines which workflow logic applies.<br /> <br /> Take MEDA as example<br /> <br /> Controls:<br /> <br /> •approval flows<br /> <br /> •task generation<br /> <br /> •communication templates<br /> <br /> === '''Minimum Connection Times''' ===<br /> Defines minimum required time between segments.<br /> <br /> Used for:<br /> <br /> •operational feasibility checks<br /> <br /> •service validation<br /> <br /> === '''Insecure Handling Advice Communication''' ===<br /> Defines fallback communication channels:<br /> <br /> •email recipients<br /> <br /> •telex recipients<br /> <br /> Used when:<br /> <br /> •digital delivery is not available<br /> [[File:TS base data I.png|none|thumb]]<br /> <br /> <br /> == '''Service Tree Creation''' ==<br /> Defines '''dependencies and relationships between services'''.<br /> <br /> This allows services to automatically trigger or recommend other services.<br /> <br /> '''Service Ordering'''<br /> <br /> Defines which services should be suggested when another service is requested.<br /> <br /> Example:<br /> <br /> Requesting '''STCR (Stretcher)''' automatically suggests:<br /> <br /> •Ambulance transport<br /> <br /> •Escort service<br /> <br /> •Medical oxygen<br /> <br /> '''Force Option'''<br /> <br /> If enabled, the suggested service is '''automatically added'''.<br /> <br /> If disabled, the user can accept or reject the suggestion.<br /> <br /> '''Backend Service Dependency'''<br /> <br /> Defines automatic service creation in backend workflows.<br /> <br /> Example:<br /> <br /> When a '''Stretcher request''' is created:<br /> <br /> Automatically add:<br /> <br /> •Stretcher mounting<br /> <br /> •Stretcher dismantling<br /> <br /> These services are invisible to the passenger.<br /> <br /> '''Vessel Manipulation Service'''<br /> <br /> Defines services that require preparation work on the aircraft.<br /> <br /> Examples:<br /> <br /> •stretcher mounting<br /> <br /> •equipment installation<br /> <br /> •seat removal<br /> <br /> '''Timing Options'''<br /> <br /> Defines when preparation must occur:<br /> {| class=&quot;wikitable&quot;<br /> |'''Option'''<br /> |'''Description'''<br /> |-<br /> |Before segment starts<br /> |preparation before flighr departure<br /> |-<br /> |After segment end<br /> |post-flight removal<br /> |}<br /> [[File:TS service tree creation I.png|none|thumb]]<br /> <br /> <br /> == '''Port Delivery''' ==<br /> The '''Port Delivery page''' defines '''where and how a service is delivered at airport level (ports)''' and '''which service delivery partners are responsible'''.<br /> <br /> This page is only relevant when the service is:<br /> <br /> •'''At-Port Direct PAX Service Delivery = Yes''' ''(from catalogue)''<br /> <br /> •AND optionally '''Limited availability by Port = enabled''' ''(from Base Data)''<br /> <br /> It allows administrators to:<br /> <br /> •define at which ports the service is available<br /> <br /> •assign responsible delivery partners<br /> <br /> •define communication fallback (insecure communication)<br /> <br /> •configure capacity restrictions per partner<br /> <br /> ''This page is '''conditionally available''' based on Base Data settings''<br /> <br /> === '''Direct PAX Service Deliverability at Port''' ===<br /> '''Purpose'''<br /> <br /> Defines '''when during the journey''' the service is delivered at port level.<br /> <br /> <br /> '''Options'''<br /> <br /> '''Deliverable during embarkation on first segment'''<br /> <br /> •Service delivered at '''departure airport'''<br /> <br /> •Example:<br /> <br /> •wheelchair at check-in<br /> <br /> •stretcher boarding preparation<br /> <br /> <br /> '''Deliverable during transfer between segments'''<br /> <br /> •Service delivered during '''transfer at connecting airports'''<br /> <br /> •Example:<br /> <br /> •escort during transfer<br /> <br /> •medical assistance between flights<br /> <br /> <br /> '''Deliverable during disembarkation from last segment'''<br /> <br /> •Service delivered at '''arrival airport'''<br /> <br /> •Example:<br /> <br /> •wheelchair on arrival<br /> <br /> •ambulance pick-up<br /> <br /> <br /> '''Behavior'''<br /> <br /> •Multiple options can be selected<br /> <br /> •Defines '''when service delivery partners are triggered'''<br /> <br /> •Directly impacts:<br /> <br /> •task creation<br /> <br /> •partner notifications<br /> <br /> •workflow timing<br /> <br /> === '''Ports Where Service is Available to PAX''' ===<br /> Defines '''where the service is operationally available''' and '''who delivers it'''.<br /> <br /> '''Global Availability Toggle'''<br /> <br /> '''Checkbox:'''<br /> <br /> '''“This service is generally available at all ports”'''<br /> <br /> '''If ENABLED'''<br /> <br /> •Service is available '''globally'''<br /> <br /> •Only '''exceptions (exclusions)''' are configured below<br /> <br /> •Table acts as: '''restriction list''' not a whitelist<br /> <br /> <br /> '''If DISABLED'''<br /> <br /> •Service is available '''only at listed ports'''<br /> <br /> Table acts as: '''explicit allow-list'''<br /> <br /> <br /> '''Add Port Configuration'''<br /> <br /> '''Fields'''<br /> <br /> '''Add known port'''<br /> <br /> Select airport (e.g., FRA, GVA)<br /> <br /> '''Add known service delivery partner'''<br /> <br /> Assign delivery partner responsible at that port<br /> <br /> Examples: Swissport, Fraport, Handling agents<br /> <br /> <br /> '''Unavailable at this port'''<br /> <br /> Marks service as '''not available''' at selected port<br /> <br /> Used when: global availability is enabled but specific ports must be excluded.<br /> <br /> <br /> '''Port Configuration Table'''<br /> {| class=&quot;wikitable&quot;<br /> |+<br /> !Column<br /> !Description<br /> |-<br /> |Available at port<br /> |Airport code<br /> |-<br /> |Authorized service delivery partner (''defines who is allowed to deliver the service at that port and who will receive tasks and notifications'')<br /> |Assigned partners<br /> |-<br /> |Insecure COM (''defines fallback communication channel and is used when no digital integration exists or communication must still be ensured)''<br /> |Fallback communication channels<br /> |-<br /> |Capacity resriction by partner (''defines operational limits such as maximum concurrent services, partner-specific constraints'')<br /> |Operational limits<br /> |}<br /> [[File:TS port availability I.png|none|thumb]]<br /> <br /> == '''Segment Availability''' ==<br /> The Segment Availability page defines on which flight segments a service can be delivered and under which routing conditions it is allowed or restricted.<br /> <br /> This page is relevant when the service is:<br /> <br /> ✔ On Segment Direct PAX Service Delivery = Yes ''(from catalogue)''<br /> <br /> AND optionally<br /> <br /> ✔ Limited availability by Segment = enabled ''(from Base Data)''<br /> <br /> It allows administrators to:<br /> <br /> define allowed or restricted route combinations (Departure → Destination)<br /> <br /> control service availability per flight segment<br /> <br /> override default behavior using inclusion/exclusion logic<br /> <br /> == '''Flight Number Availability''' ==<br /> Defines availability of a service for specific flight numbers or flight plans.<br /> <br /> This is the most granular restriction layer.<br /> <br /> Dependency<br /> <br /> Visible only if:<br /> <br /> ✔ Limited availability by flight number = enabled ''(Base Data)''<br /> <br /> Ruleset Table<br /> <br /> Defines allowed or restricted flights.<br /> <br /> allow-list OR exception list (same pattern as Segment)<br /> <br /> Used when:<br /> <br /> service differs per airline / route / regulation<br /> [[File:TS flight number availability I.png|none|thumb]]<br /> <br /> == '''Craft Type Availability''' ==<br /> Defines on which aircraft types the service is possible.<br /> <br /> Visible only if:<br /> <br /> ✔ Limited to used craft type on segment = enabled<br /> <br /> General Availability<br /> <br /> Checkbox This service is generally available to all crafts<br /> <br /> Behavior<br /> <br /> ✔ Enabled<br /> <br /> ➡️ All aircraft allowed (exceptions possible)<br /> <br /> ❌ Disabled<br /> <br /> ➡️ Only listed aircraft allowed<br /> <br /> Supported Craft Types<br /> <br /> Fields<br /> {| class=&quot;wikitable&quot;<br /> |+<br /> !Field<br /> !Description<br /> |-<br /> |Supported craft type<br /> |Aircraft (A350, A320, etc.)<br /> |-<br /> |Craft subgroup type<br /> |Category (Standard, etc.)<br /> |}<br /> Additional Option<br /> <br /> Unavailable for this craft<br /> <br /> ➡️ Marks aircraft as excluded<br /> <br /> Triggered by:<br /> <br /> ✔ '''SPFT = MEDA'''<br /> <br /> == '''Medical Approval''' ==<br /> Defines how medical approval is handled for the service.<br /> <br /> Used when:<br /> <br /> service requires medical validation<br /> <br /> passenger condition must be assessed<br /> <br /> Medical Approval Process<br /> <br /> Options<br /> <br /> Force free text entry for approval<br /> <br /> '''Force free text entry for approval'''<br /> <br /> ✔ When enabled:<br /> <br /> Doctor MUST enter explanation when approving<br /> <br /> ❌ When disabled:<br /> <br /> Approval can be done without comment<br /> <br /> '''Allow free text for request of more information'''<br /> <br /> ✔ When enabled:<br /> <br /> Doctor can send custom clarification request<br /> <br /> ❌ When disabled:<br /> <br /> Only predefined actions can be used<br /> <br /> '''Force free text info for denial reason'''<br /> <br /> ✔ When enabled:<br /> <br /> Doctor MUST explain rejection<br /> <br /> ❌ When disabled:<br /> <br /> Rejection can be done without explanation<br /> <br /> <br /> Typical Medical Actions Defines predefined medical responses that doctors can use as one-click actions.<br /> <br /> These actions:<br /> <br /> standardize communication<br /> <br /> reduce manual typing<br /> <br /> speed up approval process<br /> <br /> '''Add new default medical action'''<br /> <br /> ➡️ Opens form to create a predefined response<br /> <br /> A Typical Medical Action (Creation Form) Defines a single reusable medical response used by doctors.<br /> <br /> <br /> '''Typical reply (text input)'''<br /> <br /> Whenever this service is requested with a doctor this shall be typical reply *<br /> <br /> Main content of the response<br /> <br /> Used in communication / decision<br /> <br /> '''Action Type (radio buttons)'''<br /> <br /> Defines how the response behaves in workflow:<br /> <br /> Options<br /> <br /> '''Is a conditional approval reason'''<br /> <br /> ➡️ Used when:<br /> <br /> service is approved<br /> <br /> BUT with conditions<br /> <br /> Example:<br /> <br /> “Approved if oxygen is provided”<br /> <br /> '''Is a request for more information'''<br /> <br /> ➡️ Used when:<br /> <br /> more medical data is required<br /> <br /> Example:<br /> <br /> “Please provide updated medical report”<br /> <br /> '''Is a typical denial reason'''<br /> <br /> ➡️ Used when:<br /> <br /> service is rejected<br /> <br /> Example:<br /> <br /> “Passenger not fit to fly”<br /> <br /> [[File:TS medical approval I.png|none|thumb]]<br /> <br /> == Related articles ==<br /> [[Dev:LH MOC Admin-Travel services Translations|Translations]]</div>

Mionamilosevic https://wiki.kordeus.com/index.php?title=File:TS_flight_number_availability_I.png&diff=3288 2026-04-03T12:06:19Z

<p>Mionamilosevic: </p> <hr /> <div>TS flight number availability I</div>

Mionamilosevic https://wiki.kordeus.com/index.php?title=File:TS_medical_approval_I.png&diff=3287 2026-04-03T12:05:18Z

<p>Mionamilosevic: </p> <hr /> <div>TS medical approval</div>

Mionamilosevic https://wiki.kordeus.com/index.php?title=Dev:LH_MOC_Admin-Travel_services&diff=3286 2026-04-03T11:33:15Z

<p>Mionamilosevic: </p> <hr /> <div>The Travel Service Administration module is the central configuration area where all operational services that can be requested for a passenger are defined and managed.<br /> <br /> A Travel Service represents a concrete operational action related to a passenger’s journey.<br /> <br /> Examples include:<br /> <br /> •Wheelchair assistance<br /> <br /> •Stretcher transport (STCR)<br /> <br /> •Oxygen on board (POXY)<br /> <br /> •Escort services<br /> <br /> •Ambulance transport to/from airport<br /> <br /> •Medical device transport (CPAP/BIPAP)<br /> <br /> •Additional seating<br /> <br /> •Handling of medical baggage<br /> <br /> These services may require:<br /> <br /> •Medical approval<br /> <br /> •Operational approval<br /> <br /> •Ground handling coordination<br /> <br /> •Service delivery partner involvement<br /> <br /> •Task automation<br /> <br /> •Capacity checks<br /> <br /> The module defines '''how a service behaves in the system''', including:<br /> <br /> •Availability<br /> <br /> •Dependencies<br /> <br /> •Approval workflows<br /> <br /> •Automation rules<br /> <br /> •Service visibility<br /> <br /> The '''Travel Service Administration module''' defines the operational backbone of passenger assistance and medical service handling.<br /> <br /> It controls:<br /> <br /> •how services appear<br /> <br /> •who can request them<br /> <br /> •how they trigger other services<br /> <br /> •how approvals work<br /> <br /> •how operational workflows are automated<br /> <br /> Together with:<br /> <br /> •'''SPFT'''<br /> <br /> •'''Service Delivery Partners'''<br /> <br /> •'''Travel Partners'''<br /> <br /> this module forms the core system for managing passenger service operations.<br /> [[File:Travel Services Overview.png|none|thumb]]<br /> <br /> == Base data ==<br /> The '''Base Data''' section defines the '''core behavior of a travel service''' and controls:<br /> <br /> •where the service can be used (segment / port / flight / aircraft)<br /> <br /> •who can request it<br /> <br /> •how it behaves in workflows<br /> <br /> •which additional configuration pages become available<br /> <br /> A key part of this section is the '''Service Network Compatibility catalogue''', which drives '''availability logic and UI behavior across the system'''.<br /> <br /> === '''Member Service Requestability''' ===<br /> <br /> <br /> Defines who can request the service:<br /> {| class=&quot;wikitable&quot;<br /> |+<br /> !Option<br /> !Effect<br /> |-<br /> |Passenger<br /> |Available in PAX portal<br /> |-<br /> |Travel partner<br /> |Available or external partners<br /> |-<br /> |Internal<br /> |Only internal users can add<br /> |}<br /> <br /> === '''Service Network Compatibility (Catalogue-Driven Logic)''' ===<br /> <br /> <br /> This section defines '''system-level characteristics of the service''', based on a '''catalogue configuration'''.<br /> <br /> These values are '''not manually editable''', but are derived from the selected:<br /> <br /> •'''Global Travel Service Binding'''<br /> <br /> •'''Service Group Key'''<br /> <br /> They determine:<br /> <br /> •how the service behaves<br /> <br /> •where it can be delivered<br /> <br /> •which configuration options are available<br /> <br /> <br /> '''Catalogue Flags''' <br /> <br /> The following flags define '''service capabilities and restrictions''':<br /> <br /> <br /> '''On Segment Direct PAX Service Delivery'''<br /> <br /> '''Value (example):''' No<br /> <br /> '''Meaning:'''<br /> <br /> Defines whether the service can be delivered '''directly to the passenger during a flight segment'''.<br /> <br /> '''''If Yes:'''''<br /> <br /> •Service can be delivered '''on board'''<br /> <br /> •Enables:<br /> <br /> •segment-level availability configuration<br /> <br /> •segment-based automation<br /> <br /> •Related pages enabled:<br /> <br /> •'''Segment Availability'''<br /> <br /> •Typical examples:<br /> <br /> •onboard oxygen<br /> <br /> •onboard assistance<br /> <br /> '''''If No:'''''<br /> <br /> •Service cannot be delivered onboard<br /> <br /> •Segment-related configuration is '''restricted or irrelevant'''<br /> <br /> <br /> '''At-Port Direct PAX Service Delivery'''<br /> <br /> '''Value (example):''' Yes<br /> <br /> '''Meaning:'''<br /> <br /> Defines whether the service can be delivered '''at airport locations (departure, arrival, transfer)'''.<br /> <br /> '''''If Yes:'''''<br /> <br /> •Service is available at:<br /> <br /> •departure airport<br /> <br /> •arrival airport<br /> <br /> •transfer airport<br /> <br /> •Enables:<br /> <br /> •'''At Port Availability page'''<br /> <br /> •port-based restrictions<br /> <br /> •Typical examples:<br /> <br /> •wheelchair assistance<br /> <br /> •ambulance services<br /> <br /> •escort services<br /> <br /> '''''If No:'''''<br /> <br /> •Service cannot be delivered at airport level<br /> <br /> •Port configuration is disabled<br /> <br /> <br /> '''Describes General Medical Condition'''<br /> <br /> '''Value (example):''' No<br /> <br /> '''Meaning:'''<br /> <br /> Defines whether the service represents a '''medical condition classification''' rather than an operational service.<br /> <br /> '''''If Yes:'''''<br /> <br /> •Service is used for:<br /> <br /> •classification (e.g., MEDA)<br /> <br /> •Enables:<br /> <br /> •medical workflows<br /> <br /> •Does NOT represent a physical service<br /> <br /> '''''If No:'''''<br /> <br /> •Service is treated as an '''operational service'''<br /> <br /> <br /> '''Trip Extra Service'''<br /> <br /> '''Value (example):''' No<br /> <br /> '''Meaning:'''<br /> <br /> Defines whether the service applies to the '''entire journey (trip-level)''' rather than individual segments.<br /> <br /> '''''If Yes:'''''<br /> <br /> •Service applies to:<br /> <br /> •whole itinerary<br /> <br /> •Not tied to:<br /> <br /> •specific segments<br /> <br /> •Example:<br /> <br /> •special handling across entire trip<br /> <br /> '''''If No:'''''<br /> <br /> •Service is applied per:<br /> <br /> •segment or port<br /> <br /> <br /> '''Segment Transport Type Service'''<br /> <br /> '''Value (example):''' No<br /> <br /> '''Meaning:'''<br /> <br /> Defines whether the service is tied to '''transport type (air, rail, bus, etc.)'''<br /> <br /> '''''If Yes:'''''<br /> <br /> •Service depends on:<br /> <br /> •transport type of segment<br /> <br /> •Enables:<br /> <br /> •transport-specific filtering<br /> <br /> '''''If No:'''''<br /> <br /> •Service is independent of transport type<br /> <br /> <br /> '''Is Info Service'''<br /> <br /> '''Value (example):''' No<br /> <br /> '''Meaning:'''<br /> <br /> Defines whether the service is '''informational only'''.<br /> <br /> '''''If Yes:'''''<br /> <br /> •Service:<br /> <br /> •does NOT trigger delivery<br /> <br /> •does NOT require execution<br /> <br /> •Used for:<br /> <br /> •displaying information<br /> <br /> •No tasks or delivery partners triggered<br /> <br /> '''''If No:'''''<br /> <br /> •Service is operational and actionable<br /> <br /> === '''Service Availability Limitations''' ===<br /> <br /> <br /> Defines '''where and under which conditions''' the service can be used.<br /> <br /> These settings directly control:<br /> <br /> •which configuration pages are visible<br /> <br /> •how the service is filtered in workflows<br /> <br /> <br /> '''Limited to Used Craft Type on Segment'''<br /> <br /> '''''If enabled:'''''<br /> <br /> •Service is restricted to specific aircraft types<br /> <br /> •Enables:<br /> <br /> •'''Craft Availability page'''<br /> <br /> •Example:<br /> <br /> •stretcher only available on widebody aircraft<br /> <br /> '''''If disabled:'''''<br /> <br /> •Service available for all aircraft types<br /> <br /> <br /> '''Limited Availability by Port'''<br /> <br /> '''''If enabled:'''''<br /> <br /> •Service is restricted to selected airports<br /> <br /> •Enables:<br /> <br /> •'''At Port Availability page'''<br /> <br /> •Requires:<br /> <br /> •At-Port Direct PAX Service Delivery = '''Yes'''<br /> <br /> '''''If disabled:'''''<br /> <br /> •Service available at all ports<br /> <br /> <br /> '''Limited Availability by Segment'''<br /> <br /> '''''If enabled:'''''<br /> <br /> •Service restricted to specific routes or segments<br /> <br /> •Enables:<br /> <br /> •'''Segment Availability page'''<br /> <br /> '''''If disabled:'''''<br /> <br /> •Service available across all segments<br /> <br /> <br /> '''Limited Availability by Flight Number'''<br /> <br /> '''''If enabled:'''''<br /> <br /> •Service limited to specific flight numbers<br /> <br /> •Enables:<br /> <br /> •'''Flight Number Availability page'''<br /> <br /> '''''If disabled:'''''<br /> <br /> •Service not restricted by flight<br /> <br /> <br /> '''Vessel Manipulation Travel Service'''<br /> <br /> '''''If enabled:'''''<br /> <br /> •Service involves '''physical aircraft manipulation'''<br /> <br /> Examples:<br /> <br /> •stretcher mounting<br /> <br /> •seat removal<br /> <br /> •equipment installation<br /> <br /> '''Enables:'''<br /> <br /> •timing logic in:<br /> <br /> •Service Tree Creation<br /> <br /> •operational preparation tasks<br /> <br /> <br /> '''Enforce Mandatory Fields for this Service on Portal'''<br /> <br /> '''''If enabled:'''''<br /> <br /> •Passenger or agent must fill required fields before submitting request<br /> <br /> Examples:<br /> <br /> •medical details<br /> <br /> •equipment requirements<br /> <br /> '''''If disabled:'''''<br /> <br /> •fields remain optional<br /> <br /> == '''Dependency Logic''' ==<br /> The system behavior depends on combined conditions:<br /> <br /> '''Example 1'''<br /> <br /> '''At-Port Direct PAX Service Delivery = Yes'''<br /> <br /> AND<br /> <br /> '''Limited Availability by Port = Enabled'''<br /> <br /> ➡ Result:<br /> <br /> •'''At Port Availability page becomes visible'''<br /> <br /> •Service can be configured per airport<br /> <br /> <br /> '''Example 2'''<br /> <br /> '''On Segment Direct PAX Service Delivery = Yes'''<br /> <br /> AND<br /> <br /> '''Limited Availability by Segment = Enabled'''<br /> <br /> ➡ Result:<br /> <br /> •'''Segment Availability page becomes visible'''<br /> <br /> •Service can be configured per route<br /> <br /> <br /> '''Example 3'''<br /> <br /> '''Limited to Used Craft Type on Segment = Enabled'''<br /> <br /> ➡ Result:<br /> <br /> •'''Craft Availability page becomes visible'''<br /> <br /> •Service limited by aircraft<br /> <br /> <br /> '''Example 4'''<br /> <br /> '''Is Info Service = Yes'''<br /> <br /> ➡ Result:<br /> <br /> •No:<br /> <br /> •delivery partner assignment<br /> <br /> •operational tasks<br /> <br /> •Used only for:<br /> <br /> •display / informational purposes<br /> <br /> <br /> '''Example 5'''<br /> <br /> '''Describes General Medical Condition = Yes'''<br /> <br /> ➡ Result:<br /> <br /> •Service used in:<br /> <br /> •medical classification<br /> <br /> •Impacts:<br /> <br /> •medical approval workflows<br /> <br /> •Not treated as operational service<br /> <br /> === '''Internal Service Process Flow Type (SPFT)''' ===<br /> Defines which workflow logic applies.<br /> <br /> Take MEDA as example<br /> <br /> Controls:<br /> <br /> •approval flows<br /> <br /> •task generation<br /> <br /> •communication templates<br /> <br /> === '''Minimum Connection Times''' ===<br /> Defines minimum required time between segments.<br /> <br /> Used for:<br /> <br /> •operational feasibility checks<br /> <br /> •service validation<br /> <br /> === '''Insecure Handling Advice Communication''' ===<br /> Defines fallback communication channels:<br /> <br /> •email recipients<br /> <br /> •telex recipients<br /> <br /> Used when:<br /> <br /> •digital delivery is not available<br /> [[File:TS base data I.png|none|thumb]]<br /> <br /> <br /> == '''Service Tree Creation''' ==<br /> Defines '''dependencies and relationships between services'''.<br /> <br /> This allows services to automatically trigger or recommend other services.<br /> <br /> '''Service Ordering'''<br /> <br /> Defines which services should be suggested when another service is requested.<br /> <br /> Example:<br /> <br /> Requesting '''STCR (Stretcher)''' automatically suggests:<br /> <br /> •Ambulance transport<br /> <br /> •Escort service<br /> <br /> •Medical oxygen<br /> <br /> '''Force Option'''<br /> <br /> If enabled, the suggested service is '''automatically added'''.<br /> <br /> If disabled, the user can accept or reject the suggestion.<br /> <br /> '''Backend Service Dependency'''<br /> <br /> Defines automatic service creation in backend workflows.<br /> <br /> Example:<br /> <br /> When a '''Stretcher request''' is created:<br /> <br /> Automatically add:<br /> <br /> •Stretcher mounting<br /> <br /> •Stretcher dismantling<br /> <br /> These services are invisible to the passenger.<br /> <br /> '''Vessel Manipulation Service'''<br /> <br /> Defines services that require preparation work on the aircraft.<br /> <br /> Examples:<br /> <br /> •stretcher mounting<br /> <br /> •equipment installation<br /> <br /> •seat removal<br /> <br /> '''Timing Options'''<br /> <br /> Defines when preparation must occur:<br /> {| class=&quot;wikitable&quot;<br /> |'''Option'''<br /> |'''Description'''<br /> |-<br /> |Before segment starts<br /> |preparation before flighr departure<br /> |-<br /> |After segment end<br /> |post-flight removal<br /> |}<br /> [[File:TS service tree creation I.png|none|thumb]]<br /> <br /> <br /> == '''Port Delivery''' ==<br /> The '''Port Delivery page''' defines '''where and how a service is delivered at airport level (ports)''' and '''which service delivery partners are responsible'''.<br /> <br /> This page is only relevant when the service is:<br /> <br /> •'''At-Port Direct PAX Service Delivery = Yes''' ''(from catalogue)''<br /> <br /> •AND optionally '''Limited availability by Port = enabled''' ''(from Base Data)''<br /> <br /> It allows administrators to:<br /> <br /> •define at which ports the service is available<br /> <br /> •assign responsible delivery partners<br /> <br /> •define communication fallback (insecure communication)<br /> <br /> •configure capacity restrictions per partner<br /> <br /> ''This page is '''conditionally available''' based on Base Data settings''<br /> <br /> === '''Direct PAX Service Deliverability at Port''' ===<br /> '''Purpose'''<br /> <br /> Defines '''when during the journey''' the service is delivered at port level.<br /> <br /> <br /> '''Options'''<br /> <br /> '''Deliverable during embarkation on first segment'''<br /> <br /> •Service delivered at '''departure airport'''<br /> <br /> •Example:<br /> <br /> •wheelchair at check-in<br /> <br /> •stretcher boarding preparation<br /> <br /> <br /> '''Deliverable during transfer between segments'''<br /> <br /> •Service delivered during '''transfer at connecting airports'''<br /> <br /> •Example:<br /> <br /> •escort during transfer<br /> <br /> •medical assistance between flights<br /> <br /> <br /> '''Deliverable during disembarkation from last segment'''<br /> <br /> •Service delivered at '''arrival airport'''<br /> <br /> •Example:<br /> <br /> •wheelchair on arrival<br /> <br /> •ambulance pick-up<br /> <br /> <br /> '''Behavior'''<br /> <br /> •Multiple options can be selected<br /> <br /> •Defines '''when service delivery partners are triggered'''<br /> <br /> •Directly impacts:<br /> <br /> •task creation<br /> <br /> •partner notifications<br /> <br /> •workflow timing<br /> <br /> === '''Ports Where Service is Available to PAX''' ===<br /> Defines '''where the service is operationally available''' and '''who delivers it'''.<br /> <br /> '''Global Availability Toggle'''<br /> <br /> '''Checkbox:'''<br /> <br /> '''“This service is generally available at all ports”'''<br /> <br /> '''If ENABLED'''<br /> <br /> •Service is available '''globally'''<br /> <br /> •Only '''exceptions (exclusions)''' are configured below<br /> <br /> •Table acts as: '''restriction list''' not a whitelist<br /> <br /> <br /> '''If DISABLED'''<br /> <br /> •Service is available '''only at listed ports'''<br /> <br /> Table acts as: '''explicit allow-list'''<br /> <br /> <br /> '''Add Port Configuration'''<br /> <br /> '''Fields'''<br /> <br /> '''Add known port'''<br /> <br /> Select airport (e.g., FRA, GVA)<br /> <br /> '''Add known service delivery partner'''<br /> <br /> Assign delivery partner responsible at that port<br /> <br /> Examples: Swissport, Fraport, Handling agents<br /> <br /> <br /> '''Unavailable at this port'''<br /> <br /> Marks service as '''not available''' at selected port<br /> <br /> Used when: global availability is enabled but specific ports must be excluded.<br /> <br /> <br /> '''Port Configuration Table'''<br /> {| class=&quot;wikitable&quot;<br /> |+<br /> !Column<br /> !Description<br /> |-<br /> |Available at port<br /> |Airport code<br /> |-<br /> |Authorized service delivery partner (''defines who is allowed to deliver the service at that port and who will receive tasks and notifications'')<br /> |Assigned partners<br /> |-<br /> |Insecure COM (''defines fallback communication channel and is used when no digital integration exists or communication must still be ensured)''<br /> |Fallback communication channels<br /> |-<br /> |Capacity resriction by partner (''defines operational limits such as maximum concurrent services, partner-specific constraints'')<br /> |Operational limits<br /> |}<br /> [[File:TS port availability I.png|none|thumb]]<br /> <br /> <br /> == Related articles ==<br /> [[Dev:LH MOC Admin-Travel services Translations|Translations]]</div>

Mionamilosevic https://wiki.kordeus.com/index.php?title=File:TS_port_availability_I.png&diff=3285 2026-04-03T11:33:08Z

<p>Mionamilosevic: </p> <hr /> <div>TS port availability I</div>

Mionamilosevic https://wiki.kordeus.com/index.php?title=File:TS_service_tree_creation_I.png&diff=3284 2026-04-03T11:32:25Z

<p>Mionamilosevic: </p> <hr /> <div>TS service tree creation I</div>

Mionamilosevic https://wiki.kordeus.com/index.php?title=File:TS_base_data_I.png&diff=3283 2026-04-03T11:31:39Z

<p>Mionamilosevic: </p> <hr /> <div>TS base data I</div>

Mionamilosevic https://wiki.kordeus.com/index.php?title=File:Travel_Services_Overview.png&diff=3282 2026-04-03T11:28:43Z

<p>Mionamilosevic: </p> <hr /> <div>Travel Services Overview</div>

Mionamilosevic https://wiki.kordeus.com/index.php?title=Dev:LH_MOC_Admin-Travel_services&diff=3266 2026-03-26T08:11:14Z

<p>Mionamilosevic: </p> <hr /> <div>The Travel Service Administration module is the central configuration area where all operational services that can be requested for a passenger are defined and managed.<br /> <br /> A Travel Service represents a concrete operational action related to a passenger’s journey.<br /> <br /> Examples include:<br /> <br /> •Wheelchair assistance<br /> <br /> •Stretcher transport (STCR)<br /> <br /> •Oxygen on board (POXY)<br /> <br /> •Escort services<br /> <br /> •Ambulance transport to/from airport<br /> <br /> •Medical device transport (CPAP/BIPAP)<br /> <br /> •Additional seating<br /> <br /> •Handling of medical baggage<br /> <br /> These services may require:<br /> <br /> •Medical approval<br /> <br /> •Operational approval<br /> <br /> •Ground handling coordination<br /> <br /> •Service delivery partner involvement<br /> <br /> •Task automation<br /> <br /> •Capacity checks<br /> <br /> The module defines '''how a service behaves in the system''', including:<br /> <br /> •Availability<br /> <br /> •Dependencies<br /> <br /> •Approval workflows<br /> <br /> •Automation rules<br /> <br /> •Service visibility<br /> <br /> The '''Travel Service Administration module''' defines the operational backbone of passenger assistance and medical service handling.<br /> <br /> It controls:<br /> <br /> •how services appear<br /> <br /> •who can request them<br /> <br /> •how they trigger other services<br /> <br /> •how approvals work<br /> <br /> •how operational workflows are automated<br /> <br /> Together with:<br /> <br /> •'''SPFT'''<br /> <br /> •'''Service Delivery Partners'''<br /> <br /> •'''Travel Partners'''<br /> <br /> this module forms the core system for managing passenger service operations.<br /> <br /> == Base data ==<br /> The '''Base Data''' section defines the '''core behavior of a travel service''' and controls:<br /> <br /> •where the service can be used (segment / port / flight / aircraft)<br /> <br /> •who can request it<br /> <br /> •how it behaves in workflows<br /> <br /> •which additional configuration pages become available<br /> <br /> A key part of this section is the '''Service Network Compatibility catalogue''', which drives '''availability logic and UI behavior across the system'''.<br /> <br /> === '''Member Service Requestability''' ===<br /> <br /> <br /> Defines who can request the service:<br /> {| class=&quot;wikitable&quot;<br /> |+<br /> !Option<br /> !Effect<br /> |-<br /> |Passenger<br /> |Available in PAX portal<br /> |-<br /> |Travel partner<br /> |Available or external partners<br /> |-<br /> |Internal<br /> |Only internal users can add<br /> |}<br /> <br /> === '''Service Network Compatibility (Catalogue-Driven Logic)''' ===<br /> <br /> <br /> This section defines '''system-level characteristics of the service''', based on a '''catalogue configuration'''.<br /> <br /> These values are '''not manually editable''', but are derived from the selected:<br /> <br /> •'''Global Travel Service Binding'''<br /> <br /> •'''Service Group Key'''<br /> <br /> They determine:<br /> <br /> •how the service behaves<br /> <br /> •where it can be delivered<br /> <br /> •which configuration options are available<br /> <br /> <br /> '''Catalogue Flags''' <br /> <br /> The following flags define '''service capabilities and restrictions''':<br /> <br /> <br /> '''On Segment Direct PAX Service Delivery'''<br /> <br /> '''Value (example):''' No<br /> <br /> '''Meaning:'''<br /> <br /> Defines whether the service can be delivered '''directly to the passenger during a flight segment'''.<br /> <br /> '''''If Yes:'''''<br /> <br /> •Service can be delivered '''on board'''<br /> <br /> •Enables:<br /> <br /> •segment-level availability configuration<br /> <br /> •segment-based automation<br /> <br /> •Related pages enabled:<br /> <br /> •'''Segment Availability'''<br /> <br /> •Typical examples:<br /> <br /> •onboard oxygen<br /> <br /> •onboard assistance<br /> <br /> '''''If No:'''''<br /> <br /> •Service cannot be delivered onboard<br /> <br /> •Segment-related configuration is '''restricted or irrelevant'''<br /> <br /> <br /> '''At-Port Direct PAX Service Delivery'''<br /> <br /> '''Value (example):''' Yes<br /> <br /> '''Meaning:'''<br /> <br /> Defines whether the service can be delivered '''at airport locations (departure, arrival, transfer)'''.<br /> <br /> '''''If Yes:'''''<br /> <br /> •Service is available at:<br /> <br /> •departure airport<br /> <br /> •arrival airport<br /> <br /> •transfer airport<br /> <br /> •Enables:<br /> <br /> •'''At Port Availability page'''<br /> <br /> •port-based restrictions<br /> <br /> •Typical examples:<br /> <br /> •wheelchair assistance<br /> <br /> •ambulance services<br /> <br /> •escort services<br /> <br /> '''''If No:'''''<br /> <br /> •Service cannot be delivered at airport level<br /> <br /> •Port configuration is disabled<br /> <br /> <br /> '''Describes General Medical Condition'''<br /> <br /> '''Value (example):''' No<br /> <br /> '''Meaning:'''<br /> <br /> Defines whether the service represents a '''medical condition classification''' rather than an operational service.<br /> <br /> '''''If Yes:'''''<br /> <br /> •Service is used for:<br /> <br /> •classification (e.g., MEDA)<br /> <br /> •Enables:<br /> <br /> •medical workflows<br /> <br /> •Does NOT represent a physical service<br /> <br /> '''''If No:'''''<br /> <br /> •Service is treated as an '''operational service'''<br /> <br /> <br /> '''Trip Extra Service'''<br /> <br /> '''Value (example):''' No<br /> <br /> '''Meaning:'''<br /> <br /> Defines whether the service applies to the '''entire journey (trip-level)''' rather than individual segments.<br /> <br /> '''''If Yes:'''''<br /> <br /> •Service applies to:<br /> <br /> •whole itinerary<br /> <br /> •Not tied to:<br /> <br /> •specific segments<br /> <br /> •Example:<br /> <br /> •special handling across entire trip<br /> <br /> '''''If No:'''''<br /> <br /> •Service is applied per:<br /> <br /> •segment or port<br /> <br /> <br /> '''Segment Transport Type Service'''<br /> <br /> '''Value (example):''' No<br /> <br /> '''Meaning:'''<br /> <br /> Defines whether the service is tied to '''transport type (air, rail, bus, etc.)'''<br /> <br /> '''''If Yes:'''''<br /> <br /> •Service depends on:<br /> <br /> •transport type of segment<br /> <br /> •Enables:<br /> <br /> •transport-specific filtering<br /> <br /> '''''If No:'''''<br /> <br /> •Service is independent of transport type<br /> <br /> <br /> '''Is Info Service'''<br /> <br /> '''Value (example):''' No<br /> <br /> '''Meaning:'''<br /> <br /> Defines whether the service is '''informational only'''.<br /> <br /> '''''If Yes:'''''<br /> <br /> •Service:<br /> <br /> •does NOT trigger delivery<br /> <br /> •does NOT require execution<br /> <br /> •Used for:<br /> <br /> •displaying information<br /> <br /> •No tasks or delivery partners triggered<br /> <br /> '''''If No:'''''<br /> <br /> •Service is operational and actionable<br /> <br /> === '''Service Availability Limitations''' ===<br /> <br /> <br /> Defines '''where and under which conditions''' the service can be used.<br /> <br /> These settings directly control:<br /> <br /> •which configuration pages are visible<br /> <br /> •how the service is filtered in workflows<br /> <br /> <br /> '''Limited to Used Craft Type on Segment'''<br /> <br /> '''''If enabled:'''''<br /> <br /> •Service is restricted to specific aircraft types<br /> <br /> •Enables:<br /> <br /> •'''Craft Availability page'''<br /> <br /> •Example:<br /> <br /> •stretcher only available on widebody aircraft<br /> <br /> '''''If disabled:'''''<br /> <br /> •Service available for all aircraft types<br /> <br /> <br /> '''Limited Availability by Port'''<br /> <br /> '''''If enabled:'''''<br /> <br /> •Service is restricted to selected airports<br /> <br /> •Enables:<br /> <br /> •'''At Port Availability page'''<br /> <br /> •Requires:<br /> <br /> •At-Port Direct PAX Service Delivery = '''Yes'''<br /> <br /> '''''If disabled:'''''<br /> <br /> •Service available at all ports<br /> <br /> <br /> '''Limited Availability by Segment'''<br /> <br /> '''''If enabled:'''''<br /> <br /> •Service restricted to specific routes or segments<br /> <br /> •Enables:<br /> <br /> •'''Segment Availability page'''<br /> <br /> '''''If disabled:'''''<br /> <br /> •Service available across all segments<br /> <br /> <br /> '''Limited Availability by Flight Number'''<br /> <br /> '''''If enabled:'''''<br /> <br /> •Service limited to specific flight numbers<br /> <br /> •Enables:<br /> <br /> •'''Flight Number Availability page'''<br /> <br /> '''''If disabled:'''''<br /> <br /> •Service not restricted by flight<br /> <br /> <br /> '''Vessel Manipulation Travel Service'''<br /> <br /> '''''If enabled:'''''<br /> <br /> •Service involves '''physical aircraft manipulation'''<br /> <br /> Examples:<br /> <br /> •stretcher mounting<br /> <br /> •seat removal<br /> <br /> •equipment installation<br /> <br /> '''Enables:'''<br /> <br /> •timing logic in:<br /> <br /> •Service Tree Creation<br /> <br /> •operational preparation tasks<br /> <br /> <br /> '''Enforce Mandatory Fields for this Service on Portal'''<br /> <br /> '''''If enabled:'''''<br /> <br /> •Passenger or agent must fill required fields before submitting request<br /> <br /> Examples:<br /> <br /> •medical details<br /> <br /> •equipment requirements<br /> <br /> '''''If disabled:'''''<br /> <br /> •fields remain optional<br /> <br /> == '''Dependency Logic''' ==<br /> The system behavior depends on combined conditions:<br /> <br /> '''Example 1'''<br /> <br /> '''At-Port Direct PAX Service Delivery = Yes'''<br /> <br /> AND<br /> <br /> '''Limited Availability by Port = Enabled'''<br /> <br /> ➡ Result:<br /> <br /> •'''At Port Availability page becomes visible'''<br /> <br /> •Service can be configured per airport<br /> <br /> <br /> '''Example 2'''<br /> <br /> '''On Segment Direct PAX Service Delivery = Yes'''<br /> <br /> AND<br /> <br /> '''Limited Availability by Segment = Enabled'''<br /> <br /> ➡ Result:<br /> <br /> •'''Segment Availability page becomes visible'''<br /> <br /> •Service can be configured per route<br /> <br /> <br /> '''Example 3'''<br /> <br /> '''Limited to Used Craft Type on Segment = Enabled'''<br /> <br /> ➡ Result:<br /> <br /> •'''Craft Availability page becomes visible'''<br /> <br /> •Service limited by aircraft<br /> <br /> <br /> '''Example 4'''<br /> <br /> '''Is Info Service = Yes'''<br /> <br /> ➡ Result:<br /> <br /> •No:<br /> <br /> •delivery partner assignment<br /> <br /> •operational tasks<br /> <br /> •Used only for:<br /> <br /> •display / informational purposes<br /> <br /> <br /> '''Example 5'''<br /> <br /> '''Describes General Medical Condition = Yes'''<br /> <br /> ➡ Result:<br /> <br /> •Service used in:<br /> <br /> •medical classification<br /> <br /> •Impacts:<br /> <br /> •medical approval workflows<br /> <br /> •Not treated as operational service<br /> <br /> === '''Internal Service Process Flow Type (SPFT)''' ===<br /> Defines which workflow logic applies.<br /> <br /> Take MEDA as example<br /> <br /> Controls:<br /> <br /> •approval flows<br /> <br /> •task generation<br /> <br /> •communication templates<br /> <br /> === '''Minimum Connection Times''' ===<br /> Defines minimum required time between segments.<br /> <br /> Used for:<br /> <br /> •operational feasibility checks<br /> <br /> •service validation<br /> <br /> === '''Insecure Handling Advice Communication''' ===<br /> Defines fallback communication channels:<br /> <br /> •email recipients<br /> <br /> •telex recipients<br /> <br /> Used when:<br /> <br /> •digital delivery is not available<br /> <br /> <br /> == '''Service Tree Creation''' ==<br /> Defines '''dependencies and relationships between services'''.<br /> <br /> This allows services to automatically trigger or recommend other services.<br /> <br /> '''Service Ordering'''<br /> <br /> Defines which services should be suggested when another service is requested.<br /> <br /> Example:<br /> <br /> Requesting '''STCR (Stretcher)''' automatically suggests:<br /> <br /> •Ambulance transport<br /> <br /> •Escort service<br /> <br /> •Medical oxygen<br /> <br /> '''Force Option'''<br /> <br /> If enabled, the suggested service is '''automatically added'''.<br /> <br /> If disabled, the user can accept or reject the suggestion.<br /> <br /> '''Backend Service Dependency'''<br /> <br /> Defines automatic service creation in backend workflows.<br /> <br /> Example:<br /> <br /> When a '''Stretcher request''' is created:<br /> <br /> Automatically add:<br /> <br /> •Stretcher mounting<br /> <br /> •Stretcher dismantling<br /> <br /> These services are invisible to the passenger.<br /> <br /> '''Vessel Manipulation Service'''<br /> <br /> Defines services that require preparation work on the aircraft.<br /> <br /> Examples:<br /> <br /> •stretcher mounting<br /> <br /> •equipment installation<br /> <br /> •seat removal<br /> <br /> '''Timing Options'''<br /> <br /> Defines when preparation must occur:<br /> {| class=&quot;wikitable&quot;<br /> |'''Option'''<br /> |'''Description'''<br /> |-<br /> |Before segment starts<br /> |preparation before flighr departure<br /> |-<br /> |After segment end<br /> |post-flight removal<br /> |}<br /> <br /> == '''Port Delivery''' ==<br /> The '''Port Delivery page''' defines '''where and how a service is delivered at airport level (ports)''' and '''which service delivery partners are responsible'''.<br /> <br /> This page is only relevant when the service is:<br /> <br /> •'''At-Port Direct PAX Service Delivery = Yes''' ''(from catalogue)''<br /> <br /> •AND optionally '''Limited availability by Port = enabled''' ''(from Base Data)''<br /> <br /> It allows administrators to:<br /> <br /> •define at which ports the service is available<br /> <br /> •assign responsible delivery partners<br /> <br /> •define communication fallback (insecure communication)<br /> <br /> •configure capacity restrictions per partner<br /> <br /> ''This page is '''conditionally available''' based on Base Data settings''<br /> <br /> === '''Direct PAX Service Deliverability at Port''' ===<br /> '''Purpose'''<br /> <br /> Defines '''when during the journey''' the service is delivered at port level.<br /> <br /> <br /> '''Options'''<br /> <br /> '''Deliverable during embarkation on first segment'''<br /> <br /> •Service delivered at '''departure airport'''<br /> <br /> •Example:<br /> <br /> •wheelchair at check-in<br /> <br /> •stretcher boarding preparation<br /> <br /> <br /> '''Deliverable during transfer between segments'''<br /> <br /> •Service delivered during '''transfer at connecting airports'''<br /> <br /> •Example:<br /> <br /> •escort during transfer<br /> <br /> •medical assistance between flights<br /> <br /> <br /> '''Deliverable during disembarkation from last segment'''<br /> <br /> •Service delivered at '''arrival airport'''<br /> <br /> •Example:<br /> <br /> •wheelchair on arrival<br /> <br /> •ambulance pick-up<br /> <br /> <br /> '''Behavior'''<br /> <br /> •Multiple options can be selected<br /> <br /> •Defines '''when service delivery partners are triggered'''<br /> <br /> •Directly impacts:<br /> <br /> •task creation<br /> <br /> •partner notifications<br /> <br /> •workflow timing<br /> <br /> === '''Ports Where Service is Available to PAX''' ===<br /> Defines '''where the service is operationally available''' and '''who delivers it'''.<br /> <br /> '''Global Availability Toggle'''<br /> <br /> '''Checkbox:'''<br /> <br /> '''“This service is generally available at all ports”'''<br /> <br /> '''If ENABLED'''<br /> <br /> •Service is available '''globally'''<br /> <br /> •Only '''exceptions (exclusions)''' are configured below<br /> <br /> •Table acts as: '''restriction list''' not a whitelist<br /> <br /> <br /> '''If DISABLED'''<br /> <br /> •Service is available '''only at listed ports'''<br /> <br /> Table acts as: '''explicit allow-list'''<br /> <br /> <br /> '''Add Port Configuration'''<br /> <br /> '''Fields'''<br /> <br /> '''Add known port'''<br /> <br /> Select airport (e.g., FRA, GVA)<br /> <br /> '''Add known service delivery partner'''<br /> <br /> Assign delivery partner responsible at that port<br /> <br /> Examples: Swissport, Fraport, Handling agents<br /> <br /> <br /> '''Unavailable at this port'''<br /> <br /> Marks service as '''not available''' at selected port<br /> <br /> Used when: global availability is enabled but specific ports must be excluded.<br /> <br /> <br /> '''Port Configuration Table'''<br /> {| class=&quot;wikitable&quot;<br /> |+<br /> !Column<br /> !Description<br /> |-<br /> |Available at port<br /> |Airport code<br /> |-<br /> |Authorized service delivery partner (''defines who is allowed to deliver the service at that port and who will receive tasks and notifications'')<br /> |Assigned partners<br /> |-<br /> |Insecure COM (''defines fallback communication channel and is used when no digital integration exists or communication must still be ensured)''<br /> |Fallback communication channels<br /> |-<br /> |Capacity resriction by partner (''defines operational limits such as maximum concurrent services, partner-specific constraints'')<br /> |Operational limits<br /> |}<br /> <br /> <br /> == Related articles ==<br /> [[Dev:LH MOC Admin-Travel services Translations|Translations]]</div>

Mionamilosevic https://wiki.kordeus.com/index.php?title=Dev:LH_MOC_Admin-Travel_services&diff=3265 2026-03-25T11:38:50Z

<p>Mionamilosevic: </p> <hr /> <div>The Travel Service Administration module is the central configuration area where all operational services that can be requested for a passenger are defined and managed.<br /> <br /> A Travel Service represents a concrete operational action related to a passenger’s journey.<br /> <br /> Examples include:<br /> <br /> •Wheelchair assistance<br /> <br /> •Stretcher transport (STCR)<br /> <br /> •Oxygen on board (POXY)<br /> <br /> •Escort services<br /> <br /> •Ambulance transport to/from airport<br /> <br /> •Medical device transport (CPAP/BIPAP)<br /> <br /> •Additional seating<br /> <br /> •Handling of medical baggage<br /> <br /> These services may require:<br /> <br /> •Medical approval<br /> <br /> •Operational approval<br /> <br /> •Ground handling coordination<br /> <br /> •Service delivery partner involvement<br /> <br /> •Task automation<br /> <br /> •Capacity checks<br /> <br /> The module defines '''how a service behaves in the system''', including:<br /> <br /> •Availability<br /> <br /> •Dependencies<br /> <br /> •Approval workflows<br /> <br /> •Automation rules<br /> <br /> •Service visibility<br /> <br /> The '''Travel Service Administration module''' defines the operational backbone of passenger assistance and medical service handling.<br /> <br /> It controls:<br /> <br /> •how services appear<br /> <br /> •who can request them<br /> <br /> •how they trigger other services<br /> <br /> •how approvals work<br /> <br /> •how operational workflows are automated<br /> <br /> Together with:<br /> <br /> •'''SPFT'''<br /> <br /> •'''Service Delivery Partners'''<br /> <br /> •'''Travel Partners'''<br /> <br /> this module forms the core system for managing passenger service operations.<br /> <br /> == Base data ==<br /> The '''Base Data''' section defines the '''core behavior of a travel service''' and controls:<br /> <br /> •where the service can be used (segment / port / flight / aircraft)<br /> <br /> •who can request it<br /> <br /> •how it behaves in workflows<br /> <br /> •which additional configuration pages become available<br /> <br /> A key part of this section is the '''Service Network Compatibility catalogue''', which drives '''availability logic and UI behavior across the system'''.<br /> <br /> === '''Member Service Requestability''' ===<br /> <br /> <br /> Defines who can request the service:<br /> {| class=&quot;wikitable&quot;<br /> |+<br /> !Option<br /> !Effect<br /> |-<br /> |Passenger<br /> |Available in PAX portal<br /> |-<br /> |Travel partner<br /> |Available or external partners<br /> |-<br /> |Internal<br /> |Only internal users can add<br /> |}<br /> <br /> === '''Service Network Compatibility (Catalogue-Driven Logic)''' ===<br /> <br /> <br /> This section defines '''system-level characteristics of the service''', based on a '''catalogue configuration'''.<br /> <br /> These values are '''not manually editable''', but are derived from the selected:<br /> <br /> •'''Global Travel Service Binding'''<br /> <br /> •'''Service Group Key'''<br /> <br /> They determine:<br /> <br /> •how the service behaves<br /> <br /> •where it can be delivered<br /> <br /> •which configuration options are available<br /> <br /> <br /> '''Catalogue Flags''' <br /> <br /> The following flags define '''service capabilities and restrictions''':<br /> <br /> <br /> '''On Segment Direct PAX Service Delivery'''<br /> <br /> '''Value (example):''' No<br /> <br /> '''Meaning:'''<br /> <br /> Defines whether the service can be delivered '''directly to the passenger during a flight segment'''.<br /> <br /> '''''If Yes:'''''<br /> <br /> •Service can be delivered '''on board'''<br /> <br /> •Enables:<br /> <br /> •segment-level availability configuration<br /> <br /> •segment-based automation<br /> <br /> •Related pages enabled:<br /> <br /> •'''Segment Availability'''<br /> <br /> •Typical examples:<br /> <br /> •onboard oxygen<br /> <br /> •onboard assistance<br /> <br /> '''''If No:'''''<br /> <br /> •Service cannot be delivered onboard<br /> <br /> •Segment-related configuration is '''restricted or irrelevant'''<br /> <br /> <br /> '''At-Port Direct PAX Service Delivery'''<br /> <br /> '''Value (example):''' Yes<br /> <br /> '''Meaning:'''<br /> <br /> Defines whether the service can be delivered '''at airport locations (departure, arrival, transfer)'''.<br /> <br /> '''''If Yes:'''''<br /> <br /> •Service is available at:<br /> <br /> •departure airport<br /> <br /> •arrival airport<br /> <br /> •transfer airport<br /> <br /> •Enables:<br /> <br /> •'''At Port Availability page'''<br /> <br /> •port-based restrictions<br /> <br /> •Typical examples:<br /> <br /> •wheelchair assistance<br /> <br /> •ambulance services<br /> <br /> •escort services<br /> <br /> '''''If No:'''''<br /> <br /> •Service cannot be delivered at airport level<br /> <br /> •Port configuration is disabled<br /> <br /> <br /> '''Describes General Medical Condition'''<br /> <br /> '''Value (example):''' No<br /> <br /> '''Meaning:'''<br /> <br /> Defines whether the service represents a '''medical condition classification''' rather than an operational service.<br /> <br /> '''''If Yes:'''''<br /> <br /> •Service is used for:<br /> <br /> •classification (e.g., MEDA)<br /> <br /> •Enables:<br /> <br /> •medical workflows<br /> <br /> •Does NOT represent a physical service<br /> <br /> '''''If No:'''''<br /> <br /> •Service is treated as an '''operational service'''<br /> <br /> <br /> '''Trip Extra Service'''<br /> <br /> '''Value (example):''' No<br /> <br /> '''Meaning:'''<br /> <br /> Defines whether the service applies to the '''entire journey (trip-level)''' rather than individual segments.<br /> <br /> '''''If Yes:'''''<br /> <br /> •Service applies to:<br /> <br /> •whole itinerary<br /> <br /> •Not tied to:<br /> <br /> •specific segments<br /> <br /> •Example:<br /> <br /> •special handling across entire trip<br /> <br /> '''''If No:'''''<br /> <br /> •Service is applied per:<br /> <br /> •segment or port<br /> <br /> <br /> '''Segment Transport Type Service'''<br /> <br /> '''Value (example):''' No<br /> <br /> '''Meaning:'''<br /> <br /> Defines whether the service is tied to '''transport type (air, rail, bus, etc.)'''<br /> <br /> '''''If Yes:'''''<br /> <br /> •Service depends on:<br /> <br /> •transport type of segment<br /> <br /> •Enables:<br /> <br /> •transport-specific filtering<br /> <br /> '''''If No:'''''<br /> <br /> •Service is independent of transport type<br /> <br /> <br /> '''Is Info Service'''<br /> <br /> '''Value (example):''' No<br /> <br /> '''Meaning:'''<br /> <br /> Defines whether the service is '''informational only'''.<br /> <br /> '''''If Yes:'''''<br /> <br /> •Service:<br /> <br /> •does NOT trigger delivery<br /> <br /> •does NOT require execution<br /> <br /> •Used for:<br /> <br /> •displaying information<br /> <br /> •No tasks or delivery partners triggered<br /> <br /> '''''If No:'''''<br /> <br /> •Service is operational and actionable<br /> <br /> === '''Service Availability Limitations''' ===<br /> <br /> <br /> Defines '''where and under which conditions''' the service can be used.<br /> <br /> These settings directly control:<br /> <br /> •which configuration pages are visible<br /> <br /> •how the service is filtered in workflows<br /> <br /> <br /> '''Limited to Used Craft Type on Segment'''<br /> <br /> '''''If enabled:'''''<br /> <br /> •Service is restricted to specific aircraft types<br /> <br /> •Enables:<br /> <br /> •'''Craft Availability page'''<br /> <br /> •Example:<br /> <br /> •stretcher only available on widebody aircraft<br /> <br /> '''''If disabled:'''''<br /> <br /> •Service available for all aircraft types<br /> <br /> <br /> '''Limited Availability by Port'''<br /> <br /> '''''If enabled:'''''<br /> <br /> •Service is restricted to selected airports<br /> <br /> •Enables:<br /> <br /> •'''At Port Availability page'''<br /> <br /> •Requires:<br /> <br /> •At-Port Direct PAX Service Delivery = '''Yes'''<br /> <br /> '''''If disabled:'''''<br /> <br /> •Service available at all ports<br /> <br /> <br /> '''Limited Availability by Segment'''<br /> <br /> '''''If enabled:'''''<br /> <br /> •Service restricted to specific routes or segments<br /> <br /> •Enables:<br /> <br /> •'''Segment Availability page'''<br /> <br /> '''''If disabled:'''''<br /> <br /> •Service available across all segments<br /> <br /> <br /> '''Limited Availability by Flight Number'''<br /> <br /> '''''If enabled:'''''<br /> <br /> •Service limited to specific flight numbers<br /> <br /> •Enables:<br /> <br /> •'''Flight Number Availability page'''<br /> <br /> '''''If disabled:'''''<br /> <br /> •Service not restricted by flight<br /> <br /> <br /> '''Vessel Manipulation Travel Service'''<br /> <br /> '''''If enabled:'''''<br /> <br /> •Service involves '''physical aircraft manipulation'''<br /> <br /> Examples:<br /> <br /> •stretcher mounting<br /> <br /> •seat removal<br /> <br /> •equipment installation<br /> <br /> '''Enables:'''<br /> <br /> •timing logic in:<br /> <br /> •Service Tree Creation<br /> <br /> •operational preparation tasks<br /> <br /> <br /> '''Enforce Mandatory Fields for this Service on Portal'''<br /> <br /> '''''If enabled:'''''<br /> <br /> •Passenger or agent must fill required fields before submitting request<br /> <br /> Examples:<br /> <br /> •medical details<br /> <br /> •equipment requirements<br /> <br /> '''''If disabled:'''''<br /> <br /> •fields remain optional<br /> <br /> == '''Dependency Logic''' ==<br /> The system behavior depends on combined conditions:<br /> <br /> '''Example 1'''<br /> <br /> '''At-Port Direct PAX Service Delivery = Yes'''<br /> <br /> AND<br /> <br /> '''Limited Availability by Port = Enabled'''<br /> <br /> ➡ Result:<br /> <br /> •'''At Port Availability page becomes visible'''<br /> <br /> •Service can be configured per airport<br /> <br /> <br /> '''Example 2'''<br /> <br /> '''On Segment Direct PAX Service Delivery = Yes'''<br /> <br /> AND<br /> <br /> '''Limited Availability by Segment = Enabled'''<br /> <br /> ➡ Result:<br /> <br /> •'''Segment Availability page becomes visible'''<br /> <br /> •Service can be configured per route<br /> <br /> <br /> '''Example 3'''<br /> <br /> '''Limited to Used Craft Type on Segment = Enabled'''<br /> <br /> ➡ Result:<br /> <br /> •'''Craft Availability page becomes visible'''<br /> <br /> •Service limited by aircraft<br /> <br /> <br /> '''Example 4'''<br /> <br /> '''Is Info Service = Yes'''<br /> <br /> ➡ Result:<br /> <br /> •No:<br /> <br /> •delivery partner assignment<br /> <br /> •operational tasks<br /> <br /> •Used only for:<br /> <br /> •display / informational purposes<br /> <br /> <br /> '''Example 5'''<br /> <br /> '''Describes General Medical Condition = Yes'''<br /> <br /> ➡ Result:<br /> <br /> •Service used in:<br /> <br /> •medical classification<br /> <br /> •Impacts:<br /> <br /> •medical approval workflows<br /> <br /> •Not treated as operational service<br /> <br /> === '''Internal Service Process Flow Type (SPFT)''' ===<br /> Defines which workflow logic applies.<br /> <br /> Take MEDA as example<br /> <br /> Controls:<br /> <br /> •approval flows<br /> <br /> •task generation<br /> <br /> •communication templates<br /> <br /> === '''Minimum Connection Times''' ===<br /> Defines minimum required time between segments.<br /> <br /> Used for:<br /> <br /> •operational feasibility checks<br /> <br /> •service validation<br /> <br /> === '''Insecure Handling Advice Communication''' ===<br /> Defines fallback communication channels:<br /> <br /> •email recipients<br /> <br /> •telex recipients<br /> <br /> Used when:<br /> <br /> •digital delivery is not available<br /> <br /> == Related articles ==<br /> [[Dev:LH MOC Admin-Travel services Translations|Translations]]</div>

Mionamilosevic https://wiki.kordeus.com/index.php?title=Dev:LH_MOC_Admin&diff=3261 2026-03-17T07:27:13Z

<p>Mionamilosevic: </p> <hr /> <div>* [[Dev:Travel services|Travel Services]]<br /> * [[Dev:LH MOC Admin-Contractors|Contractors]]<br /> * [[Dev:LH MOC Admin-MOC|Medical Operation centers]]<br /> * [[Dev:LH MOC Admin-Task template administration|Task Template Administration]]<br /> * [[Dev:LH MOC Admin-Communication templates|Communication templates]]<br /> * [[Dev:LH MOC Admin-Text Standard blocks|Text Standard Blocks]]<br /> * [[Dev:LH MOC Admin-Standard document administration|Standard documents administration]]<br /> * [[Dev:LH MOC Admin-Travel partner|Travel partner]]<br /> * [[Dev:LH MOC Admin-Travel service delivery partner|Travel service delivery partner]]</div>

Mionamilosevic https://wiki.kordeus.com/index.php?title=Dev:LH_MOC_Admin-Communication_templates&diff=3260 2026-03-17T07:27:01Z

<p>Mionamilosevic: Created page with &quot;The Communication Templates Administration module manages standardized communication messages used within the system to notify passengers, travel partners, and service providers. These templates define the content of automated or manual communications such as: •email requests •portal notifications •document requests •service confirmations •operational instructions Templates ensure that communication is: •&#039;&#039;&#039;consistent&#039;&#039;&#039; •&#039;&#039;&#039;multilingual&#039;&#039;&#039; •&#039;&#039;&#039;...&quot;</p> <hr /> <div>The Communication Templates Administration module manages standardized communication messages used within the system to notify passengers, travel partners, and service providers.<br /> <br /> These templates define the content of automated or manual communications such as:<br /> <br /> •email requests<br /> <br /> •portal notifications<br /> <br /> •document requests<br /> <br /> •service confirmations<br /> <br /> •operational instructions<br /> <br /> Templates ensure that communication is:<br /> <br /> •'''consistent'''<br /> <br /> •'''multilingual'''<br /> <br /> •'''context-aware'''<br /> <br /> •'''automatically populated with case data'''<br /> <br /> Dynamic placeholders allow templates to insert information such as:<br /> <br /> •passenger name<br /> <br /> •booking reference (PNR)<br /> <br /> •case number<br /> <br /> •requested services<br /> <br /> journey details<br /> <br /> Communication templates are typically triggered when:<br /> <br /> •services are requested<br /> <br /> •approvals are required<br /> <br /> •documents are needed<br /> <br /> •case status changes<br /> <br /> <br /> Communication templates are used in many operational situations.<br /> <br /> Passenger must submit MEDIF therefor template MEDIF request will be sent<br /> <br /> Passenger documents required therefor template Document Request will be sent<br /> <br /> The system automatically selects the appropriate template based on:<br /> <br /> requested services<br /> <br /> workflow state<br /> <br /> configured service associations<br /> <br /> == '''Communication Template Groups Overview''' ==<br /> Displays all configured communication templates.<br /> <br /> Templates are organized into '''template groups''', which allow administrators to manage related communications together.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |+Example templates:<br /> !Name<br /> !Contains Medical Information<br /> !Relevant to Services<br /> |-<br /> |Request for MEDIF (Emails)<br /> |YES<br /> |Ambulance, Stretcher, POXY, WCHR-S, WENOLL<br /> |-<br /> |Request for MEDIF (Portal)<br /> |YES<br /> |Ambulance, Stretcher, POXY, WCHR-S, WENOLL<br /> |-<br /> |Request for Non commercial PNR<br /> |NO<br /> |Stretcher<br /> |}<br /> <br /> === '''Table Columns''' ===<br /> '''Name'''<br /> <br /> Name of the communication template.<br /> <br /> This describes the purpose of the communication.<br /> <br /> ''Example: Request for MEDIF (Email)''<br /> <br /> <br /> '''Contains Medical Information'''<br /> <br /> Indicates whether the template contains or transmits medical data.<br /> <br /> If enabled:<br /> <br /> •stricter privacy rules may apply<br /> <br /> •only authorized users can access the communication<br /> <br /> •additional data protection rules may be enforced<br /> <br /> ''Example: MEDIF Request → contains medical information''<br /> <br /> <br /> '''Relevant to Services'''<br /> <br /> Displays the services that trigger or are associated with this communication.<br /> <br /> ''Example: AMBULANCE, STRETCHER, POXY, WCHR-S, WENOLL''<br /> <br /> '''This helps the system determine when the template should be used.'''<br /> <br /> === '''Row Actions''' ===<br /> '''Edit (✏️)'''<br /> <br /> Opens the '''Communication Template Editor'''.<br /> <br /> '''Delete (🗑)'''<br /> <br /> Deletes the communication template.<br /> <br /> Deletion may be restricted if the template is used in active workflows.<br /> <br /> '''Preview (⚙ / Preview icon)'''<br /> <br /> Allows administrators to preview the communication output.<br /> <br /> <br /> '''Buttons'''<br /> <br /> '''Add new'''<br /> <br /> Creates a new communication template.<br /> <br /> '''Search'''<br /> <br /> Filters templates by name.<br /> <br /> == '''Communication Template Editor''' ==<br /> The Communication Template Editor defines the content and behavior of a communication template.<br /> <br /> Administrators can configure:<br /> <br /> •multilingual content<br /> <br /> •dynamic placeholders<br /> <br /> •attachments<br /> <br /> •service associations<br /> <br /> •document references<br /> <br /> === '''Base Information''' ===<br /> <br /> <br /> '''Internal Name'''<br /> <br /> Field: Internal name <br /> <br /> ''Example: Lufthansa Technics DE''<br /> <br /> Purpose:<br /> <br /> •identifies the template internally<br /> <br /> •not visible to passengers<br /> <br /> Supports multilingual naming.<br /> <br /> === '''Communication Languages''' ===<br /> Tabs representing supported languages:<br /> <br /> •EN<br /> <br /> •DE<br /> <br /> Each language tab allows administrators to create localized versions of the communication.<br /> <br /> If a language version is missing, the system may fallback to a default language.<br /> <br /> === '''Contains Medical Information''' ===<br /> Checkbox: Contains medical information<br /> <br /> Indicates whether the communication contains sensitive medical information.<br /> <br /> If enabled:<br /> <br /> •additional privacy controls apply<br /> <br /> •communications may only be sent to authorized recipients<br /> <br /> ''Example: MEDIF request emails''<br /> <br /> === '''Communication Content Editor''' ===<br /> This section defines the main message content.<br /> <br /> <br /> '''Rich Text Editor'''<br /> <br /> Allows administrators to compose formatted communication messages.<br /> <br /> Supports:<br /> <br /> •text formatting<br /> <br /> •bullet lists<br /> <br /> •links<br /> <br /> •dynamic placeholders<br /> <br /> •HTML tables<br /> <br /> This editor defines the '''main message body'''.<br /> <br /> === '''Communication Subject''' ===<br /> Field: Communication subject<br /> <br /> ''Example: Your special services assistance request at Lufthansa (#SARCaseNumber#)''<br /> <br /> Purpose: Defines the subject line of email communications.<br /> <br /> === '''Communication Body''' ===<br /> The message content that will be sent to recipients.<br /> <br /> Example content from the mockup includes:<br /> <br /> •confirmation of service request<br /> <br /> •instructions to complete MEDIF documents<br /> <br /> •next steps for passengers<br /> <br /> The body may include placeholders such as: #PassengerName#, #PNR#, #Journey#<br /> <br /> '''These placeholders are replaced with real case data when the communication is generated.'''<br /> <br /> === '''Available Placeholders''' ===<br /> Displayed in the right panel.<br /> <br /> These placeholders allow the template to dynamically insert case information.<br /> <br /> Examples include:<br /> {| class=&quot;wikitable&quot;<br /> |+<br /> !Placeholder<br /> !Description<br /> |-<br /> |SAR-Case-Number<br /> |Case identifier<br /> |-<br /> |SAR-Request Date<br /> |Date the request was created<br /> |-<br /> |PAX Letter Salutation<br /> |Passenger greeting<br /> |-<br /> |PAX Last Name<br /> |Passenger surname<br /> |-<br /> |PAX First name<br /> |Passenger first name<br /> |-<br /> |PAX Birthdate<br /> |Passenger date of birth<br /> |-<br /> |PAX Booking Code (PNR)<br /> |Passsenger booking reference<br /> |-<br /> |Case Service Request Table<br /> |Table listing requested services<br /> |-<br /> |Journey<br /> |Journey information<br /> |-<br /> |Journey Departure date<br /> |Flight Departure date<br /> |-<br /> |Journey Next Trip Departure date<br /> |Next segment departure<br /> |-<br /> |ESCORT list<br /> |List of escort services<br /> |-<br /> |ESCORT table with full information<br /> |Detailed escort table<br /> |-<br /> |Full Services Tree Table<br /> |Complete list of requested services<br /> |-<br /> |Ambulance Deatils Table<br /> |Ambulance service details<br /> |}<br /> Placeholders ensure communication content is '''automatically personalized'''.<br /> <br /> === '''Standard Text Blocks Integration''' ===<br /> Panel: Available standard text blocks<br /> <br /> <br /> These reusable text fragments come from the '''Standard Text Blocks module'''.<br /> <br /> Examples:<br /> <br /> •Standard Letter Opening<br /> <br /> •Processing Agent Footer<br /> <br /> •Processing Agent Footer with closing phrase<br /> <br /> Administrators can insert these blocks into communications to maintain consistent formatting.<br /> <br /> === '''Import from Email Template''' ===<br /> Button: Import from Email template<br /> <br /> <br /> Allows administrators to import an existing communication template.<br /> <br /> This helps:<br /> <br /> •reuse existing communication structures<br /> <br /> •accelerate template creation<br /> <br /> Supported extensions: ..oft, html, .zip, .csv, .docx<br /> <br /> === '''Attachments''' ===<br /> The template may include predefined attachments.<br /> <br /> Examples include:<br /> <br /> •MEDIF document forms<br /> <br /> •informational PDFs<br /> <br /> •document templates<br /> <br /> Attachments can be added using: <br /> <br /> •Upload from device<br /> <br /> •Pick from list (documents language specific)<br /> <br /> '''Attachments are automatically included when the communication is sent.'''<br /> <br /> === '''Associated Services''' ===<br /> Section: Associated services<br /> <br /> Allows administrators to link communication templates to services.<br /> <br /> ''Example: Wenoll, Stretcher''<br /> <br /> <br /> Purpose:<br /> <br /> •ensures the template is available only for relevant services<br /> <br /> •helps workflows automatically select the correct communication<br /> <br /> Important note:<br /> <br /> These are '''service associations''', not only travel services.<br /> <br /> == Related articles ==<br /> [[Dev:LH MOC Admin-Communication templates Translations|Translations]]</div>

Mionamilosevic https://wiki.kordeus.com/index.php?title=Dev:LH_MOC_Admin-Communication_templates_Translations&diff=3255 2026-03-16T11:35:39Z

<p>Mionamilosevic: Created page with &quot;{| class=&quot;wikitable&quot; |&#039;&#039;&#039;Application&#039;&#039;&#039; |Communication templates |- |&#039;&#039;&#039;Languages&#039;&#039;&#039; |en_en, de_de |}&quot;</p> <hr /> <div>{| class=&quot;wikitable&quot;<br /> |'''Application'''<br /> |Communication templates<br /> |-<br /> |'''Languages'''<br /> |en_en, de_de<br /> |}</div>

Mionamilosevic https://wiki.kordeus.com/index.php?title=Dev:LH_MOC_Admin&diff=3224 2026-03-11T12:13:49Z

<p>Mionamilosevic: </p> <hr /> <div>* [[Dev:Travel services|Travel Services]]<br /> * [[Dev:LH MOC Admin-Contractors|Contractors]]<br /> * [[Dev:LH MOC Admin-MOC|Medical Operation centers]]<br /> * [[Dev:LH MOC Admin-Task template administration|Task Template Administration]]<br /> * [[Dev:LH MOC Admin-Text Standard blocks|Text Standard Blocks]]<br /> * [[Dev:LH MOC Admin-Standard document administration|Standard documents administration]]<br /> * [[Dev:LH MOC Admin-Travel partner|Travel partner]]<br /> * [[Dev:LH MOC Admin-Travel service delivery partner|Travel service delivery partner]]</div>

Mionamilosevic https://wiki.kordeus.com/index.php?title=Dev:LH_MOC_Admin-Standard_document_administration&diff=3223 2026-03-11T12:13:31Z

<p>Mionamilosevic: Created page with &quot;The Standard Documents Administration module allows administrators to manage standardized documents that can be required or attached during case handling and service workflows. Standard documents represent predefined document types that may need to be uploaded, reviewed, or shared as part of passenger service handling. Typical examples include: •MEDIF – Medical Information Form •Animal Training Certificate – certification for service animals •CDC SVAN USA...&quot;</p> <hr /> <div>The Standard Documents Administration module allows administrators to manage standardized documents that can be required or attached during case handling and service workflows.<br /> <br /> Standard documents represent predefined document types that may need to be uploaded, reviewed, or shared as part of passenger service handling.<br /> <br /> Typical examples include:<br /> <br /> •MEDIF – Medical Information Form<br /> <br /> •Animal Training Certificate – certification for service animals<br /> <br /> •CDC SVAN USA – regulatory document for service animals traveling to the USA<br /> <br /> •TÜV Blitzgutachten – technical certification document<br /> <br /> These documents support operational processes by ensuring that:<br /> <br /> •required documents are defined centrally<br /> <br /> •multiple language or regional versions can exist<br /> <br /> •documents are properly categorized<br /> <br /> •sensitive medical documents are clearly identified<br /> <br /> The module also allows document variations to be managed, such as different language versions or region-specific templates.<br /> <br /> == '''Standard Documents Overview''' ==<br /> Displays all configured standard document types available in the system.<br /> <br /> This overview allows administrators to:<br /> <br /> •view existing document types<br /> <br /> •create new document definitions<br /> <br /> •edit document configurations<br /> <br /> •delete unused document types<br /> {| class=&quot;wikitable&quot;<br /> |+<br /> !Column<br /> !Description<br /> |-<br /> |Name<br /> |Name of the document type<br /> |-<br /> |Contains Medical information<br /> |Indicates whether the document contains medical data<br /> |}<br /> {| class=&quot;wikitable&quot;<br /> |+Example documents<br /> !Name<br /> !Contains Medical information<br /> |-<br /> |MEDIF<br /> |YES<br /> |-<br /> |Animal training certificate<br /> |NO<br /> |-<br /> |CDC SVAN USA<br /> |NO<br /> |-<br /> |TÜV Blitzgutachten<br /> |NO<br /> |}<br /> <br /> <br /> '''Row Actions'''<br /> <br /> <br /> '''Edit (✏️)'''<br /> <br /> Opens the '''Standard Document Editor''' where document details and variations can be managed.<br /> <br /> '''Delete (🗑)'''<br /> <br /> Deletes the document definition.<br /> <br /> Deletion may be restricted if:<br /> <br /> •the document is used in workflows<br /> <br /> •documents have already been uploaded in cases<br /> <br /> <br /> '''Buttons'''<br /> <br /> <br /> '''Add new'''<br /> <br /> Creates a new standard document definition.<br /> <br /> '''Search (🔍)'''<br /> <br /> Filters documents by name.<br /> <br /> == '''Standard Document Editor''' ==<br /> The Standard Document Editor allows administrators to configure:<br /> <br /> •the document type<br /> <br /> •document metadata<br /> <br /> •language or regional variations<br /> <br /> •document upload configurations<br /> <br /> Each document type can contain multiple '''document variations''' representing different versions.<br /> <br /> === '''Base Data''' ===<br /> This section defines the general properties of the document type.<br /> <br /> ==== '''Internal Name''' ====<br /> Field:<br /> <br /> '''Internal name'''<br /> <br /> Example: Animal Training Certificate<br /> <br /> Purpose:<br /> <br /> •identifies the document internally<br /> <br /> •used for administration and referencing<br /> <br /> Supports multilingual values.<br /> <br /> ==== '''Holds Medical Document''' ====<br /> Checkbox:<br /> <br /> '''Holds Medical Document'''<br /> <br /> Indicates whether the document contains medical data.<br /> <br /> If enabled:<br /> <br /> •the document is treated as '''medical information'''<br /> <br /> •stricter privacy rules may apply<br /> <br /> •special handling in workflows may occur<br /> <br /> Example: MEDIF → holds medical document<br /> <br /> This is important for compliance with medical data protection regulations.<br /> <br /> ==== '''Is in Use''' ====<br /> Checkbox:<br /> <br /> '''Is in use'''<br /> <br /> Indicates whether the document definition is active.<br /> <br /> If disabled:<br /> <br /> •the document cannot be requested in workflows<br /> <br /> •existing uploaded documents remain stored<br /> <br /> This allows documents to be retired without deleting them.<br /> <br /> === '''Document Variations''' ===<br /> <br /> <br /> Allows administrators to define multiple versions of a document.<br /> <br /> Variations may differ by:<br /> <br /> •language<br /> <br /> •regulatory region<br /> <br /> •document format<br /> <br /> ''For example:''<br /> <br /> ''•EU version''<br /> <br /> ''•US version''<br /> <br /> ''•language-specific version''<br /> {| class=&quot;wikitable&quot;<br /> |+<br /> !Column<br /> !Description<br /> |-<br /> |Name<br /> |Name of the document variation<br /> |-<br /> |Language<br /> |Language of the document<br /> |-<br /> |Upload information<br /> |Details about the uploaded file<br /> |}<br /> {| class=&quot;wikitable&quot;<br /> |+Example Variations<br /> !Name<br /> !Language<br /> !Uploaded Information<br /> |-<br /> |Animal training certificate (EU)<br /> |DE<br /> |Uploaded by DW<br /> |-<br /> |Animal training certificate (EU)<br /> |EN<br /> |Uploaded by DW<br /> |}<br /> '''Upload Information'''<br /> <br /> Displays metadata about the uploaded document file.<br /> <br /> Example: Uploaded by DW (06.08.2025 16:25)<br /> <br /> This helps track:<br /> <br /> •who uploaded the file<br /> <br /> •when the document was updated<br /> <br /> <br /> '''Row Actions'''<br /> <br /> <br /> Icons displayed in the table represent document actions.<br /> <br /> '''View (👁)'''<br /> <br /> Opens the uploaded document for preview.<br /> <br /> '''Download (⬇)'''<br /> <br /> Downloads the document file.<br /> <br /> '''Upload / Replace (⬆)'''<br /> <br /> Uploads a new version of the document.<br /> <br /> Used when:<br /> <br /> •document template changes<br /> <br /> •updated regulatory forms are required<br /> <br /> <br /> '''Delete (🗑)'''<br /> <br /> Deletes the document variation.<br /> <br /> Deletion may be restricted if the variation is already used in cases.<br /> <br /> <br /> '''Add new'''<br /> <br /> Button:<br /> <br /> '''Add new'''<br /> <br /> Creates a new document variation.<br /> <br /> Used when:<br /> <br /> •adding a new language<br /> <br /> •adding a regional variant<br /> <br /> •updating regulatory documents<br /> <br /> == Related articles ==<br /> [[Dev:LH MOC Admin-Standard document administration Translations|Translations]]</div>

Mionamilosevic https://wiki.kordeus.com/index.php?title=Dev:LH_MOC_Admin-Standard_document_administration_Translations&diff=3222 2026-03-11T12:13:18Z

<p>Mionamilosevic: Created page with &quot;{| class=&quot;wikitable&quot; |&#039;&#039;&#039;Application&#039;&#039;&#039; |Standard document administration |- |&#039;&#039;&#039;Languages&#039;&#039;&#039; |en_en, de_de |}&quot;</p> <hr /> <div>{| class=&quot;wikitable&quot;<br /> |'''Application'''<br /> |Standard document administration<br /> |-<br /> |'''Languages'''<br /> |en_en, de_de<br /> |}</div>

Mionamilosevic https://wiki.kordeus.com/index.php?title=Dev:LH_MOC_Admin&diff=3221 2026-03-11T11:38:39Z

<p>Mionamilosevic: </p> <hr /> <div>* [[Dev:Travel services|Travel Services]]<br /> * [[Dev:LH MOC Admin-Contractors|Contractors]]<br /> * [[Dev:LH MOC Admin-MOC|Medical Operation centers]]<br /> * [[Dev:LH MOC Admin-Task template administration|Task Template Administration]]<br /> * [[Dev:LH MOC Admin-Text Standard blocks|Text Standard Blocks]]<br /> * Standard documents administration<br /> * [[Dev:LH MOC Admin-Travel partner|Travel partner]]<br /> * [[Dev:LH MOC Admin-Travel service delivery partner|Travel service delivery partner]]</div>

Mionamilosevic https://wiki.kordeus.com/index.php?title=Dev:LH_MOC_Admin-Text_Standard_blocks&diff=3217 2026-03-10T11:13:37Z

<p>Mionamilosevic: Created page with &quot;The Standard Text Block Administration module allows administrators to create and manage reusable text fragments that can be inserted into communication templates such as emails, letters, and notifications. These text blocks ensure: •consistent communication •faster message creation •reusable standardized phrases •multilingual support •dynamic content through placeholders Typical use cases include: •email openings and greetings •closing phrases and...&quot;</p> <hr /> <div>The Standard Text Block Administration module allows administrators to create and manage reusable text fragments that can be inserted into communication templates such as emails, letters, and notifications.<br /> <br /> These text blocks ensure:<br /> <br /> •consistent communication<br /> <br /> •faster message creation<br /> <br /> •reusable standardized phrases<br /> <br /> •multilingual support<br /> <br /> •dynamic content through placeholders<br /> <br /> Typical use cases include:<br /> <br /> •email openings and greetings<br /> <br /> •closing phrases and signatures<br /> <br /> •procedural explanations<br /> <br /> •medical information texts<br /> <br /> •regulatory statements<br /> <br /> Standard text blocks can be reused across multiple communication templates, ensuring uniform wording and reducing duplication.<br /> <br /> == '''Standard Text Block Groups''' ==<br /> Standard text blocks are organized into '''groups''' that categorize their purpose.<br /> <br /> This improves:<br /> <br /> •navigation<br /> <br /> •maintainability<br /> <br /> •template design<br /> <br /> •reuse of communication fragments<br /> <br /> Example Groups<br /> {| class=&quot;wikitable&quot;<br /> |+<br /> !Group<br /> !Purpose<br /> |-<br /> |Letter<br /> |text blocks used in letters and email communication<br /> |-<br /> |Medical<br /> |Medical related standard communication<br /> |-<br /> |Processual<br /> |Procedural or operational <br /> |}<br /> Selecting a group displays the text blocks contained in that category. ''All groups will be added manually''<br /> <br /> == '''Standard Text Block Group Overview''' ==<br /> Displays all standard text blocks belonging to the selected group.<br /> <br /> Example from screenshot:<br /> <br /> Contents of standard text block group: Letter<br /> <br /> '''Table Columns'''<br /> {| class=&quot;wikitable&quot;<br /> |+<br /> !Column<br /> !Description<br /> |-<br /> |Name<br /> |Name of the text block<br /> |-<br /> |Used<br /> |Indicates whetther the block is currently used in communication templates<br /> |-<br /> |Usage in Communication Templates<br /> |Lists templates where the block is used<br /> |}<br /> <br /> <br /> '''Row Actions'''<br /> <br /> '''Edit (✏️)'''<br /> <br /> Opens the Text Block Editor.<br /> <br /> '''Delete (🗑)'''<br /> <br /> Deletes the selected text block.<br /> <br /> Deletion may be restricted if the block is used in communication templates.<br /> <br /> '''Buttons'''<br /> <br /> '''Add new'''<br /> <br /> Creates a new standard text block inside the selected group.<br /> <br /> '''Search (🔍)'''<br /> <br /> Filters text blocks by name.<br /> <br /> == '''Text Block Editor''' ==<br /> The Text Block Editor is used to create or modify the reusable content stored in a text block.<br /> <br /> Each block contains:<br /> <br /> •an identifier<br /> <br /> •multilingual content<br /> <br /> •formatted text<br /> <br /> •dynamic placeholders<br /> <br /> These blocks can then be inserted into communication templates.<br /> <br /> === '''Header''' ===<br /> '''Text Block Title'''<br /> <br /> Displays the name of the block currently being edited.<br /> <br /> Example: Text block &quot;MEDIF Request via Email&quot;<br /> <br /> === '''Text Block Identifier''' ===<br /> '''Field'''<br /> <br /> '''Text-Block-Identifier'''<br /> <br /> Example: my-text-block-17<br /> <br /> Purpose:<br /> <br /> •unique internal reference<br /> <br /> •used by templates to identify the block<br /> <br /> This identifier should remain stable once created.<br /> <br /> === '''Internal Name''' ===<br /> '''Field'''<br /> <br /> '''Internal name'''<br /> <br /> Example: Lufthansa Technics DE<br /> <br /> Purpose:<br /> <br /> •internal administrative name<br /> <br /> •helps identify the block in the system<br /> <br /> The internal name may differ from the visible content.<br /> <br /> === '''Text Block Content''' ===<br /> '''Language Tabs'''<br /> <br /> The system supports multilingual text blocks.<br /> <br /> Languages shown in the interface:<br /> <br /> •English<br /> <br /> •German<br /> <br /> •French<br /> <br /> •Italian<br /> <br /> Each language version contains the localized content for the block.<br /> <br /> This ensures communications are sent in the recipient’s language.<br /> <br /> === '''Rich Text Editor (QuillJS)''' ===<br /> The content is written using a QuillJS rich text editor.<br /> <br /> The editor supports:<br /> {| class=&quot;wikitable&quot;<br /> |+<br /> !Feature<br /> !Purpose<br /> |-<br /> |Font selection<br /> |Choose font type<br /> |-<br /> |Font size<br /> |Adjust text <br /> |-<br /> |Bold/Italic/Underline<br /> |Text emphasis<br /> |-<br /> |Lists<br /> |Bullet or numbered list<br /> |-<br /> |Alignmnet<br /> |Text alignment<br /> |-<br /> |Links<br /> |Insert hyperlinks<br /> |-<br /> |Images<br /> |Embed images if required<br /> |}<br /> This allows formatting of professional communication messages.<br /> <br /> === '''Standard Text Block Content''' ===<br /> Main content field:<br /> <br /> '''Standard Text Block'''<br /> <br /> Example: Dear {{PAX Letter Salutation}} {{PAX Last Name}},<br /> <br /> Purpose:<br /> <br /> •defines the reusable communication text<br /> <br /> •may contain placeholders<br /> <br /> •may include formatted text<br /> <br /> This block is inserted into larger communication templates.<br /> <br /> === '''Available Placeholders''' ===<br /> Panel on the right side.<br /> <br /> Displays dynamic variables that can be inserted into the text.<br /> <br /> Example placeholders:<br /> <br /> {| class=&quot;wikitable&quot;<br /> |+<br /> !Placeholder<br /> !Description<br /> |-<br /> |SAR-Case-Number<br /> |Case reference number<br /> |-<br /> |SAR-Request Date<br /> |Date of the request<br /> |-<br /> |PAX Letter Salutation<br /> |Passenger greeting (Mr./Ms.)<br /> |-<br /> |PAX Last Name<br /> |Passenger last name<br /> |-<br /> |PAX first Name<br /> |Passenger first name<br /> |-<br /> |PAX Birthdate<br /> |Passsenger date of birth<br /> |-<br /> |PAX Booking Code (PNR)<br /> |Passenger booking reference<br /> |-<br /> |Case Service Request Table (HTML)<br /> |Table with requested services<br /> |-<br /> |Journey (HTML Table)<br /> |Table with journey details<br /> |-<br /> |Journey Departure Date<br /> |Departure date<br /> |-<br /> |Journey Next Trip Departure Date<br /> |Next segment departure<br /> |-<br /> |ESCORT list<br /> |List of escort services<br /> |-<br /> |ESCORT Table with full information<br /> |Detailed escort information<br /> |-<br /> |Full Service Tree Table<br /> |Complete list of services<br /> |-<br /> |AMBULANCE Details Table (HTML)<br /> |Ambulance service information<br /> |}<br /> '''Purpose of Placeholders'''<br /> <br /> Placeholders are replaced with '''real case data''' when the communication is generated.<br /> <br /> Example:Dear {{PAX Last Name}} becomes Dear Smith<br /> <br /> === '''Available Standard Text Blocks''' ===<br /> <br /> == Panel: ==<br /> '''Available standard text blocks'''<br /> <br /> This section displays reusable blocks that can be inserted into the current text block.<br /> <br /> Examples from the screenshot:<br /> <br /> •Standard Letter Opening<br /> <br /> •Processing Agent Footer<br /> <br /> •Processing Agent Footer with closing phrase<br /> <br /> <br /> '''Manage Standard Blocks'''<br /> <br /> Button:<br /> <br /> Manage Standard Blocks<br /> <br /> Opens the administration area where standard blocks can be managed.<br /> <br /> Purpose:<br /> <br /> Allows combining smaller blocks into larger communication texts.<br /> <br /> Example structure of a letter:<br /> <br /> [Standard Letter Opening]<br /> <br /> [Main Message Content]<br /> <br /> [Processing Agent Footer]<br /> <br /> == '''Workflow Usage''' ==<br /> Standard text blocks are used in:<br /> {| class=&quot;wikitable&quot;<br /> |+<br /> !Area<br /> !Purpose<br /> |-<br /> |Communication Templates<br /> |Emails and letters<br /> |-<br /> |Medical communication<br /> |MEDIF requests<br /> |-<br /> |Operational notifications<br /> |Service confirmations<br /> |-<br /> |Partner communication<br /> |Message to external partners<br /> |}<br /> <br /> == Related articles ==<br /> [[Dev:LH MOC Admin-Text Standard blocks translations|Translations]]</div>

Mionamilosevic https://wiki.kordeus.com/index.php?title=Dev:LH_MOC_Admin-Text_Standard_blocks_translations&diff=3216 2026-03-10T11:13:23Z

<p>Mionamilosevic: Created page with &quot;{| class=&quot;wikitable&quot; |&#039;&#039;&#039;Application&#039;&#039;&#039; |Text standard blocks |- |&#039;&#039;&#039;Languages&#039;&#039;&#039; |en_en, de_de |}&quot;</p> <hr /> <div>{| class=&quot;wikitable&quot;<br /> |'''Application'''<br /> |Text standard blocks<br /> |-<br /> |'''Languages'''<br /> |en_en, de_de<br /> |}</div>

Mionamilosevic https://wiki.kordeus.com/index.php?title=Dev:LH_MOC_Admin&diff=3210 2026-03-10T09:59:22Z

<p>Mionamilosevic: </p> <hr /> <div>* [[Dev:Travel services|Travel Services]]<br /> * [[Dev:LH MOC Admin-Contractors|Contractors]]<br /> * [[Dev:LH MOC Admin-MOC|Medical Operation centers]]<br /> * [[Dev:LH MOC Admin-Task template administration|Task Template Administration]]<br /> * Text Standard Blocks<br /> * Standard documents administration<br /> * [[Dev:LH MOC Admin-Travel partner|Travel partner]]<br /> * [[Dev:LH MOC Admin-Travel service delivery partner|Travel service delivery partner]]</div>

Mionamilosevic https://wiki.kordeus.com/index.php?title=Dev:LH_MOC_Admin-Task_template_administration&diff=3208 2026-03-06T13:20:39Z

<p>Mionamilosevic: </p> <hr /> <div>The Task Template Administration module allows administrators to define standardized operational tasks that can be automatically or manually generated during case workflows.<br /> <br /> Task templates help ensure that recurring operational actions are:<br /> <br /> •consistent<br /> <br /> •clearly documented<br /> <br /> •assigned to the correct participants<br /> <br /> •executed within defined deadlines<br /> <br /> Typical examples of tasks include:<br /> <br /> •Operational checks<br /> <br /> •Medical verification<br /> <br /> •Service confirmations<br /> <br /> •Communication with partners<br /> <br /> •Follow-up reminders<br /> <br /> •Documentation checks<br /> <br /> Task templates support:<br /> <br /> •multilingual communication<br /> <br /> •dynamic placeholders<br /> <br /> •service associations<br /> <br /> •priority management<br /> <br /> •deadline automation<br /> <br /> •assignment to teams, groups, or individuals<br /> <br /> •controlled data sharing with external partners<br /> <br /> These templates are used throughout the system to support Medical Operation Center (MOC) workflows.<br /> <br /> == '''Task Template Groups''' ==<br /> Task Template Groups organize task templates into logical categories.<br /> <br /> Grouping templates improves:<br /> <br /> •navigation<br /> <br /> •administration<br /> <br /> •workflow clarity<br /> <br /> •task discovery<br /> <br /> Examples of groups shown in the system:<br /> {| class=&quot;wikitable&quot;<br /> |+<br /> !Group<br /> !Typical use<br /> |-<br /> |General<br /> |Common operational tasks<br /> |-<br /> |Sitiing case<br /> |Tasks specific to sitting passengers<br /> |-<br /> |Stretcher<br /> |Stretcher related operational tasks<br /> |-<br /> |Oxygen Concentrators<br /> |Oxygen service handling<br /> |-<br /> |SVAN<br /> |Special assistance services/pet related<br /> |-<br /> |Travel partners<br /> |Partner coordination tasks<br /> |}<br /> Each group contains one or more templates.<br /> <br /> == '''Task Template Group Overview''' ==<br /> Displays all templates belonging to the selected task template group.<br /> <br /> Example shown in mockup:<br /> <br /> '''Contents of task template group: General'''<br /> <br /> '''Table Columns'''<br /> <br /> '''Column''' '''Description'''<br /> <br /> Name Name of the task template<br /> <br /> <br /> '''Row Actions'''<br /> <br /> '''Edit (✏️)''' Opens the '''Task Template Editor''' for modifying the template.<br /> <br /> '''Delete (🗑)''' Removes the task template.<br /> <br /> Deletion is restricted if the template is used in active workflows.<br /> <br /> <br /> '''Buttons'''<br /> <br /> '''Add new''' Creates a new task template inside the selected group.<br /> <br /> <br /> '''Search (🔍)''' Filters templates by name.<br /> [[File:Task templates adm.png|none|thumb]]<br /> <br /> == '''Task Template Editor''' ==<br /> The Task Template Editor defines how a task behaves when it is generated in a workflow.<br /> <br /> This includes:<br /> <br /> •content<br /> <br /> •responsible participants<br /> <br /> •deadlines<br /> <br /> •priority<br /> <br /> •service associations<br /> <br /> •data sharing permissions<br /> <br /> == '''Task Definition''' ==<br /> '''Internal Name'''<br /> <br /> Internal identifier for the template.<br /> <br /> Used for:<br /> <br /> •administration<br /> <br /> •searching<br /> <br /> •system reference<br /> <br /> Example: Lufthansa Technics DE<br /> <br /> <br /> '''Communication (Language Tabs)'''<br /> <br /> Supports multilingual task communication.<br /> <br /> Each language version contains:<br /> <br /> •task subject<br /> <br /> •task description<br /> <br /> This ensures that tasks are displayed in the user’s language.<br /> <br /> === '''Task Subject''' ===<br /> Defines the short title of the task.<br /> <br /> Example: Check ESCORT NON-Upgrade SK<br /> <br /> This title appears in:<br /> <br /> •task lists<br /> <br /> •notifications<br /> <br /> •workflow views<br /> <br /> === '''Description''' ===<br /> Detailed explanation of the task.<br /> <br /> Used to provide instructions to the user performing the task.<br /> <br /> Examples:<br /> <br /> •operational instructions<br /> <br /> •service procedures<br /> <br /> •reminders<br /> <br /> •documentation requirements<br /> <br /> This field can also include instructional text helpful for new employees.<br /> <br /> === '''Task Type''' ===<br /> Dropdown defining the nature of the task.<br /> <br /> Typical options include:<br /> {| class=&quot;wikitable&quot;<br /> |+<br /> !Type<br /> !Purpose<br /> |-<br /> |Reminder<br /> |Informational task<br /> |-<br /> |Action<br /> |Task requiring operational action<br /> |-<br /> |Approval<br /> |Task requiring approval<br /> |}<br /> Task type influences how the task appears in the system and actions related to it.<br /> <br /> === '''Priority''' ===<br /> Marks the task as high priority.<br /> <br /> Priority tasks:<br /> <br /> •appear highlighted in task lists<br /> <br /> •are handled before normal tasks<br /> <br /> === '''Due Date''' ===<br /> Defines when the task must be completed.<br /> <br /> Options:<br /> {| class=&quot;wikitable&quot;<br /> |+<br /> !Option<br /> !Description<br /> |-<br /> |Immediately<br /> |Task appears instantly<br /> |-<br /> |In hours<br /> |Deadline defined in hours<br /> |-<br /> |In days<br /> |Deadline defined in days<br /> |}<br /> This allows tasks to be automatically scheduled relative to workflow events.<br /> <br /> == '''Participants &amp; Groups''' ==<br /> Defines who is responsible for executing the task.<br /> <br /> Tasks can be assigned to:<br /> <br /> •individual users<br /> <br /> •teams<br /> <br /> •business groups<br /> <br /> •external partners<br /> <br /> === '''Add Business Group Participant''' ===<br /> Adds a specific user belonging to a business group.<br /> <br /> Example:<br /> <br /> •doctor<br /> <br /> •operations manager<br /> <br /> === '''Add Business Group''' ===<br /> Assigns the entire group.<br /> <br /> Example groups:<br /> <br /> •MOC Operations Team<br /> <br /> •MOC Medical Team<br /> <br /> This ensures that any available member of the group can execute the task.<br /> <br /> === '''Request Task With''' ===<br /> Associates the task template with partners, groups, or users.<br /> <br /> Examples shown in mockup:<br /> <br /> •MOC Operations Team<br /> <br /> •MOC Medical Team<br /> <br /> •External Doctors<br /> <br /> •MSC Cruises<br /> <br /> •LH Technics MUC<br /> <br /> •Individual users<br /> <br /> A search field allows filtering participants.<br /> <br /> == '''Functional Placeholders''' ==<br /> Panel: '''Available functional placeholders'''<br /> <br /> These placeholders allow dynamic values to be inserted into task text.<br /> <br /> Examples:<br /> {| class=&quot;wikitable&quot;<br /> |+<br /> !Placeholder<br /> !Purpose<br /> |-<br /> |Travel partner<br /> |Inserts travel partner name<br /> |-<br /> |Pasenger (PAX) <br /> |Inserts passenger name<br /> |-<br /> |Requesting party<br /> |Shows who requested the service<br /> |-<br /> |Service delivery partner<br /> |Shows ground service provider<br /> |}<br /> When a task is generated, placeholders are automatically replaced with real values.<br /> <br /> == '''Associated Services''' ==<br /> Links the task template to one or more services.<br /> <br /> Example from mockup:<br /> <br /> •WENOLL<br /> <br /> •STRETCHER<br /> <br /> Important:<br /> <br /> These are '''services''', not only travel services.<br /> <br /> Purpose:<br /> <br /> •ensures that correct templates are suggested when specific services are used<br /> <br /> •improves task automation accuracy<br /> <br /> == '''Data Protection / Task Data Sharing with External Partners''' ==<br /> Defines which information external partners can access when tasks are shared with them.<br /> <br /> This ensures compliance with '''data protection regulations'''.<br /> <br /> === '''Share Case Base Information''' ===<br /> Shares basic case information:<br /> <br /> •case ID<br /> <br /> •passenger name<br /> <br /> •case status<br /> <br /> === '''Share Case Itinerary Information''' ===<br /> Allows partners to see:<br /> <br /> •flights<br /> <br /> •segments<br /> <br /> •travel itinerary<br /> <br /> === '''Share Case Ticketing Information''' ===<br /> Allows access to:<br /> <br /> •booking<br /> <br /> •PNR<br /> <br /> •ticket information<br /> <br /> === '''Allow Editing Case Ticketing Information''' ===<br /> Allows partners to modify ticket data.<br /> <br /> This option becomes available '''only when ticketing information sharing is enabled'''.<br /> <br /> === '''Share Case Requested Services Information''' ===<br /> Allows partners to see which services were requested.<br /> <br /> Examples:<br /> <br /> •stretcher<br /> <br /> •oxygen<br /> <br /> •escort<br /> <br /> === '''Share Case Medical Information''' ===<br /> Allows sharing of medical data related to the case.<br /> <br /> Example:<br /> <br /> •MEDA information<br /> <br /> This option should be enabled only when medically necessary.<br /> <br /> == Related articles ==<br /> [[Dev:LH MOC Admin-Task template administration Translations|Translations]]</div>

Mionamilosevic https://wiki.kordeus.com/index.php?title=Dev:LH_MOC_Admin-Task_template_administration&diff=3207 2026-03-06T13:20:19Z

<p>Mionamilosevic: </p> <hr /> <div>The Task Template Administration module allows administrators to define standardized operational tasks that can be automatically or manually generated during case workflows.<br /> <br /> Task templates help ensure that recurring operational actions are:<br /> <br /> •consistent<br /> <br /> •clearly documented<br /> <br /> •assigned to the correct participants<br /> <br /> •executed within defined deadlines<br /> <br /> Typical examples of tasks include:<br /> <br /> •Operational checks<br /> <br /> •Medical verification<br /> <br /> •Service confirmations<br /> <br /> •Communication with partners<br /> <br /> •Follow-up reminders<br /> <br /> •Documentation checks<br /> <br /> Task templates support:<br /> <br /> •multilingual communication<br /> <br /> •dynamic placeholders<br /> <br /> •service associations<br /> <br /> •priority management<br /> <br /> •deadline automation<br /> <br /> •assignment to teams, groups, or individuals<br /> <br /> •controlled data sharing with external partners<br /> <br /> These templates are used throughout the system to support Medical Operation Center (MOC) workflows.<br /> <br /> == '''Task Template Groups''' ==<br /> Task Template Groups organize task templates into logical categories.<br /> <br /> Grouping templates improves:<br /> <br /> •navigation<br /> <br /> •administration<br /> <br /> •workflow clarity<br /> <br /> •task discovery<br /> <br /> Examples of groups shown in the system:<br /> {| class=&quot;wikitable&quot;<br /> |+<br /> !Group<br /> !Typical use<br /> |-<br /> |General<br /> |Common operational tasks<br /> |-<br /> |Sitiing case<br /> |Tasks specific to sitting passengers<br /> |-<br /> |Stretcher<br /> |Stretcher related operational tasks<br /> |-<br /> |Oxygen Concentrators<br /> |Oxygen service handling<br /> |-<br /> |SVAN<br /> |Special assistance services/pet related<br /> |-<br /> |Travel partners<br /> |Partner coordination tasks<br /> |}<br /> Each group contains one or more templates.<br /> <br /> == '''Task Template Group Overview''' ==<br /> Displays all templates belonging to the selected task template group.<br /> <br /> Example shown in mockup:<br /> <br /> '''Contents of task template group: General'''<br /> <br /> '''Table Columns'''<br /> <br /> '''Column''' '''Description'''<br /> <br /> Name Name of the task template<br /> <br /> <br /> '''Row Actions'''<br /> <br /> '''Edit (✏️)''' Opens the '''Task Template Editor''' for modifying the template.<br /> <br /> '''Delete (🗑)''' Removes the task template.<br /> <br /> Deletion is restricted if the template is used in active workflows.<br /> <br /> <br /> '''Buttons'''<br /> <br /> '''Add new''' Creates a new task template inside the selected group.<br /> <br /> <br /> '''Search (🔍)''' Filters templates by name.<br /> [[File:Task templates adm.png|none|thumb]]<br /> <br /> == '''Task Template Editor''' ==<br /> The Task Template Editor defines how a task behaves when it is generated in a workflow.<br /> <br /> This includes:<br /> <br /> •content<br /> <br /> •responsible participants<br /> <br /> •deadlines<br /> <br /> •priority<br /> <br /> •service associations<br /> <br /> •data sharing permissions<br /> <br /> == '''Task Definition''' ==<br /> '''Internal Name'''<br /> <br /> Internal identifier for the template.<br /> <br /> Used for:<br /> <br /> •administration<br /> <br /> •searching<br /> <br /> •system reference<br /> <br /> Example: Lufthansa Technics DE<br /> <br /> <br /> '''Communication (Language Tabs)'''<br /> <br /> Supports multilingual task communication.<br /> <br /> Each language version contains:<br /> <br /> •task subject<br /> <br /> •task description<br /> <br /> This ensures that tasks are displayed in the user’s language.<br /> <br /> === '''Task Subject''' ===<br /> Defines the short title of the task.<br /> <br /> Example: Check ESCORT NON-Upgrade SK<br /> <br /> This title appears in:<br /> <br /> •task lists<br /> <br /> •notifications<br /> <br /> •workflow views<br /> <br /> === '''Description''' ===<br /> Detailed explanation of the task.<br /> <br /> Used to provide instructions to the user performing the task.<br /> <br /> Examples:<br /> <br /> •operational instructions<br /> <br /> •service procedures<br /> <br /> •reminders<br /> <br /> •documentation requirements<br /> <br /> This field can also include instructional text helpful for new employees.<br /> <br /> === '''Task Type''' ===<br /> Dropdown defining the nature of the task.<br /> <br /> Typical options include:<br /> {| class=&quot;wikitable&quot;<br /> |+<br /> !Type<br /> !Purpose<br /> |-<br /> |Reminder<br /> |Informational task<br /> |-<br /> |Action<br /> |Task requiring operational action<br /> |-<br /> |Approval<br /> |Task requiring approval<br /> |}<br /> Task type influences how the task appears in the system and actions related to it.<br /> <br /> === '''Priority''' ===<br /> Marks the task as high priority.<br /> <br /> Priority tasks:<br /> <br /> •appear highlighted in task lists<br /> <br /> •are handled before normal tasks<br /> <br /> === '''Due Date''' ===<br /> Defines when the task must be completed.<br /> <br /> Options:<br /> {| class=&quot;wikitable&quot;<br /> |+<br /> !Option<br /> !Description<br /> |-<br /> |Immediately<br /> |Task appears instantly<br /> |-<br /> |In hours<br /> |Deadline defined in hours<br /> |-<br /> |In days<br /> |Deadline defined in days<br /> |}<br /> This allows tasks to be automatically scheduled relative to workflow events.<br /> <br /> == '''Participants &amp; Groups''' ==<br /> Defines who is responsible for executing the task.<br /> <br /> Tasks can be assigned to:<br /> <br /> •individual users<br /> <br /> •teams<br /> <br /> •business groups<br /> <br /> •external partners<br /> <br /> === '''Add Business Group Participant''' ===<br /> Adds a specific user belonging to a business group.<br /> <br /> Example:<br /> <br /> •doctor<br /> <br /> •operations manager<br /> <br /> === '''Add Business Group''' ===<br /> Assigns the entire group.<br /> <br /> Example groups:<br /> <br /> •MOC Operations Team<br /> <br /> •MOC Medical Team<br /> <br /> This ensures that any available member of the group can execute the task.<br /> <br /> === '''Request Task With''' ===<br /> Associates the task template with partners, groups, or users.<br /> <br /> Examples shown in mockup:<br /> <br /> •MOC Operations Team<br /> <br /> •MOC Medical Team<br /> <br /> •External Doctors<br /> <br /> •MSC Cruises<br /> <br /> •LH Technics MUC<br /> <br /> •Individual users<br /> <br /> A search field allows filtering participants.<br /> <br /> == '''Functional Placeholders''' ==<br /> Panel: '''Available functional placeholders'''<br /> <br /> These placeholders allow dynamic values to be inserted into task text.<br /> <br /> Examples:<br /> {| class=&quot;wikitable&quot;<br /> |+<br /> !Placeholder<br /> !Purpose<br /> |-<br /> |Travel partner<br /> |Inserts travel partner name<br /> |-<br /> |Pasenger (PAX) <br /> |Inserts passenger name<br /> |-<br /> |Requesting party<br /> |Shows who requested the service<br /> |-<br /> |Service delivery partner<br /> |Shows ground service provider<br /> |}<br /> When a task is generated, placeholders are automatically replaced with real values.<br /> <br /> == '''Associated Services''' ==<br /> Links the task template to one or more services.<br /> <br /> Example from mockup:<br /> <br /> •WENOLL<br /> <br /> •STRETCHER<br /> <br /> Important:<br /> <br /> These are '''services''', not only travel services.<br /> <br /> Purpose:<br /> <br /> •ensures that correct templates are suggested when specific services are used<br /> <br /> •improves task automation accuracy<br /> <br /> == '''Data Protection / Task Data Sharing with External Partners''' ==<br /> Defines which information external partners can access when tasks are shared with them.<br /> <br /> This ensures compliance with '''data protection regulations'''.<br /> <br /> === '''Share Case Base Information''' ===<br /> Shares basic case information:<br /> <br /> •case ID<br /> <br /> •passenger name<br /> <br /> •case status<br /> <br /> === '''Share Case Itinerary Information''' ===<br /> Allows partners to see:<br /> <br /> •flights<br /> <br /> •segments<br /> <br /> •travel itinerary<br /> <br /> === '''Share Case Ticketing Information''' ===<br /> Allows access to:<br /> <br /> •booking<br /> <br /> •PNR<br /> <br /> •ticket information<br /> <br /> === '''Allow Editing Case Ticketing Information''' ===<br /> Allows partners to modify ticket data.<br /> <br /> This option becomes available '''only when ticketing information sharing is enabled'''.<br /> <br /> === '''Share Case Requested Services Information''' ===<br /> Allows partners to see which services were requested.<br /> <br /> Examples:<br /> <br /> •stretcher<br /> <br /> •oxygen<br /> <br /> •escort<br /> <br /> === '''Share Case Medical Information''' ===<br /> Allows sharing of medical data related to the case.<br /> <br /> Example:<br /> <br /> •MEDA information<br /> <br /> This option should be enabled only when medically necessary.<br /> <br /> [[File:Task templates adm edit.png|none|thumb]]<br /> <br /> == Related articles ==<br /> [[Dev:LH MOC Admin-Task template administration Translations|Translations]]</div>

Mionamilosevic https://wiki.kordeus.com/index.php?title=File:Task_templates_adm_edit.png&diff=3206 2026-03-06T13:20:10Z

<p>Mionamilosevic: </p> <hr /> <div>Task templates adm edit</div>

Mionamilosevic https://wiki.kordeus.com/index.php?title=File:Task_templates_adm.png&diff=3205 2026-03-06T13:19:39Z

<p>Mionamilosevic: </p> <hr /> <div>Task templates adm</div>

Mionamilosevic https://wiki.kordeus.com/index.php?title=Dev:LH_MOC_Admin-Task_template_administration&diff=3204 2026-03-06T13:08:34Z

<p>Mionamilosevic: Created page with &quot;The Task Template Administration module allows administrators to define standardized operational tasks that can be automatically or manually generated during case workflows. Task templates help ensure that recurring operational actions are: •consistent •clearly documented •assigned to the correct participants •executed within defined deadlines Typical examples of tasks include: •Operational checks •Medical verification •Service confirmations •Co...&quot;</p> <hr /> <div>The Task Template Administration module allows administrators to define standardized operational tasks that can be automatically or manually generated during case workflows.<br /> <br /> Task templates help ensure that recurring operational actions are:<br /> <br /> •consistent<br /> <br /> •clearly documented<br /> <br /> •assigned to the correct participants<br /> <br /> •executed within defined deadlines<br /> <br /> Typical examples of tasks include:<br /> <br /> •Operational checks<br /> <br /> •Medical verification<br /> <br /> •Service confirmations<br /> <br /> •Communication with partners<br /> <br /> •Follow-up reminders<br /> <br /> •Documentation checks<br /> <br /> Task templates support:<br /> <br /> •multilingual communication<br /> <br /> •dynamic placeholders<br /> <br /> •service associations<br /> <br /> •priority management<br /> <br /> •deadline automation<br /> <br /> •assignment to teams, groups, or individuals<br /> <br /> •controlled data sharing with external partners<br /> <br /> These templates are used throughout the system to support Medical Operation Center (MOC) workflows.<br /> <br /> == '''Task Template Groups''' ==<br /> Task Template Groups organize task templates into logical categories.<br /> <br /> Grouping templates improves:<br /> <br /> •navigation<br /> <br /> •administration<br /> <br /> •workflow clarity<br /> <br /> •task discovery<br /> <br /> Examples of groups shown in the system:<br /> {| class=&quot;wikitable&quot;<br /> |+<br /> !Group<br /> !Typical use<br /> |-<br /> |General<br /> |Common operational tasks<br /> |-<br /> |Sitiing case<br /> |Tasks specific to sitting passengers<br /> |-<br /> |Stretcher<br /> |Stretcher related operational tasks<br /> |-<br /> |Oxygen Concentrators<br /> |Oxygen service handling<br /> |-<br /> |SVAN<br /> |Special assistance services/pet related<br /> |-<br /> |Travel partners<br /> |Partner coordination tasks<br /> |-<br /> |Whatever (Free text)<br /> |Custom operational tasks<br /> |}<br /> Each group contains one or more templates.<br /> <br /> == '''Task Template Group Overview''' ==<br /> Displays all templates belonging to the selected task template group.<br /> <br /> Example shown in mockup:<br /> <br /> '''Contents of task template group: General'''<br /> <br /> '''Table Columns'''<br /> <br /> '''Column''' '''Description'''<br /> <br /> Name Name of the task template<br /> <br /> <br /> '''Row Actions'''<br /> <br /> '''Edit (✏️)''' Opens the '''Task Template Editor''' for modifying the template.<br /> <br /> '''Delete (🗑)''' Removes the task template.<br /> <br /> Deletion is restricted if the template is used in active workflows.<br /> <br /> <br /> '''Buttons'''<br /> <br /> '''Add new''' Creates a new task template inside the selected group.<br /> <br /> <br /> '''Search (🔍)''' Filters templates by name.<br /> <br /> == '''Task Template Editor''' ==<br /> The Task Template Editor defines how a task behaves when it is generated in a workflow.<br /> <br /> This includes:<br /> <br /> •content<br /> <br /> •responsible participants<br /> <br /> •deadlines<br /> <br /> •priority<br /> <br /> •service associations<br /> <br /> •data sharing permissions<br /> <br /> == '''Task Definition''' ==<br /> '''Internal Name'''<br /> <br /> Internal identifier for the template.<br /> <br /> Used for:<br /> <br /> •administration<br /> <br /> •searching<br /> <br /> •system reference<br /> <br /> Example: Lufthansa Technics DE<br /> <br /> <br /> '''Communication (Language Tabs)'''<br /> <br /> Supports multilingual task communication.<br /> <br /> Each language version contains:<br /> <br /> •task subject<br /> <br /> •task description<br /> <br /> This ensures that tasks are displayed in the user’s language.<br /> <br /> === '''Task Subject''' ===<br /> Defines the short title of the task.<br /> <br /> Example: Check ESCORT NON-Upgrade SK<br /> <br /> This title appears in:<br /> <br /> •task lists<br /> <br /> •notifications<br /> <br /> •workflow views<br /> <br /> === '''Description''' ===<br /> Detailed explanation of the task.<br /> <br /> Used to provide instructions to the user performing the task.<br /> <br /> Examples:<br /> <br /> •operational instructions<br /> <br /> •service procedures<br /> <br /> •reminders<br /> <br /> •documentation requirements<br /> <br /> This field can also include instructional text helpful for new employees.<br /> <br /> === '''Task Type''' ===<br /> Dropdown defining the nature of the task.<br /> <br /> Typical options include:<br /> {| class=&quot;wikitable&quot;<br /> |+<br /> !Type<br /> !Purpose<br /> |-<br /> |Reminder<br /> |Informational task<br /> |-<br /> |Action<br /> |Task requiring operational action<br /> |-<br /> |Approval<br /> |Task requiring approval<br /> |}<br /> Task type influences how the task appears in the system and actions related to it.<br /> <br /> === '''Priority''' ===<br /> Marks the task as high priority.<br /> <br /> Priority tasks:<br /> <br /> •appear highlighted in task lists<br /> <br /> •are handled before normal tasks<br /> <br /> === '''Due Date''' ===<br /> Defines when the task must be completed.<br /> <br /> Options:<br /> {| class=&quot;wikitable&quot;<br /> |+<br /> !Option<br /> !Description<br /> |-<br /> |Immediately<br /> |Task appears instantly<br /> |-<br /> |In hours<br /> |Deadline defined in hours<br /> |-<br /> |In days<br /> |Deadline defined in days<br /> |}<br /> This allows tasks to be automatically scheduled relative to workflow events.<br /> <br /> == '''Participants &amp; Groups''' ==<br /> Defines who is responsible for executing the task.<br /> <br /> Tasks can be assigned to:<br /> <br /> •individual users<br /> <br /> •teams<br /> <br /> •business groups<br /> <br /> •external partners<br /> <br /> === '''Add Business Group Participant''' ===<br /> Adds a specific user belonging to a business group.<br /> <br /> Example:<br /> <br /> •doctor<br /> <br /> •operations manager<br /> <br /> === '''Add Business Group''' ===<br /> Assigns the entire group.<br /> <br /> Example groups:<br /> <br /> •MOC Operations Team<br /> <br /> •MOC Medical Team<br /> <br /> This ensures that any available member of the group can execute the task.<br /> <br /> === '''Request Task With''' ===<br /> Associates the task template with partners, groups, or users.<br /> <br /> Examples shown in mockup:<br /> <br /> •MOC Operations Team<br /> <br /> •MOC Medical Team<br /> <br /> •External Doctors<br /> <br /> •MSC Cruises<br /> <br /> •LH Technics MUC<br /> <br /> •Individual users<br /> <br /> A search field allows filtering participants.<br /> <br /> == '''Functional Placeholders''' ==<br /> Panel: '''Available functional placeholders'''<br /> <br /> These placeholders allow dynamic values to be inserted into task text.<br /> <br /> Examples:<br /> {| class=&quot;wikitable&quot;<br /> |+<br /> !Placeholder<br /> !Purpose<br /> |-<br /> |Travel partner<br /> |Inserts travel partner name<br /> |-<br /> |Pasenger (PAX) <br /> |Inserts passenger name<br /> |-<br /> |Requesting party<br /> |Shows who requested the service<br /> |-<br /> |Service delivery partner<br /> |Shows ground service provider<br /> |}<br /> When a task is generated, placeholders are automatically replaced with real values.<br /> <br /> == '''Associated Services''' ==<br /> Links the task template to one or more services.<br /> <br /> Example from mockup:<br /> <br /> •WENOLL<br /> <br /> •STRETCHER<br /> <br /> Important:<br /> <br /> These are '''services''', not only travel services.<br /> <br /> Purpose:<br /> <br /> •ensures that correct templates are suggested when specific services are used<br /> <br /> •improves task automation accuracy<br /> <br /> == '''Data Protection / Task Data Sharing with External Partners''' ==<br /> Defines which information external partners can access when tasks are shared with them.<br /> <br /> This ensures compliance with '''data protection regulations'''.<br /> <br /> === '''Share Case Base Information''' ===<br /> Shares basic case information:<br /> <br /> •case ID<br /> <br /> •passenger name<br /> <br /> •case status<br /> <br /> === '''Share Case Itinerary Information''' ===<br /> Allows partners to see:<br /> <br /> •flights<br /> <br /> •segments<br /> <br /> •travel itinerary<br /> <br /> === '''Share Case Ticketing Information''' ===<br /> Allows access to:<br /> <br /> •booking<br /> <br /> •PNR<br /> <br /> •ticket information<br /> <br /> === '''Allow Editing Case Ticketing Information''' ===<br /> Allows partners to modify ticket data.<br /> <br /> This option becomes available '''only when ticketing information sharing is enabled'''.<br /> <br /> === '''Share Case Requested Services Information''' ===<br /> Allows partners to see which services were requested.<br /> <br /> Examples:<br /> <br /> •stretcher<br /> <br /> •oxygen<br /> <br /> •escort<br /> <br /> === '''Share Case Medical Information''' ===<br /> Allows sharing of medical data related to the case.<br /> <br /> Example:<br /> <br /> •MEDA information<br /> <br /> This option should be enabled only when medically necessary.<br /> <br /> == Related articles ==<br /> [[Dev:LH MOC Admin-Task template administration Translations|Translations]]</div>

Mionamilosevic https://wiki.kordeus.com/index.php?title=Dev:LH_MOC_Admin-Task_template_administration_Translations&diff=3203 2026-03-06T13:08:20Z

<p>Mionamilosevic: Created page with &quot;{| class=&quot;wikitable&quot; |&#039;&#039;&#039;Application&#039;&#039;&#039; |Task template administration |- |&#039;&#039;&#039;Languages&#039;&#039;&#039; |en_en, de_de |}&quot;</p> <hr /> <div>{| class=&quot;wikitable&quot;<br /> |'''Application'''<br /> |Task template administration<br /> |-<br /> |'''Languages'''<br /> |en_en, de_de<br /> |}</div>

Mionamilosevic https://wiki.kordeus.com/index.php?title=Dev:LH_MOC_Admin-Travel_services&diff=3155 2026-03-04T11:15:05Z

<p>Mionamilosevic: </p> <hr /> <div>The Travel Service Administration module is the central configuration area where all operational services that can be requested for a passenger are defined and managed.<br /> <br /> A Travel Service represents a concrete operational action related to a passenger’s journey.<br /> <br /> Examples include:<br /> <br /> •Wheelchair assistance<br /> <br /> •Stretcher transport (STCR)<br /> <br /> •Oxygen on board (POXY)<br /> <br /> •Escort services<br /> <br /> •Ambulance transport to/from airport<br /> <br /> •Medical device transport (CPAP/BIPAP)<br /> <br /> •Additional seating<br /> <br /> •Handling of medical baggage<br /> <br /> These services may require:<br /> <br /> •Medical approval<br /> <br /> •Operational approval<br /> <br /> •Ground handling coordination<br /> <br /> •Service delivery partner involvement<br /> <br /> •Task automation<br /> <br /> •Capacity checks<br /> <br /> The module defines '''how a service behaves in the system''', including:<br /> <br /> •Availability<br /> <br /> •Dependencies<br /> <br /> •Approval workflows<br /> <br /> •Automation rules<br /> <br /> •Service visibility<br /> <br /> <br /> The '''Travel Service Administration module''' defines the operational backbone of passenger assistance and medical service handling.<br /> <br /> It controls:<br /> <br /> •how services appear<br /> <br /> •who can request them<br /> <br /> •how they trigger other services<br /> <br /> •how approvals work<br /> <br /> •how operational workflows are automated<br /> <br /> Together with:<br /> <br /> •'''SPFT'''<br /> <br /> •'''Service Delivery Partners'''<br /> <br /> •'''Travel Partners'''<br /> <br /> this module forms the core system for managing passenger service operations.<br /> <br /> == '''Travel Service List View''' ==<br /> '''Purpose'''<br /> <br /> Displays all configured Travel Services and provides a central entry point for managing them.<br /> <br /> <br /> '''Table Fields'''<br /> <br /> '''Field''' '''Description'''<br /> <br /> Carrier Airline or operator responsible for the service<br /> <br /> Service Code Unique identifier for the service<br /> <br /> SPFT Service Process Flow Type assigned to the service<br /> <br /> Name Display name of the service<br /> <br /> Service Delivery Indicates how the service is delivered (port, segment, or partner)<br /> <br /> === '''Actions''' ===<br /> '''Add New ➕'''<br /> <br /> Creates a new travel service.<br /> <br /> '''Search 🔍'''<br /> <br /> Allows searching by:<br /> <br /> •Service name<br /> <br /> •Code<br /> <br /> •Carrier<br /> <br /> '''Edit ✏️'''<br /> <br /> Opens the configuration of the selected service.<br /> <br /> '''Delete 🗑️'''<br /> <br /> Removes the service.<br /> <br /> Deletion is restricted if:<br /> <br /> •The service is used in workflows<br /> <br /> •The service is referenced in automation rules<br /> <br /> •The service is assigned to delivery partners<br /> [[File:Travel services.png|none|thumb]]<br /> <br /> == '''Travel Service Configuration''' ==<br /> Each Travel Service is configured through three main sections:<br /> <br /> 1. Base Data<br /> <br /> 2. Service Tree Creation<br /> <br /> 3. Medical Approval<br /> <br /> == '''Base Data''' ==<br /> '''Purpose'''<br /> <br /> Defines the identity, classification, and availability logic of the travel service.<br /> <br /> This section determines '''how the service integrates into the service ecosystem'''.<br /> <br /> === '''General Information''' ===<br /> '''Code'''<br /> <br /> Unique identifier for the service.<br /> <br /> Example:STCR, POXY<br /> <br /> <br /> Used by:<br /> <br /> •backend systems<br /> <br /> •automation rules<br /> <br /> •integrations<br /> <br /> ==== '''Operating Carrier''' ====<br /> Defines which airline or carrier the service belongs to.<br /> <br /> Example:<br /> <br /> •Lufthansa<br /> <br /> •SWISS<br /> <br /> •Discover Airlines<br /> <br /> This enables carrier-specific configuration and rules.<br /> <br /> ==== '''Is Active''' ====<br /> Defines whether the service is currently available.<br /> <br /> Inactive services:<br /> <br /> •Cannot be requested<br /> <br /> •Remain stored for historical cases<br /> <br /> ==== '''Internal Name of Travel Service''' ====<br /> The display name used in the system and PAX portal.<br /> <br /> Example: Stretcher Transport, Passenger Oxygen Cylinder, Medical Escort<br /> <br /> ''Supports multilingual entries.''<br /> <br /> ==== '''Upload Icon''' ====<br /> Assigns an icon that visually represents the service.<br /> <br /> Icons appear in:<br /> <br /> •Passenger portal<br /> <br /> •Service selection screens<br /> <br /> •Backend UI<br /> <br /> === '''Service Network Compatibility''' ===<br /> Defines how the service integrates into the global service ecosystem.<br /> <br /> ==== '''Global Travel Service Bindings''' ====<br /> Links the service to a '''global service definition'''.<br /> <br /> This ensures:<br /> <br /> •Standardized classification<br /> <br /> •Consistent behavior across carriers<br /> <br /> •Interoperability with network partners<br /> <br /> ==== '''Member of Service Group Key''' ====<br /> Defines which service group this service belongs to.<br /> <br /> Examples of groups:<br /> <br /> •Medical services<br /> <br /> •Assistance services<br /> <br /> •Informational services<br /> <br /> •Operational services<br /> <br /> Service groups help:<br /> <br /> •organize services<br /> <br /> •apply shared logic<br /> <br /> •simplify UI grouping<br /> <br /> === '''Service Availability Limitations''' ===<br /> Defines restrictions on where and how the service can be used.<br /> <br /> ==== '''Limited Availability by Port''' ====<br /> The service is only available at specific airports.<br /> <br /> Example:<br /> <br /> •Ambulance service only at FRA and MUC.<br /> <br /> ==== '''Limited Availability by Flight Number''' ====<br /> Allows defining specific flights where the service is available.<br /> <br /> Example:<br /> <br /> •Special medical equipment only on certain aircraft.<br /> <br /> ==== '''Limited to Used Craft Type''' ====<br /> Restricts the service based on aircraft type.<br /> <br /> Example:<br /> <br /> •Stretcher services only on widebody aircraft.<br /> <br /> === '''Vessel Manipulation Service''' ===<br /> Indicates that the service requires physical work on the aircraft.<br /> <br /> Examples:<br /> <br /> •Stretcher mounting<br /> <br /> •Equipment installation<br /> <br /> These services trigger '''additional preparation workflows'''.<br /> <br /> === '''Member Service Requestability''' ===<br /> Defines who can request the service.<br /> <br /> ==== '''Requested by Passenger''' ====<br /> Service can be requested directly in the PAX portal.<br /> <br /> Example:<br /> <br /> •Escort<br /> <br /> •Medical assistance<br /> <br /> ==== '''Requested by Travel Partner''' ====<br /> Service can be requested by external partners.<br /> <br /> Example:<br /> <br /> •Medical agencies<br /> <br /> •Assistance companies<br /> <br /> ==== '''Requested Internally''' ====<br /> Service can only be added by internal staff.<br /> <br /> Example:<br /> <br /> •Technical handling services<br /> <br /> •Mounting tasks<br /> <br /> === '''Service Process Flow Type (SPFT)''' ===<br /> Assigns the service to a '''Service Process Flow Type'''.<br /> <br /> Examples:<br /> {| class=&quot;wikitable&quot;<br /> |+<br /> !Code<br /> !Description<br /> |-<br /> |PWD<br /> |Passenger with disabilities<br /> |-<br /> |MEDA<br /> |Passenger with medical conditions<br /> |-<br /> |INF<br /> |Informational services<br /> |-<br /> |ISS<br /> |Service delivery services<br /> |-<br /> |PPP<br /> |Pre/Post processing services<br /> |}<br /> SPFT controls:<br /> <br /> approval workflows<br /> <br /> service visibility<br /> <br /> automation behaviour<br /> <br /> regulatory requirements<br /> <br /> === '''Insecure Handling Advice Communication''' ===<br /> Defines fallback communication channels.<br /> <br /> Used when digital integration is unavailable.<br /> <br /> Examples:<br /> <br /> •email notifications<br /> <br /> •telex messages<br /> <br /> These recipients are always notified regardless of service delivery partner.<br /> <br /> [[File:TS base data.png|none|thumb]]<br /> <br /> <br /> == '''Service Tree Creation''' ==<br /> '''Purpose'''<br /> <br /> Defines '''dependencies and relationships between services'''.<br /> <br /> This allows services to automatically trigger or recommend other services.<br /> <br /> === '''Service Ordering''' ===<br /> Defines which services should be suggested when another service is requested.<br /> <br /> Example:<br /> <br /> Requesting '''STCR (Stretcher)''' automatically suggests:<br /> <br /> •Ambulance transport<br /> <br /> •Escort service<br /> <br /> •Medical oxygen<br /> <br /> <br /> '''Force Option'''<br /> <br /> If enabled, the suggested service is '''automatically added'''.<br /> <br /> If disabled, the user can accept or reject the suggestion.<br /> <br /> === '''Backend Service Dependency''' ===<br /> Defines automatic service creation in backend workflows.<br /> <br /> Example:<br /> <br /> When a '''Stretcher request''' is created:<br /> <br /> Automatically add:<br /> <br /> •Stretcher mounting<br /> <br /> •Stretcher dismantling<br /> <br /> These services are invisible to the passenger.<br /> <br /> === '''Vessel Manipulation Service''' ===<br /> Defines services that require preparation work on the aircraft.<br /> <br /> Examples:<br /> <br /> •stretcher mounting<br /> <br /> •equipment installation<br /> <br /> •seat removal<br /> <br /> <br /> '''Timing Options'''<br /> <br /> Defines when preparation must occur:<br /> {| class=&quot;wikitable&quot;<br /> |+<br /> !Option<br /> !Description<br /> |-<br /> |Before segment starts<br /> |preparation before flighr departure<br /> |-<br /> |After segment end<br /> |post-flight removal<br /> |-<br /> |Before rotation start<br /> |before aircraft operational rotation<br /> |-<br /> |After rotation end<br /> |after final segment<br /> |}<br /> [[File:TS service tree creation.png|none|thumb]]<br /> <br /> == '''Medical Approval''' ==<br /> '''Purpose'''<br /> <br /> Defines how medical professionals interact with service requests.<br /> <br /> Used when the service requires medical evaluation.<br /> <br /> === '''Medical Approval Process''' ===<br /> Options:<br /> <br /> '''Force Freestyle Entry for Approval'''<br /> <br /> Doctor must write an explanation when approving.<br /> <br /> '''Allow Freestyle Request for More Information'''<br /> <br /> Doctor can request additional documentation from the requester.<br /> <br /> '''Force Freestyle Denial Reason'''<br /> <br /> Doctor must provide reason when rejecting.<br /> <br /> <br /> '''Typical Medical Actions'''<br /> <br /> Defines '''predefined responses for doctors'''.<br /> <br /> These responses appear as one-click options.<br /> <br /> Examples:<br /> {| class=&quot;wikitable&quot;<br /> !Action<br /> !Description<br /> |-<br /> |Condition approval<br /> |Approve with conditions<br /> |-<br /> |Request more info<br /> |Ask for more documentation<br /> |-<br /> |Reject<br /> |Deny the request<br /> |}<br /> ''These actions simplify decision making.''<br /> [[File:TS medical approval.png|none|thumb]]<br /> <br /> == '''Operational Workflow Impact''' ==<br /> Travel Services directly affect:<br /> <br /> '''Passenger Portal'''<br /> <br /> Determines which services passengers can request.<br /> <br /> '''Task Automation'''<br /> <br /> Triggers tasks for:<br /> <br /> •operations teams<br /> <br /> •medical teams<br /> <br /> •service delivery partners<br /> <br /> <br /> '''Ground Handling'''<br /> <br /> Links services to ground providers.<br /> <br /> <br /> '''Regulatory Compliance'''<br /> <br /> Ensures proper documentation (e.g., MEDIF).<br /> <br /> <br /> '''Service Dependencies'''<br /> <br /> Automatically generates related services.<br /> <br /> == Related articles ==<br /> [[Dev:LH MOC Admin-Travel services Translations|Translations]]</div>

Mionamilosevic https://wiki.kordeus.com/index.php?title=Dev:LH_MOC_Admin-Travel_services_Translations&diff=3154 2026-03-04T11:14:52Z

<p>Mionamilosevic: Created page with &quot;{| class=&quot;wikitable&quot; |&#039;&#039;&#039;Application&#039;&#039;&#039; |Travel services |- |&#039;&#039;&#039;Languages&#039;&#039;&#039; |en_en, de_de |} {| class=&quot;wikitable&quot; |+ !Code !Comment !en_en !de_de |- | | | | |}&quot;</p> <hr /> <div>{| class=&quot;wikitable&quot;<br /> |'''Application'''<br /> |Travel services<br /> |-<br /> |'''Languages'''<br /> |en_en, de_de<br /> |}<br /> {| class=&quot;wikitable&quot;<br /> |+<br /> !Code<br /> !Comment<br /> !en_en<br /> !de_de<br /> |-<br /> |<br /> |<br /> |<br /> |<br /> |}</div>

Mionamilosevic https://wiki.kordeus.com/index.php?title=Dev:LH_MOC_Admin-Travel_services&diff=3153 2026-03-04T11:13:59Z

<p>Mionamilosevic: </p> <hr /> <div>The Travel Service Administration module is the central configuration area where all operational services that can be requested for a passenger are defined and managed.<br /> <br /> A Travel Service represents a concrete operational action related to a passenger’s journey.<br /> <br /> Examples include:<br /> <br /> •Wheelchair assistance<br /> <br /> •Stretcher transport (STCR)<br /> <br /> •Oxygen on board (POXY)<br /> <br /> •Escort services<br /> <br /> •Ambulance transport to/from airport<br /> <br /> •Medical device transport (CPAP/BIPAP)<br /> <br /> •Additional seating<br /> <br /> •Handling of medical baggage<br /> <br /> These services may require:<br /> <br /> •Medical approval<br /> <br /> •Operational approval<br /> <br /> •Ground handling coordination<br /> <br /> •Service delivery partner involvement<br /> <br /> •Task automation<br /> <br /> •Capacity checks<br /> <br /> The module defines '''how a service behaves in the system''', including:<br /> <br /> •Availability<br /> <br /> •Dependencies<br /> <br /> •Approval workflows<br /> <br /> •Automation rules<br /> <br /> •Service visibility<br /> <br /> <br /> The '''Travel Service Administration module''' defines the operational backbone of passenger assistance and medical service handling.<br /> <br /> It controls:<br /> <br /> •how services appear<br /> <br /> •who can request them<br /> <br /> •how they trigger other services<br /> <br /> •how approvals work<br /> <br /> •how operational workflows are automated<br /> <br /> Together with:<br /> <br /> •'''SPFT'''<br /> <br /> •'''Service Delivery Partners'''<br /> <br /> •'''Travel Partners'''<br /> <br /> this module forms the core system for managing passenger service operations.<br /> <br /> == '''Travel Service List View''' ==<br /> '''Purpose'''<br /> <br /> Displays all configured Travel Services and provides a central entry point for managing them.<br /> <br /> <br /> '''Table Fields'''<br /> <br /> '''Field''' '''Description'''<br /> <br /> Carrier Airline or operator responsible for the service<br /> <br /> Service Code Unique identifier for the service<br /> <br /> SPFT Service Process Flow Type assigned to the service<br /> <br /> Name Display name of the service<br /> <br /> Service Delivery Indicates how the service is delivered (port, segment, or partner)<br /> <br /> === '''Actions''' ===<br /> '''Add New ➕'''<br /> <br /> Creates a new travel service.<br /> <br /> '''Search 🔍'''<br /> <br /> Allows searching by:<br /> <br /> •Service name<br /> <br /> •Code<br /> <br /> •Carrier<br /> <br /> '''Edit ✏️'''<br /> <br /> Opens the configuration of the selected service.<br /> <br /> '''Delete 🗑️'''<br /> <br /> Removes the service.<br /> <br /> Deletion is restricted if:<br /> <br /> •The service is used in workflows<br /> <br /> •The service is referenced in automation rules<br /> <br /> •The service is assigned to delivery partners<br /> [[File:Travel services.png|none|thumb]]<br /> <br /> == '''Travel Service Configuration''' ==<br /> Each Travel Service is configured through three main sections:<br /> <br /> 1. Base Data<br /> <br /> 2. Service Tree Creation<br /> <br /> 3. Medical Approval<br /> <br /> == '''Base Data''' ==<br /> '''Purpose'''<br /> <br /> Defines the identity, classification, and availability logic of the travel service.<br /> <br /> This section determines '''how the service integrates into the service ecosystem'''.<br /> <br /> === '''General Information''' ===<br /> '''Code'''<br /> <br /> Unique identifier for the service.<br /> <br /> Example:STCR, POXY<br /> <br /> <br /> Used by:<br /> <br /> •backend systems<br /> <br /> •automation rules<br /> <br /> •integrations<br /> <br /> ==== '''Operating Carrier''' ====<br /> Defines which airline or carrier the service belongs to.<br /> <br /> Example:<br /> <br /> •Lufthansa<br /> <br /> •SWISS<br /> <br /> •Discover Airlines<br /> <br /> This enables carrier-specific configuration and rules.<br /> <br /> ==== '''Is Active''' ====<br /> Defines whether the service is currently available.<br /> <br /> Inactive services:<br /> <br /> •Cannot be requested<br /> <br /> •Remain stored for historical cases<br /> <br /> ==== '''Internal Name of Travel Service''' ====<br /> The display name used in the system and PAX portal.<br /> <br /> Example: Stretcher Transport, Passenger Oxygen Cylinder, Medical Escort<br /> <br /> ''Supports multilingual entries.''<br /> <br /> ==== '''Upload Icon''' ====<br /> Assigns an icon that visually represents the service.<br /> <br /> Icons appear in:<br /> <br /> •Passenger portal<br /> <br /> •Service selection screens<br /> <br /> •Backend UI<br /> <br /> === '''Service Network Compatibility''' ===<br /> Defines how the service integrates into the global service ecosystem.<br /> <br /> ==== '''Global Travel Service Bindings''' ====<br /> Links the service to a '''global service definition'''.<br /> <br /> This ensures:<br /> <br /> •Standardized classification<br /> <br /> •Consistent behavior across carriers<br /> <br /> •Interoperability with network partners<br /> <br /> ==== '''Member of Service Group Key''' ====<br /> Defines which service group this service belongs to.<br /> <br /> Examples of groups:<br /> <br /> •Medical services<br /> <br /> •Assistance services<br /> <br /> •Informational services<br /> <br /> •Operational services<br /> <br /> Service groups help:<br /> <br /> •organize services<br /> <br /> •apply shared logic<br /> <br /> •simplify UI grouping<br /> <br /> === '''Service Availability Limitations''' ===<br /> Defines restrictions on where and how the service can be used.<br /> <br /> ==== '''Limited Availability by Port''' ====<br /> The service is only available at specific airports.<br /> <br /> Example:<br /> <br /> •Ambulance service only at FRA and MUC.<br /> <br /> ==== '''Limited Availability by Flight Number''' ====<br /> Allows defining specific flights where the service is available.<br /> <br /> Example:<br /> <br /> •Special medical equipment only on certain aircraft.<br /> <br /> ==== '''Limited to Used Craft Type''' ====<br /> Restricts the service based on aircraft type.<br /> <br /> Example:<br /> <br /> •Stretcher services only on widebody aircraft.<br /> <br /> === '''Vessel Manipulation Service''' ===<br /> Indicates that the service requires physical work on the aircraft.<br /> <br /> Examples:<br /> <br /> •Stretcher mounting<br /> <br /> •Equipment installation<br /> <br /> These services trigger '''additional preparation workflows'''.<br /> <br /> === '''Member Service Requestability''' ===<br /> Defines who can request the service.<br /> <br /> ==== '''Requested by Passenger''' ====<br /> Service can be requested directly in the PAX portal.<br /> <br /> Example:<br /> <br /> •Escort<br /> <br /> •Medical assistance<br /> <br /> ==== '''Requested by Travel Partner''' ====<br /> Service can be requested by external partners.<br /> <br /> Example:<br /> <br /> •Medical agencies<br /> <br /> •Assistance companies<br /> <br /> ==== '''Requested Internally''' ====<br /> Service can only be added by internal staff.<br /> <br /> Example:<br /> <br /> •Technical handling services<br /> <br /> •Mounting tasks<br /> <br /> === '''Service Process Flow Type (SPFT)''' ===<br /> Assigns the service to a '''Service Process Flow Type'''.<br /> <br /> Examples:<br /> {| class=&quot;wikitable&quot;<br /> |+<br /> !Code<br /> !Description<br /> |-<br /> |PWD<br /> |Passenger with disabilities<br /> |-<br /> |MEDA<br /> |Passenger with medical conditions<br /> |-<br /> |INF<br /> |Informational services<br /> |-<br /> |ISS<br /> |Service delivery services<br /> |-<br /> |PPP<br /> |Pre/Post processing services<br /> |}<br /> SPFT controls:<br /> <br /> approval workflows<br /> <br /> service visibility<br /> <br /> automation behaviour<br /> <br /> regulatory requirements<br /> <br /> === '''Insecure Handling Advice Communication''' ===<br /> Defines fallback communication channels.<br /> <br /> Used when digital integration is unavailable.<br /> <br /> Examples:<br /> <br /> •email notifications<br /> <br /> •telex messages<br /> <br /> These recipients are always notified regardless of service delivery partner.<br /> <br /> [[File:TS base data.png|none|thumb]]<br /> <br /> <br /> == '''Service Tree Creation''' ==<br /> '''Purpose'''<br /> <br /> Defines '''dependencies and relationships between services'''.<br /> <br /> This allows services to automatically trigger or recommend other services.<br /> <br /> === '''Service Ordering''' ===<br /> Defines which services should be suggested when another service is requested.<br /> <br /> Example:<br /> <br /> Requesting '''STCR (Stretcher)''' automatically suggests:<br /> <br /> •Ambulance transport<br /> <br /> •Escort service<br /> <br /> •Medical oxygen<br /> <br /> <br /> '''Force Option'''<br /> <br /> If enabled, the suggested service is '''automatically added'''.<br /> <br /> If disabled, the user can accept or reject the suggestion.<br /> <br /> === '''Backend Service Dependency''' ===<br /> Defines automatic service creation in backend workflows.<br /> <br /> Example:<br /> <br /> When a '''Stretcher request''' is created:<br /> <br /> Automatically add:<br /> <br /> •Stretcher mounting<br /> <br /> •Stretcher dismantling<br /> <br /> These services are invisible to the passenger.<br /> <br /> === '''Vessel Manipulation Service''' ===<br /> Defines services that require preparation work on the aircraft.<br /> <br /> Examples:<br /> <br /> •stretcher mounting<br /> <br /> •equipment installation<br /> <br /> •seat removal<br /> <br /> <br /> '''Timing Options'''<br /> <br /> Defines when preparation must occur:<br /> {| class=&quot;wikitable&quot;<br /> |+<br /> !Option<br /> !Description<br /> |-<br /> |Before segment starts<br /> |preparation before flighr departure<br /> |-<br /> |After segment end<br /> |post-flight removal<br /> |-<br /> |Before rotation start<br /> |before aircraft operational rotation<br /> |-<br /> |After rotation end<br /> |after final segment<br /> |}<br /> [[File:TS service tree creation.png|none|thumb]]<br /> <br /> == '''Medical Approval''' ==<br /> '''Purpose'''<br /> <br /> Defines how medical professionals interact with service requests.<br /> <br /> Used when the service requires medical evaluation.<br /> <br /> === '''Medical Approval Process''' ===<br /> Options:<br /> <br /> '''Force Freestyle Entry for Approval'''<br /> <br /> Doctor must write an explanation when approving.<br /> <br /> '''Allow Freestyle Request for More Information'''<br /> <br /> Doctor can request additional documentation from the requester.<br /> <br /> '''Force Freestyle Denial Reason'''<br /> <br /> Doctor must provide reason when rejecting.<br /> <br /> <br /> '''Typical Medical Actions'''<br /> <br /> Defines '''predefined responses for doctors'''.<br /> <br /> These responses appear as one-click options.<br /> <br /> Examples:<br /> {| class=&quot;wikitable&quot;<br /> !Action<br /> !Description<br /> |-<br /> |Condition approval<br /> |Approve with conditions<br /> |-<br /> |Request more info<br /> |Ask for more documentation<br /> |-<br /> |Reject<br /> |Deny the request<br /> |}<br /> ''These actions simplify decision making.''<br /> [[File:TS medical approval.png|none|thumb]]<br /> <br /> == '''Operational Workflow Impact''' ==<br /> Travel Services directly affect:<br /> <br /> '''Passenger Portal'''<br /> <br /> Determines which services passengers can request.<br /> <br /> '''Task Automation'''<br /> <br /> Triggers tasks for:<br /> <br /> •operations teams<br /> <br /> •medical teams<br /> <br /> •service delivery partners<br /> <br /> <br /> '''Ground Handling'''<br /> <br /> Links services to ground providers.<br /> <br /> <br /> '''Regulatory Compliance'''<br /> <br /> Ensures proper documentation (e.g., MEDIF).<br /> <br /> <br /> '''Service Dependencies'''<br /> <br /> Automatically generates related services.</div>

Mionamilosevic https://wiki.kordeus.com/index.php?title=File:TS_medical_approval.png&diff=3152 2026-03-04T11:13:51Z

<p>Mionamilosevic: </p> <hr /> <div>TS medical approval</div>

Mionamilosevic https://wiki.kordeus.com/index.php?title=File:TS_service_tree_creation.png&diff=3151 2026-03-04T11:13:28Z

<p>Mionamilosevic: </p> <hr /> <div>TS service tree creation</div>

Mionamilosevic https://wiki.kordeus.com/index.php?title=File:TS_base_data.png&diff=3150 2026-03-04T11:13:03Z

<p>Mionamilosevic: </p> <hr /> <div>TS base data</div>

Mionamilosevic https://wiki.kordeus.com/index.php?title=File:Travel_services.png&diff=3149 2026-03-04T11:12:31Z

<p>Mionamilosevic: </p> <hr /> <div>Travel services</div>

Mionamilosevic https://wiki.kordeus.com/index.php?title=Dev:LH_Core_Admin-Service_Process_Flow_Type&diff=3147 2026-02-27T14:32:36Z

<p>Mionamilosevic: </p> <hr /> <div>The Service Process Flow Type Administration (SPFT) module defines high-level service categories and their behavioral logic within the Medical Operation Center (MOC) system.<br /> <br /> Each SPFT determines:<br /> <br /> •How a service appears in the PAX Portal<br /> <br /> •Whether it requires medical and/or operational approval<br /> <br /> •Whether MEDIF documentation is required<br /> <br /> •How it behaves in backend workflows<br /> <br /> •Which business participant groups are allowed to approve<br /> <br /> •How it is visually represented (icon &amp; color coding)<br /> <br /> SPFT acts as a meta-layer configuration that governs downstream behavior of all travel services assigned to that process type.<br /> <br /> == '''SPFT List View''' ==<br /> Displays all configured Service Process Flow Types.<br /> <br /> Each entry represents a service category that defines approval logic, visibility behavior, and automation rules.<br /> <br /> <br /> '''Fields'''<br /> <br /> '''Field''' '''Description'''<br /> <br /> Identifier Icon Visual icon representing this process type<br /> <br /> Code Unique SPFT code (e.g., PWD, MEDA, INF, ISS, PPP)<br /> <br /> Name Human-readable name of the service group<br /> <br /> '''Default Example'''<br /> <br /> '''Code''' '''Name'''<br /> <br /> PWD Services for PAX with disabilities<br /> <br /> MEDA Services for PAX with medical conditions<br /> <br /> INF Informational PAX Services<br /> <br /> ISS Service delivery services<br /> <br /> PPP Pre &amp; Postprocessing services<br /> <br /> '''Actions'''<br /> <br /> •'''Add new''' (➕)<br /> <br /> •'''Search'''<br /> <br /> •'''Edit''' (✏️)<br /> <br /> •'''Delete''' (🗑️)<br /> <br /> [[File:SPFT.png|none|thumb]]<br /> <br /> == '''SPFT Detail View''' ==<br /> Example shown: '''MEDA'''<br /> <br /> This page defines the operational behavior of a service category.<br /> <br /> === '''General Configuration''' ===<br /> '''Fields'''<br /> <br /> '''Code (required)'''<br /> <br /> Unique identifier of the SPFT.<br /> <br /> Example: MEDA<br /> <br /> === '''Service Color Code''' ===<br /> Hex color used in backend UI to visually mark requests belonging to this SPFT.<br /> <br /> Example: #FFA834<br /> <br /> Used for:<br /> <br /> •Backend case highlighting<br /> <br /> •Task visualization<br /> <br /> •Operational signaling<br /> <br /> === '''Name of Service Group (Multilingual)''' ===<br /> Defines the display name.<br /> <br /> Example: Medical Case Defining Service<br /> <br /> === '''Icon Tag (32x32)''' ===<br /> Icon displayed:<br /> <br /> •In service selection<br /> <br /> •In backend processing<br /> <br /> •In portal UI<br /> <br /> Actions:<br /> <br /> •Upload<br /> <br /> •Remove<br /> <br /> == '''Member Service Type Classification''' ==<br /> Defines how services belonging to this SPFT behave in the PAX Portal.<br /> <br /> Options:<br /> <br /> === '''1. Primary services for PAX''' ===<br /> •Displayed on main service selection screen<br /> <br /> •Manually selected by passenger<br /> <br /> === '''2. Primary informational services for PAX''' ===<br /> •Shown in second step of PAX portal (before finishing booking)<br /> <br /> •Used for informational add-ons<br /> <br /> === '''3. Secondary services automatically added by transport type''' ===<br /> Example:<br /> <br /> •Based on Bus / Train / Aircraft type<br /> <br /> •Added when primary service is requested<br /> <br /> === '''4. Secondary services added upon approval of primary service''' ===<br /> Example:<br /> <br /> •Mounting<br /> <br /> •Dismantling<br /> <br /> •Added after medical approval<br /> <br /> This directly drives:<br /> <br /> •Automatic service chaining<br /> <br /> •Task generation<br /> <br /> •Backend dependency creationž<br /> <br /> == '''Process Flow Settings (Approval Logic)''' ==<br /> Defines whether services of this SPFT require approval.<br /> <br /> <br /> '''Medical Approval Required'''<br /> <br /> Checkbox: Services of this type require approval by medical team<br /> <br /> If enabled:<br /> <br /> •Medical case workflow is triggered<br /> <br /> •Only authorized groups can approve<br /> <br /> Business participant groups selectable:<br /> <br /> •Operations Managers<br /> <br /> •Internal Doctors<br /> <br /> •External Doctors<br /> <br /> •Custom groups<br /> <br /> === '''Operations Approval Required''' ===<br /> Checkbox: Services of this type require approval by operations team<br /> <br /> If enabled:<br /> <br /> •Operations review required before confirmation<br /> <br /> •Tasks created accordingly<br /> <br /> Selectable groups:<br /> <br /> •Operations Managers<br /> <br /> •Operations Staff<br /> <br /> === '''What This Does Systemically''' ===<br /> When enabled:<br /> <br /> •Service enters approval state<br /> <br /> •Tasks created for assigned approval group<br /> <br /> •Final confirmation blocked until approval<br /> <br /> == '''MEDIF Configuration''' ==<br /> Defines whether MEDIF documentation is required.<br /> <br /> '''Options'''<br /> <br /> •Service does NOT require MEDIF<br /> <br /> •Service requires MEDIF<br /> <br /> '''Exception Handling'''<br /> <br /> Admin can define:<br /> <br /> '''Service''' '''Touched Regulatory Zone'''<br /> <br /> Oxygen Canada<br /> <br /> Oxygen US<br /> <br /> This means:<br /> <br /> Even if MEDIF is generally required, exceptions can be defined per:<br /> <br /> •Regulatory zone<br /> <br /> •Country<br /> <br /> •Service<br /> <br /> '''What It Controls'''<br /> <br /> •PAX document upload requirement<br /> <br /> •Case cannot proceed without MEDIF (unless exception applies)<br /> <br /> •Regulatory compliance enforcement<br /> <br /> == '''Delivered Service &amp; Regulatory Zone Mapping''' ==<br /> Allows defining:<br /> <br /> •Which service<br /> <br /> •Which regulatory zone<br /> <br /> •Whether MEDIF requirement is overridden<br /> <br /> Actions:<br /> <br /> •Add<br /> <br /> •Remove<br /> <br /> <br /> '''System Behavior Summary'''<br /> <br /> SPFT configuration directly impacts:<br /> <br /> '''Area''' '''Impact'''<br /> <br /> PAX Portal Service visibility &amp; placement<br /> <br /> Backend UI Color coding &amp; icon<br /> <br /> Approval Workflow Medical &amp; operational gating<br /> <br /> Task Engine Task creation triggers<br /> <br /> Automation Secondary service chaining<br /> <br /> Regulatory Compliance MEDIF enforcement<br /> [[File:SPFT detailss.png|none|thumb]]<br /> <br /> == '''Logical Dependencies''' ==<br /> SPFT interacts with:<br /> <br /> •Travel Service Administration<br /> <br /> •Service Delivery Partners<br /> <br /> •Task Template Engine<br /> <br /> •Segment &amp; Port availability logic<br /> <br /> •MEDIF validation system<br /> <br /> •Automation rules<br /> <br /> == Related articles ==<br /> [[Dev:LH Core Admin-Service Process Flow Type Translations|Translations]]</div>

Mionamilosevic https://wiki.kordeus.com/index.php?title=File:SPFT_detailss.png&diff=3146 2026-02-27T14:32:29Z

<p>Mionamilosevic: </p> <hr /> <div>SPFT detailss</div>

Mionamilosevic https://wiki.kordeus.com/index.php?title=Dev:LH_Core_Admin-Service_Process_Flow_Type&diff=3145 2026-02-27T14:31:20Z

<p>Mionamilosevic: </p> <hr /> <div>The Service Process Flow Type Administration (SPFT) module defines high-level service categories and their behavioral logic within the Medical Operation Center (MOC) system.<br /> <br /> Each SPFT determines:<br /> <br /> •How a service appears in the PAX Portal<br /> <br /> •Whether it requires medical and/or operational approval<br /> <br /> •Whether MEDIF documentation is required<br /> <br /> •How it behaves in backend workflows<br /> <br /> •Which business participant groups are allowed to approve<br /> <br /> •How it is visually represented (icon &amp; color coding)<br /> <br /> SPFT acts as a meta-layer configuration that governs downstream behavior of all travel services assigned to that process type.<br /> <br /> == '''SPFT List View''' ==<br /> Displays all configured Service Process Flow Types.<br /> <br /> Each entry represents a service category that defines approval logic, visibility behavior, and automation rules.<br /> <br /> <br /> '''Fields'''<br /> <br /> '''Field''' '''Description'''<br /> <br /> Identifier Icon Visual icon representing this process type<br /> <br /> Code Unique SPFT code (e.g., PWD, MEDA, INF, ISS, PPP)<br /> <br /> Name Human-readable name of the service group<br /> <br /> '''Default Example'''<br /> <br /> '''Code''' '''Name'''<br /> <br /> PWD Services for PAX with disabilities<br /> <br /> MEDA Services for PAX with medical conditions<br /> <br /> INF Informational PAX Services<br /> <br /> ISS Service delivery services<br /> <br /> PPP Pre &amp; Postprocessing services<br /> <br /> '''Actions'''<br /> <br /> •'''Add new''' (➕)<br /> <br /> •'''Search'''<br /> <br /> •'''Edit''' (✏️)<br /> <br /> •'''Delete''' (🗑️)<br /> <br /> [[File:SPFT.png|none|thumb]]<br /> <br /> == '''SPFT Detail View''' ==<br /> Example shown: '''MEDA'''<br /> <br /> This page defines the operational behavior of a service category.<br /> <br /> === '''General Configuration''' ===<br /> '''Fields'''<br /> <br /> '''Code (required)'''<br /> <br /> Unique identifier of the SPFT.<br /> <br /> Example: MEDA<br /> <br /> === '''Service Color Code''' ===<br /> Hex color used in backend UI to visually mark requests belonging to this SPFT.<br /> <br /> Example: #FFA834<br /> <br /> Used for:<br /> <br /> •Backend case highlighting<br /> <br /> •Task visualization<br /> <br /> •Operational signaling<br /> <br /> === '''Name of Service Group (Multilingual)''' ===<br /> Defines the display name.<br /> <br /> Example: Medical Case Defining Service<br /> <br /> === '''Icon Tag (32x32)''' ===<br /> Icon displayed:<br /> <br /> •In service selection<br /> <br /> •In backend processing<br /> <br /> •In portal UI<br /> <br /> Actions:<br /> <br /> •Upload<br /> <br /> •Remove<br /> <br /> == '''Member Service Type Classification''' ==<br /> Defines how services belonging to this SPFT behave in the PAX Portal.<br /> <br /> Options:<br /> <br /> === '''1. Primary services for PAX''' ===<br /> •Displayed on main service selection screen<br /> <br /> •Manually selected by passenger<br /> <br /> === '''2. Primary informational services for PAX''' ===<br /> •Shown in second step of PAX portal (before finishing booking)<br /> <br /> •Used for informational add-ons<br /> <br /> === '''3. Secondary services automatically added by transport type''' ===<br /> Example:<br /> <br /> •Based on Bus / Train / Aircraft type<br /> <br /> •Added when primary service is requested<br /> <br /> === '''4. Secondary services added upon approval of primary service''' ===<br /> Example:<br /> <br /> •Mounting<br /> <br /> •Dismantling<br /> <br /> •Added after medical approval<br /> <br /> This directly drives:<br /> <br /> •Automatic service chaining<br /> <br /> •Task generation<br /> <br /> •Backend dependency creationž<br /> <br /> == '''Process Flow Settings (Approval Logic)''' ==<br /> Defines whether services of this SPFT require approval.<br /> <br /> <br /> '''Medical Approval Required'''<br /> <br /> Checkbox: Services of this type require approval by medical team<br /> <br /> If enabled:<br /> <br /> •Medical case workflow is triggered<br /> <br /> •Only authorized groups can approve<br /> <br /> Business participant groups selectable:<br /> <br /> •Operations Managers<br /> <br /> •Internal Doctors<br /> <br /> •External Doctors<br /> <br /> •Custom groups<br /> <br /> === '''Operations Approval Required''' ===<br /> Checkbox: Services of this type require approval by operations team<br /> <br /> If enabled:<br /> <br /> •Operations review required before confirmation<br /> <br /> •Tasks created accordingly<br /> <br /> Selectable groups:<br /> <br /> •Operations Managers<br /> <br /> •Operations Staff<br /> <br /> === '''What This Does Systemically''' ===<br /> When enabled:<br /> <br /> •Service enters approval state<br /> <br /> •Tasks created for assigned approval group<br /> <br /> •Final confirmation blocked until approval<br /> <br /> == '''MEDIF Configuration''' ==<br /> Defines whether MEDIF documentation is required.<br /> <br /> '''Options'''<br /> <br /> •Service does NOT require MEDIF<br /> <br /> •Service requires MEDIF<br /> <br /> '''Exception Handling'''<br /> <br /> Admin can define:<br /> <br /> '''Service''' '''Touched Regulatory Zone'''<br /> <br /> Oxygen Canada<br /> <br /> Oxygen US<br /> <br /> This means:<br /> <br /> Even if MEDIF is generally required, exceptions can be defined per:<br /> <br /> •Regulatory zone<br /> <br /> •Country<br /> <br /> •Service<br /> <br /> '''What It Controls'''<br /> <br /> •PAX document upload requirement<br /> <br /> •Case cannot proceed without MEDIF (unless exception applies)<br /> <br /> •Regulatory compliance enforcement<br /> <br /> == '''Delivered Service &amp; Regulatory Zone Mapping''' ==<br /> Allows defining:<br /> <br /> •Which service<br /> <br /> •Which regulatory zone<br /> <br /> •Whether MEDIF requirement is overridden<br /> <br /> Actions:<br /> <br /> •Add<br /> <br /> •Remove<br /> <br /> <br /> '''System Behavior Summary'''<br /> <br /> SPFT configuration directly impacts:<br /> <br /> '''Area''' '''Impact'''<br /> <br /> PAX Portal Service visibility &amp; placement<br /> <br /> Backend UI Color coding &amp; icon<br /> <br /> Approval Workflow Medical &amp; operational gating<br /> <br /> Task Engine Task creation triggers<br /> <br /> Automation Secondary service chaining<br /> <br /> Regulatory Compliance MEDIF enforcement<br /> <br /> [[File:SPFT details.png|none|thumb]]<br /> [[File:SPFT details 2.png|none|thumb]]<br /> <br /> == '''Logical Dependencies''' ==<br /> SPFT interacts with:<br /> <br /> •Travel Service Administration<br /> <br /> •Service Delivery Partners<br /> <br /> •Task Template Engine<br /> <br /> •Segment &amp; Port availability logic<br /> <br /> •MEDIF validation system<br /> <br /> •Automation rules<br /> <br /> == Related articles ==<br /> [[Dev:LH Core Admin-Service Process Flow Type Translations|Translations]]</div>

Mionamilosevic https://wiki.kordeus.com/index.php?title=File:SPFT_details_2.png&diff=3144 2026-02-27T14:31:10Z

<p>Mionamilosevic: </p> <hr /> <div>SPFT details 2</div>

Mionamilosevic https://wiki.kordeus.com/index.php?title=File:SPFT_details.png&diff=3143 2026-02-27T14:30:48Z

<p>Mionamilosevic: </p> <hr /> <div>SPFT details</div>

Mionamilosevic https://wiki.kordeus.com/index.php?title=File:SPFT.png&diff=3142 2026-02-27T14:29:47Z

<p>Mionamilosevic: </p> <hr /> <div>SPFT</div>

Mionamilosevic https://wiki.kordeus.com/index.php?title=Dev:LH_MOC_Admin-Travel_service_delivery_partner_Translations&diff=3141 2026-02-27T14:27:12Z

<p>Mionamilosevic: </p> <hr /> <div>{| class=&quot;wikitable&quot;<br /> |'''Application'''<br /> |Travel service delivery partner<br /> |-<br /> |'''Languages'''<br /> |en_en, de_de<br /> |}<br /> {| class=&quot;wikitable&quot;<br /> |+<br /> !Code<br /> !Comment<br /> !en_en<br /> !de_de<br /> |-<br /> |<br /> |<br /> |<br /> |<br /> |}</div>

Mionamilosevic https://wiki.kordeus.com/index.php?title=Dev:LH_Core_Admin&diff=3140 2026-02-27T14:26:45Z

<p>Mionamilosevic: </p> <hr /> <div>* [[Dev:LH Core Admin-Craft types|Craft types]]<br /> *[[Dev:LH Core Admin-Carrier brands|Carrier brands]]<br /> *[[Dev:LH Core Admin-Destinations/Ports|Destination/Ports]]<br /> *[[Dev:LH Core Admin-Flight plan|Flight plan]]<br /> *[[Dev:LH Core Admin-Service Process Flow Type|Service Process Flow Type]]</div>

Mionamilosevic https://wiki.kordeus.com/index.php?title=Dev:LH_Core_Admin-Service_Process_Flow_Type&diff=3139 2026-02-27T14:26:23Z

<p>Mionamilosevic: Created page with &quot;The Service Process Flow Type Administration (SPFT) module defines high-level service categories and their behavioral logic within the Medical Operation Center (MOC) system. Each SPFT determines: •How a service appears in the PAX Portal •Whether it requires medical and/or operational approval •Whether MEDIF documentation is required •How it behaves in backend workflows •Which business participant groups are allowed to approve •How it is visually repres...&quot;</p> <hr /> <div>The Service Process Flow Type Administration (SPFT) module defines high-level service categories and their behavioral logic within the Medical Operation Center (MOC) system.<br /> <br /> Each SPFT determines:<br /> <br /> •How a service appears in the PAX Portal<br /> <br /> •Whether it requires medical and/or operational approval<br /> <br /> •Whether MEDIF documentation is required<br /> <br /> •How it behaves in backend workflows<br /> <br /> •Which business participant groups are allowed to approve<br /> <br /> •How it is visually represented (icon &amp; color coding)<br /> <br /> SPFT acts as a meta-layer configuration that governs downstream behavior of all travel services assigned to that process type.<br /> <br /> == '''SPFT List View''' ==<br /> Displays all configured Service Process Flow Types.<br /> <br /> Each entry represents a service category that defines approval logic, visibility behavior, and automation rules.<br /> <br /> <br /> '''Fields'''<br /> <br /> '''Field''' '''Description'''<br /> <br /> Identifier Icon Visual icon representing this process type<br /> <br /> Code Unique SPFT code (e.g., PWD, MEDA, INF, ISS, PPP)<br /> <br /> Name Human-readable name of the service group<br /> <br /> '''Default Example'''<br /> <br /> '''Code''' '''Name'''<br /> <br /> PWD Services for PAX with disabilities<br /> <br /> MEDA Services for PAX with medical conditions<br /> <br /> INF Informational PAX Services<br /> <br /> ISS Service delivery services<br /> <br /> PPP Pre &amp; Postprocessing services<br /> <br /> '''Actions'''<br /> <br /> •'''Add new''' (➕)<br /> <br /> •'''Search'''<br /> <br /> •'''Edit''' (✏️)<br /> <br /> •'''Delete''' (🗑️)<br /> <br /> == '''SPFT Detail View''' ==<br /> Example shown: '''MEDA'''<br /> <br /> This page defines the operational behavior of a service category.<br /> <br /> === '''General Configuration''' ===<br /> '''Fields'''<br /> <br /> '''Code (required)'''<br /> <br /> Unique identifier of the SPFT.<br /> <br /> Example: MEDA<br /> <br /> === '''Service Color Code''' ===<br /> Hex color used in backend UI to visually mark requests belonging to this SPFT.<br /> <br /> Example: #FFA834<br /> <br /> Used for:<br /> <br /> •Backend case highlighting<br /> <br /> •Task visualization<br /> <br /> •Operational signaling<br /> <br /> === '''Name of Service Group (Multilingual)''' ===<br /> Defines the display name.<br /> <br /> Example: Medical Case Defining Service<br /> <br /> === '''Icon Tag (32x32)''' ===<br /> Icon displayed:<br /> <br /> •In service selection<br /> <br /> •In backend processing<br /> <br /> •In portal UI<br /> <br /> Actions:<br /> <br /> •Upload<br /> <br /> •Remove<br /> <br /> == '''Member Service Type Classification''' ==<br /> Defines how services belonging to this SPFT behave in the PAX Portal.<br /> <br /> Options:<br /> <br /> === '''1. Primary services for PAX''' ===<br /> •Displayed on main service selection screen<br /> <br /> •Manually selected by passenger<br /> <br /> === '''2. Primary informational services for PAX''' ===<br /> •Shown in second step of PAX portal (before finishing booking)<br /> <br /> •Used for informational add-ons<br /> <br /> === '''3. Secondary services automatically added by transport type''' ===<br /> Example:<br /> <br /> •Based on Bus / Train / Aircraft type<br /> <br /> •Added when primary service is requested<br /> <br /> === '''4. Secondary services added upon approval of primary service''' ===<br /> Example:<br /> <br /> •Mounting<br /> <br /> •Dismantling<br /> <br /> •Added after medical approval<br /> <br /> This directly drives:<br /> <br /> •Automatic service chaining<br /> <br /> •Task generation<br /> <br /> •Backend dependency creationž<br /> <br /> == '''Process Flow Settings (Approval Logic)''' ==<br /> Defines whether services of this SPFT require approval.<br /> <br /> <br /> '''Medical Approval Required'''<br /> <br /> Checkbox: Services of this type require approval by medical team<br /> <br /> If enabled:<br /> <br /> •Medical case workflow is triggered<br /> <br /> •Only authorized groups can approve<br /> <br /> Business participant groups selectable:<br /> <br /> •Operations Managers<br /> <br /> •Internal Doctors<br /> <br /> •External Doctors<br /> <br /> •Custom groups<br /> <br /> === '''Operations Approval Required''' ===<br /> Checkbox: Services of this type require approval by operations team<br /> <br /> If enabled:<br /> <br /> •Operations review required before confirmation<br /> <br /> •Tasks created accordingly<br /> <br /> Selectable groups:<br /> <br /> •Operations Managers<br /> <br /> •Operations Staff<br /> <br /> === '''What This Does Systemically''' ===<br /> When enabled:<br /> <br /> •Service enters approval state<br /> <br /> •Tasks created for assigned approval group<br /> <br /> •Final confirmation blocked until approval<br /> <br /> == '''MEDIF Configuration''' ==<br /> Defines whether MEDIF documentation is required.<br /> <br /> '''Options'''<br /> <br /> •Service does NOT require MEDIF<br /> <br /> •Service requires MEDIF<br /> <br /> '''Exception Handling'''<br /> <br /> Admin can define:<br /> <br /> '''Service''' '''Touched Regulatory Zone'''<br /> <br /> Oxygen Canada<br /> <br /> Oxygen US<br /> <br /> This means:<br /> <br /> Even if MEDIF is generally required, exceptions can be defined per:<br /> <br /> •Regulatory zone<br /> <br /> •Country<br /> <br /> •Service<br /> <br /> '''What It Controls'''<br /> <br /> •PAX document upload requirement<br /> <br /> •Case cannot proceed without MEDIF (unless exception applies)<br /> <br /> •Regulatory compliance enforcement<br /> <br /> == '''Delivered Service &amp; Regulatory Zone Mapping''' ==<br /> Allows defining:<br /> <br /> •Which service<br /> <br /> •Which regulatory zone<br /> <br /> •Whether MEDIF requirement is overridden<br /> <br /> Actions:<br /> <br /> •Add<br /> <br /> •Remove<br /> <br /> <br /> '''System Behavior Summary'''<br /> <br /> SPFT configuration directly impacts:<br /> <br /> '''Area''' '''Impact'''<br /> <br /> PAX Portal Service visibility &amp; placement<br /> <br /> Backend UI Color coding &amp; icon<br /> <br /> Approval Workflow Medical &amp; operational gating<br /> <br /> Task Engine Task creation triggers<br /> <br /> Automation Secondary service chaining<br /> <br /> Regulatory Compliance MEDIF enforcement<br /> <br /> == '''Logical Dependencies''' ==<br /> SPFT interacts with:<br /> <br /> •Travel Service Administration<br /> <br /> •Service Delivery Partners<br /> <br /> •Task Template Engine<br /> <br /> •Segment &amp; Port availability logic<br /> <br /> •MEDIF validation system<br /> <br /> •Automation rules<br /> <br /> == Related articles ==<br /> [[Dev:LH Core Admin-Service Process Flow Type Translations|Translations]]</div>

Mionamilosevic https://wiki.kordeus.com/index.php?title=Dev:LH_Core_Admin-Service_Process_Flow_Type_Translations&diff=3138 2026-02-27T14:26:04Z

<p>Mionamilosevic: Created page with &quot;{| class=&quot;wikitable&quot; |&#039;&#039;&#039;Application&#039;&#039;&#039; |Service Process Flow Type |- |&#039;&#039;&#039;Languages&#039;&#039;&#039; |en_en, de_de |} {| class=&quot;wikitable&quot; |+ !Code !Comment !en_en !de_de |}&quot;</p> <hr /> <div>{| class=&quot;wikitable&quot;<br /> |'''Application'''<br /> |Service Process Flow Type<br /> |-<br /> |'''Languages'''<br /> |en_en, de_de<br /> |}<br /> {| class=&quot;wikitable&quot;<br /> |+<br /> !Code<br /> !Comment<br /> !en_en<br /> !de_de<br /> |}</div>

Mionamilosevic https://wiki.kordeus.com/index.php?title=Dev:LH_Core_Admin&diff=3132 2026-02-27T09:27:23Z

<p>Mionamilosevic: </p> <hr /> <div>* [[Dev:LH Core Admin-Craft types|Craft types]]<br /> *[[Dev:LH Core Admin-Carrier brands|Carrier brands]]<br /> *[[Dev:LH Core Admin-Destinations/Ports|Destination/Ports]]<br /> *[[Dev:LH Core Admin-Flight plan|Flight plan]]<br /> *Service Process Flow Type</div>

Mionamilosevic https://wiki.kordeus.com/index.php?title=Dev:LH_MOC_Admin&diff=3131 2026-02-27T09:26:48Z

<p>Mionamilosevic: </p> <hr /> <div>* [[Dev:Travel services|Travel Services]]<br /> * [[Dev:LH MOC Admin-Contractors|Contractors]]<br /> * [[Dev:LH MOC Admin-MOC|Medical Operation centers]]<br /> * Task Template Administration<br /> * Text Standard Blocks<br /> * Standard documents administration<br /> * [[Dev:LH MOC Admin-Travel partner|Travel partner]]<br /> * [[Dev:LH MOC Admin-Travel service delivery partner|Travel service delivery partner]]</div>

Mionamilosevic https://wiki.kordeus.com/index.php?title=Dev:LH_MOC_Admin-Travel_service_delivery_partner&diff=3128 2026-02-27T09:10:17Z

<p>Mionamilosevic: </p> <hr /> <div>Define and manage operational service providers (e.g., stretcher mounting teams, ambulance providers, ground handlers) that physically deliver services at specific ports and segments.<br /> <br /> This module connects:<br /> <br /> •Travel Services (e.g., STCR, WENOLL, Ambulance)<br /> <br /> •Ports (e.g., FRA, MUC, LHR)<br /> <br /> •Capacity management<br /> <br /> •Mounting/dismantling automation<br /> <br /> •B-Op Digital network connection<br /> <br /> It ensures that a service can be delivered if:<br /> <br /> 1.A Service Delivery Partner exists<br /> <br /> 2.The partner supports the service<br /> <br /> 3.The partner operates at the required port<br /> <br /> 4.Capacity restrictions allow it<br /> <br /> <br /> The Service Delivery Partner module is the operational backbone of:<br /> <br /> •Ground execution<br /> <br /> •Mounting/dismantling<br /> <br /> •Capacity control<br /> <br /> •Automated task orchestration<br /> <br /> •Port-level service enablement<br /> <br /> •Digital B-Op integration<br /> <br /> It ensures that services defined in Travel Service Administration become operationally executable in real-world environments.<br /> <br /> == '''Partner List View''' ==<br /> '''Purpose'''<br /> <br /> Displays all Service Delivery Partners configured in the system and their operational status.<br /> <br /> This is the entry point for managing operational ground/service providers.<br /> <br /> <br /> '''Table columns'''<br /> <br /> '''Column''' '''Description'''<br /> <br /> '''B-Op Connection''' Shows digital network connection status (Connected / Not Connected / Pending). Visual indicator.<br /> <br /> '''Business Participant / Digital''' Official name of the service delivery partner.<br /> <br /> '''Country''' Country where the partner operates.<br /> <br /> '''Relevant Stations / Ports''' List of ports where this partner delivers services.<br /> <br /> <br /> '''Available actions'''<br /> <br /> '''Action''' '''Description'''<br /> <br /> ➕ '''Add New''' Create a new Service Delivery Partner<br /> <br /> 🔍 '''Search''' Search by partner name or country<br /> <br /> ✏️ '''Edit''' Open partner details<br /> <br /> 🗑 '''Delete''' Remove partner (only if no active service bindings exist)<br /> <br /> <br /> '''Behaviour'''<br /> <br /> •Sorting available on table columns.<br /> <br /> •B-Op status is read-only (managed via B-Op Network app).<br /> <br /> •Deleting a partner is restricted if:<br /> <br /> •It is linked to active services<br /> <br /> •It is used in task automation rules<br /> <br /> •It is referenced in mounting/dismantling logic<br /> [[File:Service delivery partner.png|none|thumb]]<br /> <br /> <br /> == '''Partner Detail View – General''' ==<br /> '''Purpose'''<br /> <br /> Define the identity and core configuration of a Service Delivery Partner.<br /> <br /> <br /> '''General fields'''<br /> {| class=&quot;wikitable&quot;<br /> |+<br /> !Field<br /> !Description<br /> !Required<br /> |-<br /> |'''Internal Name'''<br /> |Display name of the partner (multilingual input)<br /> |Yes<br /> |-<br /> |'''Internal Code'''<br /> |Unique system identifier<br /> |Yes<br /> |-<br /> |'''Country'''<br /> |Country of operation<br /> |Yes<br /> |}<br /> <br /> === '''B-Op Digital Connection Status''' ===<br /> Displays:<br /> <br /> •✅ Connected<br /> <br /> •❌ Not Connected<br /> <br /> •⏳ Pending<br /> <br /> Connection status is managed in '''My B-Op Network app'''.<br /> <br /> This connection enables:<br /> <br /> •Digital task transmission<br /> <br /> •Secure communication<br /> <br /> •Automated service orchestration<br /> <br /> [[File:Service delivery partner general.png|none|thumb]]<br /> <br /> == '''Generally Supported Travel Services''' ==<br /> '''Purpose'''<br /> <br /> Define which services this partner can generally perform.<br /> <br /> Examples:<br /> <br /> •Stretcher mounting<br /> <br /> •Stretcher dismantling<br /> <br /> •WENOLL mounting<br /> <br /> •Ambulance<br /> <br /> •Assistance dog handling<br /> <br /> This section links the partner to Travel Services defined in: Travel Service Administration<br /> <br /> <br /> '''Behavior'''<br /> <br /> •Multi-select service binding<br /> <br /> •Once added, services become configurable per port<br /> <br /> •If not listed here → partner cannot deliver the service<br /> <br /> == '''Points-of-Presence (Port Configuration)''' ==<br /> '''Purpose'''<br /> <br /> Define where the partner operates and configure port-specific service behavior.<br /> <br /> When a port is added:<br /> <br /> •A dedicated configuration tab appears for that port<br /> <br /> •Services can be restricted or configured per port<br /> <br /> <br /> '''Available Port Presences'''<br /> <br /> •Multi-select list of ports (from Destinations / Ports module)<br /> <br /> •Each selected port creates a configuration section<br /> <br /> === '''Port-Level Configuration (Example: FRA)''' ===<br /> For each port, the following configuration areas exist:<br /> <br /> '''Insecure Communication Channels'''<br /> <br /> Define fallback communication methods (if not using digital network).<br /> <br /> Fields:<br /> <br /> •Add email recipient<br /> <br /> •Add telex recipient<br /> <br /> Usage options:<br /> <br /> •Use for handling advice<br /> <br /> •Use for routine checks<br /> <br /> This supports legacy operational flows.<br /> <br /> <br /> '''Available Services at This Port'''<br /> <br /> Shows all services previously bound in “Generally Supported Services”.<br /> <br /> For each service:<br /> <br /> '''Option''' '''Meaning'''<br /> <br /> Deliverable @ Port Service can be delivered here<br /> <br /> Capacity restrictions apply Enables capacity logic<br /> <br /> <br /> '''Service Deliverability &amp; Capacity Restrictions'''<br /> <br /> For services requiring capacity control (e.g., STCR mounting):<br /> <br /> '''Service Delivery Mode'''<br /> <br /> • Unrestricted<br /> <br /> • Restricted by concurrent capacity limit<br /> <br /> If restricted:<br /> <br /> Fields:<br /> <br /> •Max concurrent deliveries<br /> <br /> •Cap block before departure (mins)<br /> <br /> •Cap block after arrival (mins)<br /> <br /> '''Transfer Logic'''<br /> <br /> •Enforce minimum connection time<br /> <br /> •Define minimum minutes<br /> <br /> <br /> '''Worklist Integration'''<br /> <br /> •Place service on partner worklist per day<br /> <br /> •Select target worklist<br /> <br /> <br /> '''Segment Marking (Advanced)'''<br /> <br /> •Mark intercontinental segment<br /> <br /> •Influences SAE engine / routing logic<br /> <br /> [[File:SDP points of presence.png|none|thumb]]<br /> [[File:SDP FRA example.png|none|thumb]]<br /> <br /> == '''Delivery Partner Capacity Tracking Lists''' ==<br /> Allows creation of internal capacity lists.<br /> <br /> Purpose:<br /> <br /> •Define resource groups<br /> <br /> •Manage workload tracking<br /> <br /> •Control operational scaling<br /> <br /> Example:<br /> <br /> •“Ladeliste STCR FRA”<br /> <br /> •“Night shift STCR team”<br /> <br /> == Related articles ==<br /> [[Dev:LH MOC Admin-Travel service delivery partner Translations|Translations]]</div>

Mionamilosevic https://wiki.kordeus.com/index.php?title=File:SDP_FRA_example.png&diff=3127 2026-02-27T09:10:04Z

<p>Mionamilosevic: </p> <hr /> <div>SDP FRA example</div>

Mionamilosevic https://wiki.kordeus.com/index.php?title=Dev:LH_MOC_Admin-Travel_service_delivery_partner&diff=3126 2026-02-27T09:00:30Z

<p>Mionamilosevic: </p> <hr /> <div>Define and manage operational service providers (e.g., stretcher mounting teams, ambulance providers, ground handlers) that physically deliver services at specific ports and segments.<br /> <br /> This module connects:<br /> <br /> •Travel Services (e.g., STCR, WENOLL, Ambulance)<br /> <br /> •Ports (e.g., FRA, MUC, LHR)<br /> <br /> •Capacity management<br /> <br /> •Mounting/dismantling automation<br /> <br /> •B-Op Digital network connection<br /> <br /> It ensures that a service can be delivered if:<br /> <br /> 1.A Service Delivery Partner exists<br /> <br /> 2.The partner supports the service<br /> <br /> 3.The partner operates at the required port<br /> <br /> 4.Capacity restrictions allow it<br /> <br /> <br /> The Service Delivery Partner module is the operational backbone of:<br /> <br /> •Ground execution<br /> <br /> •Mounting/dismantling<br /> <br /> •Capacity control<br /> <br /> •Automated task orchestration<br /> <br /> •Port-level service enablement<br /> <br /> •Digital B-Op integration<br /> <br /> It ensures that services defined in Travel Service Administration become operationally executable in real-world environments.<br /> <br /> == '''Partner List View''' ==<br /> '''Purpose'''<br /> <br /> Displays all Service Delivery Partners configured in the system and their operational status.<br /> <br /> This is the entry point for managing operational ground/service providers.<br /> <br /> <br /> '''Table columns'''<br /> <br /> '''Column''' '''Description'''<br /> <br /> '''B-Op Connection''' Shows digital network connection status (Connected / Not Connected / Pending). Visual indicator.<br /> <br /> '''Business Participant / Digital''' Official name of the service delivery partner.<br /> <br /> '''Country''' Country where the partner operates.<br /> <br /> '''Relevant Stations / Ports''' List of ports where this partner delivers services.<br /> <br /> <br /> '''Available actions'''<br /> <br /> '''Action''' '''Description'''<br /> <br /> ➕ '''Add New''' Create a new Service Delivery Partner<br /> <br /> 🔍 '''Search''' Search by partner name or country<br /> <br /> ✏️ '''Edit''' Open partner details<br /> <br /> 🗑 '''Delete''' Remove partner (only if no active service bindings exist)<br /> <br /> <br /> '''Behaviour'''<br /> <br /> •Sorting available on table columns.<br /> <br /> •B-Op status is read-only (managed via B-Op Network app).<br /> <br /> •Deleting a partner is restricted if:<br /> <br /> •It is linked to active services<br /> <br /> •It is used in task automation rules<br /> <br /> •It is referenced in mounting/dismantling logic<br /> [[File:Service delivery partner.png|none|thumb]]<br /> <br /> <br /> == '''Partner Detail View – General''' ==<br /> '''Purpose'''<br /> <br /> Define the identity and core configuration of a Service Delivery Partner.<br /> <br /> <br /> '''General fields'''<br /> {| class=&quot;wikitable&quot;<br /> |+<br /> !Field<br /> !Description<br /> !Required<br /> |-<br /> |'''Internal Name'''<br /> |Display name of the partner (multilingual input)<br /> |Yes<br /> |-<br /> |'''Internal Code'''<br /> |Unique system identifier<br /> |Yes<br /> |-<br /> |'''Country'''<br /> |Country of operation<br /> |Yes<br /> |}<br /> <br /> === '''B-Op Digital Connection Status''' ===<br /> Displays:<br /> <br /> •✅ Connected<br /> <br /> •❌ Not Connected<br /> <br /> •⏳ Pending<br /> <br /> Connection status is managed in '''My B-Op Network app'''.<br /> <br /> This connection enables:<br /> <br /> •Digital task transmission<br /> <br /> •Secure communication<br /> <br /> •Automated service orchestration<br /> <br /> [[File:Service delivery partner general.png|none|thumb]]<br /> <br /> == '''Generally Supported Travel Services''' ==<br /> '''Purpose'''<br /> <br /> Define which services this partner can generally perform.<br /> <br /> Examples:<br /> <br /> •Stretcher mounting<br /> <br /> •Stretcher dismantling<br /> <br /> •WENOLL mounting<br /> <br /> •Ambulance<br /> <br /> •Assistance dog handling<br /> <br /> This section links the partner to Travel Services defined in: Travel Service Administration<br /> <br /> <br /> '''Behavior'''<br /> <br /> •Multi-select service binding<br /> <br /> •Once added, services become configurable per port<br /> <br /> •If not listed here → partner cannot deliver the service<br /> <br /> == '''Points-of-Presence (Port Configuration)''' ==<br /> '''Purpose'''<br /> <br /> Define where the partner operates and configure port-specific service behavior.<br /> <br /> When a port is added:<br /> <br /> •A dedicated configuration tab appears for that port<br /> <br /> •Services can be restricted or configured per port<br /> <br /> <br /> '''Available Port Presences'''<br /> <br /> •Multi-select list of ports (from Destinations / Ports module)<br /> <br /> •Each selected port creates a configuration section<br /> <br /> === '''Port-Level Configuration (Example: FRA)''' ===<br /> For each port, the following configuration areas exist:<br /> <br /> '''Insecure Communication Channels'''<br /> <br /> Define fallback communication methods (if not using digital network).<br /> <br /> Fields:<br /> <br /> •Add email recipient<br /> <br /> •Add telex recipient<br /> <br /> Usage options:<br /> <br /> •Use for handling advice<br /> <br /> •Use for routine checks<br /> <br /> This supports legacy operational flows.<br /> <br /> <br /> '''Available Services at This Port'''<br /> <br /> Shows all services previously bound in “Generally Supported Services”.<br /> <br /> For each service:<br /> <br /> '''Option''' '''Meaning'''<br /> <br /> Deliverable @ Port Service can be delivered here<br /> <br /> Capacity restrictions apply Enables capacity logic<br /> <br /> <br /> '''Service Deliverability &amp; Capacity Restrictions'''<br /> <br /> For services requiring capacity control (e.g., STCR mounting):<br /> <br /> '''Service Delivery Mode'''<br /> <br /> • Unrestricted<br /> <br /> • Restricted by concurrent capacity limit<br /> <br /> If restricted:<br /> <br /> Fields:<br /> <br /> •Max concurrent deliveries<br /> <br /> •Cap block before departure (mins)<br /> <br /> •Cap block after arrival (mins)<br /> <br /> '''Transfer Logic'''<br /> <br /> •Enforce minimum connection time<br /> <br /> •Define minimum minutes<br /> <br /> <br /> '''Worklist Integration'''<br /> <br /> •Place service on partner worklist per day<br /> <br /> •Select target worklist<br /> <br /> <br /> '''Segment Marking (Advanced)'''<br /> <br /> •Mark intercontinental segment<br /> <br /> •Influences SAE engine / routing logic<br /> <br /> [[File:SDP points of presence.png|none|thumb]]<br /> <br /> == '''Delivery Partner Capacity Tracking Lists''' ==<br /> Allows creation of internal capacity lists.<br /> <br /> Purpose:<br /> <br /> •Define resource groups<br /> <br /> •Manage workload tracking<br /> <br /> •Control operational scaling<br /> <br /> Example:<br /> <br /> •“Ladeliste STCR FRA”<br /> <br /> •“Night shift STCR team”<br /> <br /> == Related articles ==<br /> [[Dev:LH MOC Admin-Travel service delivery partner Translations|Translations]]</div>

Mionamilosevic https://wiki.kordeus.com/index.php?title=File:SDP_points_of_presence.png&diff=3125 2026-02-27T09:00:19Z

<p>Mionamilosevic: </p> <hr /> <div>SDP points of presence</div>

Mionamilosevic https://wiki.kordeus.com/index.php?title=File:Service_delivery_partner_general.png&diff=3124 2026-02-27T08:59:56Z

<p>Mionamilosevic: </p> <hr /> <div>Service delivery partner general</div>

Mionamilosevic