SAG_Twitter_MEME_Deliver_Value_880x440_Mar19The Industrial Internet of Things (IIoT) has almost infinite potential but implementations can prove challenging.

Two common hurdles include not having a clear starting point and being unable to ensure value is delivered quickly. Another common scenario that can lead to dire consequences is conducting IIoT in a vacuum.

For example, if a manufacturer selects an IIoT software platform for a particular need or use case but neglects to consider any other needs the IIoT platform could fulfill, expanding that IIoT implementation will prove exceptionally difficult. The truth is, successfully scaling any IIoT project requires continually expanding to incorporate other use cases and/or expanding single use cases horizontally across the entire organization.

Understandably, organizations often start with cloud-based IIoT software trials that promise quick delivery and easy implementations. However such an approach only deepens the IIoT vacuum problem, as it removes the critical step of thinking holistically and taking the time to carefully evaluate how the software will meet a range of criteria and long-term operational goals. That said, taking months or even years to engage in a more traditional software evaluation process and request for proposal is no longer realistic from a competitive standpoint, even if this approach does tend to encourage more holistic IIoT thinking.

To escape the IIoT vacuum scenario and implement software that supports both current operational needs and long-term business goals, organizations should adhere to the following three best practices:

  1. Evaluate all use cases.For any IIoT project to be successful, organizations must first determine their current and potential future use cases, as well as carefully consider their current IIoT platform capabilities.
  2. Determine supporting capabilities.After evaluating both current and potential IIoT use cases, organizations need to determine what specific capabilities are required in order to deliver those use cases. This could include capabilities such as device connectivity, analytics, application connectivity and/or partner connectivity requirements.
  3. Confirm what’s real.Once all use cases have been evaluated and relevant supporting capabilities have been determined, it’s time to confirm the capabilities of whatever IIoT platform is currently in place. This is a difficult yet critical step that must be completed objectively, as often many software capabilities have been promised but they’re not real.

Organizations that avoid the perennial IIoT vacuum stand to gain far more value from their implementations. Thinking more comprehensively allows them to scale their IIoT projects vertically and horizontally, which can increase existing investment returns and create additional returns as new projects are completed. Escaping the IIoT vacuum also allows organizations to devise stronger strategies around emerging IIoT capabilities and accurately forecast the real-world impact of their IIoT project on critical business processes.

Too many IIoT initiatives promise lofty strategic differentiation, impressive increased revenue figures and enticingly low operational costs, when in reality most result in comparatively smaller gains due to the structure or current capabilities of the organization in question.

Avoid falling victim to this widespread phenomenon by putting ample thought into the specific use cases, necessary capabilities and objective truths of your IIoT project before implementing a myriad of potentially conflicting solutions. In doing so, organizations can realize the full benefits of IIoT, while also gaining the ability to scale (up and/or out) their use of IIoT in iterations and reduce any potential implementation risks.

This article first appeared in Manufacturing.net.

Connected Manufacturing

Leave a comment

Search B2B

Most Popular Blog Posts

Subscribe

Connect with us!