The following tables describe the standard default responsibilities between OBS and the customer depending on the build model.
The following tables describe the standard default responsibilities between OBS and the customer depending on classes of service. Those may be amended with mutuel consent depending on project.
- R stands for responsible
- A stands for Accountable
- C stands for Contributor
- I stands for Informed
- RACI for Managed OS
| Service Implementation | OBS | Customer | OBS | Customer | OBS | Customer |
| OS Server infrastructure implementation Full build | Operations build | Backend build | ||||
| Deployment of the infrastructure | R, A | I | I | R, A | I | R, A |
| Deployment of LAN components | R, A | I | I | R, A | I | R, A |
| Deployment of DNS and NTP services | R, A | I | R, A | I | I | R, A |
| Backup tools for operations (AWS backup & AWS Snapshots) | R, A | I | R, A | I | I | R, A |
| Deployment of the OS patching solution (AWS Systems Manager Patch Manager) or OBS Patch management | R, A | I | R, A | I | I | R, A |
| Deployment of the Antivirus solution | R, A | I | R, A | I | SoW | SoW |
| Deployment of the supervision solution (Amazon CloudWatch) | R, A | I | R, A | I | I | R, A |
| Deployment of the supervision solution (Amazon CloudWatch) | R, A | I | R, A | I | I | R, A |
| Deployment of security groups and firewall rules | R, A | I | SoW | SoW | I | R, A |
| Recovery procedure (Infra as Code, restore, other…) | R, A | I | I | R, A | I | R, A |
| Testing and validation of infrastructure implementation | R | A | I | R, A | I | R, A |
| Testing and validation of AWS tooling implementation and lifecycle management | R | A | R | A | I | R, A |
| OS Server Implementation | ||||||
| Evaluation or deployment of the operating system | R, A | I | R, A | I | I | R, A |
| Deployment of new packages | R, A | I | R, A | I | R, A | I |
| Test and validation of operating system implementation for new packages | R, A | I | R, A | I | R, A | I |
| Service implementation documentation | ||||||
| Conception, architecture and low-level design for infrastructure | I | R, A | I | R, A | I | R, A |
| Implementation and operation documentation for infrastructure | R, A | I | I | R, A | I | R, A |
| Conception and low-level design for tooling (AWS) | R, A | I | R, A | I | I | R, A |
| Implementation & operation documentation for tooling (AWS) | R, A | I | R, A | I | I | R, A |
- RACI for Database as a Service
| Service Implementation | OBS | Customer | OBS | Customer | OBS | Customer |
| Database aaS services conception and implementation Full Build | Operations Build | Backend Build | ||||
| Maintenance of Infrastructure architecture referential | R, A | I | I | R, A | I | R, A |
| Maintenance of tooling configuration referential | R, A | I | R, A | I | I | R, A |
| Deployment of the infrastructure | R, A | I | I | R, A | I | R, A |
| Deployment of the supervision solution (Amazon CloudWatch) | R, A | I | R, A | I | I | R, A |
| Deployment of the logging solution (Amazon CloudWatch Logs) (optional) | R, A | I | R, A | I | I | R, A |
| Deployment of the backup solution (AWS Backup, Snapshot) | R, A | C, I | R, A | C, I | I | R, A |
| Recovery procedure for infrastructure from referential (Infra as code, restore from backup, other…) | R, A | C, I | I | R, A | I | R, A |
| Recovery procedure for tooling from referential (Infra as code, restore, other…) | R, A | C, I | R, A | C, I | I | R, A |
| Testing and validation of infrastructure implementation | R, A | I | I | R, A | I | R, A |
| Testing and validation of tooling implementation and lifecycle management | R, A | I | R, A | C, I | I | R, A |
| Customer provided script execution on DB instance | R | A, I | R | A, I | R | A, I |
| OBS script execution on DB instance | R, A | C, I | R, A | C, I | R, A | C, I |
| Service implementation documentation | ||||||
| Conception, architecture, and low-level design for infrastructure | C, I | R, A | I | R, A | I | R, A |
| Implementation and operation documentation for infra | R, A | C, I | I | R, A | I | R, A |
| Conception and low-level design for tooling (AWS) | R, A | C, I | R, A | C, I | I | R, A |
| Implementation & operation documentation for tooling (AWS) | R, A | C, I | R, A | C, I | I | R, A |
| Service Operation | OBS | Customer | OBS | Customer | OBS | Customer |
| Database aaS services operations Full Build | Operations Build | Backend Build | ||||
| Monitoring through Amazon CloudWatch | R | I | R | I | R* | I |
| Investigation through Amazon CloudWatch | R, A | C,I | R, A | C,I | R* | A |
| Restore from Infra as Code and backup | R, A | C,I | R, A | C,I | R* | A |
| Changing capacity of database instance | R, A | C,I | C, I | R, A | C, I | R, A |
| ITSM operations | ||||||
| Change Management | R | A | R | A | R | A |
| Incident Management | R, A | R**,I | R, A | R**,I | R, A | R**,I |
| Event management | R, A | I | R, A | I | R, A | I |
| Baseline security management | R | A | SoW | SoW | SoW | SoW |
| Configuration management | R, A | C, I | R | A | R | A |
| Report management via SDM service | R, A | C, I | R, A | C, I | R, A | C, I |
| Invoicing management | R, A | I | R, A | I | R, A | I |
R*: within the limitations of tooling provided by the Customer
R**: in co-management model, customer may have joint responsibilities related to the activity & incident
- RACI for other Native Services managed
| Service Implementation | OBS | Customer | OBS | Customer | OBS | Customer |
| Native service infrastructure implementation Full Build | Operations Build | Backend Build | ||||
| Deployment of the infrastructure | R, A | I | I | R, A | I | R, A |
| Backup tools for operations (AWS backup) (1) | R, A | I | R, A | I | I | R, A |
| Deployment of the supervision solution (Amazon CloudWatch) (1) | R, A | I | R, A | I | I | R, A |
| Deployment of the logging solution (Amazon CloudWatch Logs) optional (1) | R, A | I | R, A | I | I | R, A |
| Deployment of security groups and firewall rules | R, A | I | SoW | SoW | I | R, A |
| Recovery procedure (Infra as Code, restore, other…) | R, A | I | I | R, A | I | R, A |
| Testing and validation of infrastructure implementation | R | A | I | R, A | I | R, A |
| Testing and validation of AWS tooling implementation | R | A | R | A | I | R, A |
| Packages | ||||||
| Deployment of new packages (1) | I | R, A | I | R, A | I | R, A |
| Service implementation documentation | ||||||
| Conception, architecture, and low-level design for infrastructure | C, I | R, A | I | R, A | I | R, A |
| Implementation and operation documentation for infrastructure | R, A | I | I | R, A | I | R, A |
| Conception and low-level design for tooling (AWS) | R, A | I | R, A | I | I | R, A |
| Implementation & operation documentation for tooling (AWS) | R, A | I | R, A | I | I | R, A |
| Service Operation | OBS | Customer | OBS | Customer | OBS | Customer |
| Native service operations Full Build | Operations build | Backend build | ||||
| Monitoring (1) | R, A | I | R, A | I | R* | A |
| Backup (1) | R | A | R | A | R* | A |
| Restore from Infra as Code and backup (1) | R, A | C, I | R, A | C, I | R* | A |
| Security groups, Firewall rules setting | R | A | SoW | SoW | I | R, A |
| ITSM operations | ||||||
| Change Management | R | A | R | A | R* | A |
| Incident Management | R, A | R**, I | R, A | R**, I | R*, A | R**, I |
| Event management | R, A | I | R, A | I | R* | A |
| Baseline security management | R | A | SoW | SoW | SoW | SoW |
| Report management via SDM service | R, A | I | R, A | I | R, A | I |
| Invoicing management | R, A | I | R, A | I | R, A | I |
R*: within the limitations of tooling provided by the Customer
R**: in co-management model, customer may have joint responsibilities related to the activity & incident
(1) When applicable as per detailed description per service