Skip to main content

What Traveler Identity Service does — and what it doesn't

Traveler Identity Service (TIS) is the runtime engine and data repository at the center of the platform. This page sets its scope explicitly: what TIS itself takes responsibility for, and what is owned by other modules of the Border Control Platform.

What TIS does​

  • Multimodal matching — native processing for face, fingerprint, iris, palmprint, and contactless fingerprint (images and templates), with fused multimodal scoring
  • Identification (1:N) — searches the full database or logically isolated galleries; targeted identification scopes search for latency and false-positive control
  • Verification (1:1 and 1:few) — confirms whether a presented probe matches a known reference
  • Enrollment — accepts capture from any of the channel modules; runs deduplication before committing
  • Traveler register — persistent biometric and reference data for every enrolled traveler
  • Galleries & watchlists — internal and integrator-defined groupings used to scope identification and matching; internal watchlist checks exposed via secure APIs
  • Configurable scoring & thresholds — partial, modality-specific, and fused multimodal scores with deployment-tunable thresholds
  • Stateless / semi-stateful / stateful matching modes — flexible deployment for different operational scenarios
  • Deduplication — built-in duplicate detection at enrollment with continuous data-quality checks
  • Web UI for operations — applicant records browser with full transaction and audit context, available to operators and supervisors
  • Workflow orchestration — routes low-confidence or exception cases to an adjudicator for manual review and decisioning (the adjudication workflow itself is owned by Traveler Management Module)
  • Secure APIs — enrollment, search, watchlist, and system-integration endpoints
  • RBAC — operator, supervisor, adjudicator, admin roles, each scoped to permitted data and actions
  • Audit-ready persistence — full transaction context, audit trails, and resolution actions persisted for governance
  • Identity-subset distribution — TIS distributes time-windowed, location-scoped identity subsets to validation endpoints (Smart Corridors, eGates, border posts) so they can run identification locally and stay operational during link degradation

What TIS deliberately does not do​

TIS is the matching engine and the biometric data repository — nothing else. The following live in other modules of the platform:

  • No officer UI — TIS has no Traveler Hub or operator-facing screens. UI lives in Traveler Management Module.
  • No workflows — configurable operational workflows (adjudication queues, status transitions, exception handling) are owned by Traveler Management Module.
  • No encounter data — encounter events (the immutable record of border interactions) are owned by Traveler Management Module. TIS does not persist or expose them.
  • No journey data — journey records (planned and actual traveler movement on a transport instance) are owned by Traveler Management Module. TIS does not persist or expose them.

The Audit GUI delivered with TIS ABIS (biometric record browser, fingerprint adjudicator, split-screen audit) is a low-level operator tool for ABIS administration — distinct from the person-centric Traveler Management UI.

See also​