CAMPUS EXECUTIVES
Upcoming SlideShare
Loading in...5
×
 

CAMPUS EXECUTIVES

on

  • 589 views

 

Statistics

Views

Total Views
589
Views on SlideShare
589
Embed Views
0

Actions

Likes
0
Downloads
10
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

CAMPUS EXECUTIVES CAMPUS EXECUTIVES Presentation Transcript

  • The CUNY ERP Project Campus Executives
  • ERP Project Management
    • Agenda
      • Members of the ERP Project Management Team
      • Glossary of Key Project Management Terms
      • Key Project Management Requirements of the RFP
        • Project Planning
        • Scope Management
        • Status Reporting
        • Issue Management
        • Risk Management
      • Questions and Answers
  • Accountable Entities of the ERP PMO E G X A E R T T E N R R Implementation Partner Project Management Office Implementation Partner PMO CUNY ERP PMO Primarily responsible for Project Management activities Provides oversight, adheres to CUNY standards, manages contracts Exeter provides Project Monitoring Services and is CUNY’s independent verification and validation partner Gartner provides independent Quality Assurance services The ERP Project Management Office
  • Future State – ERP STUDENT RECORDS ADMISSIONS/PROSPECTING STUDENT FINANCIALS FINANCIAL AID HUMAN RESOURCES (HCM) GENERAL LEDGER CAMPUS COMMUNITY Acctg Depts Depts SINGLE DATABASE AND MULTI-INSTITUTIONAL Financial Aid Not Always Multi-Institutional Admissions Not Always Multi-Institutional AN ERP SYSTEM IS A SET OF FULLY INTEGRATED MODULES
  • Student System Phasing
    • We intend to phase in the colleges on the new student system in “waves”
    • The first wave of colleges are referred to as the “Vanguards”
    • The ERP implementation for these two colleges will examine business processes CUNY-wide, so all colleges will be participating
    • The Vanguards will be the “model” implementation for the rest of the university in terms of business processes
  • Student System Phasing
    • Financial Aid will be implemented for ALL CUNY colleges after the Vanguards are in production
    • Remaining colleges will be brought onto the ERP student system in waves
    • Current legacy system state presents some challenges in phasing in the ERP modules
  • HR Functionality: Phase 1 TBD Dec 07 Talent Acquisition and Candidate Gateway TBD July – Sept 07 Base Benefits June 07 – June 08 April – May 2007 CORE HR (includes workforce administration, labor relations administration, position management, managing base compensation, regulatory reporting) DESIGN FIT/ GAP FUNCTIONALITY
  • HR Functionality: Phase 1 (cont.) TBD Spring 07 Concurrent with ERP Phase One, OFSR will Implement Time and Attendance System This system will link to ERP system in Phase 2 TBD July 07- Sept 07 Payroll Interface
  • HR Functionality: Phase 2 TBD Jan 09 – April 09 Absence Management TBD Jan 09 – April 09 Time and Labor TBD Jan 09 – April 09 Advanced Benefits Administration TBD Feb 09 Competency Management (e-Performance Evaluation, Recruitment, Workforce Planning) DESIGN FIT/ GAP FUNCTIONALITY
  • Some Anticipated Outcomes
    • Automated Workflows
    • On-line applications
    • Electronic Processing of Applicants Including Search Committees
    • Payroll Interface with City and State (Phase One for demographic data; Phase Two – pay data
    • Benefits Repository
    • Employee and Manager Self-Service in a managed phased implementation
    • Team as “Agents Of Change”
      • Periodic Meetings
      • Rotating Campus Locations
      • Act as Champions for ERP
    • Process Changes
      • Suggest
      • Endorse
    • Communication Strategy
      • Scribing the meetings
      • Notes out – Issues tracked
    • Handout
    The Finance Liaison Role
    • Training Vision: Train the Trainer
      • Core Team
      • Super User
      • Power User
      • End User
      • Discussion
    • Training Liaison Vision
      • Discussion
    CUNY ERP Training
  • CUNY ERP Training
    • Current Training Needs
      • Schedule
      • Project (Core) Training
      • SME Training
      • Facilities: Current and Future
    • “ Why training matters!”
      • Learning Approaches
      • Productivity
      • Problem-Solving
      • Primary Knowledge
  • Communication Goals
    • What do we want to accomplish?
      • How we’ll communicate?
      • What are the best channels to pass along information?
      • What are the campus-unique ways to get information around?
      • What’s next?
  • Common Liaison Roles and Responsibilities
    • Direction and Input
    • SME Panels
    • SME Work Teams
    • Campus Liaisons
      • Champion
      • Serve as SME
      • Secure SME from Campuses
      • Campus Implementation/Readiness
  • Fit/Gap Analysis
    • Examine how ERP software “fits” into our CUNY business processes
    • Explore the changing of business processes to come up to “best business practices” within higher education (which ERP software delivers), and to enable improvement of administrative services
    • If CUNY has a business process not delivered by the software, or a business process unique in higher education, negotiate the “gap”
  • Fit/Gap Analysis
    • Software will be ”configured” jointly by vendor consultants working with CUNY subject matter experts (SME’s), who provide CUNY specific knowledge
    • SME’s will be learning to configure many functions currently maintained by programmers (see example on next page)
  • Business Process Re-design
    • Define Business Process Re-Engineering (BPR)
      • Reengineering is the fundamental rethinking and redesign of business processes to achieve dramatic improvements in critical measures of performance, such as cost, quality, service, and speed.
      • (Hammer & Champy, 1993)
    • How can ERP help with BPR?
      • Our processes will fall into one of three categories:
        • Processes that can’t be re-designed due to the aging technology of our legacy systems
        • Processes we could re-design right now, but we’re waiting for ERP to motivate us
        • Processes that ERP will force us to re-design
    • Can we come up with some examples of each?
  • ERP Campus Executives
    • Organizing for high performing teams
    • Your skills continuum and effective execution
    • Managing competing responsibilities on your campus
    • Communication with the total organization
      • Go back to your teams for feedback