Prove it on your own programme in four weeks
A fixed-fee pilot that ends in a written report you can take to your steering committee. S4 RetrofitBox is installed in your network, carries your first 20 released BAU transports onto your converted S/4HANA code, and is measured against five acceptance criteria. You keep your code and every record, whatever you decide.
What the pilot covers
One package, 20 real transports, a fixed fee and a written result. The box never connects to or writes to SAP.
- Length
- Four weeks.
- Scope
- One package, with its subpackages.
- Measured on
- The first 20 released BAU transports.
- Install
- Your Basis team, from the runbook. The target is under one working day.
- Fee
- Fixed, and credited against the first year's licence on adoption.
- Report
- A final report, with the acceptance results and an audit export for every approved Retrofit.
- Exit
- You keep your code and every record.
The pilot plan, in four steps
Your team does the install and the review. We verify the release, issue the licence, walk your team through the first transport and write the report.
Preparation and prerequisites
Your team works through the readiness checklist and signs the ready to install table. We verify the container image on a test VM and agree the automation target with you at kick-off.
Install and onboarding
Your Basis team installs the box from the runbook and sends us the installation id, and we issue the pilot licence file. The team then connects ECC and S/4 to the box, and we walk it through the first transport until the first Retrofit appears.
Transports measured
The first 20 released BAU transports are carried across. Your reviewers handle Manual objects and approve or reject each Retrofit, and your developers pull approved code into S/4 under their own transports.
Final report and decision
We enter the results in the acceptance plan, take an audit export for every approved Retrofit and issue the report. Your programme director signs the acceptance decision.
What you need ready
Four groups of items, each with a named owner on your side. The full readiness checklist comes with the pilot pack.
Infrastructure
- A Linux VM that you control, with Docker Engine and the Compose plugin
- A DNS name for the box that both SAP development systems can reach over HTTPS on port 443
- Port 80 open for the TLS certificate challenge, and no route from the box to any SAP system
- Access to the container image, and storage for backups
SAP systems
- An ABAP add-on allowed on the ECC and S/4 development systems. We name it, and what it needs, when you request a pilot
- The automatic export set up on ECC, with a slot for its background job
- The top customer package identified, with the same package names on ECC and S/4
- The converted S/4 code ready to hand to the box, and a decision on whether an exact baseline exists
People
- A Basis lead named for the install
- An SAP development lead named to link the systems and work with the Retrofit records
- A reviewer for each pilot Retrofit, who is not an author of that transport
- Someone to supply SAP transport logs for the zero writes check
Optional: model key
- Your own key with Anthropic, OpenAI or Azure OpenAI, paid to your provider directly
- Your security and legal owners' review of what a model call contains and of your provider's retention terms
- No key is needed to run the pilot: rules and checks still run, and conflicts go to a person
How success is measured
The pilot is accepted when all five criteria are measured and signed. We agree the automation target with you at kick-off, and we report the result as measured.
| Criterion | How it is measured |
|---|---|
| Install to first Retrofit in under one working day | Your Basis team follows the runbook alone. The clock runs from the first runbook step to the first Retrofit record, from a timestamped log. |
| Share of objects finished without a human edit | On the first 20 released BAU transports, the objects that reach Applied, Already present, Remediated or Resolved conflict with no recorded edit, divided by all objects. Manual objects count against the share. The target is set with you at kick-off. |
| Zero writes to SAP by the box | Shown from SAP's own transport logs and object version history. Each entry is classed as developer BAU work or a named developer's pull transport, and the box's outbound destinations are listed. |
| An audit record for every approved Retrofit | Each approved Retrofit is exported, and the export is checked against the box records for its inputs, outcomes, rationale and approver. |
| The model key never leaves the box | A log search and a controlled error test show no occurrence of the key in stored output, and no outbound destination other than the model endpoint you configured. |
The independent security review and penetration test have not been carried out yet. They are scheduled before production use, and you decide whether to commission one for the pilot.
The pilot pack
Ten documents cover the product, the security position, the pilot and the commercial terms. We send them on request: tick the box on the form below.
- Solution Brief
- Security Whitepaper
- AI and Data Handling Statement
- Prerequisites and Readiness Checklist
- SAP Onboarding Guide
- Pilot Statement of Work
- Pilot Acceptance Plan
- Commercial Term Sheet
- Systems Integrator Partnership Proposal
- High-Level Design
Questions your team will ask
Answers from the pilot pack. If yours is not here, put it in the message field below.
Does the box write to SAP?
Do we have to use AI?
Which model providers can we use?
What leaves our network?
What if our security team will not allow an add-on on ECC?
Is customising covered?
How long does the install take?
What happens to our code if we stop?
Is there a hosted option?
Does it support single sign-on?
Request a pilot
Tell us who you are and how many transports your legacy system releases. We then arrange a call and send the pilot pack.
We use the details you give only to answer this request.