KNet Technologies builds and implements manufacturing execution, scheduling and planning software for steel, aluminium and copper producers — backed by nearly three decades on real mill floors, not just in architecture diagrams.
From advisory through to running software in production — and the scarce domain people who know what a heat, a coil and a caster sequence actually mean.
Independent advice on MES, L2/L3 architecture, vendor selection and roadmaps — from people who have sat on both the plant and the supplier side.
Practical Industry 4.0 for metals: connect the line, get trustworthy data out of it, then automate the decisions that actually cost money.
Custom industrial software built to survive a plant environment — Django, PostgreSQL, React and TypeScript, delivered as versioned, upgradable releases.
Consultants who already speak the domain: PSI Metals, MES, L3 planning and scheduling specialists placed onto your programme without a 12-month learning curve.
A modular, multi-tenant Manufacturing Execution System for mid-size metals plants. Everything the big platforms do at the execution layer, on a PostgreSQL stack with no Oracle licence attached — and priced so a mid-market mill can actually approve it.
Metals scheduling is not generic APS. Each unit has its own physics, its own campaign rules and its own definition of a good sequence. We build them one by one.
Heat-level sequencing through EAF, ladle furnace, degasser and caster — grade groupings, ladle availability, crane and transport constraints.
Sequence building by width, grade family and tundish life. Transition penalties, cast length optimisation, and slab-to-order matching.
Hot strip and plate rolling programmes that respect the coffin curve, roll campaign wear, width step-downs and gauge transitions.
Colour campaigns on the paint line, coating-weight blocks on galvanising, and cold-mill programmes linked back to hot-band availability.
Press and hammer loading with furnace soak times, die changeovers and heat-treatment batch grouping across the shop.
Sinter, pickling, tube, extrusion, rod and wire — the modelling approach is the same. Tell us the unit and its rules.
Most metals groups run several plants that quietly compete for the same order book. Our planning layer makes that allocation explicit — and re-plannable when a caster goes down on a Tuesday.
Plenty of firms can write software. Very few can tell you why your caster sequence keeps breaking at the width transition — and then write the software that fixes it.
Our team has lived through commissioning weekends, L2 handshake failures and month-end reconciliation. That shows up in the design.
An open-source data stack and per-customer deployment model removes the licence layer that puts tier-1 platforms out of reach.
Start with one unit or one module. Prove it. Extend. No two-year big-bang programme with no exit.
We are selecting a small number of design partners to shape DigiPlantMES against real operations. In exchange for your input and a reference commitment, you get terms no one will see again.
For the first three customers, scaled to the reference commitment you make.
Every release on the train, at no additional licence cost.
Continuity protection, so a mid-size supplier is never a single point of failure.