ETS/UTO Server on Demand Service

info highway.jpg
Quick View
Summary: 

The purpose of this project is to evaluate the benefits of "growing" the ETS server on demand service to an enterprise level of service at the ISTB1 Data Center.

Currently the ETS Server on Demand (SoD) service provides virtual servers to entities across the university. This includes both the virtual hardware as well as storage resources. The primary drive behind this push is for academic entities to get out of the server business and centralize server resources under a UTO/ETS management partnership.

Current service pricing scheme is as follows:

  • Virtual server (managed or unmanaged) - $1800 for 5-years
  • Virtual server + 1TB of storage - $2700 for 5 years

 

Tasks

  • Bring server-on-demand service up to university level
  • Evaluate current SoD service infrastructure
  • Determine network infrastructure
  • Determine storage needs
  • Build up the service to meet demand
  • Refine business model, integrate with UTO services.

 

Start Date: 
August 1, 2008
Go Live: 
January 13, 2009
End Date: 
December 31, 2008
Current Milestone: 
MS to be met by January 16, 2009 Decision to initiate new project for migration of ETS/SOD environment to ISTB1 Data Center.
Stage: 
Complete - In operation and supported by UTO.
People
Sponsor/Champion: 
Adrian Sannier, Vice President and University Technology Officer
Project Manager: 
Duane Woerman
Contact for more information: 
Duane.Woerman@asu.edu
Associate VP University Technology: 
Bob Nelson
University Technology Director: 
Terry Hinton
More Info
Source: 
Internal
Priority: 
Medium
Scope: 

 The goal of the initial assessment is to establish how the current environment is set up and what resources it is using. 

The initial assessment of the current SoD environment will encompass:

  • Networking
  • Storage
  • VMware infrastructure
  • Operations infrastructure (power, etc.)

One additional piece of information will need to be established before moving to the next phase (Ideal Configuration) – That is projected demand / usage.

This assessment will only deal with those components actually touching the current SoD environment, some areas (most notably networking) may choose to have a larger assessment scope.

All Milestones and Schedule: 

The initial assessment of the current SoD environment will encompass the areas listed below.

Individuals involved are noted w/ a lead designated for each area. The lead will be responsible for reporting the information back to group. The goal of the initial assessment is to establish how the current environment is set up and what resources it is using.

o Networking – Duane (lead), Bob Belisle, Ed

o Storage – Kirt (lead), Jack, Mehran Yahya

o VMware infrastructure – Marc (lead), Scott A.

o Operations infrastructure (power, etc.) – Jim Z. (lead)

The tentative completion deadline for this initial assessment phase is end of October. · One additional piece of information will need to be established before moving to phase 2 (Ideal Configuration) – That is projected demand / usage. Denise will be the lead on this w/ assistance from Marc and Kirt. (Milestone to be determined)

Deliverables: 

The main focus of the assessment is how the network is laid out around the server on demand environment.

This would include:

* 1. Current configuration - What's currently in place? Networking hardware, etc. Some areas to look at specifically would be how are these systems tied in to the HPC research network.

* 2. Ideal configuration - What is the ideal setup for this system to provide stability, manageability, and adequate throughput for the systems especially w/ an eye toward scaling in the future.

* 3. Reaching the ideal configuration - What can we do to get as close as possible to the ideal system within the constraints of time and money? The team currently targets to generate a few alternatives w/ associated impact and price tags. For example: What needs to be done to upgrade the infrastructure in place to accommodate the SoD VM systems? Is there a better (more cost efficient) place to put the systems? Also, currently installed "emergency" networking hardware should be looked at w/ an eye toward permanent manageable solutions.

Contract Tracking Database

Quick View
Summary: 

This project would create/enhance the database system that has been started and provide a mechanism to issue reports to administration about expiration, budget requirements, history, images of contract (electronic file for universal access), etc. This tool would help in budget planning, planning for system admin resources, and version upgrades.

