Where the Profit Goes When Your Engineering Data Doesn’t Connect

Here’s a question worth asking at your next project closeout: did drafting come in under budget because the work went well, or because the hard part got pushed downstream to engineering?

 

Justin Mason has been asking that question for years. He’s the engineering manager at WB Powell in California, with 27 years in the industry and a Microvellum user since 2011. In our recent webinar on May 27 with Clay Swayze, Director of Product for CAD/CAM at INNERGY, he put it plainly: shops often come in under on submittal drawings and over on production engineering, then call it a wash. It usually isn’t. When engineering has to reinterpret drawings that were created in a separate system, the extra hours show up in one column or the other. The mistakes show up on the shop floor.

 

The four-application problem

 

Most shops that aren’t running connected engineering data are running something like this: one CAD application for drafting, maybe a modeling tool for custom products, a separate cabinet software where engineering recreates what was already drawn, another application generating CNC machine code, and a spreadsheet for hand cut listing. Clay described working with a Canadian company that was running eight applications to get product out the door.

 

None of those tools is the problem on its own. The problem is that each one holds a different piece of the project data, and none of them talk to each other. Every handoff between systems is a place where information gets reinterpreted, and every reinterpretation is a chance for a mistake.

 

The cost shows up when something changes midstream. A dimension moves. A material swaps. A customer revision lands after release to production. The drafter updates the drawing, but downstream, nothing happens automatically. Someone has to chase the change through every system, confirm the old data is gone, and hope nothing got missed. When it does get missed, you’re paying for rework, wasted material, and production delays on a job you already quoted.

 

One drawing, one database

 

Microvellum takes a different approach. It’s a CAD-based engineering platform built on BricsCAD and compatible with full-version AutoCAD, where the drawing itself becomes the manufacturing data. Every route, drill operation, sawing operation, piece of hardware, and material lives in a single database tied to the parametric model.

 

When a change request comes in, you update the drawing. The 3D model, 2D elevations, sections, annotations, cut lists, reports, and machine code all regenerate from the same data.

 

Justin’s example: a finished break room, installed and done, until the architect decided he wanted a taller coffee maker on the counter. Change order. In Microvellum, that meant pulling the prompts on two products, shortening one, adding a finished end to the other, and generating a new work order from the same data that built the original. No re-listing, no re-programming, no running between departments.

 

Drafters become engineers

 

One of the more interesting consequences of connected data is what it does to roles. At W.B. Powell, drafters and engineers work in the same environment with the same tools, so any drafter can pick up behind any engineer and vice versa. A drafter who knows CAD can learn to place parametric products and generate work orders. A seasoned builder from the shop floor who knows exactly how a die wall should go together can come into the office and produce drawings without years of drafting experience.

 

That matters for hiring, too. Drafters are easier to find than engineers who know how to build. Connected data lets you grow one into the other.

 

What it looks like on the floor

 

Before going fully to Microvellum, Justin’s shop floor got three different packets of reports for the same room, generated by three different systems. Now it’s one stack of paperwork, one set of reports, one package to the CNC.
When the edgebander eats the end of a part, the operator scans the barcode on the label and the G-code for that exact part comes up at the machine. No walking back to the office, no figuring out which cabinet, which side. Scan, re-cut, move on.

 

The more you put in, the more you get out

 

Justin’s advice for existing Microvellum users: put everything in. Grommets, in-wall brackets for nurses stations, even the elaborate metal-and-glass features you don’t manufacture yourself. Once they’re products in the system, they’re machined, reported, ordered, received, and tracked instead of living on a sticky note.

 

For shops evaluating Microvellum, his recommendation is to start with one or two people as keepers of the specification groups, the settings that dictate how your shop builds. Flip the switches once, and everyone works from the same standards.

 

Disconnected workflows don’t fail loudly. They leak: a little extra labor on every job, a little rework on every change, margin you never see leave. If you want to see what connected engineering data looks like in the context of your own operation, request a demo and we’ll walk through it with your products and your process.