| Service overview | Data storage providers and applications representing individual users subscribe to data through a well-defined interface Subscriptions are activated by matching notifications |
|---|
| Service name | Data Subscription Service |
|---|
| Service area | Discovery of data set changes and user notification |
|---|
| Service phase | Working Proof of Concept |
|---|
| Service description | High-level description of what the service does in terms of functionalities it provides and the resources it enables access to |
|---|
Customer group | Type of customers who are allowed to commission this service. Restrictions may apply according to various criteria like the location (e.g. country) or type of activity (e.g. research, commercial). By customer, we mean an organisation a service provider to receive one or more services, doing so on behalf of a number of users; customers commission a service but do not necessarily use it; users use the service but do not necessarily commission it |
|---|
| User group | Type of Individuals that primarily benefits from and uses a service |
|---|
| Value | The benefit to a customer and their users delivered by a service; benefits are usually related to alleviating pains (e.g., eliminate undesired outcomes, obstacles or risks) or producing gains (e.g. increased performance, social gains, positive emotions or cost saving). |
|---|
| Tagline | 1-line value proposition (max XX words to be derived from value) |
|---|
| Features | List of distinct characteristics for this service |
|---|
| Service options | | Option | Name | Description | Attributes | |
|---|
| 1 | Add a name for this option | Add a description for this option; this description is targeted to potential customers who need to understand what each option is about and being able to choose the best for their needs | Add attributes as numbered bullet lists in the form of 1. attribute name: [possible values] 2. attribute name: [possible values] ... | | | 2 | | | | | | 3 | | | | |
|
|---|
| Access policies | Policies stating how the service can be accessed, examples are: Policy-based: users are granted access to the service based on policies defined by the EGI service provider(s) or by EGI.eu; Wide access: users can freely access the service provided; Market-driven: users can negotiate a fee to access the service either directly with the EGI service provider or indirectly with EGI.eu |
|---|
| Service management information | |
|---|
| Service owner * | EUDAT |
|---|
| Contact (internal) * | Jani.Heikkinen |
|---|
| Contact (public) | External contact (e.g., e-mail, phone) to ask information about the service |
|---|
| Request workflow * | Description of the workflow that a customer needs to follow to request the service |
|---|
| Service request list | List of requests that a user can submit to the service desk during the provision of the service |
|---|
| Terms of use | URL to a document containing the rules which one must agree to abide by in order to use the service |
|---|
| SLA(s) | Link to URL to a document containing information about the levels of performance that a service provider is expected to achieve (service level agreement) |
|---|
| Other agreements | List of agreement documents that are associated to this services (e.g. OLA, UA) |
|---|
| Support unit | Name of the support unit in the EGI Helpdesk |
|---|
| User manual | URL to the user manual for this service |
|---|
| Service architecture | |
|---|
| Service components | List of service components that are the minimum required to make the service available and their TRL | # | Type | Name | Description | TRL [1] |
|---|
| 1 | Choose: Enabling or Enhancing Definitions: - Enabling service components are the minimum set of service components that make the service available - Enhancing service components are any additional service components that improves the service, however, the service would still run without them, even if at lesser quality. | Name of the component | | | | 2 | | | | |
|
|---|
| Finances & resources | |
|---|
| Payment model(s) | Supported payment models and restrictions that apply to each of them; example of types of payment models are: free, pay-as-you-go, subscription, membership to corporate customers , higher education, etc. |
|---|
| Pricing | Describe the price scheme for this service in case the customer is charged for access/usage |
|---|
| Cost * | The costs required to develop (CAPEX) and maintain/operate (OPEX) the service in the best case, e.g. human effort; financial investment |
|---|
| Revenue stream(s) * | e.g. public funding, membership fees, in-kind, paid (specify price) |
|---|
| Action required | List the actions that are required to complete the service portfolio entry according to the specific service phase; if no actions are required, write 'no' |
|---|