| <!doctype html> |
| <html data-n-head-ssr data-n-head=""> |
| <head data-n-head=""> |
| <title data-n-head="true">Eclipse unide - Frequently asked questions</title><meta data-n-head="true" charset="utf-8"><meta data-n-head="true" name="viewport" content="width=device-width,initial-scale=1"><meta data-n-head="true" data-hid="description" name="description" content="Eclipse Unide: Understand Industry devices"><link data-n-head="true" rel="icon" type="image/x-icon" href="/unide/favicon.ico"><base href="/unide/"><link rel="stylesheet" href="/unide/files/aacbf5835f7143d93ae2.css"><link rel="stylesheet" href="/unide/files/d0fdea7b1fe36ac7586f.css"> |
| </head> |
| <body data-n-head=""> |
| <div data-server-rendered="true" id="__nuxt"><!----><div id="__layout"><div><header class="nav-header"><div class="container"><nav class="navbar"><div id="navMenu" class="navbar-menu"><div class="navbar-start"><a href="/unide/" class="navbar-item"> |
| Home |
| </a> <a href="/unide/proposal" class="navbar-item"> |
| Proposal |
| </a> <a href="/unide/specification" class="navbar-item"> |
| Specification |
| </a> <a href="/unide/blog" class="navbar-item"> |
| Blog Archives |
| </a> <a href="/unide/faq" class="navbar-item nuxt-link-exact-active is-active"> |
| FAQ |
| </a></div></div> <div class="navbar-brand"><div class="navbar-burger burger"><span></span> <span></span> <span></span></div> <a href="/unide/" class="navbar-item nuxt-link-active"><img src="logo.svg"></a></div></nav></div></header> <div class="container"><div class="header clearfix"></div> <div class="columns"><div class="faq column is-8"><h1 class="title is-3"> |
| Frequently Asked Questions |
| </h1> <div> |
| We assembled a few frequently asked questions about the Production Performance Protocol (PPMP) and the Unide project. You're welcome to raise your questions in the <a href="https://www.eclipse.org/forums/index.php/f/348/">Unide forum</a>. |
| </div> <div class="accordion"><div class="card collapsibleCard collapsed"><header class="card-header"><p class="card-header-title"> |
| What does "Unide" stand for? |
| </p> <a class="card-header-icon"><span class="icon"><i class="fa fa-angle-up"></i></span></a></header> <div style="display:none"><div class="card-content"> <div>The projects name is derived from understand industry devices. Other ideas like connect industry machines turned out to have meanings in foreign languages or being trademarked already.<br>Regarding the logo: Unide and Production Performance Management Protocol's goal is to enable you to connect machines and receive their measurements / alerts. The logo represents that. It has you ('<i>U</i>') highlighted and connects to rings. As a side note, we found that the words almost look like <i>you-nice</i>.</div></div></div></div><div class="card collapsibleCard collapsed"><header class="card-header"><p class="card-header-title"> |
| What's the difference between Unide and the Production Performance Management Protocol? |
| </p> <a class="card-header-icon"><span class="icon"><i class="fa fa-angle-up"></i></span></a></header> <div style="display:none"><div class="card-content"> <div>The Production Performance Mangement Protocol (PPMP) is the name of the structure of the <a href="specification/">payload</a> whereas Unide is the project that aims to provide sample implementations and further development of this protocol in and with the Eclipse Open Source community. Nevertheless, the Production Performance Management Protocol is an open suggestion, and everyone is welcome to using it, even without contributing to the Unide project.</div></div></div></div><div class="card collapsibleCard collapsed"><header class="card-header"><p class="card-header-title"> |
| Why introducing another industry protocol? |
| </p> <a class="card-header-icon"><span class="icon"><i class="fa fa-angle-up"></i></span></a></header> <div style="display:none"><div class="card-content"> <div>There are already plenty of transport protocols (REST, AMQP, etc.) available. The Production Performance Management Protocol aims to provide the very industry specific semantic structure for their payload. So it aims to complete such IoT transport infrastructure and bridge the gap to the manufacturing domain. OPC-DA/UA on the other hand covers full service oriented architecture, security concerns and information model, which makes it more complex and costly to implement and operate. In some use cases, this is not necessary.</div></div></div></div><div class="card collapsibleCard collapsed"><header class="card-header"><p class="card-header-title"> |
| Why have you choosen JSON as syntax? |
| </p> <a class="card-header-icon"><span class="icon"><i class="fa fa-angle-up"></i></span></a></header> <div style="display:none"><div class="card-content"> <div>JSON is a good fit regarding understandability and size. Having a structured and comprehensible basis is the first step for acceptance in the industry. In the spirit of Donald E. Knuth ("<a href="http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.103.6084"><i>premature optimization is the root of all evil</i></a>"), further compacting is possible in a later stage.</div></div></div></div><div class="card collapsibleCard collapsed"><header class="card-header"><p class="card-header-title"> |
| Why are time and measurement points separated in multiple arrays? |
| </p> <a class="card-header-icon"><span class="icon"><i class="fa fa-angle-up"></i></span></a></header> <div style="display:none"><div class="card-content"> <div>We have discussed multiple options for <a href="specification">series</a>: having an array of<br>tupels (<code>[[0, 23.34],[...],...]</code>),<br>plain objects (<code>[{time: 0, temperature: 23.34}, {...}...]</code>),<br>objects with time as key (<code>{ "0": [23.34,...],...}</code>) and other.<br>When parsing, we had to recognize, that unsigned long int for time and floating point measurements are of different types. Also, all former variants are more verbose due to additional brackets, commas or quotation marks. We believe that the current version is a good compromise between readability and structure.</div></div></div></div><div class="card collapsibleCard collapsed"><header class="card-header"><p class="card-header-title"> |
| I'm interested in Unide/Production Performance Management Protocol. How can I contribute? |
| </p> <a class="card-header-icon"><span class="icon"><i class="fa fa-angle-up"></i></span></a></header> <div style="display:none"><div class="card-content"> <div>The first goal of Unide is to provide sample client/server implementations of the Production Performance Management Protocol. Secondly, we're looking forward to improving the Production Performance Management Protocol in future versions together with the eclipse community.<br>If you want to contribute with source code, use cases or implementing it in your devices, let us know and discuss in the <a href="https://github.com/eclipse/unide">unide forum</a> or by forking / filing an issue on <a href="https://github.com/eclipse/unide">github</a>.</div></div></div></div><div class="card collapsibleCard collapsed"><header class="card-header"><p class="card-header-title"> |
| Why have you included content-spec uri, if that can also be expressed in the a REST url already? |
| </p> <a class="card-header-icon"><span class="icon"><i class="fa fa-angle-up"></i></span></a></header> <div style="display:none"><div class="card-content"> <div><a href="specification">content-spec</a> is included in the payload, because the Production Performance Management Protocol does not rely on a specific transport protocol (like REST).</div></div></div></div></div></div> <div class="sidebar column is-3 is-offset-1"><div class="recentPosts"><h4 class="subtitle is-5"> |
| Recent Posts |
| </h4> <ul><li><a href="/unide/blog/2019/11/26/Version-3-final"> |
| Protocol v3 final |
| </a></li><li><a href="/unide/blog/2019/3/1/Version-3"> |
| Protocol Version 3 release candidate |
| </a></li><li><a href="/unide/blog/2018/9/4/Template-for-PPMP-transformation"> |
| Use Cases: Template for transformation |
| </a></li><li><a href="/unide/blog/2018/3/26/Release-0.2.0"> |
| Unide 0.2.0 released |
| </a></li><li><a href="/unide/blog/2018/2/13/grinding-machine-scenario"> |
| Use Cases: Unide and the Eclipse Testbed |
| </a></li></ul></div> <div class="blogArchives"><h4 class="subtitle is-5"> |
| Blog Archives |
| </h4> <ul><li><a href="/unide/blog/2019/11"> |
| December 2019 |
| </a> |
| (1) |
| </li><li><a href="/unide/blog/2019/3"> |
| April 2019 |
| </a> |
| (1) |
| </li><li><a href="/unide/blog/2018/9"> |
| October 2018 |
| </a> |
| (1) |
| </li><li><a href="/unide/blog/2018/3"> |
| April 2018 |
| </a> |
| (1) |
| </li><li><a href="/unide/blog/2018/2"> |
| March 2018 |
| </a> |
| (2) |
| </li><li><a href="/unide/blog/2018/1"> |
| February 2018 |
| </a> |
| (1) |
| </li><li><a href="/unide/blog/2017/10"> |
| November 2017 |
| </a> |
| (2) |
| </li><li><a href="/unide/blog/2017/6"> |
| July 2017 |
| </a> |
| (2) |
| </li><li><a href="/unide/blog/2017/3"> |
| April 2017 |
| </a> |
| (1) |
| </li><li><a href="/unide/blog/2016/9"> |
| October 2016 |
| </a> |
| (4) |
| </li></ul></div></div></div></div> <footer class="footer"><div class="container"><div class="columns is-mobile is-multiline is-centered"><div class="column is-narrow"><a href="http://www.eclipse.org">Eclipse Foundation</a></div> <div class="column is-narrow"><a href="http://www.eclipse.org/legal/privacy.php">Privacy Policy</a></div> <div class="column is-narrow"><a href="http://www.eclipse.org/legal/termsofuse.php">Terms of Use</a></div> <div class="column is-narrow"><a href="http://www.eclipse.org/legal/copyright.php">Copyright Agent</a></div> <div class="column is-narrow"><a href="https://eclipse.org/security/">Security reports</a></div> <div class="column is-narrow"><a href="http://www.eclipse.org/legal/">Legal</a></div></div></div></footer></div></div></div><script>window.__NUXT__={layout:"sidebar",data:[{}],error:null,serverRendered:!0}</script><script src="/unide/files/a195a9468a7b0964153f.js" defer></script><script src="/unide/files/5559b707095db7adf400.js" defer></script><script src="/unide/files/c01c4654e10f48ab3d43.js" defer></script><script src="/unide/files/7267eda02aa7844877f4.js" defer></script> |
| </body> |
| </html> |
