In a prior blog post, I spoke about Element Unify™ 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 are, you’ll be hamstrung to perform simple comparisons, let alone wide scale advanced analytical projects.
Before we talk about features of Asset Templates, it’s important to understand our perspective of what an Asset Template represents, and how we ensure that these models can be encoded in software. Asset Templates define a common standard for like-equipment, like-instrumentation, or like-processes. These are not templates of an entire plant or facility, nor are they templates that define the structure. What they are is the smallest unit of common data representations that you want to use as a basis of comparing like-things.
This means that the templates need to fulfill the following requirements:
Asset Templates define a common standard for like-equipment, like-instrumentation, or like-processes...the smallest unit of common data representations.
The emerging concepts of digital twins are designed to support consumer technologies or singular objects like wearables, smart home devices or wind turbines. To consistently model process or discrete manufacturing operations these simpler data models will not suffice. What’s needed are Asset Twins. Asset Twins target your operational challenges, acting as an information map that defines how production systems are related to each piece of instrumentation, equipment, or an entire process unit.
Element Unify approaches building Asset Twins from the ground up, ensuring industrial information can be encoded in standardized Asset Template models. Foundationally each template is a structured, graph-based data model. Having a graph-based data structure allows for us to create “has-a” relationships between templates (meaning that it supports nested templates), as well as “is-a” relationships between templates (meaning that it supports template inheritance).
Graph-based structures provide a lot of flexibility, but to enforce standardization it is important to have some standard schema. Within the graph resides a set of user-defined models that represent equipment, instrumentation, and processes - which is our Asset Template. These models allow for a rigid standard structure to be defined, and can also encode mathematical relationships between the collection of attributes that represent the Asset Template.
In addition to the graph model and the standardized template structure, we understand that the model keeps changing over time and that these models must be searchable. Enterprise level features like governance, version management, authorization, metadata search, standards adoption, and many other capabilities are at the core of what Element Unify offers in its ability to design Asset Templates.
With our approach out of the way, it makes sense to dive deeper into what Element Unify offers when it comes to designing the template for consistent Asset Twins. This is broken down into 4 areas below.
Part 2 discusses in detail how each area contributes to building Asset Twins.