We had a talk with the President and Executive Director of DLMS UA, Sergio Lazzarotto. We covered the main goals and values of DLMS and talked about the importance of compatibility. DLMS recently took over the IDIS Association, and we discussed further plans regarding the standardization of device applications, all within the same organization.
In our conversation, we also touched upon the benefits of being a member of DLMS and how its members can benefit from being the first to gain access to the latest specification.
What would you say are your organization’s core values?
DLMS is an association that aggregates the representatives of certain industries, companies manufacturing and using devices for strategic infrastructures. When we say “certain industries” we’re talking about the 4 pillars: electricity, water, gas, and heat.
Within this, our responsibility is to guarantee that these companies offer products that are compatible. Beyond standardizing the data exchange protocol between devices, DLMS also guarantees that these products that use the DLMS standard are compatible and interoperable.
A standard that is not tested has little to no value. That is why we aim to give certificates of compatibility. Being interoperable is one thing, but being compatible, having interchangeability – that is something even more. When offering plug & play devices, you offer a higher value. Plug & play devices can come from different manufacturers, which makes it easier for users.
We also offer training to our members and have an international footprint across all continents.
What would you say are the main goals of DLMS?
Our main goal is to raise the level of interoperability for devices so that they become interchangeable. DLMS wants to be the standard of choice, innovating through the standardization, standardizing the digitalization of the last mile of electricity, water, gas and heat strategic infrastructures bringing the digital convenience in the hand of the consumers through the distributed energy resources and demand response management.
We want to not only work in defining the standard but defining implementation models as well. We want to make a specification of a certain type of implementation – for a specific application.
A minimum level of implementation brings a minimum set of functionalities that should be standardized; defining what specific application should be standardized is what is bringing interoperability and compatibility between devices and manufacturers.
Depending on the above-mentioned 4 pillars: water, gas, electricity, or heat, DLMS teams are working on not only standardizing the protocol but defining generic profiles. Generic profiles are the minimum set of functionalities by applications.
Can you explain the reasons for the acquisition of the IDIS Association, and what are the further plans in this regard?
It was a natural step. Who better than DLMS can, within its organization, standardize certain implementations in order to address certain application requirements? The merge with DLMS and what’s been done in IDIS is a logical step and only the beginning of this strategy.
I have experience with different standardizations where similar things have happened, and everything was done within the mother organization.
Bluetooth is a good example: the first few years were spent on the protocol itself. Then, working groups worked on specific applications (Bluetooth audio profile, Bluetooth headset profile, Bluetooth HID profile, etc.). Now, over 50 different applications of Bluetooth exist. This is how standardization should be done. Creating standardization of certain applications within the same organization.
Does your acquisition mean that in the future DLMS will always have a specification that provides interoperability and not just a broad standard?
(Earlier, DLMS was defining quite broad standards, and IDIS provided interoperability/interchangeability)
We will have several standardized implementations for different applications. The first and most natural one is to build on top of what the IDIS association did. We already started doing this and will release the first DLMS electricity smart metering generic profile sometime this year. We’ll also release the first electric charging station generic profile which will permit the connection of the charging station with the smart meter.
We are working on other generic profiles for different applications: for the gas smart meter, the water smart meter, the multi-utility smart meter, etc.
Things are changing. People used to be only consumers, but now they can also produce and store energy (batteries, solar panels, etc.). This is where we want to be a reference point for standardization.
No matter which device or application is applying for obtaining the certificate, it will be tested for compliance. We want to guarantee that the implemented standard is compliant with our generic specification. Then, we test it for compatibility and interoperability. We are raising the level of the test and will look at the parameterization of the implementation.
On the compliance part, we look at the implementation. On the compatibility part, we will look at the parameterization of the implementation. Why? To make sure everything works in the way we are recommending. We are working with external accredited test labs that will perform compatibility test sessions. In those test sessions, we will test the devices in different settings.
Does this mean devices will only be able to be tested at these labs?
No. The manufacturer will still be able to test the device through authorized software and send the results to DLMS for certification for compliance. However, once you want to reach another certification level, such as compliance with a certain generic profile, the compatibility part, then the device will have to be submitted to an accredited lab. The lab will send the report to DLMS and we will give the certificate.
We are currently in the process of accrediting the labs. We will be looking at the candidate labs’ qualifications and start this process to accredit them by May. Our plan is to have at least one lab in every geographical region, all over the world.
One thing to also note is that we will also be offering this certification to non-DLMS members.
What are the benefits of becoming a member of the DLMS UA?
IEC is not as fast and not as flexible as DLMS. Their specifications are updated every 18 to 24 months, due to the way they operate and their need to be considered a stable reference. This means that, from the moment DLMS releases something, to the moment the IEC integrate it into their specification, there is a gap of 18 to 24 months. Basically, the DLMS members have access to the specification instantly, while those who rely only on IEC have to wait. This time to market advantage offers a serious competitive advantage to our members versus those who do not want to be DLMS UA members.
The second advantage of being a DLMS member is that you can participate in the working groups while specifications are being discussed, developed, approved, and modified. This means that members have an option to give their input and have the access to all versions instantaneously. Those members who participate will have access to these specifications even before other members of DLMS who didn’t participate in the working groups, which provides an advantage permitting those manufacturers to launch newly developed products few months after the specification is made public.
Conclusion
The DLMS User Association will provide the compatibility (interchangeability) of devices using a two-step certification process. The devices will first be tested for compliance with the DLMS specification and after that, the compatibility (interchangeability) test will be performed. The Association will accredit the external testing labs in different regions of the world to perform compatibility (interchangeability) tests, to help manufacturers obtain certificates locally.
Question for the audience
What do you think, could we achieve device compatibility in Smart cities, worldwide? How?