Buildings NA3.2.3 - Exploitation Strategies: EMI Strategy Paper


Develop an "EMI strategy Paper" to have a clear EMI strategy as an independent task from Science Soft Activities.

Related Work: Other Strategic Documents/Papers"

  • e-Health
    • An action plan for a European e-Health Area [ PDF ]
  • Research Networking
    • NORDUnet Strategy 2009-2012 [ NORDUnet_Strategy_2009-2012_Final.pdf ]
      Many NRENs have developed written strategies lately; unfortunately not all of them are public. This one is commendably short (8 pages) and follows the classical structure pretty well: Vision, mission, core values...

TOP 5 TOPICS for the Strategic Paper

Morris Top 5 Topics

(1) e-Science through Middleware: We have to take ownership of the task to demonstrate that middleware is required for e-Science underpinned with evidence. This opens the ears of funding organizations and perhaps even larger user communities.

(2) European Leadership in middleware development: the middleware in Europe is the most used ones world-wide for the e-Science infrastructures. We are eager to continue this leadership with institutes commitment.

(3) Benefits of loosely coupled cooperation in Europe: demonstrate that collaboration makes sense encouraging healthy competition in science and avoiding the re-development of existing related work.

(4) ScienceSoft as continuation of EMI and its chances for scientific and open source markets.

(5) Outline envisaged landscape in e-Science for the next 5 years including new data wave aspects faced in science and engineering.

Oxana Top 5 Topics

0. Future form of collaboration: a consortium, a foundation, a project, a forum etc; or maybe no collaboration at all, apart of existing frameworks like UNICORE, NorduGrid, OGF etc (I don't know the answer, but the latter seems to be most realistic)

I'd say that this is the one and only really strategic decision that EMI must make now. Everything else depends on the outcome of this decision.

1. Define target customers: primarily research infrastructures, or primarily businesses, or some mixture (I'd say, it is only research). In the same vein, we must decide whether we want to stick with existing customers, or attempt to expand to new infrastructures within Europe.

2. Partners should express their commitment (or absence of such) to common standards and approaches developed during EMI, and possibly to be developed in future.

3. Funding: strategic step is to decide whether support should be sought from EU, or from national governments, or from individual research projects, or in a commercial manner. These decisions can even be made on per-product basis.

4. Place on the global arena: do we want to penetrate "markets" outside Europe, possibly attracting contributors, or do we stay chiefly within Europe.

Peter Top 5 Topics and Comments

Based on what I already mentioned on the last week meeting I would have the following comments: * In the sections From mw to Scientific Results I would mention the ecosystem of the science. How science works? What brings scientific results forward? How simulations, computers, supercomputers help in achieving them? * I would also put something like European middleware in Europe landscaping the potential user communities like CERN, PRACE, the Nordic communities, etc.

> What would be your top 5 strategic topics this document should cover?

Mine in the order of preference:

1. Research and e-infrastructures tomorrow 2. Loosing European leadership... 3. Non-interoperable mw 4. From the mw to scientific results 5. EMI brand - SWOT

TOC Reviews

  • 2012-09-10 - Draft TOC after NA3 Telcon on 2012-09-05: [ doc ]
  • 2012-10-22 - TOC after NA3 Circulation with Oxana's comments [doc]:
  • 2012-11-28 - TOC with task assignments of NA3 members [ doc ]


  • 2013-01-24 - Input for various sections (Peter) [ doc ]
  • 2013-01-02 - "unstable middleware" section input (Jon) [ doc ]
  • 2012-12-20 - input for various sections (Simon) [ doc ]

Report based on PEB comments and received inputs

  • 2013-05-20 - compiled Report for PEB and NA3 Review [ pdf ]
Topic attachments
I Attachment History Action Size Date Who Comment
Microsoft Word filedoc EMI-DOC-WP6-EMI-Strategy-v0-01.doc r1 manage 102.5 K 2012-09-10 - 12:29 MorrisRiedelExCern EMI Strategy (v.0.01) - TOC after NA3 Telcon on 2012-09-05
Microsoft Word filedoc EMI-DOC-WP6-EMI-Strategy-v0-02.doc r1 manage 114.0 K 2012-10-22 - 21:34 MorrisRiedelExCern EMI Strategy (v.0.02) - TOC after NA3 Circulation with Oxana's comments
Microsoft Word filedoc EMI-DOC-WP6-EMI-Strategy-v0-03-SL0.doc r1 manage 125.0 K 2013-01-30 - 09:55 MorrisRiedelExCern EMI Strategy Paper - Various inputs (Simon)
Microsoft Word filedoc EMI-DOC-WP6-EMI-Strategy-v0-03.doc r2 r1 manage 117.5 K 2013-01-30 - 09:44 MorrisRiedelExCern EMI Strategy Paper - Input unstable middleware (Jon)
Microsoft Word filedoc EMI-DOC-WP6-EMI-Strategy-v0-03_sp.doc r1 manage 134.5 K 2013-01-24 - 14:33 UnknownUser Strategy document including Peter Stefan's parts.
Microsoft Word filedoc EMI-DOC-WP6-EMI-Strategy-v0-10.doc r1 manage 127.5 K 2013-05-20 - 12:52 MorrisRiedelExCern Compiled Strategy Report v0.10 for PEB and NA3 review (doc)
PDFpdf EMI-DOC-WP6-EMI-Strategy-v0-10.pdf r1 manage 271.5 K 2013-05-20 - 12:52 MorrisRiedelExCern Compiled Strategy Report v0.10 for PEB and NA3 review (pdf)
PDFpdf NORDUnet_Strategy_2009-2012_Final.pdf r1 manage 60.4 K 2012-09-03 - 15:00 SimonLeinenExCern NORDUnet Strategy 2009-2012. Source:
PDFpdf com2004_0356en01.pdf r1 manage 298.0 K 2012-08-27 - 13:32 MorrisRiedelExCern An action plan for a European e-Health Area
Edit | Attach | Watch | Print version | History: r9 < r8 < r7 < r6 < r5 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r9 - 2013-05-20 - MorrisRiedelExCern
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    EMI All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2021 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
or Ideas, requests, problems regarding TWiki? use Discourse or Send feedback