How to Move Up a Level

A service stops at the first level with a condition that is not met. Moving up means meeting the missing conditions of the next gate, then letting Ready collect the evidence again.

1. Find what is missing

Open the service in Ready and go to the Checklist tab. It opens on the next gate, for example Gate to TRL 6 — 2 of 3 met. For each condition marked ! Missing:

• Needs (or Needs any one of, Needs all of) lists what would meet it, with the value Ready holds for your service now.
• Not collected yet means Ready has no value for it: collect again, or declare it yourself.
• Checked — the evidence does not meet this means Ready has a value and it falls short: the service itself needs to change.

The Next steps tab orders recommendations by how much they would help, and gives configuration you can copy where that applies.

2. Fix it

• Answer what only you can answer. Some evidence cannot be collected, such as who the service is for. Fill in Only you can answer these on the service page and select Declare. Declared answers are shown as yours, and you can withdraw them.
• Fix wrong addresses. If Ready reads the wrong repository or web address, change it on the Information tab.
• Change the service. For anything else (a CI pipeline, monitoring, documentation, a release), make the change in the repository or deployment, as the condition describes.

3. Collect again

Select Collect on the service page. Ready reads everything again and re-scores the service, which takes about two minutes. A service can be collected again six hours after its last collection; until then the button shows when it will be available.

When Ready gets it wrong

Service owners cannot edit collected evidence; that is what keeps the level comparable. If a collected value is wrong, or a condition cannot apply to your service, ask the EBRAINS Ready team through EBRAINS support, naming the service and the condition. A corrected value is always labelled as entered by hand. See Versions and corrections.