Build on meaning.
Engineer for reality.
A shared spatial model connects authoring tools, generated configuration and installed systems. Explore the contracts and boundaries that make the chain understandable.
Explore the engineering guides
One foundation.
Purpose-built consumers.
Spatial identity and capabilities carry meaning. Each consumer receives the representation appropriate to its responsibility.
Manager
Rooms · geometry · design intent
ENGINEERINGStudio
Objects · bindings · configuration
Spatial identity
+ capabilities
Ownership, scope and revision
Architecture overview · a conceptual engineering map, not a public API specification.
The contract becomes inspectable.
The Studio SuperChart connects an object’s identity with control and status addresses, data types and generated configuration. A command and its feedback are different engineering facts.
Explore Studio
Publishing is a state transition, not a file copy.
A configuration is only useful when the edge can receive and interpret it. The engineering record separates authored drafts, published revisions and runtime readiness rather than treating an upload as completion.
| Boundary | Responsibility | Engineering consideration |
|---|---|---|
| Readiness | Gateway ready · network reachable · protocol connected | Report completion only after the required edge confirmations. |
| Version ordering | A revision sequence with explicit ordering | Numeric comparison avoids the “9 versus 10” string-ordering failure. |
| Atomic promotion | A coherent published revision | Avoid presenting a partially updated configuration as a complete release. |
What if the project has no conventional chart?
Valid project shapes need explicit handling. Engineering work includes bootstrap drafts and LifeSmart-only configurations. A reliable publisher validates the actual project shape instead of assuming that every installation follows one chart-based path.
Choose your engineering boundary.
All guides
Concept artworkAuthoring to runtime
Follow a shared project model into generated views, configuration and runtime reconciliation.
View guide
Concept artworkModel & identity
Separate stable spatial identity, ownership and capabilities from protocol addresses.
View guide
Concept artworkProtocol integration
Understand KNX bindings, cloud-connected devices and the distinction between commands and observations.
View guide
Concept artworkValidation & release
Review model agreement, mixed-system composition and physical outcomes before release.
View detailsBring an integration problem.
Start with the installation context, device family, interface and desired outcome. These guides explain our engineering approach; project-specific interfaces and access are discussed with the team.
Discuss an integration