LSN - Life-cycle States Network

latest update: 2021-04-28   

Introduction

Below a mapping to Templates is shown of the 'Plant life-cycle model'.  This is done in three parts of that model: Process Design, Tag and Tag Classes, and Real World incl. Manufacturer.

Rationale

As already indicated in the topic about the Plant Life-cycle Model, this model applies to each plant item. That may sound overdone, but compare it to a life cycle of a human being:
  • Conception
  • Birth
  • Childhood
  • etc.
mixed with all sorts of interrelationships with other human beings, such as Marriage, Profession, etc. and with states, such as Education, Health, etc. That applies to each and every human being.

So the idea is that for each plant item (the detail of what the term 'plant item' entails is a (hopefully informed) business decision) the life-cycle states network (further referred to as LSN), as shown in this topic, applies.
Each of the numbered balloons represents a state in which the object of interest can be.

In many cases that does not mean that only one straightforward network from conceptional design to shredding will occur, because plant items can be used in more than one service, thereby creating links between LSN's.
That leads to branches in the network, which is fine as long as we maintain the logic of it.

Each node in the network has non-interrelationship information attributed to it, such as properties, materials, sizes, shapes, etc. This is depicted in the little diagram below:
                                                                                      

A good example where that rule is violated is the table TAG PHYSICAL CONNECTION in the CFIHOS data model, with the description:
"A physical connection between tags. This information is primarily used for mechanical completions." (if that 'used for' would be rephrased to 'used as a reference when reporting' then it is OK).
Those Tags are only connected on a P&ID and in a 3D model, that 'mechanical completion' implies a connection between two physical objects in the real world that are implementing those Tags.
The related template first models those two implementations and then the physical connection between them.

Is that important? Yes, in case you reliably want to integrate plant life-cycle information.
Is that table in the CFIHOS model hurtful? Not really for communications between humans, it is understood properly by insiders.
But it hurts for information integration and the resulting global interoperability when mapped one-to-one. That creates fake information for computers and non-insiders.

Data Access

An LSN has the advantage that data access between the states is predefined and predictable. For example: an engineer who is working on an energy savings plan can easily get access to the Heat & Material Balance information.
Or a maintenance engineer can easily get manufacturer's information. Or a mechanical engineer can easily get information about similar or identical equipment that already exists. Those data sets can be mapped to OWL-DL
and be used for reasoning / AI purposes.


Process Design

First boxes are inserted, where each box covers the objects in a template. The boxes overlap by definition.



Then a kind of 'exploded view' is created in which we add the applicable template names.



These templates are instantiated and interconnected, thus creating an information network. Normally these networks are combinations of declared object --- template ---- declared object --- template, etc.
There are only a few templates that refer to another template.



and finally a version where, for better readability, all templates have been replaced by an rfd:Property (relation):



Please be aware that templates are required in case you want to integrate life-cycle information.


Tag and Tag Classes

First boxes are inserted, where each box covers the objects in a template. The boxes overlap by definition.



Then a kind of 'exploded view' is created in which we add the applicable template names.



These templates are instantiated and interconnected, thus creating an information network.



and finally a version where, for better readability, all templates have been replaced by an rfd:Property (relation):


Please be aware that templates are required in case you want to integrate life-cycle information.


Real World incl. Manufacturer

First boxes are inserted, where each box covers the objects in a template. The boxes overlap by definition.



Then a kind of 'exploded view' is created in which we add the applicable template names.



And finally these templates are instantiated and interconnected, thus creating an information network.


and finally a version where, for better readability, all templates have been replaced by an rfd:Property (relation):



Please be aware that templates are required in case you want to integrate life-cycle information.