Actility.com

Actility, a Netmore Company Signs Channel Partnership with Czame to Support Smarter, More Efficient Cities Press Release –  February 26, 2026 – Paris, France Accelerating LoRaWAN® adoption across Canada to optimize municipal services, enhance asset visibility, and reduce operational costs. Actility, a Netmore company and a global leader in IoT connectivity solutions, announces a new channel partnership with Czame in Canada, to help municipalities and enterprises improve operational efficiency, reduce costs, and gain real-time visibility over critical assets. Through this partnership, cities will be able to better manage essential services such as waste collection, public lighting, water infrastructure, and public asset monitoring. By enabling real-time data insights, municipalities can move from reactive operations to predictive management — reducing unnecessary interventions, preventing service disruptions, and improving citizen satisfaction. In addition, the collaboration strengthens asset tracking capabilities using Abeeway solutions. Organizations can reduce equipment loss, prevent theft, and minimize operational downtime by knowing the precise location of critical assets at all times. This results in lower replacement costs, improved workforce productivity, and better control over high-value equipment. Shmuel Solomon Global business America Actility, a Netmore Company. “This partnership allows us to deliver practical, high-impact digital solutions that directly address the daily challenges faced by cities and enterprises in Canada” Paul Forostowsky President of Czame “The expertise of Actility’s teams and the products and services from Actility and its subsidiary Abeeway address a strong market need for cities across Quebec and Canada. Czame and its Czame-City division are proud to combine our local IoT and LoRaWAN know-how — already deployed in the Port of Montreal for parking solutions and in the city of Magog for senior safety — with Actility’s technologies. Smart cities are a concrete reality that help municipalities reduce operating costs and mitigate risks, and together we are adapting these solutions to the Canadian market.“ By combining Actility’s ThingPark by Netmore IoT platform and Abeeway tracking expertise with Czame’s local market presence and customer relationships, the partnership aims to accelerate the deployment of scalable, cost-effective IoT solutions that deliver tangible operational value. About Czame Czame is a Canadian IoT solutions provider founded 12 years ago, specializing in connected infrastructures for municipalities, healthcare institutions, and commercial environments. Through its Czame-City division, the company supports cities in deploying innovative IoT solutions that improve safety, operational efficiency, and citizen services. Media contact : https://czame-city.com/ About Actility Actility, one of the co-inventors of LoRaWAN® technology and a founding member of the LoRa Alliance, is the leader in industrial-grade low-power wide-area network (LPWAN) connectivity and IoT tracking solutions. Actility’s ThingPark™ platform, which supports multi-radio connectivity (LoRaWAN®, NB-IoT, LTE-M), powers the majority of public networks and numerous private and enterprise networks worldwide. Through its subsidiary Abeeway, Actility offers patented ultra-low power, multi-radio trackers and comprehensive indoor and outdoor geolocation services. Additionally, the ThingPark Market boast the largest catalog of LoRaWAN® devices, gateways, and solutions available.  Media contact : marketing@actility.com – https://www.actility.com/contact/  Why choose Actility? At Actility, we are passionate about unlocking the full potential of IoT for businesses and communities around the world. Join us as we continue to innovate, collaborate, and lead the way in connecting the digital and physical realms through cutting-edge IoT solutions. Get in touch with our team

