Topics In Demand
Notification
New

No notification found.

Blog
How do You Manage Alerts from Your IIoT?

December 5, 2016

IOT

546

0

Rapid Adoption of IIoT by OEMs

Equipment manufacturers are rapidly adopting IIoT to offer asset health monitoring and predictive maintenance subscriptions for new sources after market revenue (reference IIoT enables New Revenue Sources for Equipment Manufacturers).  This technology adoption started with expensive million dollar plus equipment that is both complex and critical.  Now, those OEMs with equipment costing as low as $50,000 are adopting this approach for obtaining new sources of relatively high margin revenue.  Most of these initiatives apply to new products that will take time for development of an installed base and associated revenue.  However, others like Kaeser Kompressoren sell modules that can be added to existing equipment in its installed base.  This upgrading of existing installations allows for more rapid adoption and growth.

Capturing and Managing Alerts from Multiple Suppliers

Now, view this trend from the user’s perspective. As adoption grows, a large industrial site could have hundreds of suppliers with predictive maintenance services.  Currently, these alerts are often emails going to an individual without established procedures for:

  • Assessment and validation to remove false positives
  • Business processes to engage maintenance to repair
  • Governance for changes in personnel and processes

Communications of issues with maintenance is often ad-hoc. All too commonly, alerts become lost, and the equipment fails as predicted – just the outcome the subscription service is meant to prevent. As IIoT adoption with predictive maintenance services grows among OEMs, managing these alerts will become a significant new role for end-users.

https://industrial-iot.com/wp-content/uploads/2016/11/IIoT-WorkFlow.jpg

Business    

Business Processes for Converting IIoT Alerts into Maintenance Work OrdersIFS IoT Business Connector Platform

IFS recognized this issue and focused its IIoT initiative on managing alerts.  Please refer to Dick Slansky’s blog posting earlier this month for a description of the new IFS IoT Business Connector Platform.This new cloud service includes an “IoT Hub” to apply analytics to IIoT data using Microsoft Azure to generate alerts. However, it does not assume all of the alerts will be generated by this analytics platform.  The “IFS IoT Gateway” accepts alerts from other platforms.  The “IFS IoT Controller” helps the user rank, manage and covert chosen alerts into maintenance work orders in the enterprise asset management (EAM) or field service management (FSM) systems.

IFS.                                            

IFS IoT Business Connector ArchitectureRecommendations

The adoption of IIoT for predictive maintenance will lower unplanned downtime only if the alerts are acted upon.

  • To prevent lost alerts, users should establish business processes and governance
  • Suppliers of enterprise software should review their offering to assess the functions and workflows needed for managing alerts and converting the appropriate ones into work orders

“Reprinted with permission, original blog was posted here”. You may also visit here for more such insights on the digital transformation of industry.

About ARC Advisory Group (www.arcweb.com): Founded in 1986, ARC Advisory Group is a Boston based leading technology research and advisory firm for industry and infrastructure.

For further information or to provide feedback on this article, please contact sgandhi@arcweb.com

About the Author:

Ralph Rio

Vice President, Enterprise Software, ARC Advisory Group, Boston

Ralph’s focus areas include Enterprise Asset Management (EAM), Field Service Management (FSM), Global Service Providers (GSP), and 3D Scanning systems & software.


That the contents of third-party articles/blogs published here on the website, and the interpretation of all information in the article/blogs such as data, maps, numbers, opinions etc. displayed in the article/blogs and views or the opinions expressed within the content are solely of the author's; and do not reflect the opinions and beliefs of NASSCOM or its affiliates in any manner. NASSCOM does not take any liability w.r.t. content in any manner and will not be liable in any manner whatsoever for any kind of liability arising out of any act, error or omission. The contents of third-party article/blogs published, are provided solely as convenience; and the presence of these articles/blogs should not, under any circumstances, be considered as an endorsement of the contents by NASSCOM in any manner; and if you chose to access these articles/blogs , you do so at your own risk.


© Copyright nasscom. All Rights Reserved.