The engineering problemManage engineering work and CAD queues.
Fry Reglet's quoting, product configuration, engineering, CAD, BOM, document, and order workflows crossed spreadsheets, desktop tools, Autodesk applications, enterprise data, and production handoffs that needed consistent rules and governed state.
Component responsibilityWhat this part of the system owns
Engineering Service within the Fry Tools engineering automation ecosystem.
The portfolio shows an integrated engineering-operations platform rather than isolated scripts: customer and project intake feed quote state, product rules, CAD generation, BOM classification, documents, and production services.
- Primary platform
- .NET desktop + Autodesk automation
- Interface
- Desktop UI
- System relationship
- Fry Tools
- Priority
- Strong
Operating flowHow inputs become controlled outputs
Inputs- Customer, RFQ, project, and order context
- Product dimensions, options, and engineering rules
- Enterprise, Autodesk, document, and file-system state
System behavior- Validate governed quote and project state
- Apply product and engineering configuration rules
- Drive CAD, BOM, document, and production-handoff services
Outputs- Controlled quotes and project records
- Configured models, drawings, BOMs, and production files
- Release, reporting, and manufacturing handoff packages
Engineering decisionsWhy the solution is shaped this way
Separate customer, quote, product, CAD, BOM, and lifecycle responsibilities.
Why: Distinct service boundaries let shared rules evolve without duplicating behavior across each user-facing application.
Tradeoff: The platform requires explicit contracts and coordinated release discipline between components.
Keep deterministic product and engineering rules ahead of generated output.
Why: Models, drawings, BOMs, and documents can be traced to validated configuration state instead of operator memory.
Tradeoff: Exceptions must be modeled deliberately rather than handled through undocumented manual edits.
Connect legacy enterprise context to modern application and Autodesk boundaries.
Why: Engineering users can work from governed customer and order state while modernization proceeds incrementally.
Tradeoff: Adapters and compatibility layers remain necessary until legacy systems are retired.
Implementation architectureHow the solution is structured and verified
Solution shape
- Desktop engineering and operations suite
- Customer, quote, project, lifecycle, and order services
- Product configuration, CAD, BOM, estimating, and production automation
- Enterprise data, identity, Autodesk, file, and document integrations
Framework and package signals
- C# / .NET
- WPF and WinForms
- Autodesk Inventor and Vault APIs
- Layered desktop services
- Shared domain libraries
- Enterprise integration adapters
Executable surfaces
- RFQ and quote workspaces
- Engineering configurators
- CAD and BOM automation
- Production and document handoff services
Verification
- Reconciled public case-study claims and chronology
- Preserved application and solution inventory
- Public demonstrations for column-cover and door-frame workflows
- Explicit separation of applications, libraries, services, tests, and archive records
Role and responsibilityWhat Thomas built
Thomas created the FryTools applications and services represented here as part of his Fry Reglet technical leadership and operations-technology work. Supporting libraries and team context remain distinguished from end-user applications.
Technical compositionTechnologies, logic, and connected outputs
C#VB.NET.NET FrameworkAutodesk Inventor APIAutoCAD .NET APIExcel automation.NET desktop + Autodesk automation
Algorithms and domain rules
- CAD queue views and engineering container UI
Integrations and data
- Autodesk Inventor
- AutoCAD
- Excel
- PDF
- file system
Outputs and runtime
- Desktop UI
- Desktop Service / UI Module
- Windows desktop / internal enterprise
Libraries and architecture
- Service-oriented modular desktop ecosystem
- .NET Framework
- Autodesk Inventor API
- AutoCAD .NET API
- Excel automation
Technical references and sourcingWhat an evaluator can inspect
Confidence: High. This portfolio distinguishes delivered applications, supporting components, tests, libraries, utilities, and repository containers.
The implementation summary was derived from reviewed solution files, project or package manifests, architecture documentation, and test surfaces. Private locators, source code, secrets, and proprietary rules are not published.
- FryTools implementation-story registry (architecture)
- Public experience and authorship graph (architecture)
- Sanitized application inventory (manifest)
- Prior-employment work is presented as professional history, not as a CAD Guardian customer engagement or endorsement.
- Private source locations, customer data, proprietary rules, and raw implementation material are withheld.
Portfolio source review
The public record summarizes application purpose and composition. Private paths, source, customer data, proprietary rules, and restricted artifacts are not published.