From APIs and data foundations to TMCs and travel risk management: explore key travel-data architecture terms, their meaning and their relevance to NP4.
The definitions explain technical and functional terminology. They do not constitute legal advice or imply that every capability described is automatically included in an NP4 implementation.
24 terms
Updating glossary …
Application Programming Interface
An API is a defined interface through which software systems exchange data or access functions. The available information and actions depend on the interface and its access permissions.
NP4 uses available APIs to connect agreed sources and target systems. The scope depends on the provider, permissions and project.
Connectors & APIsDecisioning · Travel Approvals
Approval logic describes the rules-based assessment and control of an approval using defined inputs and enterprise rules.
At NP4, approval logic primarily relates to travel approvals and renewed assessment when relevant journey information changes.
TD goA data contract describes the data one system supplies to another and how it should be understood and processed. It can define fields, formats, meaning, freshness, quality rules and responsibilities.
NP4 separates source connections from the defined data contracts used by recipients such as Finance, BI or Corporate Security. The details are agreed within the project.
Connectors & APIsShared Data Foundation · Travel Data Foundation
A shared data foundation makes related, prepared information available to defined applications and processes. It supports purpose-specific data views and consistent downstream processing.
At NP4, the shared data foundation sits within the Travel Data Suite. TD pool supplies consolidated travel data; the other products use that foundation for their respective tasks. Data Foundation is not another name for TD pool.
Data FoundationGovernance
Data governance defines rules, roles and responsibilities for using and processing data. It can specify who may receive which data for which purpose and how changes and quality issues are handled.
NP4 implements agreed permissions, quality rules and purpose-specific data views within the relevant data and operating model.
Data Quality & GovernanceHere, data portability means the technical ability to take over, transfer or use agreed data in other systems through defined formats. Data scope, structure, permissions and delivery methods determine what is possible.
For provider changes, M&A or carve-outs, NP4 can support agreed data transfers. Their scope and target structure are defined for the relevant transformation.
A data product is a documented data offering for a specific business purpose. Alongside the data, it can include a defined scope, meaning, quality characteristics and an agreed access or delivery method.
In the NP4 context, the term describes defined data deliveries for agreed recipients and applications. It does not identify an additional software product in the Travel Data Suite.
Data Quality describes how suitable data is for a particular business purpose. Relevant aspects can include origin, freshness, completeness, consistency and the treatment of conflicting information.
The quality characteristics and validation rules that apply within an NP4 project are defined for the relevant sources and process requirements.
Data Quality & GovernanceA Direct Connect is a direct technical connection to a travel, content or data provider. It can transfer data or content outside a traditional GDS data flow; the concrete scope depends on the provider, contract and technical access available.
Direct connections can be part of an NP4 integration alongside TMC, GDS, OBT and other sources.
Connectors & APIsIn business travel, duty of care refers to an organisation’s responsibility to consider the safety and wellbeing of its travellers appropriately. Travel risk management describes the processes used to address travel-related risks systematically.
TD care supports the data and communication-related parts of these security processes. Organisational responsibility, decisions and actions remain with the company.
TD careGLOBAL DISTRIBUTION SYSTEM
A Global Distribution System is a technology platform that connects travel providers with travel sellers. Travel sellers and TMCs can use it to access travel content, availability and fares from connected providers.
GDS and PNR data are among the potential data sources for the NP4 Travel Data Suite.
IntegrationsMultiple TMCs
Multi-TMC describes a corporate travel landscape using several Travel Management Companies, for example across countries or entities. Their data and processes need to be brought together for shared oversight.
TD pool consolidates travel data from the agreed TMC sources for the shared data foundation within the Travel Data Suite.
Multi-TMCNEW DISTRIBUTION CAPABILITY
NDC is an airline-distribution data standard developed by IATA. Its exchange format is based on Offer and Order processes and enables structured communication of airline offers and orders regardless of the distribution channel.
NDC is one of the data and distribution models that can form part of modern heterogeneous travel landscapes alongside traditional GDS and PNR structures.
PlatformONLINE BOOKING TOOL
An Online Booking Tool is a digital booking interface that allows employees to search for and book business travel themselves. Corporate programmes typically use OBTs with defined booking content and travel policies.
NP4 treats OBTs as potential booking and data sources within a broader travel landscape.
PlatformTravel outside connected booking channels · Trip Logging
Here, off-channel refers to travel that is not automatically transmitted to NP4 through connected booking channels. Being captured outside a connected channel does not by itself mean that a trip breaches company travel policy.
Within the agreed setup, Trip Logging can capture these trips through an Outlook add-in or a web form and pass them to TD pool in a controlled way.
PASSENGER NAME RECORD
A Passenger Name Record is a booking record in a reservation system. It can include names, itinerary details and ticket or booking information. A PNR is a source record and does not automatically represent the complete journey across all sources.
NP4 can consolidate PNR-based travel data within the agreed scope and make it available to defined downstream processes.
A Provider Migration is the controlled transition from one TMC, OBT or other travel, security, data or content provider to another. New data sources and formats need to be integrated without unnecessarily binding downstream processes to the technical logic of either the old or new provider.
NP4 separates source connectivity from defined data and process views for reporting, duty of care, approvals, communications and enterprise systems.
Provider MigrationRisk Information · Riskline
Risk intelligence is prepared information about risks, events and their geographic or time-related context. Assessing a specific journey requires relating this information to available travel and company data.
TD care can optionally integrate external risk intelligence, such as Riskline, into defined security and communication processes. Actual use depends on the integration, available data and configuration.
Optional risk integrationSingle Sign-on · Single Sign On
Single sign-on enables access to connected applications through a shared identity or central identity provider. Signing in and being authorised to use particular functions or data remain separate concerns.
Traveller Hub can be integrated into an existing sign-in environment through SSO. The specific integration is defined within the relevant setup.
Traveller HubTRAVEL MANAGEMENT COMPANY
A Travel Management Company organises and supports corporate travel programmes. Depending on the provider, services can include booking, traveller support, travel policy, supplier management and reporting. A TMC therefore extends beyond a simple booking interface.
NP4 can integrate travel data from one or several TMCs into a provider-independent data and process landscape.
Multi-TMCTravel data consolidation brings available travel information from multiple sources together, checks and standardises it, and connects related information. This provides consistent data for downstream processes.
TD pool handles travel data consolidation and passes the prepared data to the shared data foundation within the Travel Data Suite.
TD poolNP4 Travel Data Suite
The Travel Data Suite is NP4’s product family for travel data consolidation, duty of care, traveller communication, reporting, travel approvals, and data integration and distribution. Products are combined to suit the required tasks.
The shared data foundation sits within the Travel Data Suite. TD pool consolidates incoming travel data; TD care, TD doc, TD chart, TD go and TD hub use that shared foundation for their respective tasks.
Products overviewISO 31030
Travel risk management covers the systematic identification, assessment and treatment of risks associated with business travel. It includes organisational policies, responsibilities, preparation and incident handling. ISO 31030 provides structured guidance for this work.
NP4 supports defined data and communication processes, particularly through TD care and optional risk integrations. A product alone does not replace an organisation-wide travel risk management programme.
Travel Risk & Duty of CareEvent Notification
A webhook sends a message to an agreed endpoint when a defined event occurs. This lets a receiving system react to a change without repeatedly checking for new data.
Webhooks are one of NP4’s possible integration methods. Events, data scope, delivery and error handling are defined for the relevant connection.
Connectors & APIsLet us review your current landscape, objectives and relevant data and process requirements.
Necessary cookies keep this website running. Optional analytics, marketing or social-media trackers are not currently embedded. Your choice is stored for 6 months.
