The life cycle of pump P-101

latest update: 2015-03-18    


In this topic a sliver of the entire life cycle of pump P-101 will be coded, from Process Design to Maintenance.

The diagram from the topic Plant Lifecycle Model will be followed:

Plant Lifecycle Model


(click on the headings to see the code)

Process Design

On Sept. 16, 2011 the Process Engineer finished work on his design and, as a part of it, his software mapped the information that the Activity with tag "PUMPING-5" has two participants: the PUMP FUNCTION with tag "PUMP-5" and the PUMPED FLUID with tag "STRM-5".

The RATED VOLUME FLOW RATE was 1565 m3/hr and the DIFFERENTIAL HEAD 30 mH20.

Plant Design

On January 9, 2012 the instance of FunctionalPhysicalObject with tag number P-101 is declared and shown on P&ID VP-1234.

Detailed Engineering

On February 23, 2012 the Requirements Class for P-101, with tag CO_P-101, and the Stream are declared, and the fact that the Stream is contained in P-101.

The Process Engineer sent the process conditions for P-101. These differ from the above data, because there is a rule that 10% overcapacity shall be included. So we see that the RATED VOLUME FLOW RATE now is 1730 m3/hr and the DIFFERENTIAL HEAD remained 30 mH20. This example is of course a very thin sliver, considering that a Pump Spec has some 30 process data.

On March 15, 2012 an information set was compiled, using an instance of EnumeratedSetOfClass as the collector.

Product Catalog

Meanwhile the ACME Ltd has published, on July 19, 2009, a design for a pump model BN-3834R. That design allows for a RATED VOLUME FLOW RATE of 1783 m3/hr at a DIFFERENTIAL HEAD of 30 mh2O (just a point on its QH-curve). Normally this information is defined in a more complex manner, with at least three instances of ClassOfIndividualHasConditionalIndirectPropertyWithValue, but that would obscure this story.

On December 18, 2011 ACME published their 2012 catalog, for which they produced, for their Model BN-3834R, an information set.


About Procurement much more could be shown, but here we only show the template that links the P-101 Requirements Class with the Model BN-3834R pump of ACME Ltd. It confirms that to the analysis of the Pump Specialist the latter fulfils all requirements for P-101.


At the end of the manufacturing process we declare the manufactured instance of MaterializedPhysicalObject that is a member of the BN-3834R Class. It gets the serial number SN-3834_2349830-Xn.


The purchased pump is transported to Warehouse 2 on the plant site. After the Event of arrival at destination there is a transfer of ownership. A temporal part of the pump is the start of its existence at the site (it may end some day when it is either sold or destructed). That temporal part gets the Asset Number AN98765.


The pump with Asset Number AN98765 is installed in the function place P-101. That installed instance of PhysicalObject (with its GUID :T411F0ABAE23A425785811720FD084A59) is the temporal whole in all templates for its activities in Operations and for templates describing the fact that it was subjected to IN-LINE MAINTAINING.

The Activity in Role 1 of the template InstallingAMaterializedPhysicalObjectInFunctionPlace allows for linking further information such as who did it, used consumables, costs, etc.

The fact that the installed object is a temporal part of both P-101 and AN98765 means that all information about these two objects in valid for the installed object, because the relationship TemporalWholePart is transitive (not for annotation properties). The operator who speaks about P-101 in fact speaks about both P-101 and the MaterializedPhysicalObject that is installed in the function place at that time.


Two runs are coded, inclusive of the start and stop Events.

Although a template shows that there is an AVERAGE VOLUME FLOW RATE it is not certain that this particular flow is being measured, neither is the differential head. If there is a flow measurement, it would be impossible to represent each and every changed value for years and years. That would easily fill the largest data store capacity. It is advisable to store measured values as time series in, for example, the HDF5 format, and calculate average values per hour or shift or day. This aspect has not yet been thoroughly evaluated.

The calculated average flow rate then could be compared with the flow rate calculated in Process Design and published in the Heat and Material Balance.

In-line Maintenance

In cases where maintenance can be done without de-installing the pump, a temporal part of the installed pump is subjected to that maintenance.

Shop Maintenance

In cases where the maintenance must be done in a shop, the pump is de-installed. The template :T31B7D9DEF9A44B97836A3C0E7B2417B6 is deprecated, so the represented information is no longer valid.

To spice this story up a bit maintenance costs of $ 890 were reported on March 11, 2014, two and a half year after Process Design data became available.

Reference Data


In the RDL several concepts were missing. A proposal to add them can be found here.

ACME Ltd RDL Extension

The ACME Ltd stores their product data in an extension of the RDL.

XYZ Corp.

The plant owner/operator stores company-specific information in their extension to the RDL.


All declared objects and templates are interconnected (please report if not completely the case!) and describe (a part of) the life cycle of P-101. In fact there is no end to the information that could be added. The only limitation is the business need.