Project Update – High Level Timeline 
             Project Phases                                                          2013                                                                        2014
                                                      Jan Feb Mar Apr May Jun              Jul   Aug Sep Oct Nov Dec Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec
          Discovery Phase                                    100%
          (6/1/2012-4/30/2013)
          Planning & 
          Analysis Phase                                           65%
          (12/15/2012-6/30/2013)
          Build Phase
          Test Phase
          Phase 1 Rollout
          Phase 2 Rollout
          Closure Phase
                 Indicates percentage of work complete.
                 Indicates percentage of unfinished work.
                 Future phase timing TBD.
                                                                                                         2
        Project Update – Status of Current Activities
           Project             Continuing governance meetings with Executive & Steering Committees and 
        Governance             Business Sponsors; work streams working through design questions
           Change              Stakeholder analysis complete; second communication with a project update 
        Management             sent 
          Business             “As Is” Meetings complete; leveraging SMEs from businesses for work streams
        Engagement
          Business             Requirements being compiled including functional business requirements and 
          Analysis             future business process flows
           Training            Additional Oracle University Training Session Scheduled for July (7/15 and 7/16)
         Committee             Next Executive Committee Meeting 6/27
          Reporting
         No Major issues foreseen. Confidence level is high.
         Issues needs to be resolved. Go- Live not in jeopardy.
         Major issues foreseen. Confidence level is very low.
                                                           3
          Project Update – Asset Project Risks
                                Project Risk                                   Approach  (Accept, Avoid, Transfer, Mitigate)
          Oracle’s Technical Infrastructure capacity may need                Accept - Separate infrastructure upgrade project will need to be 
          to be augmented before full rollout                                initiated
          Lack of business resources available to the project                Avoid / Mitigate - Early identification of resource needs; backfill 
                                                                             critical project team members if necessary
          Lack  of  agreement  on  critical  process  or                     Avoid / Mitigate - Early identification of critical areas where all 
          configuration decisions                                            schools  will  need  to  agree;  careful  tracking  of  key  issues  / 
                                                                             decisions; early escalation where appropriate 
          Resistance  by  the  business  to  needed  business                Avoid / Mitigate - Early and frequent communication; focus on 
          process redesign                                                   effective  change  management;  inclusion  of  all  TUBS  in 
                                                                             requirements gathering / design
          Key decisions on Accounting Policy and Treatment                   Mitigate  -  Early  decision  making  around  policy  and  treatment 
          to enable system design  and configuration                         questions;  careful  tracking  of  key  issues  /  decisions;  early 
                                                                             escalation where appropriate
          Data Integrity & Conversion / Ability to meet Oracle               Mitigate - Identify data conversion issues early, set expectations 
          requirements                                                       around system requirements; consideration of all TUBS in data 
                                                                             conversion plan
          Ability    to   rollout  new  solution  to  sponsored              Accept – Schedule roll out to schools with significant sponsored 
          community  during  base  year  for  calculation  of                impact at conclusion of base year
          overhead rates
          Requirement of Oracle Assets to source information                 Mitigate  –  Define  options  for  addressing  with  AP;  minimize 
          from AP                                                            changes directly to GL
                                                                                  4
     Project Update – Next Steps & Deliverables
     • Business Analysis
         – Continue Detailed Functional Requirements
             • Business requirements, integration points, project scope
         – Complete Proposed Future State Design 
         – Continue Business Process Flows by Role
         – Review with TUBs / Schools
     • Change Management
         – Conduct Impact Analysis
         – Continue Communication
     • Project Management
         – Project Planning for Next Phase
         – Develop Roll-Out Strategy
                                        5
                        PROJECT SCOPE
                                   6