Where to Download the Latest BACnet Standard Key Takeaways : How to Download the Latest BACnet Standard The BACnet standard is maintained by ASHRAE and published as Standard 135 The latest BACnet specification is not freely downloadable in most cases Official access is provided through ASHRAE, ISO, ANSI, and links from BACnet.org Some countries allow free read-only access via national standards bodies Paid versions ensure legal, complete, and up-to-date documentation Errata and addenda are essential to correctly implement the BACnet standard Downloading BACnet from unofficial sources is risky and not compliant Using the latest BACnet version is critical for interoperability and cybersecurity Table of Contents Introduction BACnet is one of the most widely adopted communication standards for building automation and control systems worldwide. It enables interoperable communication between devices such as HVAC systems, lighting controls, fire detection systems, access control, and energy management platforms—regardless of manufacturer. If you are new to the topic, you can start with a general overview of BACnet and its role in smart buildings here : What is BACnet. and a more technical explanation of the BACnet ASHRAE Standard 135. As BACnet continues to evolve, new versions of the standard are regularly released to address emerging use cases, cybersecurity requirements, new device profiles, and integration with IP-based and IoT architectures. For system integrators, manufacturers, consultants, and building owners alike, accessing the latest official version of the BACnet standard is critical to ensure compliance, interoperability, and long-term system reliability. However, a common question arises: where can you actually download the latest BACnet standard, and under what conditions? Unlike many open technical specifications, BACnet is governed by formal standards organizations, which means access rules, pricing, and availability can vary depending on the source and region. This article explains where to download the latest BACnet standard, which sources are official, whether the standard is free or paid, and how to make sure you are always working with the most up-to-date and authoritative version. What Is the BACnet Standard? BACnet (Building Automation and Control networks) is an open communication standard designed to enable interoperability between building automation and control systems from different manufacturers. It is widely used in commercial, industrial, and institutional buildings to manage and monitor systems such as HVAC, lighting, fire safety, access control, and energy management. The BACnet standard is developed and maintained by ASHRAE (the American Society of Heating, Refrigerating and Air-Conditioning Engineers) and is officially published as ASHRAE Standard 135. At the international level, BACnet is also recognized as ISO Standard ISO 16484-5, ensuring global alignment and adoption. Unlike proprietary protocols, BACnet defines a common data model, standardized object types, services, and communication mechanisms. This allows devices from different vendors to exchange data seamlessly over various network technologies, including Ethernet, IP, MS/TP, and more recently, secure IP-based infrastructures. The BACnet standard is not static. It evolves continuously through: New revisions of the core standard Addenda introducing new features or clarifications Errata correcting issues found after publication These updates address emerging needs such as enhanced cybersecurity, improved scalability, new device profiles, and better integration with modern IT and IoT architectures. As a result, referencing an outdated version of the BACnet standard can lead to interoperability issues, security gaps, or non-compliance with current certification requirements. This ongoing evolution explains why accessing the latest official version of the BACnet standard is essential for manufacturers, system integrators, consultants, and building owners alike. Where to Download the Latest BACnet Standard The latest BACnet standard cannot be downloaded from just any website. To ensure legal compliance, completeness, and accuracy, it must be obtained from official standards organizations only. These organizations are responsible for publishing, maintaining, and updating the BACnet specification, including its errata and addenda. Official Sources for the BACnet Standard Source Description BACnet.org Official BACnet website providing guidance and redirection to authorized publishers ASHRAE Primary publisher of BACnet as ASHRAE Standard 135 ISO International version published as ISO 16484-5 ANSI Provides access to the US national version of the standard BACnet.org: A Starting Point, Not a Download Portal The official BACnet website does not host the standard itself. Instead, it serves as a trusted reference point that explains: What the BACnet standard is How it is governed Where to legally obtain the latest version From BACnet.org, users are redirected to authorized publishers such as ASHRAE or ISO, ensuring they access the correct and most recent documentation. ASHRAE: The Primary Publisher ASHRAE is the main authority behind the BACnet standard. The latest version of ASHRAE Standard 135 can be purchased directly from ASHRAE’s digital standards store. This version includes: The full normative text Official diagrams and definitions Compatibility with certification and compliance processes This is the most commonly referenced source by manufacturers, integrators, and consultants worldwide. ISO and National Standards Bodies Internationally, BACnet is published as ISO 16484-5. Depending on your country, you may access it through: ISO’s official website National standards organizations affiliated with ISO In some regions, national standards bodies provide free, read-only access to the standard for public consultation. However, this access is often limited (no download, no printing) and may not include the latest addenda. Access to the BACnet standard depends on where and how you obtain it. While BACnet is often described as an open standard, this does not automatically mean free access to the full specification. Free vs Paid Access to the BACnet Standard Access Type What You Get Paid (ASHRAE / ISO) Complete, official, up-to-date and legally valid standard Free (national bodies) Read-only access, sometimes limited or outdated Unofficial sources High risk of outdated, incomplete, or illegal copies Relying on unofficial downloads can lead to implementation errors, compliance issues, and legal risks. For any professional use—product development, system integration, certification, or specification writing—official sources remain the only safe option. Is the BACnet Standard Free or Paid? The BACnet standard is often described as an open standard, but this does not necessarily mean free access. In most cases, the full and official specification must be purchased from authorized standards organizations such as ASHRAE or ISO.

How often is the BACnet standard updated? Key Takeaways : How often is the BACnet standard updated? BACnet is a living, evolving standard designed to adapt to changes in building automation technologies The standard is governed by ASHRAE under ANSI/ASHRAE Standard 135 There is no fixed annual update schedule for BACnet revisions Major revisions typically occur every few years Interim updates are delivered through addenda and errata Working groups continuously propose enhancements and corrections Updates often focus on interoperability, cybersecurity, and IP-based communication Following BACnet updates is essential for long-term system compatibility Table of Contents How often is the BACnet standard updated? BACnet is one of the most widely adopted communication standards for Building Automation and Control Systems (BACS). Designed to ensure interoperability between devices from different manufacturers, the BACnet standard plays a critical role in modern smart buildings, from HVAC and lighting to energy management and security systems. But BACnet is not static. As building technologies evolve, so do requirements around cybersecurity, data exchange, IP-based networking, and system scalability. This naturally raises a common question among system integrators, manufacturers, and building owners alike: how often is the BACnet standard updated? Unlike software products that follow strict release cycles, BACnet evolves through a structured but flexible process governed by ASHRAE. Updates are introduced through major revisions, intermediate addenda, and errata—each serving a specific purpose. Understanding this update rhythm is essential to ensure long-term interoperability, compliance, and future-proof building architectures. In this article, we explore how frequently BACnet is updated, how these updates are managed, and what they mean for the building automation ecosystem. How the BACnet update process works The evolution of BACnet is governed by a formal, consensus-driven process led by ASHRAE (the American Society of Heating, Refrigerating and Air-Conditioning Engineers). BACnet itself is officially published as ANSI/ASHRAE Standard 135, which defines how devices in building automation systems communicate. A committee-based governance model BACnet updates are developed and reviewed by the BACnet Standing Standard Project Committee (SSPC 135). This international committee brings together manufacturers, system integrators, engineers, consultants, and end users. Its mission is to ensure that the standard remains technically robust, interoperable, and aligned with real-world building requirements. Rather than following a fixed release calendar, the committee works on a continuous improvement model. Proposed changes are discussed, refined, publicly reviewed, and only then approved for inclusion in the standard. Three types of BACnet updates BACnet evolves through three main mechanisms, each with a different scope and impact: Update Type What It Covers Major revisions A consolidated new edition of the BACnet standard (ASHRAE 135) Addenda Incremental functional enhancements, extensions, or clarifications released between editions Errata Corrections for errors, ambiguities, or inconsistencies found after publication This layered approach allows BACnet to evolve without forcing disruptive changes across the entire ecosystem. Why BACnet does not follow a fixed update schedule BACnet updates are needs-driven, not time-driven. Changes are introduced when: New technologies emerge (IP networking, secure communications, cloud integration) Interoperability gaps are identified in real deployments Cybersecurity requirements evolve Industry stakeholders request new object types or services As a result, some years may see multiple addenda, while others focus on consolidating existing changes into a new official revision. From proposal to publication Before any update becomes part of the BACnet standard, it must go through: Technical proposal within the committee Internal review and refinement Public review and comment period Final approval and publication by ASHRAE This rigorous process ensures stability and backward compatibility—key requirements for building systems expected to operate for decades. How often are major BACnet revisions released? Unlike software platforms that follow predictable annual or biannual release cycles, BACnet major revisions are published on an irregular but relatively stable long-term rhythm. On average, a consolidated new edition of the BACnet standard is released every 3 to 5 years, depending on the volume and significance of accumulated changes. No fixed calendar, but a clear pattern BACnet is published as ANSI/ASHRAE Standard 135 under the responsibility of ASHRAE. A new major revision is typically issued when: A sufficient number of addenda have accumulated Structural or architectural changes need to be consolidated New communication paradigms (such as secure IP-based transport) must be formally integrated Rather than pushing frequent disruptive releases, the committee prioritizes stability, backward compatibility, and long-term operability, which are essential in building automation systems expected to remain in service for decades. Historical overview of major BACnet revisions The table below highlights the cadence of major BACnet editions and illustrates how updates tend to cluster around significant technological shifts rather than fixed dates. BACnet Edition Publication Year ANSI/ASHRAE 135-1995 1995 ANSI/ASHRAE 135-2001 2001 ANSI/ASHRAE 135-2004 2004 ANSI/ASHRAE 135-2012 2012 ANSI/ASHRAE 135-2016 2016 ANSI/ASHRAE 135-2020 2020 Olivier Hersent “BACnet’s strength lies in its ability to evolve without breaking existing systems. The standard is deliberately updated at a measured pace, ensuring that innovation—whether in IP networking or cybersecurity—can be adopted while preserving long-term interoperability in buildings.” Historical overview of major BACnet revisions A major BACnet revision is not simply a packaging exercise. It often reflects structural evolution of the protocol, such as: Expanded support for IP-based networking New standardized object types and services Enhanced interoperability rules Alignment with evolving cybersecurity expectations For example, recent editions have progressively paved the way for secure communication profiles and more scalable architectures, responding to the increasing convergence between building systems and IT networks. Why this matters for manufacturers and integrators Because major revisions are infrequent, most BACnet deployments remain compatible across multiple editions. However, system designers and manufacturers must monitor new releases carefully to: Anticipate upcoming compliance requirements Plan firmware or software roadmaps Ensure long-term interoperability in multi-vendor environments In practice, this balance between slow major releases and frequent incremental updates is what allows BACnet to evolve without fragmenting the ecosystem. Addenda and errata: how BACnet evolves between major releases While major BACnet revisions are released only every few years, the standard continues to evolve between editions through a steady stream of addenda and errata. This mechanism allows BACnet to remain responsive to technological change

