Inuatek A/S

Your equipment needs to report its condition. Does it also need to accept instructions from the internet? 🤔 I am of course referring to the recent attack on supermarket refrigeration systems in France: https://lnkd.in/ecXrEvaB This definitely should make us question how equipment is connected! An understandable reaction is to disconnect everything. But maintaining equipment without knowing how it is performing has consequences too, especially at unmanned installations. A rising temperature, more frequent pump starts or increasing energy consumption can warn service teams before a breakdown. None of those insights requires the ability to operate the equipment remotely. For monitoring purposes, the IoT device can publish measurements to the cloud without subscribing to incoming messages. Broker permissions should enforce that restriction, with no separate remote access or control path enabled. That does not remove every cybersecurity risk. It removes a capability that many monitoring applications simply do not need. Remote access has its place when technicians need to intervene. It deserves a clear operational justification rather than being included by default. There is a cost advantage too. Dedicated monitoring hardware can make connectivity viable for smaller, price-sensitive equipment. This is where I see strong potential in combining e.g. Teracom Ltd. devices with Inuatek DCC: useful service insights at a cost that makes sense. Before pulling the plug, ask whether you can keep the insight and close the control path.

One prompt... A working DCC dashboard ?!? 🫨 When our developer Kasper suggested that an AI assistant could build dashboards directly in DCC, we gave him room to try. Within a week, he showed us his first prototype. He wrote something like: “Build a dashboard for this device and choose suitable widgets based on the sample point names.”.. And the dashboard took shape in DCC before our eyes. I was stunned! Even with a no-code dashboard builder, someone still has to select the data, choose widgets, configure them and arrange the layout. Of course, I had to try it myself, since the prototype was already running in our live test environment.... And it worked! A dashboard was built from my prompt in a few seconds, and when I wanted changes, I simply asked. Better yet, the resulting dashboard actually looked quite cool 😎 The video shows the principle of the concept, but will soon post real screen recordings. What excites me most is how much this could lower the threshold for working with industrial data. You can start by describing what you need, then review and refine the result. Behind it is a DCC MCP server (using the Model Context Protocol) to connect compatible AI assistants with the platform. That gives the assistant access to the context and tools it needs to work with DCC devices, sample points and dashboard widgets. For me, seeing a working prototype within a week also said something about the foundation we have built in DCC: it gives us room to adopt new ways of working as they emerge.. and to do it fast! We are now refining the experience, validating security and permissions, and adding safeguards so users can review, roll back and publish changes when ready. But is already so mature at this point that we dare target it for DCC 7.5 expected next month. But dashboard creation is only the first step. We already plan to extend the MCP integration to let users explore their DCC data through conversation. What would you ask your AI assistant to build from your machine data?

Get a free trial of our DCC platform and gain real-time insights with a custom industrial dashboard. Monitor and track any machine data. The Inuatek Data Collection Cloud

We support eWon, Secomea, IXON, SIA Connect, Teltonika, SENECA, Quake Global and any MQTT-enabled device. Try it yourself - no demo required. Explore our Inuatek DCC and see how the platform handles industrial data, machine fleets and dashboards in a fully configured demonstration environment. No installation. No account creation. No guided presentation required.

Machines running across customers 🧑🤝🧑, sites 🏭 and countries 🌍. One OEM service team. 𝗪𝗵𝗼 𝘀𝗲𝗲𝘀 𝗮𝗻 𝗶𝘀𝘀𝘂𝗲 𝗳𝗶𝗿𝘀𝘁 - 𝘁𝗵𝗲 𝗢𝗘𝗠 𝗼𝗿 𝘁𝗵𝗲 𝗰𝘂𝘀𝘁𝗼𝗺𝗲𝗿? Well.. In my experience, it is most often the customer. Only then does the technician begin reactive troubleshooting. Typically through a remote-access solution, if the customer’s security policies allow remote access at all. But by then, it may already be too late. The machine is standing idle, and production has been affected. The machine may have all the bells and whistles: sensors, alarms and plenty of operational data. If the relevant information had reached the OEM sooner, the service team might have identified the developing issue early enough to avoid the stop; or at least arrived at the customer conversation much better prepared. It may not always eliminate a site visit. But in some cases, it could even remove the need for a remote-access session that potentially conflicts with the customer’s security policies. 𝗦𝗼 𝘆𝗲𝘀,- 𝗰𝗼𝗻𝗻𝗲𝗰𝘁𝗲𝗱 𝗺𝗮𝗰𝗵𝗶𝗻𝗲𝘀 𝘀𝗵𝗼𝘂𝗹𝗱 𝗰𝗵𝗮𝗻𝗴𝗲 𝘁𝗵𝗮𝘁. In this short video, Olivia shows what that change could look like when the OEM gets visibility before the customer calls. Because the objective is not simply to collect more machine data or build another dashboard. It is to help the OEM deliver more value throughout the machine’s lifetime -AND turn that value into a scalable service business. #MachineBuilders #IndustrialIoT #AfterSalesService

Your machines are operating across customers, sites, and countries. But when something changes, who knows first - your service team or your customer? For many machine builders, the answer is still the customer. In this short video, Olivia shows how Inuatek DCC gives OEM service teams a single, cloud-based overview of their installed machine base. When a machine signal crosses a defined limit, the service team can quickly identify the affected machine, see which customer operates it, and investigate the data surrounding the event. That changes the customer conversation from: “What happened?” to: “We can see what’s happening. Here’s what we recommend as the next step.” For the customer, that can mean faster support and fewer interruptions. For the OEM, it creates a foundation for faster diagnostics, stronger service agreements, and scalable, cloud-based after-sales services. Watch the video to see how it works in less than 2 minutes 👇 #MachineBuilders #DigitalServices #IndustrialIoT #OEM #AfterSales