1	The BIG-NA BACnet Connected Interoperability Demo 9 vendors participating. Ethernet connection representing Internet/Intranet. Control of typical building systems (chiller, boiler, AHU, VAV box, VSD). Demonstration of BIBBs. MS/TP device demo.
2	Grant Wichenko moderates BIG-NA’s BACnet connected demo.
3	Grant Wichenko leads the BIG-NA demo of 9 vendors.
4	The BIG-NA BACnet demo results were projected live on screen.
5	Automated Logic controls the boiler in the demo.
6	The initial HWS setpoint is on the ALC boiler is 188 F.
7	Lithonia Lighting shows the two lighting presets and the ALC boiler setpoint on its Front End.
8	Lithonia can control Delta’s booth lights and ALC’s boiler, as well as the points in its own lighting panel.
9	Lithonia resets ALC boiler setpoint from 188 F to 88 F using its own Front End.
10	Delta Controls activates Lighting Preset #2 on its on the Lithonia lighting panel.
11	Grant Wichenko explains that BACnet can be used from the web level to the device level.
12	Lithonia, using only IE, can also set the ALC boiler supply setpoint to 88 C via the ALC web server.
13	Alerton, using IE,can access the Lithonia lighting panel via the ALC web server.
14	Alerton, using only IE, can also access Lithonia’s Lighting Preset #2 via the ALC web server.
15	Three different vendors’ devices (Alerton, Delta and Reliable) are running on a common MS/TP LAN.
16	McQuay’s RTU panel is sitting the on the common BACnet MS/TP LAN set up for the demo.
17	Alerton displays the McQuay RTU data on the common BACnet MS/TP LAN.
18	Delta arms its access panel by swiping a security card.
19	Alerton sees that the Delta access panel is armed.
20	Reliable represents the Delta access panel as a graphic in its system.
21	Reliable sees that the Delta access panel is armed.
22	Delta shows Trane panel data in a non-graphical Explorer-style window. Graphics are not needed for BACnet interoperability.
23	Delta creates an AO object in the Trane panel.
24	Trane looks for the AO object that Delta created in its panel.
25	Trane sees the object that Delta created in its panel and deletes it.
26	Delta gets ready to generate the low limit alarm on its AHU.
27	Reliable Controls graphic of the Delta AHU. No alarm has been generated yet by Delta Controls.
28	Siemens also shows no low limit alarm on the Delta AHU.
29	Delta sees generates the low limit alarm on its AHU. The alarm dialog box pops up.
30	Reliable also sees the low limit alarm on the Delta AHU.
31	Alerton sees the low limit alarm on the Delta AHU. All vendors display the alarm.
32	Alerton acknowledges the Delta low limit alarm.
33	Alerton gets ready to generate a fault alarm on its heat pump.
34	Alerton sees the fault alarm on its heat pump in the dialog box.
35	Delta acknowledges the Alerton heat pump alarm.
36	Delta gets ready to create an intruder alarm on its access panel.
37	Delta sees the intruder alarm on its own access panel.
38	Alerton acknowledges the intruder alarm.
39	Delta’s schedule object is unoccupied on Wednesday.
40	Automated Logic adds Wednesday as an occupied day to the Delta schedule.
41	ALC shows the Delta schedule that it modified for Wednesday.
42	Delta also shows the schedule that ALC modified for Wednesday.
43	Delta’s calendar object shows that April 6, 2003 is not a holiday.
44	Alerton edits the Delta calendar object to make April 6, 2003 a holiday.
45	Delta’s calendar object shows that April 6, 2003 is now a holiday.
46	This is Alerton’s graph of different vendors’ objects it is trending.
47	This is the list of objects from different vendors’ panels that Alerton is trending.
48	This is Reliable’s graph of different vendors’ objects it is trending. Every vendor is trending different objects.
49	This is Siemens’ graph of different vendors’ objects it is trending.
50	This is ALC’s graph of different vendors’ objects it is trending.
51	Grant Wichenko introduces Mike Newman, who explains the protocol sniffer.
52	Mike Newman explains how his protocol sniffer can see BACnet message packets.
53	The protocol sniffer can read the contents of each BACnet message as ASCII text.
54	The protocol sniffer can also read the contents of each BACnet message as hexidecimal.