什么是TSN?

TSN(时间敏感网络)是一组标准,用于指定基于以太网的通信。它保证了设备之间的确定性和有限的低延迟通信。

联系HMS

保持联系!我们的员工、分销商和合作伙伴都将竭诚为您服务!

质量对我们来说意味着什么

质量是HMS产品的核心。说到底,是我们产品的质量和功能使我们的业务得以持续发展。

为水和加工业提供阀门连接

现场总线控制系统能够远程控制执行阀,以帮助在后疫情时代实现工厂无需人工值守。

我们的主要环境目标: 2025年CO2 Net Positive

- Staffan Dahlström, President and CEO

人工智能(AI)

人工智能将帮助工业自动化变得更加有效。 来自机器的信息非常重要。 HMS可以为您提供帮助。

使您的远程连接水平更上一层楼!

Ewon Flexy允许您从您的机器数据中获得真正的价值以及安全的远程访问。

5G入门套件和测试解决方案

HMS提供入门套件和测试解决方案,使您能够在自己的站点上开始使用5G。

针对工厂的无线技术

WiFi、蓝牙、蜂窝、Zigbee——不同技术之间的区别和优势是什么?阅读更多内容并下载我们的白皮书。

下载有关使用最新无线技术进行工业通信的指南白皮书!

了解无线连接的业务优势。 有关不同无线技术以及何时使用它们的指南。

安全性白皮书

下载《工业设备的安全性》白皮书

使用Anybus建立连接

您对我们的Anybus产品有兴趣吗?直接进入产品页面了解更多信息。

Start IIoT - NOW !

让您的设备为IIoT做好准备---趋势,技术和Quick Wins

市场活动

在接下来的活动中与HMS见面

60分钟的培训

如何从你的Anybus和Ewon产品中获得最大的价值。现在就报名参加我们的新系列网络研讨会吧!

Intesis by HMS Networks

连接楼宇! Intesis产品将空调、供暖、照明等与楼宇自动化系统连接。

塑造互联的世界

HMS连接工业设备到周围的系统和互联网。

适用于系统集成商和最终用户的HMS解决方案

在工厂车间和建筑物中,HMS产品可帮助系统集成商为最终用户解决棘手的通信问题。

为机器制造商提供HMS解决方案

现代机器需要通信。HMS帮助机器制造商连接到周围的系统、工业网络和互联网。

IIoT 安全

让您的设备为IIoT做好准备-趋势、技术和Quick Wins

How to Prevent Pilot Purgatory and Ensure Time to Value

by Staff Writer | 7月 09, 2020

Prevent-Pilot-Purgatory

 

The heart of the promise of IoT lies in the realization of the value of the insights created from the data. Business owners implementing a Digital Transformation strategy continuously ask themselves, “Am I receiving critical information which is helping me to improve my business?” and “Am I getting the Return on Investment (ROI)?”.  Very often the answer is “Not yet”.  There are many reasons projects often get stuck in “Pilot Purgatory” – and in this article we will focus on the path to success – and how to ensure bright IoT ideas can reach their “Proof of Value” (POV) destination quickly.

Keep-It-Simple-Stupid

Use the Keep it Simple Stupid (K.I.S.S.) method to define the MVP, which should likely include:
  1. Crisply define Goals (MVP pilot requirements to achieve early success)
  2. Can it connect?
  3. Southbound and Northbound - Can data flow to destination?
  4. Is it Secure?
  5. Is it Robust? Can it Scale?
  6. Examples of IoT Pilot Technology and Business Goals

 

Define Success Criterion

Just like any project, IoT Pilots are subject to scope creep. And given the nature of many of the digital transformation objectives being more ‘art of possible’ – it is important to take a step back and create a Minimum Viable Product (MVP) approach which starts with only the most crucial requirements needed to ensure that the foundation of the system ‘works’. You can’t build a house without building the groundwork first. Furthermore, don’t forget to build into the pilot the “Why are we doing this” business goal. Without crisply defining technology goals that dovetail into business strategies, IoT projects are destined to die in the lab as a ‘science experiment’.

 

Defining Connectivity

