1. Hybrid Cloud: Partly Cloudy Becoming Mostly Sunny Kevin Muller Fordham University June 16, 2016

2. 2 Introduction EVENT: In July 2015, our ERP system moved to the cloud. This presentation will cover: Driving factors Architecture footprint Challenges to achievement Attendee take-aways: Increased understanding from first-hand experience

3. 3 1 Initiation 2 Preparation 3 Evaluation 4 Implementation 5 Continuation Agenda

4. 4 Where we began Background

5. Before the “leap”…

6. Prior to cloud planning

7. 7 Initiation Driving forces leading up to our move to the cloud

8. Required uptime

9. 9 Required uptime – Our driving force Challenges to achievement Aging hardware & storage Interconnected applications Multiple authentication platforms / methods Portal SSO, LDAP, CAS, and ERP-based authentication Clarity of attainment goal How to budget to make incremental improvement? What is our timeframe for 99.998 uptime?

10. Challenge accepted!

11. 11 Preparation Preliminary steps which helped to prepare us for what was to come

12. Test flights

13. 13 Test flights – Cloud exploration Cloud-based E-mail Previously hosted locally on multiple server (Lotus Notes) Migrated to Gmail & Google Apps Extensive contract negotiation to address privacy Multi-site, multi-location, multi-platform After Hurricane Sandy, authentication DR is diversified West coast-based “third site” is activated Rackspace-based cloud option is created & tested

14. Cloud e-mail & DR authentication

15. Next, CRM & Online Enrollment launched

16. 16 Evaluation Our move to the cloud was not an overnight success; Planning is key.

17. Plan & Negotiate

18. 18 Plan & Negotiate – The birth of… Exploratory & deep-dive consulting sessions Our unique application & server architecture review in-depth Many sessions to capture, understand & re-present Understanding was key! Then, the contract negotiations began All parties were invested in getting the details right Discussions of “less important” details are best done up-front The investment is this phase will payoff later

19. 19 Implementation The culmination of the idea, the strategy, the planning, and several months of active coordination.

20. The big move

21. 21 The big move – Pack up & check up Collaboration is critical On-site & cloud personnel team up Cloud instances are spun up easily, but config is more intense A full-fledged production system is readied Testing in PROD takes precedence over testing in TEST Secured access between sites is achieved through VPN However, IP mapping & server naming becomes tedious TEST environment is deferred until post “go-live”

22. The pioneer move – ERP moves to the cloud

23. 23 Continuation The partly cloudy forecast is starting to look more like mostly cloudy.

24. Extending the core

25. 25 Extending the core – New applications “Don’t bite off more than you can chew!” Workflow & Degree Audit implementations follow later Post-implementation upgrades & stability are prioritized Some kinks did crop up along the way Having a trusted surrogate in the managed space is critical Management from both teams meet to level-set expectations

26. Supporting ERP applications follow

27. Still working ‘em out

28. 28 Summary It helped to have explored “the cloud” beforehand Nothing is as easy as sales teams will portray A “Trust, but verify” approach is preferable Always prepare for contingencies Including backing away from the process, so as to reassess Take nothing for granted – document & confirm (in writing) With proper planning, you can be successful

29. You, too, can do it!

30. 30 Questions & Answers

31. 31 Thank you! Kevin Muller kemuller@fordham.edu