SHOREX · DATA ADAPTOR

The shorex toolset, and the shape it all runs on

Jump into any tool below, or read the lifecycle: how a season nests down to a single bus, colored by phase — the structure every downstream tool inherits.

Stages as nested object boxes with slim close-in and post-recon sections, colored by phase; tool icons pinned to the stages each tool reaches STAGE 1 · SEASON Season the planning horizon STAGE 2 · CLOSE-IN STAGE 3 · VOYAGE Voyage STAGE 6 · PR VOYAGE STAGE 4 · CLOSE-IN STAGE 5 · TOUR DAY Tour Day STAGE 6 · PR TOUR DEPARTURE Departure(s) bus-level dispatch units STAGE 7 · POST-CRUISE Post-Recon final settlement After all tour and voyage actuals are captured (slims to the left), final GL postings, credits, and loyalty close out the books. PHASE Pre-Cruise Operational Post-Cruise slim sections = transitional close-in (Stage 2/4) and per-level post-recon (Stage 6)

Connections & the cell matrix

Wire each source system, then map every track × stage cell to one. The canonical model lives on the Model tab.

CONNECTIONS Source systems wired up for this tenant · health, role, contributed entities

Source systems shown here are for tenant solstice. Full adapter operations — reconciliation queue, dead-letter, canonical entity browser — live in the standalone shorex-adaptor/ page.

CELL MAPPING Global defaults · all ships, all seasons · click a cell to inspect
Dispatch Tour Day
FIDELITY LADDER reaches Operating
SOURCES (PRIORITY ORDER)

The canonical model

The entities the adaptor produces, and the source-field mappings behind each.

CANONICAL ENTITIES The schema the adaptor produces · each entity has one authoritative source, with others contributing fields
FIELD MAPPING Each (source × entity) pair has its own mapping · expand to see the field table
TARGET APP
VALUES
PREVIEW

Find where your data lives: check a data need to see where it should come from, or follow the operational flow end to end. The structural map lives on the landing page.

Where should this data come from?

Pick the part of the process in focus to get the source systems to use, and why.

1 What detail level?
2 What are you working on?

Operational flow

Follow one excursion from catalog to settlement, then explore the live flow.

STORYBOARD One excursion, catalog → settlement · phase color · how often each step changes
1 season many voyages many tour days departures bus-level dispatch
LIVE FLOW Each lifecycle node, the systems that feed it and how active each track is · click to drill in