Business problem
A high-volume airport column-cover program required coordinated model, drawing, metadata, and package output across many configured conditions.

Accepted project and quote data drove Inventor parameters, coordinated model and drawing state, job metadata, PDF/DXF output, package collection, and accountable engineering release for the Salt Lake City Airport column-cover workflow.
Engineering systems implementationFry RegletCAD Technical Manager; Operations Technology SpecialistAug 2017–Sep 2021
A high-volume airport column-cover program required coordinated model, drawing, metadata, and package output across many configured conditions.
CAD Technical Manager; Operations Technology Specialist
Accepted job data drove Inventor parameters, coordinated model and drawing state, metadata, PDF/DXF output, and package collection.
configured part/assembly · submittal · shop pack
Directly documented in a contemporaneous one-year overview; not combined with unreconciled cover or unit aggregates.
Manual recreation across dozens of drawings would have multiplied update effort and increased the chance of package inconsistency.
A high-volume airport column-cover program required coordinated model, drawing, metadata, and package output across many configured conditions.
Accepted configuration data became the starting point for coordinated models, drawings, exports, and release packages.
Accepted job data drove Inventor parameters, coordinated model and drawing state, metadata, PDF/DXF output, and package collection.
The public demo shows an Inventor/iLogic/VB.NET configurator; a contemporaneous overview records 35+ automated column-cover drawings and source matches the Salt Lake City Airport awarded-job path.
Open technical detailThe implementation supported 35+ directly documented automated drawings while keeping engineering release accountable.
The model shows accepted examples, deterministic checks, exceptions, reviewer decisions, and handoff without exposing protected customer artifacts.
Inventor, iLogic, and VB.NET configuration demonstration for the SLC column-cover workflow.
Inventor, iLogic, and VB.NET configuration demonstration for the SLC column-cover workflow.
Start with the current workflow, accepted output, connected systems, operational risk, and the first result worth implementing.
Review authorship, inputs, constraints, rules, outputs, integrations, validation, metrics, and source context in directly linkable technical sections.
The public demo shows an Inventor/iLogic/VB.NET configurator; a contemporaneous overview records 35+ automated column-cover drawings and source matches the Salt Lake City Airport awarded-job path.
Shows an order-driven configurator coordinating model, drawing, document, and machine-readable output with review intact.
The model shows accepted examples, deterministic checks, exceptions, reviewer decisions, and handoff without exposing protected customer artifacts.
Order-to-output evidence matrix — Prior employment at Fry Reglet · public demonstrations. A public-safe reconstruction paired with three public demonstrations; it contains no employer drawings or rules.
The workflow keeps commercial, engineering, and production outputs tied to one governed source decision and one accountable release gate.
Quote-to-CAD/BOM/document/production flow — Prior employment at Fry Reglet · public demonstrations. Derived from source-backed implementation boundaries without employer records or rules.
The reconstructed SLC flow exposes coordinated assembly, drawing, package, validation, revision, and release evidence without publishing employer artifacts.
SLC configurator input-to-release flow — Prior employment at Fry Reglet · public demonstrations. Derived from direct source, the contemporaneous overview, and the public demonstration.
The BOM diagram exposes traversal, classification, exception, reconciliation, and release boundaries while proprietary classification values remain private.
Assembly traversal and BOM classification flow — Prior employment at Fry Reglet · public demonstrations. Derived from the private source census; product-specific rules and records are excluded.
Inventor, iLogic, and VB.NET configuration demonstration for the SLC column-cover workflow.
Inventor, iLogic, and VB.NET configuration demonstration for the SLC column-cover workflow.
35+ automated SLC column-cover drawings — Directly documented in a contemporaneous one-year overview; not combined with unreconciled cover or unit aggregates.
Prior employment at Fry Reglet · public demonstrations. Thomas Smith one-year overview, matched configurator source, and public SLC Airport Column Configurator demonstration.
Prior employment at Fry Reglet · public demonstrations. Private solution-capability ledger cross-checked against source and project inventory; employer rules and code are not published.
Prior employment at Fry Reglet · public demonstrations. Public YouTube demonstrations reviewed July 2026.
Prior employment at Fry Reglet · public demonstrations. A contemporaneous one-year overview and 2021 résumé support the qualified 35+ SLC automated-drawing and 3,000+ role-wide drawing observations.
Publication limit: The role-wide drawing total is not attributed to one configurator, and conflicting SLC cover/unit totals remain unpublished.
Prior employment at Fry Reglet · public demonstrations. A private source census confirms assembly traversal, drawing/PDF/DXF generation, BOM classification, parameter control, Pack-and-Go, and label-layout categories.
Publication limit: No source, product rule, identifier, path, title block, customer record, or employer screenshot is published.
Prior employment at Fry Reglet · public demonstrations. The SLC column configurator, Door Frame generator form, and connected Door Frame CAD/BOM/quote demonstrations remain publicly reviewable.
Publication limit: The videos demonstrate workflow behavior; they do not publish employer source or imply Fry Reglet endorsement.
Prior employment at Fry Reglet · public demonstrations. Salt Lake City International Airport's construction timeline independently documents column-cover assembly and installation within The New SLC program.
Publication limit: The airport source establishes public project context only; Thomas's automation contribution comes from separate direct and contemporaneous records.
Review the official SLC Airport construction timelineStart with the users, current workflow, accepted output, failure mode, connected systems, and the first implementation decision.