SteelFabSolutions Redefining What's Possible
Built for project managers and coordinators

Typing is not the job worth paying for.

Most of a project manager's or coordinator's day comes down to two things. Entering data, and confirming it is correct. AI can already handle the first one. It reads drawings, pulls job numbers, and populates Tekla, ProjectSight, Trimble Connect, and your production database. That leaves your team focused only on what actually needs a person: confirming the AI got it right.

NO GENERIC AI PITCH. NOT XML OR KSS IMPORT. THE ACTUAL DRAWING. AI TYPES, YOU CONFIRM.
DWG NO. SFS AI 001  ·  REV NONE  ·  SCALE N.T.S.
01
Package In
Detailer ZIP arrives. Any folder structure, any naming convention, any mess at all.
02
Classify & Extract
Assembly, Part, and Erection drawings get sorted automatically by page size and content.
03
Verify Against the Drawing
Job number, drawing number, and revision read straight from the title block. Never from a filename, and never from an XML or KSS import file either.
04
Rename & Organize
Standard naming applied automatically. Bolt lists, IFC, and CNC files sorted and ready to use.
05
Import & Verify
Automated import into Tekla and PowerFab, checked against the source drawings.
The real cost

You already know exactly where the hours disappear.

Every shop bleeds real time on the same tasks. Checking drawing packages against title blocks by hand. Renaming files one at a time. Chasing down whatever revision is actually current. None of it gets cheaper as the workload grows, and most "AI tools" built for this industry come from people who have never opened a title block in their life. We have.

35 min to 2 hrs
spent on manual intake, verification, and renaming for a single drawing package
10 to 25+
packages a midsize fabrication shop handles in a typical month
$10,000s
lost to rework and delays after just one missed revision reaches the floor
01
Receive and unpack the package, then figure out whatever folder structure this detailer decided to use this time.
02
Open every PDF by hand to check the job number, drawing number, and revision visually.
03
Rename every file to match the shop's naming standard, one at a time, entirely by hand.
04
Sort supporting files, including bolt lists, IFC models, and CNC data, into the correct place.
05
Import everything into the production system while checking each assembly against the source drawings.
06
Create and send transmittals out to engineers, general contractors, and erectors.
How it works

The answers are already sitting inside your systems.

Tekla, ProjectSight, Trimble Connect, and your production database. You are already running real systems full of real data. Almost no AI actually knows how to read or work with any of it. We built the connection layer that does. Once an AI can see your systems the same way you do, everything built after that is simple configuration, not a brand new software project every single time.

Your software already has an XML or KSS import built in. Every shop leans on it. That import moves data from a file into your system. It does not check whether that data is actually correct. We skip it entirely. The system reads the real drawing, compares it against whatever those imports would have produced, and catches every discrepancy before anything gets touched.

Tell it what you need. It handles the work.

No dashboard to learn and no training session required. Tell it what you need in plain English, and it runs the pipeline while flagging anything it is 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 B12. Confirm before import?
yes
Imported. Final report generated. 13 of 14 clean, 1 flagged item resolved.

The Golden Rule

Never trust a filename, and never trust an XML or KSS import either. The title block is the legal document of record, which makes it the only thing the system actually trusts.

Filenames & folder names
Email subject lines
Standard XML or KSS import files
Any metadata the detailer provides
Text pulled directly from the title block
A clear confirmation from your team
If the filename says one thing and the title block says another, the title block wins, every single time.

Most drawings are not scanned images. They are text based files already. The AI is not guessing at pixels here. It reads the same text your own software already generated, and we have trained it to interpret that information correctly.

99%
how accurately it extracts data, tuned for each detailer
83%
generic AI with no tuning applied, tested and rejected
Part of the same system

Teach it a detailer once. It remembers.

Every detailer uses a different folder structure, a different title block layout, and a different page size. A single setup session, about 15 to 30 minutes, teaches the system that detailer's exact format. After that, every package from them processes automatically, 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 to 30 min, once
PROCESSING AFTERunlimited, automatic
Built for a production shop floor

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

Every behavior described here exists because something similar went wrong once, by hand, and cost real time to track down.

Halt on mismatch
Verifies before it processes
If the first drawing does not match the job you told it, the package stops and gets quarantined instead of being partially processed.
Deletion protection
Refuses to guess
It errors out and stops rather than deleting anything outside its designated safe zones.
Every package, documented
A report for every run
A detailed report gets generated automatically, showing what processed, what got flagged, and what still needs a human look.
Runs unattended
Headless by default
It watches a drop folder and processes new packages on its own, with nobody triggering it by hand.
How we work

Four steps, no wasted motion.

The same discipline as the Golden Rule above applies to how an engagement runs. Nothing vague, nothing left open, nothing you cannot see working before you commit to more.

01
Discovery call. Thirty minutes, bring a real problem you are dealing with right now. No slide deck and no sales pitch, just figuring out together if there is something worth building.
02
Scope. A fixed, specific deliverable with a real timeline. No ongoing retainer, and no scope that quietly grows once the invoice is signed.
03
Build. Working software tested against your actual data. Not a demo and not a mockup. You see it running before you are ever asked to commit to more.
04
Handoff. You keep permanent rights to your data, your specific setup, and everything the system produces, even if we are never involved again. The underlying engine stays ours to keep improving across every shop we work with, so nothing about your setup or your workflow ever gets held hostage to keep the relationship going.
SteelFabSolutions
Ready to talk about your shop

Bring a real problem. Fifteen minutes is enough time to know if it is worth building.

No pricing deck and no generic AI sales pitch. Tell us what is actually eating your time, and we will tell you honestly whether automation solves it.