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)

Data Frequency ↗

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 & SYNC HEALTH Live source feeds for tenant solstice

Conflict reconciliation and dead-letter replay live in The Resolver (see the Tools rail) — opened only when a feed actually diverges. The canonical entity browser is on the Model tab.

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

A tour, in strata

One tour departure on the surface; its supporting data in layers below — deeper means further from the guest.

TOUR STRATA Height = information weight · color = track · the strip = how far the data matures (Pre / Voyage / Post) · click any card to pin it everywhere

The canonical model

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

CANONICAL ENTITIES Color = track · bar = information weight · lines = connections · details live on the strata cards above (switch to Detail)
FIELD MAPPING Coverage at a glance · switch to Detail to map individual fields to a source
TARGET APP Lodestone
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?

Drill to the level you’re working at, pick what you need, and get the source systems to use — and why.

1 Where in the lifecycle?
Click a level to scope · Season → Voyage → Tour Day → Departure → bus-level dispatch
2 What are you working on?

Operational flow

Follow one excursion from catalog to settlement.

STORYBOARD One excursion, catalog → settlement · phase color · how often each step changes
1 season many voyages many tour days departures bus-level dispatch