DMOne™ for SI partners
Accelerate the Oracle Fusion implementations you deliver with the DMOne™ modules, so your consultants spend less time on mechanics and more on achieving successful outcomes for the client. Your team stays in front of the client. We provide the platform, enablement and specialist support behind you.
How it works
Agree the scope
Tell us the programme, the modules you need and the phase. Commercial terms are agreed per partner and per programme.
Enablement
Your consultants are trained on the modules and given access to an environment configured for the programme.
Delivery
Your team runs the modules on the client programme. eAppSys provides platform support and product updates.
Ongoing support
Continue to use ConfigIQ™, MaskIQ™, DeployIQ™ and ArchiveIQ™ after go-live as part of your support service.
What partners get
- Access to the five DMOne™ modules for named client programmes
- Training and enablement for your consultants
- Platform support and product updates from the eAppSys product team
- Option to add eAppSys consultants from the UK or the Hyderabad Global Delivery Centre
- Hosting in the client’s OCI tenancy or an eAppSys-managed tenancy in the client’s region
Where partners use it most
- Data migration workstreams on EBS, PeopleSoft, JDE and SAP to Fusion projects
- Clear, evidenced data handoffs from the client, so late data is visible early and does not turn into a dispute
- Environment comparisons before and after Oracle quarterly updates
- New business unit and country rollouts on an existing Fusion pod
- Masked test and training environments for client UAT
- Legacy decommissioning at the end of a programme
How delivery teams use DMOne™ across a programme
Mobilise and design
Templates and mappings set up against the Fusion design.
Unit testing
Masked, representative data loaded for build teams.
Mocks
Full-volume runs with reconciliation evidence.
SIT and UAT
Separate environments loaded in parallel.
Cutover
The rehearsed process run on the same rule set.
After go-live
Business unit changes, mass updates and corrections.
What changes
Client and SI execution runs on one platform, with fewer handoffs.
What stays the same
The client owns its data, approves the rules and signs off each cycle.
Two ways to use DMOne™
Both can be used on the same programme, for example an outcome-based pilot first, then your own team taking over.
| Mode 1: you deliver on DMOne™, with our product support | Mode 2: data migration as an outcome-based service | |
|---|---|---|
| Who delivers | Your team, using DMOne™ | The eAppSys data migration team, using DMOne™ |
| eAppSys provides | Platform, onboarding and training, product support and quarterly updates | Migration outcomes, the platform and data migration specialists |
| You provide | Programme leadership, client relationship and data migration delivery | Programme leadership and the client relationship |
| Suited to | Partners building or scaling their own data migration capability | Programmes that want migration risk and outcomes owned by a specialist |
Benefits from the start of the programme
Tested migration runbooks
Migration starts from runbooks already tested on other programmes, then customised for the new client’s objects, sources and cutover plan.
Extraction, transformation and rules
Pre-built templates for extraction rules, mapping and transformation, agreed with the functional team.
Data quality analysis
Analysis of Oracle EBS source data establishes its quality before design decisions are made.
Early test data for design workshops
Once the initial design and build configuration is in place, work structures, employees, suppliers, invoices and the chart of accounts are loaded, so workshops run on representative data.
Your environment or ours
Data is loaded into a client test environment or your own lab environment.
Potential to reduce
- Client-side data migration effort: less manual extraction, file preparation and error rework
- SI rework and handoffs: fewer failed loads returned between teams
Potential to improve
- Test readiness: representative data available when testing starts
- Migration predictability: multiple cycles on top of data already loaded, not one late load
Business data owners remain essential. Benefits depend on scope and are best quantified in a value assessment for a specific programme.
Where to start
A current programme
Where data migration is at risk or about to start.
A pilot
A defined set of objects and agreed success criteria.
An architecture review
Technical due diligence with your architects.
A value assessment
Quantified effort, cost and risk for a named programme.
Discuss a programme with us
We will arrange an introductory meeting with the product team.