SteelFabSolutions
AI integration, built for the shop floor

Systems built by someone who's done the job by hand.

Three years running document control on a structural steel shop floor taught me exactly where the manual work piles up. Now I build the AI and automation that gets rid of it — for shops that don't have time for a software project that doesn't fit how they actually work.

NO GENERIC AI PITCH. NO SOFTWARE TO LEARN FIRST. I'VE DONE YOUR JOB.
01
Package In
Detailer ZIP arrives — any folder structure, any naming convention, any mess.
02
Classify & Extract
Assembly, Part, and Erection drawings sorted automatically by page size and content.
03
Verify Against the Drawing
Job#, Drawing#, and Revision# read straight from the title block — never from a filename.
04
Rename & Organize
Standard naming applied. Bolt lists, IFC, and CNC files sorted and ready.
05
Import & Verify
Automated import to Tekla / PowerFab, checked against the source drawings.
The problem

You already know this part.

Every detailer packages their drawings differently — different folders, different naming, different everything. Somebody still has to open each PDF, check it against the title block, rename it, sort the bolt lists and CNC files, and get it into production. That's real hours every week, and it doesn't get any cheaper as you take on more work.

35min–2hrs
spent per drawing package on manual intake, verification, and renaming
10–25+
packages a mid-size fabrication shop processes in a typical month
$10,000s
in rework and delays from a single missed revision that reaches the floor
01
Receive and extract the package, then navigate whatever folder structure this detailer happened to use this time.
02
Open every PDF individually to verify the job number, drawing number, and revision by eye.
03
Rename every file to the shop's naming standard, by hand, one at a time.
04
Sort supporting files — bolt lists, IFC models, CNC data — into the right place.
05
Import and verify against the production system, checking every assembly against the source drawings.
06
Generate and distribute transmittals to engineers, GCs, and erectors.
How it works

The Golden Rule: never trust a filename.

A ZIP filename can say anything. A folder name can say anything. The drawing itself — the title block — is the legal document of record. So that's the only thing the system trusts.

Never Trusted

ZIP and PDF filenames
Folder names inside the package
Email subject lines
Any metadata the detailer provides

Only Trusted

Text extracted directly from the drawing's title block
Explicit confirmation from your team
Detailers don't always follow delivery standards. If the filename says one thing and the title block says another, the title block wins — every time. — the rule the whole system runs on
99%
extraction accuracy — coordinate-based reading, tuned per detailer
83%
accuracy from general-purpose AI reading the same drawings with no tuning — tested and rejected
The interface

You describe what you need. It does the work.

There's no dashboard to learn and no training session. Tell it what you need in plain English — process this transmittal, check this job's status — and it runs the pipeline and tells you what it found, including anything it's not sure about.

shop floor — document control
Process this transmittal and import the BOM to PowerFab.
Extracted 14 drawings. Classified: 9 Assembly, 3 Part, 2 Erection. All title blocks matched Job 277. One BOM mismatch flagged on B-12 — confirm before import?
yes
Imported. Final report generated. 13 of 14 clean, 1 flagged item resolved.
Getting a new detailer running

Teach it a detailer once. It remembers.

Every detailer uses a different folder structure, a different title block layout, a different page size. A one-time setup — about 15 to 30 minutes — teaches the system that detailer's format. After that, every package from them processes on its own, for as long as you keep using it.

DETAILER[your detailer]
JOB #[job number]
PAGE SIZEARCH_D / TABLOID / LETTER
DRAWING TYPEAssembly / Part / Erection
SETUP TIME~15–30 min, once
PROCESSING AFTERunlimited, automatic
Built for a production shop floor

Built so a bad package can't slip through quietly.

Every behavior below exists because something like it went wrong once, by hand, and cost real time to track down.

Halt on mismatch
Verifies before it processes
If the first drawing doesn't match the job you told it, the package stops and quarantines instead of half-processing.
Deletion protection
Refuses to guess
Errors and quits rather than deleting anything outside its designated safe zones.
Every package, documented
A report for every run
Detailed report generated automatically — what processed, what's flagged, what needs a human look.
Runs unattended
Headless by default
Watches a drop folder and processes new packages without anyone triggering it by hand.
Where this is headed

What's live now, and what's next.

Normalizing packages — classifying, renaming, verifying against the title block — is running today. Next is automating the import into your production system with checks against the source drawings, then automating transmittals after that. Each phase cuts out another manual step.

Ready to see it on your own package

Bring a real package. Watch it process while you wait.

No pricing conversation. No slide deck. Send a package from your own detailer and see exactly what comes out the other end.