The Use Cases Repository is a centralised archive used for managing and storing data related to Use Cases (UC) within the Horizon projects contributing to BRIDGE. It has been developed under Action#1 of the Data Management Working Group (DMWG) of BRIDGE.
The repository contains structured information on Use Cases developed by the Horizon Projects participating in BRIDGE, including step-by-step descriptions, objectives, KPIs, actors, diagrams, data, requirements, etc. The Use Cases are described following the IEC 62559-2:2015 Standard. All Use Cases published in the Repository must be reviewed by Action#1 of DMWG to check the completeness and compliance with the IEC 62559-2:2015 standard.
The Use Cases Repository is open to any visitor accessing the Smart Electricity Systems website of the JRC. At the moment, the adopted policy is to make publicly available the contents published in the Use Cases repository. Published Use Cases can be read and downloaded without logging in to the JRC portal with an ECAS account.
If you want to know more about the repository, please email Action#1 of the Bridge Data Management Working Group: secretariat@horizon-bridge.eu
Horizon projects in BRIDGE are allowed to upload one or more Use Cases in the Repository defined within their projects. Action#1 of DMWG coordinates and organises the contributions to be published in the Repository coming from the Projects participating in any Working Group of BRIDGE. Representatives from Horizon Projects participating in BRIDGE have to contact DMWG and ask to contribute to Action#1.
Action#1 organises shifts for Horizon Projects to upload their Use Cases to the Repository. Once a Project uploads a Use Case draft, it will be reviewed by an Evaluator from Action#1, who can request improvements before publishing it. If you are a member of the BRIDGE community working on a Horizon Project and you want to share a Use Case, please contact Action#1 of DMWG in BRIDGE first.
If you want to contribute by creating one or more Use Cases from your Horizon project, you have to get in touch with the Action#1 Leader of DMWG first to coordinate your contribution. Differently from the consultation of the published Use Cases, to upload any content in the Repository, you have to log in with your ECAS account. In addition, the Action#1 leader has to enable the ECAS account as “Author” in the JRC web portal (to prevent malicious access to the repository).
Once a BRIDGE member is logged in and enabled as “Author” by the DMWG Action#1 leader, (s)he can start creating a Use Case in the Repository. The procedure to create a Use Case is described in the guidelines, so the Author has to fill in each one of the mandatory fields of the Use Case form.
At the moment, it is not possible to upload a Use Case through any file (.docx, XML, etc.); so a Use Case has to be created manually by filling in the different fields of the form. Instructions on the Repository and Use Case creation are available in the guidelines, too.
All information uploaded during the creation of a Use Case is stored in the JRC web portal and can be made publicly available to any visitor. While saving a Use Case draft, any Author has to accept a privacy statement ensuring that the provided information from the Horizon Project can be disclosed.
Once an Author has completed a Use Case draft in all its mandatory fields, the Author has to submit it for review before it can be published (see the guidelines for evaluation procedure).
Once a Use Case draft is under review, an Evaluator from Action#1 of the Data Management Working Group of BRIDGE will check the content and decide whether to publish it or request any improvements.
Only an Evaluator can publish a Use Case in the Repository. Hence, Authors must complete the Use Case following the IEC 62559-2:2015 Standard and the instructions reported in the guidelines.
Once an Author completes a Use Case draft, it has to be submitted for a quality evaluation before being published. This is an essential step, as not all Horizon Projects follow the IEC62559-2:2015 standard, or they may interpret the fields of the template in different ways. The evaluation process is therefore needed to ensure all Use Cases properly answer the different fields of the template. In this respect, a document with the guidelines for Authors has been created by Action#1.
If an Evaluator detects some inconsistency in the information provided, (s)he can ask to Author to improve it or provide explanations.
The Use Case evaluation is not intended to be a technical review of the contents of the Use Cases (unless major problems are detected).
Evaluators are volunteers from Bridge projects, participating in Action#1 of the Data Management Working Group, who give their availability to check the quality of the Use Cases drafts and decide whether to publish them or request improvements. Action#1 Leader will organise the activities of the Evaluators, assigning them the Use Case to review, ensuring a balanced workload and organising shifts among them.
All Use Cases are described following the template of the standard IEC 62559-2:2015. They can be visualised directly on the Repository or downloaded in PDF. It is not possible to download an XML file for a Use Case.
An Author may visualise this error message while drafting a Use Case in the Repository: “The requested URL was rejected. Please consult with your administrator.”
The message is complemented by a support ID code. This error is generated by a block from the firewall of the web portal. If this happens, the Author has to contact the WAF team of the JRC at the following email: JRC-WAF@ec.europa.eu, sharing the support ID number and requesting the enabling of the ECAS account in the JRC portal.
You can find the document with guidelines for the Use Case author at this link. The guidelines will be periodically updated as soon as the improvements or updates to the Repository are implemented. For any other questions, you can contact Action#1 of the Data Management Working Group of BRIDGE.