A TRANXACT deployment is the same reference architecture every time, built from code on the customer’s chosen cloud — AWS, Microsoft Azure or Google Cloud — in the region they choose. Each customer has its own network, cluster and database. Nothing is shared with another customer.
Almost none of the work in this programme happens on a TRANXACT screen. Nobody can sign in until an address range is agreed, a DNS record published, a certificate issued and an identity provider federated. Those are the subjects here.
Five phases, five roles
- Proposal — the Ledger Architect sizes the deployment and signs off the architecture.
- Onboarding and build — the AI Deployment Orchestrator runs kick-off and the build; the Data Migration Conductor joins from the build.
- Configure and migrate — the Data Migration Conductor takes the migration cockpit through trial loads to an audited cutover.
- Operate and advise — the Autonomous Operations Pilot runs the service from environment handover, Live DR included.
- Renew — the AI Adoption Navigator drives adoption and ASK usage and leads the renewal.
The Orchestrator is the one role that spans all five: the customer’s single point of contact from contract to steady state.
The documents
The order form is at the centre. Around it: master terms, the licence schedule (a share of audited revenue), the SLA, infrastructure and AI usage, the support policy, the DPA, the Roles & Responsibilities workbook, and the service description. When anything in training or in a deck disagrees with them, the contract documents win.
Calderwood Group runs four legal entities, three currencies and two languages. It wants Accounting, CRM and Supply Chain at go-live and HRMS in phase 2, on Microsoft Azure, with Live DR. Every course in this programme follows Calderwood’s deployment one step further.
Try it Calderwood’s CFO asks who their single point of contact is between signing and the first month of steady operations. Who, and why not the Ledger Architect?
The AI Deployment Orchestrator, who spans every phase. The Ledger Architect leads the proposal and the architecture sign-off and then hands over; the design stays theirs, but the contact point does not.
Revenue-based licensing needs audited figures before the contract, and infrastructure is a separate cloud bill. Both have to be settled before signature — the first because there is no price without it, the second because it decides whose account the cluster is built in.