|
|
Events and Incident Definition
Working group leader:
Marco Dozza, Chalmers, Email
Mikael Ljung Aust, Chalmers, Email
Participants:
A core group will be invited directly, other members will be invited through mailing lists.
Activities, planning, results, meetings:
Task
|
Who
|
Deadline
|
How
|
Result (milestone)*
|
|
1. Collect previous work on events and incidents definition
|
WG leader
WG leader
|
Beginning of March 2012
End of March 2012
|
|
Report compiling existing incident and event definitions
|
|
2. Select and invite core group and make list of other members
|
WG leader
|
End of March 2012
|
Physical or telco/ webinar
|
List of members in core group
|
|
3. Brainstorming by inviting to an open meeting for input on the topic
|
Core group
|
Spring 2012
|
Physical or telco/ webinar
|
|
|
4. Identification of specific items that need to be worked on, and have different categories of people give input on them
|
Core group and other members
|
Summer 2012
|
Telcos and meetings in conjunction with conferences
|
List of targeted items
|
|
5. Write a proposal for improved event and incident definitions
|
WG leader and core group
|
September 2012
|
Webinars, FOTNET international workshop 2012
|
Draft proposal
|
|
6. Arrange workshops for additional inputs on the proposal.
|
Core group and other members
|
Spring 2013
|
|
|
|
7. Finalize the proposal including identification of issues needing research to be properly addressed
|
WG leader and core group
|
Fall 2013
|
|
Report on the new suggested event and incident definitions including recommendations for focused research on remaining issues
|
*Additional milestones are status reports and stakeholder meetings and international workshops in M15, M21, M23, M34 and M35.
Download the WG description: .pdf (56.1 KB)
|
|
More about our events
|
 |
|
More news
|
|