Why a fixed furnace setpoint is a decision you made years ago
The furnace runs for a decade. The batch, the cullet ratio and the pull change every week. A setpoint that was right at campaign start is a guess by month six.
Working notes on glass making and autonomy, written as the product is built. Dated posts appear here once there is something shipped to date them against.
Short notes on glass making and autonomy, written as we build. No publication dates yet; these are the pieces in progress and what each one argues.
The furnace runs for a decade. The batch, the cullet ratio and the pull change every week. A setpoint that was right at campaign start is a guess by month six.
Attribution is the whole point of fusing inspection with control. A defect you cannot trace to a process cause is a reject; one you can trace is a setpoint.
Polariscope spot checks tell you about one piece. Birefringence at the lehr exit, on every piece, tells you about the curve.
Furnace campaigns are long and qualifications are unforgiving. The twin is where the expensive mistakes should happen.
Nobody hands a furnace to software on day one. The three pilot stages exist so the plant can check the recommendations before they become writes.
The judgement that keeps a plant on grade is leaving with the people who hold it. Capturing their corrections is how the models learn what the recipes never wrote down.
Every Glasent run is an ordered, inspectable sequence. This is scenario_fl2_01 on FL-2 · float line · clear soda-lime: Thickness change FL-2 · 6 mm to 4 mm clear float, residual stress inside spec, zero escaped seeds. It is a worked scenario that shows the shape of a run, not a measured customer result.
Plant Orchestrator · Pulled the 4 mm clear float spec, optical-grade tolerances and the standing energy window from plant MES; locked the target envelope for the run.
Glastwin · Simulated 36 candidate transition recipes across furnace pull, tin-bath ribbon speed and lehr curve; ranked them on seed risk, residual stress and energy per tonne.
Meltrix · Stepped furnace pull toward the new ribbon mass flow while holding melt temperature and fining; chemistry stayed inside the composition window.
Formeon · Raised ribbon speed and re-angled the top rollers to thin the ribbon toward 4 mm; thickness converged inside the design tolerance.
Anneon · Re-shaped the lehr cooling curve for the thinner, faster ribbon so residual stress stays inside spec at the higher speed.
Seedscan · 8 camera, optical and stress stations streaming; a seed cluster flagged at the ribbon edge and attributed to the pull transient, routed to cullet.
Plant Orchestrator · Re-sequenced cut sizes so transition ribbon routes to cullet recovery and good ribbon to the highest-value open order.
Plant Orchestrator · The second pull step exceeded the site autonomy threshold. Held for the glass technologist on shift; approved and written to the audit log.
Panebot · Re-planned pick and stack paths for the thinner panes; plates flagged by Seedscan diverted to cullet, good plates stacked to rack A3.
Plant Orchestrator · Lot released with full genealogy: batch, melt, forming, lehr curve, defect map, stress map and the technologist's approval.
Every tool invocation, argument and result is written to an immutable, human-readable log, and every reasoning step is expandable. Nothing about a run is hidden from the plant.
Plan, thought, action, observation, exactly as the orchestrator would record it.
Move FL-2 from 6 mm to 4 mm clear float with residual stress inside spec and zero escaped seeds.
Simulate the transition on the twin first. Lead with furnace pull so the ribbon mass flow is right before the forming change, then thin the ribbon, then re-shape the lehr curve. Watch the ribbon continuously; hold the second pull step for a human.
The standing recipe changes pull and ribbon speed together. On the twin that produces a fining transient that seeds the ribbon edge. Sequencing the pull step ahead of the forming change and holding fining removes most of it.
twin.simulate(candidates=36) returned recipe #19: pull in two steps, forming change after fining settles, lehr curve re-shaped before belt speed rises.
Recipe #19 scored lowest on seed risk with stress inside spec. Two candidates scored lower on energy but pushed residual stress over the site limit and were discarded.
Execute recipe #19 under autonomy level L3: eleven setpoint writes permitted, the second pull step routed to the glass technologist.
Seed cluster at the ribbon edge at 02:28:41, attributed to the pull transient. cuOpt routed that ribbon to cullet recovery; no flagged plate reached a customer stack.
Scenario run complete. Thickness at 4.0 mm, residual stress inside spec, one approval gate, full genealogy written to the lot record.
Three longer threads we keep returning to.
One note per product: what it watches, what it moves, what the plant counts, and where the craft it encodes came from.
A pilot stage at a time: what the plant sees, what the technologist approves, and what has to be true before the next level.
How a simulation earns the right to rank recipes: correction against the real line, discards, and replay before promotion.
The ground the notes cover.
Fixed setpoints, fining transients, redox, energy per tonne.
Gob weight, ribbon speed, roller angle, thickness, flatness.
Cooling curves, birefringence, breakage, field escapes.
Attribution, line-speed perception, synthetic rare defects.
Allow-lists, limits, named approvers, replay.
What technologists know that recipes never wrote down.
A plant does not go from manual to unattended in one step. Glasent makes the level explicit, auditable and reversible at any time, and the first release plan is shadow, then assist, then graduated autonomy.
| Level | What the agent does | What the person does | When |
|---|---|---|---|
| L1 · Shadow and advisory | Observes, predicts and recommends setpoints with its reasoning | Enters every change manually; a baseline is measured | Pilot weeks 1 to 3 |
| L2 · Assist | Proposes a write; it executes on approval | Approves each write in the review console | Pilot weeks 4 to 8 |
| L3 · Bounded | Writes inside tag, rate and magnitude limits on low-risk loops | Approves pull steps, grade releases and anything above threshold | Pilot week 9 onward |
| L4 · Unattended | Runs the approved envelope without prompting | Sets the envelope; reviews the shift record | Planned, after graduated autonomy proves out |
No customer quotes yet; we are pre-launch. These are the three buyer personas the product is built for and the pain each one describes, in their own terms.
"The furnace has run for years on the same setpoints. The process never has. We find out a melt drifted when the cullet pile grows."
Plant / operations director · ICP persona
"I can tell you why a check appeared from the lehr curve and the gob weight. I cannot be at every line, and the people who could are retiring."
Glass technologist · ICP persona
"A missed seed is a reject. A missed stress fault is a pane that shatters in the field. I need genealogy on every piece, not a spot check."
Quality / reliability engineer · ICP persona
These are the numbers the architecture is built to hit and the pilot is built to measure. None is a customer result yet; every pilot report reproduces its figures from the plant's own ware genealogy.
Glasent writes to production equipment. Every capability is scoped, every write is policy-checked, and every action is written to an append-only audit log the plant owns.
| Standard | Scope | Status |
|---|---|---|
| SOC 2 Type I | Cloud control plane | RUNNING Planned in the first six months |
| SOC 2 Type II | Cloud control plane | QUEUED Planned in months six to twelve |
| IEC 62443 | Plant-edge OT security | RUNNING Design-aligned |
| ISO 9001 / IATF 16949 | Quality and genealogy records | SUCCEEDED Record formats supported |
| Container and safety-glass standards | Stress and defect conformance records | SUCCEEDED Record formats supported |
Glasent reads and writes through the furnace, forming, lehr, inspection and MES systems already on the floor. No rip-and-replace, no parallel historian, no new HMI to learn.
Furnace SCADA and PLC, batch-plant weighing, redox and fining instruments
Setpoint reads and guarded writes over OPC UA and Modbus
Float-bath and IS-machine controls, gob-weight and timing systems
Gob, pull, ribbon speed and roller reads; guarded writes
Lehr zone controllers and belt drives
Zone temperature and curve reads; guarded writes
Camera, optical, thermal, polariscope and birefringence stations
Frames, stress maps, defect records, line-speed streams
Orders, grades, lots and ware genealogy
Spec and tolerance reads; genealogy and release writes
Time-series stores and lab information systems
Backfill, replay and lab chemistry
Robot cells, conveyors and stackers via NVIDIA Isaac
Pick, path and stack commands inside the safety envelope
SSO and RBAC via SAML or OIDC; NVIDIA Jetson Orin edge nodes
Named approvers, tag-level roles, sub-100 ms inference
The questions plant directors and glass technologists ask in the first meeting.
Yes, but only within an explicit tag allow-list with per-tag rate and magnitude limits, and only at the autonomy level your site has set. Every pilot starts in shadow mode, where Glasent predicts and recommends and a person enters everything. Writes come later, after the recommendations have earned it.
Control returns to your existing furnace, forming and lehr systems at their last known-good state. Glasent is a supervisory layer on top of the control system you already run, never a replacement for it, so an outage degrades the plant to its current way of running, not to a stop.
Shadow mode starts on the first day from existing SCADA, forming, lehr and inspection data. Defect and stress prediction improve as site history and labelled outcomes accumulate; the pilot plan sets a baseline period before any recommendation is scored.
Only if you choose cloud training. Compositions, forming recipes and defect libraries are tenant-isolated and never used to train another customer's models. On-prem training and an air-gapped plant edge are available for IP-sensitive producers.
You are, the same as with any control strategy, which is why every write is policy-checked, bounded, logged and reversible, and why anything above your risk threshold waits for a named approver. The audit log records the request, the reasoning, the limits applied and the human decision.
A 90 to 120 day line pilot in three stages: shadow mode to measure the baseline, assist mode where a technologist approves each recommendation, then bounded write-back on low-risk forming, annealing or inspection loops if the plant is satisfied with the results.
↑↓ navigate↵ openesc close