Demo

Create an Airline Disruption Recovery application that helps airline operations teams manage passengers affected by cancellations, major delays, airport closures or other disruptions.


Core Workflow

Use Disruption Event as the single parent workflow:

Disruption Received → Review Affected Flights → Segment Passengers → Recover Passengers → Verify Recovery → Resolve

A disruption is received from the Flight Operations System through an Inbound API. The event contains the disruption reason, airport and affected flights. Retrieve the passenger manifest for each affected flight from the Reservation System.

Caseworker Journey

Notify the assigned Disruption Caseworker when a new disruption occurs.

The caseworker opens one operational workspace showing:

- disruption details and recovery progress
- affected flights
- passenger manifest
- passenger segments
- active recovery workflows
- unresolved exceptions

The caseworker can select one or multiple affected flights and view their combined passenger manifest.

Allow passengers to be filtered using simple operational metadata including:

destination, age group, travelling party/family, priority status, cabin class, connection status, special/medical assistance, alternative-flight status, hotel requirement and recovery status.

The caseworker can select filtered passengers and create named Passenger Segments, for example:

- New York passengers needing alternative flights
- Passengers requiring overnight accommodation
- Families travelling with children
- Passengers requiring special or medical assistance

Recovery Actions

For any Passenger Segment, allow the caseworker to trigger one or more child recovery workflows:

Alternative Flight
Search available flights → caseworker selects/assigns flight → book passengers → update recovery status.

Hotel & Services
Search available hotels → allocate rooms → arrange meals/ground transport if required → confirm services.

Passenger Assistance
Review assistance requirement → arrange wheelchair, accessibility, family or medical assistance → confirm service.

Passenger Communication
Send confirmed recovery information through WhatsApp, with SMS/email fallback.

Multiple recovery workflows may run in parallel for the same segment.

Parent/Child Dependency

All recovery workflows must remain associated with the parent Disruption Event.

The parent must remain in Recover Passengers while mandatory child recovery workflows are active.

Use a dependency/wait condition so the parent cannot progress to Verify Recovery until its required child workflows are completed or updated to an accepted final status.

Tracking

Keep tracking simple.

At Disruption level show:

Affected | Recovered | In Progress | Unassigned | Exceptions

At Passenger Segment level show:

Passenger Count | Recovery Service | Progress | Status

At Passenger level use only:

Not Assigned | In Progress | Recovered | Exception

Allow the caseworker to drill from any count directly into the corresponding passengers.

Integrations

Use:

- Flight Operations System: Inbound API for disruption and flight information
- Reservation System: passenger manifests, alternative-flight search and rebooking
- Hotel Service: hotel availability and booking
- Ground Transportation Service: transport booking
- Messaging Service: WhatsApp Business, with SMS/email fallback

Personas

Use only two internal personas:

Disruption Caseworker: manages flights, passengers, segments and recovery actions.

Disruption Supervisor: monitors overall progress, workload and exceptions and can reassign/escalate work.

Keep the application straightforward and operational. Avoid unnecessary workflows, approvals and screens.

The primary experience should remain:

Disruption → Flights → Passengers → Segments → Recovery Actions → Track Completion → Resolve.

Comments

Post a Comment

Popular posts from this blog

D2 install

import com.emc.documentum.rest.model.Repository; import com.emc.documentum.rest.view.impl.RepositoryView; import com.emc.documentum.rest.context.ResourceUriBuilder; import com.emc.documentum.rest.http.UriInfo; import com.emc.documentum.rest.view.annotation.DataViewBinding; import java.util.Map; @DataViewBinding(modelType = Repository.class) public class CustomRepositoryView extends RepositoryView { public CustomRepositoryView(Repository data, UriInfo uriInfo, String repositoryName, boolean returnLinks, Map<String, Object> others) { super(data, uriInfo, repositoryName, returnLinks, others); } @Override public void customize() { // Build the link as a template for the client to fill // Refer to Guide Section 7.6.3.14 (Page 222) String templateHref = ResourceUriBuilder.onResource("SubmissionExportController") .asTemplate("submissionReference") .build(); // Inject the li...
Read more

Common Lines Finder Java

 import java.io.BufferedReader; import java.io.FileReader; import java.io.FileWriter; import java.io.IOException; import java.util.ArrayList; import java.util.HashMap; import java.util.Map; import java.util.stream.Collectors; public class CommonLines {     public static void main(String[] args) {                 String fileName = "C:\\Users\\Sri Vishnu\\Downloads\\testDupLines.txt";         System.out.println(fileName);         HashMap<String, ArrayList<BatchInfo>> map = new HashMap<>();         int lineNumber = 0;         int minBatchSize =3;         ArrayList<BatchInfo>  lastOccurence=new ArrayList<BatchInfo>();         double threshold = 0.9; // Change this value to adjust the similarity threshold         StringBuilder currentBatch = new StringBuilder();...
Read more

D2-Ref

/**  * D2CollectionServicePlugin.java  *  * Service override — post-processes the collection list returned by  * D2CollectionService to filter collections by case_id of the selected document.  *  * Pattern: IDENTICAL to D2ContentServicePlugin.java from the D2 SDK.  * Dev Guide reference: pp.31-34 "Understanding Service Interface Overrides"  *                      "Post-Processing" and "Setting Up D2 Service Overrides"  *  * HOW IT WORKS:  *   1. D2CollectionService.getCollections() is called by D2 when the  *      "Add to Collection" picker opens in SmartView.  *   2. This plugin intercepts that call, calls super() to get the full list,  *      then post-processes: removes any collection whose name does NOT end  *      with the case_id value of the currently selected document.  *  ...
Read more