Industrial AI from strategy through PLC — built by the same engineer who designs it.
Vendor-neutral architecture, honest pilots on real production data, and a runbook that survives the handover. Five focused offerings, two in-house products, one founder accountable for every line of code.
Vendor-neutral by default, line-walked before code is written.
When a manufacturer asks me to bring AI to a line, the engagement usually starts with AI Consulting — vendor-neutral architecture before code. From there it might branch into a PLC retrofit if the cabinet needs modernizing, or a system prototype if the integration shape isn't yet defined. When the orchestration layer matters, NexusVisionOrchestrator is the platform I bring; when the vision model itself is the bottleneck, CodingNexusVision is the engine I extend.
Three principles run through all of it. Vendor-neutral by default — the orchestrator drives Maddox Edge, Estek, CodingNexusVision, or any ONNX model in the same recipe, so the architectural decision survives a vendor change. Line walk before code — I refuse to design a PLC retrofit from a Zoom call; the first invoice always covers a physical or video-attended cabinet survey. Real data in the pilot — every pilot runs on production frames the customer captured, not on the vendor's curated demo dataset, because that's where the brittleness lives.
Three engagement shapes.
Each runs as a sequenced engagement with weekly demos, a written phase gate, and an explicit disqualifier section so you can self-screen before the discovery call.
AI Consulting
4–8 week senior-led engagement: vendor-neutral architecture, working pilot on your data, decision document.
PLC / SPS Retrofit
6-week modernization per cabinet: cabinet survey, OPC UA / ADS / S7 protocol choice, bench prototype, staged rollout with rollback.
System Prototyping
4-week proof-of-architecture: spec workshop, one-page architecture, weekly shippable demos, decision-grade prototype.
Two in-house products extend the consulting work.
Both ship as on-premise installers. Both came out of consulting engagements that needed reusable infrastructure.
NexusVisionOrchestrator
On-premise AI vision orchestration. Routes image evaluation to any engine; talks to Siemens, Beckhoff, CODESYS PLCs natively. .NET 8, plug-in SDK, Rete v2 flow editor.
Visit product → LiveCodingNexusVision
Industrial vision-AI engine. Drop-in component for the orchestrator or any other consumer over a clean API. Designed for defect inspection and classification.
Learn more →Three shapes industrial engagements take.
-
Discovery + 2-day workshop
Site visit (DACH) or remote 2-day workshop (US). Inventory existing assets, identify the highest-leverage problem, scope the pilot.
-
Architecture + pilot (4–8 weeks)
Vendor-neutral architecture document, then a working pilot on real production frames. Measured success criterion, decision-grade output.
-
Production rollout (6–12 weeks)
Staged install per line, parallel-run period, runbook + on-call support. Optional retainer for first-90-day stabilization.
Industrial-pillar questions.
What does the Industrial pillar at CodingNexus cover?
Five offerings: AI Consulting, PLC / SPS Retrofit, System Prototyping, plus two products — NexusVisionOrchestrator (on-premise AI vision orchestration) and CodingNexusVision (industrial vision engine).
What does vendor-neutral mean in practice?
Architecture decisions are made on technical merit, not on hidden vendor incentives. NexusVisionOrchestrator can drive Maddox Edge, Estek, CodingNexusVision, or any ONNX model side-by-side. PLC integrations cover Siemens, Beckhoff and CODESYS natively.
Do you do safety-PLC integration?
No. Safety-PLC programming and SIL-rated systems are specialist disciplines — we bring in a partner or refer you to one. We handle the standard-PLC side and the AI/orchestration layer end-to-end.
Can you work fully on-premise without cloud connectivity?
Yes. NexusVisionOrchestrator and CodingNexusVision both run on a single industrial PC with no outbound connectivity. Updates ship as offline installers; license activation is offline.
What is a typical industrial engagement?
Most start with a 4–8 week AI Consulting engagement (vendor-neutral architecture + pilot), then either a PLC retrofit (6 weeks per line) or a system-prototyping engagement (4 weeks per concept). Volumes typically EUR 40–120k.
Industrial-AI discovery call.
30 minutes, no sales pressure. Bring a line photo, a recipe sketch or a vendor quote you want a second opinion on. I'll tell you whether I'm the right engineer for the next step — and if not, who is.
Book an industrial-AI discovery call by email: