Founder and Technical Lead

I learned the workflow, then built the systems around it.

I am Thomas Smith. My path runs from product-development CAD and manufacturing drawing packages to quote systems, configurators, BOM and document automation, production software, and CAD Guardian.

Discuss an engineering system Explore implementation stories

Career arc: 2012–present
Drawing delivery: 3,000+ drawings
Application delivery: 14 desktop applications
Current role: CAD Guardian founder

Implementation diagramThomas Smith career evidence timeline

The twelve-year timeline links each role to a source-bounded case file while keeping proposals, team contributions, prior employment, current proof, and confidential work visibly distinct.

Implementation diagramThomas Smith career evidence timeline

The twelve-year timeline links each role to a source-bounded case file while keeping proposals, team contributions, prior employment, current proof, and confidential work visibly distinct.

How the timeline is supported

The canonical career timeline links each published role to source-bounded employer case files while keeping prior employment, proposals, team delivery, current proof, and confidential work distinct.

Derived chronology only; the timeline contains no employer logo, customer artifact, private locator, endorsement, or active-client identity.

2012–2014

Essential Dental / Sapian R&D

CAD Technician / Technologist · website, IT, and project support · 2012–2014

I began in small-team R&D and CAD work, supporting prototypes, manufacturer handoffs, technical records, websites, and day-to-day IT around regulated dental-product work.

Supported product-development CAD and prototype communication.
Maintained CAD, website, backup, and small-business technology workflows.
Learned early that design output, vendor communication, and protected information have to be managed together.

Selected implementations

Patented endodontic instruments and small-team dental-product R&D

Prototype CAD and manufacturer handoff in a regulated product setting

Early CAD, prototype communication, technical records, website/data, backup, and small-business IT work established the connection between product geometry and the systems protecting its handoff.

Problem

A small product team needed prototype and manufacturer communication without separating CAD from protected records and operating support.

Algorithms and rules

CAD/revision organization
manufacturer handoff checklist
backup and technical-record workflow

Outputs

prototype CAD support
manufacturer handoff documentation
maintained website/data and backup workflows

Stakeholder roles

Thomas Smith
technical reviewer
downstream operator

Validation

Résumé chronology and public-safe role descriptions.
Essential Dental Systems' official site establishes the endodontic product-development and manufacturing setting.

Buyer relevance

Shows the origin of Thomas's document-control and protected-information discipline.

Role and sourcing detail

ContributorContributedRésumé-derived · pending corroboration

Role and workflow wording is published as a qualified résumé-derived account; delivery detail remains pending corroboration.

Portfolio Derived · Approved Public Summary

Résumé chronology and public-safe role descriptions.

Claim boundary: The record establishes the role and work category; it does not publish clinical, patient, proprietary product, or vendor material.

Direct Record · Approved Public Direct

Essential Dental Systems' official site establishes the endodontic product-development and manufacturing setting.

Review Essential Dental Systems' official product context

Claim boundary: The official company source establishes industry and product context only; it does not prove Thomas's contribution.

Non-endorsement and private boundary

Prior-employment experience is presented as Thomas Smith's work history. The named organization has not sponsored, reviewed, or endorsed this page.

Patient information, clinical records, proprietary instrument drawings, manufacturer records, databases, and protected research remain private.

2012–2013

Nimiety Bio

Product Development / CAD Team Lead · 2012–2013

At Nimiety Bio I supported early instrument development through CAD, material and supplier research, prototype coordination, and small-team technical leadership.

Supported gas-testing instrument concepts through CAD and prototype-development work.
Coordinated material, component, and supplier research for a small product-development team.
The public account remains owner-attested until stronger dated project records are recovered.

Selected implementations

Early-stage gas-testing instrument development

Instrument prototyping and supplier research under an evidence gap

CAD, material/component research, supplier coordination, and small-team leadership are presented as owner-attested experience without a quantified outcome or production-adoption claim.

Problem

An early product concept required geometry, material, component, and supplier decisions to converge into prototype work.

Algorithms and rules

component/material comparison
supplier option screening
prototype iteration planning

Outputs

instrument CAD concepts
component/material research
prototype coordination

Stakeholder roles

Thomas Smith
technical reviewer
downstream operator

Validation

Résumé chronology and Thomas Smith's bounded account of the role.

Buyer relevance

Demonstrates product-development breadth while making the current primary-evidence gap explicit.

Role and sourcing detail

ContributorContributedOwner-attested · pending corroboration

The account is owner-attested and deliberately unquantified; implementation delivery remains pending corroboration.

Additional documentation pending

No independently reviewed primary project artifact has yet been approved for public attribution; wording remains conservative and unquantified.

Owner Attested · Documented Evidence Gap

Résumé chronology and Thomas Smith's bounded account of the role.

Claim boundary: No quantified outcome, production adoption, patent ownership, customer identity, or sole-inventor claim is published without a stronger dated record.

Non-endorsement and private boundary

Prior-employment experience is presented as Thomas Smith's work history. The named organization has not sponsored, reviewed, or endorsed this page.

Instrument geometry, test data, supplier terms, research notes, prototype records, and any regulated or proprietary product detail remain private.

2014–2015

Carson Tool & Mold

CAD Drafter · 2014–2015

I carried that discipline into tool-and-mold drafting, where geometry, revisions, and production interpretation had to survive the handoff from drawing intent to manufacturing.

Produced and interpreted manufacturing CAD documentation in a tool-and-mold setting.
Worked inside revision-sensitive production handoffs.

Selected implementations

Injection and compression mold manufacturing

Tooling drawings, legacy conversion, and manufacturability handoff

Plastic-part approval drawings and legacy CAD interpretation supported CNC/EDM and shop handoff inside revision- and ISO-sensitive manufacturing work.

Problem

Customer and legacy geometry had to become production-usable tooling documentation without losing revision or manufacturability context.

Algorithms and rules

legacy-geometry conversion
drawing/revision comparison
manufacturability and handoff checks

Outputs

approval drawings
converted production geometry
CNC/EDM-facing documentation
ISO-related records

Stakeholder roles

Thomas Smith
technical reviewer
downstream operator

Validation

Résumé-derived chronology and role summary.
Carson Tool & Mold's official capabilities page establishes its mold design, manufacturing, quality-control, and qualification-testing setting.

Buyer relevance

Shows direct experience with the production consequences of CAD interpretation and revision control.

Role and sourcing detail

Drafted To ProductionContributedRésumé-derived · pending corroboration

Role and workflow wording is published as a qualified résumé-derived account; delivery detail remains pending corroboration.

Portfolio Derived · Approved Public Summary

Résumé-derived chronology and role summary.

Claim boundary: The public record stays at role and workflow level and does not establish ownership of any customer geometry or tooling design.

Direct Record · Approved Public Direct

Carson Tool & Mold's official capabilities page establishes its mold design, manufacturing, quality-control, and qualification-testing setting.

Review Carson Tool & Mold's official capabilities

Claim boundary: The official company source establishes industry and process context only; it does not prove Thomas's contribution or ownership of customer tooling.

Non-endorsement and private boundary

Prior-employment experience is presented as Thomas Smith's work history. The named organization has not sponsored, reviewed, or endorsed this page.

Customer tooling, part geometry, mold details, manufacturing methods, identities, and internal files remain private.

Feb 2015–Apr 2016

Interroll

CAD Drafter · Feb 2015–Nov 2015
IT Administrator · Nov 2015–Apr 2016

At Interroll I worked first as a CAD Drafter and then as an IT Administrator, connecting conveyor and material-handling drawing packages with the plant systems, users, vendors, and support work around them.

Worked directly with assembly, fabrication, BOM, DXF, checking, revision, and manufacturing-handoff workflows.
Moved from CAD drafting into plant IT administration, user support, onboarding, vendors, and operational documentation.
A privately reviewed work archive contains 1,217 files, including 1,088 PDFs and 96 DXFs; those are archive counts, not a claim of exclusive authorship.
The mixed-authorship archive includes directly matched Brazil Post carrier and conveyor packages plus an Amazon carrier binder; the Amazon reference is archive-presence-only, and direct contribution is stated only where a title block or role record supports it.

Selected implementations

Conveyor, sorter, carrier, and material-handling equipment

Material-handling packages and the CAD-to-plant-IT bridge

Assembly/fabrication sheets, BOMs, DXFs, checks, revisions, and release binders preceded a move into plant IT, user onboarding, device support, vendors, and operational documentation.

Problem

Engineering output had to survive fabrication and plant operations while authorship, revision, and system support remained visible.

Algorithms and rules

assembly-to-detail decomposition
BOM/parts organization
DXF preparation
check/revision/release sequencing
IT support triage

Outputs

fabrication packages
BOM/parts lists
DXFs
release binders
user/device support and documentation

Stakeholder roles

CAD drafter
senior engineer/checker
fabrication/production
plant user
IT vendor

Validation

Employment chronology and public professional history.
Private portfolio archive reviewed only for file classes and workflow patterns.
Interroll's official company material establishes the conveyor, sorter, and material-handling industry context.

Named downstream project context

Brazil Post carrier and conveyor packages

Direct private folder and binder match plus independent public project context.

Brazil Post was a downstream Interroll project context, not Thomas Smith's customer and not an endorsement.

Amazon carrier-binder archive context

Direct private carrier-binder artifact match, independent official Interroll–Amazon relationship corroboration, and explicit owner clearance.

Amazon was a downstream Interroll project context, not Thomas Smith's customer and not an endorsement.

Buyer relevance

Explains the combined drawing-package and operational-support perspective behind CAD Guardian.

Role and sourcing detail

ContributorDeliveredPrivate sources reviewed · public-safe summary

Private artifacts corroborate the summary but are not themselves published.

Related implementation stories

Direct Record · Approved Public Summary

Employment chronology and public professional history.

Claim boundary: Dates and role transition are publishable as prior-employment history.

Private Source Review · Private Corroboration Only

Private portfolio archive reviewed only for file classes and workflow patterns.

Claim boundary: Archive totals describe preserved material, not exclusive drawing authorship; the cleared Brazil Post and Amazon context does not expose raw drawings, title blocks, part numbers, dimensions, or unapproved customer identities.

Direct Record · Approved Public Direct

Interroll's official company material establishes the conveyor, sorter, and material-handling industry context.

Review Interroll's official material-handling context

Claim boundary: The official company source establishes industry context only; Thomas's work and named-project boundaries come from separate role and artifact evidence.

Non-endorsement and private boundary

Prior-employment experience is presented as Thomas Smith's work history. The named organization has not sponsored, reviewed, or endorsed this page.

Raw drawings, title blocks, unapproved customer identities, part numbers, dimensions, plant security, server details, credentials, and operational procedures remain private.

2016

KinMetal

CAD Drafter / Designer · 2016

At KinMetal I continued shop-facing metal-fabrication CAD work, translating design intent into drawings and technical communication that production could use.

Supported metal-fabrication CAD and production communication.
Worked at the boundary between design intent, drawings, and shop handoff.

Selected implementations

Stainless commercial foodservice and custom sheet-metal fabrication

Custom sheet-metal configuration and distributed production coordination

Configured metal-fabrication work connected drawings and technical clarification across Georgia and New York production operations without publishing unsupported improvement percentages.

Problem

Custom sheet-metal requirements needed to remain consistent across design intent, shop drawings, clarification, and distributed production.

Algorithms and rules

configuration-to-drawing translation
revision/clarification tracking
cross-location handoff checks

Outputs

fabrication drawings
technical clarifications
production-ready handoff

Stakeholder roles

Thomas Smith
technical reviewer
downstream operator

Validation

Résumé-derived chronology and role summary.

Buyer relevance

Shows practical shop-facing coordination across custom configured products.

Role and sourcing detail

Drafted To ProductionContributedRésumé-derived · pending corroboration

Role and workflow wording is published as a qualified résumé-derived account; delivery detail remains pending corroboration.

Portfolio Derived · Approved Public Summary

Résumé-derived chronology and role summary.

Claim boundary: The public record supports role and workflow context, not ownership of proprietary drawings or fabrication methods.

Non-endorsement and private boundary

Prior-employment experience is presented as Thomas Smith's work history. The named organization has not sponsored, reviewed, or endorsed this page.

Proprietary drawings, customer names, part geometry, pricing, shop methods, and internal production detail remain private.

Dec 2016–Apr 2017

Fascinate LLC

Junior CAD Designer · Dec 2016–Apr 2017

At Fascinate I worked on experiential fabrication, including the SeaWorld DeepSee virtual-reality desk and a Carnival Cruise Line Experience Center Exhibit, converting concepts and assemblies into fabrication-ready documentation.

Provided 3D assembly and fabrication drawings for the SeaWorld DeepSee virtual-reality desk.
Converted wall-system design drawings into fabrication drawings for a Carnival Cruise Line Experience Center Exhibit.
Worked across architectural, lighting, experiential, and fabrication documentation.

Selected implementations

Experiential exhibits, architectural fabrication, lighting, and branded environments

Experiential concepts converted into fabrication-ready packages

A dated profile directly attributes SeaWorld DeepSee desk assembly/fabrication drawings and Carnival Cruise Line Experience Center Exhibit wall-system-to-fabrication drawing conversion.

Problem

Designed experiences had to become assemblies and fabrication drawings that a shop could build without treating Thomas as the concept owner.

Algorithms and rules

design-to-assembly decomposition
wall-system drawing conversion
fabrication-detail and package coordination

Outputs

3D assembly drawings
fabrication drawings
wall-system production packages

Stakeholder roles

Thomas Smith
technical reviewer
downstream operator

Validation

Public professional-history PDF and portfolio project descriptions.
SeaWorld's official visitor guidance independently names the DeepSee VR experience.
Carnival Corporation's issued release independently establishes the invitation-only Experience Center at CES.

Named downstream project context

SeaWorld DeepSee virtual-reality desk

A dated contemporaneous profile directly states 3D assembly and fabrication drawing responsibility.

SeaWorld was a downstream Fascinate project context, not Thomas Smith's customer and not an endorsement.

Carnival Cruise Line Experience Center Exhibit

A dated contemporaneous profile directly states wall-system design-drawing conversion into fabrication drawings.

Carnival Cruise Line Experience Center Exhibit was a downstream Fascinate project context, not Thomas Smith's customer and not an endorsement.

Buyer relevance

Shows direct physical-delivery experience behind later CAD and document automation work.

Role and sourcing detail

Drafted To ProductionDeliveredPrivate sources reviewed · public-safe summary

Private artifacts corroborate the summary but are not themselves published.

Related implementation stories

Portfolio Derived · Approved Public Summary

Public professional-history PDF and portfolio project descriptions.

Claim boundary: The language is limited to documented project and drawing responsibilities; it does not imply client endorsement or publish project files.

Direct Record · Approved Public Direct

SeaWorld's official visitor guidance independently names the DeepSee VR experience.

Review SeaWorld's official DeepSee reference

Claim boundary: The official source establishes project context only; the fabrication-drawing contribution comes from separate dated portfolio evidence.

Direct Record · Approved Public Direct

Carnival Corporation's issued release independently establishes the invitation-only Experience Center at CES.

Review Carnival's issued Experience Center release

Claim boundary: The official source establishes event context only; the public event year is omitted because it conflicts with the separate private profile chronology.

Non-endorsement and private boundary

Prior-employment experience is presented as Thomas Smith's work history. The named organization has not sponsored, reviewed, or endorsed this page.

Concept files, assemblies, fabrication drawings, installation detail, proprietary models, and client-owned visuals remain private.

Aug 2017–Sep 2021

Fry Reglet

CAD Technical Manager · Aug 2017–Mar 2019
Operations Technology Specialist · Mar 2019–Sep 2021

At Fry Reglet I progressed from leading CAD delivery to a role created around operations technology. I turned quote and RFQ workbooks, product rules, drawings, BOMs, configurators, reports, and production handoffs into an integrated application portfolio.

Built the FryTools path from Excel workbooks and focused desktop utilities toward an integrated Blazor platform.
Connected identity and role-based access, Dynamics NAV 2017 services, Power BI, configurators, documents, and production workflows.
Delivered door-frame, LED, column-cover, modular-wall, part-number, labeling, folder, reporting, and deployment workflows.
Preserved solution snapshots contain 44, 45, and 46 Visual Studio projects across end-user applications, services, libraries, data access, tests, installers, and support utilities; those project counts are not application counts.
A separate contemporaneous résumé records 14 delivered desktop applications, while the private archive preserves more than 20 application/project directories including versions and support components.

35+automated SLC column-cover drawingsDocumented in the contemporaneous one-year overview; kept distinct from unreconciled cover/unit aggregates.
3,000+drawings deliveredDocumented in contemporaneous résumé material.
14delivered desktop applicationsDocumented in contemporaneous résumé material; not a count of archive directories.

Selected implementations

Architectural metal systems for transportation, stadium, higher-education, healthcare, and corporate projects

FryTools workbook-to-desktop-to-web platform evolution

Quote/RFQ workbooks became 14 documented desktop applications and then an integrated Blazor platform; solution snapshots contain 44–46 projects across applications, services, libraries, data, tests, installer, and support.

Problem

Commercial intake, configuration, CAD, BOM, documents, project services, reporting, and production handoffs were distributed across files and specialized knowledge.

Algorithms and rules

finite RFQ/quote states
record validation
pricing/BOM/labor rollups
C# ETL/reconciliation
version/update and audit controls

Outputs

14 documented desktop applications
integrated Blazor platform
quote and project records
reports and controlled handoffs

Stakeholder roles

CSR
estimator
engineering
project services
production
management
IT support

Validation

Employment correspondence and role description.
Résumés, internal presentations, and status material created during or near the work.
Private work-computer archive reviewed for application names and lifecycle patterns.
Fry Reglet's official company page establishes the architectural-metal, engineered-fabrication, airport, stadium, and production setting.

Named downstream project context

Salt Lake City Airport column-cover program

Direct private configurator-source/job-path match, contemporaneous overview, public demo, and independent public column-cover context.

Salt Lake City Airport was a downstream Fry Reglet project context, not Thomas Smith's customer and not an endorsement.

Buyer relevance

Provides the deepest historical example of software built from the workflow rather than dropped on top of it.

Role and sourcing detail

Technical OwnerLed DeliveryCorroborated public-safe summary

Public wording is limited to the approved evidence and authorship classification.

Configured architectural products and manufacturing packages

Order-driven CAD, BOM, document, DXF, and label generation

Source-backed units cover SLC columns, door frames, LED, modular walls, FMS BOMs, drawing generation, Pack-and-Go, flat-pattern/DXF export, Excel BOM merging, cut/buy/pack lists, and labels.

Problem

Product decisions were repeatedly translated into models, drawings, BOMs, CNC files, documents, and production instructions.

Algorithms and rules

parameter/feature/iProperty control
recursive assembly traversal
BOM extraction/classification
flat-pattern detection
view scale/placement
label/page layout

Outputs

configured CAD
drawings/PDFs
BOMs
DXFs
Pack-and-Go packages
cut/buy/pack lists
labels
sanitized quote-report coverage ledger

Stakeholder roles

Thomas Smith
technical reviewer
downstream operator

Validation

Direct source and public-video validation for configuration and generated-output behavior
2,125 canonical latest-revision quote families from 2,889 parsed report rows
15,886 quoted frame units across 1,759 numeric-frame records
1,081–1,196 normalized organization labels across 2,125 usable records; labels are not Thomas Smith's customers or endorsements
1,840 project labels / 2,122 usable fields and 918 architect labels / 1,388 usable fields
3,557 qualified populated-row line items / 1,627 numeric records, with the source discrepancy retained

Buyer relevance

Demonstrates explicit algorithms and production outputs instead of a generic CAD-automation claim.

Role and sourcing detail

Technical OwnerDeliveredCorroborated public-safe summary

Public wording is limited to the approved evidence and authorship classification.

Related implementation stories

Direct Record · Approved Public Summary

Employment correspondence and role description.

Claim boundary: The role transition and cross-functional tool mandate are directly documented.

Contemporaneous Self Report · Approved Public Summary

Résumés, internal presentations, and status material created during or near the work.

Claim boundary: Counts are published with their source class and qualifier; uptime and unsupported efficiency percentages are omitted.

Private Source Review · Private Corroboration Only

Private work-computer archive reviewed for application names and lifecycle patterns.

Claim boundary: No private source, screenshots, product rules, quote logic, pricing, customer data, or internal paths are public evidence.

Direct Record · Approved Public Direct

Fry Reglet's official company page establishes the architectural-metal, engineered-fabrication, airport, stadium, and production setting.

Review Fry Reglet's official company context

Claim boundary: The official company source establishes industry and product context only; Thomas's systems and metrics are supported separately.

Non-endorsement and private boundary

Prior-employment experience is presented as Thomas Smith's work history. The named organization has not sponsored, reviewed, or endorsed this page.

Product records, quote logic, pricing, customer data, private source, internal screenshots, application packages, and workflow records remain private.

Dec 2021–Jun 2022

Daikin Applied

Lead IT Applications Developer / Senior IT Applications Developer · Dec 2021–Jun 2022

At Daikin Applied I worked in a senior applications-development role around legacy business software, enhancement and support decisions, data/reporting concerns, and controlled release work.

Maintained and enhanced existing business applications rather than claiming ownership of an enterprise-wide replacement.
Worked across application support, data/reporting context, release coordination, and stakeholder communication.
No rollout count, user count, or exclusive platform-ownership claim is published without stronger primary evidence.

Selected implementations

Commercial and industrial HVAC systems

Legacy business-application enhancement and release support

A senior applications-development role is presented conservatively around maintenance, bounded enhancement, data/reporting context, release coordination, and stakeholder communication.

Problem

Existing business applications had to continue operating while enhancements and support decisions were made safely.

Algorithms and rules

legacy behavior mapping
defect/feature triage
release-impact and data/reporting checks

Outputs

bounded enhancements
support decisions
release and stakeholder evidence

Stakeholder roles

Thomas Smith
technical reviewer
downstream operator

Validation

Dated application, role-description, and employment-correspondence records establish the role and period.
Résumé-derived implementation summary; direct source, release, and rollout artifacts remain under review.
Daikin Applied's official product literature documents a selection-and-configuration software environment that produces specifications, performance outputs, and dimensional drawings.

Buyer relevance

Shows enterprise application work without inventing ownership, rollout, or user-count claims.

Role and sourcing detail

Maintained OperatedContributedRésumé-derived · pending corroboration

Role and workflow wording is published as a qualified résumé-derived account; delivery detail remains pending corroboration.

Additional documentation pending

Direct implementation, release, rollout, and user-count artifacts have not yet been approved for public attribution; the case remains a qualified responsibility-level account.

Direct Record · Approved Public Summary

Dated application, role-description, and employment-correspondence records establish the role and period.

Claim boundary: Direct records establish chronology and the senior application/CAD-BIM role context, not delivery ownership or production outcomes.

Owner Attested · Documented Evidence Gap

Résumé-derived implementation summary; direct source, release, and rollout artifacts remain under review.

Claim boundary: Public claims stay at bounded maintenance, enhancement, support, and release-responsibility level; no rollout, user, or primary-owner claim is made.

Direct Record · Approved Public Direct

Daikin Applied's official product literature documents a selection-and-configuration software environment that produces specifications, performance outputs, and dimensional drawings.

Review Daikin Applied's official selection-software context

Claim boundary: The official product source establishes company software context only; it does not identify Thomas's private application or prove his contribution.

Non-endorsement and private boundary

Prior-employment experience is presented as Thomas Smith's work history. The named organization has not sponsored, reviewed, or endorsed this page.

Warehouse structure, source data, reports, credentials, diagrams, and customer-specific integration records remain private.

Sep 2022–Apr 2023

1Path Systems / Atlas Professional Services

Senior Software Architect · Sep 2022–Apr 2023

At 1Path Systems / Atlas Professional Services I worked as a Senior Software Architect around trusted legacy .NET applications, application mapping, feature and hotfix delivery, onboarding, stakeholder communication, and knowledge transfer.

Mapped legacy .NET Framework, WinForms, and WebForms behavior before making modernization recommendations.
Supported bounded feature and hotfix work across APIs, SSO, SQL, and established interface components.
Produced onboarding and knowledge-transfer material without representing confidential customer systems as public proof.

Selected implementations

Managed IT, cybersecurity, and customer business applications

Legacy ERP/application mapping, features, hotfixes, and knowledge transfer

Legacy .NET Framework, WinForms, WebForms, API/SSO, SQL, and established UI behavior were mapped before bounded feature and hotfix work, onboarding, and knowledge transfer.

Problem

Trusted customer application behavior and delivery knowledge were distributed across older frameworks, people, integrations, and release practices.

Algorithms and rules

application/dependency mapping
feature/hotfix impact analysis
release and knowledge-transfer sequencing

Outputs

architecture/application maps
bounded features/hotfixes
onboarding and knowledge-transfer material

Stakeholder roles

Thomas Smith
technical reviewer
downstream operator

Validation

A dated offer letter directly establishes the Senior Software Architect title and September 2022 start chronology.
Résumé-derived application-mapping, feature/hotfix, onboarding, and knowledge-transfer summary.
1Path's official services page establishes its managed-IT and line-of-business application-support setting.

Buyer relevance

Shows modernization judgment grounded in a real legacy application rather than a rewrite-first pattern.

Role and sourcing detail

Materially EnhancedContributedRésumé-derived · pending corroboration

Role and workflow wording is published as a qualified résumé-derived account; delivery detail remains pending corroboration.

Additional documentation pending

Direct customer-application, source, release, and knowledge-transfer artifacts have not yet been approved for public attribution; implementation wording remains résumé-derived and qualified.

Direct Record · Approved Public Summary

A dated offer letter directly establishes the Senior Software Architect title and September 2022 start chronology.

Claim boundary: The offer record establishes employment chronology only; compensation, personal data, contacts, and contract terms remain private.

Owner Attested · Documented Evidence Gap

Résumé-derived application-mapping, feature/hotfix, onboarding, and knowledge-transfer summary.

Claim boundary: Public claims describe bounded architecture responsibilities without naming customer applications or asserting platform ownership, rollout, or exclusive delivery.

Direct Record · Approved Public Direct

1Path's official services page establishes its managed-IT and line-of-business application-support setting.

Review 1Path's official application-support context

Claim boundary: The official company source establishes service context only; it does not prove Thomas's contribution to any customer application.

Non-endorsement and private boundary

Prior-employment experience is presented as Thomas Smith's work history. The named organization has not sponsored, reviewed, or endorsed this page.

Customer application names, source, identity and security designs, licensing detail, credentials, and implementation artifacts remain private.

May–Nov 2023

New Black Wall Street Market

Volunteer Software / Operations Contributor · May–Nov 2023

At New Black Wall Street Market I co-created a multi-vendor portal and operating-model proposal covering vendor onboarding, permissions, commissions, content, and day-to-day ownership; the surviving evidence supports a proposal and prototype story, not a production-launch claim.

Co-created a multi-vendor portal and operating-model proposal for a market supporting minority- and women-owned businesses.
Mapped role-based access, vendor onboarding, commission rules, content operations, and administrator responsibilities.
Presented the operating model to stakeholders; public wording explicitly stops short of claiming deployment or adoption.

Selected implementations

Marketplace supporting minority- and women-owned businesses

Multi-vendor portal and operating-model proposal

A co-created portal and stakeholder presentation modeled vendor onboarding, role-based access, commissions, content operations, and administration, explicitly classified as proposal/prototype rather than deployed software.

Problem

A multi-vendor market needed a coherent account, catalog, commission, onboarding, content, and administrator operating model.

Algorithms and rules

role/permission matrix
vendor onboarding state
commission and content-workflow mapping

Outputs

portal prototype/proposal
operating model
stakeholder presentation
administration boundary

Stakeholder roles

Thomas Smith
technical reviewer
downstream operator

Validation

Dated presentation and surviving proposal artifacts.
The market's official information center documents its merchant-application, directory, and operating context.

Buyer relevance

Shows product and stakeholder communication depth while preserving the difference between proposal and deployment.

Role and sourcing detail

Proposal OnlyProposal OnlyCorroborated public-safe summary

Public wording is limited to the approved evidence and authorship classification.

Direct Record · Approved Public Summary

Dated presentation and surviving proposal artifacts.

Claim boundary: The records support co-created proposal, prototype, and presentation work; they do not establish a production deployment or market-wide adoption.

Direct Record · Approved Public Direct

The market's official information center documents its merchant-application, directory, and operating context.

Review the market's official operating context

Claim boundary: The official market source establishes operating context only; the proposal and prototype remain separately evidenced and are not described as deployed.

Non-endorsement and private boundary

Volunteer experience is presented as Thomas Smith's work history. New Black Wall Street Market has not sponsored, reviewed, or endorsed this page.

Vendor records, identities, financial terms, commission values, credentials, unpublished screens, and internal operational discussions remain private.

Sep 2024–May 2025

Habasit America

CAD Drafter · manufacturing workflow and drawing-system development · Sep 2024–May 2025

At Habasit America I produced special-build modular-belting drawings inside AutoCAD LT and related manufacturing constraints, while building an October 2024 Blazor drawing-number workflow for intake, deterministic code construction, search, title-block data, and print/export.

Worked with AutoCAD LT, SolidWorks, DraftSight, PDFs, DWGs, STEP files, templates, product metadata, and production handoff.
Developed the historical .NET/Blazor drawing-number application beginning with an October 2024 commit, including guided intake, deterministic code construction, query/free search, search-before-create, reverse deciphering, structured-text parsing, and print-packet preparation.
A separate 2026 public-safe reconstruction adds governed validation, compatibility matrices, rule traces, provisional-versus-deterministic BOM previews, and tests; it is not represented as a Habasit deployment.
The associated PDF extractor is documentation-only, the SolidWorks repository contains one VBA rotation macro, and the efficiency dashboard is present-day pilot proof rather than historical deployment evidence.

Selected implementations

Conveyor and power-transmission belting with customized special solutions

Special-build modular-belting drawing production

Historical 2024–2025 work produced special-build manufacturing drawings and packages within AutoCAD LT and adjacent CAD-tool constraints.

Problem

Special-build requests had to become identifiable, findable, reviewable manufacturing drawings and packages inside constrained desktop tooling.

Algorithms and rules

request normalization
product-data interpretation
package completeness checks
title-block/print preparation

Outputs

manufacturing drawings/packages
print/title-block preparation

Stakeholder roles

CAD drafter
CSR/requestor
manufacturing reviewer
production

Validation

Employment records establish the role period.
Private repository and drawing-workflow material reviewed for architecture and capability categories.
Habasit's official product page documents plastic modular-belt families, application constraints, engineering selection, and special-solution context.

Buyer relevance

Shows direct special-build drawing production without implying that all historical outputs were software-generated.

Role and sourcing detail

Drafted To ProductionDeliveredPrivate sources reviewed · public-safe summary

Private artifacts corroborate the summary but are not themselves published.

Special-build drawing intake, discovery, numbering, and packet preparation

Drawing Number Generator workflow

A separately evidenced Blazor application beginning in October 2024 structured drawing-number intake, deterministic construction, search-before-create, deciphering, and packet preparation.

Problem

Drawing-number requests needed a find-before-create boundary and reviewable construction path without publishing employer product rules.

Algorithms and rules

deterministic code construction
search-before-create
query/free search
reverse deciphering
structured-text parsing

Outputs

drawing-number workflow
search/decipher results
print-packet preparation

Stakeholder roles

developer
CSR/requestor
manufacturing reviewer

Validation

Employment records establish the role period.
Private repository and drawing-workflow material reviewed for architecture and capability categories.
Habasit's official product page documents plastic modular-belt families, application constraints, engineering selection, and special-solution context.

Buyer relevance

Separates from-scratch application authorship from the drafted-to-production drawing packages it supported.

Role and sourcing detail

Created From ScratchDeliveredPrivate sources reviewed · public-safe summary

Private artifacts corroborate the summary but are not themselves published.

Related implementation stories

Direct Record · Approved Public Summary

Employment records establish the role period.

Claim boundary: Dates and broad manufacturing CAD responsibilities are public-safe.

Private Source Review · Private Corroboration Only

Private repository and drawing-workflow material reviewed for architecture and capability categories.

Claim boundary: Public evidence is reconstructed and generalized; no source, screenshots, product rules, paths, identifiers, title blocks, drawings, or percentages are published.

Direct Record · Approved Public Direct

Habasit's official product page documents plastic modular-belt families, application constraints, engineering selection, and special-solution context.

Review Habasit's official modular-belt context

Claim boundary: The official company source establishes product and industry context only; Thomas's drawing and software contributions come from separate private records.

Non-endorsement and private boundary

Prior-employment experience is presented as Thomas Smith's work history. The named organization has not sponsored, reviewed, or endorsed this page.

Raw drawings, models, title blocks, product rules, internal paths, identifiers, customer data, source, screenshots, filenames, and unsupported metrics remain private.

Jul–Dec 2025

IBM / American Electric Power via AlgebraIT and Artech

Autodesk Developer / Architect · Software Architect / Platform Modernization · Jul–Dec 2025

On the IBM assignment for American Electric Power through AlgebraIT and Artech I worked in enterprise energy and infrastructure software context across C#/.NET, Autodesk automation, Inventor and BOM workflows, Vault, UAT, packaging, and knowledge capture.

Worked in a team-based Autodesk and .NET modernization context for American Electric Power (AEP).
Contributed to a VBA-to-Inventor conversion playbook connecting engineering automation with BOM, Vault, UAT, packaging, release, and stakeholder evidence.
Current public proof kits demonstrate related capabilities independently; they are not customer implementations.

Selected implementations

American Electric Power enterprise energy and infrastructure software through IBM, AlgebraIT, and Artech

Team-based VBA-to-Inventor modernization playbook

The assignment connected C#/.NET and Autodesk API work with Inventor/BOM/Vault context, UAT, packaging, release readiness, and knowledge capture without presenting strategy documents as delivered production outcomes.

Problem

Legacy VBA/Autodesk workflows needed a team-owned conversion, testing, packaging, and knowledge-transfer path.

Algorithms and rules

legacy behavior inventory
API conversion boundary
BOM/Vault handoff mapping
UAT and packaging gate

Outputs

conversion playbook
Autodesk/.NET implementation contributions
UAT/release evidence
knowledge capture

Stakeholder roles

Autodesk developer
software architect
IBM/AEP team
UAT/release stakeholders

Validation

Contract onboarding and assignment-end records.
Current public Autodesk proof kits maintained independently after the assignment.
American Electric Power's official transmission page establishes the utility-engineering and standards environment.

Buyer relevance

Shows enterprise engineering-software delivery while preserving team authorship and contract-chain context.

Role and sourcing detail

ContributorContributedCorroborated public-safe summary

Public wording is limited to the approved evidence and authorship classification.

Related implementation stories

Review current engineering workflow proofPresent Day Demonstration

Direct Record · Approved Public Summary

Contract onboarding and assignment-end records.

Claim boundary: Public claims establish the assignment period and capability context without exposing utility workflows, tickets, diagrams, or implementation artifacts.

Present Day Demonstration · Approved Public Summary

Current public Autodesk proof kits maintained independently after the assignment.

Claim boundary: Present-day demonstrations support evaluator review but are not represented as IBM, AEP, or Artech deliverables.

Direct Record · Approved Public Direct

American Electric Power's official transmission page establishes the utility-engineering and standards environment.

