The latest specification of the Talq Consortium includes a waste management profile, which has been requested by many members, demonstrating the momentum behind smart waste.
The Talq Consortium has added a waste management profile to the latest release of its Smart City Protocol.
The protocol is a global interface standard for managing heterogeneous smart city device networks. It enables interoperability between central management software (CMS) and outdoor device networks (ODN) from different vendors so that a single CMS can control different ODNs in different parts of a city or region.
The profile in the newly released version 2.3.0 includes a description of a waste container, a weight sensor, an accelerometer, a pH sensor and a gas sensor. The consortium said that this particular profile was requested by many members, demonstrating the momentum that has developed in the waste management sector in smart cities.
Smarter waste management can help to realise important savings in both costs and carbon emissions as waste collection is based on real data gathered live from containers.
Additionally, the consortium has added several other new features and stated that it is significant that most of the new requests address smart city applications other than street lighting. All protocol updates aim to improve the interoperability of different systems and so ease investment decisions for cities and other operators. It also reports that some minor bugs have been fixed and some descriptions have been clarified with the inclusion of several real examples.
To respond best to all new requirements of users and system manufacturers, the Smart City Protocol is regularly reviewed and updated. Talq members and partners, such as cities and consultants, can propose new functions and other changes. All requests are reviewed by the requirements work group before being passed on to the technical work group for approval and integration.
As a result of the API changes, new releases of the specification, data model files and Talq Certification Tool (TCT) have been created. From now on, the technical capability to run the TCT with Docker is provided by the installation documentation file, allowing developers to use the tool without worrying about Java configuration and dependencies.
“As with all the existing functions already defined, the challenge is to describe new functions in a way which best balances interoperability, implementation complexity and feature value”
The TCT also includes the possibility of running selected test cases only without waiting for the whole test session to finish, and pausing and resuming a test session have been made simpler.
“As with all the existing functions already defined, the challenge is to describe new functions in a way which best balances interoperability, implementation complexity and feature value,” said Simon Dunkley, secretary general, Talq Consortium, which was founded in 2012 and consists of around 50 members.
He added: “To successfully manage this goal, the collaboration between members is fundamental. Releasing version 2.3.0 proves again the engagement, trust and openness among all parties.”
Version 2.3.0 is fully compatible with all existing certified Talq-compliant products certified against Version 2.x.
You might also like: