Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
CAN CSA ISO IEC TR 15067-3-2-18: Home Electronic System (HES) Application Model – Process Management System
A comprehensive technical overview of the Canadian adoption of ISO/IEC Technical Report 15067-3-2:2018 for interoperable smart home process management
The standard CAN CSA ISO IEC TR 15067-3-2-18 is the Canadian Standards Association (CSA) adoption of the ISO/IEC TR 15067-3-2:2018, titled “Information technology — Home Electronic System (HES) application model — Part 3-2: Model of a process management system for HES.” This technical report provides an informative framework for modeling and managing processes within a Home Electronic System (HES), enabling interoperable, flexible, and efficient control of smart home devices and services. This article examines the scope, architectural components, implementation insights, and compliance notes for this standard.
Scope and Purpose of CAN CSA ISO IEC TR 15067-3-2-18
The primary objective of this Technical Report is to define a generic model for a process management system (PMS) in the context of a Home Electronic System (HES). It addresses the need for a consistent representation of processes—such as energy management, security, health monitoring, and comfort control—that can be deployed across heterogeneous home environments. The document is intended for system architects, device manufacturers, and software developers who design interoperable smart home solutions.
Key inclusions in the scope:
- Definition of process concepts and their relationships within an HES.
- Specification of the PMS model, including components like process definition, process instance, process state, and event handling.
- Guidelines for mapping home automation application processes to the model.
- Informative examples illustrating typical use cases (e.g., scheduled lighting, alarm system activation).
Tip: This Technical Report is informative (not normative). Use it as a design blueprint when building HES-compliant systems; it helps ensure that applications from different vendors can coordinate processes seamlessly.
Technical Model Architecture
The process management system defined in CAN CSA ISO IEC TR 15067-3-2-18 is built around a set of core entities and their interactions. The model centers on a Process Manager that supervises the lifecycle of processes within an HES gateway or controller. Each process is described through its attributes, behavior, and state transitions.
Core components of the PMS model
| Component | Description | Example in HES |
|---|---|---|
| Process Definition | Template describing the logic, inputs, outputs, and flow of a process. | “Security Alarm” definition with trigger events, delay, notification steps. |
| Process Instance | A running occurrence of a process definition, holding current state and data. | Specific alarm instance waiting for sensor input. |
| Process Manager | Central component that creates, monitors, terminates, and coordinates process instances. | HES controller software module. |
| State Machine | Defines allowed states (e.g., inactive, active, suspended, completed) and transitions based on events or conditions. | Transition from “armed” to “alarm triggered”. |
| Event & Condition | External or internal triggers (time, sensor data, user command) that influence process behavior. | Motion sensor event, temperature threshold condition. |
| Resource Binding | Mapping of process steps to actual HES devices (actuators, sensors, services). | Binding “turn on light” to a specific smart bulb. |
Process lifecycle and state management
The model defines standard states: Created, Ready, Running, Suspended, and Completed/Terminated. The Process Manager ensures consistency across concurrent processes and resolves conflicts, e.g., by applying priority rules defined in the application model.
Important: Implementers must handle state synchronization carefully, especially when multiple process instances attempt to control the same device. The standard recommends a locking mechanism or a priority scheme to avoid erratic behavior.
Implementation Considerations
When applying CAN CSA ISO IEC TR 15067-3-2-18 in a real-world smart home product or service, developers should consider the following aspects:
Mapping to existing smart home protocols
The PMS model is protocol-agnostic. It can be realized on top of Zigbee, Z-Wave, Wi-Fi, or other IoT stacks. The key is to expose process definitions and state information through a common interface (e.g., using Web Services or a REST API).
Graceful degradation and error handling
The Technical Report encourages robust fail‑over strategies. If a process instance cannot complete due to a device failure, the Process Manager should either trigger an alternative sequence (fallback) or report the failure to the user.
Interoperability with other HES application models
This PMS model aligns with other parts of the ISO/IEC 15067 series, especially Part 3-1 (Energy management) and Part 4 (System management). Coordinating these models enables advanced scenarios like demand‑response and adaptive lighting.
Best practice: Use a design methodology that separates process logic from device‑specific bindings. This approach, advocated by the standard, simplifies maintenance and porting to new hardware platforms.
Compliance and Adoption Notes
Because this document is a Technical Report (TR), it does not assert mandatory requirements for certification. However, demonstrating alignment with the PMS model can be critical for achieving broader interoperability in a multi‑vendor smart home ecosystem.
Using CAN CSA ISO IEC TR 15067-3-2-18 in product development
- Claiming compliance: A product may claim “conformance to the model described in CAN CSA ISO IEC TR 15067-3-2-18” if it implements the core components (Process Manager, state machine, event handling) as defined.
- Testing: Interoperability tests can be designed around the state‑behavior checkpoints listed in the TR.
- CSA endorsement: The Canadian adoption ensures that the model is recognized in North American markets; additional local requirements (e.g., safety, electrical) must still be met.
Caution: The Technical Report does not specify security nor data privacy mechanisms. Implementers must supplement it with appropriate cybersecurity measures (e.g., encryption, authentication) in accordance with standards like ISO/IEC 27001 or IEEE 2413.
Future outlook
The process management model is expected to play a foundational role in next‑generation smart home platforms, especially when combined with AI‑based decision making. The TR provides a stable reference that can evolve with new service requirements.
Tip: Stay updated with the latest amendments from ISO/IEC JTC 1/SC 25/WG 1, the working group responsible for the 15067 series. The Canadian version (CAN CSA ISO IEC TR 15067-3-2-18) follows the same release cycle as the international document.
Frequently Asked Questions (FAQs)
Q: Is CAN CSA ISO IEC TR 15067-3-2-18 a mandatory standard in Canada?
A: No, it is an informative Technical Report adopted by CSA. It provides guidance for designing interoperable home electronic systems but is not a mandatory legal requirement.
A: No, it is an informative Technical Report adopted by CSA. It provides guidance for designing interoperable home electronic systems but is not a mandatory legal requirement.
Q: What is the difference between a Technical Report and an International Standard in the ISO/IEC context?
A: A Technical Report is purely informative—it offers best practices, models, or survey information. An International Standard contains normative requirements that must be followed for compliance. CAN CSA ISO IEC TR 15067-3-2-18 is the former.
A: A Technical Report is purely informative—it offers best practices, models, or survey information. An International Standard contains normative requirements that must be followed for compliance. CAN CSA ISO IEC TR 15067-3-2-18 is the former.
Q: How does this PMS model relate to other smart home models like OCF or Matter?
A: The model is abstract and protocol‑independent. It can serve as a high‑level architectural blueprint that complements device‑level specifications like Matter (which focuses on application‑layer interoperability). The PMS model adds process orchestration capabilities not fully covered by many current smart home standards.
A: The model is abstract and protocol‑independent. It can serve as a high‑level architectural blueprint that complements device‑level specifications like Matter (which focuses on application‑layer interoperability). The PMS model adds process orchestration capabilities not fully covered by many current smart home standards.
Q: Can I use the model for commercial building automation (BACS)?
A: While originally designed for home environments (residential HES), the generic nature of the process management model makes it applicable to small‑scale building automation. However, for larger systems you should also consider standards like ISO 16484 (Building automation and control systems).
A: While originally designed for home environments (residential HES), the generic nature of the process management model makes it applicable to small‑scale building automation. However, for larger systems you should also consider standards like ISO 16484 (Building automation and control systems).
© 2026 — Technical Review of CAN CSA ISO IEC TR 15067-3-2-18. This article is for reference purposes and does not substitute the official standard document. Always consult the latest version published by CSA Group or ISO/IEC.