Reading and scoping the R&R workbook
The nine chapters and their task counts, what every column means, the criteria columns that decide whether a task applies, the amber In Scope column, the seven packages, and the service request catalogue.
The Roles & Responsibilities workbook is the task-level contract behind the RACI. It is a catalogue, not a to-do list: not every row applies to every deployment, and scoping it with the customer is part of the proposal.
The tabs
- Defined Service Options — the five categories, the Delivery-by codes and the ordering types.
- Core Technical Operations — every task, chapters A to H and X.
- Summary — counts per chapter and category; updates by itself from the task list and the In Scope column.
- Packages — the seven packages and whether each is contracted.
- Service Request Catalogue — examples with lead times and quotas, category and ordering looked up live by identifier.
- RACI, and Crew & Counterparts — mirroring the deployment guide.
The chapters
| Chapter | Prefix | Tasks | Applies |
|---|---|---|---|
| A — Service Management | SM | 21 | Every customer. |
| B — Managed Cloud Infrastructure | INFRA | 40 | Every customer. |
| C — Managed Database | DB | 12 | Every customer. |
| D — Core Technical Operations | TO | 82 | Every customer. |
| E — TRANXACT Platform Operations | PLAT | 31 | Every customer. |
| F — ASK AI Operations | ASK | 12 | When ASK is enabled. |
| G — Packaged Services | PKG | 14 | When packages are contracted. |
| H — Data Migration and Onboarding | MIG | 15 | During onboarding. |
| X — Extensions and Third-Party Software | EXT | 10 | Only when extensions are approved. |
237 tasks in all: 118 Standard, 26 Optional, 13 Additional, 29 Packaged and 51 Excluded — plus one not-offered marker that is left out of the totals.
The columns, left to right
| Column | What it says |
|---|---|
| Identifier | The unique, stable task ID used in requests and contracts, e.g. TO_4.10.03. Chapter prefix, section, task. |
| Task | What is done. Chapter and section headings group the rows. |
| Responsibility | The service category. |
| Remarks | Conditions, quotas, lead times and restrictions — often the most important cell on the row. |
| Package, Package code, Cluster | For a Packaged task, which package it belongs to (e.g. Functional Administration, F1, Application Management). |
| Delivery by | P, A, S or C. |
| Ordering information | How it is ordered. |
| TRANXACT owner, Customer counterpart | The crew role, and who the customer names against it. |
| Special Services, Module, Cloud Provider, Continuity Pattern | The criteria columns — see below. |
| In Scope (Y/N) | The amber customer-input column. |
Criteria columns: does this row apply?
Four columns hold either * — the task applies to every deployment — or ONLY:… naming the deployments it applies to.
| Criteria column | Examples of ONLY values |
|---|---|
| Special Services | Regulated industry · Customer-owned cloud account · Site-to-site VPN · Private connection · Peering · Transit hub · Customer-managed keys · BYOK · Approved extension |
| Module | EHR, Student Lifecycle, HRMS (the qualification deliverables for regulated workloads, SM_1.3.01) |
| Cloud Provider | Every task in this edition is * — the same catalogue on all three clouds. |
| Continuity Pattern | Live DR, Live DR Premium · Live DR Premium |
Filter on the customer’s special services, modules, cloud and continuity pattern before you share the workbook. A customer on Standard HA who is shown the Live DR drill rows will reasonably ask when their drills are.
Note how an Optional task switches Standard tasks on. Setting up the Live DR region (TO_4.10.02) is Optional; once it is contracted, continuous verification, the quarterly switchover drill and automatic failover (TO_4.10.01, 4.10.03, 4.10.07) are Standard, because their Continuity Pattern criterion is now met.
Setting In Scope
- Standard Services and Excluded Tasks default to Y. Leave them, unless a criteria column says the row does not apply to this deployment.
- Decide every Optional, Additional and Packaged row with the customer. These are the 68 open decisions the Summary counts.
- For Packaged rows, the answer follows the Packages tab: a contracted package puts its rows in scope for TRANXACT; an uncontracted one leaves them with the customer.
- Check the Summary. In scope and open decisions update from the column, per chapter.
- Share the scoped workbook with the order form. It is one of the contract documents.
The seven packages
| Code | Package | Cluster | Tasks |
|---|---|---|---|
| F1 | Functional Administration | Application Management | 9 |
| R1 | Reporting & Analytics | Application Management | 2 |
| M1 | Integration Monitoring | Advanced Monitoring | 5 |
| J1 | Business Job Management | Advanced Monitoring | 3 |
| T1 | Regression Testing | Test Management | 3 |
| G1 | ASK Usage Governance | AI Governance | 6 |
| H1 | Hypercare | Continuous Operations | 1 |
Packages exclude any extension, reduction or change of the landscape — additional infrastructure is always a separate change request. TRANXACT delivers them proactively or reactively; reactive requests are raised in the service portal.
Open definitions worth quoting
- Anything applicable to the deployment that the customer did not purchase and that is not Standard is the customer’s responsibility.
- Task descriptions cover doing the task, not extra capacity. More compute, storage or network is a change request with its own fee.
- Service availability may be limited for sandbox and other test environments.
- Identifiers are stable across versions of the workbook.