For fifty years machines obeyed commands. The next curve is different — machines that explain, negotiate, and converse. IONECT builds the products and services that give any machine that capability.
"Cable temperature is 62 °C. I'm derating to 38 kW until it cools."
"Forecast says clouds at 14:00. Want me to pre-charge batteries?"
"Peak is in 42 minutes. I'll cover 180 kW from storage — you'll save ฿3,400."
Show me any station below 90% uptime this week.
Every generation of automation rides an S-curve. Mechanical arms gave machines muscles. Sensors and vision gave them eyes. We are at the foot of the next curve — the one where machines understand language, hold a conversation, and explain themselves. IONECT exists to accelerate that curve and to build the products that live on top of it.
A conceptual map of three overlapping eras of machine capability — illustrative, not to scale.
Machines do what we tell them. Press a button, turn a valve, execute a program. The language is binary — commands in, state out.
Machines report what they see. Sensors, cameras, telemetry — dashboards full of numbers. Humans still do all the thinking.
Machines explain, negotiate, propose. They speak our language and reason about their own. This is the curve IONECT builds on.
Every industrial operator today drowns in dashboards. Graphs. Numbers. Colour-coded alerts. The information is there — but a human still has to connect the dots. Talkable machines close that gap. They don't just report; they explain, recommend, and act.
This is a typical machine communication log — the kind of system messages, process events and protocol traffic every connected device produces. It tells you what happened, not why. Operators have to read the stream, cross-reference manuals, check the values and call a technician to interpret it. The machine itself stays silent.
The operator asks in plain language. The machine reads its own communication log, correlates the events, explains the root cause, and proposes a concrete next step for a human to approve — minutes instead of hours, no protocol decoding required.
Four building blocks — designed to be added step by step. Start with the foundation, layer in context, then reasoning, then conversation. Each one stands alone; together they make a machine talkable.
The first step. The machine has structured access to its own protocols (OCPP, Modbus, proprietary), its firmware version, its error codes and its maintenance history — so questions about itself are answered from real data, not guesswork. This is the data foundation everything else stands on.
Layer in the human-written context. PLCs and historians log structured data well — registers, alarms, timestamps. What they cannot do is read the manual, parse a vendor's release notes, or interpret a free-text fault description. We build a knowledge base of manuals, firmware notes, fault history and operator playbooks — so the machine can connect structured telemetry to unstructured documents and explain the root cause in plain language.
Now the machine can propose. It weighs trade-offs — revenue vs safety, comfort vs cost, now vs later — and recommends an action for a human to approve. Autonomy is opt-in, scoped, and always bounded by safety policies you control.
Finally, expose it to humans. Operators, technicians and drivers speak to the machine in plain English or Thai across chat, voice or app. Under the hood, an LLM grounds every answer in the foundation, context and reasoning layers below — designed to minimise hallucinations and cite the data behind every response.
We can build at every layer of the stack — but every engagement is different. Some pieces we bring off the shelf, others we custom-build for your machines, your protocols and your operators. The point is end-to-end coverage with no vendor seams.
Buy a product. Commission a service. Or both — we design for whichever shape fits your operation.
A white-label CSMS where operators, drivers and technicians interact with chargers through conversation as well as the dashboard. OCPP-native and operating in pilot deployments.
An IoT gateway designed to bring legacy fleets — chargers, ESS, HVAC, generators — onto the conversational layer. Reference designs in development; available for design-partner engagements.
Your hardware, your brand, your domain. We co-design the conversation, write the firmware glue, build the context layer, and ship a product your customers can talk to — across chat, voice or app.
Making a machine talk is not an AI problem. It is a full-stack problem — silicon, protocols, cloud and language, all the way through. We have spent seven years assembling exactly that stack.
Tell us about the machine, the operator, and the job to be done. We'll come back with a conversation flow, a candidate stack, and a plan tailored to your scope.
The talkable curve is moving fast — first movers shape the conversation.