A Programmable Logic Controller is the small, stubborn computer that actually runs the machine. It reads sensors, decides in milliseconds, and switches motors, valves, conveyors and robots. No mouse, no dashboard, no opinions — just a scan loop that never gets bored and never misses a cycle.
PLCs live where software meets steel. They are built for the shop floor: hardened against heat, vibration and electrical noise, deterministic in timing, and safe by design. When a press has to stop in ten milliseconds because a light curtain broke, that decision belongs in a PLC — not in a cloud service three network hops away.
What a PLC actually does
- Executes control logic on a fixed scan cycle — inputs read, logic solved, outputs written, every few milliseconds.
- Drives the physical layer: motors, drives, valves, pneumatics, robots, conveyors, fixtures.
- Enforces interlocks and safe states, so a machine cannot be commanded into a dangerous condition.
- Runs the right recipe and setpoints for the right part and revision.
- Emits the ground truth — counts, cycle times, alarms, downtime reasons, process values — that everything upstream depends on.
In most plants the PLC is an island. Its logic lives in a vendor tool, its tags live in a spreadsheet, and the data it produces gets scraped by middleware nobody wants to own. The machine knows the truth; the business finds out later, in a different format, minus the context.
Natively connected, not glued together
N23D runs one data model from geometry to shipment. The controller is not a stranger bolted on at the end — it is part of the same system as the design, the toolpath, the route and the audit trail.
- One data model. A tag, a machine, an operation, a part revision and a nonconformance point at the same objects. No mapping tables, no nightly sync, no drift.
- No export/import loss. CAM output, setpoints and recipes reach the controller without a round trip through post-processors and hand-edited files.
- Auditability by default. Logic versions, parameter changes and alarm history are versioned and attributable — who changed what, on which machine, against which revision. A query, not an investigation.
- Speed. 100% Rust from the edge upward: native performance, small footprint, predictable latency, no runtime surprises between the machine and the record.
- Sovereignty. Your logic, your tags, your process data, on your infrastructure. No lock-in on the layer that runs your factory.
Connect the controller natively and everything upstream stops guessing: MES dispatches against real machine state, QMS sees process values instead of after-the-fact samples, ERP costs the job on actual cycles, PMO tracks a plan that matches the floor, and CRM promises dates the machines can keep.
Explore the platform, and the connected disciplines: 100% Rust · CAD · CAM · CAE · PLM · ERP · MES · QMS · PMO · CRM
