North DakotaUniversity System

Campus Solutions

Project Plan

Campus Solutions Upgrade to 9.0

September 28, 2007, Baseline Version

Presented by:

Jennifer Kunz, PMP

Assistant Director, Campus Solutions

Table of Contents

Introduction

Purpose of this document

Background

Project Purpose

Project Assumptions and Constraints

Project Approach

Scope Management

Product Scope

Project Scope Statement

Scope Control

Acceptance Management (Deliverable Acceptance Process)

Time Management

Baseline Schedule

Schedule Control

Cost Management

Budget

Cost Control

Quality Management

Quality Control

Human Resources Management

Project Organization Chart

Team Directory

Roles and Responsibilities

Communication Management

Communication Management Plan

Risk Management and Issue Management

Risk Management Plan

Issues Management Plan

Appendix I

Baseline Project Schedule

Appendix II

Training Plan

Potential Classes

Testing Plan

Functional Testing

Technical Testing

Appendix III

Change Control Log

Risk Management Log

Issue Management Log

Deliverable Acceptance Log

Baseline Project Plan Approval

Sign-off

Introduction

Purpose of this document

The purpose of the Project Plan is to define the project scope, schedule, budget, and quality expectations of the project, and to provide a comprehensive strategy for managing the project.

Background

Project Background:

ConnectND is North Dakota’s implementation of Oracle PeopleSoft financials, human resources, and student administration applications across North Dakota’s State Government and University System. The Oracle PeopleSoft implementation provides web-based applications for its users.

NDUS Institutions originally went live with Campus Solutions, beginning in October 2003 with two pilot campuses. In 2004, five additional campuses went live with campus solutions and in 2005, the remaining four campuses were live. In 2005, PeopleSoft was purchased by Oracle.

Business Need:

The decision on whether to upgrade or not, or whether to upgrade to version 8.9 or 9.0 was based upon several factors. The primary driver to upgrade is Oracle published end dates for application support. The Campus Solutions portal will go unsupported in March 2008 and the application software will go unsupported at the end of August 2008. The lack of support would mean that changes to meet regulations and security, performance and other issues would not be available and the application would fail to meet business requirements.

In determining whether or not to upgrade to 9.0 several factors were considered. First, in the Oracle Health Check it was Oracle’s opinion that we should bypass version 8.9 and move directly to 9.0. Second, 9.0 offers much additional functionality not provided in version 8.9. Many of these are the functionalities, such as the ability to have multiple GPA’s or the ability to easily modify the transcript, which the Institutions have been requesting. Third, the 8.9 software, from what we’ve become aware of on the listserv, has many issues that are resolved in 9.0.

The decision to move to the Oracle 9.0 Enterprise Portal is to keep all software in sync and to allow us to fully take advantage of the software’s capabilities.

It was these factors that led us to determine that version 9.0 would be a much more viable product for upgrade versus 8.9. Finally, Oracle is providing migration paths from versions 8.0 to 8.9 and 8.0 to 9.0. The version 9.0 software puts the Institutions of the NDUS in a much better position for eventual movement to the Fusion product.

The decision to move to the Oracle 10g database software was driven by the Oracle Health Check which indicated that we would gain performance and be better prepared for Fusion by using this opportunity to change databases. Application changes will also more likely be available and tested on the Oracle database prior to that of other vendor’s products.

Project Purpose

The purpose of this project is to upgrade the existing NDUS student administration system to Campus Solutions 9.0 and to migrate the database from a SQL platform to an Oracle platform.

Project Assumptions and Constraints

Assumptions:

  1. Project staffing will be sufficient to allow us to meet the deadlines imposed on the project plan and if it is not, we will hire contracted resources.
  2. Consulting help will be available to assist us through this first major upgrade and to ensure that we continue the level of support for 8.0.
  3. Campus staff, especially the User Groups, will be availableto ensure the project keeps progressing; the project management team will give campus staff at least 30 days lead time, but sometimes only a short notice will be possible.
  4. The project scope and schedule will be driven by effort estimates.
  5. Sufficient consulting assistance will be available for loading of both the Oracle database as well as the conversion of current data.
  6. Sufficient funding will be available for training of programming and technical staff with changes to the technology.
  7. At the appropriate time during the upgrade there will be a stop put on all developments and migrations of projects.
  8. We will need to maintain the bundles and fixes on the current 8.0SP1 system.
  9. After the infrastructure upgrade and the start of the Fall 2007 semester, this project will have priority status over all other projects and staffing will be adjusted accordingly.
  10. Staff will, in general, be able to maintain a normal work schedule and take vacation time which if not taken will be lost according to NDUS policy.
  11. New functionality will only be considered for implementation at this time if it replaces an existing customization.

