<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Products, Platforms, Business &amp; Innovation in Industry 4.0/IIoT - Medium]]></title>
        <description><![CDATA[I write on product management, business models and innovations in Industry 4.0/Industrial Internet of Things - Medium]]></description>
        <link>https://medium.com/world-of-iot?source=rss----99efd32c5c03---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Products, Platforms, Business &amp;amp; Innovation in Industry 4.0/IIoT - Medium</title>
            <link>https://medium.com/world-of-iot?source=rss----99efd32c5c03---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 04:53:04 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/world-of-iot" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[(73) Lessons to learn from the failure of GE’s IoT Platform, Predix?]]></title>
            <link>https://medium.com/world-of-iot/73-lessons-to-learn-from-the-failure-of-ges-iot-platform-predix-3b3d20eccd42?source=rss----99efd32c5c03---4</link>
            <guid isPermaLink="false">https://medium.com/p/3b3d20eccd42</guid>
            <category><![CDATA[internet-of-things]]></category>
            <dc:creator><![CDATA[Ravi Kumar.]]></dc:creator>
            <pubDate>Thu, 08 Aug 2019 06:51:39 GMT</pubDate>
            <atom:updated>2019-07-31T06:14:46.036Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*vlIrtEFMofvUEJdh7lNp7g.jpeg" /></figure><p>GE announced a few days ago that it was selling off its digital assets business, which to a large extent refects the failure of its industrial IoT platform, Predix. In 2016, GE predicted to make $15 billion in software sales by 2020 of which Predix was expected to deliver half of the revenues. Very clearly, Predix hasn’t taken off as expected.</p><p>I have been reading up on Predix and here are some of the lessons I gathered from my research:</p><ul><li><strong>Deep pockets don’t guarantee success of a platform: </strong>Just because one is a huge manufacturer with dedicated customer base, it doesn’t guarantee success in building a platform of your own. Inspite of GE’s deep pockets and customer base, it did not guarantee Predix’s success.</li><li><strong>Supporting too many verticals:</strong> It’s difficult to build a software platform that works across many verticals. GE tried to be everything to everyone and built an all purpose platform for the wider industrial world, which was a diffused strategy.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*gA_6gKN9aRelIVJs" /></figure><ul><li><strong>Wrong partner ecosystem:</strong> <a href="https://www.linkedin.com/pulse/why-ge-predix-failed-parthasarathi-v/">According to Parthasarthi V</a>, y<em>our product needs to enable upmarket movement for your partners otherwise you will fail</em>. If you see the business models of [GE] partners, none of them had opportunity to move up-market by leveraging Predix. GE selected a wrong partner ecosystem. There is no incentives for its partners to <em>leverage Predix and move upmarket</em>. The existing partners can only invest to a certain extent and they certainly did by training their resources, building Predix apps but it was not enough for Predix. GE couldn’t run fast because its partners could not run faster</li><li><strong>Building their own cloud data center:</strong> GE committed a strategic blunder to create its own Predix cloud data center to handle the data being produced by industrial asset. It took GE some time to realize that they were competing with cloud giants like Amazon, Microsoft and Google.</li><li><strong>IoT platform must be developer friendly:</strong> Predix platform is known not to be developer friendly. An IoT platform should provide future looking monetizing opportunities. It should be caring for the needs of professional developers. A good platform provides accuracy, findability and readability of developer content. Developers also need knowledgeable support from the community.</li><li><strong>Not transitioning from product mindset to service mindset: </strong>According to Dima Tokar, co-founder and head of research at IoT analyst MachNation, GE failed to transition from a product-centric company to a services-centric company. He said that the transformation requires not only an evolution of human capital, but also an evolution in company culture, sales incentive structure and much more.</li></ul><h4>Resources:</h4><ul><li><a href="https://www.channelnomics.com/channelnomics-us/news/3036862/ge-digital-assets-sale-highlights-struggles-of-iot-platform-predix">https://www.channelnomics.com/channelnomics-us/news/3036862/ge-digital-assets-sale-highlights-struggles-of-iot-platform-predix</a></li><li><a href="https://www.linkedin.com/pulse/why-ge-predix-failed-parthasarathi-v/">https://www.linkedin.com/pulse/why-ge-predix-failed-parthasarathi-v/</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3b3d20eccd42" width="1" height="1" alt=""><hr><p><a href="https://medium.com/world-of-iot/73-lessons-to-learn-from-the-failure-of-ges-iot-platform-predix-3b3d20eccd42">(73) Lessons to learn from the failure of GE’s IoT Platform, Predix?</a> was originally published in <a href="https://medium.com/world-of-iot">Products, Platforms, Business &amp; Innovation in Industry 4.0/IIoT</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[(74) As an IoT Platform, what should be the right balance of data computing between the Edge and…]]></title>
            <link>https://medium.com/world-of-iot/74-as-an-iot-platform-what-should-be-the-right-balance-of-data-computing-between-the-edge-and-8a845d96f2b5?source=rss----99efd32c5c03---4</link>
            <guid isPermaLink="false">https://medium.com/p/8a845d96f2b5</guid>
            <category><![CDATA[internet-of-things]]></category>
            <dc:creator><![CDATA[Ravi Kumar.]]></dc:creator>
            <pubDate>Thu, 08 Aug 2019 06:51:09 GMT</pubDate>
            <atom:updated>2019-07-31T06:14:59.655Z</atom:updated>
            <content:encoded><![CDATA[<h3>(74) As an IoT Platform, what should be the right balance of data computing between the Edge and the Cloud?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1022/1*STrUJDSgBCfalb2bDzx7Gw.png" /></figure><p>In this post, I am summarising some research I put in understanding what Edge strategy should be in an IIoT platform. I went about looking at how some of the prominent platforms of IIoT implementations deal with edge computing and how do they split the data processing burden between the cloud and the edge. Here’s what I found:</p><p>More and more enterprises are discovering that not all real time computing should be pushed to the cloud. There are multiple reasons:</p><ul><li>Security</li><li>Latency/performance</li><li>Cost — the more data is pushed to the cloud, the more you pay to the Cloud hosting providers.</li></ul><p>They are pushing more and more computing to the edge of their networks and gravitating towards a hybrid cloud strategy.</p><p>Here are some of the broad observations:</p><ul><li>On an average, only 15% of the data generated by machines needs to be sent to the cloud and made available to other systems. The other 85% needs to be aggregated and analyzed to determine how it can be made valuable. If all is being pushed to the cloud, its very costly when only a fraction of it is going to be put into use.</li><li>Some computing will always need to live at the edge, such as real-time processing, decision support, SCADA functions and more.</li><li>100% cloud adoption is not necessary and must only be utilized for non-real time workloads like post-processing analytics or planning.</li><li>Risk based use cases like condition monitoring of remote devices where operators need to act fast on critical issues and mitigate the situation. It could be too risky for the data to travel back to the data center, undergo analysis and direct actions back to the device.</li></ul><p>Cloud would suit more to support planning and trend-spotting by collecting metrics from all the remote machines and periodically sending them to the data center for aggregation and analysis.</p><p>There is another trend towards offering customers full on-premise solutions before the customers can trust the system. Here’s what the customers state:</p><p><em>“We will only start this journey with you if you can put all the infrastructure we need on our premises, isolated from the internet, so we can be assured of security, of governance, of adequate latency for decision making,”</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/0*zULjGEVph88nA_mg" /></figure><blockquote><strong>Verdict: Hybrid Cloud strategy is a must have for all IIoT platforms with 60–70% of processing, transactions and data management happening on the edge.</strong></blockquote><p>In particular, Gartner in his magic quadrant report for IIoT believes that “By 2020, on-premises Internet of Things (IoT) platforms coupled with edge computing will account for up to 60% of industrial IoT (IIoT) analytics, up from less than 10% today.”</p><h4>All big cloud providers are offering edge solutions</h4><p>Edge is going to be the future is validated by all the big cloud providers who have begun offering edge solutions. Microsoft, Amazon and Google delivering edge products is a testament to the reality of Edge offerings.</p><ul><li><strong>Azure IoT Edge:</strong></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/900/0*fP8eSz_n_TOzAuxk" /></figure><p>Azure IoT Edge extends cloud intelligence and analytics to edge devices — Azure IoT Edge is a fully managed service that delivers cloud intelligence locally by deploying and running artificial intelligence (AI), Azure services, and custom logic directly on cross-platform IoT devices.Watch this video on Azure Stack for Edge: <a href="https://www.youtube.com/watch?v=c6EutwJHecc">https://www.youtube.com/watch?v=c6EutwJHecc</a></p><ul><li><strong>Amazon Greengrass and Snowball Edge</strong></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/638/0*XK9qJZqH4ujYE6Zy" /></figure><p>Here’s what the press release of Amazon Snowball Edge read:</p><p><em>“Amazon’s AWS cloud service </em><a href="http://e.businessinsider.com/click/13907969.2/aHR0cHM6Ly9hd3MuYW1hem9uLmNvbS9ibG9ncy9hd3MvbmV3LWVjMi1jb21wdXRlLWluc3RhbmNlcy1mb3ItYXdzLXNub3diYWxsLWVkZ2Uv/5adde55340f86675182a51c9B3a8fa4bb"><em>announced</em></a><em> that it is bringing the full cloud computing capabilities of its Elastic Compute Cloud (EC2) service to its Snowball Edge system, in a move that will create a powerful edge computing option for remote locations and factory floors. This new capability will give AWS users a more feature-rich local computing environment that they can leverage to cut down on processing delays, as well as to reduce the amount of data they need to transmit to the cloud for storage.”</em></p><ul><li><strong>Google IoT Edge</strong></li></ul><p>Here’s what the press release for Google IoT Edge:</p><p><em>“Cloud IoT Edge extends Google Cloud’s powerful data processing and machine learning to billions of edge devices, such as robotic arms, wind turbines, and oil rigs, so they can act on the data from their sensors in real time and predict outcomes locally. Cloud IoT Edge can run on </em><a href="https://developer.android.com/things/"><em>Android Things</em></a><em> or Linux-based operating systems.”</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*lVPgVoTtPc83inpj" /></figure><p>Share your thoughts and comments on what you think should be the Edge strategy for an IIoT platform.</p><h4>References:</h4><ul><li><a href="https://www.linkedin.com/pulse/tomorrows-digital-transformation-battles-fought-edge-bill-schmarzo/?lipi=urn%3Ali%3Apage%3Ad_flagship3_profile_view_base_post_details%3BDTk44qG3SPiFpJNMYppfWw%3D%3D">Tomorrow’s Digital Transformation Battles Will Be Fought at the Edge</a></li><li><a href="https://www.businessinsider.com/amazon-snowball-edge-aws-computing-ability-2018-7?IR=T">https://www.businessinsider.com/amazon-snowball-edge-aws-computing-ability-2018-7?IR=T</a></li><li><a href="https://cloud.google.com/iot-edge/">https://cloud.google.com/iot-edge/</a></li><li><a href="https://www.forbes.com/sites/janakirammsv/2018/07/01/5-reasons-why-azure-iot-edge-is-industrys-most-promising-edge-computing-platform/#5afce1e73249">https://www.forbes.com/sites/janakirammsv/2018/07/01/5-reasons-why-azure-iot-edge-is-industrys-most-promising-edge-computing-platform/#5afce1e73249</a></li><li><a href="https://uk.pcmag.com/tableau-desktop/116871/feature/how-the-iot-brings-billions-of-devices-closer-to-the-edge">https://uk.pcmag.com/tableau-desktop/116871/feature/how-the-iot-brings-billions-of-devices-closer-to-the-edge</a></li><li><a href="https://www.forbes.com/sites/forbestechcouncil/2018/08/21/three-myths-about-edge-computing/#7cbb8e873d52">https://www.forbes.com/sites/forbestechcouncil/2018/08/21/three-myths-about-edge-computing/#7cbb8e873d52</a></li><li><a href="https://searchmobilecomputing.techtarget.com/opinion/How-IoT-edge-devices-fit-into-unified-endpoint-management">https://searchmobilecomputing.techtarget.com/opinion/How-IoT-edge-devices-fit-into-unified-endpoint-management</a></li><li><a href="https://www.linkedin.com/pulse/why-iiot-revolution-happen-edge-cloud-kudzai-manditereza/?lipi=urn%3Ali%3Apage%3Ad_flagship3_profile_view_base_post_details%3BOSDYGuFdT3aZ0cWNDNGYlA%3D%3D">https://www.linkedin.com/pulse/why-iiot-revolution-happen-edge-cloud-kudzai-manditereza/?lipi=urn%3Ali%3Apage%3Ad_flagship3_profile_view_base_post_details%3BOSDYGuFdT3aZ0cWNDNGYlA%3D%3D</a></li><li><a href="https://www.iotcentral.io/blog/the-iot-architecture-at-the-edge">https://www.iotcentral.io/blog/the-iot-architecture-at-the-edge</a></li><li><a href="https://www.ptc.com/-/media/Files/PDFs/IoT/Foundational-Elements-of-an-IoT-Solution.pdf?la=en&amp;hash=A496A994897B2C7AC1AEC853DE4906E10A7AD03C">https://www.ptc.com/-/media/Files/PDFs/IoT/Foundational-Elements-of-an-IoT-Solution.pdf?la=en&amp;hash=A496A994897B2C7AC1AEC853DE4906E10A7AD03C</a></li><li><a href="https://internetofthingsagenda.techtarget.com/blog/IoT-Agenda/Myth-busting-Cloud-vs-edge-in-IIoT">https://internetofthingsagenda.techtarget.com/blog/IoT-Agenda/Myth-busting-Cloud-vs-edge-in-IIoT</a></li><li><a href="http://%20https//www.networkworld.com/article/3247801/internet-of-things/the-top-5-user-requirements-of-iot-edge-platforms.html">https://www.networkworld.com/article/3247801/internet-of-things/the-top-5-user-requirements-of-iot-edge-platforms.html</a></li><li><a href="https://wikibon.com/the-vital-role-of-edge-computing-in-the-internet-of-things/">https://wikibon.com/the-vital-role-of-edge-computing-in-the-internet-of-things/</a></li><li><a href="https://www.vanillaplus.com/2018/10/05/42404-instead-sending-data-cloud-not-send-cloud-edge/">https://www.vanillaplus.com/2018/10/05/42404-instead-sending-data-cloud-not-send-cloud-edge/</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8a845d96f2b5" width="1" height="1" alt=""><hr><p><a href="https://medium.com/world-of-iot/74-as-an-iot-platform-what-should-be-the-right-balance-of-data-computing-between-the-edge-and-8a845d96f2b5">(74) As an IoT Platform, what should be the right balance of data computing between the Edge and…</a> was originally published in <a href="https://medium.com/world-of-iot">Products, Platforms, Business &amp; Innovation in Industry 4.0/IIoT</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[(88) Making sense of SPS IPC Drives 2018, Germany]]></title>
            <link>https://medium.com/world-of-iot/88-making-sense-of-sps-ipc-drives-2018-germany-3040ef09d52f?source=rss----99efd32c5c03---4</link>
            <guid isPermaLink="false">https://medium.com/p/3040ef09d52f</guid>
            <category><![CDATA[internet-of-things]]></category>
            <dc:creator><![CDATA[Ravi Kumar.]]></dc:creator>
            <pubDate>Thu, 08 Aug 2019 06:50:21 GMT</pubDate>
            <atom:updated>2019-08-01T16:31:02.593Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/916/1*0Y8bO3TsQOUSUZ-vtgqJag.jpeg" /></figure><p>SPS IPC Drives is by far the biggest industrial automation show in Germany, in Europe, and possibly in the world. “SPS” is PLC (Programmable Logic Controller) in German, “IPC” stands for Industrial Process Control, and “Drives” are tools that control the speed of machinery. The mega fair comprises a dozen exhibition halls, each one practically a trade show in itself, filled with gigantic, colorful booths displaying robots, machines, and control system components. It’s where thousands of engineers, system integrators, machine builders and parts vendors gather for a massive show-and-tell featuring the latest and greatest — sensors, actuators, controllers, software, services and more.</p><p>Some stats from the fair:</p><ul><li>Exhibition space 136,000 sqm</li><li>Exhibitors 1,630</li><li>Visitors 65,700.</li></ul><p>Considering this was only my first visit, there was no way for me to be able to accurately grasp and make sense of the complete picture in the industry. This is my attempt through the lens of my limited experience and limited booths that I could visit.</p><h4>Why is the fair important for Industrial IoT platform players?</h4><p>The answer lies in the picture below that was taken from a talk at the Siemens hall.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*guDgnbvwvww51Mla" /></figure><p>The keyword in the slide above is “Knowledge Gap”. There are experts either on the Operational Technology (OT) side of IoT or there are experts on the Software/Cloud (IT) side of the IoT. There are only the rarest of rare who would have knowledge on both sides of the IoT stack. SPS IPC Drives is bridging that divide where you find conversations happening that criss-crosses both sides.</p><p><strong>Let’s try to segment the type of exhibitors in the fair…</strong></p><p>The exhibitors could be compartmentalized into the following groups:</p><ul><li>Drive systems and components</li><li>Mechanical infrastructure</li><li>Sensor Technology</li><li>Control Technology</li><li>IPCs</li><li>Software and IT in manufacturing</li><li>Interface Technology and power supplies</li><li>Low voltage switching devices</li><li>Human machine interface devices</li><li>Industrial Communication</li><li>Training and consulting</li><li>Functional groups</li></ul><p>Given so many exhibitors, I decided to focus on three areas:</p><ul><li>Industrial Communication</li><li>IIoT Platforms</li><li>Sensor and PLC technologies</li></ul><h4>Industrial Communication</h4><p>I must tell you that I had a few mental models and frames of reference to be able able to position every exhibitors rightly.</p><p>These two were my frames of reference:</p><ol><li>Market share of different industrial networking technologies</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*PYcU5L2xJkut6sfR" /></figure><p>2. The industrial automation pyramid</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*xHGyAB0drRd7hcqb" /></figure><p><strong>PI (Profibus/Profinet International )Booth</strong></p><p>I visited the PI booth to understand the latest and greatest they had to offer. PI is the parent organization for both Profinet and Profibus, which together constitues close to 24% of industrial communication market share, making it the largest automation community in a very fragmented market.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*QOoNRQqAOf99J_9d" /></figure><p><strong>I/O Link</strong></p><p>I attended a demo on I/O Link, a standard for or the communication with sensors and also actuators that has also grown exponentially in adoption.</p><p><strong>EtherCAT’s popularity growing</strong></p><p>In my interactions, I was told that EtherCAT is growing in popularity even though it has just 7% of market share. EtherCAT protocol was introduced by Beckhoff Automation and is growing in popularity especially in Robotic arms.</p><h4>Support for OPC UA and Time-Sensitive Networking (TSN) technology</h4><p>Time Sensitive Networking is the new technology that transforms standard Ethernet from an “I’ll get it there as soon as I can” communications technology to one that provides timing guarantees for mission-critical applications. Now, you can achieve an entirely new level of determinism.</p><p>Three of the largest industrial automation companies- Mitsubishi Electric , Rockwell Automation and Siemens — are joining hands for an open industrial network protocol with TSN. This group will standardize the so called “TSN Profile for Industrial Automation (TSN-IA Profile)” to ensure a multivendor converged TSN network approach for industrial automation where different applications and protocols like OPC UA, PROFINET, EtherNet/IP, etc. can share the same TSN network infrastructure.</p><p><a href="https://www.automationworld.com/article/industry-type/all/2019-year-industrial-network-protocol">https://www.automationworld.com/article/industry-type/all/2019-year-industrial-network-protocol</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*gr0Tzt4k98peH2gK" /></figure><h4>Industrial IoT Starter Boxes</h4><p>One trend that I noticed in the fair was the introduction of IoT starter boxes to get started quickly with cloud connectivity.</p><p><strong>Softing/HPE/Microsoft</strong></p><p>Softing for example offered a starter kit that was a product of an alliance between HPE, Softing and Microsoft Group.</p><p><a href="https://h22168.www2.hpe.com/us/en/partners/microsoft/iisk.aspx">https://h22168.www2.hpe.com/us/en/partners/microsoft/iisk.aspx</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*YoqXn40FvaZrTJ62" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*JgIj1f6hthe7mspD" /></figure><p>Here’s it what it offers:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*qu5JRBjIfDEkbFBV" /></figure><p><strong>com.tom Starter Kit</strong></p><p>The starter kit contains a Beck com.tom Edge Gateway supporting digital I/O and many industrial networks to connect to your industrial devices. Data gathered from the industrial devices can be processed via an easy-to-use web-based programming tool. Selected data will be automatically transferred into the com.tom IIoT portal, which provides a huge variety of functions for creation of dashboards, trend graphs and alarms.</p><p><a href="https://www.com-tom.de/download/other/fair-offer-starterkit_v1.pdf">https://www.com-tom.de/download/other/fair-offer-starterkit_v1.pdf</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*EVMtITxjermQFkOW" /></figure><h4>Industrial IoT Platforms</h4><h4>Siemens Mindsphere</h4><p>Siemens had an entire hall to itself and was impressive. I was more focused to understand the offerings from its Mindsphere platform. Interestingly, they don’t call themselves an IoT platform, but an Open IoT Operating System.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*nasNe0uy_NIrjzF0" /></figure><p>Here’s how their offerings value chain looks like with a wide array of partners and customers:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*b1YvivJL3RgMhKSZ" /></figure><p>This board reflected the customer base of Siemens Mindsphere:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*O2wqljbX-1Eunohl" /></figure><p>If you pay attention, my parent company TRUMPF is also one of their customers.</p><h4>Software AG/Cumulocity</h4><p>Pepperl + Fuchs, Software AG and Dell were showing a joint showcase in the fair. Software AG was also demoing their latest acquisition, Trendminer, a self-service analytics solution.</p><p><a href="https://www.trendminer.com/">https://www.trendminer.com/</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ZSXrd2dWFSNkHRDQ" /></figure><h4>Summary</h4><p>I provide a very limited perspective of the fair given the constraints of time and exposure I had. But there is no denying the fact that SPS IPC Drives is definitely the place to be to gauge and stay abreast with the latest industrial trends.</p><p>My maiden visit injected in me enough curiosity to delve deeper into the different aspects of this industry and present a more confident self in 2019. By the way, in 2019 the name SPS IPC Drives will rechristened into Smart Production Solutions (SPS).</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3040ef09d52f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/world-of-iot/88-making-sense-of-sps-ipc-drives-2018-germany-3040ef09d52f">(88) Making sense of SPS IPC Drives 2018, Germany</a> was originally published in <a href="https://medium.com/world-of-iot">Products, Platforms, Business &amp; Innovation in Industry 4.0/IIoT</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[(87) What do open source IoT platforms/projects like Mainflux and EdgeXFoundry mean?]]></title>
            <link>https://medium.com/world-of-iot/87-what-do-open-source-iot-platforms-projects-like-mainflux-and-edgexfoundry-mean-866eb829619a?source=rss----99efd32c5c03---4</link>
            <guid isPermaLink="false">https://medium.com/p/866eb829619a</guid>
            <category><![CDATA[internet-of-things]]></category>
            <dc:creator><![CDATA[Ravi Kumar.]]></dc:creator>
            <pubDate>Thu, 08 Aug 2019 06:49:50 GMT</pubDate>
            <atom:updated>2019-08-01T16:21:01.435Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*L43emKPCCpDCjdVVhUKsFA.png" /></figure><p>I had the privilege of interviewing <a href="https://www.linkedin.com/in/jankoisidorovic/">Janko Isidorovic</a>, CEO, Mainflux to understand what Open Source IoT Platforms/projects mean and why are they growing in popularity.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fw.soundcloud.com%2Fplayer%2F%3Furl%3Dhttps%253A%252F%252Fapi.soundcloud.com%252Ftracks%252F531054312%26show_artwork%3Dtrue&amp;url=https%3A%2F%2Fsoundcloud.com%2Fiiotmake%2Fjanko-isidorovic&amp;image=https%3A%2F%2Fi1.sndcdn.com%2Fartworks-000441148356-10z0ou-t500x500.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=soundcloud" width="800" height="166" frameborder="0" scrolling="no"><a href="https://medium.com/media/429f891c4dea7eb840f19b710e8ffcf9/href">https://medium.com/media/429f891c4dea7eb840f19b710e8ffcf9/href</a></iframe><h4>Q. What are open source IoT platforms? Why are they becoming popular?</h4><p>IoT is a complex domain that includes hardware, software, and telecommunication layer in between. When you create IoT products, you need to have expertise across all these layers — connectivity, software in cloud and on-premise, edge, cloud, ML, AI and more. There cannot be a single person who is an expert across all these layers. Therefore, the teams that need to build a smart IoT product needs to be big, which increases your time to market and makes it expensive.</p><p>With open-source IoT platforms, you are able to reduce the time-to-market by leveraging the expertise of the community. Mainflux is one such open source platform and EdgeX is edge based open source IoT platform. Hence, both are complimentary to each other.</p><blockquote>With open-source IoT platforms, you are able to reduce the time-to-market by leveraging the expertise of the community.</blockquote><p>Open-source IoT platforms enable small companies to compete with the big ones. So, instead of architecture, they can focus on devices and the applications to be used by the end customer.</p><blockquote>Open-source IoT platforms enable small companies to compete with the big ones. So, instead of thinking about how to build an architecture, they can focus on devices and the applications to be used by the end customer.</blockquote><h4>Q2. What is Mainflux?</h4><p>Of the entire IoT stack, Mainflux forms the part of the application layer and is solving issues in that layer. It tries to be agnostic to any deployment methods, to networks, to devices and applications you are building. It is is published under the very permissive Apache v2.0 license which guarantees patent-free software usable by the industry in proprietary and commercial products.</p><p>It is deployed either on cloud or on-premise as long as cloud supports containers. Due to the architecture and technology choices, Mainflux has a small footprint, which makes it easy to deploy on the edge if you need. You can deploy it in Raspberry Pi device and also scale to a multi-data center case with Kubernetes and Cassandra database.</p><p>Mainflux is not locked into single cloud and can be deployed into AWS or MS Azure or Google IoT or bare-metal cloud.</p><h4>Q3. What is the business model of Mainflux?</h4><p>At this point, we provide services around Mainflux and help implement Mainflux in their environment either as a product or in-company IoT implementations. We were profitable within the first year. With the growth in Mainflux adoption, we realized that the architecture choices that we made were modern and lean.</p><h4>Q4. Help us understand the Mainflux infrastructure stack?</h4><p>Architecture of Mainflux was similar to the architecture of EdgeXFoundry. Both platforms were using microservices, both were using docker and container and both had similar strategies to tackle modular and scalable plug and play architecture.</p><p>You don’t need to pay any license fees for any component of Mainflux.</p><p>We have four building blocks:</p><ol><li><strong>Device connectivity</strong></li></ol><ul><li>It supports HTTP, MQTT, WebSocket, and CoAP. We use NATS as a system event bus to bridge messages between these protocols.</li></ul><p><strong>2. Management</strong></p><ul><li>It manages users, things, and channels. Users can login to the system and manage the system. Things are both devices and applications. We realized that applications and devices are really similar in structure and behavior. So, we use single entity for both things and applications. Channels can be thought of as extended MQTT topics. Only devices and applications connected to same channel can talk to each other. This is a way of securing the systems so that unauthorized devices cannot listen to something they are not authorized.</li></ul><p><strong>3. Database</strong></p><ul><li>For telemetry, we support MongoDB, CassandraDB or InfluxDB, which are more popular. For POC, Grafana and InfluxDB is quick and easy for rich dashboard. For scalable systems for multiple data centres, we can use MongoDB or CassandraDB.</li></ul><p><strong>4. NGINX</strong></p><ul><li>Reverse proxy (NGINX) for security and load-balancing</li><li>We use NGINX out of the box because it is the only open source that supports both TCP and UDP proxy and also enables</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/0*JNL2Ga4axnI3ovoU" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1020/0*pbmIKCdr3Qluf9wk" /></figure><h4>Q5. Which are the most prominent open source IoT platforms available in the market?</h4><p>There are more than 450 IoT platforms in the market. Of the open source IoT platforms, the prominent ones are:</p><ul><li>ThingsBoard: <a href="https://thingsboard.io/">https://thingsboard.io/</a></li><li>Kaa: <a href="https://www.kaaproject.org/">https://www.kaaproject.org/</a></li></ul><p>However, they are all developed in Java. Mainflux, however is developed using Go language.</p><h4>Q6. What is Go language and what are its benefits?</h4><p>Go is a general purpose language developed by Google. In 2009, it had its first public introduction. Initially the EdgeX project was developed in Java but the footprint was pretty big and took too long to start the system. The codebase was then migrated from Java to Go and improvements in footprint were huge, close to 80%. While Java miscroservice startup takes 30 seconds, Go microservice takes 0.5 seconds. For scaling the system, Go language is efficient.</p><h4>Q7. What do you mean by footprint?</h4><p>The amount of memory that you need to have in the system in order to start the system up , the amount of hard drive, CPU efficiency all contributes to footprint.</p><h4>Other Questions:</h4><p>Q8. What is EdgeXFoundry Project? And what are its goals?</p><p><strong>Q9. Help us navigate the architecture of EdgeXFoundry Project?</strong></p><p><strong>Q10. How many open source IoT projects are active today?</strong></p><p><strong>Q11. You are the Chair of the Application Working Group of EdgeX Foundry Project. What is this working group all about and what are your responsibilities as a chair?</strong></p><p><strong>Q12. How many working groups are there in EdgeXFoundry?</strong></p><p><strong>Q13.Help us understand the difference between bodies like EdgeXFoundry and Industrial IoT Consortium.</strong></p><p><strong>Q14.To all IoT implementors, how should they decide whether to go open source way, or build themselves?</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=866eb829619a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/world-of-iot/87-what-do-open-source-iot-platforms-projects-like-mainflux-and-edgexfoundry-mean-866eb829619a">(87) What do open source IoT platforms/projects like Mainflux and EdgeXFoundry mean?</a> was originally published in <a href="https://medium.com/world-of-iot">Products, Platforms, Business &amp; Innovation in Industry 4.0/IIoT</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[(86) “How Data Moves in a Modern Factory”​ by Kudzai Manditereza, Product Architect and CEO…]]></title>
            <link>https://medium.com/world-of-iot/86-how-data-moves-in-a-modern-factory-by-kudzai-manditereza-product-architect-and-ceo-588e88b6ae18?source=rss----99efd32c5c03---4</link>
            <guid isPermaLink="false">https://medium.com/p/588e88b6ae18</guid>
            <category><![CDATA[internet-of-things]]></category>
            <dc:creator><![CDATA[Ravi Kumar.]]></dc:creator>
            <pubDate>Thu, 08 Aug 2019 06:49:10 GMT</pubDate>
            <atom:updated>2019-08-01T16:16:01.351Z</atom:updated>
            <content:encoded><![CDATA[<h3>(86) “How Data Moves in a Modern Factory”​ by Kudzai Manditereza, Product Architect and CEO, Cloresol</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*P-lJFdGVMQq0e0VJOVD4hA.jpeg" /></figure><p>I just finished recording an insightful podcast episode with Kudzai Manditereza, Product Architect and CEO of Cloresol, an IIoT based company in Johannesburg, South Africa. Kudzai writes a lot on technology subjects particularly Industrial IoT and Industry 4.0 and that too in a very interesting manner. And that is how I got to know of him — through his writings. So he began exploring the implementation of IIoT solutions and In 2015 he founded Cloresol, which he currently run as the CEO. And he has been focused on making Industrial IoT available to SME manufacturers and in that regard we’ve been Integrating various IIoT Systems for our clients and also providing OEM manufacturers with products that make their machines Industry 4.0 compatible.</p><p>The topic of our conversation was, How Data Moves in a Modern Factory.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fw.soundcloud.com%2Fplayer%2F%3Furl%3Dhttps%253A%252F%252Fapi.soundcloud.com%252Ftracks%252F520773249%26show_artwork%3Dtrue&amp;url=https%3A%2F%2Fsoundcloud.com%2Fiiotmake%2Fkudzai-manditereza&amp;image=http%3A%2F%2Fi1.sndcdn.com%2Fartworks-000429427272-54v4gy-t500x500.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=soundcloud" width="800" height="166" frameborder="0" scrolling="no"><a href="https://medium.com/media/5a805fc49b9039298da90ab5ec8b7f7a/href">https://medium.com/media/5a805fc49b9039298da90ab5ec8b7f7a/href</a></iframe><p>Kudzai has shared an infographic on the same topic on <a href="https://www.linkedin.com/pulse/how-data-moves-modern-factory-infographic-kudzai-manditereza/">his Linkedin blog</a> which had caught my attention. I approached him and asked if we could make that as a topic of our conversation.</p><p>Here is Kudzai’s infographic:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/0*NS3LG0PL-mAaa52g" /></figure><p>Here are the key insights of our conversation:</p><ul><li><strong>What is Cloresol’s business focus?</strong></li></ul><p>Cloresol’s business is focused towards digitally transforming small to medium manufacturing companies. That’s because Industrial IoT is often spoken about in the realms of large organizations but we want to shatter that myth.</p><p>We also building Industry 4.0 compatible products for OEMs because most OEMs use legacy systems that are not IIoT ready.</p><ul><li><strong>Help us understand the logical divisions of these three networks — Plant network, Operations network and Enterprise network?</strong></li></ul><p>Connectivity at the factory floor can be divided logically into three layers — connectivity at the end (plant network), operations connectivity and connectivity at the cloud (enterprise).</p><p>With edge or plant network, we are dealing with physical devices and components like motors and PLCs, Gateways, assembly line etc.</p><p>Operation network deals with various software that work in conjunction with the various devices in the factory floor.</p><ul><li><strong>What does a typical factory floor look like?</strong></li></ul><p>The equipment in a factory floor can be classified into different types depending on type of connectivity. Two wire protocols(I2C) machines, which could range from pumps, valves, blowers or temperature sensors. There could also be machines such as compressors, robotic arms, and various PLCs from different vendors.</p><p>In most cases, these PLCs are not designed to communicate with each other, especially when they are from different vendors. So most of these devices were not designed to work on Internet and were built for constrained environments.</p><p>There are other class of devices that were designed to work with open technologies and standards like OPC-UA. These devices can communicate with other devices in a plant.</p><ul><li><strong>How do you communicate with devices that have proprietary protocols?</strong></li></ul><p>It is a challenge to communicate with such devices and to get them to communicate, you need protocol drivers written for such devices on the Gateway that converts all of that information into a standard communication protocol like MQTT or OPC-UA.</p><ul><li><strong>Where is the next level of innovation going to come in the IIoT architectural stack in the future?</strong></li></ul><p>I have written a blog post on that already — <a href="https://www.linkedin.com/pulse/why-iiot-revolution-happen-edge-cloud-kudzai-manditereza/">https://www.linkedin.com/pulse/why-iiot-revolution-happen-edge-cloud-kudzai-manditereza/</a>. The next innovation is going to be at the Edge. Most processing will move away from the Cloud to the Edge. For argument’s sake what we perhaps need to establish before moving on is where or what is the edge?In short, the edge could be a sensor, pump, car, gateway. Any point where compute and storage could exist.</p><p>Sending terabytes of data to a central point for analysis and decision making and then sending it back down again will never work. It is not sustainable both in terms of bandwidth cost and increase in network latency. Time to insight and action can be tremendously accelerated only if machine learning models, server-less computing and lightweight databases are driven into edge devices.</p><blockquote>Sending terabytes of data to a central point for analysis and decision making and then sending it back down again will never work.</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=588e88b6ae18" width="1" height="1" alt=""><hr><p><a href="https://medium.com/world-of-iot/86-how-data-moves-in-a-modern-factory-by-kudzai-manditereza-product-architect-and-ceo-588e88b6ae18">(86) “How Data Moves in a Modern Factory”​ by Kudzai Manditereza, Product Architect and CEO…</a> was originally published in <a href="https://medium.com/world-of-iot">Products, Platforms, Business &amp; Innovation in Industry 4.0/IIoT</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[(84) Stages of IIoT Value Curve for the manufacturing industry]]></title>
            <link>https://medium.com/world-of-iot/84-stages-of-iiot-value-curve-for-the-manufacturing-industry-2566c3ffa970?source=rss----99efd32c5c03---4</link>
            <guid isPermaLink="false">https://medium.com/p/2566c3ffa970</guid>
            <category><![CDATA[internet-of-things]]></category>
            <dc:creator><![CDATA[Ravi Kumar.]]></dc:creator>
            <pubDate>Thu, 08 Aug 2019 06:48:17 GMT</pubDate>
            <atom:updated>2019-08-01T16:06:00.936Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/450/1*1xCZjKzbIfgHViRYEXS-Kg.jpeg" /></figure><p>A well-designed Industrial Internet of Things (IIoT) system helps manufacturers analyze all the raw plant information and convert it into business value, such as improving production yields, optimizing maintenance costs, maximizing line productivity, and tracking resource use in real time to meet business, production, and regulatory objectives.</p><p>IIoT adoption is a maturity progression where IoT companies realize increasing levels of benefit as they expand from basic machine connectivity to advanced approaches including analytics, automation, and edge computing.</p><p>In this post, I try to summarize my research on how most of the existing IIoT players navigate the stages of maturity.</p><p>To begin with, lets try to list out all the goals a factory owner hoped to benefit from digital transformation:</p><ul><li>Increase production yield</li><li>Efficiency</li><li>Quality</li><li>Compliance</li><li>Reduce unplanned downtime</li><li>Maximizing line efficiency and output</li><li>Tracking and automating real time resource usage</li><li>Preventive maintenance</li><li>Remote diagnostics</li><li>Asset tracking</li><li>Automatic fulfilment</li><li>Compliance monitoring</li><li>Strategic asset management</li><li>Production quality</li><li>Asset optimization</li><li>Improving safety</li><li>Cost reduction</li><li>Optimizing Overall Equipment Effectiveness (OEE)</li><li>Customization for customer experience</li><li>Increasing uptime and throughput in the plant and closely managing costs</li></ul><p>If you were to fulfil these benefits, which goal would you begin with and navigate next?</p><p>Jason Shepherd , CTO, IoT and Edge Computing says:</p><blockquote>“To get the power of IoT, you need to connect the physical world to the digital, with the evolution typically starting with real-time monitoring for visibility and then moving to optimization through analytics and eventually automation.”</blockquote><h4>Bsquare’s 5 Stage IoT Value Curve</h4><p>Bsquare, which is an IoT solutions provider defines five stages of IoT maturity:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Z_H9aW6iGzJqJwfr" /></figure><p><strong>Stage 1: Device Connectivity &amp; Data Forwarding</strong></p><p>Today, most factory equipment comes outfitted with myriad sensors to transmit a wide array of data. They also have a variety of connectivity options, from plug-in diagnostic reader ports to wireless modules, for delivering data to cloud-based devices. As a result, the average factory streams terabytes of production-relevant each month — ranging from motor operating temperatures to unit counts, product weights to conveyor speeds, motion-tolerance detection to raw materials usage, and much more.</p><p>Although IIoT-connected equipment provides the foundational first stage of such data collection and forwarding, merely gathering and storing data delivers little to no business benefit. <strong>At a minimum, monitoring and error alerts are required to begin to achieve value from the data.</strong></p><p><strong>Stage 2: Real-time monitoring</strong></p><p>Monitoring connected plant data begins to provide just-intime awareness of machine and production line conditions. Real-time operating parameters and fault codes can be visualized as graphics, charts, color-coded alerts, etc., on dashboards that are view-able on any cloud-enabled device. So factory owners at headquarters, operators in plant offices, and engineers on the floor can receive notifications when faults are detected, equipment failure is likely, inventory is low, or operating limits are exceeded. Teams can then take appropriate steps to adjust and re-mediate.</p><p>While these basic dashboard and monitoring solutions benefit human operators, they lack the sophisticated logic to detect the complex conditions and events frequently found in factory environments. They do, however, provide a starting point for manufacturers to examine and refine the business processes necessary to achieve their desired outcomes.</p><p><strong>Stage 3: Adaptive Data Analytics</strong></p><p>Analysis of intricate, multifaceted events, using multiple sources of data for context, is where IIoT really begins adding measurable business value. The best solutions use data discovery, machine learning, cluster analysis, and digital modeling to apply complex event processing and adaptive analytics to real-time and historical data from factory and complementary sources — providing detailed visibility across the manufacturing infrastructure. These insights allow plant operators, engineers, and technicians to proactively manage equipment health and optimize production. This reduces the likelihood of unexpected failures and related problems, like production delays and expensive repairs.</p><p>Factory data use cases:</p><ul><li><strong>Root cause analysis:</strong> Identify problems faster, with greater accuracy.</li><li><strong>Optimized repair workflows:</strong> Guide technicians to improve first-time repair rates.</li><li><strong>Condition-based maintenance: </strong>Service equipment based on actual usage, conditions, and performance</li></ul><p>This ability to detect, alert, and guide equipment maintenance provides high value to any manufacturer seeking to optimize production output. However, the sheer amount of data produced by multiple sources and across entire plants may overwhelm human operators and dashboard systems, limiting the scope of where analytics can provide business benefit. Some form of automation is also needed to help teams respond quickly and appropriately to fluctuating factory conditions.</p><h4>Stage 4: Automation</h4><p>Automating the wealth of insight and awareness provided by the adaptive data analytics in Stage 3 allows a manufacturer’s IIoT system to become progressively more intelligent, and capable of delivering greater business benefit. Dynamic rules-based logic can orchestrate complex actions across an organization, including service ticketing and inventory adjustment requests. Machine learning and sophisticated analytics also enhance an IIoT system’s intelligence. For example, it increases data collection and transmission upon detecting an anomalous condition on a production line. The system can then execute a series of automated steps to correct the error, or automatically adjust operating parameters to minimize damage while also notifying a technician of the issue and repair urgency.</p><p>In Stage 4, all IIoT processing activities are done over a separate cloud location that is accessible from any mobile or desktop device. Even greater automation can be achieved by moving these automated processing tasks onto the units themselves.</p><h4>Stage 5: Enhancing onboard intelligence</h4><p>By embedding the same intelligence and processing capabilities from Stage 4 directly into plant equipment, analytics and actions can be performed right at the network edge, rather than in a separate cloud location. Juxtaposing logic capabilities with source data aboard the machine (rather than transmitting the data from the machine to the logic tools in the cloud) eliminates any loss of accuracy from wireless transmission and conserves cloud data storage and network bandwidth. It also enables many other ways to work with the data and manipulate equipment directly, such as to apply real-time asset optimization and configuration to achieve greater quality control, or to automatically retool production lines.</p><p>Stage 5 provides maximum ROI and business benefit from predictive failure, data-driven diagnostics, and device optimization.</p><p>Most manufacturers start with less complex projects, such as enhanced visibility or tracking, and progress to more sophisticated processes that require automated or predictive workflows, according to IDC.</p><h4>Elevate’s 6 Stages of Maturity</h4><p>Elevat.IoT, an IoT company identifies 6 stages of IoT maturity as shown below</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*GeAE95MTcHhtT7mj" /></figure><p><strong>Stage 1: Unconnected</strong></p><p><strong>Stage 2: Connected</strong></p><p><strong>Stage 3: Serviceable</strong></p><p><strong>Stage 4: Intelligent</strong></p><p><strong>Stage 5: Optimized</strong></p><p><strong>Stage 6: Differentiated</strong></p><h4>PTC IoT Roadmap Value Curve</h4><p>PTC identifies the following value curve that all IoT companies should traverse towards.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*4zb2Zu7YIqksELeo" /></figure><p>The Value Chain is usually defined for a particular industry. For IoT as a technology (coming together of technologies rather), it starts with the (bottom up)</p><ol><li>Hardware layer : Sensors, Actuators, Chipsets, MEMS</li><li>Network layer: Both connectivity layer (PAN: Bluetooth, Zigbee, Wifi, etc), and telecom service layer (Wifi, GSM, 4G)</li><li>Platforms: Software platforms that enable IoT.</li><li>Cloud / Analytics / Application layer: to make store, visualize and make sense out of data.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*eMSCzY0HiqehFZOL" /></figure><p><strong>PTC came up with another value chain</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*lsAHrO6JUmmhrRln" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Pks8EY_LaEbeZ0zb" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*VUQBa4vHSBUdIkDW" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*kcYL60MZ0lCvFQ8U" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*MzZhMKb7tFKwq5PC" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*TV3xEggahE3CLV-L" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*VwOSjrNsQSExAlgg" /></figure><h4>Siemen’s Mindsphere’s Value Chain</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*z7K2a6OmtqvgONyy" /></figure><h4>Axeda defines 6 stages of maturity</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*9boWdilz01uscAXv" /></figure><h4>Level 1: Unconnected</h4><p><strong>Description.</strong> An unconnected organization is looking to make existing processes more efficient and drive higher levels of intelligence from the connected world. There are IoT opportunities in every industry because virtually all electronic and electro-mechanical products can be designed to automatically transmit information about status, performance, and usage, and can interact with people and other devices in real time.</p><p><strong>Requirements.</strong> At this level, understanding what’s possible and the underlying technologies is critical. Embedded software, network communications, device protocols, provisioning, and real-time data processing technologies combine with advanced Web Services, security, and data management to strain the skills of most IT organizations and development teams. Few companies have all these specialized people on staff, so IoT projects can get stalled or off track — if they are ever started at all. Increasingly, companies are coming to the conclusion that they should focus on their core competency, dismiss the idea of the internal “build,” and conduct an educated “buy” with faster, short-term ROI and time to market.</p><p><strong>Implementation.</strong> Level 1 starts with planning. The first step is “Getting connected” which is a broad term with different meanings depending upon the environment of the product and the economics of the solution. And while IoT isn’t new, the fundamentals of a connected product initiative are incredibly complex. Basic enablement, network connectivity, security, middleware services, cloud services, application development, and other device management functions are all needs that must be addressed when organizations seek to launch a connected product initiative. Axeda provides the features and functionality to help your organization connect, as well as the infrastructure to support an IoT environment with domain experts and proven cloud services. Axeda also offers Innovation Workshops which will help you define and launch your connected products program and help your key business and technical groups work together to develop a common point of view. After you describe your key business and IT objectives and challenges, Axeda subject matter experts collaborate with your team on the key elements of a IoT strategy, especially as they apply to your current environment. Innovation Workshops are offered at your business location, or at Axeda headquarters in Foxboro, Massachusetts.</p><h4>Level 2: Connected</h4><p><strong>Description.</strong> Once connected, organizations begin to realize a new means to generate growth and achieve a sustainable service position. Connected product services typically generate a recurring revenue stream, require less fixed capital, and provide potentially higher margins.</p><p><strong>Requirements. </strong>Connecting products to a network is not always trivial. Keeping up with device proliferation and the numbers and types of devices produced by manufacturers continues to grow rapidly Here, the focus should be on developing a solution that is resilient to change and allows applications to capitalize on, rather than be hindered by, product differences</p><p><strong>Implementation. </strong>Reaching Level 2 is accomplished by connecting a product to a network (internet, cellular or satellite) and enabling data transmission back to an enterprise server or system for processing. Axeda provides IoT Connectivity Services that include software agents and tool-kits that enable your organization to establish connectivity between products or assets and the Axeda Cloud, while allowing a choice of communication methods and hardware to suit the requirements of any IoT solution. As a result, your organization can connect to any product over any communication channel — cellular networks, the Internet, Wi-Fi, or satellite</p><h4>Level 3 — Serviceable</h4><p>Description. Each and every product requires some level of service and support. Service organizations are increasingly adopting remote service solutions to identify, diagnose, and resolve issues remotely. Axeda connected product management applications fit that need in helping to deliver proactive service to their range of devices — improving uptime, slashing service costs, and paving the way for value-added services based on the devices’ data. Requirements. Organizations require a cloud-based application platform and suite of tools to monitor assets remotely login and manage remote content. The solution would handle hosting, security, scalability and have flexible APIs, so that they are unencumbered by infrastructure and can focus on the value of the solution. Implementation. Reaching Level 3 is accomplished by enabling remote access and service. Axeda provides a secure and scalable cloud to process and store machine data and cloud-based applications to deliver remote service. The service includes web-based purpose-built connected product management applications for monitoring, remote login, desktop sharing, software management and remote content distribution.</p><h4>Level 4 — Intelligent</h4><p>Description. Here, the focus quickly turns to analyzing the data and developing user-facing tools and applications that facilitate data analysis, provide insights and improve business functions. With the right IoT reporting and BI solution, your company can run reports, query the data, create dashboards, or feed the data into your data warehouse and BI environments. Requirements. Many organizations including Service, Engineering, Finance, Compliance, QA, Product Management, and Sales need visibility into product usage, performance and behavior. The data from the connected products needs to organized and stored in a way that makes it is easy to report on and analyze. Implementation. Reaching Level 4 is accomplished by enabling reporting and analytics. With Axeda Service Intelligence, your organization can easily build and deliver ad-hoc queries, professional reports, and dashboards that articulate success metrics and KPIs, with reporting functionality that demonstrates the value of connected products. With a powerful business intelligence engine and easy-to-use report and dashboard building tools, your organization can understand the “what” and “why” of your IoT data.</p><h4>Level 5 — Optimized</h4><p>Description. Organizations who were early in bringing their products online are now realizing that the real “gold” in IoT is taking that data and integrating with enterprise systems such as CRM, ERP, PLM or data warehouses — optimizing critical business processes and essentially “IoT-izing” their business.</p><p>Requirements. IoT data must be made available to integrate with other systems. The IoT data must deliver additional value by combining information from connected products with information from other complementary sources and systems to enable people and processes to collaborate and extract even more value. For example, product data flowing through a CRM system can be sent to billing or into a supply chain management system — eliminating error-prone manual steps and providing new sales opportunities for consumable replenishment or warranty renewals. Quality assurance or product management can help enhance product features based on realworld data that shows usage patterns or equipment issues — improving customer satisfaction and streamlining beta programs. The valuable IoT product data — now unlocked — can also guide engineering efforts in building more reliable products with differentiating features driven by customer demand. Implementation. Axeda offers a framework to integrate with business systems by feeding IoT data into CRM/ERP/PLM systems to optimize business processes by enhancing service, billing, sales, inventory management, and product development. The framework includes web services APIs to read and write data as well as a standards-based message queue for asynchronous data transfers. Once integrated with Axeda, IoT data from connected assets, in collaboration with other enterprise systems, can provide visibility and automation across organizations not previously possible.</p><h4>Cumulocity’s (SoftwareAG) Value Chain</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*zAT5nAopTr7IkpxY" /></figure><h4>Value Chain from Site Machine</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*qpzBbG2H6612Emzg" /></figure><p>Resources:</p><p><a href="https://www.forbes.com/sites/adrianbridgwater/2018/05/15/software-ag-cumulocity-measures-three-steps-to-the-internet-of-things/#4be0327c2b88">https://www.forbes.com/sites/adrianbridgwater/2018/05/15/software-ag-cumulocity-measures-three-steps-to-the-internet-of-things/#4be0327c2b88</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2566c3ffa970" width="1" height="1" alt=""><hr><p><a href="https://medium.com/world-of-iot/84-stages-of-iiot-value-curve-for-the-manufacturing-industry-2566c3ffa970">(84) Stages of IIoT Value Curve for the manufacturing industry</a> was originally published in <a href="https://medium.com/world-of-iot">Products, Platforms, Business &amp; Innovation in Industry 4.0/IIoT</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[(79) What are the challenges in industrial device connectivity today?]]></title>
            <link>https://medium.com/world-of-iot/79-what-are-the-challenges-in-industrial-device-connectivity-today-a3da577cd19e?source=rss----99efd32c5c03---4</link>
            <guid isPermaLink="false">https://medium.com/p/a3da577cd19e</guid>
            <category><![CDATA[internet-of-things]]></category>
            <dc:creator><![CDATA[Ravi Kumar.]]></dc:creator>
            <pubDate>Thu, 08 Aug 2019 06:47:27 GMT</pubDate>
            <atom:updated>2019-07-31T06:16:48.440Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/459/1*eM98etJ6iDIgpLrqg5H7yw.png" /></figure><p>It was projected that by 2020, more than 50 billion devices would be connected to the cloud. But that goal doesn’t seem to be achievable as we approach 2019. And the biggest reason for this lack of pace is the protocol incompatibilities of different kinds of industrial machines in the world — especially from legacy machines that do not support standard connection protocols and need complicated integration, workarounds and configurations to connect them to cloud and draw data out of them. If any IoT platform ever has to have a competitive edge over other it has to have a fast and easy way to connect, which my German friends would say, schnell and einfach.</p><p>I spoke to the CEO of Omnio, Mikkel Sørensen to understand the topic better.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fw.soundcloud.com%2Fplayer%2F%3Furl%3Dhttps%253A%252F%252Fapi.soundcloud.com%252Ftracks%252F513211368%26show_artwork%3Dtrue&amp;url=https%3A%2F%2Fsoundcloud.com%2Fiiotmake%2Fmikkel-c-sorensen&amp;image=https%3A%2F%2Fi1.sndcdn.com%2Fartworks-000419456181-s5tqam-t500x500.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=soundcloud" width="800" height="166" frameborder="0" scrolling="no"><a href="https://medium.com/media/828aa23ea7898f117caa9383e52b21cb/href">https://medium.com/media/828aa23ea7898f117caa9383e52b21cb/href</a></iframe><p>Here are the key insights:</p><p><strong>Why is it so challenging to connect industrial devices than it is to connect consumer appliances easy?</strong></p><ul><li>In consumer appliances, you don’t have to know the exact model number and go online and find out how to write a driver and create a custom tool to write the driver. This is not necessary because the standards of communication were drafted in the 90s.</li><li><strong>Expensive to get communication standard:</strong> Industrial devices on the other hand were not built for connectivity in the first place. Manufacturers have used various kinds of protocols and there are many different kinds of standards. Therefore the connectivity features for every machine are very different from others. You can buy communication boards for bringing them to one standard but they are very very expensive.</li><li><strong>Unique data models: </strong>You can have two similar devices from the same vendor but you will have different data models. That means you need to understand each device data model in order to send it the right instructions to communicate with it and interpret the response. To extract information from all devices can take hours to days or weeks of effort. You then need to normalize the responses, which is painstaking exercise.</li><li><strong>Issues in data normalization:</strong> Different devices have different data models. Even though they may have similar data points, they will be different. For e.g, temperature can be measure in many different ways — Fahrenheit, Celsius, Kelvin etc . You need to normalize all of that before you can pass it to a IoT software application.</li><li><strong>IT tools are not compatible to OT tools:</strong> A lot of the IT tools don’t come from the automation world hence they don’t inherently understand the world of industrial automation. Hence, there are a lot of issues on usability and design.</li><li><strong>Cost on onboarding a device: </strong>There is a large cost of developing a driver for a device the first time and this effort can run into weeks for a single device. Also, the skill set needed for this is provided by an automation engineer.</li><li><strong>Hard to scale:</strong> Its hard to scale every time you connect to another device because you need to program a driver and need a few weeks to test it. This is why 70–80% of industrial IoT projects get stuck beyond the pilot stage.</li></ul><p><strong>What do you mean by data models?</strong></p><ul><li>For example, Machines with Modbus protocols have a list of data points that you can get from a pump. For example, you can the flow, the speed and pressure. And average device might have a couple of hundred data points. These data points will have a name for example, Flow. They will also have units, for eg, cubic meters per hour. It will also have an address from where you need to ask for inputs. You need to send the address to communicate from the machines. You then need to get the data back and analyze it.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a3da577cd19e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/world-of-iot/79-what-are-the-challenges-in-industrial-device-connectivity-today-a3da577cd19e">(79) What are the challenges in industrial device connectivity today?</a> was originally published in <a href="https://medium.com/world-of-iot">Products, Platforms, Business &amp; Innovation in Industry 4.0/IIoT</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[(83) Cracking the IIoT architectural code — Part 2]]></title>
            <link>https://medium.com/world-of-iot/83-cracking-the-iiot-architectural-code-part-2-b889ff7755f5?source=rss----99efd32c5c03---4</link>
            <guid isPermaLink="false">https://medium.com/p/b889ff7755f5</guid>
            <category><![CDATA[internet-of-things]]></category>
            <dc:creator><![CDATA[Ravi Kumar.]]></dc:creator>
            <pubDate>Thu, 08 Aug 2019 06:46:54 GMT</pubDate>
            <atom:updated>2019-07-31T06:36:37.612Z</atom:updated>
            <content:encoded><![CDATA[<h3>(83) Cracking the IIoT architectural code — Part 2</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kiQyBg8lJyzhjcQGEfBOkQ.png" /></figure><p>Continuing the topic around IIoT architecture from <a href="https://www.linkedin.com/pulse/cracking-iiot-architectural-code-part-1-ravi-kumar-sapata/">the earlier post</a>, I present to you an overview of IIoT architectural framework proposed by the Industrial Internet Consortium.</p><h4>Industrial Internet Architectural Framework from Industrial Internet Consortium</h4><p>IIC has published an Industrial Internet Reference Architecture as a guidance to the industry at large and caters to architects, business leaders and IIoT implementors.</p><p>The functional domain in an IIoT architecture is divided into the following:</p><ul><li>Control domain</li><li>Operations domain</li><li>Information</li><li>Application</li><li>Business</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/846/0*A2HU4XoPMT3u-QIB" /></figure><p>Controls, coordination and orchestration exercised from each of the functional domains have different granularities and run on different levels. As it moves up in the functional domains, the coarseness of the interactions increases, their cycle becomes longer and the scope of impact likely becomes larger. Correspondingly, as the information moves up in the functional domains, the scope of the information becomes broader and richer, new information can be derived, and new intelligence may emerge in the larger contexts.</p><h4><strong>Control Domain</strong></h4><p>The control domain represents the collection of functions that are performed by industrial control systems. The core of these functions comprises fine-grained closed-loops, reading data from sensors (“sense” in the figure), applying rules and logic, and exercising control over the physical system through actuators (“actuation”). Both accuracy and resolution in timing is usually critical. Simple examples of functional components in this domain include a control room in electricity utility plant, control units in a wind-turbine, and control units in autonomous vehicles.</p><p>The control domain comprises a set of common functions, as shown in the diagram below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*nY3NavFTc_appjXc" /></figure><ul><li><strong>Sensing:</strong> It is the function that reads sensor data from sensors. Its implementation spans hardware, firmware, device drivers and software elements.</li><li><strong>Actuation :</strong> It is the function that writes data and control signals to an actuator to enact the actuation. Its implementation spans hardware, firmware, device drivers and software elements</li><li><strong>Communication:</strong> Connects sensors, actuators, controllers, gateways and other edge systems. The communication mechanisms take different forms, such as a bus (local to an underlying system platform or remote), or networked architecture (hierarchical, hubs and spokes, meshed, point to-point), some statically configured and others dynamically.</li><li><strong>Entity Abstraction: </strong>provides an abstraction of scores of sensors and actuators, peer controllers and systems in the next higher tiers, and expresses relationships between them.</li><li><strong>Modeling:</strong> deals with understanding the states, conditions and behaviors of the systems under control and those of peer systems by interpreting and correlating data gathered from sensors and peer systems.</li><li><strong>Asset Management:</strong> Enables operations management of the control systems including system onboarding, configuration, policy, system, software/firmware updates and other lifecycle management operations.</li><li><strong>Executor:</strong> Executes control logic to the understanding of the states, conditions and behavior of the system under control and its environment in accordance with control objectives. The control objectives may be programmed or otherwise set by static configuration, be dynamic under the authority of local autonomy, or be advised dynamically by systems at higher tiers.</li></ul><h4>Operations Domain</h4><p>The operations domain represents the collection of functions responsible for the provisioning, management, monitoring and optimization of the systems in the control domain.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/798/0*g_mRt2W496E7QVkr" /></figure><ul><li><strong>Provisioning and Deployment </strong>consists of a set of functions required to configure, onboard, register, and track assets, and to deploy and retire assets from operations. These functions must be able to provision and bring assets online remotely, securely and at scale. They must be able to communicate with them at the asset level as well as the fleet level, given the harsh, dynamic and remote environments common in industrial contexts.</li><li><strong>Management</strong> consists of a set of functions that enable assets management centers to issue a suite of management commands to the control systems, and from the control systems to the assets in which the control systems are installed, and in the reverse direction enable the control systems and the assets to respond to these commands. For this, many of the legacy “dumb” assets need to be retrofitted to have compute, storage and connectivity capabilities.</li><li><strong>Monitoring and Diagnostics</strong> consists of functions that enable the detection and prediction of occurrences of problems. It is responsible for real-time monitoring of asset key performance indicators, collecting and processing asset health data with intelligence so that it can diagnose the real cause of a problem, and then alerting on abnormal conditions and deviations. This set of functions should assist operations and maintenance personnel to reduce the response time between detecting and addressing a problem.</li><li><strong>Prognostics</strong> consists of the set of functions that serves as a predictive analytics engine of the IIoT systems. It relies on historical data of asset operation and performance, engineering and physics properties of assets, and modeling information. The main goal is to is to identify potential issues before they occur and provide recommendations on their mitigation.</li><li><strong>Optimization</strong> consists of a set of functions that improves asset reliability and performance, reduces energy consumption, and increase availability and output in correspondence to how the assets are used. It helps to ensure assets operating at their peak efficiency by identifying production losses and inefficiencies. This process should be automated, as much as it is feasible, in order to avoid potential inaccuracies and inconsistencies.</li></ul><p>At this level, this set of functions should support major automation and analytics features including:</p><ul><li>automated data collection, processing and validation,</li><li>the ability to capture and identify major events, such as downtime, delay and</li><li>the ability to analyze and assign causes for known problems.</li></ul><h4>Information Domain</h4><p>The information domain represents the collection of functions for gathering data from various domains, most significantly from the control domain, and transforming, persisting, and modeling or analyzing those data to acquire high-level intelligence about the overall system.1 The data collection and analysis functions in this domain are complementary to those implemented in the control domain. In the control domain, these functions participate directly in the immediate control of the physical systems whereas in the information domain they are for aiding decision-making, optimization of system-wide operations and improving the system models over the long term. Components implementing these functions may or may not be co-located with their counterparts in the control domain. They may be deployed in building closets, in factory control rooms, in corporate data-centers, or in the cloud as a service.</p><p>Example: Optimizing the electricity generation level of a plant or a generator based on the condition of the facility, fuel cost and electricity price. Changing the route of a fleet of freight trucks based on weather, traffic and the condition of the goods in the trucks. Changing the output of an automated production plant based on condition of the facility, energy and material cost, demand patterns and logistic. Changing the temperature set-point of a boiler based on energy cost, weather condition and usage pattern.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/846/0*K8z4jxeG7VCOSQEP" /></figure><ul><li><strong>Data</strong> consists of functions for:</li></ul><p>ingesting sensor and operation state data from all domains,  quality-of-data processing (data cleansing, filtering, de-duplication, etc.),  syntactical transformation (e.g., format and value normalization),  semantic transformation (semantic assignment, context injection and other data augmentation processing based on metadata (e.g. provisioning data from the Operations Domain) and other collaborating data set,  data persistence and storage (e.g. for batch analysis) and  data distribution (e.g. for streaming analytic processing).</p><ul><li><strong>Analytics </strong>encapsulates a set of functions for data modeling, analytics and other advanced data processing, such as rule engines. The analytic functions may be done in online/streaming or offline/batch modes. In the streaming mode, events and alerts may be generated and fed into functions in the application domains. In the batch mode, the outcome of analysis may be provided to the business domain for planning or persisted as information for other applications</li></ul><h4>Application Domain</h4><p>The application domain represents the collection of functions implementing application logic that realizes specific business functionalities. Functions in this domain apply application logic, rules and models at a coarse-grained, high level for optimization in a global scope. They do not maintain low-level continuing operations, as these are delegated to functions in the control domain that must maintain local rules and models in the event of connectivity loss. Requests to the control domain from the application domain are advisory so as not to violate safety, security, or other operational constraints.</p><ul><li><strong>Logics and Rules</strong> comprises logics (rules, models, engines, activity flows, etc.) implementing specific functionality that is required for the use case under consideration. It is expected that there are great variations in these functions in both its contents and its constructs among the use cases.</li><li><strong>APIs and UI </strong>represent a set of functions that an application exposes its functionalities as APIs for other applications to consume, or human user interface enabling human interactions with the application.</li></ul><h4>Business Domain</h4><p>The business domain functions enable end-to-end operations of the industrial internet of things systems by integrating them with traditional or new types of industrial internet systems specific business functions including those supporting business processes and procedural activities. Examples of these business functions include Enterprise Resource Planning (ERP), Customer Relationship Management (CRM), Product Lifecycle Management (PLM), Manufacturing Execution System (MES), Human Resource Management (HRM), asset management, service lifecycle management, billing and payment, work planning and scheduling systems.</p><p>Example: A predictive maintenance service for an oil-rig may have an application that forecasts failures in the field. To do so, it may require a resource planning system to ensure the required parts are available and reserved, and it may need to connect to internal or partner’s service work schedule system and logistics management system, as well as the customer’s, to schedule the field service.</p><p>Reference architecture proposed by IIC:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*amVAiHCldLZF52D8" /></figure><p><strong>Edge Tier: </strong>The edge tier collects data from the edge nodes, using the proximity network. The architectural characteristics of this tier, including the breadth of distribution, location, governance scope and the nature of the proximity network, vary depending on the specific use cases.</p><p><strong>Platform Tier:</strong> The platform tier receives, processes and forwards control commands from the enterprise tier to the edge tier. It consolidates processes and analyzes data flows from the edge tier and other tiers. It provides management functions for devices and assets. It also offers non-domain specific services such as data query and analytics.</p><p><strong>Enterprise Tier:</strong> The enterprise tier implements domain-specific applications, decision support systems and provides interfaces to end-users including operation specialists. The enterprise tier receives data flows from the edge and platform tier. It also issues control commands to the platform tier and edge tier.</p><p>The architecture below maps, functional and reference together:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*CC2VS6CRTmxfowWX" /></figure><p>From the tier and domain perspective, the edge tier implements most of the control domain; the platform tier most of the information and operations domains; the enterprise tier most of the application and business domains. This mapping demonstrates a simple functional partitioning across tiers.</p><ul><li>References: <a href="https://www.iiconsortium.org/IIC_PUB_G1_V1.80_2017-01-31.pdf">https://www.iiconsortium.org/IIC_PUB_G1_V1.80_2017-01-31.pdf</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b889ff7755f5" width="1" height="1" alt=""><hr><p><a href="https://medium.com/world-of-iot/83-cracking-the-iiot-architectural-code-part-2-b889ff7755f5">(83) Cracking the IIoT architectural code — Part 2</a> was originally published in <a href="https://medium.com/world-of-iot">Products, Platforms, Business &amp; Innovation in Industry 4.0/IIoT</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[(82) Cracking the IIoT architectural code — Part 1]]></title>
            <link>https://medium.com/world-of-iot/82-cracking-the-iiot-architectural-code-part-1-304ee289a1c5?source=rss----99efd32c5c03---4</link>
            <guid isPermaLink="false">https://medium.com/p/304ee289a1c5</guid>
            <category><![CDATA[internet-of-things]]></category>
            <dc:creator><![CDATA[Ravi Kumar.]]></dc:creator>
            <pubDate>Thu, 08 Aug 2019 06:43:52 GMT</pubDate>
            <atom:updated>2019-07-31T06:29:27.154Z</atom:updated>
            <content:encoded><![CDATA[<h3>(82) Cracking the IIoT architectural code — Part 1</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kiQyBg8lJyzhjcQGEfBOkQ.png" /></figure><p>I have spent the last several weeks deep diving on architectural frameworks that define any IIoT implementation. The more I read up and interact with industry experts, the more I realised that there will be no one single architecture and no single system that will provide all of the capability that an industrial company will want.</p><p>An architecture will always be a combination of Edge, on-premise, centralized, and cloud systems for a company to be successful.</p><p>Here is my interpretation of an IIoT platform</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*CQKaTGIIYKTpH0Gg" /></figure><h4>Level 1: Sensors and Actuators</h4><p>This is the layer from where data is gathered from sensors and PLCs where the data is originally generated. A sensor is defined as device that can record a measurement about its physical environment. This measurement can then be turned into an electrical signal that is sent to a gateway for additional processing. Sensors have predefined roles in data gathering. Sensors can generate data like temperature, air quality, water levels etc in<strong> analog form.</strong> The more sensors you have, the more volume of data gets generated.</p><p><strong>Actuators</strong> intervene to change the physical conditions that generate the data. An actuator might, for example, shut off a power supply, adjust an air flow valve, or move a robotic arm in an assembly process.</p><h4>Level 2: Internet Gateway</h4><p>The data from the sensors starts in analog form. That data needs to be aggregated and converted into digital streams for further processing downstream.</p><p>Data acquisition systems (DAS) perform these data aggregation and conversion functions. The DAS connects to the sensor network, aggregates outputs, and performs the analog-to-digital conversion.</p><p>The Internet gateway receives the aggregated and digitized data and routes it over Wi-Fi, wired LANs, or the Internet, to Stage 3 systems for further processing to the cloud.</p><p>Stage 2 systems often sit in close proximity to the sensors and actuators. For example, a pump might contain a half-dozen sensors and actuators that feed data into a data aggregation device that also digitizes the data. This device might be physically attached to the pump. An adjacent gateway device or server would then process the data and forward it to the Stage 3 or Stage 4 systems.</p><h4>Level 3: Edge IT</h4><p>Once IoT data has been digitized and aggregated, it’s ready to cross into the IT layer. However, the data may require further processing before it enters the data center. This is where edge IT systems, which perform more analysis, come into play. Edge IT processing systems may be located in remote offices or other edge locations, but generally these sit in the facility or location where the sensors reside closer to the sensors.</p><p>Because IoT data can easily eat up network bandwidth and swamp your data center resources, it’s best to have systems at the edge capable of performing analytics as a way to lessen the burden on core IT infrastructure. You’d also face security concerns, storage issues, and delays processing the data.</p><p>With a staged approach, you can preprocess the data, generate meaningful results, and pass only those on. For example, rather than passing on raw vibration data for the pumps, you could aggregate and convert the data, analyze it, and send only projections as to when each device will fail or need service.</p><p>Here’s another example: You might use machine learning at the edge to scan for anomalies that identify impending maintenance problems that require immediate attention. Then you could use visualization technology to present that information using easy-to-understand dashboards, maps, or graphs. Highly integrated compute systems, such as hyper-converged infrastructure, are ideally suited to these tasks because they’re relatively fast, and easy to deploy and manage remotely.</p><h4>Level 4: The data center and the cloud</h4><p>Data that needs more in-depth processing, and where feedback doesn’t have to be immediate, gets forwarded to physical data center or cloud-based systems, where more powerful IT systems can analyze, manage, and securely store the data. It takes longer to get results when you wait until data reaches Stage 4, but you can execute a more in-depth analysis, as well as combine your sensor data with data from other sources for deeper insights.</p><p>The data is aggregated in a big data warehouse. It makes sense to add a data lake to the solution to accumulate all the data a company plans to use in the future and thus separate potentially useful data from the data with the already proved usefulness.</p><h4>Functional Architecture</h4><p>Machnation has attempted to create a functional IoT architecture for the industry, which looks a very promising reference guide.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*pb_VqVKZcP8sAd7L" /></figure><p>Here’s a quick summary of its eight functional categories:</p><ol><li><strong>Application: </strong>An application is any piece of contained logic either running on or directly integrated to an IoT platform. On-cloud and on-premises applications enable code-based control over IoT platform components, enriching the raw assets or data with customer-specific logic. An application can contain customer-, operator-, or administrator-facing user interfaces (UIs), or could function as a self-contained service, providing any type of relevant data or device manipulation.</li><li><strong>Access Control:</strong> Access control is the system of identity verification and permission management for all platform-connected elements including APIs, administrator or operator interfaces, devices, users, organizations, stored or in-transit data, or any other platform service.</li><li><strong>Analytics: </strong>Analytics refers to the ability of an administrator or operator to monitor both historical and real-time observations collected from platform-connected IoT devices. Analytics can include descriptive, predictive, and prescriptive components.</li><li><strong>Data Management:</strong> Data management is defined as the capabilities within an IoT platform to ingest, store, manage, and forward data received from platform-connected IoT devices.</li><li><strong>Device Management: </strong>Device management refers to the ability of a platform to provide lifecycle management functionality for connected devices, including device onboarding, deployment of software and firmware updates, and configuration of managed devices.</li><li><strong>Event Processing: </strong>Event processing refers to the ability of an IoT platform to execute actions or provide notifications based on administrator or operator configured rules or triggers.</li><li><strong>Integration:</strong> Integration is defined as the ability of an IoT platform to interface and share data with off-platform or third-party applications, services, or systems.</li><li><strong>Monitoring:</strong> Monitoring is defined as the ability of a platform to trigger events, evaluate device status, and follow ingested data streams. Platform capabilities for monitoring should include both aggregated and drill-down views, and typically include operator- or administrator-facing dashboards and other graphical interfaces.</li></ol><p>In the next post, I will continue the topic and present to you IIoT architectural framework proposed by the Industrial Internet Consortium</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=304ee289a1c5" width="1" height="1" alt=""><hr><p><a href="https://medium.com/world-of-iot/82-cracking-the-iiot-architectural-code-part-1-304ee289a1c5">(82) Cracking the IIoT architectural code — Part 1</a> was originally published in <a href="https://medium.com/world-of-iot">Products, Platforms, Business &amp; Innovation in Industry 4.0/IIoT</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[(89) Understanding Overall Equipment Effectiveness (OEE)]]></title>
            <link>https://medium.com/world-of-iot/89-understanding-overall-equipment-effectiveness-oee-43f30d49bb48?source=rss----99efd32c5c03---4</link>
            <guid isPermaLink="false">https://medium.com/p/43f30d49bb48</guid>
            <category><![CDATA[entrepreneurship]]></category>
            <dc:creator><![CDATA[Ravi Kumar.]]></dc:creator>
            <pubDate>Thu, 08 Aug 2019 06:42:56 GMT</pubDate>
            <atom:updated>2019-08-01T16:41:01.357Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*CetrhnPe2hCmCu3lQjdTqQ.png" /></figure><p>OEE as a term is very loosely used in in the industry and runs the risk of being misinterpreted. This post is a result of clarifying my own understanding of the term. During my research, I spoke to Joern Steinbeck who is the Founder/Managing Director at oee.ai and Managing Partner at Institute of Productivity, Achen.</p><p>Here are his thoughts:</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fw.soundcloud.com%2Fplayer%2F%3Furl%3Dhttps%253A%252F%252Fapi.soundcloud.com%252Ftracks%252F543981087%26show_artwork%3Dtrue&amp;url=https%3A%2F%2Fsoundcloud.com%2Fiiotmake%2Fjoern-steinbeck&amp;image=https%3A%2F%2Fi1.sndcdn.com%2Fartworks-000457411392-4zifd7-t500x500.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=soundcloud" width="800" height="166" frameborder="0" scrolling="no"><a href="https://medium.com/media/0b6e032e197e0a640893b7f8c181ef0e/href">https://medium.com/media/0b6e032e197e0a640893b7f8c181ef0e/href</a></iframe><h4>What is OEE?</h4><p>OEE is a globally accepted measure /KPI for machine productivity. This KPI answers if the machine is running at all, whether it is running in full speed and whether it produces the quality acceptable to the customer. It is measured in percentage. When you have a 100% OEE, you would produce with 100% availability, a 100% performance (desired speed), and 100% quality which means you don’t produce any faults and scrap.</p><p>OEE <em>assigns numerical value to improvement opportunity</em></p><p><strong>Where does this definition come from?</strong></p><p>This definition comes from <strong>Total Productive Maintenance (TPM)</strong> movement. In industry, total productive maintenance (TPM) is a system of maintaining and improving the integrity of production and quality systems through the machines, equipment, processes, and employees that add <a href="https://en.wikipedia.org/wiki/Business_value">business value</a> to an organization. The term <em>total productive maintenance</em> is attributed to Nippondenso, a company that created parts for Toyota. The main objective of TPM is to increase the <a href="https://en.wikipedia.org/wiki/Overall_equipment_effectiveness">Overall Equipment Effectiveness</a> (OEE) of plant equipment.</p><h4>Help us understand the three factors, Availability, Performance, and Quality with some examples?</h4><p>The three factors are best explained via the losses. The OEE calculation rolls the “6 big losses” of TPM into one number that represents the effective operating rate for a piece of equipment or synchronized line — in other words, the percent of time the equipment or line is operating effectively, or its <em>valuable operating time.</em> That translates to the percentage of product produced compared to what could have been produced in the scheduled time.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ROlonWKOH5tj3jdJ" /></figure><p>OEE has three factors which are multiplied to give one measure called OEE</p><p>It’s calculated like this:</p><p><strong>OEE (%) = Availability rate × Performance rate × Quality rate</strong></p><ul><li><strong>Availability rate: </strong>It is the percentage of time the machine is ready to produce, working properly, and not in the midst of changeovers or adjustments) = <em>Available time (scheduled operating time − downtime) ÷ Scheduled operating time.</em></li><li><strong>Performance rate:</strong> It is the ratio of output produced compared to a standard) <em>= Actual output ÷ Standard output.</em></li><li><strong>Quality rate:</strong> It is the ratio of good output compared to actual output)<em>= Right-first-time output ÷ Actual output.</em></li></ul><p><strong>EXAMPLE OEE CALCULATION</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1022/0*XssoodqcDUOz2vZj" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*hixTY7JI6hKhC4YV" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*F5SoxYIkvQjX-g6a" /></figure><p>Resources:</p><ul><li><a href="https://www.oee.com/">https://www.oee.com/</a></li><li><a href="https://www.industryweek.com/quality/oee-learn-how-use-it-right">https://www.industryweek.com/quality/oee-learn-how-use-it-right</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=43f30d49bb48" width="1" height="1" alt=""><hr><p><a href="https://medium.com/world-of-iot/89-understanding-overall-equipment-effectiveness-oee-43f30d49bb48">(89) Understanding Overall Equipment Effectiveness (OEE)</a> was originally published in <a href="https://medium.com/world-of-iot">Products, Platforms, Business &amp; Innovation in Industry 4.0/IIoT</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>