Final Presentation Ivan Tam Lindsay Tabas Katrina Rhoads John Mark Josling

Problem Statement & Goals Goal: To develop an interface for facility managers to control and monitor a building’s entire wireless- controlled lighting system. Key Functionality: –Monitor energy usage –Control the lighting at various levels of granularity –Provide notice of lighting failures

Personas Tomas Cupertino, 51 (Primary User) Facilities Manager Texan with a big, loving family Good at his job, but no high school degree Basic computer skills – , Word & web forms Main Goal: To deal with maintenance issues in a timely manner Dan Mason, 46 Physical Plant Utilities Manager Divorced, father of two Pays campus wide utility bills Works on automating energy usage with motion sensors and the like. Main Goal: To reduce energy usage

Scenarios Scenario 1: It was a long weekend and Tomas needs to check for new lighting problems that occurred over the weekend. Scenario 2: The museum is having a special showing this week and Tomas would like to keep the lights in a select number of rooms on 2 hours later than usual. Scenario 3: New energy-saving devices have been installed last week and Dan wants to check on the actual energy savings.

First Interactive Prototype Tools: HTML & JavaScript Improvements: Scheduling & Grouping Limitations: No saved state IE only Energy graphing & scheduling wizard incomplete Heuristic Evaluation: Reveals minor violations and leads to some major redesigns

Heuristic Evaluation Results Lighting Problems Page: Icons are unclear Listing of fixed lights and broken lights together is confusing Mapping between problem list and visual display is difficult ON/OFF Page: On/Off buttons not visually distinct Schedule Lights Page: No way to cancel or exit when editing a schedule What Lights Are On Page: Grouped with dissimilar pages Overall: Inconsistent interaction with floor plans

Changes Made: Navigation Moved “What Lights Are On” to under the “Energy Usage” category

Scheduling Page New Schedule wizard Mouse-over effects Delete button becomes Cancel during editing Increased size of the Save button Schedule names editable

Changes Made: Scheduling Previous Stack New Schedule Wizard

Changes Made: Lighting Failures Fixed lights removed from list New status: Reported/Unreported Flags replace icons Additional ways to mark a problem as reported Call-out window for notes and details Brushing & linking to connect problems list to floor plan

Changes Made: Lighting Failures Icons with no mapping from list to visual display Brushing & linking with flags

Changes Made: Energy Graph Legend Removed chart junk Increased interactivity Clearer comparison line options

Changes Made: Energy Graph no comparison line red comparison line

Changes Made: Turn On/Off More visible On/Off buttons Mouse-over effects for room selection Labels indicating number of lights on per floor

Changes Made: Turn On/Off Hard to see buttons More distinct buttons & labels

Demo Second Interactive Prototype Second Interactive Prototype

Pilot Study Procedure and Participants Think Aloud 3 of 5 sessions recorded Comparison Study –Schedule Wizard v. Schedule Stack –Within Participants –Measures: Time & Likert Scale Opinions

Pilot Study Discussion Stack: seconds Wizard: seconds Questionnaire indicates preference for Wizard Errors made on the Stack were greater

Experiment Discussion If it were a real experiment… –Record all sessions –Increase familiarization prior to testing –Allow users to create the first schedule Improving the Post-Test Survey –Ask more questions about satisfaction –Include more detailed questions Disassociate ourselves from the interface

Planned: 3rd Prototype Changes Schedule Wizard: Hyperlink breadcrumbs Schedule Page: Add dialog box to enter edit mode Lighting Problems Page: Saving Notes - Add save & cancel button to call-out Value of Sort Functionality – needs more attention Building plan perceived as interactive – call-out should appear over floor plan upon mouse-click Reported/Unreported Confusion Energy Usage Graph: Legend Location Add Export Functionality Summary Data

Questions? Thanks for your attention! Ivan Tam Lindsay Tabas Katrina Rhoads John Mark Josling