ABOUT
Why BAC Exists
Many organizations have strong engineers and strong vendors—but lack a neutral systems layer that aligns decisions early.
​
As automation environments become more multi-vendor and architecturally complex, the greatest risk is often introduced before execution begins—during requirements interpretation, system boundary definition, and procurement decisions.
​
BAC exists to provide that missing systems layer.
​
We embed alongside engineering teams to bring vendor-neutral architectural clarity, reduce integration risk, and support better decisions before commitments are made.​
​
​
Patrick Bunn
Owner / Consultant
Patrick Bunn has over twenty years of experience in industrial and heavy automation, with a career spanning plant maintenance, system integration, and multi-industry project environments. He has supported automation initiatives across metals, food and beverage, textile, wood, pulp and paper, oil and gas, chemical, pharmaceutical, and nuclear sectors.
​
Throughout his career, Patrick observed a recurring challenge: strong engineering teams and capable vendors operating without a unifying systems layer to align architectural decisions early. That gap—often invisible at the outset—frequently led to integration friction, scope ambiguity, and avoidable risk during execution.
​
After nine years in plant maintenance and twelve years in system integration, Patrick founded Bunn Automation Consulting to address that gap. BAC operates as a vendor-neutral, embedded systems engineering partner—supporting front-end loading, system architecture definition, and cross-vendor alignment before procurement commitments are made.
​
His background includes extensive hands-on experience in PLC and servo programming, HMI and SCADA development, VFD and soft starter configuration, and IT/OT control system network design. That execution-level depth now informs his systems-level perspective—enabling disciplined requirements clarification, interface ownership definition, and integration risk identification across complex, multi-vendor environments.
​
In addition to project work, Patrick has taught AC Theory at a local technical college and delivered instruction in motor controls, PLCs, and industrial networking to co-ops and interns. He has also presented a multi-part technical series on control networking, reflecting a long-standing commitment to engineering rigor and knowledge transfer.
​
Originally from San Diego, California, Patrick now lives in Birmingham, Alabama with his wife Emily and their two sons, Theo and Levi.
Awards:
-
Cisco CCNA 200-302 – The Complete Guide to Getting Certified
-
Rockwell Automation – RAU SI PlantPAx Capability certificate
-
Rockwell Automation – RAU Low Voltage Drives Assessment certificate
-
Rockwell Automation – RAU Visualization Final Exam certificate
-
Rockwell Automation – RAU Control Capability Assessment
-
AVEVA – Citect SCADA 2018 R2 Configuration
-
CISCO – IMINS2 – Managing Industrial Networks for Manufacturing
-
PANDUIT – Industrial Network Design for Physical Infrastructure
-
ALLEN-BRADELY – CCN144 - Kinetix 6500 CIP Programming, Studio 5000 Level 4
-
WONDERWARE – InTouch Classic Stand Alone
-
SIEMENS ENERGY & AUTOMATION, INC. – S7 TIA PLC Programming 1
-
ABB UNIVERSITY – ACS800 Customer Multidrive
-
SHERMCO INDUSTRIES – NFPA 70E Electrical Safety Training Course
Vendor-Neutral by Design
BAC does not manufacture equipment, represent hardware suppliers, or operate as a turnkey integrator.
​
This independence allows us to:
-
Provide objective technical guidance
-
Evaluate architecture options without commercial bias
-
Support OEMs and manufacturers across diverse vendor ecosystems
-
Maintain alignment across competing suppliers
Vendor neutrality is not incidental — it is foundational to our model.
Systems-Level Leadership
Automation challenges rarely originate from individual components.
They emerge at interfaces — where mechanical, controls, software, data, and organizational responsibilities intersect.
​
BAC operates at that intersection.
​
Our focus is not individual technologies, but system architecture:
-
Defining boundaries
-
Clarifying ownership
-
Maintaining traceability from requirements to execution
Preserving architectural integrity across project phases
How We Engage
Because system architecture requires continuity, BAC operates through ongoing collaboration rather than fixed-scope project delivery.
​
We embed as a strategic systems architecture advis—supporting front-end loading, cross-vendor alignment, and decision-making across planning and execution phases.
​
This structure provides senior-level systems guidance without increasing permanent headcount.
​
​BAC’s retainer model embeds our expertise into your team, rather than functioning as a standalone project.