Go Live: 
December 31, 2008
Current Milestone: 
As temporary database has been started, but there needs to be maintenance and additional developement on the system so it will be functional and administered. 8/19/08
Stage: 
Canceled - No UTO involvement.
People
Sponsor/Champion: 
Adrian Sannier, Vice President and University Technology Officer
Project Manager: 
No Project Manager
Contact for more information: 
Connie.roberts@asu.edu
More Info
Source: 
Internal
Priority: 
Needs Prioritization
Scope: 

The University has more than 200 contracts that are technology related. Many of these agreements are managed and administered by UTO. Currenty there is a huge dependence on individuals within the department to renew, negotiate and track contracts from one year to the next as there is no central tracking system.

This project would create/enhance the database system that has been started and provide a mechanism to issue reports to administration about expiration, budget requirements, history, images of contract (electronic file for universal access), etc. This tool would help in budget planning, planning for system admin resources, and version upgrades.

Additional benefits:
• assuring no contract lapses
• identifying overlapping agreements to negotiate better deals
• tracking MOU’s, ISA’s, etc. for cost recovery and achieving service levels

Deliverables: 

Reporting for renewals, cost recovery and consolidation

Access to contracts in an electronic format

Risk & Threats: 

Not having all the information for the database resulting in inacurate reporting
Creating a reliance on tool that may not be accurate initially

Benefits Enhancements: New Hire Enrollment Effective Dates

Quick View
Summary: 

To comply with ADOA, coverage effective 1st pay period following enrollment, provided enrollment occurs within 31 days. This project will require significant changes to the current interface with ADOA to start benefit deductions in the same pay period as the employee elects coverage.
CRM ticket 307107

Start Date: 
August 25, 2008
Go Live: 
October 31, 2008
End Date: 
October 31, 2008
Current Milestone: 
10/24/2008 - Migrated to Production
Stage: 
Complete - In operation and supported by UTO.
People
Sponsor/Champion: 
Carol Campbell, Executive Vice President and Chief Financial Officer
Project Manager: 
Clara Adams
Associate VP University Technology: 
Max Davis-Johnson
University Technology Director: 
Tina Thorstenson
More Info
Source: 
Executive
Priority: 
Medium
Scope: 

Need to amend the date rules in Ben Admin for specific event classes.
When an employee has a specific action running through Ben Admin (become benefits eligible, is a new hire, sustains a job related action/reason, or a qualified life event) and enrollment is completed, his/her benefits coverage should begin the first of the pay period following their enrollment date. The system will need to be programmed to take the event as the coverage elect date yet still make sure it is within 31days of HIRE or QLE.

Enhanced Access/Manager Self Service Improvements - Notice of Appointments (NOAs)

Quick View
Summary: 

Notice of Appointment letters go out to all non-classified staff each fall semester. This project will setup the process as an XMLP process instead of flat file exports.

Click here to view the case in PeopleSoft: CRM Case #307104

Start Date: 
July 15, 2008
Go Live: 
December 15, 2008
End Date: 
December 15, 2008
Current Milestone: 
1/12/2008 - Roll out NOAs to employees
Stage: 
Complete - In operation and supported by UTO.
People
Sponsor/Champion: 
Morgan Olsen, Executive Vice President and Chief Financial Officer
Project Manager: 
Kristen Micetic
Contact for more information: 
kristen.micetic@asu.edu
Associate VP University Technology: 
Max Davis-Johnson
University Technology Director: 
Tina Thorstenson
More Info
Source: 
Internal
Priority: 
High
Scope: 

Need to develop a self-service page for distributing Notice of Appointments to ASU faculty, academic professionals and service professionals. NOAs are a legislative requirement and act as the contract between the university and the employee. Previous to PeopleSoft, Prd Support produced the letters in hard copy formats for distribution by the departments/colleges. With PeopleSoft, HRIS ran a query and created a mail merge template to use. Both processes were time consuming and produced a lot of paperwork.  The Provost Office, HRIS and PRD Support would like to have a paperless way to create and track the NOA approvals.

 

All Milestones and Schedule: 

5/29/2008 - Specifications have been written

8/12/2008 - Developer to review specs and begin Technical specs

10/1/2008 - In Development

Revised: 12/12/2008 - Signature Approval from President's Office