The first challenge is simply ‘connecting’ existing machines/devices into a common data repository. Often in OT, devices live on ‘islands of information’ – that is they are completely autonomous, and not operating within the overall context of the organization. Basic data integration first requires that the information from the device is liberated from its proprietary heritage - often through an edge gateway with built in protocol conversion capabilities. Once interoperability is achieved on the ‘south bound’ (gateway to device (or sensor)) the problem gets much cleaner to solve. Common protocols like Modbus are typically much easier to convert to more IT friendly formats such as OPC – or even to altogether new protocol transport like MQTT – which are more ‘cloud friendly’. However, there a dozens of OT protocols and fieldbuses which require very specialized protocol conversion capabilities to support even more obscure formats such a PLC protocols.

Northbound connectivity is the potentially more complex half of the equation, as this is where the OT truly meets the IT. For example, is your destination a ‘cloud host’ like Microsoft Azure or Amazon Web Services (AWS)? Or perhaps some hybrid OT/IT IoT platforms like ThingWorx, Siemens Mindsphere, etc? Does your edge device handle the conversion from OT protocol to IT formats (like MQTT) and/or payloads over rest based web services?

 

Is it Secure?

A critical component of any IoT solution is to ensure that it adheres to your company's (and your customer’s) IT/Security guidelines, therefore comprehensive security policies are required to ensure success. When choosing a solution, equipment manufacturers need to follow best practices regarding cybersecurity. Taking guidance from common standards like ISO27002, IEC 62443-2-4 and NIST Cyber security Framework 1.1 is strongly recommended. This means choosing a solution that employs a defense-in-depth approach, so that no single point of failure will cause the solution to become compromised. Additionally, the way in which remote connectivity is achieved should be considered. Does the solution have crucial cyber security certifications like ISO27001? Has the solution undergone penetration testing? Is there an audit trail of connections? Is there control over when the solution is active and who can access it? The answer to all these questions needs to be yes.

 

Is it Robust and Scalable?

Sometimes a quickly assembled pilot might pass the “hello world” test, but that does not mean it is an indicator of production ready environments. It is important to truly stress test an application in different ‘real world’ environments and ensure that several stakeholders all can witness the same repeatable success. Often, it becomes valuable to actually exceed the limits of the design – to potentially learn about how the solution may outperform the specifications (or at least learn new boundary edges to avoid). And if failures happen, was it easy to update? How do you define easy?

Assuming you pass the robustness test, it is also important to understand if the solution can scale. One or two pilots might be manageable, but can the solution easily be amplified to 50 or 100? Defining availability requirements up front ensure that your customer are not disappointed when they finally trust you on that big order!

 

Examples of Succinct IoT Pilot Goals:

An example of defining the connectivity, robustness and scalability might be something like:

  • “Pilot just begin no later than July 15 and must be proven no later than August 31”
  • “Using Modbus TCP Connect to PLC and read 10 Tags (specify which) as 1 second interval and communicate to data historian (define app) via OPCUA over local network (define protocol/payload) and also Microsoft Azure IoT Hub (via MQTT) with data logging and HTML web page data value readout status on local on edge devices for period of 1 month without any failures”

 

Defining the Business Goal might look something like:

  • “Data values indicating equipment health must reliably communicate a ‘Red, Yellow, Green” status on customer site (define customer) with daily solution status update to key stakeholders for 1 week to prove our new 2020 Smart Machine Service initiative in time for Fall launch on Sept 15”

 

Summary

My grandfather always said, “Measure Twice, Cut Once” and that mantra holds true especially when creating new Proof of Value strategies. Create a great plan and make it realistic, and you can fail fast and learn - or potentially succeed fast and WIN quicker! To learn more on how HMS Networks can help you on this journey visit our digital transformation page:

Learn More Here

即将到来的活动

展会和活动

查看HMS将参加哪些活动和展会,了解我们的最新技术并与我们的专家交流。
客户感言

案例研究

当谈到我们给予的质量和奉献时,我们的客户为我们代言。查阅我们的成功案例。
探索媒体库

媒体库

浏览HMS Networks创建的视频,播客,图像,白皮书和电子书
查看广泛选择

工业物联网博客

及时了解工业通信和物联网领域的最新技术发展和趋势