Kantara Information Sharing Work Group

Date and Time

• Date: 9th, November, 2009#
• Time: 9 PDT | 12 EDT | 5PM UK

Attendees

• Iain Henderson (voting)
• Trent Adams (voting)
• Joe Andrieu (voting)
• Colin Soutar (voting)
• Henrik Beiring (voting)
• Joe Lackey (observer)
• Joni Brennan (staff)
• Brett McDowell (staff)

Apologies

• Eve Maler
• Mark Lizar

Agenda

1. Quorum and Voting
2. Previous meeting minutes
3. Car Buying Scenario

Minutes

1. Quorum and Voting

The group did not reach quorum on the call, and thus did not vote on previous meeting minutes.

2. Car Buying Scenario Development

We worked on the sections shown below, the text below being where we ended up at the conclusion of the call.

7c
Over the course of using her vehicle and getting it serviced, Sally learns about the Road Warrior program that the manufacturer offers to help customers who take frequent Roadtrips. She had heard about this on one of her favorite TV shows and it came up in her Twitter feed recently. She visits the manufactuer's website and signs up, pointing them to her personal datastore, and provisioning a variety of services for specific, limited acces to her driving data. This information is shared under the Kantara Information Sharing Agreement.

She authorizes anonymized use of her usage data for civic planning and road maintenance.

Provisioning Terms for Civic Planning and Road Maintenance:

Data set
Driving data
Space-time travel (location & time while driving)

1. Passengers
   Type of car (Make, Model, Year)
   License Term
   License Term (duration): 1 year
   Use
   Use: civic planning and road maintenance
   Retention
   immediate use
   planning
   archive
   Propagation
   No propagation other than exceptional circumstances as defined in the KISA.
   "Anonymized" needs further definition

She also provisions the manufacturer for access to her "roadtrip" travel dates and in-car location information for use by the Road Warrior Program. And she requests "speed trap" notifications, construction alerts, amber alerts, and emergency alerts. Finally, she approves identified use for smart offers from her list of approved suppliers when she's in their neighborhood.

Sally's unique ID in her driver's key logs her into the Road Warrior system when she drives. As she travels, occasional relevant notices appear on the dashboard interface. Sally also has the pleasure of knowing her usage data is being smartly utilized in an anonymous fashion to help manage and develop the roadways.

7d. Personal RFP integrated into GPS
On her way home from a customer visit, Sally asks the Road Warrior Negotiator interface to find her a good spot to fill up the tank. The system analyzes her route and sends out a personal RFP to those stations within 1000 feet (1/5 mile). Those online respond with a customized bid for gas. For those not online, the Road Warrior system responds with their known pricing data where does this data come from today&. She picks one and a visit to that station is calculated into her route.

How does she pay and/or identify herself to the station, if at all?
On her drive, she stops and gets the gas...

Another: husband has different road warrior preferences and doesn't want to be notified of the stuff she has.

8. Manage Problems
8a. Problem with the Engine (2nd opinion)
There is an engine malfunction. Unfortunately, the repair company says the problem isn't covered by warranty. In response, Sally sends the diagnostics from the repair company and the vehicle maintenance history to an expert for a second opinion. The expert reviews the information points out that this is a common problem (with that engine) and identifies the intermediate repair in her history that actually reset the warranty to another 3 years, so the current repair /is/ under warranty.

8b. Escalation
From the Road Warrior interface, Sally escalates this problem directly to Chryota. She explains the issue, specifically provisioning access for Chryota to view the repair company diagnostics, her maintenance record, and the expert review. She selects from the drop down list for her issue, "Other", and fills in the text block as "Warranty Dispute".

8c. Resolution
The message is tracked into Chryota's CRM system and is received by a customer support representative. The representative is directed to Sally's inquiry. Based on the description, the CRM system has suggested five possible issues from the Chryota knowledge base. The representative reviews the data from Sally and finds the appropriate business rule. The representative checks the criteria for approving the repair and determines that Sally's case is, in fact, covered by the warranty. This determination is recorded in the CRM system and communicated back to both Sally and the repair company provider. The repair company gets the message and sends confirmation to Sally that the repair will be handled free of cost to her and that she can come pick up the vehicle after 4PM today.

9. Manage Exits

A few thoughts...

Changing personal needs. Another baby, goes from compact prius to the mini-van.
After a considerable time, or any number of problems, Sally quits the relationship.

Problems, exit
End-of-product-life, exit
End-of-life, exit
Changing personal needs, exit *(we'll do this one) Sally chooses a non-Chryota vehicle.
Data retention, expulsion, extraction/export, communication permissions

Next Meeting

Monday 16th November, 9am Pacific, Midday Eastern, 5pm UK

Skype: +9900827042954214
US Dial-In: +1-201-793-9022
UK Dial-In: +44 (0) 8454018081
Room Code: 2954214

NOTE: Do not follow the code with a "#" symbol as it may cause the code not to be recognized.