[SmartHouses] Remaining work for the SmartHouse online simulation

Gregg Vanderheiden gregg at raisingthefloor.org
Wed Jul 30 13:20:13 EDT 2014


Welcome !

gregg

On Jul 30, 2014, at 12:15 PM, Trifon Trifonov <ttrifonov at asteasolutions.com> wrote:

> Hello, Boyan and Gregg
> 
> I would like to join this call as well in order to better understand outstanding tasks on the SmartHouses activity.
> 
> Regards,
>   Trifon
> 
> 
> just got/saw this — so today is out.  
> but I can meet tomorrow at  15:00.
> that is 7 am here but I can do that
> 
> see you then
> lets use Room 2
> 
> gregg
> 
> 
> 
> 1.  You can join using the following URL
> https://www3.gotomeeting.com/join/619028605
> 
> Use your microphone and speakers (VoIP) - a headset is recommended. 
> BE SURE TO SET THE AUDIO TO    "Microphone and Speaker"   if it is set to Telephone when you sign on. 
> 
> 2. Or, call in using your telephone.
> Meeting ID: 619-028-605
> Audio PIN: Shown after joining the meeting
> 
> Australia:+61 2 8355 1036
> Austria:+43 (0) 7 2088 1036
> Belgium:+32 (0) 28 08 4345
> Canada:+1 (647) 497-9372
> Denmark: +45 (0) 69 91 89 24
> Finland:+358 (0) 942 41 5788
> France:+33 (0) 170 950 586
> Germany:+49 (0) 811 8899 6928
> Ireland:+353 (0) 19 030 053
> Italy:+39 0 693 38 75 53
> Netherlands:+31 (0) 208 080 212
> New Zealand:+64 (0) 4 974 7243
> Norway:+47 21 04 29 76
> Spain:+34 931 81 6713
> Sweden:+46 (0) 852 500 182
> Switzerland:+41 (0) 225 3311 20
> United Kingdom:+44 (0) 20 3657 6777
> United States:+1 (213) 493-0618
> 
> Meeting ID: 619-028-605
> 
> gregg
> 
> On Jul 30, 2014, at 3:23 AM, Boyan Sheytanov <bsheytanov at asteasolutions.com> wrote:
> 
> Hi Gregg!
> 
> I'm available for a call to discuss the remaining SmartHouses tasks today and tomorrow at 15:00 CEST. Let me know if you are available then.
> 
> Best,
> Boyan
> 
> 
> just got/saw this — so today is out.  
> but I can meet tomorrow at  15:00.
> that is 7 am here but I can do that
> 
> see you then
> lets use Room 2
> 
> gregg
> 
> 
> 
> 
> 1.  You can join using the following URL
> https://www3.gotomeeting.com/join/619028605
> 
> Use your microphone and speakers (VoIP) - a headset is recommended. 
> BE SURE TO SET THE AUDIO TO    "Microphone and Speaker"   if it is set to Telephone when you sign on. 
> 
> 
> 2. Or, call in using your telephone.
> Meeting ID: 619-028-605
> Audio PIN: Shown after joining the meeting
> 
> Australia: +61 2 8355 1036
> Austria: +43 (0) 7 2088 1036
> Belgium: +32 (0) 28 08 4345
> Canada: +1 (647) 497-9372
> Denmark: +45 (0) 69 91 89 24
> Finland: +358 (0) 942 41 5788
> France: +33 (0) 170 950 586
> Germany: +49 (0) 811 8899 6928
> Ireland: +353 (0) 19 030 053
> Italy: +39 0 693 38 75 53
> Netherlands: +31 (0) 208 080 212
> New Zealand: +64 (0) 4 974 7243
> Norway: +47 21 04 29 76
> Spain: +34 931 81 6713
> Sweden: +46 (0) 852 500 182
> Switzerland: +41 (0) 225 3311 20
> United Kingdom: +44 (0) 20 3657 6777
> United States: +1 (213) 493-0618
> 
> Meeting ID: 619-028-605
> 
> 
> gregg
> 
> On Jul 30, 2014, at 3:23 AM, Boyan Sheytanov <bsheytanov at asteasolutions.com> wrote:
> 
>> Hi Gregg!
>> 
>> I'm available for a call to discuss the remaining SmartHouses tasks today and tomorrow at 15:00 CEST. Let me know if you are available then.
>> 
>> Best,
>> Boyan
>> 
>> On Fri, Jul 25, 2014 at 3:17 PM, Boyan Sheytanov <bsheytanov at asteasolutions.com> wrote:
>> Hi Gregg!
>> 
>> Thank you for your detailed description of the phone interface for the blind! It is really helpful to have it in a written form. I remember that we discussed controlling the appliances via the cell phone. However, looking at the time left I am not sure if this would be feasible -- which is why I proposed the screen reader case as a compromise. I imagined that since the screen reader would read the elements of the phone menu, and the user would be able to navigate through them and activate them, this might serve as an alternative for the blind. If that is not the case - let's discuss. I realize that this task is very valuable since it would affect a lot of users -- and thanks for bringing up that point.
>> 
>> I am unavailable for a call today and out of office on Monday. Let me know what times work for you on Tuesday (or after) and we can talk.
>> 
>> Best,
>> Boyan
>> 
>> On Thu, Jul 24, 2014 at 6:37 PM, Gregg Vanderheiden <gregg at raisingthefloor.org> wrote:
>> Hi Boyan, 
>> 
>> Comments below
>> 
>> And then lets talk. 
>> 
>> gregg
>> 
>> On Jul 21, 2014, at 10:18 AM, Boyan Sheytanov <bsheytanov at asteasolutions.com> wrote:
>> 
>>> Hi everyone!
>>> 
>>> A305.3, the Smart house online simulation is ending in August according to the DoW. At roughly the same time we will be running out of person months on the activity. Therefore, we have created an implementation plan for completing the simulation, which you can review in Google Drive. It is based on a discussion Gregg, Svetlana, and I had at HCII2014 in Crete. The summary is as follows:
>>> 
>>> We will support adaptations for low vision users in the appliances themselves.
>> GV:  √
>> 
>>> 
>>> We will support adaptations for cognitive and motor impairments via the phone as a controller.
>> GV:  √
>> 
>>> 
>>> We will support adaptations for the blind by ensuring the simulation is accessible via a screen reader.
>> GV:  Maybe you forgot — but what we discussed was showing that everything in the house could be controlled from their cell phone using URC.   Gottfried can help show you what that might look like.  Easy to simulate.  In total it would look like this
>> 
>> (With Blind KeyToken - (or the Physical Disability KeyToken) 
>> 
>> -  Text would appear onscreen (screen reader readable) that described the house.
>> 
>> - A Smartphone would appear onscreen to the right of the smart house
>> 
>> -  The following instructions would appear on screen (next to or below the smartphone) 
>> 
>> "People who cannot see the labels and screens on products, or who cannot physically operate their controls, can operate all of the smart products and features in the house from their cell phone.  For this simulation, a cellphone is shown on screen that you can control from your computer keyboard. If the user could not see - they would have their cell phone set to talk to them as the navigated it.  If they could see but not physically use the products then it would just be used to control the products.  People could also use their communication aid instead of a phone.  {You might edit this so that it would only talk about physical with physical KeyToken - and vision with a vision KeyToken}
>> 
>> Use the following keys on your keyboard - to navigate the simulated phone.
>> Down arrow - next item in list  (same as swipe-to-the-right for example on an iPhone)
>> Up arrow - previous item in list   (same as swipe-to-the-left for example on an iPhone)
>> Return key  -  Activate  item in list    (Same as double-tap for example on an iPhone)
>> left arrow - jump to top of list  
>> right arrow - jump to bottom of list  
>> Escape to exit the list and go back to previous list
>> {At the bottom of each list is a choice to  “go back to ….”   They can use either this menu item or the escape key to go back up one level}
>> 
>> The navigation then becomes as simple as navigating through a set of hierarchical lists like the following — with an action at each item. 
>> As they move to each item it is read aloud (in the Blind mode - but not in they physical disability mode).  
>> (the text in parentheses is read after a 1 second pause)
>> 
>> SmartHouse Features & Devices 
>> Television
>> Volume up
>> Volume down
>> Mute   (now off)
>> Captions  (now on)
>> Channel up  (currently 27)
>> Channel down   (currently 27)
>> Enter channel Now (currently 27)  (Use Keypad)
>> Last Channel 
>> Activate Menu (use escape key to exit and arrow keys to operate menus) 
>> {when activated - the menu would show up on screen and the arrow keys on the device would navigate it.  Escape would exit back out of control of it}
>> Activate Channel Guide (use escape key to exit and arrow keys to operate menus) 
>> {when activated - the menu would show up on screen and the arrow keys on the device would navigate it.  Escape would exit back out of control of it}
>> Enter Play Controls 
>> Play
>> Pause - Play  
>> Fast forward
>> Fast Reverse
>> Jump forward 
>> Jump backward
>> Exit play Controls  
>> Back to list of SmartHouse Devices
>> Stove
>> Front-Left burner Setting (Current 5) (use keypad or control-Arrowup/down) 
>> Front-Right burner Setting (Current 5) (use keypad or control-Arrowup/down) 
>> Back-Left burner Setting (Current 5) (use keypad or control-Arrowup/down) 
>> Back-Right burner Setting (Current 5) (use keypad or control-Arrowup/down) 
>> Oven Setting (currently off)
>> Off
>> Bake
>> Broil
>> Self-Clean
>> Back to stove settings
>> Set Oven Temperature now (Currently 0) (Currently Off) (Use Keypad)   {you could make it turn the oven on if they set the value to non-zero}
>> Preheat Status light (currently off)
>> Oven Timer
>> Time (currently 10:30 )
>> Set timer (currently zero) (Use Keypad. Hit enter to start.)    {if they enter 105 and pause for 1 second - it would say  “currently 1 minute and 5 seconds”.  if they then hit 5 it would say “currently 10 min and 55 seconds.   When they hit enter  it says  “Timer started”}
>> Reset / Silence Timer
>> Hit Enter to set Time
>> Automatically Set time
>> Hit Enter to Set Time Zone  (Currently  Central European Time)
>> Use arrow keys to choose time zone. then hit enter.  use escape to exit without changing time zone
>> Enter time now  (use keypad. hit enter to start)
>> Alarm Clock
>> Silence Alarm
>> Set Alarm (currently 7:50) (Use Keypad. Hit enter to start.)    {if they enter 105 and pause for 1 second - it would say  “currently 1:50”.  if they then hit 5 it would say “currently 10:55    When they hit enter  it says  “Alarm Set to 10:55”}
>> Hit Enter to set Time
>> Automatically Set time
>> Hit Enter to Set Time Zone  (Currently  Central European Time)
>> Use arrow keys to choose time zone. then hit enter.  use escape to exit without changing time zone
>> Enter time now  (use keypad. hit enter to start)
>> Coffee Pot/   {or whatever other things you have in house}
>> Front Door
>> Turn Intercom on/off (currently on) 
>> Release door catch for 5 seconds
>> Front Porch Light (currently on)
>> Lights 
>> Living room (currently on 10)  (use keypad to enter value. Enter to turn on/off)
>> Bed room (currently on 10)  (use keypad to enter value. Enter to turn on/off)
>> Kitchen (currently on)
>> Bathroom (currently on)  
>> Front Porch (currently on)
>> Back Yard (currently on)
>> Den (currently on)
>> Thermostat  {make it simple for now}
>> Temperature is 19 Celsius
>> Set Thermostat (Currently 20 Celsius) (Use keypad and enter)
>> Raise Thermostat 1 degree  (currently 20 celsius)
>> Lower Thermostat 1 degree  (currently 20 celsius)
>> ETC
>> 
>> 
>> This will give us a very nice solution for people who are BLIND, have LOW VISION (where they can’t read labels on things reliably), CAN’T READ,  have PHYSICAL DISABILITIES (reach etc).    It can also be used as the basis for people who are deaf being able to “see/feel” alerts through their phones.   (we can just show the phone with vibration lines around it (static)  — and describe how alerts/alarms would be sent to the phone )
>> 
>> ( what was proposed (simply making the simulation screen reader compatible) would not be very helpful —  it would only make it easy for people who are blind to see that the smart house is not accessible at all to them.)
>> 
>> 
>>> We will demonstrate conflict resolution between two users by defining rules for that in the simulation itself (since we won't have architectural support for that yet).
>> 
>> 
>> GV:  GOOD
>> 
>>> 
>>> 
>>> All other tasks won't get implemented (you can see them below line 14 in the spreadsheet linked above).
>> 
>> GV:  Lets talk.  In the end we need to demonstrate to the EC something that looks like it would be a deliverable in line with the amount of money in the budget for this work package. 
>> 
>>> 
>>> We plan to leave 0.5PMs in the activity for Year 4 -- so that we have allocated effort for responding to architectural changes and user feedback from the pilots.
>>> 
>>> Let me know if you have questions or comments.
>>> 
>>> Best,
>>> Boyan
>> 
>> 
>> -- 
>> Boyan Sheytanov
>> Lead Systems Engineer
>> Astea Solutions AD
>> http://www.asteasolutions.com
>> 
>> The information in this e-mail and any accompanying files is intended only for the recipients named above. This message may contain CONFIDENTIAL INFORMATION THAT IS LEGALLY PRIVILEGED. If you are not an intended recipient, you may not download, copy, disseminate, distribute or use in any way the information in this e-mail. Any of these actions can be a criminal offense. If you have received this e-mail in error, please notify Astea Solutions AD immediately by reply e-mail, and delete this e-mail and any copies of it.
> 
> 
> The information in this e-mail and any accompanying files is intended only for the recipients named above. This message may contain CONFIDENTIAL INFORMATION THAT IS LEGALLY PRIVILEGED. If you are not an intended recipient, you may not download, copy, disseminate, distribute or use in any way the information in this e-mail. Any of these actions can be a criminal offense. If you have received this e-mail in error, please notify Astea Solutions AD immediately by reply e-mail, and delete this e-mail and any copies of it.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gpii.net/pipermail/smarthouses/attachments/20140730/abbd3e6a/attachment-0001.html>


More information about the SmartHouses mailing list