Dynexis is now officially registered and live. This is the first post, so it makes sense to explain what the company is, where it came from, and what we are building.
The problem I kept running into
I have 15 years of working experience as an automation service engineer in the process industry. Power plants, industrial sites, facilities where equipment runs around the clock and the maintenance record matters. Over the years, one thing kept repeating itself: the gap between what operators observed and what actually ended up in the system.
It is not that people are careless. The problem is structural. You notice something at the machine, finish the job, move on to the next task. By the time you sit down to write the ERP note, it is two hours later and you are working from memory. Equipment codes get approximated. Context gets lost. The maintenance history, which should be a reliable record, becomes something engineers learn not to fully trust.
Shift handovers have the same problem from a different angle. The outgoing operator knows what happened. The incoming one needs to know. But the logbook is free text, written in a hurry, with no consistent structure. A lot of operational knowledge transfers verbally, if it transfers at all.
Forma was built to close that gap.
Two tools, one workflow
Forma has two parts. The first handles ERP notes. The operator speaks an observation at the machine, immediately after the job. Forma transcribes it, structures it into an ERP-ready note, and delivers it by email. The whole thing takes about thirty seconds. The note is ready to paste.
The second part is Shiftlog. Operators log observations throughout the shift, by voice or by typing, and each entry is structured automatically by severity, equipment, and category. At the end of the shift, there is a complete, searchable handover log ready for the incoming team. Not a wall of free text. Not a verbal briefing that half-lands. A structured record of everything that happened, organised in a way the next operator can actually use.
In most shift-based environments, the handover is where operational knowledge either survives or disappears. Shiftlog is built around making sure it survives.
There is one more thing worth saying about both tools. In any team of operators, people write differently. Some are comfortable producing detailed written reports. Others find it harder, for all kinds of reasons: language background, dyslexia, the pace of the job, or simply never having been trained to write technical documentation. With Forma, that difference disappears. You speak what you observed, and the output is structured and consistent. The quality of the report no longer depends on who wrote it.
Where Forma fits
The voice-to-documentation pattern works well anywhere operators move between equipment and a documentation system that expects structured input. That covers a lot of ground.
Process industry is the obvious fit: power generation, water treatment, oil and gas, chemical production. Operators in these environments deal with SAP or similar systems daily, work in shifts, and document faults, inspections, and maintenance observations as a matter of routine. Forma slots directly into that workflow without requiring any integration work.
Shift-based manufacturing has the same dynamics. So does facilities management, where a technician might service twenty pieces of equipment in a day and needs a consistent record of each visit. Security operations, where observation logs matter for audits and incident review, are another natural fit.
The common thread is this: a person who knows something, a system that needs to capture it, and a gap in between where the knowledge currently gets lost.
What comes next
Forma is the first product. The longer plan is a suite of tools for industrial operations: certification management, digital work permits, and eventually a layer that connects the data from all of them into a single operational picture. Each product is useful on its own. Together they start to close the compliance and knowledge gaps that most industrial sites manage manually today.
I am building this as a solo founder alongside my main job, so the pace is deliberate. The priority right now is getting Forma in front of real operators and learning from that.
First pilot conversations
Forma is ready for its first pilots. If you work in process industry or a related field and recognise the documentation problem described above, I would like to talk. No commitment, no sales process. A conversation about whether Forma fits your workflow, and if it does, a short pilot to test it properly.
Get in touch at info@dynexis.net.