ACTUATE RETIREMENT PROJECT KICKOFF MEETING Butch Labrecque 12/8/06

MEETING GOALS Introduce the project & team State the vision & objectives Describe the approach Set preliminary expectations Achieve alignment

AGENDA Team Introductions Introduction by the Project Director Business Case, Objectives, Assumptions, Risks Project Management Approaches by the PM Background – Current Actuate Usage Approach to the Work, Project Cycles, Milestones, Governance Next Steps Questions

TEAM INTRODUCTIONS Role & experience with Actuate Role on the project Expectations following closeout Areas of responsibility for new solutions

INTRODUCTION TO THE PROJECT Rick Jones – Project Director Business Case, Objectives, Assumptions, Risks

BUSINESS CASE Actuate can be replace with another technology currently licensed – freeing funds for other investments Actuate maintenance lapsed Support & maintenance fees increased by vendor to $120,000 Aged hardware 5 ½ years old Runs on AIX As of June, 2007 S&O will no longer support AIX

PROJECT OBJECTIVES Primary: Retire Actuate to reduce operational support costs & simplify the architecture Replace Actuate reports with customer-accepted alternatives Establish maintenance & user support processes for new solutions Secondary: Rationalize the use of other data delivery channels

ASSUMPTIONS No new major infrastructure components Utilize Hyperion/Brio Few new information requirements Lighter analysis load Security & distribution models can be “ported” unchanged Business “owners” can be identified for each report …and they will assume responsibility for aligning Actuate users Central offices will choose to utilize existing delivery mechanisms Web Financials, HR Online

RISKS TO PROJECT SUCCESS Security &/or distribution models require changes Technical training for CIT staff may be required Increased use of Temp tables, use of SQR, integration with the Brio dashboard Clear report “ownership” not identified Maintenance & support costs

PROJECT MANAGEMENT APPROACHES Butch Labrecque – Project Manager Business Case, Objectives, Assumptions, Risks

ACTUATE USAGE What we know thus far… Users are supported, happy 92 reports “Owners” for 35 identified thus far 27 of the reports will be replaced by CUBS 17 reports go against production… the rest against data warehouses and/or flat files

AREAS OF FOCUS – DATA DELIVERY Hyperion/Brio Development, maintenance, & support SQR use with Hyperion/Brio is new Increased usage of Brio TEMP tables? Dashboard integration In general, mimicking of Actuate functionality

AREAS OF FOCUS - INFRASTRUCTURE Hyperion/Brio maintenance Changes, increased loads? New/additional Security - overlap w/ current Brio users? Apache Loads? SQR Testing & training, development & administration Dashboard Development, integration & support Implementation & Support Soft/Hard Infrastructure needs? Configuration management processes and procedures Broadening of user base

AREAS OF FOCUS – DATA WAREHOUSES Sources: HR DW & ADW Possible use of reporting tables? ETL Additional fields Reporting tables? Eye toward future dimensional models

AREAS OF FOCUS – SECURITY & DISTRIBUTION MODELS Push vs. pull HR Dept structure Accounting Org codes, departments, & account ranges Move toward Brio roles Look to VPD for row level security

APPROACH Business Analysis assist with engagement of business “owners” Produce Functional Specifications that detail the scope of the solutions to be delivered Perform Technical Analysis Outline report-by-report architectural approach & pinpoint technical tasks required “Start the assembly line” Develop replacements Test Move to production

AON NETWORK DIAGRAM (Early & Incomplete)

CYCLES OF THE PROJECT

IDENTIFIED MILESTONES Initiation Draft Project Initiation Plan (PIP) Planning & Analysis Draft Functional Specifications Approve Functional Specifications Draft Technical Specifications Re-draft Project Initiation Plan (PIP), including a schedule for replacement of each category of reports/datasets Approve Project Initiation Plan (PIP) Executing & Controlling Rewrite reports/datasets (schedule TBD) & move them to production Acceptance obtained from “owners” Closing Transition to steady state – Project closeout report End of Project Review Report (Lessons Learned)

PROJECT ORGANIZATION / GOVENERNANCE

NEXT STEPS Determine level of BA involvement Complete business “owner” identification Continue technical analysis of distribution & security models Schedule technical knowledge sharing session(s) Engage business “owners” Create customized Functional Specification templates Complete Business Analysis This will prepare us for “war room” style technical design discussions

QUESTIONS / COMMENTS?