Control logic reviewed before it reaches the plant.
For controls, commissioning and DCS engineers. Your vendor compilers, controllers and change process stay as they are.
- Standards
- IEC 61131-3 · IEC 62443
- PLC
- Beckhoff TwinCAT 3 first; CODESYS and TIA Portal to follow
- DCS
- Emerson DeltaV, from FHX exports
- Agent policy
- PLC and OT sector template
- Deployment
- Self-hosted, your cloud or air-gapped
What your team gets
PLC and DCS engineering, with your vendor engines underneath.
Govern features are in use today. Domain modules are pre-release; their state is listed under Tools and formats.
Who uses it
One environment for every role on the team.
Tools and formats
What the PLC and DCS modules handle, and how far each is verified.
Both modules are behind a setting, off by default, and run only in a trusted workspace.
Domain modules are pre-release. Nothing is verified by a customer yet, and nothing is verified on Windows. Do not rely on a capability for production work until it is verified for your tools, versions and operating system. Product names belong to their owners.
How a change moves
A person decides before anything leaves the desk.
- ProposeAn engineer or agent drafts a change to control logic.
- VerifyYour vendor compiler builds it.
- ApproveA change to safety logic waits for a named approver.
- RecordChange, results and approval kept together in the audit record.
Standards
Evidence for your plant's change process. The certification is yours.
Neural Inverse provides evidence toward these standards. Certification stays with your organisation and assessor.
Products used
Product names belong to their owners.

Talk to our team.
Neural Inverse is available by request. We work with your engineering, security and procurement teams from the first conversation.