Recommended
Recommended
More Related Content
Similar to Claremont Cloud Top Ten Tips
Similar to Claremont Cloud Top Ten Tips (20)
Recently uploaded
Recently uploaded (20)
Claremont Cloud Top Ten Tips
- 1. Insider’s Top 10 Tips to a Successful Cloud ERP Implementation Patrick Hopkins | Managing Consultant / Capability Lead
- 2. Top 10 Tips #1 COTS is king
- 3. Top 10 Tips #2 There’s lots of collateral out there - Use it! MOS https://support.oracle.com/ Oracle Docs http://docs.oracle.com/en/ OER http://www.oracle.com/webfolder/technetwork/docs/HTML/oer-redirect.html Oracle Documentation Links (Doc ID 1597048.1) https://cloud.oracle.com Product Development Training etc… Do your homework!
- 4. Top 10 Tips #3 Planning & Communication
- 5. Top 10 Tips #4 • Cloud is a re-implementation • Opportunity to remove redundancy e.g. Chart of Accounts design/re-design • A chance to revisit existing EBS architectural decisions – you don’t have to just “lift and shift” …. • Data Cleansing opportunities etc… Change Management
- 6. Top 10 Tips #5 Involve Oracle Playing by the Rules Being “easy” to deal with Working With Oracle (not against)
- 7. Top 10 Tips #6 The Only method of communication with Oracle • Closely monitor – daily - morning and night • One SR per query per pod • Lots isn’t necessarily “bad”… but … • They take significant “management” • Never use the phrase “Well … in EBS it …” – destination naughty step! SR Management
- 8. Top 10 tips #7 But that experience isn’t wasted Remember Cloud ERP is already at R11 – footprint and functionality expanding This isn’t EBS
- 9. Top 10 Tips #8 Iterative approach of OUM FP1 FP2 UAT • …Consider PoC’s / Accelerators for larger Roll-Outs • Shorter implementation cycle than a traditional EBS project • The time/cost savings are available by NOT customising and adoption of leading business processes and Cloud functionality • Monthly patching/x2 Upgrades p.a. – possibly mid project … A Rapid Implementation But don’t take shortcuts!
- 10. Top 10 Tips #9 Implementation Team: Support moving forward – more than just an implementation partner The Importance of a Great Team
- 11. Top 10 Tips #10 For Pod think “environment” • How many? • What for? • Who uses? • When? • Establish Rules of Engagement • Robust Documentation • P2T requirements • SR per pod • Remember cadence Pod Management
- 12. Conclusions • Planning & SR management is critical (e.g. P2T) • Adoption of leading practice business processes and standard product • Research and don’t assume - test • Adopt a realistic timeframe to your implementation • Invest time in SR Management • Utilise your pods efficiently • Moving to SaaS means collaborating with Oracle and your Implementation Partner longer term beyond the initial implementation SaaS is different but ….. there are many similarities to a traditional EBS implementation Remember…
- 13. Q & A www.claremont.co.uk Patrick.Hopkins@Claremont.co.uk Where do I go next? Other queries:
Editor's Notes
- Capability Lead for ERP – EBS & Cloud I’ve now completed two successful and referencable Cloud ERP projects
- What’s COTS? – for COTS read Commercial Off The Shelf /aka vanilla/ OOTB Think of a train analogy – your Cloud journey – you get on that train and travel but as a passenger … not as a train driver – Oracle are driving the train Continually improving product - customisations are not applicable as useful improvements become part of the standard product There are extendible options even with SaaS – there’s PaaS/3P Providers/Project Visual Code etc …. So you are always looking at what is possible within these boundaries …
- There’s no excuse not to …. No GLIG/GLUG.pdf’s anymore etc …. All web based so should all be current
- Lead Consultant/Solution Architect play a pivotal role, As does, does having a Strong client lead empowered by the business to drive the changes that need to happen client side for SaaS to be a success Essential to maintain a realistic expectation of what’s possible within the timelines and project scope you are facing
- The elephant in the room is that Cloud is ALWAYS a re-implementation This means you have a number of choices available - Fresh start / keep the good bits / lift and shift – or any mix of the above
- New roles (ISM/CSM’s) – they are there to help you succeed – request and involve your ISM throughout I had calls with mine every Monday and used him as a point of escalation when necessary Critical Accounts Manager – very useful to get you’re project across the line and LIVE– Treat Oracle as you would like to be treated – keep your promises
- SR = Service Request Raised through MOS – aka Metalink/Web IV for those who remember that far back ….
- Think of Fusion as the best bits of “the acquisitions” but PO Vendor, DFF’s, CVR’s are ALL still in there … Functionality is always expanding as is the footprint .. E.g. Budgetary Control & Encumbrance accounting came in at R9
- Much shorter Time to Value (TTV) Think Configuration rather than Customisation Plan for the upgrades – even take advantage of them Very limited options for delaying any monthly patching or upgrade….
- Critical that client SME’s are involved and empowered to make decisions there and then … To achieve the shorter implementation cycle …. Maintaining flexibility throughout
- Staging Pods/Prod Pods Initial recommendation was x2 – now x3 for that first year at least… The “good old days” of 10+ environments on a large project are gone … unless of course you need them … Configuration copy options are there top be used e.g. Production To Test (P2T copies)
- Cloud - It’s a different product/approach/mind-set Oracle’s investment in Cloud is significant – it will work Big organisations are moving – Significant savings are available to be made It’s not just about an implementation but engaging with an implementation partner Not just you and Oracle but you, Oracle and your partner working collaboratively to exploit the continually improving functionality ….
- Please feel free to follow up …..