This document provides an overview of the TeamHawaii Solar Decathlon software system interface milestone 2 kickoff. The goal is to implement monitoring and control for five house systems by April 2011 to explore the design space of these capabilities. It discusses what makes a house "smart" through integration, data collection, and control. The system architecture collects data from house systems through various interfaces to a central iHale API and repository for monitoring and sending control commands. Details are provided on assumptions for milestone 2 capabilities for each system and issues to consider regarding monitoring and control capabilities.

1. TeamHawaii Solar DecathlonSoftware System InterfaceMilestone 2 KickoffPhilip JohnsonCollaborative Software Development LaboratoryInformation and Computer SciencesUniversity of Hawaii

2. Overview for everyone

3. ICS Software MissionProvide a student-based, innovative software solution.Create functionality not available in commercial, off the shelf software.Support a "smart" house.

4. What makes a house smart?Requires data:Need to know the current and historical "state" of major house systems.Requires control:"Smart" implies ability to take action.Requires integration:Within house: actions based upon knowledge of *all* systems, not one.Outside of house: ability to interact with Facebook, smart phones, etc.

5. System architectureAdditionalInterfacesHouse SystemsiHaleTabletAquaponicsSmart PhonePVWeb UIDataDataFacebookHVACiHale APIHTTPHTTPRepositoryControlMachineLearningLightingControlKinectWater

6. UI Example

7. Milestone 2 goalImplement monitoring and control for all five house systems.Due in April, 2011.Explore the "design space" of monitoring and control capabilities.The following slides show our assumptions for Milestone 2 about each system.

8. AquaponicsMonitoring:CirculationDead FishElec. Conduct.NutrientsOxygenpHTemperatureTurbidityWater LevelControl:Feed fishHarvest fishAdd nutrientsAdjust pHSet temperatureSet water level

9. HVACMonitoring:TemperatureControl:Set temperature

10. PhotovoltaicMonitoring:Instantaneous powerCumulative energyControl:(No control)

11. Electricity ConsumptionMonitoring:Instantaneous power consumptionCumulative energyControl:(No control.)

12. LightingMonitoring:Monitor each room individually:Lighting levelLighting enabledLighting colorControl:Control each room individually:Lighting levelLighting enabledLighting color

13. Issues to ponderWhat is the "sweet spot" for monitoring and control capabilities that:Enables innovation beyond present commercial software;Provides maximum opportunities for "smart" behavior;Is within budget.Brainstorm:What else can we monitor/control?What other kinds of "smart" are possible?

14. Thanks for listeningQuestions?ICS student project lead:Kurt Teichmankurt.t.teichman@gmail.comFaculty sponsor: Philip Johnsonjohnson@hawaii.edu

15. Details of Milestone 2Non-programmers can stop watching now.

16. Milestone 1 API (review)ihale-api.jar provided:Interface for repository (DB).Interface for commands.Backend:Implemented both interfaces.Frontend:Used the backend implementations.Simulator:Didn't need either, used HTTP API

17. Milestone 2 APIihale-api.jarProvides interface for repository (DB).Provides interface for commands.Provides implementation of DB!Backend:Implement commands.Use iHale API repository implementation.Frontend:Use Backend implementation of commandsUse iHale API repository implementation.

18. iHale API repositoryUses enumerated types to specify:System namesState variable namesCommand namesRoom namesProvides ~60 methods for retrieval of:The most recent state value for any system/state variable combination.A list of historical data points for anysystem/state variable combination.New persistent data: "System Status Messages"

19. Benefits"API Dictionary" is now hard-codedNo strings attached.Front end can create sample repository data for testing/development.No need to wait for backend.

20. on to the demo