IDoT telecon 2013-

12-

03

Date and Time

• Tuesday, Novmber 19, at 9am PT (time chart)
  • Voice: Skype: +99051000000481 or US +1-805-309-2350Image Removed / Alternate Toll +1 (714) 551-9842Image Removed (international dial-in lines), room code 613-2898#
  • (Turbobridge call options)

Agenda

• Roll call
• Action item review
• New hour/date for our bi-weekly call
• IDoT work items (I’d like to discuss this points with you)
  • Filling in the use-case table
  • Landscape paper
  • IDoT Paper (ownership, who owns the data in a thing, mapping&name-spaces…)
• IDoT use-case collection
/ next steps
• AOB

Minutes

Minute taker: Keith UberIngo Friese

Action item review

review

IDoT Use case collection

Continuation/recap of list discussion on risk of having a single protocol/channel for all things.

An earlier shared presentation may have lead readers to believe that the plethora of protocols is a problem in itself.

Scott Jensen had categorized things into three layers

• measurements / actuators
• control
• coordination

(supervisory, control, data acqusition)

Consensus was that the categorization is okay and we can try to map our use cases to these.

Action Point 1:

To try to iteratively build a spreadsheet with the SCADA classfiications down one axis and a common feature/functionality on the other access - iterating on the categories and structure of the sheet of course

- Colin volunteered to start

Closed: Colin sent an exel-sheet with a schema to the mailing list 

Action point 2:

Find an existing or come up with a list of existing proprietory protocols

Show how many various protocols are around and to see the state of the art.

• SCADA
• CAN-bus
• Serial comms
• etc

- Sal volunteered to start a page

Closed: Sal sent it to the ist

IDoT Use case collection

It was agreed that

Attendees

• Frank Mildner
• Ingo Friese
• Benoit Ball
• Keith Uber
• Jeff Stollman

excused

• Sal D'agostino

Next Meetings

Tuesday, November 26, at 9am PT (time chart)