Query 2: Product Hierarchy CEE-243, Spring 2011 1 April 7, 2011 Query 2 Query overview In completing this query, you create a structured hierarchy illustrating the structure of your group’s assigned system(s). Group and system assignments can be found on the last page of this handout. Please get in touch with us if you are still taking the class but have not been assigned to a group. As discussed in class on April 5, product hierarchies are useful to show the way that systems have subsystems and components and thermal zones in the building that they serve. For this query, working with your group, please create a product hierarchy that shows the way you represent your assigned systems and subsystems. . Use SEE IT to create your hierarchy, which SEE IT will store and you will extend and elaborate in future queries and the final project. Product hierarchy example Please look at the Week-2 Introduction to product hierarchies Systems and Y2E2 HVAC systems on the class agenda at http://www.stanford.edu/class/cee243/Agenda.htm. Slides 24 to 27 show a generic description of Product Hierarchies. Figure 1 below illustrates a sample product hierarchy. For simplicity, this model does not show geometric elements, i.e., the decomposition of floors into zones, . Due to the limitation of graphing tools, there are some duplicate nodes in the graph, although not in the conceptual model. Figure 1: Hierarchical representation of Systems and Spaces of the Y2E2 building, with a elaboration of some derails of the Air Loop 1 system and the 2nd floor. Floors (note the ribbon on the top of the figure) include Basement, 2nd Floor, etc. and they are part of the building. Spaces include rooms 291 and 293 and are part of the 2nd Floor. Systems include the three Air Loops and Water Loops and are part of the building. The components Heating Coil 1, Cooling Coil 1, and CV-1-2-7 are all part of the Air Loop System. The zones 291 and 293 are served by component CV 1-2-7 while spaces 291 and 293 are part of these zones. The diagram represents entities as names, e.g., 2nd Floor and Air Loop 1 and class-subclass relationships among entities as lines withQuery 2: Product Hierarchy CEE-243, Spring 2011 2 April 7, 2011 semantic meaning defined by the legend, e.g., a blue arrow indicates the originating entity IsServedBy the entity being pointed at. Figure 2: This SEE IT screenshot shows the same hierarchy as Figure 1 in the left pane, although represented in a different way than Figure 1. Note that the hierarchy tree shows instance or specific example nodes as text names, e.g., Y2E2, 291, and lines as links between nodes, e.g., BL, Co, FL, Sp, Sy, Zo for Buildings, Has_CoolingCoils, Has_Floors, Has_Space, Has_Subsystems and Has_Zones respectively. In SEE IT, the zones are currently associated with the larger system rather than the component, e.g., Zo 291 is associated with System Air Loop 1, not component Cooling Coil 1. Note that all of these physical elements, i.e., buildings, system components and spaces, are examples of physical forms that the design team created in response to some functional intent, which at the moment is implicit. Each in turn has behavior, some of which we can measure, that may (and of course may not) align with the functional intent. For example, we can infer that the physical Air Handling Unit R1 has functional intent to supply (presumably fresh) air to the building and return some (presumably not so fresh) air from the building to the outside. AHU R1 has several associated sensors, e.g., Outside Air Temp (1123). Further, we can infer that the normal range of measured values for point 1123 should be typical for this climate, say something like 0o to 120 o F. Thus, we could classify sensed data value in this range as “green” using a traffic light convention and 600 o F as “red” or abnormal. This query has the joint goals of helping you to create and understand the product hierarchical representation of your assigned system in the broader context of Y2E2 and in general building systems, and to start to describe specific functions, forms and behaviors for Y2E2 and to start to develop intuition and methods to interpret the goodness or state of behaviors given their measured values and associated functions and forms. Due Date 1:15 pm Thursday, April 14. Please submit via the Assignment Q2 on Coursework.Query 2: Product Hierarchy CEE-243, Spring 2011 3 April 7, 2011 What to submit SEE IT on Wiki Please create your system hierarchies in SEE IT and update your group’s hierarchy sections on the wiki. Include the following: 1. (2 points) Submit a PowerPoint slide that includes an annotated screenshot of product “type” hierarchy of your assigned systems that you created and saved in SEE IT. Use the example shown in above Figure 1 as a representation convention. o Use the Data Manual and System-Component-Assignment file in the Building Information folder on CourseWork as references. o Note that our example hierarchies represent individual instances of products. Thus, for example, your product type hierarchy will include components, such as individual valves, boilers and pipes. A building energy system will have multiple valves and pipes, and it may have multiple boilers. o In your submitted description and in the wiki text, please describe the semantics (meaning) of nodes and connections. For example, one type of node might be product system function (e.g., valves, boilers, pipes) and one type of connection might be system (Sy)  component (Co), e.g., Heating Coil 1 is a part of Air Loop 1. 2. (1 point) Upload the SEE IT file to the wiki and add a reference to it in the wiki hierarchy section. 3. (2 points) Submit a PowerPoint slide that shows the hierarchy you created and explains how you analyze your decomposition to explain the design, or physical forms, of your HVAC subsystem and how, given some assumptions about function and measurement of behaviors, you could analyze the consistency of its behaviors given the functional intents you assume the designers and the operators have. 4. (2 points) Using the Data Manual and the wiki, identify a measurement point associated with a physical element in your hierarchy. Submit a slide that describes your inference about its function and includes a SEE IT plot of at least one month of measured behavior