Certifications & standards

Procurement and compliance teams need to know exactly which standards a platform is built against, and where formal certification stands. This page lays out the standards bodies relevant to xSERVA and is explicit about what is confirmed today versus what is in progress.

Ask About Compliance
A conformance test rig on a laboratory bench, a circuit assembly clamped in a jig with fine test leads fanning out to a breakout board under a task lamp.
Conformance is decided on a rig. The certificate only records what the rig already found.

BTL: BACnet Testing Laboratories — pursuing, not held

The BACnet Testing Laboratories (BTL) is the independent body that verifies a product correctly implements the BACnet standard it claims to support, giving specifiers confidence that a listed device will interoperate correctly with other BACnet equipment on a project. xSERVA’s BACnet integration is being built to align with the BACnet specification that BTL testing verifies against, and pursuing formal BTL Listing is part of our standards roadmap. Both the integration and the listing are ahead of us, not behind us: protocol integration is an unbuilt module today. See the roadmap section below.

KNX Association Certified Partner — pursuing, not held

The KNX Association administers certification for products and partners working with the KNX standard, covering correct implementation of group addressing, datapoint types, and ETS-based configuration. xSERVA’s KNX integration is being engineered against the published KNX specification, and becoming a recognized KNX Association Certified Partner is part of the standards roadmap we are actively pursuing, rather than a status already held. The KNX integration itself is part of the protocol module that is still on the roadmap.

A calibration bench at night, a precision reference instrument and a device under test side by side with a short interconnect between them.
A reading is a claim until something traceable agrees with it.

Modbus Organization — pursuing, not held

The Modbus Organization maintains the Modbus protocol specification used widely across meters, generators, and industrial equipment in building environments. xSERVA’s Modbus TCP and RTU support is being built to conform to the published Modbus specification, and formal membership or recognition with the Modbus Organization is part of the standards alignment we are pursuing, alongside our BACnet and KNX roadmap items. As with the other two, the Modbus support itself is roadmap rather than something running in the product today.

Compliance roadmap

Roadmap — certifications in progress, not yet held.

We are explicit that BTL Listing, KNX Association Certified Partner status, and formal Modbus Organization recognition are certifications xSERVA is working toward, not credentials already on file. Our engineering approach is to build strictly to each standard’s published specification first, so that when formal certification testing is completed, it confirms conformance that already exists in the product rather than triggering rework. If a specific certification is a hard requirement for your tender or procurement process, message our team directly for the current, up-to-date status.

The three bodies governing the protocols xSERVA speaks — BACnet Testing Laboratories, the KNX Association and the Modbus Organization — each shown with a dashed status badge reading in progress, not held, because none of these certifications is currently on file. Separately marked as engineered in today: encrypted data transport, role-based access control and PDPA-aligned data handling.
The three protocol certifications are in progress. The practices below them are in the platform today.
An electronics test bench in a dim laboratory at night, benchtop instruments with softly glowing readouts, probe leads coiled on an anti-static mat and an assembly under a magnifier lamp.
Conformance is decided on a bench like this one. A certificate only records what the bench already found.
A shelf of thick unmarked technical binders in a dim office, spines square to the camera, a reading lamp throwing a warm pool across the middle of the row.
The documents matter, but only because somebody keeps re-reading them.

Security and data compliance

Alongside protocol standards, xSERVA is engineered with encrypted data transport, role-based access control, and data handling practices designed with Malaysia’s Personal Data Protection Act (PDPA) in mind. For a full breakdown of our security architecture, visit the security and compliance page.

See security & compliance →

Frequently asked questions

Is xSERVA already BTL Listed, KNX Certified, and a Modbus Organization member?

These are the standards bodies xSERVA is built to align with and is pursuing recognition from, not certifications already held. See the roadmap note on this page for the current status.

Why does protocol alignment matter if certification is still in progress?

Because the order matters. xSERVA's BACnet, KNX, and Modbus support is being built against each standard's published specification first, so that when formal certification testing happens it confirms conformance rather than triggering a rewrite. To be clear about the current state: the protocol integration module is on the roadmap and is not available in the product today, so there is no shipping protocol behavior for an integrator to rely on yet.

What data security practices does xSERVA follow?

xSERVA is engineered with encrypted data transport, role-based access control, and PDPA-aware data handling practices for personal and building data. Full detail is available on our security and compliance page.

When will formal certifications be completed?

Timelines depend on each certifying body's process. Message our team on WhatsApp for the current status of any specific certification you need for a procurement or tender requirement.