1. Artemis Repository WG Petri Liuha, Nokia
ARTEMIS Industry Association The association for R&D actors in embedded systems

2. Artemis Repository WG
Collect Artemis projects results that projects are willing to list
Openness levels
title+description+keywords (desired minimum level) -> contact owner
demo app -> try out, contact owner
source licensed by owner -> contact owner, try out, agree on terms for use
fully open source-> download and try, community effort
Searchable results
No liabilities
User monitoring and registry? User agreement?
Default: project handles
Collect user statistics for Artemisia to publish

3. Roles and contributors
Chair
Comms
Information storage & IT
Domain experts
ASP “chairs”
Automotive, rail, aerospace, manufacturing, mobile, health
Multicore, UI, connectivity, computing platforms, middleware
modelling tools design tools, test tools
Project coordinators
Project experts

4. Results from Breakout:
Vision: embodyment of ARTEMIS way
Target group: R&D community in Europe & world. Technical people!
Purpose:
Make results available to R&D community.
Build on results of previous projects (premarily Artemis).
Set-up info for new projects.
Promote results: window showing impact of results, with info on use of results.
Snap-shot of industrial priorities coverage.
Support for CoIE network building.

5. Results II
Motivation for projects to upload: make research available for actual use (productise). Shop to show info on results.
Example: SMARCOS uses SOFIA results
Structure and screening? Allow competing solutions. Entry gate needed to avoid pollution.
Content in Repository: pointer towards owners, open source pointers, reports, abstracts, video’s of demo’s.
Information on results with point-of-contact (voluntary by consortium).
Links to SourceForge
IPR rights. Impose?
Categories?

6. Results III Accessibility: access for IA members only?
Different levels of access, more info for members.
Dynamic upload accessible for all project partners, with a signed form that nobody objects in the project.
For new projects: refer to results in repository. Obligation to list to contribute to the repository.

7. Results: implementation
Initialise: ask projects: what to put in it? and why?
Organise results: different domains, reflect levels in value chain in the repository structure.
Push consortia to put information.
Implementation: IA or NoE?
NoE: distributed effort
Conditions: FRAND
Rich presentation tools: video for demo’s.
CSA project? Public procurement?

8. Actions:
Create a plan for adoption in Steering Board Co-Summit.
Advertise the Repository at the Co-Summit
Active people: Elena, Alun, Andrei Lobov, Patrick.