Platform checklist

For third-party software EBRAINS operates as infrastructure. Its development happens upstream, so the ladder is about operating it: provisioning, integration, monitoring and reliability.

Service types: platform · Rubric: EBRAINS default, version x4

How to read it: a level is reached when all of its conditions are met, and levels are climbed in order. Waived conditions are not required yet and are always shown as waived. A condition can be marked not applicable for a service (a status page cannot monitor itself); it then drops out of the level.

TRL 1 · Project initiation

  • Platform registered with its purpose and owner
    Met when any of:
    • Service description recorded
    • Owner contact recorded
    • Use case recorded

TRL 2 · Conceptualisation

  • Platform provisioned (reachable URL or container image)
    Met when any of:
    • Web app URL recorded
    • Containerised
    • Deployment URL recorded

TRL 3 · Proof of concept implementation

  • Wired into the EBRAINS ecosystem (IAM, Knowledge Graph or registry)
    Met when any of:
    • Auth integration: hbp_keycloak or ebrains_keycloak
    • Knowledge graph integration more than 0
    • Docker registry integration more than 0
    • EBRAINS ecosystem integration recorded

TRL 4 · Prototype component

  • Running in an operational environment
    Met when any of:
    • Deployment environment: staging or production
    • Deployed environments include production
    • Web app accessible

TRL 5 · Prototype integration

  • Monitoring in place
    Met when any of:
    • Uptime monitoring: yes
    • Uptime percentage (30 days) more than 0

TRL 6 · Pilot-scale prototype to real-world integration

  • Operated at real-world scale with backups, maintainers or support
    Met when any of:
    • Backup strategy recorded
    • Maintainer count at least 1
    • Has maintainer recorded
    • Support channels recorded
    • Uptime percentage (30 days) at least 95

TRL 7 · Operational integration

  • Deployed in production with all key functionality
    Met when any of:
    • Deployment environment: production
    • Deployed environments include production
  • System monitoring points implemented
    Met when any of:
    • Uptime monitoring: yes
    • Uptime percentage (30 days) more than 0
  • Integrated with the EBRAINS ecosystem
    Met when any of:
    • Auth integration: hbp_keycloak or ebrains_keycloak
    • Knowledge graph integration more than 0
    • Docker registry integration more than 0
    • EBRAINS ecosystem integration recorded
  • SLA monitored
    Waived — EBRAINS runs no SLA programme yet.

TRL 8 · Deployment

  • Proven to work in its final form under expected conditions
    Met when: Uptime percentage (30 days) at least 99.
  • Operational documentation completed (runbooks, procedures)
    Met when any of:
    • Runbooks documented recorded
    • Knowledge Graph documentation URL recorded
    • README quality: good or comprehensive
    • Documentation strategy recorded
  • Serving real EBRAINS users
    Met when any of:
    • IAM active users more than 0
    • Users count more than 0
    • Deployment environment: production
  • SLA enforced
    Waived — EBRAINS runs no SLA programme yet.

TRL 9 · Production

  • Operated over the full range of conditions with sustained reliability
    Met when: Uptime percentage (30 days) at least 99.9.
  • Target number of real users
    Met when: iam_active_users ≥ 50 (gap-tolerant if no IAM telemetry).
  • Service engineering and follow-up support in place
    Met when any of:
    • Support channels recorded
    • Issue tracking recorded
    • Incident response plan recorded

Generated from the rubric Ready evaluates. Organisations can assess their own catalogues against their own rubric in Ready; those results are labelled as such and are not the EBRAINS default.