shakeout — long after
the only minute that mattered.
position
What you'll see runs on synthetic data calibrated to IS 210 FG260 grey iron — the models, SHAP explanations, and rupee math are production-grade ML. Point the same architecture at your heats and the same screen reads your plant — your operators at the ladle, your engineers at shakeout, your metallurgist on the morning round, your plant head at month-end.
MES dashboards tell you what scrapped yesterday. We tell you what's about to scrap this heat — an XGBoost classifier across 10 defect classes in under 100 ms, while pour temp, delay, and sand moisture are still adjustable.
Conservative foundry buyers don't trust black boxes — rightly. Every prediction ships with its top six SHAP drivers in the operator's vocabulary: "pour delay 6.5 min: +1.77", "humidity 78%: +1.25". The argument and the answer on the same page.
A "76% defect risk" persuades no one in a CFO review. ₹20,248 of expected loss per casting — split into scrap, rework, delay, OEM complaint, and warranty reserve, each formula traceable to a calibrated cost table — is a P&L line the plant head can defend.
Off-the-shelf models trained on academic datasets assume a steady-state plant that doesn't exist in India. FoundryOps Copilot retrains on your heat logs — your operators, your furnaces, your patterns, your monsoon. Seasonal effects, pattern wear past 800 cycles, furnace drift — learned, not assumed.
Heat logs, chemistry, dispositions, OEM complaints, and warranty events — encoded into a model that answers in the operator's, metallurgist's, and plant head's vocabulary. Ask in English; get charts, SHAP attributions, and the underlying heats back. It works two ways: