College of Law using IPOS

Quick View
Summary: 

Review Graduate Plan of Study (IPOS) application on PeopleSoft and assess changes required to adapt this for use with students enrolled through the College of Law in the JD program.

Current Milestone: 
Mod Spec received
Stage: 
Canceled - No UTO involvement.
People
Sponsor/Champion: 
none
Project Manager: 
No Project Manager
Contact for more information: 
Roger.Lurie@asu.edu
University Technology Director: 
Leah Lommel
More Info
Source: 
Internal
Priority: 
none
Scope: 

Next Steps:

· Review list of proposed changes below and provide feedback (Please respond no later than by Tuesday, 10/14)
· Prepare a mod specification to be approved and prioritized by UTO; work to be coordinated in conjunction with the Graduate College that is currently working on other retrofits and bug fixes to this mod (Roger)
· Identify resources and timeline (UTO)

General Requirements:

The following are requirements and retrofits identified during the meeting. Please review this list and add to or edit the list.

· Establish Academic Advising requirements in PeopleSoft for the JD

o No previous degree/blanket 30 hour transfer option

o 88 credit hours, of which 64 or more must be graded (non pass/fail courses), and up to 24 hours may be pass/fail courses

o No more than 12 hours of externship

o Accept 400 level courses, in rare cases – requires petition

o No more than 4 credit hours of deficient grade work (grades of 65 – 69) on 600 level or above courses

o Required Professional Responsibility Course

· Modify IPOS and administrative interfaces to work for the LAW career
· Exclude all Law courses from ASU course page with a grade of 64 or below
· Exclude all Law courses from ASU course page with a pass/fail grade of Fail
· Create and code a petition type for 400 level courses added to POS
· Create a customizable set of culminating documents to include the following; modify the admin interface so that list os unique based on academic career, thereby separating the list for GRAD versus LAW.

o Professional Skills Requirement

o Graduation Writing Requirement

o Seminar Writing Requirement

· Calculate deadline as requirement (admit) term + 5 years
· Alter calculation of overall and POS GPA’s to accommodate numeric grading. This may be done automatically by the audit, but will need to be tested.
· Modify approval page to eliminate approval at the academic unit, Graduation Office and Graduate College and replace with one approval by the College of Law. This will require a new milestone type.
· On transfer page, pull all courses from external education page; no free form data entry of transfer courses allowed

All Milestones and Schedule: 

Mod spec

CLA v2

Quick View
Summary: 

Collegiate Learning Assessmet will need to be taken by a sub-set of Seniors as a baseline. Univeristy Evaluation Office will identify a set of Seniors, UTO will assist in any setup, taging or reporting needed.

Start Date: 
November 6, 2008
Go Live: 
January 20, 2009
Current Milestone: 
Requirement gathering - 11/26
Stage: 
Canceled - No UTO involvement.
People
Sponsor/Champion: 
none
Project Manager: 
Bonnie Stoneking
Contact for more information: 
stoneking@asu.edu
University Technology Director: 
leah lommel
More Info
Source: 
Internal
Priority: 
none
Scope: 

* Requirement gathering
* Identify Seniors that will be tracked and tested for Spring 2009
* Reivew set up for ASU 2 class and schedule as needed
* Review process for assigning checklists
* Review use of myReports for OUE needs

All Milestones and Schedule: 

Requirement Gathering 11/6

Deliverables: 

Set-up for CLA classes
Checklist items
Class lists/Enrollment Reports
QBU processing

Using IPOS for College of Law JD program

Quick View
Summary: 

Purpose:

Review Graduate Plan of Study (IPOS) application on PeopleSoft and assess changes required to adapt this for use with students enrolled through the College of Law in the JD program.

Stage: 
Canceled - No UTO involvement.
People
Sponsor/Champion: 
none
Project Manager: 
No Project Manager
Contact for more information: 
Roger.lurie@asu.edu
University Technology Director: 
leah lommel
More Info
Source: 
none
Priority: 
none
Scope: 

Next Steps:

·Review list of proposed changes below and provide feedback (Please respond no later than by Tuesday, 10/14)

·Prepare a mod specification to be approved and prioritized by UTO; work to be coordinated in conjunction with the Graduate College that is currently working on other retrofits and bug fixes to this mod (Roger)

·Identify resources and timeline (UTO)

General Requirements:

The following are requirements and retrofits identified during the meeting. Please review this list and add to or edit the list.

· Establish Academic Advising requirements in PeopleSoft for the JD

o No previous degree/blanket 30 hour transfer option

o 88 credit hours, of which 64 or more must be graded (non pass/fail courses), and up to 24 hours may be pass/fail courses

o No more than 12 hours of externship

o Accept 400 level courses, in rare cases – requires petition

o No more than 4 credit hours of deficient grade work (grades of 65 – 69) on 600 level or above courses

o Required Professional Responsibility Course

· Modify IPOS and administrative interfaces to work for the LAW career
· Exclude all Law courses from ASU course page with a grade of 64 or below
· Exclude all Law courses from ASU course page with a pass/fail grade of Fail
· Create and code a petition type for 400 level courses added to POS
· Create a customizable set of culminating documents to include the following; modify the admin interface so that list os unique based on academic career, thereby separating the list for GRAD versus LAW.

o Professional Skills Requirement

o Graduation Writing Requirement

o Seminar Writing Requirement

· Calculate deadline as requirement (admit) term + 5 years
· Alter calculation of overall and POS GPA’s to accommodate numeric grading. This may be done automatically by the audit, but will need to be tested.
· Modify approval page to eliminate approval at the academic unit, Graduation Office and Graduate College and replace with one approval by the College of Law. This will require a new milestone type.
· On transfer page, pull all courses from external education page; no free form data entry of transfer courses allowed

New Project Menu Name

The name of "Submit a Project" has been replaced with "New Project" to make it clearer. It was found to be confusing to some.

Evaluate Google Calendaring Connector

Quick View
Summary: 

Install the Google Calendaring connector in the Exchange environment and evaluate its functionality.

Stage: 
On hold
People
Sponsor/Champion: 
Adrian Sannier, Vice President and University Technology Officer
Project Manager: 
No Project Manager
Contact for more information: 
Kari.barlow@asu.edu
Associate VP University Technology: 
Kari Barlow
More Info
Source: 
Internal
Priority: 
none
Scope: 

This project is an evaluation of the google calendaring connector to Exchange. It is not an implementation phase.

The project will require the following staff at a minimum:

(1) Project director to set evaluation criteria and to provide final recommendation.
(2) Exchange support FTE to do installation and troubleshooting of issues
(3) Support staff knowledgeable in the Google infrastructure
(4) Test subjects

Deliverables: 

Recommendation on whether the current delivered version will support the required functionality, and is feasible to implement. If the connector is deemed feasible to implement, the recommendation should also include steps for the "best" way to implement any required changes.

Risk & Threats: 

*The evaluation critieria is open and is not well defined. This might prolong the evaluation period.
*There is no true DEV environment for Exchange and Google.

CRM Person Contact Data Synchronization Phase 1

CRM Person Sync.png
Quick View
Summary: 

Person contact information in CRM does not match HRSA (source system). Discrepancies in person name, email, phone number, and address result in degraded service function of the CRM system. For example, auto email notifications to CRM customers are lost and some ERMS cases get associated with general customer name vs actual customer due to missing email addresses. Additionally, application support efforts to address reported discrepancies continue to increase while user confidence decreases due to data issues.

Addressing the problem will result in increased confidence in the system due to higher levels of data integrity, which will result in fewer cases related to manually changing person data.

