BOPTEST and Data Tagging

Learning objectives

• >Run a BOPTEST test case and compare control strategies
• >Interpret energy and comfort KPIs
• >Apply Haystack tags to a points list
• >Describe a plant using Brick relationships

Sessions

Three 2-hour weeknight sessions plus a weekend block. Check each one off as you finish it.

1. SESSION 1· 2 h Install Docker and run BOPTEST. Load a hydronic test case
2. SESSION 2· 2 h Run the baseline controller, then your own strategy (supply-temperature reset or pump speed)
3. SESSION 3· 2 h Compare energy and discomfort results in a short table
4. WEEKEND· 4 h Tag your Week 2 points list with Haystack tags, and sketch the plant in Brick

Answer in your notebook first, then reveal the answer and grade yourself honestly.

1. Q1Name two KPIs BOPTEST reports.

   [ reveal answer ]

   Examples: total energy use, thermal discomfort, operating cost, emissions, and peak demand.

   ✓ I got it ✗ Missed it

2. Q2Why test control strategies on an emulator rather than a real building first?

   [ reveal answer ]

   It's safe and repeatable, and it lets you compare strategies under identical conditions.

   ✓ I got it ✗ Missed it

3. Q3Give a plausible set of Haystack tags for a chilled-water pump speed command.

   [ reveal answer ]

   For example: chilled, water, pump, speed, cmd.

   ✓ I got it ✗ Missed it

4. Q4What is the main difference between Haystack and Brick?

   [ reveal answer ]

   Haystack is tag-based. Brick is a formal ontology (RDF) with explicit equipment and point relationships.

   ✓ I got it ✗ Missed it

5. Q5In Brick, what does the 'feeds' relationship express? Give a pump example.

   [ reveal answer ]

   That one piece of equipment supplies a medium to another, for example a pump feeds a chilled-water loop.

   ✓ I got it ✗ Missed it