This Graphic is Deliberately not accurate, it is only being used to give an approximate impression of its form.

We will only give details about this platform’s capabilities to MoD employees only and we will need to confirm their interest is relevant to any project that we are active in, or wish to be involved in. We will not give details to contractors working for the MoD, nor to any other person.

Summary. This platform’s role is Anti-Submarine Detection. It will be developed and tested to TRL 6 by Summer 2025.

databases

Much of this will be determined by what database skills you have access to.

NoSQL databases are well represented amongst the IoT community, however where a customer has resources and staff skilled and experienced in SQL Databases, then SQL will be a preferred option.

In either case, we suggest considering how you would extricate yourself from a Cloud, should you ever need to do that. One of the services we provide, is building a duplicate IoT solution, at a micro level, deployed on your premises.

dashboards

Perhaps one of the more valuable outputs of an IoT project. This is where your “end-to-end” strategy brings value. It can also be where unexpected costs arise at your Cloud. The things you need to consider are;

• Frequency of updates from remote sensors
• What and why are the remote sensors publishing any new data
• Is new data being uploaded to your database, application or directly to your dashboard?
• Frequency of updating your dashboard? This can have unexpected costs, based on your cloud provider, but can be removed through the correct design.
• Is it a read-only dashboard, or will you allow write commands, to change the behaviour of remote devices?
• Can you have different views of the same data and dashboard? E.g. one as a summary, and another as a graphical “drill-down” as shown in our IoT demonstration page?
• Security of your dashboard. You need to secure your dashboard. A weak security end-point here, gives a hacker access to your complete solution, from databases, to applications.

applications

How many applications will the data from your IoT solution be used in?

Will you also have an edge compute application? What happens to data that is filtered out at the edge? Might that data be useful in the future?

Is this a stand-alone IoT solution, or is it part of something larger? Is your Business changing it’s way of doing things, and is IoT now strategic to you?

What and how will your IoT capability affect your customers, competitors and what changes will be needed from within?

Pricing, for new features and functionality? Is it possible to know what future development costs will be, for a new way of doing things, and a new application?

integrating incompatible IoT sensors

Our real-time data markup protocol converter is essential in projects involving dissimilar sensors. See our live demonstration page for details (3rd example on that page)

At this time we include JSON, XML and PROTOBUF as standard. If you have a different requirement let’s discuss it.

multiple clouds - simultaneously

We set up your IoT gateways so they can connect to multiple clouds – simultaneously.



That can be done in many ways. The reasons for doing this are usually related to data integrity & resilience, and to separate data publishing and maintenance routes.

IoT deployment type

Standard physical IoT gateway, with a Linux operating system, with (or without) edge compute and graphical application environment.

Docker container, in which the application and all its dependencies are packaged together. This can be used on dissimilar platforms, to give a standard operating environment, which makes management & support easier.

artificial intelligence & machine learning

To benefit from A.I. or M.L. one option is to deploy at least part of your application at the edge, directly in your IoT gateway.

The options we suggest include server grade CPU’s and powerful GPU’s. By doing this, you remove WAN latency, and the risk of a WAN link failure.

digitising older systems

For industrial machines we can deliver machine control as well as supervisory capability.

If a production line needs re-configuring, that can be done automatically or remotely by an operator.

We include a user friendly GUI, that can be accessed locally or remotely.