Start Date: 
May 6, 2009
Go Live: 
October 20, 2009
End Date: 
October 30, 2009
Current Milestone: 
10/20/2009 - Initial clean-up complete
Stage: 
Critical
People
Sponsor/Champion: 
Adrian Sannier, Vice President and University Technology Officer
Project Manager: 
Katherine Ranes
Contact for more information: 
Katherine.Ranes@asu.edu
Associate VP University Technology: 
Bob Nelson
University Technology Director: 
Katherine Ranes
More Info
Source: 
Internal
Priority: 
Medium
Scope: 

Implement an SQR solution to scan person records and identify person name, email, phone number, and email discrepancies. Correct data is moved to a temporary record from HRSA (source system) and inserted into the CRM record.

Initial clean-up will be a manually controlled and coordinated effort (batch process).

Discrepancies will continue to occur, therefore, a batch process will need reoccur and scheduled on a recurring basis.

This solution will not address and remove the duplicate person records in CRM.

This solution will not address messaging errors between HRSA and CRM.

The solution will address the errors related to person name, email, phone number, and address caused by the broken messaging process.

The solution is an incremental step to decrease recurrent cases and customer requests to fix contact information. The solution will restore user confidence in the system.

Note: The Solution is partially developed.

Required resources: PM/Lead Business Analyst, CRM developer

All Milestones and Schedule: 

Determine scope of cross-reference anomalies and establish baseline data - 06/10/09
Confirm scope of data to be corrected - 06/10/09
Develop, test, and migrate to prod person email sync SQR - 08/08/2009

Develop, test, and migrate to prod person phone number sync SQR - 08/08/2009 - complete
Develop, test, and migrate to prod person address sync SQR - 08/08/2009 - complete
Manually process SQRs for intial data sync - 08/10/2009 - 09/15/2009 - Delayed - Target 11/20/2009
Schedule SQR processing via batch - Delayed - 11/30/2009

Deliverables: 

SQR processes to sychnronize CRM person contact information (person name, email, phone number, address) with HRSA person record (source system).

Initial clean up of person records using developed SQR processes.

A scheduled batch process to run SQRs on a recurring basis.

Risk & Threats: 

Constraints

  • Availability of testing environments
  • Scheduling of HRSA update/fix cycle
  • Quality of user cross-reference table
  • Availability of batch processing windows near start of semester

Installed Product data migration - Fulton School of Engineering

Quick View
Summary: 

Import inventory records into PeopleSoft Installed Product component tables for Fulton School of Engineering.

Start Date: 
January 26, 2009
Go Live: 
May 8, 2009
End Date: 
May 11, 2009
Stage: 
Recently Released - Completed in last 3 months.
People
Sponsor/Champion: 
Adrian Sannier, Vice President and University Technology Officer
Project Manager: 
Frank Montoya
Associate VP University Technology: 
Bob Nelson
University Technology Director: 
Tina Thorstenson
More Info
Source: 
Internal
Priority: 
Medium
Scope: 

Migrate approximately 3,000 asset records from the Remedy system to Peoplesoft Installed Product database tables.

All Milestones and Schedule: 

Define detail project plan, timeline, resources - Complete

Sample CSV file to be used for Development - Complete

Analyze file, verify data is valid for import, and provide mapping data to developer. Complete

Develop spec for data import - 2/20/09 - Complete

Inititate Development of import script - 2/20/09 - Complete

Test (DEV) import script using sample CSV file data - 4/03/09 - Complete

Import data from CSV file to Installed Product Tables - 5/8/09

Customer sign off - 5/08/09

Deliverables: 

Migration of Remedy asset records to PeopleSoft installed product database.

CRM Classroom Reporting

Quick View
Summary: 

Classrooms as entities in CRM for trend reporting

