1 / 25

FIS Enterprise Solutions EPK/EPM Implementation

FIS Enterprise Solutions EPK/EPM Implementation. Debbie Bellish, Jon Hale, Truman Hale, Daun Hugi, Barb Mours Fidelity National Information Services (FIS). Agenda. Business Situation Implementation Approach and Schedule Lessons Learned Results Sample Views/Reports. Business Situation.

noah
Download Presentation

FIS Enterprise Solutions EPK/EPM Implementation

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. FIS Enterprise SolutionsEPK/EPM Implementation Debbie Bellish, Jon Hale, Truman Hale, Daun Hugi, Barb Mours Fidelity National Information Services (FIS)

  2. Agenda • Business Situation • Implementation Approach and Schedule • Lessons Learned • Results • Sample Views/Reports

  3. Business Situation • Large geographically dispersed resource pool of 750 serving 100+ financial services customer account teams • Resource staffing requirements/capabilities critical • Access database utilized for resource staffing • PMBOK-based project management methodology • Formalized in 1999 and continuously improved • Emphasis on scope, time (schedule) and budget management with software development influences • Defined project management roles and organization • Manually intensive report production • Lotus Notes database for document (including .mpp files), risk, issue, action item management • Minimal user Project Server experience • Other divisions had implemented Project Server User’s Meeting January 23-25, 2007 3

  4. Business Situation Project Objectives: • Integrated project and resource information • Enhanced capacity and resource planning capabilities • Presented in automated, user configurable dashboard views User’s Meeting January 23-25, 2007 4

  5. Project Team Arrangement

  6. Implementation Approach • Phased Approach • Phase 1 - Implement MS Project 2003 Server, MS Project Professional 2003 and MS Project Web Access (PWA), EPK Portfolio, EPK Resources, and Enterprise Resource Planning • Retire Access database Complete

  7. Implementation Schedule User’s Meeting January 23-25, 2007 7

  8. Approach and Schedule Phased Approach Phase 2 - Implement MS Share Point Team Services (document management and team information), Rational (risks, issues, action items, defects) and automated status reporting Retire Lotus Notes tool Phase 3 – Implement EPK Time and interfaces to Oracle Financials Retire PlanView In Progress – 1Q ‘07 2007 Dates TBD User’s Meeting January 23-25, 2007 8

  9. Lessons Learned • Successes • Smooth implementation facilitated by: • Established resource and project management practices • Heavy user involvement in requirements, testing and support • Virtual training and job aids, plus live meeting Q&A sessions, provided on demand training solution for users • Opportunities/staffing guidelines identified tool best practices • Change champions facilitated tool adoption • Inclusion of requirements into EPK core product • EPK Group configuration review User’s Meeting January 23-25, 2007 9

  10. Lessons Learned • Challenges • Virtual team: needed face-to-face interactions at critical junctures • Internal project that required significant project management discipline • Recreating Access database functionality vs. defining “real” requirements • User representatives needed direct line of communication with EPK Group regarding requirements • Delayed testing of EPK and lack of understanding of core functionality led to theorizing about the tool

  11. Lessons Learned • Challenges • Integration with corporate HR systems, e.g., PeopleSoft • Major configuration error (most codes on Project Server vs. EPK) corrected late in the development cycle • Lack of resource Requirements visibility in Capacity Center requires reliance on reports vs. standard EPK functionality User’s Meeting January 23-25, 2007 11

  12. Results • Other FIS divisions have adopted (or plan to adopt) EPK after reviewing the solution • Increased productivity • Collocated, refreshed project status and resource information readily available • Portfolio visibility for executives and senior management

  13. Sample Project Health Views

  14. Sample Resource Plan User’s Meeting January 23-25, 2007 14

  15. Sample Project Financial Views User’s Meeting January 23-25, 2007 15

  16. Sample Capacity Center Views User’s Meeting January 23-25, 2007 16

  17. Sample Capacity Center Views User’s Meeting January 23-25, 2007 17

  18. Sample Reports User’s Meeting January 23-25, 2007 18

  19. Sample Reports User’s Meeting January 23-25, 2007 19

  20. Sample Reports User’s Meeting January 23-25, 2007 20

  21. Sample Reports User’s Meeting January 23-25, 2007 21

  22. Sample Reports User’s Meeting January 23-25, 2007 22

  23. EPM Information Site User’s Meeting January 23-25, 2007 23

  24. EPM/EPK Training Solution User’s Meeting January 23-25, 2007 24

  25. Questions?

More Related