Dev:LH MOC Admin-Travel service delivery partner

Define and manage operational service providers (e.g., stretcher mounting teams, ambulance providers, ground handlers) that physically deliver services at specific ports and segments.

This module connects:

•Travel Services (e.g., STCR, WENOLL, Ambulance)

•Ports (e.g., FRA, MUC, LHR)

•Capacity management

•Mounting/dismantling automation

•B-Op Digital network connection

It ensures that a service can be delivered if:

1.A Service Delivery Partner exists

2.The partner supports the service

3.The partner operates at the required port

4.Capacity restrictions allow it

The Service Delivery Partner module is the operational backbone of:

•Ground execution

•Mounting/dismantling

•Capacity control

•Automated task orchestration

•Port-level service enablement

•Digital B-Op integration

It ensures that services defined in Travel Service Administration become operationally executable in real-world environments.

Partner List View

Purpose

Displays all Service Delivery Partners configured in the system and their operational status.

This is the entry point for managing operational ground/service providers.

Table columns

Column Description

B-Op Connection Shows digital network connection status (Connected / Not Connected / Pending). Visual indicator.

Business Participant / Digital Official name of the service delivery partner.

Country Country where the partner operates.

Relevant Stations / Ports List of ports where this partner delivers services.

Available actions

Action Description

➕ Add New Create a new Service Delivery Partner

🔍 Search Search by partner name or country

✏️ Edit Open partner details

🗑 Delete Remove partner (only if no active service bindings exist)

Behaviour

•Sorting available on table columns.

•B-Op status is read-only (managed via B-Op Network app).

•Deleting a partner is restricted if:

•It is linked to active services

•It is used in task automation rules

•It is referenced in mounting/dismantling logic

Partner Detail View – General

Purpose

Define the identity and core configuration of a Service Delivery Partner.

General fields

Field	Description	Required
Internal Name	Display name of the partner (multilingual input)	Yes
Internal Code	Unique system identifier	Yes
Country	Country of operation	Yes

B-Op Digital Connection Status

Displays:

•✅ Connected

•❌ Not Connected

•⏳ Pending

Connection status is managed in My B-Op Network app.

This connection enables:

•Digital task transmission

•Secure communication

•Automated service orchestration

Generally Supported Travel Services

Purpose

Define which services this partner can generally perform.

Examples:

•Stretcher mounting

•Stretcher dismantling

•WENOLL mounting

•Ambulance

•Assistance dog handling

This section links the partner to Travel Services defined in: Travel Service Administration

Behavior

•Multi-select service binding

•Once added, services become configurable per port

•If not listed here → partner cannot deliver the service

Points-of-Presence (Port Configuration)

Purpose

Define where the partner operates and configure port-specific service behavior.

When a port is added:

•A dedicated configuration tab appears for that port

•Services can be restricted or configured per port

Available Port Presences

•Multi-select list of ports (from Destinations / Ports module)

•Each selected port creates a configuration section

Port-Level Configuration (Example: FRA)

For each port, the following configuration areas exist:

Insecure Communication Channels

Define fallback communication methods (if not using digital network).

Fields:

•Add email recipient

•Add telex recipient

Usage options:

•Use for handling advice

•Use for routine checks

This supports legacy operational flows.

Available Services at This Port

Shows all services previously bound in “Generally Supported Services”.

For each service:

Option Meaning

Deliverable @ Port Service can be delivered here

Capacity restrictions apply Enables capacity logic

Service Deliverability & Capacity Restrictions

For services requiring capacity control (e.g., STCR mounting):

Service Delivery Mode

• Unrestricted

• Restricted by concurrent capacity limit

If restricted:

Fields:

•Max concurrent deliveries

•Cap block before departure (mins)

•Cap block after arrival (mins)

Transfer Logic

•Enforce minimum connection time

•Define minimum minutes

Worklist Integration

•Place service on partner worklist per day

•Select target worklist

Segment Marking (Advanced)

•Mark intercontinental segment

•Influences SAE engine / routing logic

Delivery Partner Capacity Tracking Lists

Allows creation of internal capacity lists.

Purpose:

•Define resource groups

•Manage workload tracking

•Control operational scaling

Example:

•“Ladeliste STCR FRA”

•“Night shift STCR team”

Related articles

Translations