The BACnet Standard would not be celebrating its 30th Anniversary without the time, expertise, and dedication of volunteers within the BACnet Community! Learn more about BACnet’s volunteers and how you can get involved with the BACnet Community.
BACnet Community Volunteers
How are you involved within the BACnet Community?
- Attendee and contributor to the BACnet standard (SSPC 135)
- Active Contributor and voting member for the BTL-WG
- Champion for BACnet within Schneider Electric
What benefits do you gain from volunteering within the BACnet Community?
I gain several key benefits from volunteering within the BACnet community. I genuinely enjoy the collaboration with industry peers and the opportunity to exchange ideas with people who share the same passion for building automation. Being part of the committee that helps guide the future direction of the BACnet standard is also especially meaningful to me. In addition, I value the role I play in ensuring that products can implement features in ways that meet their customers’ needs while still maintaining interoperability through compliance with the BACnet standard.
What’s one word you’d use to describe the BACnet Community?
Collaboration
What excites you most about BACnet and its place in the future of building automation?
What excites me most about BACnet’s future is the role it plays in advancing sustainability and the environmental impact of commercial buildings. BACnet already has broad industry adoption, and it provides the right framework and tools to help organizations reach their sustainability and efficiency goals. Its open, interoperable approach makes it possible to integrate systems in smart, meaningful ways.
What’s been your most rewarding moment or favorite part of being a BACnet volunteer?
One of my most rewarding moments as a BACnet volunteer was being recognized as the BTL‑WG Volunteer of the Year in 2024 – that was definitely a highlight for me. Beyond that, it’s always rewarding to get a new set of tests for a functional area reviewed and accepted by the group. Writing a set of tests is its own rewarding experience. It requires a deep understanding of the technical content and a clear sense of which requirements really matter for interoperability. There’s something very satisfying about crafting tests with a well‑defined purpose, along with test steps that work smoothly for both automated and manual execution. And because the reviewers in the working group are so thorough and detail‑oriented, getting a set of tests through their review process feels like a real accomplishment.