Meters and 'feeds'

[danie...@csiro.au]

Hi all, 

I was thinking about 1.3, but this would apply to 1.4 too... Meters of fluids are installed in-line with pipes. Physically, gas or liquid is fed from upstream, through the meter, which then feeds downstream equipment. 

When creating Brick models, as well as declaring what a meter meters, should the feeds relationship be routinely modelled too? e.g. Gas_Distribution feeds a Gas_Meter, which then feeds [some other equipment].

Or should such a meter be left out of the feeds sequence (and only model the meter as brick:meters whatever is downstream)? 

If the latter, should there be a SHACL shape to set a norm? 

Cheers, 
Dan. 

[Gabriel Fierro]

Hi Dan:

 

ASHRAE 223P is better suited to modeling how a flow meter might be in line with other equipment (see https://docs.brickschema.org/modeling/connections.html). In Brick, meters should not participate in the “feeds/isFedBy” topology; they can “meter” other equipment but that’s it. In this case, you would probably have your Meter instance “meter” the downstream equipment to capture the consumption of that liquid/substance. If you care about modeling where that measurement takes place, I would encourage you to use the 223 Pipe (or other connection object) to connect those equipment and have your sensor relate to some connection point or connection where the measurement takes place.

 

I’ll make a note to update some of the Brick documentation (https://docs.brickschema.org/modeling/meters.html), and we might explore encoding some of this in a SHACL shape as well. Does this answer your question?

 

Best,

Gabe

 

--
You received this message because you are subscribed to the Google Groups "Brick User Forum (Unified Building Metadata Schema)" group.
To unsubscribe from this group and stop receiving emails from it, send an email to brickschema...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/brickschema/1e24f9af-1c0f-41ce-a82b-b2c5c500cba2n%40googlegroups.com.

[Sarah MacDougall]

Hi Gabe,

 

If it is not best practice to use the 'feeds/isFedBy' relationship with meters, then what do you recommend for modeling electricity flow from a electricity source, such as utility connection or generator, to a switch that toggles between electricity source?

 

What do you think of the following modeling from electricity source (Building's utility connection or Building Generator) to electricity load (equipment consuming electricity)?

 

Building> 'isMeteredBy' -> Building Electrical Meter

                                                   -> has Sub-meter-> Floor 1 Electrical Meter (Electrical Meter)

-> Has Sub-meter

->Breaker 1 Meter

 

Building> 'IsLocationOf'->ext:Generator

     >'Feeds'> ATS Switch  (ATS  switch to auto-toggle between power sources)

 

Building> 'IsLocationOf'->ATS Switch

                                                 > 'Feeds' > Breaker Panel 1 > Equipment 1

>is Metered By> Breaker 1 Meter

 

 

I'm using the feeds relationship between equipment, but there is no connection showing the electricity flow from utility connection to the ATS Switch. How would you represent this connection?

Thanks,

Sarah

[Gabe Fierro]

Hi Sarah:

 

Sorry for the delay in my reply!

 

We have not done much with modeling electrical service in buildings outside of the meters. Most of the electrical-oriented equipment in Brick today was driven by metering needs rather than modeling the supply. Is there anything you miss by using “feeds/isFedBy” in this case (or the directionless https://ontology.brickschema.org/brick/connectedTo.html)? What is important to capture about the electricity source/load relationships?

 

223P does have support for wires and electrical supply but the design is still being worked through. Some of the example models have this available: https://models.open223.info/examples/pnnl-bdg2-1.html

 

To view this discussion visit https://groups.google.com/d/msgid/brickschema/9d1377be-5c69-4119-8d2a-dc9ed765388cn%40googlegroups.com.