Roche Letters

The dataset or system is findable in a searchable catalog or inventory (e.g., ).

A named data owner or steward is formally assigned and documented.

Access and usage conditions, including legal and compliance constraints, are documented and available to users.

What is the percentage of the data uses standardized terminologies such as RTiS.

Data lineage is captured for key data flows and is maintained over time.

The system uses the approved corporate identity provider for user authentication (e.g., Roche SSO via PingFederate, OAuth 2.0, OpenID Connect).

Data is encrypted in transit.

Data is encrypted at rest.

Secrets are managed in an approved central vault (e.g., HashiCorp Vault or AWS Secrets Manager).

Access rights and permissions are reviewed and formally certified at defined intervals.

No shared or generic privileged accounts exist in the production environment.

Infrastructure is provisioned declaratively using Infrastructure as Code.

The system uses approved shared internal platforms or Golden Paths, where applicable. (e.g., Minerva Application Blueprint)

Can we swap in and out components without modifying the system.

All application services are exposed through clear and defined interfaces.

Data contracts are documented and governed.

API lifecycle management is actively implemented using Gravitee.

All critical services have defined SLAs and SLOs.

Major incidents are followed by systematic postmortems, and resulting corrective actions are tracked to closure in the backlog.

SLIs are defined and calculated for all established SLAs and SLOs, and are visible to stakeholders and system owners.

The system supports automated vertical and horizontal scaling based on real-time demand, where applicable.

Load and performance testing are performed routinely and included in major release cycles.

Core workloads are supported by a complete CI/CD pipeline.

Builds, tests, and deployments are executed through fully automated processes.

Automated quality gates are enforced before production deployment. (e.g., SonarQube)

Production rollback or deployment occurs regularly and within the last 6 months.

Build artifacts and dependencies are managed in a traceable and controlled manner.

All critical services generate standard telemetry, including logs, metrics, and traces.

Observability data is available through approved central monitoring and observability tools.

Incident analysis can be performed across upstream and downstream dependencies.

Critical services and data have defined Recovery Time Objective (RTO) and Recovery Point Objective (RPO) targets.

Backup, restore, and recovery procedures, including assigned roles and responsibilities, are documented and tested.

Cost visibility is available at component, system, product family, or domain level.

Cost is reviewed regularly together with usage and business value by the owning team.

Architectural decisions explicitly consider cost as a primary decision variable.