Difference between revisions of "SCOTT talk:SCOTT-NO November 2017"
From its-wiki.no
Josef.Noll (Talk | contribs) (Created page with "= From Use Cases to Show Cases = * Starting point: use case scenario(s) * narrow down: == Challenges == Reviewer(s) and Forms: * Why do we need "harmonised deliverables"?...") |
Josef.Noll (Talk | contribs) (→From Use Cases to Show Cases) |
||
| (8 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
= From Use Cases to Show Cases = | = From Use Cases to Show Cases = | ||
* Starting point: use case scenario(s) | * Starting point: use case scenario(s) | ||
| − | * | + | * from use cases |
| + | * to development | ||
| + | * to implementation | ||
| + | * to demonstration | ||
| + | * to showcases | ||
| + | Each use case should have three categories for BuildingBlocks (BB) | ||
| + | # Need to have (for the functioning of the use case) | ||
| + | # Nice to have (could contribute to the use case, depends on developments and API) | ||
| + | # Future "enhancing the story" | ||
| + | Example: | ||
| + | * need to be established | ||
| + | |||
| + | https://www.helpnetsecurity.com/2017/01/05/iot-trust-framework/ | ||
| + | 37 principles for IoT trust framework | ||
== Challenges == | == Challenges == | ||
Reviewer(s) and Forms: | Reviewer(s) and Forms: | ||
| Line 14: | Line 27: | ||
Administrative overhead | Administrative overhead | ||
* ''bin-counting dominated: deliverables, excel, phone conferenes, coordination | * ''bin-counting dominated: deliverables, excel, phone conferenes, coordination | ||
| − | * | + | * too little focus on technical work |
| + | Impact on National and European Scale | ||
| + | * Driving forces are often the BuildingBlocks, not the use cases | ||
| + | * missing focus on ''showcases'' for SCOTT | ||
| + | * impact analysis for Europe: | ||
| + | ** Leadership (ECSEL) | ||
| + | ** Jobb creation | ||
| + | |||
| + | == WP showcases and updates == | ||
WP6 - coordinating | WP6 - coordinating | ||
| Line 26: | Line 47: | ||
* 25 installations Smart Home | * 25 installations Smart Home | ||
* Showcase: wireless services | * Showcase: wireless services | ||
| + | * Future Showcase: 5G Network slicing for Free Access to Health, Education and Governmental Information | ||
WP9 | WP9 | ||
| Line 44: | Line 66: | ||
WP21 - Assisted living and community care | WP21 - Assisted living and community care | ||
| − | * | + | * showcase: fall sensor |
| + | * showcase: diabetes monitoring | ||
| + | * future showcase: 4.75G Network Slicing (interoperability: health care and alarm services co-ordinating) | ||
BUZ cooperation | BUZ cooperation | ||
* F-Sense as SDK to EyeNetworks, TellU and Telenor | * F-Sense as SDK to EyeNetworks, TellU and Telenor | ||
| + | |||
| + | == Future: Assessment of Technology== | ||
| + | SP1 suggestion: assessment of each requirement | ||
| + | * assessment of implementation of requirements | ||
| + | * based on state of implementation | ||
| + | * Draft proposal D1.1. | ||
| + | * Proposal: Adding more granularity | ||
| + | * "readiness level" | ||
| + | |||
| + | Suggestion: High-level view | ||
| + | * focus on building blocks | ||
| + | * SP1: Requirements (''driving the project?'') | ||
| + | * SP2: '''The story of future services and their requirements''' (use cases) | ||
| + | * SP3: '''Technology development''' | ||
Latest revision as of 13:51, 30 November 2017
Contents
From Use Cases to Show Cases
- Starting point: use case scenario(s)
- from use cases
- to development
- to implementation
- to demonstration
- to showcases
Each use case should have three categories for BuildingBlocks (BB)
- Need to have (for the functioning of the use case)
- Nice to have (could contribute to the use case, depends on developments and API)
- Future "enhancing the story"
Example:
- need to be established
https://www.helpnetsecurity.com/2017/01/05/iot-trust-framework/ 37 principles for IoT trust framework
Challenges
Reviewer(s) and Forms:
- Why do we need "harmonised deliverables"?
- Focus on impact of use case
Real-world relevance
- from use cases to development to implementation to demonstration to showcases
Administrative overhead
- bin-counting dominated: deliverables, excel, phone conferenes, coordination
- too little focus on technical work
Impact on National and European Scale
- Driving forces are often the BuildingBlocks, not the use cases
- missing focus on showcases for SCOTT
- impact analysis for Europe:
- Leadership (ECSEL)
- Jobb creation
WP showcases and updates
WP6 - coordinating
WP7 - Air Quality -
- showcase: Smart Remmen and VTT
- extended by management
- Workshop as main showcase
WP8 - Managed Wireless
- 25 installations Smart Home
- Showcase: wireless services
- Future Showcase: 5G Network slicing for Free Access to Health, Education and Governmental Information
WP9
- 20 scenarios, define "new scenario" using 3 building blocks: ABAC, ...
- showcase: facility management in Gdansk (replay from DEWI)
WP13 - Trustable Wireless vehicle communication network
- 4 PM EyeNetworks - smart sensors
- 2 PM moved to WP26, due to required manpwoer for meas. sec development
WP14
- 1 PM move to WP26
WP15 - Vehicle as sensor (related to WP9)
- UiO 3 PM - 1 PM used, 1 PM used
- SmartIO 3 PM -> moved to WP8
- Telenor, Wolffia, HiOA
WP21 - Assisted living and community care
- showcase: fall sensor
- showcase: diabetes monitoring
- future showcase: 4.75G Network Slicing (interoperability: health care and alarm services co-ordinating)
BUZ cooperation
- F-Sense as SDK to EyeNetworks, TellU and Telenor
Future: Assessment of Technology
SP1 suggestion: assessment of each requirement
- assessment of implementation of requirements
- based on state of implementation
- Draft proposal D1.1.
- Proposal: Adding more granularity
- "readiness level"
Suggestion: High-level view
- focus on building blocks
- SP1: Requirements (driving the project?)
- SP2: The story of future services and their requirements (use cases)
- SP3: Technology development