Ray (foreman, Lakeview)
IMG_3381.jpg: tickets on the tailgate
LaunchAI converts ductwork sketches and fitting tickets into CAD drawings. Create fitting geometry with sizes, gauge, connectors and liner specifications. The drawing is built from the supplied measurements, notes and specifications. Unclear details are flagged for your team to review.
For shop foremen, fitting-entry operators and detailers at HVAC sheet metal and duct fabrication shops
The foremen dropped them off Friday: carbon-copy fitting tickets, a couple on the back of a delivery slip, one written on a scrap of duct board. A transition sketched as a trapezoid with "24x12 → 16x12" and "FOT" on it. An offset with the dimensions written on the wrong side. A note that just says "1" liner?". Then a text with a photo of the ceiling, a PDF markup from the GC's coordinator, and a voicemail from Lakeview saying the 45 on tag 14 is backwards and they need another one today.
So you sit down at FabShop or CAMduct and type. Pick the fitting from the library. Width, depth, length, offset, which side stays flat. Gauge off your table for the big side. Connectors each end: TDC, S&D, raw. Liner, and whether the sizes on the ticket are clear inside or sheet metal. Job, area and tag number so it ends up on the right truck. Thirty tickets, a couple hundred numbers, and the coil line and the plasma table both waiting on you.
When a ticket gets read wrong, nobody finds out until an installer is on a lift holding a fitting that's two inches small or mirrored. That's a remake, a second delivery, and a foreman who now writes his tickets even faster because he doesn't trust the shop.
What the job looks like today
Which fitting, which side is width, which side is flat, and what the scribble in the corner means.
Fitting from the library, then every size, length and offset, by hand.
Gauge, connectors, seams, liner: from memory and the foreman's habits.
Job, area, tag number, so it ships on the right truck.
The installer calls from the lift when it doesn't fit.
Where it goes wrong
Fitting tickets get written on a lift, in a hurry, by someone who knows exactly what he means. The shop has to guess.
"24x12" is width by depth, and width is the side you're looking at. Unless he was looking at it from underneath. Swap them and the fitting won't meet the duct it's going on.
With 1" liner, a 24x12 clear inside is a 26x14 piece of sheet metal. Some foremen write the clear size, some write the metal. The ticket almost never says which.
FOT on the ticket, FOB in his head, or the other way around once you flip it over on the bench. Mirror a transition or an offset and it's the right size and completely useless.
No connector on the ticket means whatever that foreman usually uses. TDC on one end and S&D on the other changes the blank, the corners, and whether it bolts up to the run.
Why it's still manual
Duct shops already run serious software. The ticket is still paper, and someone still types it in.
Your CAD and quoting software
Waits for someone to type
Trimble FabShop and Autodesk CAMduct have every fitting you'll ever make, parametric and ready to nest. They still need someone to pick the fitting and type the sizes, length, flat side, gauge and connectors off the ticket.
Generic AI and OCR models
Confidently wrong
A chat model reads "24x12 → 16x12" fine and guesses the rest: which side is flat, whether the sizes include liner, what "S/D" means. It turns "26ga" into "26 gal" and never tells you which answers were guesses.
Image-to-CAD converters
Traces lines, not intent
Image-to-CAD tools trace the trapezoid on the ticket. A duct fitting isn't a picture, it's a library item with a handful of parameters, and a traced outline gives you none of them.
Measuring apps and configurators
Only if everyone uses them
Field-entry apps like FabShop Mobile work when every foreman uses them. Half of yours still write on carbon tickets and duct board, and the GC's coordinator sends PDF markups.
How the agent does it
LaunchAI converts the sketch and its measurements into CAD geometry, applies your drawing standards and prepares the related order information. Missing dimensions and unclear notes are flagged for your team to review.
Every size, arrow, flat side and note, with a confidence score on each value.
Gauge table, connectors, seams and liner rules, by job and by foreman.
Opens FabShop or CAMduct and builds it from your fitting library.
Sizes have to meet the duct before and after, and the flat side has to make sense.
Your shop lead confirms the flagged liner basis; it goes to nesting.
Caught at the desk
Today the order bounces when someone hits save. The agent runs the same checks first, fills what it can from a trusted source, and brings you only the one thing that needs a person.
Today
Fitting incomplete · cannot nest or cut
Verify the following
With the agent
Fitting type
Arrow and two sizes read as a rect-to-rect transition, 48" long.
Sizes meet the run
Outlet 16" x 12" matches the duct on the next ticket in the same run.
Liner basis unclear
Ticket says "1" liner?". Entered as clear inside (+2" metal); confirm with Ray before cutting.
Gauge
26 ga matches your gauge table for a 24" side on this job's pressure class.
Flat side
FOT: top kept flat, all the change taken on the bottom.
Connectors and seams
TDC both ends, Pittsburgh seams per your shop defaults.
Human review
The paperwork on one side, the agent's drawing on the other, and every value it read in between, with the one it's unsure of called out.
Approval you asked for
The agent read the field ticket, picked a rect-to-rect transition and entered every size. The liner basis needs confirmation.
Agent suggests: Approve after confirming the 1" liner and that 24x12 and 16x12 are clear inside sizes. Length, flat side, gauge and connectors match the ticket.
Dimensions read from sketch
Inputs and outputs
Your numbers
Change the numbers to match your shop.
Example values. Put in your own.
today with the agent: review only
Your software
LaunchAI converts sketches into drawings through your CAD and design workflow. Bring your software version, drawing standards and a sample sketch so we can confirm the conversion steps and outputs for your setup.
FAQ
No import and no integration. LaunchAI agents use your software through the screen with your team's logins, the same way your fitting-entry person does. It picks from your own fitting library, so your custom fittings and connector names work as they are.
The agent never invents a dimension. It enters what the ticket supports, flags what's missing, and drafts a text to the foreman ("Tag 14: flat on top or bottom?"). The fitting waits; the rest of the tickets keep moving.
Your shop lead. The agent stops at a review screen with each fitting and every flagged value. Nothing gets nested or cut until someone on your team approves it.
That's the point. They keep writing tickets the way they always have, on paper, duct board or a photo, and the agent does the typing at the shop.
All of it. Round and oval fittings, spiral, takeoffs, elbows with throat and heel radii, offsets, square-to-rounds: if it's in your fitting library and on the ticket, the agent can enter it.
Yes. It reads clouded PDF markups and takeoff exports from QuoteSoft, FastDUCT or ESTmep, and flags any fitting where the field ticket and the coordination drawing disagree.
Other industries
Send us a box of last month's fitting tickets.