EGI Pay-for-Use PoC:Business Cases/Workplan

From EGIWiki
Revision as of 00:03, 28 February 2014 by Davidb (talk | contribs) (By Roles)
Jump to: navigation, search
Pay-For-Use menu: Home Processes/Instructions Service/Price Overview Service Management Legal/Policy Actions Meetings

List of selected business cases and overall workplan of agreed activities.

(To be developed)

Business Cases


  • Consumer (User): The person actually using the service (user).
  • Customer: The person or entity that negotiates the level of services and commissions the service provider or broker and may pay, doing so on behalf of a number of consumers (users).
  • Resource Provider: An organisation offering access to ICT resources through service abstractions (e.g., computing power, storage).
  • Broker: An organisation facilitating or arranging transactions and agreements between a customer and one or more resource providers.
  • Technology Provider: A person or entity providing the required technology to support service delivery.

User Stories

A list of potential questions that each role may ask or scenarios that will lead to the developments required:

See wikipedia page


Define, at least, the "first level" or "base" service we are going to provide for each class of services.

By Roles

  • Consumer: I want a list of the available services and their price
  • Consumer: Who helps me when issues arise ? Is this help cost and how much?
  • Consumer: Where do I get information about your services?
  • Consumer: How can I access your services? Do you have a portal or something similar?
  • Consumer: What is the price? Is it cheaper than the commercial cloud?
  • Consumer: If not, what is the difference with commercial clouds? What are the advantages or using yours?
  • Consumer: How can I pay for the services? Credit Card?
  • Consumer: Can I receive a formal invoice with my requirements to put it into my budget?
  • Consumer: How can I be sure the price is equal to the quality of resource?
  • Consumer: Are any other communities paying for resources?
  • Consumer: Do you have Windows?
  • Consumer: Do you support products with licensing (like ANSYS, that only allows licenses for a given customer, not shared) even if the license machine is at my site behind a firewall? how?
  • Consumer: Do I get a contact to phone/mail who will be reliable? what time can I call?
  • Consumer: Will the service be there for next 12 months?
  • Consumer: Can I test for free? (only next 12 months or so)
  • Consumer: Is your firewall open for what I need?
  • Consumer: I can't ftp, do you support dropbox?
  • Consumer: Do I need a certificate? who gives it?
  • Consumer: Do I get a machine/service for me immediately at any time? will the machine be too busy? is the data transfer too slow? can I use Teamviewer?
  • Consumer: Is there a Service Level Agreement?
  • Resource Provider: I want to set a price for the Grid Compute service on a HEPSPEC-hour (or hour?)
  • Resource Provider: I want to set a price for the Cloud Compute service based on ....
  • Resource Provider: I want to set a price for the Grid/Cloud Storage service based on GB per month
  • Resource Provider: How much extra effort & on how many people does this require, and at what level?
  • Resource Provider: Can I pay such extra effort to those people?
  • Resource Provider: If I give a contact name, how many mails/calls will she/he receive?
  • Resource Provider: When do I get the extra fund and under what constraints?
  • Resource Provider: Can I reject potential users that will create more problems than benefits? On what basis?
  • Resource Provider: What are the legal issues if the customer is not in my country? will digital certificates be used?
  • Resource Provider: Do I know these users? (example, bitcoin "researchers") Does it make sense to work with them even if they say they work on research or innovation?
  • Resource Provider: Can parts of administration be outsourced? If so, what are the service costs? What are the benefits?
  • Resource Provider: What agreements do I have to make and with whom?
  • Resource Provider: Does VAT apply? If so, when?
  • Resource Provider: We are a publicly funded institution, are there any known restrictions for selling services?
  • Technology Provider: What technologies are you lacking that we could offer or develop? Can I develop pay-per-use tools and deploy them? Can I charge for that?
  • Technology Provider: How do I get paid? who pays me? when?
  • Technology Provider: Who is our interface for e.g. agreements/contracts, requirements, improvement, support?
  • Technology Provider: Can I deploy a contextualized solution? (may need to explain this)
  • Technology Provider: Do you run on Windows?
  • Technology Provider: Does it make sense to prepare something for mobile phones? (guessing no)
  • Broker: What agreements do I have to make and with whom?
  • Broker: How do I get paid? who pays me? when?
  • Broker: Do customers prefer a % and/or flat rate for broker services? Will it depend?
  • Broker: How is revenue shared in federated service provision? (e.g. GOCDB, Acct Portal)
  • Multi: Do I have to get involved in the communication between provider and user after an agreement/contract is signed? If yes, how do I get a percent or a contract for support?
  • Multi: How can I teach this to the users?
  • All: How can I learn what is this about?

Workplan Overview

January 2014: Kick-off of the activity

  • Hold first call - 23 Feb 2014 @ 12:00 CET (TBC)
  • Establish fixed day and time for semi-monthly calls

April 2014: First phase implementation of all technical specifications, list of required agreements and refinements to policy issues documented in the EGI Sustainability Plan (M48)

  • Technical
    • Review technical detail table and complete with relevant information
    • Associate prices within GOCDB according to instructions provided here
    • Accounting Portal to make required extraction from GOCDB and accounting for usage
      • Pull the site data and create a table for use in displaying charging. This table should be directly viewable, at least for the pilot.
      • Create test cpu view like the cloud one. Best to base it on the Custom_View so that we can select particular VOs relevant to the pilot.
    • Investigate and implement a billing function (initially a virtual bill)
    • Perform a gap analysis of supporting services (either new or extensions to the current tools) that would enable the increased automation of the process once it has been manually established and subsequent development required for missing functionality.
    • Report back on identified issues and overall progress
  • Policy/Legal
    • Identify and evaluate legal, policy, and organisational issues around the full implementation of the pay-for-use model (review initial information from first survey)
    • Articulate appropriate business and responsibility models (review initial broker models developed)
    • Request potential consultation from FedSM regarding service management processes and agreements.
    • Collate information to be presented within Sustainability Plan that is easily digestible (Lead:

May 2014: Pay-for-Use aspects included in Federated Cloud release (even in Beta/pre-production)

  • Identify members involved in the EGI Federated Cloud to serve as pay-for-use representatives
  • Gather requirements from the EGI FedCloud for its inclusion

June 2014: First presentation of activities and feedback from EGI-InSPIRE EC Review

  • PoC to decide what information to be presented and ultimate goal

October 2014: Conclusion of phase 2 activities: updates from feedback and overall refinements

  • TBD based on activities carried out. Dedicated F2F to be discussed either following EC review or other date TBD (e.g. Sept 2014).

December 2014: Circulation/Publication of Final Proof of Concept Report

  • To be included in final EGI-InSPIRE Periodic Report (Lead: with requested contributions from PoC members)