Date and Time
- Tuesday, December 03, at 9am PT (time chart)
- Voice: Skype: +99051000000481 or US +1-805-309-2350 / Alternate Toll +1 (714) 551-9842 (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
- AOB
Minutes
Minute taker: Ingo Friese
Action item review
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
New hour/date for our bi-weekly call
IDoT Use case collection
It was agreed that mapping use-cases to the SCADA (Complexity) scheme is a good exercise in order to:
1.) Classify the use-cases in easier, and more complex ones
2.) Check whether all sub-use cases (ID, owner, registration, identification, mapping, authentication, authorization, policies etc.) are covered
Ingo started as an example with the “Runaway use-case”.
Action point 1:
Analyse our current use-cases and identify the sub-uses cases regarding the complexity scheme (see also "Runaway dog" example)
- All use case authors
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)