What’s the difference between ASHRAE 135 and 135.1? Key Takeaways : Difference between ASHRAE 135 and 135.1? What BACnet is and why it has become the global reference protocol for building automation The role of ASHRAE in defining and governing the BACnet standard How BACnet ensures interoperability across multi-vendor building systems The scope of ASHRAE 135 and what it standardizes — and what it does not The relationship between BACnet, ISO standardization, and international adoption Core BACnet concepts: objects, services, data models, and communication layers How BACnet evolves through addenda and backward-compatible updates Why BACnet is foundational for modern smart buildings and IoT-driven BMS architectures Table of Contents Why the BACnet Standard Matters Buildings are long-term assets. HVAC systems, lighting controls, safety equipment, and energy management platforms are often expected to operate reliably for 20 to 30 years, sometimes more. Yet the technologies used to manage these systems evolve rapidly, creating a structural tension between innovation and durability. Historically, building automation relied heavily on proprietary communication protocols, each tied to a specific manufacturer. While these solutions could be effective in isolated deployments, they introduced long-term constraints: vendor lock-in, limited interoperability, complex upgrades, and rising lifecycle costs. The BACnet standard emerged as a response to this challenge. Rather than defining how building systems should be engineered or operated, BACnet focuses on a more fundamental question: how systems communicate. By standardizing data models and communication rules, BACnet enables devices from different vendors to exchange information in a consistent and predictable way—without imposing proprietary dependencies. This approach fundamentally shifts control back to building owners and operators. Systems can evolve over time, equipment can be replaced or extended incrementally, and technology choices remain open. As a result, BACnet has become a cornerstone of modern building automation, widely adopted in commercial buildings, critical infrastructure, campuses, and smart cities worldwide. Understanding the BACnet standard is therefore not just a technical concern. It is a strategic issue for anyone involved in building design, operation, or digital transformation. What Is the BACnet Standard (ASHRAE 135)? The BACnet standard is a formal, open standard that defines how building automation systems communicate with each other. Officially published as ASHRAE Standard 135, it provides a vendor-neutral framework that enables interoperability across building technologies, regardless of manufacturer or underlying implementation. BACnet does not describe products, architectures, or control strategies. Instead, it defines a common communication model that allows systems to exchange information in a consistent and predictable way. This distinction is essential: BACnet is not a product specification, nor a performance guarantee—it is a standardized language for building systems. The standard is developed and maintained by ASHRAE, which ensures that BACnet remains technically coherent, open, and aligned with real-world industry needs. Over time, the standard has evolved to support new use cases and technologies while preserving compatibility with existing installations. What BACnet Standardizes — and What It Does Not BACnet’s strength lies in the clarity of its scope. By focusing exclusively on interoperability, the standard avoids constraining innovation or system design choices. Aspect Defined by the BACnet Standard Data models and semantics Yes Communication rules Yes Interoperability principles Yes Vendor neutrality Yes Product quality No System performance No Project execution No In practice, this means that BACnet ensures systems can understand each other, but not that they are well-designed, correctly installed, or optimally operated. Those responsibilities remain with manufacturers, integrators, and building stakeholders. This deliberate separation explains why BACnet has proven both durable and adaptable. It provides a stable foundation that supports competition, long system lifecycles, and incremental modernization—without locking the market into proprietary ecosystems. For readers seeking a more detailed view of the formal structure and publication framework of ASHRAE 135, a dedicated overview is available here: Understanding BACnet as ASHRAE Standard 135. How the BACnet Standard Is Governed and Maintained The long-term relevance of BACnet is closely tied to how the standard is governed. Unlike proprietary protocols or vendor-driven specifications, BACnet follows a formal standardization process designed to ensure neutrality, transparency, and continuity over time. The governance of BACnet is overseen by ASHRAE, which acts as the sole technical authority for ASHRAE Standard 135. This role is not commercial in nature: ASHRAE does not manufacture products, certify implementations, or promote specific vendors. Its responsibility is to safeguard the technical integrity and consistency of the standard itself. A Neutral and Open Governance Model BACnet is maintained through an open, consensus-based process involving a broad range of industry stakeholders. Manufacturers, system integrators, consultants, engineers, and building owners can all contribute to the evolution of the standard. Key principles of this governance model include: Open participation, ensuring that no single interest dominates Consensus-driven decisions, balancing innovation with stability Public review and comment periods, allowing industry-wide feedback This structure is essential in a domain where systems are expected to remain operational for decades. It ensures that changes are introduced carefully, with a clear understanding of their long-term impact. Clear Separation of Responsibilities Another defining characteristic of BACnet governance is the strict separation between standard definition and system implementation. Responsibility Scope Technical specification Defined and maintained by ASHRAE Evolution of the standard Managed through formal revisions and addenda Product implementation Handled by manufacturers System design and integration Handled by integrators and engineers Operational performance Responsibility of building owners and operators By limiting its role to the standard itself, ASHRAE preserves BACnet’s vendor neutrality and prevents fragmentation. This approach allows the market to innovate freely while relying on a stable and trusted interoperability foundation. As a result, BACnet is not only a technical specification, but also a governance framework—one that supports long system lifecycles, multi-vendor ecosystems, and predictable evolution in an industry where change must be carefully managed. BACnet and International Standardization (ISO) While BACnet is authored and governed as ASHRAE Standard 135, its reach extends well beyond North America. To support global adoption and regulatory alignment, BACnet is also published internationally as ISO 16484-5. This dual standardization model plays a critical role in the worldwide success of BACnet. It allows the standard to combine

