Courses › Deployment
Deploying TRANXACT
The work that happens outside the product: who owns which task, how the cloud account, network, database, Live DR region and vault are staged, and what is done before the contract, during the build and after go-live.
11 courses
9 diagrams
57 questions
3.3 hours
Start here
Deployment practitioner exam
i
None of this happens on a TRANXACT screen, so these courses are read, drawn and checked rather than walked through the console. Each one follows the same invented customer, Calderwood Group, one step further, and links to the reference guide on the help site.
3 Foundations
45 minutes
5 Architecture and network
93 minutes
3 Before, during and after
58 minutes
Foundations Who does what, and how the catalogue of tasks is read.
Foundations The deployment at a glance
The five phases of a customer deployment, who leads each one, and the documents that define it.
Foundations Who does what: roles and responsibilities
The five service categories, Delivery-by codes, how tasks are ordered, the crew and their counterparts, and the RACI.
Foundations Scoping the R&R workbook
The chapters and their counts, the columns, the criteria that decide whether a row applies, the In Scope column, and the seven packages.
Architecture and network What is built in the cloud, and how everything reaches it.
Architecture Reference architecture and runtime
The ingress, the three-node cluster across zones, the HA database, object storage, egress and the vault — and why every customer gets the same one.
Architecture Staging the tenant: private and public
Single-tenant isolation, TRANXACT-hosted versus customer-owned accounts, the separate vault tenant, the environments per year, and public versus private-only access.
Architecture Network topologies
The five connectivity options, VPN and private-connection requirements, /22 address planning, hub-and-spoke peering, DNS and certificates, egress and operator access.
Architecture Live DR, backup and the vault
Availability tiers, continuity patterns, how Live DR is proven and drilled, the backup policy, long-term retention, and why the vault sits outside both regions.
Architecture Security and compliance in a deployment
The controls the customer switches on, keys and encryption, patch targets, breach notification, customer penetration tests, ASK governance, and residency.
Before, during and after The proposal, the build and go-live, and running the service.
Lifecycle Before the contract: proposal and sizing
Interfaces as they are, sizing for the peak, the usage tiers, the bill of materials and commercial model, assumptions, the non-standard log, and the decisions to lock before signature.
Lifecycle During the deployment: build to go-live
Provisioning, the timeline, the onboarding form, identity and communications, the migration cockpit, cutover and the go-live gates.
Lifecycle After go-live: running the service
Service requests and refreshes, incidents and the P1 path, SLAs, releases, the governance cadence, scaling, extensions, and the steady-state checklist.
Check the whole programme
How the customer is then taken from signature to go-live, day by day: T-Minus, the implementation methodology
Sources: the TRANXACT Private Cloud Technical Architecture & Customer Deployment Guide and the Roles & Responsibilities workbook, version 2026-09. Values marked proposed are defaults to confirm per customer; the contract, order form, SLA and DPA prevail.