Constraints:

  1. Schedule:
  2. Ideally, the application and database would have been implemented separately and the project begun earlier. The availability of funding set the start date. There is a need to complete the project prior to the end of August 2008 due to loss of support. Implementing over the summer months prior to students returning is preferred.
  3. Due to the steep learning curve with the products of this project and the unknowns of the new technology, the tasks cannot be thoroughly scoped very far in advance. Task start/end dates will be firm only within 30 days of this plan version and/or a status communication. High-level dates for tasks will be provided out to 90 daysand are somewhat firm, but any dates beyond 90 days are not firm and are subject to change due to the necessity of the gradual detailing of the scope and schedule.
  1. Project Dependencies:
  • The project will overlap with the Financials upgrade and there may be concern whether we have sufficient technical staff. Additionally, we have a dependency on hiring additional staff plus having consulting staff to ensure the upgrade and the maintenance of the current software is maintained. We will still need to do all the Federal Updates on 8.0 during this time which takes several weeks and will happen 6-8 times during the upgrade. Having the staffing levels to support both projects will put constraints on what can/can’t be accomplished. We have 14 major projects to implement during this time and having the time, resources, and campus assistance will be vital to ensuring we meet all deadlines.

Project Approach

The method of project management to be used in the project is based on the Project Management Institute’s ( Project Management Body of Knowledge (PMBOK) and the North Dakota Project Management Guidebook ( Both methodologies are based on initiating, planning, executing, controlling, and closing processes to ensure that the project completes its objective on time and on budget, while meeting the quality expectations of the stakeholders.

1

Baseline Project Plan for the Campus Solutions Upgrade to 9.0

Scope Management

Scope Management involves the identification of all the work required, and only the work required, to complete the project successfully. In an effort to ensure the deadlines are met, a comprehensive project scope statement is necessary. Without a thorough understanding of the scope, we run the risk of missing deadlines which are critical to campuses

Product Scope

The product scope is thesoftware, hardware, features, functions, etc. that are being delivered. It is the “what.” The major products of this project are as follows:

  1. New hardware
  2. Oracle 10gR2 Database
  3. All new environments (Demo, Test, Stage, Production, Query)
  4. 9.0 Oracle PeopleSoft Campus Solutions
  5. 9.0 Oracle PeopleSoft Enterprise Portal
  6. PeopleTools 8.49
  7. UPK (User Productivity Kit)
  8. Third-party product modifications

Project Scope Statement

The project scope is the work that must be accomplished in order to deliver the product. It is the “how.” The project scope for this particular project is first broken down into initiating, planning, executing, monitoring and controlling, and closing phases. These phases are further broken down into tasks and deliverables.

NOTE: the numbering of the tasks corresponds with the numbering in the project schedule.

  1. Campus Solutions Upgrade to 9.0

1.1.INITIATING

1.1.1.Contract Negotiations

  • Deliverable: Signed Contracts
  1. Finalize the NDUS Business Case
  2. Deliverable: Project Business Case
  3. Develop the NDUS Project Charter
  4. Deliverable: Acceptance of Project Charter
  5. Define Oracle planning services and Schedule the Upgrade Planning Workshop

1.2.PLANNING

1.2.1.Develop Project Plan

1.2.1.1.Develop Scope, Schedule, Budget and Risk, Quality and HR Mgmt Plan

1.2.1.2.Draft the Training Plan

1.2.1.3.Draft the Testing Plan

1.2.1.4.Draft the Environment Management Plan

1.2.1.5.Draft the Application Maintenance Plan

1.2.1.6.Deliverable:BaselineProject Plan

1.2.2.Project Planning Kickoff Meeting - Internal Managers

1.2.3.Oracle Upgrade Planning and Strategy Workshop

  • Oracle attends on site for this workshop to review and plan all activities that will occur in their ‘ApplicationSolutionCenter’ (lab). This workshop will be done in correlation with the Planning Workshop
  • Deliverable(Migration Milestone #1): Platform Migration Workshop and Platform Migration Report
  1. Finalizethe Cutoff Date for Development
  2. Project Kickoff Meeting - CND and ITSS Staff
  3. CAC and Oversight Project Kickoff Meeting
  4. User Group Kickoff Meeting
  5. Develop MS Project Server and Project Repository

1.3.EXECUTING

1.3.1.CND Staff Training

1.3.1.1.Learn the New Release (this occurs throughout the project)

  • Throughout the project, all team members should reference the information on Customer Connection including: Benchmark performance reports, Change Assistant documentation, Hardware and software requirements guides, Installation guides (for PeopleTools and the product), PeopleTools PeopleBooks, Platform certifications, Product documentation (PeopleBooks), Red papers, Release notes, Upgrade guides, Upgrade pages (upgrade documentation, template and scripts, planning info.)
  1. Training Classes for Staff
  2. See Training Plan in Appendix II for details on planned or upcoming training classes

The following classes have already occurred:

1.3.1.2.2Oracle 10gR2 Administration I

1.3.1.2.3Oracle 10gR2 Administration II

1.3.1.2.4Oracle Enterprise Manager 10g Grid Control

1.3.1.3.UPK Planning and Implementation

1.3.1.3.1UPK Planning

  • Determine how to deploy UPK
  1. UPK Implementation and Testing
  2. Install and test UPK
  3. NOTE: the details of how UPK will be used will be a part of the Training Plan in Appendix II.

1.3.2.Prepare Technical Environments

1.3.2.1.Complete Pre-Installation Checklist

  • This checklist must be sent to Oracle before they will complete their installation of DEMO and certification
  1. Package Database for the Upgrade Lab
  2. The DBA’s will perform various tasks per Oracle’s instructions to package the database and send it to the Lab.
  3. Planning must take place before and after the database is sent, because all subsequent customizations that change the table structure must be tracked very closely as they won’t be part of the first compare report.
  4. Schedule the Oracle Installer to be onsite for the installation in DEMO.
  5. Create and Certify DEMO Environment
  6. This involves multiple tasks related to network configuration, hardware and operating system installation, and installing the Oracle 10g database shell into the DEMO environment (Oracle will assist with this as part of the contract). Crystal and COBOL will also need to be installed, but before doing so, those licenses must be verified and/or acquired.
  7. Oracle will perform the following services onsite according to Exhibit 1 of the contract:
  8. Install the standard functionality contained within Campus Solutions version 9 (PeopleSoft application and PeopleTools 8.49)
  9. Deliverables: Certification / Post Installation Checklist (a completed checklist verifying the implementation readiness of the Installed Software as demonstrated by the Install verification Test) aka certification of DEMO by Oracle.
  10. Set up Access
  11. Technical staff must perform a series of tasks to make the DEMO environment accessible to other CND/ITSS staff.
  12. NOTE: DEMO is one of several environments to be created, described as follows:
  13. DEMO: this will remain ‘vanilla’ and be used as it is today
  14. TEST (SYS): this will be where the developers build projects, queries, programs and functional analysts do their initial testing
  15. STAGE: this environment will be a scaled down production environment. This environment will include multiple web servers, app servers and a clustered database. It will be used as a last test for developments. Users will also do their final testing in this environment.
  16. PRODUCTION: This will remain as it is today
  17. QUERY: for query writers
  18. LOAD TEST: This environment will be built after the go-live date. This environment is exactly like production and will be used to perform load tests
  19. Planning for Tools, Access, Bundles, Migrations, and Refreshes
  20. Planning meetings and research in order to make decisions on the following areas: tools, access, bundles, migrations, and refreshes.
  21. Create PROD Environment
  22. This task is similar to the creation of the DEMO Environment, including the network services configuration, hardware and operating system installation and installing the Oracle 10g database shell. In addition, PeopleTools 8.22 should be installed and Data Mover and App Designer will need to be tested. Refer to the detailed technical plan (spreadsheet for specific details and steps).
  23. Create TESTand STAGEEnvironments
  24. Post Install Management for All Environments
  25. Various technical tasks required to plan and manage the Oracle environments (refer to schedule details and/or associated technical plan).
  26. Environment Management and Tuning
  27. General Environment Management and Tuning
  28. Performance Tool Setup
  29. Plan for Load Testing and Update the Master Test Plan
  30. Customization tracking
  31. Bundle 19 for 8.0 PROD
  32. Bundle 20 in 8.0, Bundle 4 in 9.0 (1098T & Fixes, to be available Aug. 24)
  33. Bundle 21 in 8.0, Bundle 5 in 9.0 (Regulatory Release 1, to be available Nov. 2)
  34. Bundle 22 in 8.0, Bundle 6 in 9.0 (Regulatory Release 2, to be available Jan. 18)
  35. Critical Fix (to be available mid-Feb.)
  36. Bundle 23 in 8.0, Bundle 7 in 9.0 (Regulatory Release 3, to be available Apr. 18)
  37. NOTE: it does not appear that there will be time to do Bundle 24 for 8.0 (8 for 9.0) before go-live.

1.3.3.Oracle Database Platform Migration and Upgrade Services (in Upgrade Lab)

1.3.3.1.Oracle DATABASE MIGRATION Services (according to Exhibit 2 of the contract):

  • Compare our existing release to a vanilla version of the same release
  • Deliverables (Migration Milestone #2):Standard Oracle Compare Reports; Vanilla Compare Spreadsheet
  • Evaluate the results of the compare reports and update existing Platform SQL syntax objects: Records View, Peoplecode, Application Engine and Structured Query Reports (SQR’s) as appropriate for the new Target Platform and document the updated objects in a MS Excel spreadsheet. Create SQL-to-Oracle database migration scripts designed for use to migrate one copy of our PeopleSoft production environment using proprietary migration tools.
  • Deliverables (Migration Milestone #3): Database Migration Scripts, PeopleSoft Datamover export of the PeopleTools Tables, Updated Vanilla Compare Reports
  1. Oracle UPGRADE Services according to Exhibit 3 of the contract:
  2. Compare our existing release to an “out-of-the-box” version of the new release and provide us with the standard Oracle compare reports and an Excel spreadsheet containing the results of the vanilla compare. Compare our PeopleTools queries contained in our existing release with the standard fields and records contained in the standard “out-of-the-box” upgrade release and provide us with an Excel spreadsheet showing the results of the query Jumpstart Tier 1. Compare our SQR’s/SQC’s contained in our existing release with the standard fields and records contained in the standard “out-of-the-box” upgrade release
  3. Deliverables (Upgrade Milestone #1):

Standard Oracle Compare Reports – Vanilla and New Release

Vanilla compare spreadsheet in MS Excel

Query Jumpstart Tier I Reports

SQR Jumpstart Tier I Reports

  • Initial Upgrade Steps
  • Deliverables (Upgrade Milestone #2):

A PeopleSoft Datamover export of the PeopleTools tables at the upgrade release after the initial upgrade steps have been completed

Standard Oracle data conversion programs contained in our upgraded release modified to include our custom added record/field objects.

Our changes to reapplication objects contained in the existing release manually reapplied to the upgraded release.

The latest certified PeopleTools release

A record of the decisions made by Oracle regarding the reapplication objects in the Excel spreadsheet containing the results of the new release compare

1.3.3.3.NDUS Obligations with Oracle Lab Services

  • Participate in weekly Oracle Status Meetings
  • Identify customizations that will be retained, removed, remapped, or renamed
  • Review Migration Preparation Checklist and Upgrade preparation Checklist documents and return to Oracle by August 31.
  • Review Defaults Questionnaire for LS 801-90 and return to the lab by August 31.
  • Review functional steps in Ch. 1 Upgrade Instructions in order to perform on MSS copy of production take prior to Test Move.
  • Complete the ASC Upgrade Services discovery questionnaire

1.3.4.Perform Test Moves (into TEST (SYS))

1.3.4.1.Develop Master Test Plan

1.3.4.2.First Test Move

1.3.4.2.1Preparations and Create SQL Copy of Production

1.3.4.2.2Perform the First Test Move

  • On-site Database Migration Test Move Services – Oracle will migrate one copy of our PeopleSoft production environment from SQL to Oracle.

Deliverables (Migration Milestone #4):

  • Up to 15 person days of onsite technical assistance
  • Database Platform Migration Design Document
  • On-site Upgrade Test Move Services – Oracle will upgrade a copy of our existing release in its production environment to version 9.0.

Deliverables (Upgrade Milestone #3):