Integration on networks that cannot call out

The engine maps and maintains the interfaces between defence systems from what the data means, and runs entirely inside the network it serves.

The sector

Armed forces, defence agencies and their suppliers run operational, logistics and maintenance systems on segregated networks, many of them under accreditation. Data moves between national systems, allied systems and industry, each built to its own standards.

The problem

Every interface between those systems is mapped by hand, by the few people cleared to work on them, and a change to an interface can reopen its accreditation. So integrations get frozen rather than fixed, and each new system adds to the backlog.

How we fix it

defence · where it breaks and what the engine doeswhere it breaks · the fix swipe →
Where it breaksWhat the engine does
Different standards National, allied and supplier systems exchange data in different message formats, and every interface is mapped by hand. The engine maps each field by what it contains and how it is used, not by its name or format. Cleared staff review what falls below the threshold instead of writing every mapping.
Materiel and maintenance Spare parts, equipment and maintenance data describe the same item differently in logistics, maintenance and ERP systems. Records that describe the same item are matched by content. Each match carries a confidence score, and uncertain matches wait for a person.
Changed interfaces A change can reopen an accreditation case, so interfaces are left alone even when they are wrong. A changed element is re-interpreted and re-scored, and each decision is logged with its inputs, score and timestamp. The assessor can see exactly what changed.
Nothing may leave the network Software that calls home, fetches models or needs a cloud control plane is ruled out before anyone evaluates it. At runtime the engine needs nothing outside your network: no licence server, no model API, no control plane. The models run on your hardware.

What your architect will ask

Can it run on a network with no outside connection?
At runtime it needs nothing outside your network. Installation and updates arrive as container images from our registry. On an isolated network that transfer goes through the media and review process you already use for software, and we agree how before installation.
Is it accredited?
Accreditation is your authority’s decision about your system. What we can give the assessor is a documented architecture with no outbound connection to us or any other third party, isolation between components, and a complete decision log. Source code escrow is available.
Who at masterVantage sees the data?
The engine sends us nothing. If you want our people on the project, they work only on access you grant, which on a classified network means your clearance process, not ours.

Where we would start

On an unclassified network. Run discovery or a single integration there, judge the result, and only then decide whether it is worth taking through accreditation.

Bring us one of your integrations

We will run it against your systems in a working session and show you what the engine does with it.

Book a demo