CAD Guardian designs and implements the systems behind engineering output—connecting quoting, product configuration, CAD, BOMs, drawings, PDM/PLM, ERP, documents, reporting, and production handoff.
This buyer-safe model makes the inputs, rules, review gates, and handoff visible before an implementation begins.
A representative operating model for keeping commands, rules, exceptions, review, and release evidence visible.
Each story shows the operating pressure, the system that changed the work, Thomas’s role, and the result. Detailed implementation notes remain available for technical review.
Thomas Smith helped move a configurable-product quote workflow from Excel workbooks and separate desktop utilities toward FryTools: an integrated .NET platform connecting intake, configuration, CAD, BOM, documents, ERP services, reporting, and accountable handoffs.
A form-driven minimal-door-frame workflow connected configuration, CAD, BOM, drawing, and quote output. Five private report snapshots were deterministically reconciled to publish aggregate workflow scale without exposing customer, project-row, architect-row, contact, identifier, or pricing data.
The historical 2024–2025 lane covers special-build modular-belting drawings and an October 2024 Blazor drawing-number workflow; a separately labeled 2026 reconstruction demonstrates stronger governed validation without being represented as a Habasit deployment.
We start with the repeated work, the output people must trust, and the decisions that control release. That shows where automation helps—and where it could create new risk.
Drawing, model, BOM, export, and package work depends on manual steps that are difficult to repeat consistently.
CAD, PDM, ERP, quoting, documents, and reporting do not share dependable ownership or workflow state.
Scripts, add-ins, spreadsheets, and desktop utilities carry important operating knowledge but are risky to change.
Strong automation removes re-entry while keeping engineers in control of rules, exceptions, and release.
The work defines the solution: who provides the inputs, which rules govern the result, how exceptions are reviewed, and what the next system needs.
Turn repeated drafting, modeling, data extraction, and release work into a dependable path from input to approved output.
Review solutionConnect intake, configuration, engineering review, costing, documents, status, and commercial handoff.
Review solutionClarify lifecycle state, revision, metadata, approval, release, and document ownership before changes expand.
Review solutionStandardize package contents, naming, metadata, generated documents, exception reporting, and release checks.
Review solutionConnect CAD and engineering applications with data, APIs, PDM, ERP, estimating, reporting, and internal workflow systems.
Review solutionThese models show how work moves, where decisions occur, and what the operating team will own.
A bounded package flow makes accepted inputs, deterministic rules, review gates, and released artifacts inspectable.
The commercial output remains traceable to request quality, engineering decisions, owned assumptions, and approval state.
The model shows accepted examples, deterministic checks, exceptions, reviewer decisions, and handoff without exposing protected customer artifacts.
Each step keeps the scope, accepted output, review responsibility, and support handoff clear from the first decision through release.
Name the users, systems, inputs, accepted outputs, known exceptions, and decision owner before selecting technology.
Set the scope, success criteria, stop conditions, and smallest result worth funding.
Implement a focused slice and compare it with accepted examples, output rules, failure cases, and reviewer expectations.
Leave documentation, acceptance checks, known limitations, release guidance, and a clear next decision.
Every package needs visible checks, clear exceptions, and a responsible human release—not just a successful script run.
The work spans drawing production, application delivery, product configuration, reporting, and quote-to-production systems across demanding manufacturing environments.
Figures are drawn from contemporaneous role materials and retain their original scope; detailed qualifications are available in the related implementation stories.
Platform expertise matters. The real work is connecting the workflow, data, documents, review gates, and downstream owners around the CAD environment.
Buyers get a clear starting point, direct technical leadership, and a delivery path that can move through engineering, IT, operations, and procurement.
Name the platform, repeated work, failure mode, trusted output, and decision the first conversation should make easier.
Do not send proprietary files or credentials in the first message.
