Architecture Master Repository

Content owner: orlando.pereira@roche.com

The Architecture Master Repository (AMR) is the operational source for pan-RED application, architecture, and business information across the CS-CoE and the REDs. It covers current, planned, and retired applications and supports the continuous maintenance of architecture information throughout a system’s lifecycle.

AMR provides broad, complete, and role-relevant views of an application’s architecture, dependencies, and business context. It enables teams to keep information current over time so that architectural knowledge remains transparent, discoverable, and actionable.

Core Capabilities

Applications — View the inventory of all pan-RED applications, including current, planned, and retired systems.
Application Dependencies — Explore upstream and downstream dependencies between applications and related platforms.
Data Landscape — Use interactive visualizations to understand data flows across systems and domains.
Key Systems — Identify foundational systems across the REDs.
Search — Use faceted search to find applications and related architecture information quickly.
Browse by Business Capability — Navigate the application landscape using the PRISME Business Capability Taxonomy.

Training Material

Training materials for AMR are provided through externally hosted videos and learning resources.

Module 1: Getting Started with AMR - Overview of scope, roles and responsibilities
Module 2: Application Data Capture - Step-by-step guide for updating records, including taxonomies and field definitions

FAQ

Question	Answer
What should be documented in AMR?	Pan-RED application, architecture, and business information, including lifecycle status, ownership, dependencies, and landscape context.
Who should use AMR?	Architects, application owners, platform teams, and other stakeholders who need visibility into the RED application landscape and its dependencies.
When should AMR be updated?	AMR should be updated when a system is introduced, significantly changed, integrated with new upstream or downstream systems, re-platformed, or moved toward retirement.
What can I find in AMR?	AMR provides access to application inventories, dependency views, data landscape visualizations, key systems, faceted search, and business-capability-based navigation.
How can I explore the landscape by business domain?	Use Browse by Business Capability to navigate the landscape through the PRISME Business Capability Taxonomy.
Does AMR replace enterprise architecture tooling?	AMR is the operational architecture repository for RED-focused needs today. Enterprise-wide alignment with broader Roche architecture tooling remains part of the longer-term direction.

Question

Answer

What should be documented in AMR?

Pan-RED application, architecture, and business information, including lifecycle status, ownership, dependencies, and landscape context.

Who should use AMR?

Architects, application owners, platform teams, and other stakeholders who need visibility into the RED application landscape and its dependencies.

When should AMR be updated?

AMR should be updated when a system is introduced, significantly changed, integrated with new upstream or downstream systems, re-platformed, or moved toward retirement.

What can I find in AMR?

AMR provides access to application inventories, dependency views, data landscape visualizations, key systems, faceted search, and business-capability-based navigation.

How can I explore the landscape by business domain?

Use Browse by Business Capability to navigate the landscape through the PRISME Business Capability Taxonomy.

Does AMR replace enterprise architecture tooling?

AMR is the operational architecture repository for RED-focused needs today. Enterprise-wide alignment with broader Roche architecture tooling remains part of the longer-term direction.