Understanding the BACnet Standard (ASHRAE 135) Key Takeaways : BACnet Standard (ASHRAE 135) BACnet is formally defined as ASHRAE Standard 135, not merely a technical protocol. The standard was created to address interoperability and vendor lock-in at an industry level. ASHRAE provides a governance framework that ensures long-term stability and evolution. BACnet’s standardization separates normative rules from vendor-specific implementations. The addenda-based update process allows BACnet to evolve without breaking existing systems. Adoption as ISO 16484-5 confirms BACnet’s role as a global reference standard. ASHRAE 135 defines what must be common, not how products must be engineered. BACnet’s value lies in its institutional continuity, not just its technical features. Table of Contents Understanding BACnet as ASHRAE Standard 135 BACnet is often described as a building automation protocol, but this definition alone fails to capture its true nature and long-term significance. Beyond its technical capabilities, BACnet is first and foremost a formal international standard, developed, governed, and maintained within a rigorous institutional framework. Published as ASHRAE Standard 135, BACnet represents the building automation industry’s response to a fundamental challenge: ensuring long-term interoperability, vendor neutrality, and consistency across increasingly complex building systems. Rather than addressing a single technology or use case, the standard provides a stable and extensible foundation upon which building automation solutions can evolve over decades. Understanding BACnet as an ASHRAE standard means looking beyond implementation details to examine why it was standardized, how it is governed, and what guarantees it provides at an industry level. This perspective is essential for decision-makers, consultants, and architects who must design building systems with long life cycles, regulatory constraints, and multi-vendor environments in mind. Why BACnet Was Standardized by ASHRAE The standardization of BACnet by ASHRAE was not driven by technological novelty, but by a structural problem within the building automation industry. Before BACnet, building systems relied heavily on proprietary communication protocols, each tied to a specific manufacturer or product ecosystem. Challenge Impact on Building Automation Projects Limited interoperability Systems from different vendors struggle to communicate seamlessly High integration costs Custom gateways and complex commissioning increase project budgets Vendor dependency Long-term reliance on a single manufacturer limits flexibility Limited scalability Upgrading or extending systems becomes complex and risky over time This fragmentation created significant challenges: Limited interoperability between systems High integration and commissioning costs Long-term dependency on individual vendors Difficulty upgrading or extending installations over time For an industry in which buildings are expected to operate for decades, these constraints were incompatible with sustainable design and long-term asset management. Aligning with ASHRAE’s Mission Standardizing BACnet within ASHRAE also aligned with the organization’s broader mission: advancing building performance, efficiency, and sustainability through open, technically sound standards. By embedding BACnet within this institutional framework, ASHRAE ensured that the protocol would evolve according to industry needs and technical consensus, rather than short-term market pressures. As a result, BACnet became more than a communication mechanism—it became a shared foundation for how building automation systems are specified, designed, and evaluated worldwide. What Does “ASHRAE Standard 135” Really Mean? Referring to BACnet as ASHRAE Standard 135 has a precise and important meaning. It indicates that BACnet is governed by a formal standardization framework, not simply published as a technical specification or implementation guide. Understanding this distinction is essential, as the terms protocol, specification, standard, and certification are often used interchangeably—incorrectly so—in building automation discussions. Protocol, Specification, and Standard: Key Differences A protocol describes how systems communicate. A specification documents how a technology works. A standard, however, goes further: it defines normative rules, establishes compliance requirements, and is maintained through a recognized governance process. ASHRAE Standard 135 places BACnet in this third category. Specification vs Standard vs Certification Concept What It Means in Practice Specification Technical description of how something works Standard Normative, consensus-based rules maintained by a standards body Certification Process to verify conformance to a standard What ASHRAE Standard 135 Covers ASHRAE 135 defines: The normative communication model for BACnet The structure and behavior of standardized elements The rules that ensure consistent interpretation across vendors Crucially, the standard specifies what must be common, not how products must be implemented internally. This separation allows manufacturers to innovate while remaining compliant with the same shared rules. What the Standard Does Not Define Equally important is what ASHRAE 135 deliberately leaves out. The standard does not prescribe: Product performance or quality levels User interface design System architecture choices Project-specific integration practices This boundary ensures that the standard remains stable, neutral, and adaptable, even as technologies, networks, and building requirements evolve. By clearly defining the scope of what is standardized—and what is not—ASHRAE Standard 135 provides a robust foundation without constraining innovation or architectural freedom. Governance of BACnet: How ASHRAE Manages the Standard One of the defining characteristics of BACnet is not its technical structure, but the way it is governed over time. As ASHRAE Standard 135, BACnet is managed through a formal, transparent, and consensus-driven standardization process designed to ensure long-term stability while allowing controlled evolution. A Structured Governance Model BACnet is maintained by a dedicated standards committee operating under ASHRAE’s rules for standards development. This governance model is designed to balance innovation with backward compatibility, a critical requirement in an industry where systems are expected to remain operational for decades. Governance Principle What It Means in Practice Open participation Industry stakeholders can contribute to the standard development process Consensus-based decision-making Changes are approved through collective agreement rather than unilateral control Public review and comments Draft updates are openly reviewed and commented before approval Clear normative boundaries Strict separation between mandatory requirements and informative guidance This approach ensures that no single vendor or technology roadmap can dominate the evolution of the standard. The Addenda-Based Evolution Process Rather than releasing disruptive new versions, ASHRAE evolves BACnet through addenda. Each addendum introduces clearly defined changes or extensions to the standard, which are reviewed, approved, and published independently. Standard Evolution Benefit What It Enables in Practice Incremental innovation New technologies are introduced gradually without disrupting existing systems Backward compatibility Existing installations remain functional as