When an order is accepted for an issued offer, the bid costs must be recalculated to the planned<\/strong> ones, if possible automatically. If the costs for the period between the request and the order were to increase dramatically, we could accept a loss-making order. This cannot be allowed.<\/strong><\/p>\n Once the order is released into production, a third set<\/strong> of data on real costs<\/strong> is loaded, based on actual times, actual hours worked, actual cost prices, and actual furnaces allocated. This is every heat treater dream. Once the order is closed, usually by printing a delivery note, we can see if it was profitable or not. And if we use Power BI,<\/strong> it can present this visualization for everyone on a central plant screen in the hall.<\/p>\n But the heat atreatment plant itself cannot handle this. For metallurgists, IT<\/strong> is a very distant activity. But there are expert companies that can do it, such as AIMTEC, ADASTRA, MELZER, depending on the ERP system (SAP, Navision, QI<\/strong> … ) that is used.<\/p>\n And the price? For this entry into the world of AI<\/strong>, at least 50 to 150 k\u20ac. And that is just the beginning. But you have to start somewhere, and this area in particular does not require any significant technical changes, only setting up the correct communication between individual databases and systems. It therefore plays an important role in understanding the benefits of AI<\/strong> and in communicating with it.<\/p>\n So does it make sense? It will probably be individual, plant by plant. Our model in Bodycote Liberec (plant with only vacuum furnaces for heat treatment, mainly of tool steels) was built on general technological procedures and a general price list. In that case, up to 40% of orders are accepted without a tender, without an RFQ. Another 30% of orders are long-term contracts, with fixed terms and conditions, negotiated for 1 year or more. The remaining 30% are contracts where a tender is required. Therefore, only 30% of turnover can be expected to be supported by AI<\/strong>.<\/p>\n But there are heat treatment plants where offers are made for 100% of orders. These differences must be taken into account. However, if we take this phase as a learning stage, we can accept that it is an inevitable step for the future. The benefits will be minimal at first, and the investment in AI<\/strong> will seem to us to be not very effective. But with increasing data, things will improve, and once we start connecting furnaces via OPC UA<\/strong>, we will know what to expect. And the more data we have, the more beneficial this investment will seem to us. And this is all the more so the less qualified personnel we have.<\/p>\n The worst option is that we start, and after the first failures or negative reactions we stop again. In essence, we will scrap the entire investment in AI<\/strong>. Here, the heat treatment shop needs a visionary at the helm, a person who will tirelessly pursue his goal. Without his support, this cannot work out well, because in the short term it will bring minimal results<\/strong>. And in the long term? The worst is the so-called management burnout<\/strong>. His expectations are usually greater than the speed of implementation.<\/p>\n ======================================================================================================= AI<\/strong>:\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0A<\/strong>rtificial\u00a0I<\/strong>ntelligence![\"\"](\"https:\/\/intelligent-kalam.80-240-27-133.plesk.page\/wp-content\/uploads\/2026\/08\/img-0388-kopie-scaled.jpg\")
<\/a><\/p>\n<\/a><\/p>\n
\nAbbreviations used:<\/em><\/span><\/span><\/strong><\/p>\n
\n<\/em>API:\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/strong>Application Programming\u00a0I<\/strong>nterface: definovan\u00e9 rozhran\u00ed a soubor pravidel, podle kter\u00fdch si dva syst\u00e9my p\u0159ed\u00e1vaj\u00ed data a p\u0159\u00edkazy. Webov\u00e9 API m\u016f\u017ee b\u00fdt dostupn\u00e9 prost\u0159ednictv\u00edm jedn\u00e9 nebo v\u00edce URL adres, ozna\u010dovan\u00fdch jako endpoints.
\n<\/strong><\/em>JSON: \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/strong>JavaScript\u00a0O<\/strong>bject\u00a0N<\/strong>otation: textov\u00fd form\u00e1t pro strukturovan\u00fd p\u0159enos dat. Vznikl v prost\u0159ed\u00ed JavaScriptu, ale dnes je nez\u00e1visl\u00fd na programovac\u00edm jazyce.
\n<\/em>Middleware: \u00a0\u00a0<\/strong>integra\u010dn\u00ed vrstva, kter\u00e1 propojuje syst\u00e9my, transformuje data, \u0159\u00edd\u00ed komunikaci, zabezpe\u010den\u00ed a auditn\u00ed z\u00e1znamy.
\n<\/em>AI model: \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/strong>matematick\u00fd nebo statistick\u00fd model, kter\u00fd prov\u00e1d\u00ed klasifikaci, predikci, detekci odchylek nebo doporu\u010den\u00ed.
\n<\/em>OPC UA<\/strong>: \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 Open Platform Communications nebo OPC Unified Architecture
\n<\/em>AI vrstva: \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/strong>\u0159e\u0161en\u00ed sestaven\u00e9 ze standardn\u00edch platforem, konektor\u016f, pravidel a individu\u00e1ln\u011b nakonfigurovan\u00fdch nebo vyvinut\u00fdch model\u016f.
\n<\/em>Document AI:\u00a0<\/strong>Technologie vyu\u017e\u00edvan\u00e1 k\u00a0extrakci vyu\u017e\u00edv\u00e1 k\u00a0extrakci informac\u00ed<\/a>\u00a0z ti\u0161t\u011bn\u00fdch i\u00a0digit\u00e1ln\u00edch dokument\u016f<\/a>, jako jsou obr\u00e1zky, texty, znaky
\n<\/em>DMS:\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 D<\/strong>ocument\u00a0M<\/strong>anagement\u00a0S<\/strong>ystem
\n<\/em>FQ<\/strong>: \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0R<\/strong>equest\u00a0F<\/strong>or\u00a0Q<\/strong>uotation
\n<\/em>APQP:<\/strong>\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0A<\/strong>dvanced\u00a0P<\/strong>roduct\u00a0Q<\/strong>uality\u00a0P<\/strong>lanning
\n<\/em>PPAP:<\/strong>\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0P<\/strong>roduction\u00a0P<\/strong>art\u00a0A<\/strong>pproval\u00a0P<\/strong>rocess
\n<\/em>ERP:<\/strong>\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0E<\/strong>nterprise\u00a0R<\/strong>esource\u00a0P<\/strong>lanning
\n<\/em>OTIF:\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 On Time In Full (%)\u00a0 – <\/strong>percentage of orders delivered within the required deadline
\n<\/em><\/span>TAT:\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0<\/strong><\/em>Turn Around Time (hrs) –\u00a0<\/strong> the time between order recording and packing slip printing\u00a0<\/em><\/span><\/p>\n