Review AEP's official transmission-engineering context

Claim boundary: The official AEP source establishes industry context only; it does not prove Thomas's assignment contribution or expose utility workflows.

Non-endorsement and private boundary

Prior contract experience is presented as Thomas Smith's work history. IBM, AEP, and Artech have not sponsored, reviewed, or endorsed this page.

Internal utility workflows, private source, credentials, diagrams, tickets, customer data, and customer-owned implementation artifacts remain private.

2026–present

Confidential infrastructure engineering engagement

AEC Software / CAD Automation Contractor · 2026–present

I am working in a current confidential infrastructure-engineering software engagement. Its client implementation results remain private; a separately maintained public DGN proof kit demonstrates the pre-native evidence and review method without being presented as a client deployment.

The public kit inventories two approved DGN fixtures and records size and SHA-256 receipts for both.
Three of three pre-native package-readiness checks can be evaluated before licensed host execution.
An eight-stage declared workflow includes one explicit reviewer-signoff gate; no completed approval receipt is claimed.
No DGN index, host-parity result, native failure receipt, or confidential-client validation result is claimed from the accessible proof.

2 / 2public DGN fixtures inventoriedSize and SHA-256 receipts only; neither fixture was parsed natively.
3 / 3pre-native readiness checks evaluatedReady for a private sample, not production-ready or native-validated.
8 + 1declared workflow stages and reviewer gateOne review gate is designed; no completed approval receipt is present.

Selected implementations

Current critical-infrastructure engineering software engagement

Anonymized current AEC chronology and public DGN readiness proof

The current engagement is listed only as anonymized chronology. A separately maintained public kit inventories two DGN fixtures, evaluates three pre-native readiness checks, and defines an eight-stage workflow with one reviewer gate before licensed-host execution.

Problem

AEC teams need an evidence boundary that prevents portable package checks from being confused with native-host validation.

Algorithms and rules

fixture size and SHA-256 inventory
three deterministic package-readiness rules
licensed-native-runtime stop gate
declared reviewer-signoff stage

Outputs

two fixture receipts
pre-native readiness report
eight-stage workflow declaration
native evidence-gap register

Stakeholder roles

software/CAD automation contractor
AEC operator
technical reviewer
release owner

Validation

2 of 2 configured public fixtures inventoried
3 of 3 pre-native readiness rules evaluated
0 licensed-runtime, DGN-index, host-parity, or completed-approval receipts claimed

Buyer relevance

Demonstrates a precise pre-native evaluation boundary without presenting the public kit as an active-client deployment.

Role and sourcing detail

Created From ScratchPresent Day ProofCurrent public proof · client results withheld

Only the independent pre-native public-proof behavior is published; the active employer, client, project, source, and implementation results remain confidential.

Related implementation stories

Review current engineering workflow proofPresent Day Demonstration

Direct Record · Private Corroboration Only

Current-role chronology records reviewed; no confidential implementation receipt set is connected to the public projection.

Claim boundary: The current-role chronology may be stated, but no confidential-client implementation result or architecture claim is inferred from it.

Present Day Demonstration · Approved Public Summary

Current public MicroStation/DGN proof material maintained independently.

Claim boundary: Public proof demonstrates only pre-native fixture inventory, readiness rules, and a declared review method; it does not represent the confidential customer's environment or deliverables.

Non-endorsement and private boundary

This anonymized current engagement is presented as Thomas Smith's work history. No client or contracting organization has sponsored, reviewed, or endorsed this page.

Employer and client identity, project names, live models, source, credentials, environment details, test fixtures, defects, tickets, and operational records remain private.

The throughline

I did not arrive at automation from a generic software playbook.

I started inside the drawings, revisions, prototypes, fabrication packages, plant support, quotes, BOMs, document sets, and production handoffs. The repeated friction in that work is what pushed me to build tools, then application portfolios, then complete operational systems.

Product-development CAD and prototype handoff
Industrial drawing packages and plant IT
Experiential and architectural fabrication
Quote, configurator, BOM, drawing, and document automation
Enterprise applications, data, Autodesk, release, and support ownership

2012–2017 · learning the work

R&D, tooling, material handling, metal fabrication, and experiential delivery came first.

Those early roles taught me that a drawing is not just geometry. It carries assumptions about materials, revisions, vendors, fabrication, assembly, support, and the person who has to use it next.

Essential Dental / Sapian R&D · 2012–2014 — CAD Technician / Technologist · website, IT, and project support
Carson Tool & Mold · 2014–2015 — CAD Drafter
Interroll · Feb 2015–Apr 2016 — CAD Drafter · IT Administrator
KinMetal · 2016 — CAD Drafter / Designer
Fascinate LLC · Dec 2016–Apr 2017 — Junior CAD Designer

Review landmark fabrication delivery

Fry Reglet · Aug 2017–Sep 2021

I moved from leading CAD output to building the operational technology around it.

The work reached across 35+ automated SLC drawing outputs, 3,000+ role-wide drawings, and 14 delivered desktop applications. By a documented 2020 rollout point, the application portfolio had reached 18 users and 33 automatic updates.

Excel quote and RFQ workbooks to focused desktop tools
Door-frame, LED, column-cover, and modular-wall configurators
CAD, BOM, labels, reports, folders, and production handoffs
Blazor, identity/RBAC, Dynamics NAV 2017 services, and Power BI

Review FryTools quote and RFQ evolution

How this portfolio is documented

The career story stays specific while protected employer material stays private.

Named prior-employment experience is factual work history, not an endorsement. Direct records, contemporaneous self-report, portfolio descriptions, private-source review, and present-day demonstrations are labeled separately so an evaluator can see what each claim actually rests on.

Raw employer drawings, customer data, internal source, product rules, pricing, title blocks, identifiers, credentials, and private screenshots stay private. Public reconstructions explain the workflow without publishing protected artifacts.

Explore implementation stories

2021–2025 · broader systems ownership

The same workflow thinking expanded into enterprise applications, data, and Autodesk systems.