Revised: 12/18/2008 - Roll out MSS piece

Revised: 12/29/2008 - Roll out to all University through ESS

Enhanced Access/Manager Self Service Improvements - eHire

eHire.gif
Quick View
Summary: 

Need to create a better way for hiring managers to consistently enter hiring data on their Job Offers. This will create a place for the managers to get the data to Data Mgmt for entering the new hire or additional job data into PeopleSoft for both Staff and non-staff workers, eliminating the need for the paper HPR and reducing the different processes for entering data from 2 to 1.

Start Date: 
July 1, 2008
Go Live: 
December 15, 2008
End Date: 
January 1, 2009
Current Milestone: 
University launch on 12/23
Stage: 
Complete - In operation and supported by UTO.
People
Sponsor/Champion: 
Carol Campbell, Executive Vice President and Chief Financial Officer
Project Manager: 
Kristen Micetic
Contact for more information: 
Kristen.Micetic@asu.edu
Associate VP University Technology: 
Max Davis-Johnson
University Technology Director: 
Tina Thorstenson
More Info
Source: 
Executive
Priority: 
High
Scope: 

This project will enable the enhanced functionality of Employee Self Service and Manager Self Service. By improving the Business Processes, the downstream effect will be a more streamlined way of dealing with a transactional based environment.

All Milestones and Schedule: 

7/1/2008 - Meet with Business Technology Services (BTS), Roger Lurie to discuss possibilities

7/15/2008 - Fit/Gap Analysis to be drafted.

7/22/2008 - Mapping and documentation over the next two weeks. BTS is changing from ASP to Java.

8/5/2008 - BTS is reviewing code.

8/12/2008 - Waiting on Oracle db and application ID

8/29/2008 - ARB Review

10/10/08 - Rewrite application from ASP to Java

10/13/08 - Internal review, testing, feedback

10/20/08 - Make development modifications

10/23/08 - Create component Interface

10/25/08 - Test component interface

10/29/08 - Make modifications to component interface

10/31/08 - Migrate component interface to PRD

11/3/08 - Unit Testing

Revised: Soft Launch - 12/08/08

Revised: Go Live - 12/15/2008

Deliverables: 

Web application for ASU managers to hire new employees.

ASU PeopleSoft Tools Upgrade and Support with UTO Labs - August to October

tools_upgrade.jpg
Quick View
Summary: 

In order to align ASU's PeopleSoft application with ORACLE and CMSC support, ASU's PeopleSoft Tools application is slated to be updated from version 8.48 to 8.49 starting in August of 2008 and will complete on or around October 10/11. PeopleSoft Tools upgrades differ from Bundles and Fixes in that a Tools Upgrade updates the core application functionality where as Bundles and Fixes updates individual PeopleSoft Module code and page functionality.  Additionally, PeopleSoft Tools upgrades do not generally touch Module code, but rather the toolset that allows the code to work. PeopleTools environments that will be effected during this Tools Upgrade will be the following: 1) HRSA, 2) CRM, 3) EPM, & 4) EP.

Start Date: 
August 18, 2008
Go Live: 
October 12, 2008
End Date: 
October 13, 2008
Current Milestone: 
PeopleSoft Tools 8.49 Successfully applied and resolutions resolved.
Stage: 
Complete - In operation and supported by UTO.
People
Sponsor/Champion: 
Adrian Sannier, Vice President and University Technology Officer
Project Manager: 
Daniel McDonald
Contact for more information: 
daniel.mcdonald@asu.edu
Associate VP University Technology: 
Bob Nelson
University Technology Director: 
Katherine Ranes
More Info
Source: 
Internal
Priority: 
High
Scope: 
  1. Install PeopleTools Version 8.49 to IDP/STG Environments
  2. Verify and compare IDP Environments
  3. Install PeopleTools Version 8.49 to TST Environments
  4. Verify TST Environments
  5. Apply PeopleTools Version 8.49 to PRD Environments
  6. Verify PRD Environments
  7. Refresh DEV, STG Environments.
Deliverables: 

1) Installation of HRSA, CRM, EPM, EP PeopleTools Upgrade 8.49.

