An SAP implementation methodology scored while it runs
Every Raptors engagement runs on SAP Activate, the implementation methodology SAP defines, from scoping to application management. From the first day of your project, PreFlight scores the work and you see the score.
How we deliver
One method on every engagement
SAP Activate, as SAP defines it
We deliver on SAP Activate, the implementation methodology SAP defines for its own products. It runs in six phases and is built around fit-to-standard: your processes are matched to what the software already does before anything is configured. We run the same phases on SAP SuccessFactors, on SAP S/4HANA Cloud Public Edition and on SAP Business Technology Platform work. The method does not change with the product.
Scored while it runs
What is different is that the method is scored while it runs. PreFlight, our quality assurance platform, is part of every engagement. Each phase closes on a formal quality gate, every deliverable is reviewed before it passes, and the results combine into one composite score for your project. You have access to that score.
What we do
Six services, one method
These are the services we deliver. Each one runs against the SAP Activate phases below and is scored in PreFlight on the same measures, from a scoping engagement through to application management after go-live. What you receive from each is listed under it.
Discovery and scoping
Stakeholders are mapped, requirements are gathered, and a target state is designed. The deployment approach is decided here: a new implementation, or a move from the systems you run today. This is the work of the Discover phase.
Deliverables
- Statement of work
- Target architecture
- Deployment plan
Implementation
Delivery through Prepare, Explore, Realize and Deploy, on the SAP Activate phases below, with PreFlight scoring active from the first day of the project to go-live.
Deliverables
- Configured solution
- Cutover plan
- Go-live readiness report
Integration
Integration to your SAP S/4HANA estate, to the third-party systems around it, to government portals and to biometric devices on site. Built on SAP Integration Suite, so the interfaces are maintained where SAP maintains them.
Deliverables
- Integration design
- Live interfaces
- Operations runbooks
Data migration
Source systems are profiled, fields are mapped, and data is cleansed before it moves. Trial loads run and are reconciled against the source, and the migration is scored in PreFlight before cutover rather than after it.
Deliverables
- Mapping specification
- Migrated data
- Reconciliation evidence
Optimisation
Work after go-live, on a system now in use: processes redesigned, steps automated, reporting extended, and further modules brought into use as you are ready for them.
Deliverables
- Optimisation roadmap
- Executed changes
- Record of each change
Application management
The system is operated, patched and extended after go-live. Incidents are handled against agreed response levels, changes are assessed before they are made, and SAP's releases are reviewed for their effect on your configuration.
Deliverables
- Monthly service review
- Wave Health snapshot
- Backlog burndown
Delivery quality
The score you see while we work
Every Raptors engagement runs on PreFlight, whichever of the six services it is. Reviews, workshop surveys, quality gates and test cycles feed one composite score for your project, and the same score bands apply from the first phase to the last. You have access to your project from the first day. It is the view we work from ourselves, not a report prepared for a meeting.
SAP Activate
The six phases behind every service
SAP Activate is SAP's methodology, not ours. It is the same six phases whichever SAP product is being deployed, and it is what the services above are organised around. Scoring begins at Prepare, because that is where a project exists. Discover happens before it.
Discover
The evaluation phase, before a project exists: the solution is assessed, the case is made, and the deployment approach is decided.
Prepare
The project is set up to be governed: team, steering committee, phase schedule, baseline dates, and the standard system activated.
Explore
Fit-to-standard workshops match your processes to the standard, and every gap is recorded with a decision on how to close it.
Realize
The solution is configured to the agreed design in successive cycles, with integrations built and data migrated in trial loads.
Deploy
Cutover is planned and rehearsed, users are trained, acceptance testing runs, and go-live is agreed on documented readiness.
Run
The solution is live. Hypercare covers the settling period, then the system moves into normal operation and continued support.
Your part
What we ask of you
Process owners in the workshops
Fit-to-standard works when the people who run the process are in the room. We ask you to name a process owner for each area in scope, and to give them the time to attend the Explore workshops and to decide on gaps. Their anonymous survey at the end of each session is one of the inputs to the score.
Testers who raise defects
In Deploy, your testers execute the acceptance scenarios and raise defects directly in PreFlight. The pass rate of each test cycle is recorded and feeds the score. Which test cycle types count toward the score is agreed with you in Prepare, so nothing is measured that you did not agree to.
Talk through how we would run your project
A first call covers what is in scope, which phases apply, and what you would see in PreFlight from the first day.