IBS iLogistics, in its own words
iLogistics Personnel Logistics provides "a commercial-travel-like experience" for FIFO personnel: end-to-end travel by commercial and charter airlines, helicopters, crew boats, buses, trains, and cars, with accommodation at camps and offshore assets, map-based seat selection, self-service check-in, multi-level approval workflows, rotator and crew scheduling, personnel-on-board tracking, and deep safety compliance — training certifications, medical requirements, and no-fly rules enforced before travel. It sits inside a broader IBS suite spanning airline passenger systems, cargo, and energy logistics, backed by a consulting and digital-transformation practice.
That is real depth — particularly offshore, where helicopter and crew-boat operations with certification gating are their own discipline — delivered by an organisation of enterprise scale.
Two descendants of the same ancestor
Here is what makes this comparison unusual. IBS also builds iFly Staff — airline staff travel: entitlements, standby, and quotas for an airline's own employees, one of the most sophisticated allocation problems in travel. UnityTrip's founders built the previous generation of regional-airline operational systems, and UnityTrip is that same staff-travel discipline generalised: entitlement, standby, and quota thinking applied to any organisation's own transport, not only an airline's employees.
So the two companies hold the same insight — that seats without fares must be allocated by policy — and deployed it differently: IBS kept it inside the airline world and built a separate operational-logistics suite for energy; UnityTrip fused the two, putting the staff-travel allocation engine at the centre of workforce travel itself.
The difference is what counts as the hard problem
iLogistics treats the hard problem as operations and safety: get personnel to remote and offshore sites compliantly, trackably, and comfortably. Those are necessary things, and it does them at scale. UnityTrip treats the hard problem as allocation and accountability: the seat has no fare, so policy is the economic instrument — a priority matrix, quotas, booking windows, and penalty points rationing scarce seats — go-show automation refills what no-shows free, and the money loop closes in the same platform: budget approval in the booking flow, expense claims alongside bookings, and for business bookings no payment without an approved claim number.
The delivery models differ the same way. An enterprise suite of this breadth is typically bought and implemented as a programme, supported by a transformation practice. UnityTrip is built so the programme is unnecessary: onboarding is configuration, not migration — measured in weeks — the platform is transactable on the Microsoft Azure Marketplace, and the depth is published rather than presented: the API and ontology reference, the policy JSON Schema, and measured outcomes stated plainly.
What UnityTrip puts on the table
- Policy as the economic instrument — priority, quotas, booking windows, and penalty points executed by a deterministic engine, with every decision reproducible from the event record.
- Go-show automation and measured outcomes — no-shows down by roughly half, leased-fleet seat utilisation lifted from a ~40% industry average to around 90%, published with the levers behind them.
- The money loop closed — budget approval at booking, expense claims in the same platform, no payment for business bookings without an approved claim number, bidirectional SAP in production.
- Weeks, not a programme — per-tenant configuration on one codebase, provisioned through infrastructure as code, purchasable through the Azure Marketplace and billed through your existing Microsoft agreement.
- Published depth — the platform thesis, ontology, specs, and outcomes are on the open web for any evaluator to check.
Where IBS is strong
Honest scorekeeping: offshore modal depth — helicopter operations, crew boats, certification and no-fly gating — is genuinely specialised ground; suite breadth across passenger, cargo, and material logistics suits organisations consolidating on one enterprise vendor; and a global delivery organisation is an asset for multi-region programmes. An airline moving its own staff sits squarely in iFly Staff's home category. And where an operator already runs iLogistics for offshore operations, the practical question is the same one UnityTrip answers everywhere: integration rather than replacement — existing operational systems plug in beneath the policy layer.
Choosing between them? The ten evaluation questions separate the architectures — put them to every vendor, including us.
Common questions
Is UnityTrip an alternative to IBS iLogistics?
For the travel and policy layer of personnel logistics, yes. iLogistics is an enterprise suite — multi-modal transport, accommodation, safety compliance — from a large global vendor. UnityTrip is a focused platform that treats allocation and accountability as the hard problem: seats without fares rationed by deterministic policy, the finance loop closed in the same platform, and onboarding in weeks as configuration rather than an implementation programme.
What is the main difference between UnityTrip and IBS iLogistics?
What each governs, and how each is delivered. iLogistics governs movement and safety compliance; UnityTrip governs movement and money — policy as economics, go-show refill, budget approval and claims in the booking flow. IBS delivers an enterprise suite with a transformation practice; UnityTrip delivers configuration on one codebase, transactable on the Azure Marketplace, with outcomes and ontology published.
How are UnityTrip and IBS iFly Staff related?
Same ancestor, different descendants. iFly Staff is airline staff travel — entitlements, standby, quotas for airline employees. UnityTrip is that discipline generalised to any organisation's own transport: leased aircraft, chartered vessels, buses, and guesthouses. An airline moving its own staff is iFly's home ground; an energy or resources operator flying its workforce on its own metal is UnityTrip's.
When should an organisation choose UnityTrip over IBS iLogistics?
When the binding problem is allocation and accountability rather than suite breadth: seats rationed by priority and quota rather than scheduled only; utilisation outcomes the vendor publishes rather than implies; spend that reaches finance as governed data with approval enforced at booking; and onboarding that must be weeks of configuration, purchased through a cloud marketplace, rather than an enterprise programme.