FLEX stays authoritative
Proposed schedule adapter with versioned mappings and change detection. Q&A estimates FLEX production in Q1 2027. Interface documentation and representative test access remain prerequisites.
TICKETING & RESERVATIONS MODERNIZATION
Trust the handoff.
Explore the controls that keep data consistent when systems change.
Synthetic demonstration
No live WSF connections
No live WSF connections
Independent SIG.AI response. This lab uses invented data and runs entirely in your browser. It performs no payments, reservations or boarding actions.
Q&A 32 + 37
The right rides. On the right card.
Matching totals can hide errors. Compare each account, physical card and product.
Choose a migration scenario
| Card / account | Source | Target |
|---|
One active product per physical card in this fixture. The production data model requires WSF validation.
Inspect the matching rule
Key: account_id + card_id + product_id. Every key and integer ride count must match. Missing records, changed identities, duplicate cards and invalid ride counts block acceptance. Ride entitlements are not money and are not reconciled to Great Plains.
RESILIENCE + RECONCILIATION
A retry is not a second payment.
Inject synthetic events. Inspect what the journal accepts, ignores or flags.
Payment event stream
Start with a timeout, then deliver a provider callback. Replay the same callback or deliberately reuse its ID with a changed amount.
The amount is a synthetic $25.90 transaction. This is an event-processing fixture, not a WSF fare or a payment connection.
Inspect the event contract and projection
The allowlist rejects unexpected fields; no payment-card data is accepted. Identity is source + event_id. A changed payload under the same identity flags both affected objects. In production, authenticated callbacks, durable storage and settlement reconciliation are required.
OFFLINE CLAIMS
Two devices. One ticket.
A local scan cannot establish global exclusivity while terminals are disconnected.
Synchronize scan claims
Click a terminal again to replay its identical event. Distinct terminal claims are retained for the selected ferry platform to resolve under WSF's operating rules.
PROPOSED DELIVERY BOUNDARIES
One connected journey. Clear owners.
These are proposed interfaces. No live external integration is connected to this lab.
WSF-selected ferry platformFares, reservations, tickets, validation and entitlements
Payment & device suppliersCard capture, certification, processing and field hardware
↔ Versioned events & supported APIs ↔
SIG.AI integration servicesContract validation → deduplication → projections → reconciliation → review queueMigration, integration tests, monitoring and controlled cutover
↔ System-specific adapters ↔
WSF & system ownersData access, business rules, security decisions and production acceptance
Authoritative external systemsFLEX · Great Plains · WA.gov · selected CRM
Rides and billing stay distinct
Physical revalue cards hold rides. Great Plains retains business-account billing with bank lockbox payments. Migration reconciles ride entitlements separately from financial records.
Integrate the selected services
WA.gov identity and a selected external CRM require supported contracts and security review. There is no legacy CRM to migrate. Bidirectional CRM flows depend on each use case.
Resolve dependencies early
ORCA documentation is expected with the RFP. Good To Go! documentation is not yet available. No existing adapter, certification or commercial access is claimed here.
From this lab to production
1. Agree data ownership, interface contracts and acceptance criteria in WSF's Azure DevOps environment.
2. Replace synthetic sources with authenticated, supported sandbox endpoints.
3. Add transactional persistence, access controls, monitoring and retention policies.
4. Rehearse migrations, recovery and end-to-end workflows; validate load and device behavior.
5. Obtain WSF approval before a controlled pilot and phased rollout.