Asset Twin Blogs

Sameer Kalwani
Apr 2, 2019

Sameer Kalwani

Managing the Design of Asset Twins

In a prior blog post, I spoke about Element AssetHub at a high level, explaining the need for Asset Twins and why we need to CONNECT to existing data sources, MANAGE the building and operationalizing of Asset Twins, and easily SHARE the data about these Asset Twins so they can be used for a multitude of use cases.

One of the most critical pieces of this process is designing the right Asset Twin. Without the right operational data forming a consistent data model of what your instrumentation, equipment, and/or processes, you’ll be hamstrung to perform simple comparisons, let alone wide scale advanced analytical projects.

Read More

You’re Building the Wrong Twin!

Everyone is talking about Digital Transformation, Industrial Analytics, IoT, and Industry 4.0. Much of the discussion advocates a crawl, walk, run approach by taking on the low hanging fruit of smaller, limited use cases using Proof of Concepts (POCs). This typically requires a lot of data wrangling to be completed before the use case can even be executed. More often than not, these data wrangling activities enable just one use case. So when things change operationally, applications fail and they lack the scalability to be deployed enterprise-wide.

If you find yourself manually mapping data, building specialized integrations, or manipulating 40,000 row X 26,000 column spreadsheets then you need to consider whether the solution will scale across your organization and provide you with the runway that supports you as your operations and use cases change over time.

Read More