The numbers, and how they will be measured.
Glasent has not shipped a customer result yet, and this page says so. What it does have is a measurement method, a report template and a worked scenario, so the first case study will be one a quality team can check.
How we measure, and what we exclude
There are no case studies yet. There is a measurement method, agreed before any pilot, so that when the first report exists it can be trusted.
- Plant-owned baseline. Cullet, defect rate, energy per tonne, breakage or escaped-defect risk from the plant's own genealogy and inspection records, over an agreed window.
- Same instruments before and after. No new sensor is used to score a result that the baseline did not have.
- Named exclusions. Campaign changes, raw-material swaps, unrelated outages and product mix shifts are listed and removed from both sides.
- Reproducible. Every figure in the report can be regenerated from the lot records by the plant's own quality team.
Pilot report template
- Scope
- line · product · agent · autonomy level reached
- KPI
- one, agreed in writing
- Baseline
- window · method · value
- Result
- window · method · value
- Exclusions
- event · reason · effect
- Approvals
- count · time-to-approve · overrides
- Decision
- convert · extend · stop
Scenario: FL-2 thickness change
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.
-
01
ingest.order
SUCCEEDED
0.9 s
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.
-
02
twin.simulate
SUCCEEDED
41 s
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.
-
03
melt.pull
SUCCEEDED
6 m 20 s
Meltrix · Stepped furnace pull toward the new ribbon mass flow while holding melt temperature and fining; chemistry stayed inside the composition window.
-
04
form.ribbon
SUCCEEDED
4 m 05 s
Formeon · Raised ribbon speed and re-angled the top rollers to thin the ribbon toward 4 mm; thickness converged inside the design tolerance.
-
05
anneal.curve
SUCCEEDED
3 m 12 s
Anneon · Re-shaped the lehr cooling curve for the thinner, faster ribbon so residual stress stays inside spec at the higher speed.
-
06
inspect.ribbon
SUCCEEDED
continuous
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.
-
07
yield.balance
SUCCEEDED
2.4 s
Plant Orchestrator · Re-sequenced cut sizes so transition ribbon routes to cullet recovery and good ribbon to the highest-value open order.
-
08
approve.human
APPROVAL
48 s
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.
-
09
handle.stack
SUCCEEDED
1 m 10 s
Panebot · Re-planned pick and stack paths for the thinner panes; plates flagged by Seedscan diverted to cullet, good plates stacked to rack A3.
-
10
ware.qualify
SUCCEEDED
1 m 02 s
Plant Orchestrator · Lot released with full genealogy: batch, melt, forming, lehr curve, defect map, stress map and the technologist's approval.
The tool calls behind the scenario
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.
- 02:14:03mes.read_orders({ line: "FL-2", next: "CLR-4MM" })
- 02:14:03ok spec locked · 4.0 mm · optical grade · stress limit set
- 02:14:04twin.simulate({ candidates: 36, horizon: "22 min" })
- 02:14:45ok best recipe #19 · seed risk low · stress inside spec
- 02:14:46policy.evaluate({ recipe: 19, autonomy: "L3" })
- 02:14:46ok 11 writes permitted · 1 write requires human approval
- 02:14:47scada.write_setpoint({ tag: "F1.PULL_SP", step: 1 })
- 02:21:07ok pull step 1 settled · fining stable · chemistry in window
- 02:21:08float.write_ribbon({ speed: "+", rollers: "re-angle" })
- 02:25:13ok thickness converging to 4.0 mm · flatness in tolerance
- 02:25:14lehr.write_curve({ zones: 12, profile: "4mm-fast" })
- 02:28:26ok residual stress inside spec at new belt speed
- 02:28:27vision.stream({ stations: 8, model: "seedscan-v3" })
- 02:28:41seed cluster · ribbon edge · attributed to pull transient
- 02:28:42cuopt.sequence({ objective: "cullet+energy" })
- 02:28:44ok transition ribbon routed to cullet · good ribbon to order
- 02:28:45approval.request({ action: "pull_step_2" })
- 02:29:33ok approved by the technologist on shift · logged
- 02:31:02isaac.plan_path({ stack: "A3", thickness: "4.0 mm" })
- 02:32:12ok paths validated in Isaac Sim · flagged plates diverted
- 02:33:15mes.log_lot({ lot: "FL2-4MM", genealogy: "full" })
- 02:34:17ok scenario run complete · stress in spec · 0 escaped seeds
Reasoning trace
Plan, thought, action, observation, exactly as the orchestrator would record it.
GoalMove FL-2 from 6 mm to 4 mm clear float with residual stress i…
Move FL-2 from 6 mm to 4 mm clear float with residual stress inside spec and zero escaped seeds.
PlanSimulate the transition on the twin first. Lead with furnace p…
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.
ThoughtThe standing recipe changes pull and ribbon speed together. On…
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.
Actiontwin.simulate(candidates=36) returned recipe #19: pull in two …
twin.simulate(candidates=36) returned recipe #19: pull in two steps, forming change after fining settles, lehr curve re-shaped before belt speed rises.
ObservationRecipe #19 scored lowest on seed risk with stress inside spec.…
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.
ActionExecute recipe #19 under autonomy level L3: eleven setpoint wr…
Execute recipe #19 under autonomy level L3: eleven setpoint writes permitted, the second pull step routed to the glass technologist.
ObservationSeed cluster at the ribbon edge at 02:28:41, attributed to the…
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.
OutcomeScenario run complete. Thickness at 4.0 mm, residual stress in…
Scenario run complete. Thickness at 4.0 mm, residual stress inside spec, one approval gate, full genealogy written to the lot record.
What a pilot report will contain
The fields and the measurement behind each one. Nothing here is a result; it is the contract for one.
| Field | Measured from | Method | Exclusions |
|---|---|---|---|
| Cullet | MES and cullet-return records | Tonnes per shift by cause | Campaign and raw-material changes |
| Seeds, stones, checks | Inspection station records | Rate per thousand ware | Station outages |
| Energy per tonne | Furnace meters and pull | MWh per tonne of pull | Furnace repair and idling |
| Residual stress | Birefringence and polariscope | Share of ware inside spec | Product mix shifts |
| First-pass quality | Grade records | Share of ware to first grade | Order spec changes |
| Escaped defects | Customer returns and field reports | Count per period | Transport damage |
The scenario, unpacked
The run on this site is a worked example. Here is what each agent did in it and why that matters to the measurement.
Sequencing beat the standing recipe
The standing recipe changed pull and ribbon speed together. On Glastwin that produced a fining transient that seeded the ribbon edge. Recipe #19 stepped pull first, held fining, then thinned the ribbon. In a real pilot the measurement is seeds per thousand ware across the transition, against the baseline transitions.
Stress held through a speed change
Anneon re-shaped the lehr curve before belt speed rose, and Seedscan attributed the one seed cluster to the pull transient so cuOpt could route that ribbon to cullet recovery. In a real pilot the measurement is the share of ware inside the stress spec and the count of flagged plates that reached a customer stack.
Design targets, stated as targets
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.
The problems we hear
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
Four levels, set per agent and per tag
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 |
An agent that can move a furnace needs a leash
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.
- Bounded action space. Each agent can only write to an explicit tag allow-list, inside per-tag rate and magnitude limits.
- Policy engine before every write. Autonomy level, shift, product, interlock state and operator presence are all evaluated before a setpoint moves.
- Human-in-the-loop gates. Anything above the site threshold, pull steps, grade releases, safety-adjacent moves, waits for a named approver.
- Immutable audit log. Append-only, hash-chained, exportable, and retained on the plant's own storage.
- Hard fallback. Loss of the edge node, the network or the model returns control to the furnace, forming and lehr systems' last known-good state.
- Tenant and IP isolation. Compositions, forming recipes and defect libraries never cross a customer boundary. On-prem deployment available.
Compliance posture
| 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 |
Straight answers
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.
Run the same measurement on your line
Agree the KPI, the baseline window and the exclusions first. Then run the pilot. Then publish the number, whatever it is.