Engineering Manifesto

CWK/DFW Engineering Department

Who We Are

We are the engineers who transform concepts into built reality. We take architect drawings, client specifications, and raw project data and synthesize them into the precise, actionable information that puts product on the shop floor and installations in the field. We bridge the gap between design intent and physical craft.

What We Believe

I. Precision Is Respect

Every dimension we model, every part we name, every BOM line we enter is a promise to the people downstream — the programmers, the fabricators, the installers, the client. A sloppy model wastes material. An unclear drawing wastes hours. A missed redline wastes trust. We treat precision not as overhead but as the foundation of our professional respect for one another and for the work.

II. Process Is Freedom

We maintain rigorous standards — in our layer structure, our naming conventions, our folder organization, our release procedures — not because we love bureaucracy, but because shared process is what lets a team of individuals operate as a single engine. When everyone knows where the file lives, what the part name means, and which checks to hit before release, we spend less time searching and more time solving.

III. Ownership Over Handoff

An FE doesn’t just “throw it over the wall” to the PE. A PE doesn’t just “dump files” to the shop. Every handoff is a deliberate act of communication — a clean model, a complete shipping component list, a release form with context. We own our deliverables from the moment we receive an assignment to the moment the next person can run with it without asking a single question.

We invest deliberately in the tools that multiply our effort — Grasshopper scripts, Epicor integrations, automated BOM generation, nesting algorithms. But a tool only has value when the whole team can use it. We document what we build. We teach what we learn. The wiki exists because institutional knowledge locked inside one person’s head is a liability, not an asset.

V. The Model Is the Truth

Our Rhino models are not illustrations — they are the single source of truth for geometry, material, and assembly. We maintain closed, manifold polysurfaces. We enforce correct material thicknesses. We tag every part. When the model is right, the drawings, the BOM, and the cut sheets follow. When we cut corners in the model, every downstream artifact inherits the error.

VI. Accountability Is Saying It Out Loud

We clearly state what we’re doing and why. We track our hours against budget. We surface problems early — before they become expensive. We don’t hide behind ambiguity. “Engineering Complete” in Epicor means complete. “BOM Complete” means every part and every material accounted for. Our checkboxes are commitments, not suggestions.

VII. Field Conditions Beat Assumptions

Nominal dimensions get us started. Field dimensions make it real. We gather laser scans, conduct site visits, and document actual conditions because the building doesn’t care what the architect drew. We design for the world as it is, not as it was specified.

VIII. We Finish What We Start

A job isn’t done when the model looks good on screen. It’s done when the shop drawings are approved, the BOM is entered, the release form is submitted, the Teams channel is notified, and the PE can begin work without delay. Engineering is not a creative exercise that ends when we lose interest — it is a relay race, and we don’t drop the baton.

How We Work

We follow the phases. Assignment → Fabrication Engineering → Handoff → Production Engineering → Closeout. Each phase has defined inputs, defined outputs, and defined quality gates. We respect the sequence.
We standardize relentlessly. Same layer names. Same file paths. Same naming conventions. Same templates. Consistency is what makes a team of engineers interchangeable on any project at any time.
We automate the repeatable. The Engineering Toolkit, auto-BOM, nesting scripts, parameterized drawing variables — we build systems that eliminate manual drudgery so our time goes to judgment and problem-solving.
We document everything. If it’s not in the wiki, it doesn’t scale. If it’s not in the model, it doesn’t ship. If it’s not in Epicor, it doesn’t get tracked.
We cross-reference obsessively. No document stands alone. Every workflow links to its standards. Every standard links to its tools. Every tool links back to the workflow that uses it. Context is never more than one click away.

Our Commitment

To each other: we will leave every file, every model, and every handoff in better condition than we found it.

To the shop: we will deliver information that is complete, correct, and unambiguous — so they can build with confidence.

To the company: we will manage our time, track our progress, and surface risks early — so leadership can make informed decisions.

To the craft: we will never stop improving our processes, our tools, and our standards — because the gap between good enough and excellent is where our reputation lives.

This is how we engineer. This is the standard we hold ourselves to. This is CWK/DFW Engineering.