![\"Smart](\"https:\/\/blog.bosch-si.com\/wp-content\/uploads\/eebus-energy-transition-1136x729.jpg\")
EEBUS covers two aspects: first, there is a protocol \u2013 the SHIP (Smart Home IP) protocol. One of the principal objectives is to fulfil the strict security standards required in the energy domain. SHIP complies with the security regulations of the German Federal Office for Information Security.<\/p>\n
Second, and arguably more interesting, EEBUS defines a common language with which devices can communicate with each other. Today\u2019s energy market is very fragmented, with many different protocols, data models, and platforms in use. In other words, a standardized means of communication between different devices is highly practical: by speaking a common language, devices can work together in a way that helps optimize their power consumption. The underlying specification that makes this possible is known as SPINE (Smart Premises Interoperable Neutral-message Exchange).<\/p>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n
A big advantage of the EEBUS specification is that it is technology agnostic. First and foremost, the standard defines a way in which devices communicate with one another. This means that it can be viewed separately from the other technological aspects that come into play with IoT devices. Take the protocols, for example: you don\u2019t need to use the aforementioned SHIP protocol to make use of the EEBUS standard; you can simply stick to the one you\u2019re already using.<\/p>\n
Facilitating interoperability between IoT devices also brings a major benefit for consumers: they are not restricted to using devices of a single provider but are free to choose which one work best for them.<\/p>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n
Putting the EEBUS specification into practice<\/strong><\/p>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n So, what does it mean to put the standard by EEBUS into practice? We recently worked with the electricals company\u00a0Hager\u00a0on an application implementing this standard. In partnership with its customer Audi, Hager developed a home energy-management system for charging electric vehicles. The goal was to create an easy way of integrating\u00a0Audi\u2019s e-tron electric car\u00a0within a smart home infrastructure. An approach based on open standards was a key requirement \u2013 which is where we entered the picture.<\/p>\n Our contribution was to help implement two use cases covered by the EEBUS specification. The first was to protect against overload. Imagine you want to recharge your vehicle, but the domestic water heating is also switched on. This is where overload protection comes into play: the system is able to intelligently manage network loads, thus ensuring that the fuse doesn\u2019t blow.<\/p>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n The second use case we helped develop is designed to manage and coordinate vehicle recharging. Imagine you have a photovoltaic system. In this case, you can ensure that your car is recharged when photovoltaic power is available, rather than drawing electricity from the public grid. This use case can also help you reduce costs. For example, you can tell the system that your car should be ready to go at a specific time. It then charges the vehicle in the cheapest-possible way.<\/p>\n EEBUS, of course, goes way beyond these two use cases. If you want to learn more about how the EEBUS standard can be implemented in practice, check out our\u00a0article highlighting the various use cases.<\/p>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n Fuente:<\/strong>\u00a0https:\/\/blog.bosch-si.com<\/em><\/p>\n","protected":false},"excerpt":{"rendered":" EEBUS una asociaci\u00f3n que re\u00fane a 70 empresas Europeas vinculadas al mercado energ\u00e9tico, trabaja en est\u00e1ndares de optimizaci\u00f3n del IoT.<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":[],"categories":[23,29],"tags":[],"_links":{"self":[{"href":"https:\/\/www.fie.undef.edu.ar\/ceptm\/index.php?rest_route=\/wp\/v2\/posts\/3732"}],"collection":[{"href":"https:\/\/www.fie.undef.edu.ar\/ceptm\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.fie.undef.edu.ar\/ceptm\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.fie.undef.edu.ar\/ceptm\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.fie.undef.edu.ar\/ceptm\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=3732"}],"version-history":[{"count":0,"href":"https:\/\/www.fie.undef.edu.ar\/ceptm\/index.php?rest_route=\/wp\/v2\/posts\/3732\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.fie.undef.edu.ar\/ceptm\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=3732"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.fie.undef.edu.ar\/ceptm\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=3732"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.fie.undef.edu.ar\/ceptm\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=3732"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}