After Fry, I applied that operating discipline to industrial data and APIs, legacy .NET architecture, manufacturing drawing systems, and enterprise Autodesk modernization. Each role added another part of the same chain: trusted inputs, controlled change, accepted output, release evidence, and accountable handoff.

Daikin Applied · Dec 2021–Jun 2022 — Lead IT Applications Developer / Senior IT Applications Developer
1Path Systems / Atlas Professional Services · Sep 2022–Apr 2023 — Senior Software Architect
Habasit America · Sep 2024–May 2025 — CAD Drafter · manufacturing workflow and drawing-system development
IBM / American Electric Power via AlgebraIT and Artech · Jul–Dec 2025 — Autodesk Developer / Architect · Software Architect / Platform Modernization

Review the manufacturing drawing workflow

Next step

Bring the engineering workflow that needs technical ownership.

Use the first conversation to identify the operating problem, available examples, constraints, and the decision that should come next.

Discuss an engineering system

Aug 2017–Sep 2021

Fry Reglet

CAD Technical Manager · Aug 2017–Mar 2019
Operations Technology Specialist · Mar 2019–Sep 2021

Built the FryTools path from Excel workbooks and focused desktop utilities toward an integrated Blazor platform.
Connected identity and role-based access, Dynamics NAV 2017 services, Power BI, configurators, documents, and production workflows.
Delivered door-frame, LED, column-cover, modular-wall, part-number, labeling, folder, reporting, and deployment workflows.
Preserved solution snapshots contain 44, 45, and 46 Visual Studio projects across end-user applications, services, libraries, data access, tests, installers, and support utilities; those project counts are not application counts.
A separate contemporaneous résumé records 14 delivered desktop applications, while the private archive preserves more than 20 application/project directories including versions and support components.

35+automated SLC column-cover drawingsDocumented in the contemporaneous one-year overview; kept distinct from unreconciled cover/unit aggregates.
3,000+drawings deliveredDocumented in contemporaneous résumé material.
14delivered desktop applicationsDocumented in contemporaneous résumé material; not a count of archive directories.

Selected implementations

Architectural metal systems for transportation, stadium, higher-education, healthcare, and corporate projects

FryTools workbook-to-desktop-to-web platform evolution

Problem

Commercial intake, configuration, CAD, BOM, documents, project services, reporting, and production handoffs were distributed across files and specialized knowledge.

Algorithms and rules

finite RFQ/quote states
record validation
pricing/BOM/labor rollups
C# ETL/reconciliation
version/update and audit controls

Outputs

14 documented desktop applications
integrated Blazor platform
quote and project records
reports and controlled handoffs

Stakeholder roles

CSR
estimator
engineering
project services
production
management
IT support

Validation

Employment correspondence and role description.
Résumés, internal presentations, and status material created during or near the work.
Private work-computer archive reviewed for application names and lifecycle patterns.
Fry Reglet's official company page establishes the architectural-metal, engineered-fabrication, airport, stadium, and production setting.

Named downstream project context

Salt Lake City Airport column-cover program

Direct private configurator-source/job-path match, contemporaneous overview, public demo, and independent public column-cover context.

Salt Lake City Airport was a downstream Fry Reglet project context, not Thomas Smith's customer and not an endorsement.

Buyer relevance

Provides the deepest historical example of software built from the workflow rather than dropped on top of it.

Role and sourcing detail

Technical OwnerLed DeliveryCorroborated public-safe summary

Public wording is limited to the approved evidence and authorship classification.

Configured architectural products and manufacturing packages

Order-driven CAD, BOM, document, DXF, and label generation

Source-backed units cover SLC columns, door frames, LED, modular walls, FMS BOMs, drawing generation, Pack-and-Go, flat-pattern/DXF export, Excel BOM merging, cut/buy/pack lists, and labels.

Problem

Product decisions were repeatedly translated into models, drawings, BOMs, CNC files, documents, and production instructions.

Algorithms and rules

parameter/feature/iProperty control
recursive assembly traversal
BOM extraction/classification
flat-pattern detection
view scale/placement
label/page layout

Outputs

configured CAD
drawings/PDFs
BOMs
DXFs
Pack-and-Go packages
cut/buy/pack lists
labels
sanitized quote-report coverage ledger

Stakeholder roles

Thomas Smith
technical reviewer
downstream operator

Validation

Direct source and public-video validation for configuration and generated-output behavior
2,125 canonical latest-revision quote families from 2,889 parsed report rows
15,886 quoted frame units across 1,759 numeric-frame records
1,081–1,196 normalized organization labels across 2,125 usable records; labels are not Thomas Smith's customers or endorsements
1,840 project labels / 2,122 usable fields and 918 architect labels / 1,388 usable fields
3,557 qualified populated-row line items / 1,627 numeric records, with the source discrepancy retained

Buyer relevance

Demonstrates explicit algorithms and production outputs instead of a generic CAD-automation claim.

Role and sourcing detail

Technical OwnerDeliveredCorroborated public-safe summary

Public wording is limited to the approved evidence and authorship classification.

Related implementation stories

Direct Record · Approved Public Summary

Employment correspondence and role description.

Claim boundary: The role transition and cross-functional tool mandate are directly documented.

Contemporaneous Self Report · Approved Public Summary

Résumés, internal presentations, and status material created during or near the work.

Claim boundary: Counts are published with their source class and qualifier; uptime and unsupported efficiency percentages are omitted.

Private Source Review · Private Corroboration Only

Private work-computer archive reviewed for application names and lifecycle patterns.

Claim boundary: No private source, screenshots, product rules, quote logic, pricing, customer data, or internal paths are public evidence.

Direct Record · Approved Public Direct

Fry Reglet's official company page establishes the architectural-metal, engineered-fabrication, airport, stadium, and production setting.

Review Fry Reglet's official company context

Claim boundary: The official company source establishes industry and product context only; Thomas's systems and metrics are supported separately.

Non-endorsement and private boundary

Prior-employment experience is presented as Thomas Smith's work history. The named organization has not sponsored, reviewed, or endorsed this page.

Product records, quote logic, pricing, customer data, private source, internal screenshots, application packages, and workflow records remain private.