Assess Your First Service
In this tutorial you add one service to EBRAINS Ready, let it collect the evidence, and read the level it reaches and what stands between it and the next one. It takes about five minutes. You need an EBRAINS account and the address of the service’s code repository.
Ready only reads your repository. Adding it does not write anything to it.
1. Sign in
Open ready.ebrains.eu and select Continue with EBRAINS.
If your organisation is already in Ready, you are offered Request to join it. For this tutorial, choose Skip — just register a service of my own.
2. Add the service
Your workspace opens on Start with one service.
- Paste the repository address, for example
https://github.com/my-lab/my-tool, and select Start. Ready reads the repository and shows what it is doing (“Checking the files…”, “Finding its addresses…”). - If the repository belongs to an organisation, you can set up a catalogue for it or register the service on its own. Choose Register … on its own.
- Answer One question about your service: does it run somewhere for people to use, or is it a tool people install? This decides which checklist it is assessed against.
The service page opens and evidence collection starts by itself. A first run takes about two minutes; the page shows what is being read while it runs. When it says the assessment is fresh, it is done.
3. Read the level
At the top of the service page are nine stage bars, one per TRL, and the level the service has reached. Assessed under names the rubric version that judged it.
Open the Checklist tab. It opens on the next gate, for example Gate to TRL 6 — 2 of 3 met:
| Mark | Meaning |
|---|---|
| ✓ Met | The evidence meets this condition. Met by shows which evidence. |
| ! Missing | Not met yet. Needs shows what would meet it, with your service’s current value. |
| ~ Waived | Not required yet for anyone; it always passes. |
| – N/A | Does not apply to this service, so it does not block the level. |
The level is the highest one whose conditions are all met, climbed in order. So the first gate with a missing condition is where the service stops, and that condition is the next thing to work on.
4. Look around
- Evidence: everything Ready collected, with where each value came from and when.
- Next steps: recommendations, ordered by what would help most.
- History: past evaluations and the rubric version of each.
What next
- Move your service up a level
- Show your level with a badge
- Add many services at once
- How a level is decided
A personal workspace holds up to five services from public repositories. Private repositories and larger portfolios need an organisation; see How to add services in bulk.