General Motors / 05
TAD Workflow Automation
GM's firewall request process depended on lengthy approval cycles, disconnected enterprise systems, and manual operational handoffs that could take up to two months. TAD was designed to centralize the workflow, connect its supporting systems, and create a more automated technical path from request to outcome.
01 / The problem
What needed to change.
GM's firewall request process depended on lengthy approval cycles, disconnected enterprise systems, and manual operational handoffs that could take up to two months. TAD was designed to centralize the workflow, connect its supporting systems, and create a more automated technical path from request to outcome.
02 / My contribution
Where I made a difference.
- Mapped the end-to-end firewall request flow, system handoffs, dependencies, and automation opportunities.
- Researched and supported enterprise API integrations across GM systems.
- Worked with Slack, Confluence, Gleam, and additional enterprise platform Enterprise APIs.
- Contributed JavaScript and integration-focused technical work supporting the connected workflow.
- Helped establish the orchestration groundwork for a faster, more scalable request process.
03 / Product capabilities
What the product supported.
- Centralized request workflow
- Enterprise API integrations
- Cross-system orchestration
- Automated operational handoffs
- Connected knowledge and collaboration tools
- Infrastructure request optimization
04 / Outcome
Why it mattered.
The connected technical workflow helped reduce firewall processing timelines from as long as two months to days while creating a more scalable foundation for enterprise infrastructure requests.