2) Application of ALL ASU Retrofits, to include Security and LDAP Single Sign-on

3) Validation by both UTO and Business user environments that the PeopleSoft Application is working as expected.

Risk & Threats: 

Lack of Problem resolution of PeopleTools Installation, Retrofits, and/or testing issues in the provided time frame will push back Deliverable Date of 10/11/2008.

ASU Web Developer Support System

Quick View
Summary: 

UTO offers a collection of tools to university developers to help them create web sites and applications that are properly branded, well functioning and relevant to the ASU web as a whole. However, although we're now concentrating on a more select group of tools, we still don't have the resources necessary to fully support them. In addition, as more and more departments and colleges redesign their sites, the number of "new" developers with little knowledge of web design and development continues to grow. Often, those people turn to UTO for support and training.

We could make better use of our limited resources by developing self-sustaining support systems (listed below)

Start Date: 
August 18, 2008
Stage: 
On hold
People
Sponsor/Champion: 
Adrian Sannier, Vice President and University Technology Officer
Project Manager: 
Kelli Thornton
Associate VP University Technology: 
Max Davis-Johnson
More Info
Source: 
Internal
Priority: 
Lower
Scope: 

1. Web Community Redesign
Estimated resources needed: 20-30 hours development time

The redesign will concentrate on enhancing and highlighting the forums to encourage user participation and peer-to-peer support. In additon, out-dated articles and all other features would be removed. Fostering peer support in the forums will help decrease requests for staff support.

2. Training Videos
Estimated resources needed: 40 hours

Creating brief training videos on a variety of web development tasks will supply site administrators and developers with instant access to web-based training and information. In addition, many free video tutorials are available on the web and can be gathered and organized in a central location. With such a collection of videos, staff will receive fewer support requests, and the requests they do get will be easier to answer when they can direct customers to a training video.

3. Peer-led training courses
Estimated resources needed: 80 hours

Developing a set of courses for those topics that demand classroom-like instruction, as well as a plan to deliver them to larger audiences, will more effectively train larger groups of participants on a scheduled basis. When participants become better trained, they require less support from UTO and are able to support other new developers, in turn.

4. 3-day training workshop with Lullabot
Estimated resources needed: $18,000 (recoverable)

Lullabot has proposed $18,000 for a 3-day Drupal workshop for up to 25 people. This cost would be covered by a participant fee. We are in the process of gauging the development community's interest, and will renegotiate the fee and number of attendees with Lullabot when we have a firmer estimate of the partcipants we can expect.

5. Patterns Library
Estimated resources needed: 80 hours

Web development patterns libraries, such as the Yahoo User Interface Library, are immensely important for encouraging consistent design and coding. Creating an ASU pattern library will help to set a standard, as well as provide easy-to-use, tested "plug-n-play" elements and features for developers and designers.

Dashboard - CRM V.2.0

Picture 4.png
Quick View
Summary: 

The CRM Dashboard v.2 project seeks to implement additions and enhancements to the existing CRM dashboard. Please review the scope below for more details.

Click here to view the case in PeopleSoft: CRM Case #306411

Current Milestone: 
Communication to UTO Call Center Agents - COMPLETED
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: 
etetzner@asu.edu
Associate VP University Technology: 
John Rome
More Info
Source: 
Internal
Priority: 
Lower
Scope: 


  • Integrate AVP/SLA into CRM dashboard
  • Add reporting rollup structure by provider group in CRM
  • Dashboard summary and reports format enhancements
  • Add new search/filtering criteria
  • Standardize filters for all pages

