BRICK Class Support
Last updated
Last updated
has the following top-level classes:
Collection
Equipment
Location
Measurable
Point
DCH has partial support for BRICK Collection classes. In DCH, all Collection classes (including the top level/generic "Collection" class) are internally treated the same as Equipment. This affects how Collection classes are found/viewed/selected in the DCH interface. It also adds an important restriction to the use of Collection classes in DCH. The only valid relationships to/from Classes from the Collection hierarchy are the valid relationships to/from Equipment Classes. See DCH support of BRICK relationships for details. As most items in the BRICK 1.2.1 Collection Hierarchy can be considered types of equipment this is not a significant limitation. There is one outlier, which was discussed earlier, brick:Portfolio. BRICK Portfolio should not be used in DCH.
Currently brick:Portfolio is not explicitly forbidden (it is treated as a type of equipment), however that may change future DCH.
DCH fully supports declaration of all BRICK 1.2.1 Equipment Classes including the top level/generic "Equipment" class.
DCH has partial support for the declaration of BRICK Location Classes.
The following classes are not supported or only partially supported in DCH:
Location
Parking_Structure
Outdoor_Area (& subclasses Bench_Space, Field_Of_Play, & Information_Area)
Outside
Region
Storey
Space (& all subclasses)
Zones (& all subclasses)
In DCH the top level/generic "Location" class is NOT supported. Upload of models that declare things as "a brick:Location" will not flag an error but those declarations will be silently dropped and those things will not exist in the model in DCH.
Suggested Workaround:
More specific Location classes must be used when modelling locations in DCH.
In DCH the building type “Parking Structure” is not supported. Upload of models that declare things as "a brick:Parking_Structure" will not flag an error but those declarations will be silently dropped and those things will not exist in the model in DCH.
Suggested Workaround:
Model a Parking Structure as a Building.
In DCH none of the Outdoor_area classes are supported. Upload of models that declare things as "a brick:Outdoor_Area" or any of its subclasses will not flag an error but those declarations will be silently dropped and those things will not exist in the model in DCH.
Suggested Workarounds:
Model Outdoor_Area as a Wing. Model Bench_Space's, Field_Of_Play's, and/or Information_Area's as a "Space" in DCH. Note the caveats around the use of Space below.
In DCH the class Outside is not supported. Upload of models that declare things as "a brick:Outside" will not flag an error but those declarations will be silently dropped and those things will not exist in the model in DCH.
Suggested Workarounds:
Model “Outside” as a “Wing”.
As discussed previously, because the modelling in DCH is building centric, the Region Class is not supported. Upload of models that declare things as "a brick:Region" will not flag an error but those declarations will be silently dropped and those things will not exist in the model in DCH. There is no suggested workaround for this. Use of Region as a semantic concept must not be used in DCH models.
In BRICK 1.2.1 BRICK:Floor and BRICK:Storey are defined as equivalent classes. DCH automatically translates the Storey class to the Floor class. Models that declare things as Storey(s), when uploaded to DCH, will appear with those things declared as Floors. This has some implications to searching and querying, discussed later.
DCH accepts declarations of all classes in the Space class hierarchy.
Internally in DCH, all types of Space Classes are treated like Rooms. This affects how Space classes are found/viewed/selected in the DCH interface. As DCH adds some restrictions on the relationships that Rooms can have, those restrictions also apply to things declared as classes from the Space class hierarchy. See DCH support of BRICK relationships for details.
All types of zones can be declared and used in DCH.
They are listed here as having partial support because there are restrictions on the allowable relationships that can be used with Zones. See BRICK 1.2.1 relationship support for further details.