FIS Enterprise SolutionsEPK/EPM Implementation

Debbie Bellish, Jon Hale, Truman Hale, Daun Hugi, Barb Mours

Fidelity National Information Services (FIS)

User’s Meeting January 23-25, 2007 1

Agenda

• Business Situation• Implementation Approach and

Schedule• Lessons Learned• Results• Sample Views/Reports

User’s Meeting January 23-25, 2007 2

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

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

Project Team Arrangement

User’s Meeting January 23-25, 2007 5

Executive SponsorJon Hale

Project SponsorDaun Hugi

Project ManagerDebbie Bellish

Technical TeamLinda Lander

External Consultants

Business Analysts

DBA

Resourcing PracticesBarb Mours

TrainingScott Berrett

Project ManagementPractices

Change ManagementTruman Hale

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

User’s Meeting January 23-25, 2007 6

Complete

User’s Meeting January 23-25, 2007 7

Imp

lem

en

tati

on

Sch

ed

ule

6/1/05 9/30/057/1 8/1 9/1

Initiating & Planning / Requirements

10/3/05 11/16/0511/1

Design

11/14/05 4/14/0612/1 1/1 2/1 3/1 4/1

5/16/06 6/2/06

ReportDevelopment

12/18/05 6/30/061/1 2/1 3/1 4/1 5/1 6/1

Process and Training Development

7/6/06 8/28/068/1

Implementation

3/10EPK Group Configuration Review

EPK Custom Development/Technical Testing

4/24/05 6/30/06

User AcceptanceTesting

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

User’s Meeting January 23-25, 2007 8

In Progress – 1Q ‘07

2007 Dates TBD

Lessons Learned

User’s Meeting January 23-25, 2007 9

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

Lessons Learned

User’s Meeting January 23-25, 2007 10

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

Lessons Learned

User’s Meeting January 23-25, 2007 11

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

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

User’s Meeting January 23-25, 2007 12

Sample Project Health Views

User’s Meeting January 23-25, 2007 13

Sample Resource Plan

User’s Meeting January 23-25, 2007 14

Sample Project Financial Views

User’s Meeting January 23-25, 2007 15

Sample Capacity Center Views

User’s Meeting January 23-25, 2007 16

Sample Capacity Center Views

User’s Meeting January 23-25, 2007 17

Sample Reports

User’s Meeting January 23-25, 2007 18

Sample Reports

User’s Meeting January 23-25, 2007 19

Sample Reports

User’s Meeting January 23-25, 2007 20

Sample Reports

User’s Meeting January 23-25, 2007 21

Sample Reports

User’s Meeting January 23-25, 2007 22

EPM Information Site

User’s Meeting January 23-25, 2007 23

EPM/EPK Training Solution

User’s Meeting January 23-25, 2007 24

Questions?

User’s Meeting January 23-25, 2007 25