Today
Defects found. Causes investigated later.
- Defect data is used mainly for pass/fail and quality disposition.
- Root-cause work starts after a trend is already visible.
- Inspection and furnace or tin-bath data sit in separate systems.
Modern float lines already generate continuous defect data from online inspection. INSUS connects that output with furnace, tin bath and line conditions so quality teams can review likely root causes and early drift signals. The inspection system still detects. People still decide what to investigate.
01
Defect patterns linked to process context.
02
Likely causes ranked for review.
03
No replacement of the inspection system.
The problem
Online inspection can detect and classify bubbles, seeds, distortion and tin-side defects as glass moves. The harder question is what upstream condition changed when the defect rate moved. Quality teams often cross-reference inspection results with furnace, tin bath and line data only after a trend is already visible.
The shift
Quality and process teams stay responsible for investigation and action. What changes is whether defect-rate changes arrive with ranked process context from this line's own history.
Today
With INSUS
How it works
This fits OptiStudio as operational analytics and decision support above existing inspection and process systems. Day one is advisory: no automatic furnace or line setpoint changes.
Connect
Read-only links to online defect type, location, severity and timing with furnace DCS or historian tags, tin bath conditions, line speed and other available process records.
Understand
Analyze how defect-rate changes have related to upstream parameters on this plant, not from a generic defect-to-cause template.
Predict
When a defect pattern changes, rank likely process causes by historical correlation strength for that production line.
Advise
Present ranked causes and, where history supports it, flag process conditions moving toward patterns previously linked to rising defects. Teams investigate and decide.
Verify
Compare flagged causes with actual investigation findings. Confirmed and disproved cases feed the plant-specific model.
Getting started
For float lines that already hold inspection logs and time-aligned furnace or process history. Delivered through OptiStudio as advisory quality analytics. Expert Services can help with discovery and validation against known incidents. No new cameras or sensors are assumed.
Inspection finds defects; diagnosis often waits until trends are already visible. This use case correlates defect and process history so quality teams can review likely causes sooner.
Existing defect-inspection logs and time-aligned furnace and process historian data, including defect type, location, severity, furnace temperatures, tin bath conditions and line speed where available.
No. Inspection still detects and classifies defects. Quality and process teams investigate recommendations and decide what action to take.
No. The pilot analyzes data from existing inspection and process systems rather than adding new inspection hardware.
No. It is advisory decision support with read-only integration. Furnace optimization is a separate use case.
Flagged causes are compared with quality-team investigation findings. Confirmed and disproved cases improve plant-specific confidence over time.
Through OptiStudio as operational quality analytics. Expert Services can support discovery, data alignment and validation against known historical incidents on one line.
Glass · Quality & process analytics
Connect defect-inspection data with furnace and process history so rising defect rates become explainable signals your quality and process teams can investigate.