Which deployment pattern matches your landscape?
Let us review your current landscape, objectives and relevant data and process requirements.
Customers & use cases
Proven across differently structured travel organisations.
Continental, Airbus and GEA represent three documented deployment patterns: enterprise-owned approvals, international pre-trip processes and cross-functional travel data.
Customer projects in detail
Continental
Continental uses an approval process based on NP4 travel data. The functional approval logic remains independent of the process capabilities of individual travel-provider products.
Starting point
Travel approvals needed to continue following the organisation's rules across different or changing booking environments. This requires the information relevant to each decision to be available in an appropriate functional structure.
NP4 approach
NP4 connects the required travel data with an independent approval process. Journey information, relevant enterprise rules and approval status remain functionally linked.
Use / outcome
The existing approach allows Continental to retain control of its own approval logic rather than tying it to the process capabilities of a single supplier product.
What this case shows
Travel-data consolidation is not limited to reporting. The same data foundation can support organisation-owned operational processes.
Project summary
Continental uses an approval process based on NP4 travel data that significantly reduces processing time, improves the traveller experience and generates positive feedback for Travel Management. Strategically, Continental retains control of its own approval processes instead of depending on the process functions of individual supplier products.
Relevant NP4 capabilities
Which data and approval steps does your process need?