Heat-number-centred traceability
Every heat becomes a record; the charge composition, analysis results, the products made from it and the customers they shipped to are linked to that record. The chain can be queried both forwards and backwards.
We do not replace your accounting backbone. We bring charge and heat planning, heat-number traceability, laboratory analysis records, quality certificate generation, energy consumption and the emissions data requested on exports to Europe together in a single operational layer. Not an off-the-shelf package — built for your plant. The source code stays with you.
In steel, traceability is not a preference — it is a condition of trade. The buyer wants a certificate, the certificate rests on the laboratory analysis, and the analysis rests on the heat number. If one link of that chain is unrecorded, the whole chain falls apart the moment someone asks.
There is a clear software divide between large integrated plants and mid-sized rolling mills. The upper segment runs industry-specific imported systems, while in the mid segment the gap between the accounting ERP and Excel is bridged with a notebook.
| Layer | Software in use today | The gap it leaves |
|---|---|---|
| General ERP / accounting (horizontal backbone) | Logo Tiger, Logo Netsis, Mikro, SAP, CanIAS | Solid for customer and supplier accounts, stock, purchasing, finance and e-documents, and it stays in place. Its limit is that it does not carry steel's own concepts: heat numbers, analysis values, quality certificates and length-based stock are not standard in these systems. The traceability chain therefore has to be built alongside the ERP, not inside it. |
| Industry-specific production management (imported) | PSImetals and similar production management systems built for the metals industry | Broad systems that meet the industry's needs in depth, from heat planning to quality management, and they are established in large integrated plants. Licensing, adaptation and maintenance costs are usually out of reach for mid-sized rolling mills. At that scale the need is most often not a full-scope system but the traceability and certificate chain. |
| Process automation | PLC and SCADA systems on the furnace, casting and rolling lines | Necessary for process control and rich in machine-level data; temperature, current, speed and cycle information originates here. But linking that data to heat numbers, orders and costs is not automation's job. The result is plenty of data on the floor while the commercial questions go unanswered. |
| Laboratory and analysis | The spectrometers' and mechanical test instruments' own software | They produce the analysis results and store them in their own archive; measurement quality is rarely the problem. The problem is that linking results to the batch and turning them into a certificate is done by hand. The most critical link in the chain sits exactly here: even if the laboratory measures correctly, a copying error voids all that accuracy. |
| Quality certificates | Word and Excel templates, standard certificate formats | Certificates are prepared by hand, and different templates per customer and standard sit scattered across individuals' computers. Which document was produced from which data on which date is not recorded. Yet in steel a certificate is not a formality — it is the basis of the sale and of every dispute that follows. |
| Energy and emissions | Meter data, electricity bills, Excel spreadsheets | Energy consumption is known in total but never allocated to products. The per-product emissions data European buyers are asking for cannot be produced from this infrastructure; when the request arrives, the infrastructure has to be built from scratch, and that is not a job to start at that moment. In a plant where energy metering is in place, the emissions side largely reuses the same data. |
Our solution does not compete with your existing systems; it builds the chain between your process automation and your commercial system. The aim is to be able to show where a product came from and which values it carries the moment anyone asks.
Every heat becomes a record; the charge composition, analysis results, the products made from it and the customers they shipped to are linked to that record. The chain can be queried both forwards and backwards.
Scrap and alloy compositions, the target analysis range and cost are weighed together. Alternative charges can be compared; the actual analysis result is fed back into the plan.
Results from spectrometers and test instruments are linked to the heat record. Values outside specification limits raise an alert; manual copying and copying errors disappear.
The quality certificate is generated automatically from laboratory data. Templates per customer and standard are defined in the system; which certificate was produced for which shipment on which date stays on record.
Meter and fuel data is matched with production records; energy and emissions per unit of product become calculable. The data your European buyer asks for comes out of this infrastructure.
Finished stock is tracked by grade, length and heat. Maintenance plans and spare-part tracking for critical equipment run in the same system; unplanned downtime gets shorter.
Not every company needs all of them. After discovery we start where it hurts most and grow module by module.
Collecting production, speed and downtime data from the furnace, casting and rolling lines; production records per heat number and downtime cause classification.
Detailed page → ERPCharge alternatives based on scrap and alloy compositions, target analysis range and cost comparison; feeding the actual result back into the plan.
Detailed page → LIMSLinking spectrometer and mechanical test results to the heat record, specification limit checks and deviation alerts.
Detailed page → QMSCertificate templates per standard and customer; generating the document from laboratory data and keeping a record of versions and dispatches.
Detailed page → QRLabelling by bundle, pack and batch; tracing a shipped product back to the heat and the line it came from.
Detailed page → BICollecting meter and fuel data, calculating energy per unit of product and producing the emissions data requested on exports to Europe.
Detailed page → CMMSMaintenance plans for critical equipment, breakdown and downtime records, spare-part stock and predictive alerts.
Detailed page → WMSTracking finished stock broken down by grade, length, diameter and heat; instantly finding existing stock that matches a customer request.
Detailed page → APIStock, order and invoice matching with Logo, Netsis, SAP and CanIAS; a data-reading layer on the PLC and SCADA side.
Detailed page →Your accounting backbone and your process automation systems stay in place. The layer we build makes the link between process data on the floor and the commercial system, and completes the traceability chain.
Our integration approach →We talk through your plant structure, your product range, your current ERP and automation systems and the point that hurts most. We clarify expectations and scope and draw a realistic frame; at this stage understanding comes before selling. No obligation.
We walk the flow on site, from the scrap yard to the furnace, from the laboratory to the rolling mill and dispatch. We map where the traceability chain breaks and which records still live on paper.
We decide which module to build first; heat traceability together with the laboratory and certificate chain usually delivers the highest return. Scope, timeline and deliverables are put in writing.
The system is developed and run in parallel with the current routine on a limited product group. Generated certificates are compared with the hand-prepared ones; every divergence is examined.
The remaining modules are added in turn, and the integrations and the energy side are switched on. Users are trained, and documentation and source code are handed over. Maintenance and support run as a separate agreement.
In steel, a certificate is not a formality — it is a condition of the sale. We build the system around that fact; if one link of the chain stays on paper, the job is not finished.
Your PLC and SCADA side stays in place. We read data from that layer and connect it to the commercial side; we do not touch process control.
Everything we build, source code included, belongs to you. We do not leave behind a structure designed to keep you dependent on a supplier.
In this industry the heart of the job is the data model; if the relationship between heat, batch, product and certificate is not built correctly, no screen built on top of it will work. We build the model up front, and in writing.
We do not change everything at once. We start where it hurts most and expand as the gains show; progressing without stopping production is essential.
Documentation and a handover package are part of the job. If another team takes over tomorrow, we deliver in a state they can take over.
Those systems are strong, and if one covers your needs it is the right choice; we will tell you so openly. Custom software makes sense when their licensing and adaptation costs are too heavy for your business, or when most of the scope would go unused. In mid-sized rolling mills the need is most often not a full-scope system but the traceability and certificate chain.
Your quality department remains responsible for the certificate's content and signature; that does not change. What the system does is carry the values from the laboratory record without error, fill the template correctly and store which document was produced from which data. It eliminates manual copying errors; it does not take over responsibility.
Most spectrometers and test instruments offer some export route; the instrument model and software version are examined during discovery. On instruments that cannot export, structured entry is set up on a laboratory screen — still a clear improvement over handwritten paper. What can be captured from which instrument is put in writing at the start of the project.
The demand is growing, and its foundation is largely energy and production data. Under the carbon border adjustment mechanism, the legal obligation sits with the importer in Europe; you are the data supplier. But when you cannot provide the data, default values kick in, and those are usually worse than your real performance. We cover this topic in detail on a separate page.
The system calculates alternatives and puts cost and the target analysis range side by side; your furnace supervisor makes the decision. We do not aim to switch off experience. As actual analysis results feed back over time the suggestions get sharper, but the last word always belongs to the floor.
No. We work read-only; we do not write to process control. The data-reading method is agreed together with your automation supplier, and any intervention that could affect your warranty cover is avoided. We put that boundary in the contract as well.
The timeline depends on the scope and is given in writing after discovery. Our approach is not to deliver one big system in one go, but to build the traceability chain quickly and grow from there. That way feedback comes early, and the return on the investment shows early too.
A working system, its source code, the database and handover documentation. User training and initial support are part of the scope. Maintenance and further development then run under a separate agreement; you are not obliged to sign it — you can also maintain the system with your own team.
Let us examine your traceability chain on site, from the scrap yard to the furnace and from the laboratory to dispatch, and decide together where to start.