Pre-launch. This page holds the release line from the roadmap, the support policy and the release gates, so the first shipped version lands in a process plants already know.
Glasent has not cut a customer release yet. This is the release line the roadmap commits to, in order, with what each one has to prove before it ships. When releases exist, they will be listed here with the reference run per version.
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.
The policy that will govern releases once they exist. Written now so plants know what they are signing up to.
| Component | Cadence | Supported versions | Rollback |
|---|---|---|---|
| Edge runtime | Monthly | Current and previous | Per node, by version |
| Perception models | Monthly per plant, planned | Current and previous | From the model registry |
| Control agents | With the edge runtime | Current and previous | Per agent, by version |
| Policy schema | On change, versioned | All historical, read-only | Re-sign a prior version |
| SDK and CLI | Monthly | Two minor versions | pip pin |
| Twin models | Quarterly, planned | Current | Previous snapshot |
No release touches production equipment without the same four gates a new agent passes.
Every model and prompt change is evaluated against golden defect, stress and process datasets in CI. Regressions block the release.
The release is replayed against the reference run and recent plant runs. Differences are listed in the release note.
Control changes are replayed on Glastwin. Anything that would have exceeded a stress or seed limit blocks promotion.
The plant's policy owner signs the release for their site. Rollback is one command, per node, by version.
Where the release line goes after the first plants.
Batch and melt, forming, annealing and inspection end to end; multi-site makers; glass-machinery and inspection vendor channel; benchmark data products.
Platform and API ecosystem, adjacent scopes through coating, tempering, finishing and secondary processing, and category leadership.
Grounding, audit, human-in-the-loop and graduated control; every supervised correction trains the system; land narrow, expand relentlessly.
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 |
A float ribbon never stops and an IS machine forms thousands of pieces an hour. Perception has to be local, deterministic and fast, so Glasent runs GPU inference at the plant edge and keeps training, simulation and optimisation on DGX, HGX and OVX.
4 to 24 synchronised camera, optical, thermal and stress stations per line. Sub-100 ms defect alerts on container lines and sub-500 ms fused stress and flatness decisions on flat glass are the design targets.
Defect, stress, time-series drift and process-risk models served across edge and plant servers, with glass-knowledge and reasoning endpoints packaged as NIM services.
Multimodal models fine-tuned on inspection imagery, optical and stress outputs, PLC time series, recipes, gob weight, furnace temperature, pull rate, lehr curves, energy, cullet and final grade. Planned cadence: monthly plant refreshes.
GPU-accelerated furnace CFD, glass-flow and annealing-stress simulation of the as-run line, with 10 to 100 candidate recipes evaluated per grade change.
50,000 to 250,000 rare seed, stone, cord, inclusion, check and stress scenes per glass family, always validated against real inspection distributions before training use.
Pull-rate constraints, energy windows, cullet routing, forming and annealing sequence and line takt, with RAPIDS for high-volume telemetry ETL.
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.
Design partners see release notes first and sign each one for their site.
↑↓ navigate↵ openesc close