All Milestones and Schedule: 


  • Scope Revised on 9/22 - Pending AVP Approval - APPROVED 10/14
  • Filter Standards Defined - 9/22 COMPLETE
  • Provider Group reporting rollup page - migrated to CMDEV - 10/22 COMPLETE
  • Test PG Reporting Rollup Page in CMDEV - 10/22 COMPLETE
  • Review/provide modified case results list SQL to Dashboard Team - COMPLETE 10/27
  • Migrate Provider Group Rollup to CMTST - COMPLETE 10/28
  • Re-migration necessary after testing - COMPLETE 11//07
  • User Acceptance Testing in CMTST - COMPLETE 11/6
  • User Sign-off for PG Rollup to PRD - COMPLETE 11/14
  • PG Rollup migration to PRD, Data Migration - COMPLETE 11/18
  • SQL to Dashboard Team 'Cases by Department' - COMPLETE 11/19
  • Data Verification in PRD - COMPLETE 11/21
  • Department Rollup by College to CMTST - COMPLETE 12/01
  • Department Rollup by College to CMPRD - 12/10 COMPLETE
  • CRM Support Dashboard enhancements migration to PRD - 12/15 COMPLETE
  • Communication to UTO Call Center Agents - 12/15 COMPLETE

Deliverables: 


  • Improved functionality on CRM Support Summary
  • UTO AVP/SLA reports integrated into the dashboard
  • Reporting rollup structure by provider group stored in CRM
  • Standarized search/filtering criteria on dashboard
  • Standarized format for open cases results lists
  • Columns included for assignment tracking
  • Enhance existing dashboard reports
  • Communication
  • Training

CRM - Field Service Support Integration

Quick View
Summary: 


The objective of this project is to improve Netcom customer experience to generate a Netcom CRM Service Order via a CRM Support Case. The initial research of the project involves:


  • Identify and analyze implications of disabling Service Request modifications.
  • Identify and document information required when creating a Service Order.
  • Analyze and propose solution options.


The following options are used for consideration:



  • Self service template to create a SO. The technical resource needs to find out if PeopleSoft provides a self service template/functionality for Service Orders.
  • Configure UTO CRM Support self service template to create case that supports generation of Service Order
  • Determine if CRM Support Self Service template can be configured to capture required on a Service Order.
  • Utilize existing UTO CRM Support self service to generate case. Train and modify business process for Help Desk resources (PerceptIS) to create Service Orders from case.

Start Date: 
September 10, 2008
Go Live: 
November 6, 2008
End Date: 
November 6, 2008
Current Milestone: 
Remove Service Request modification for CRM application - 11/6/08
Stage: 
Complete - In operation and supported by UTO.
People
Sponsor/Champion: 
Adrian Sannier, Vice President and University Technology Officer
Project Manager: 
Frank Montoya
Associate VP University Technology: 
Bob Nelson
University Technology Director: 
Katherine Ranes
More Info
Source: 
Internal
Priority: 
Medium
Scope: 


  • Remove Service Request modification and implement configuration requirements.
  • The team will follow CRM development team design, development, testing, and implementation processes.
  • Review, redefine, and document business processes to create Service Order from a CRM Support Case.
  • Training
  • Communication
Transition to Application Support Team

All Milestones and Schedule: 

- Redirect link on My ASU page from SR to Netcom page. Complete

- Add Category/Type required values and define PG default. Complete

- Publish communication on Netcom page. Complete

- Research and apply configuration options. Complete

- Update Business Unit ASU01 description from Datacom to Netcom in the DEV, TST, IDP, and PROD environment. Test and update. Complete

- Communicate business process/change to UTONCCOORD PG. Complete

- Redirect CSR link Netcom page to UTO create case self-service page. Complete

- Develop and publish training documentation - Complete

- Migrate project to prod to remove SR modification from CRM FS application - 11/6/08 Complete

Deliverables: 

Remove SR Modification from CRM production environment 11/3/08

Enable creation of Service Order from Support Case 11/3/08

Enhanced Access/Manager Self Service Improvements - Departmental Transfers

Quick View
Start Date: 
August 30, 2008
Current Milestone: 
Gathering Requirements
Stage: 
Canceled - No UTO involvement.
People
Sponsor/Champion: 
Carol Campbell, Executive Vice President and Chief Financial Officer
Project Manager: 
Clara Adams
More Info
Source: 
Internal
Priority: 
Medium
Scope: 

This project will enable the enhanced functionality of Employee Self Service and Manager Self Service. By improving the Business Processes, the downstream effect will be a more streamlined way of dealing with a transactional based environment.

Syndicate content