I have AHU booster pump and also I need to represent pumps in Chiller Plant.

cool booster pump //Could be used for booster pumps on AHU's

We also need description for primary and secondary loops.

secondary chilled water pump primary chilled water pump

Thank you

We also have the need to represent pumps in the building energy plant - HWS, CWS, and HHWS pumps. We are new to haystack. Appreciate any feedback and suggestions. Regards,

We haven't really done a good job on nailing down pumps. There seem to be some cases where pumps and valves are best treated as points, but others when they should be modeled as full blown equip. Also given the complexity of piping and pump location in a central plant, we haven't been able to come up with an all inclusive model. But its a great topic for discussion!

Can ISO 15926 be used for pumps? http://en.wikipedia.org/wiki/ISO_15926

Hi Deborah,

Can you give us a brief introduction to 15926 and how it might help model a pump in the context of Haystack tags?

Hi Brian -

ISO 15926, "the semantic web for engineering", has been used for a long time in the oil and gas industry. 15926 pumps are different than pumps used in building systems. However, enough people have worked with 15926 for enough time, that a solid structure has been made to represent the larger world pumps are used in.

An excerpt from a paper by Matthew West et al is "For example, let us assume that a pump was designed and identified as P-101. Some time later, a manufacturer delivers a pump with serial number 1234 that meets the design specifications of P-101. Pump 1234 is installed and after a period of operation the pump fails. Therefore, maintenance decides to replace it with pump 9876. This situation can be easily modeled using the concept of temporal parts as shown in Figure 1."

Online tools to see what 15926 has are here http://15926.org/viewtopic.php?f=10&t=68?sid=

Another reason is 15926 is written in EXPRESS, which should be able to hook into pumps and systems modeled in BIM. Easier said than done, but one implementation is Bentley using 15926 as the basis of OpenPlant PDx Manager.

If pumps used in buildings can be organized and tagged up properly for Project Haystack, and there is a future need to expand Haystack tags out to larger supply chains, physical locations and so forth - 15926 has proven ontologies to link into.

Deborah

Based upon my limited understanding it looks like this ISO standard uses sort of RDF like triples. But if there is interest in seeing how this might help with pump (or other equip modeling in Haystack), I think someone needs to take the lead in how to take some of the semantic database from ISO 15926 and show how we could turn it into tags.

Brian,

I think a realistic starting point would be to define at a minimum tags for the following:

pumpCommand pumpStatus pumpAlarm

I think by convention, we would pair sensor and cmd with status for the command and status points. Although don't really love the word status. I don't think we ever really came up with good term to use for the core on/off status values.

Alarming is really a whole new topic we haven't really tackled in Haystack.

See below from Matthew West regarding 15926 and pumps, recommending the Reference Data Library (RDL) particularly. This also addresses Control Functions raised by Jacob Nicosia

I have some .xls to forward also - where should those go or where should I send?

Deborah MacPherson ____________________

Dear Deborah, Well I think what you are really looking for is the ISO 15926 RDL. This has a significant list of equipment types. Oh and pumps in the building industry are just the same as pumps in the oil industry, if only because the oil industry has rather a lot of buildings.

I attach some of the spreadsheets from Ed 1 of the RDL, which I think is the latest version. It is available also from a SPARQL end point, but the spreadsheets are usually more familiar. I trust they are reasonably self explanatory. The spreadsheet on rotating equipment will include pumps, and most of the other things on the link you gave me are probably in one or other of the spreadsheets.

Regards

Matthew West Information Junction Tel: +44 1489 880185 Mobile: +44 750 3385279 Skype: dr.matthew.west [email protected] http://www.informationjunction.co.uk/ http://www.matthew-west.org.uk/

This email originates from Information Junction Ltd. Registered in England and Wales No. 6632177. Registered office: 2 Brookside, Meadow Way, Letchworth Garden City, Hertfordshire, SG6 3JE.

Bringing focus back to this: pump should definitely be added as a tag.

pump could be an equip, but it typically can be associated directly to a chiller or chillerPlant. At least, I am not seeing a reason to require this as an equip over a point in SkySpark.

If made as a point, pump should be associated with chillerPlant and related to the tags: primaryLoop, secondaryLoop, and/or condenser.

I think by convention, we would pair sensor and cmd with status for the command and status points.

Does this mean:

• pumpCommand would become status cmd?
• pumpStatus would become status sensor?

Looking at:

Although don't really love the word status. I don't think we ever really came up with good term to use for the core on/off status values.

status is relatively common in BAS; engaged also works as on/off. Sometimes also see a simple on.

Final point examples:

• primaryLoop chilled water pump cmd
• secondaryLoop chilled water pump status

To correct one point in my last post, I was thinking of the instances where the pump is married directly to another equip such as a chiller, but there are definitely cases where multiple pumps are put in parallel on the primaryLoop, secondaryLoop, etc.

Accordingly, I think it's better to have the pump as a separate equip, with an optional equipRef in case it is linked directly to an equip.

It seems to me that the general consensus is that fans with a VFD and pumps should be their own equipment. That then begs the question should be consistent across the board and say that is true for all fans and pumps? Or in simple cases do we let fan/pumps/valves just be a simple point?