Scope a line pilot
One line, one KPI, 90 to 120 days. Starts with a data review on your extract.
Contact
Start with the line that is costing you the most.
A founder reads every message. Tell us the line, the problem and the number you want moved.
Contact
Tell us about your line
The more specific the line and the problem, the more useful the first call is. Every field is optional except the ones marked required.
Direct contact
- Everything, for now
- hello@glasent.com
One mailbox on the glasent.com business domain, read by a founder. Separate addresses for partners, security review and careers are added when the team is.
What happens next
- 01We read it
A founder reads every message. No routing queue.
- 02A 30-minute call
Your furnace, your forming line, your actual problem.
- 03A data review
A historian or inspection extract tells us in a week whether this is worth doing.
- 04A written proposal
Scope, baseline definition and what we will and will not claim.
Reasons
Why people get in touch
Six good reasons and what each one leads to.
Become a design partner
Join the first cohort of three to five plants with signed data-rights terms.
Request the security pack
Architecture, data flows, audit schema and deployment options for your reviewers.
Talk about partnering
OEMs, MES vendors and integrators; a joint pilot is how it starts.
Request SDK or documentation access
Provisioned with a pilot; ask when you scope the line.
Tell us what you want to own
A role on the careers page, or a loop we have not listed.
Run timeline · scenario
What we would be deploying
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.
scenario_fl2_01
FL-2 · float line · clear soda-lime
scenario
SUCCEEDED
-
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.
First 90 days
What an engagement looks like
The same three stages for every plant, with exit conditions agreed in advance.
- 01Weeks 1 to 3 · Connect and shadow
Connectors for one line, the edge node observing, the baseline measured from your genealogy.
- 02Weeks 4 to 8 · Assist
Recommendations approved or corrected by your technologist; accuracy and ROI scored against the baseline.
- 03Week 9 onward · Bounded
Low-risk loops move to bounded writes inside limits if you are satisfied. Exceptions escalate to a person.
- 04Close · Report
Every figure reproduced from your records, exclusions listed, and a decision: convert, extend or stop.
Enterprise
Standardise autonomy across the group
One policy model, one audit trail, one benchmark across every line in every plant, with the composition and forming models kept private to each site.
- SSO and role-based access down to the tag level
- Group-wide autonomy policy with per-site override and approval chains
- Cross-plant benchmarking on cullet, seeds, energy per tonne and first-pass quality
- VPC, on-prem and air-gapped plant-edge deployment options
- Custom composition, forming and tolerance models per site
- Dedicated deployment engineer and quarterly model review per plant
Pricing
Priced per line, per plant, per group
Land on one workflow with a measurable baseline. Expand by line, module and autonomy level. Outcome components available on yield, cullet, defects and energy.
Melting and forming control, annealing control or inspection AI for one line. For glass makers validating ROI on the wedge.
- One line, one agent module
- Plant-edge inference node included
- Furnace, forming, lehr or inspection connectors
- Run log, audit trail, ware genealogy
- Business-hours support
The whole loop: batch and melt, form and shape, anneal and stress, coat and temper, defect, quality and dimension, yield and takt, robotic handling and the twin.
- Meltrix, Formeon, Anneon, Seedscan, Panebot
- Glastwin twin and grade-change sequencing
- Coat-and-temper, quality, yield and takt scopes
- Orchestrator with site autonomy policy
- 24/7 support, quarterly model review
Multi-site glass groups standardising on Glasent, with custom composition, forming and tolerance models.
- Multi-site plant-edge fleet
- Custom composition, forming and tolerance models
- Group autonomy policy and approval chains
- On-prem and air-gapped options
- SLAs, SSO and a dedicated engineer
Guardrails
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 |
From the plant floor
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
Integrations
It speaks plant, not cloud
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
FAQ
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.
Get started
Or just send the extract
A historian or inspection export and the KPI you care about is enough to start the data review.