Open gtfierro opened 1 year ago
Proposal:
Would like to add suppressing systems like extinguishers and sprinklers.
Also wonder if detectors could be an alarm at the same time in many cases (like home fire alarms)
Also wonder if detectors could be an alarm at the same time in many cases (like home fire alarms)
We can probably create an Alarm Point that we associate with the detectors to draw a distinction between the device and the signal
Or are you asking if it is both the "detector" and the "sound emitter"?
Or are you asking if it is both the "detector" and the "sound emitter"?
Yes. Those detectors emit sound as well, so either we have to adjust the hierarchy or let users instantiate both at the same time. I 'guess' it's common to have both functions.
According to the conversation I'm having on the REC gitter, future versions of DTDL (v3 in particular) will support up to 1024-way multiple inheritance. Azure Digital Twins v3 is still in preview I guess, so we don't know if REC will migrate to DTDLv3 yet. If they do, it will probably be after ADTv3 moves out of preview
Or are you asking if it is both the "detector" and the "sound emitter"?
Yes. Those detectors emit sound as well, so either we have to adjust the hierarchy or let users instantiate both at the same time. I 'guess' it's common to have both functions.
Yes, I think it's quite common to have devices that combine multiple aspects (e.g., a point detector that detects both heat and smoke).
A sound-emitting fire detector, I think, I would model as a combination of a Fire_Detector
and an Audible_Alarm_Device
.
According to the conversation I'm having on the REC gitter, future versions of DTDL (v3 in particular) will support up to 1024-way multiple inheritance. Azure Digital Twins v3 is still in preview I guess, so we don't know if REC will migrate to DTDLv3 yet. If they do, it will probably be after ADTv3 moves out of preview
Great, then perhaps we can avoid the combinatorial explosion by using multiple inheritance here.
What would be the most pythonic brickish bricky way of doing this, e.g., for the Fire_Detector
? Should there be one subclass for each item along each dimension?
Relevant past discussion: https://github.com/BrickSchema/Brick/pull/336
@gtfierro @jbkoh @epaulson I would like to ask for quick feedback as to whether the proposed terms in https://github.com/BrickSchema/Brick/issues/556#issuecomment-1708900836 are OK. If so, I would prepare a pull request so that the new equipment types can become part of Brick 1.4.
Though I like the hierarchy, I'm not sure if we have an agreement on the audible fire detector issue. Is the solution to have "Fire_Detector_with_Audible_Alarm"?
Btw, I'm looking to define Smoke Zones and Fire Zones too: https://ltc.health.mo.gov/archives/15059#:~:text=The%20fire%20alarm%20zones%20are,full%20evacuation%20of%20the%20building. Maybe this should go to REC though.
Smoke damper and fire dampers too.
@ektrah @jbkoh I suggest changing the term "Carbon Monoxide Fire Detector" to simply "Carbon Monoxide Detector." These devices primarily serve to identify the presence of CO gas originating from malfunctioning boilers, water heaters, leaking exhaust vents, or vehicles in enclosed parking areas. While they are associated with combustible sources, their primary function is not directly connected to fire detection or fire safety.
As I understand it, on the one hand there are detectors that have the purpose of detecting fire and of which there are a number of variants that differ in the detection method (e.g., based on the presence of smoke, heat, flames, carbon monoxide). And on the other hand, there are detectors whose purpose is to detect the presence of gases. I'm not sure if carbon monoxide fire detectors and carbon monoxide detectors are interchangeable enough that we should combine them, even though they probably work internally very similarly. What do you think about having both?
Hi @ektrah yeah, we can have both and let the fire one be a subclass of the other one. However, if we distinguish "alarm device" from "detectors", sole detectors are equivalent to just "sensor equipment", and in that case having a separate class of "CO Detector" might be not super necessary.
So, I have to ask the question that I raised again; are "detectors" dedicated to just sensing something alone if we have Audible_Alarm_Device separately? In that case, what are the distinguishable features for detectors compared to Sensor Equipment's?
With regards, Jason Koh
On Thu, Feb 22, 2024 at 4:05 PM ektrah @.***> wrote:
As I understand it, on the one hand there are detectors that have the purpose of detecting fire and of which there are a number of variants that differ in the detection method (e.g., based on the presence of smoke, heat, flames, carbon monoxide). And on the other hand, there are detectors whose purpose is to detect the presence of gases. I'm not sure if carbon monoxide fire detectors and carbon monoxide detectors are interchangeable enough that we should combine them, even though they probably work internally very similarly. What do you think about having both?
— Reply to this email directly, view it on GitHub https://github.com/BrickSchema/Brick/issues/556#issuecomment-1960539217, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAL76E6GSXUQC2WNMYTASPDYU7MMFAVCNFSM6AAAAAA4KUIKCOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNRQGUZTSMRRG4 . You are receiving this because you were mentioned.Message ID: @.***>
Here is how I understand it:
The open question from my point of view is how to model a box that combines a fire detector and an audible alarm device.
(¹ in the sense of s223:Sensor
, not brick:Sensor
or brick:Sensor_Equipment
)
There is some ambiguity in our classes around fire control systems. According to https://www.nfpa.org/News-and-Research/Publications-and-media/Blogs-Landing-Page/NFPA-Today/Blog-Posts/2021/03/03/A-Guide-to-Fire-Alarm-Basics we may want to have 3 broad types of equipment: fire control panel, fire alarm initiation systems, and fire alarm notification systems.