Easy integration of the Internet with Things: Calendar Subscription and  Syndication
Sunday, March 11, 2012 at 05:11PM
Toby Considine in Energy, Schedules, Smart Energy, Standards

I use Outlook in my day to day life. It shows me an aggregate calendar, with meetings I accept at the office (one account) meetings I accept not at the office (another email account) and two corporate calendars: one based in Exchange, and one in SharePoint. When I was working on the national smart grid roadmap, my Outlook showed the calendar of that SharePoint project as well. In Outlook, I can turn each calendar off or on, and when aggregated, each appointment was a different color by source. I live by Calendar aggregation.

In my Phone, which happens to be an Android, I used to have a calendar for each email account. Each has different security set-ups and realms. Each source has different policies about sharing calendar on distributed devices. It was easy to miss appointments when on the road as I switched between different companies.

With an overnight upgrade pushed out by my phone company, this changed to a single calendar. That single calendar is color coded, showing the source of each event. Some of the things that are on my phone are “not quite meetings”, when GMAIL has interpreted something as a meeting although I have not accepted the meeting. The rules GMAIL uses for this appear to be similar to, but not identical to, the workings of Google Calendar.

Because I speak regularly in front of large audiences, I am always working in concrete examples of abstract issues. I use my phone as a prop when talking about the problem of smart homes and vehicle charging. The narrative goes as follows:

I may choose to create additional information within the house. The party, family church, Sunday afternoon football viewing may all be events originating in a house-based schedule and not appearing in any of the subscribed calendars. Or perhaps the household calendar is just another subscribed calendar fed into the syndication. That is an implementation detail that no one but the magnet-on-the-refrigerator computer needs to know.

My phone Calendar, then is an aggregation of calendars that I potentially syndicate out to other calendars.

If we flesh out the needs of the electric car, negotiating expensive fast charges and cheap slow charges, it needs to negotiate only with this household schedule. It may learn its own secrets, such as how far I drive when I go to choir practice. It may learn off-the-schedule stuff, such as that I frequently stop at the bar (an extra 10 miles of driving range) on the way home from choir practice. It does not need to share that information upstream to my house, or with my electric utility. It merely uses this information itself to make decisions autonomously about charging strategies.

The car has its own calendar for sharing. Based upon what it has learned, not only about my schedule (from the house) but about my habits, it can create a schedule of charging needs. It syndicates *that* schedule to the house, and negotiates with the house for access to market. The house syndicates the requirements from all the systems it supports, and uses them to guide it market position in energy.

The same calendar may be syndicated in different ways. The house subscriptions may include multiple children of the same syndicate. The house may learn from its subscription to my Android that I am out this evening, and do not need heat and lights in my rooms. The house may learn from the Calendar in the car, that I need power before this evening to support that same trip out. It is OK for the syndication to affect the houses buying position twice. There is no need for round-tripping or end-to-end tracking. The information is consumed, decisions are made, and market positions are created.

OK, this is a nice tale of autonomous systems relying on aggregated schedule streams to create time-dependent market positions. It is time to start thinking about Calendar Subscription. Aggregation, and Syndication, and of touch-less integration with the Internet of things.

Article originally appeared on New Daedalus (http://www.newdaedalus.com/).
See website for complete article licensing information.