Convert behavior incrementally instead of rewriting the entire toolchain at once.
Why: Operational equivalence and UAT can be established component by component.
Tradeoff: Legacy and modern components coexist during the migration window.
Centralize repeatable Autodesk processing in Vault Job Processor workflows.
IBM / American Electric Power via AlgebraIT and Artech · Jul–Dec 2025 · .NET/C# Autodesk Developer / Architect via AlgebraIT and Artech
Legacy VBA and Autodesk automation needed a controlled path into supported Inventor and Vault delivery without losing operational behavior, packaging discipline, UAT, or knowledge transfer.
Vault Job Processor Modernization created or advanced within the IBM-managed AEP Autodesk modernization program.
The work demonstrates modernization as a governed conversion program: inventory behavior, isolate Autodesk API boundaries, rebuild and package components, validate with users, and preserve operating knowledge.
Why: Operational equivalence and UAT can be established component by component.
Tradeoff: Legacy and modern components coexist during the migration window.
Why: A technically correct API conversion still fails if operators cannot validate, deploy, or support it.
Tradeoff: Delivery work extends beyond source conversion into release and adoption controls.
Thomas worked within the IBM/AEP delivery team through AlgebraIT and Artech, contributing Autodesk API implementation, migration, packaging, UAT support, and knowledge capture.
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.
The public record summarizes application purpose and composition. Private paths, source, customer data, proprietary rules, and restricted artifacts are not published.
These records show adjacent applications, services, libraries, tests, or delivery components.
Give engineering operators visibility and control over queued Vault jobs.
Export bills of material from Inventor/Vault into downstream business formats.
Modernize fragile VBA automation into maintainable C#/.NET components.
Identify and resolve API, reference, and runtime changes during Autodesk upgrades.