R&D / L3 asks for an outcome.
You do not need to choose firewall rules or infrastructure patterns. You explain the workload, constraints and services you need.
This interactive model explains responsibilities without forcing users to understand technical layer language first. R&D / L3 describes the need. Local IS translates it. Architects design it. IS protects it. Hosting Provider and Common Services deliver the services.
The model shows the collaboration from a user perspective: what R&D / L3 asks for, who translates the need, who designs the approved setup, who protects the workload, who handles security governance and who provides the consumable services.
You do not need to choose firewall rules or infrastructure patterns. You explain the workload, constraints and services you need.
Local IS, Architects and IS convert the need into a WorkZone, Security Shield and service pattern that can be implemented.
Shared capabilities such as backup, storage, monitoring, remote access or managed hypervisor capacity should be consumed where possible.
Users do not need to remember all technical details. The key is simple: the WorkZone is where R&D / L3 works, the Security Shield protects it, and the Service Shelf provides reusable services.
The same RASCI model can be read from two directions: what a specific role does, or who is involved in a specific scenario.
Select a scenario to see the task sequence and the RASCI split. Air-gapped environments are handled separately because they do not consume connected Layer 3 services.
The table below shows the complete model used by the explorer. Every row has one clear accountable owner.
The interactive model is a plain-language translation of the responsibility logic in the Polaris guideline. It keeps the key rules while making them easier to use in discussions.