Start Date: 
October 2, 2008
Stage: 
Complete - In operation and supported by UTO.
People
Sponsor/Champion: 
Adrian Sannier, Vice President and University Technology Officer
Project Manager: 
Beth Tetzner
Contact for more information: 
Elizabeth.Tetzner@asu.edu
Associate VP University Technology: 
Sarah Hughes
University Technology Director: 
Tina Thorstenson
More Info
Priority: 
Needs Prioritization
Scope: 

Define classrooms as entities in CRM
Case creation for location instead of customer
Use of 'Anonymous Caller' for quick case creation
Track equipment and facilities data for trend reporting

All Milestones and Schedule: 

Requirements gathering with WPC on 10/7 - COMPLETE
Research integration of AD ASTRA - 10/17 - COMPLETE
Proposal for immediate and long term options - 10/21 - COMPLETE
Obtain consensus for required values of category/type/detail - Pending Lead Input 11/12 - Awaiting - COMPLETE 12/17
Test impact on self service and ERMS by 11/14 - COMPLETE
Follow-up with lead customers on non-development items - 11/03 COMPLETE
Enable Anonymous Caller feature on case - 12/5 Pending CMT - COMPLETE 12/17
Meeting with classroom leads scheduled on 12/17 - COMPLETE
Communication - 12/18 COMPLETE

Deliverables: 

Enable 'Anonymous Caller' on case, eliminates need of classroom as entities
Location defined using Building, Facilities Code and Room number fields on case
Values set for 'Detail' field under classroom category/specialty types for reporting
Quick Codes for swift case population specific to classrooms issues

CLA Online v2

Quick View
Summary: 

The Collegiate Learning Assessment will be administered a second population for Spring 2009. A sample of seniors will be tested in Spring 2009 (February and March). Students will be required to enroll in an ASU prefix class (that will be the test) and complete the exam.

Start Date: 
November 1, 2008
Go Live: 
February 1, 2009
End Date: 
April 15, 2009
Current Milestone: 
Planning meeting - TBS
Stage: 
Canceled - No UTO involvement.
People
Sponsor/Champion: 
Elizabeth D. Capaldi, Executive Vice President and University Provost
Project Manager: 
Bonnie Stoneking
University Technology Director: 
Leah Lommel
More Info
Source: 
none
Priority: 
Needs Prioritization
Scope: 

•Review lessons learned from round 1
•Schedule classes for enrollment
•Create Checklist items for students records
•Add Proctors/Coordinators to CLA test classes so they can see sessions and list of students, can print class roster
•Review myReports used to retrieve registered students information

All Milestones and Schedule: 

Planning meeting - TBS
Schedule classes
Review enrollments
.....

Sun Card Photo available for internal ASU use

Quick View
Summary: 

The Sun Card (Blackboard transactional system) contains the photos taken for the cards.  It has been requested from at least one department to make these photos available for internal application uses.

The first request for this availability is WP Carey internal advisor application.

Start Date: 
October 6, 2008
Go Live: 
October 31, 2008
End Date: 
November 7, 2008
Current Milestone: 
10/15/08-Kick-Off meetin scheduled
Stage: 
On hold
People
Sponsor/Champion: 
Adrian Sannier, Vice President and University Technology Officer
Project Manager: 
Robin Manke-Cassidy
Associate VP University Technology: 
Max Davis-Johnson
University Technology Director: 
Robin Manke-Cassidy
More Info
Source: 
Internal
Priority: 
Lower
Scope: 
  • Provide the Sun Card photos for internal ASU use
  • Make the access to the Sun Card photos easily accessible
  • Automate the update of the photos to keep current within a day
All Milestones and Schedule: 
  • 10-15-08 - Kick off meeting to define remaining scope and goals
  • Design the process
  • Review process with all parties involved
  • Implement and automate the design
  • Documentation (Ops and Care plans)
  • Go Live
  • Post Mortem

NOTE:  A new option for the

Deliverables: 
  • Sun Card Photos accessible to internal ASU applications
Risk & Threats: 
  • Mechanism for approval of applications for data

 

Syndicate content