network

It is a common problem for many businesses, that systems designed to solve specific problems are not designed to talk to each other.

We’ve been considering this problem ourselves in the design of our systems at Inquiron. While our platforms have solved a range of problems for our clients in high-risk countries, we’ve found new challenges that require data from multiple systems.

For example, it was obvious that our Vehicle and Driver Analytics system would need vehicle tracking feeds, but we’ve seen increasing interest from Security Managers to have access to those same feeds for threat assessments in our Incident Management System.

Similarly our Personnel Monitor has found increasing demand for those feeds to automate the previously manual process of filling out a Personnel on Board sheet.

And in this communication problem we also see the potential for an integrated system for Journey Management, a leap from event reporting to aiding and optimising operations.

To plan journeys in high-risk environment can be extremely time consuming, relying on driver and vehicle data to know what assets are available, security data to choose safe routes and Personnel data to book journeys on the correct day and time, as well as a swath of risk assessments and approvals, or even unnecessary guesswork.

This requires a large and inefficient communication network for a day-to-day problem, that we can solve quite simply by a new system, communicating with our incident management, vehicle and driver analytics, and personnel tracking applications to book, plot and dispatch journeys instantly.

This represents a real time saver, and translates to a much more efficient use of resources.

This is why we have committed to interoperability between our platforms, designing and building APIs (interfaces) to access data from all our current applications, and building new applications quickly with those APIs.