Projects On Hold

The goal of this project is to enhance the customer experience with Suncards and Dining at ASU. From My ASU, customers should be able to add money to their Suncard, purchase M&G dollars, purchase meal plans, and see the balances for all Suncard – enabled accounts. This project will implement the following:

JSA Single Sign-on - implement single sign on (ASURITE/password) on the new JSA StudentLink application web page. JSA’s StudentLink application is used to manage Suncard funds (Sun Dollars). (COMPLETE – Launched 10/30)

ARAMARK Single Sign-on – implement single sign on (ASURITE/password) on the ARAMARK Campus Dish web page. Currently, the Campus Dish site requires customers to create and maintain a second login and password. The Campus Dish system is managed by ARAMARK and is used by customers to purchase M&G dollars, purchase meal plans, and view meal plan and M&G balances.

Display Sun Dollars balance on the Housing and Dining popout of My ASU
Display M&G balance on the Housing and Dining popout of My ASU
Display the meal count (for inclusive meal plans) on the Housing and Dining popout of My ASU

** 11.11 UPDATE **
Waiting on vendor documentation.

** 11.18 UPDATE **
Changing stage to 'On Hold' pending documentation from ARAMARK and/or JSA

ASU has a set of projects stemming from audit findings and Provost Initiates that involve building the underlying infrastructure, including department hierachary and supporting business workflows, to support a key set of approval-based business transactions in the HRIS System. The purpose of theis project will be to implement and track the aprroval of Job Actions Requests created through online tools.

This dashboard will replicate retention report including students retained within the university and where they transferred.

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

This application will allow students to apply for, modify and confirm housing and dining preferences online. The application will interact with RMS Housing.

Change Management audit requirements have resulted in the need to enhance the current CRM application/interface. Enhancements to the system will facilitate the capture and retrival of required change management documentation and information.

Implementing the CRM enhancements will enable compliance with change mmanagement requirements.

CRM case #460480

Part two the the BitKOO/Keystone project will be focused on integrating the identity management, authentication and authorization solution, Keystone, into the ASU IT infrastructure. The goal for Keystone deployment is to span further than the walls of UTO. With the mindset of "The Concept of One", the projection for Keystone implemention will be in colleges and departments throughout the university thus providing a standardized means of authentication, authorization, and identity management.

Current interested parties include WP Carey School of Business and The BioDesign Institute. In addition, the streamlining of standard buisness processes will be realized through the use of Keystone's dynamic rule set by Role Based Access Control.  Latency time for processes such as provisioning, and granting acess to accounts and service will be reduced resulting in a noticable reduction in the costs associated with non-productive hours spent waiting to aquire proper role permissions.

An added benefit to BitKOO's Keystone product is the implementation a proof-of-concept (POC) for Single Sign-On (SSO) functionality. This POC will provide users the ability to present their credentials once and gain access to CAS, Citrix, and Outlook Web Access (OWA). With sucessful implementation of the POC, future applications such as Sharepoint will also have the capability of gaining SSO functionality via Keystone.

Currently our ERP System, Advantage, has interfaces to the E-Commerce application, SunRISE, to transfer both budget and purchase order information. Sunrise, powered by SciQuest, has significant value with regard to purchase life tracking and usability. This systems integration with Advantage will be enhanced through this project by adding non-catalog supplier information to SunRISE (SciQuest) and providing more accurate budget information for purchases made through SunRISE.

ASU enterprise administrative systems are Oracle/PeopleSoft systems. The underlying technology, called PeopleTools, is going through a major upgrade this fall from version 8.49 to 8.50. Oracle has been working through the development cycle for the past 2 1/2 years and is ready to release the beta code to a select set of customer for feedback. The project is scheduled to run for approximately 6 weeks beginning Monday August 10th. The goal of the project is to get customer feedback on the new user interface and integration options for PS applications.

The Tempe Facilities Maintenance Department has inquired about purchasing TMA Systems for their Facilities Ticketing and Tracking System. In Version 1.0, Polytechnic and Downtown facilities purchased and installed an enterprise system, which was installed and is accessible through Citrix. At this time this research project is in place to identify project scope for a possible TMA Systems version 2.0, which will include at minimum, Tempe Facilities.

Implement a production-level and well supported instance of Shib so that the University Libraries can use this in conjunction with EZProxy to provide authenticated remote access with single sign-on convenience. This will support the Libraries’ information providers as well as Blackboard and other systems. This is an Internet2 effort, InCommon Library Services Collaboration.

Simple part is a web form for incoming students to register for workshops in July. Difficult part is replicating a function of the University's orientation registration system - where information is pulled from Peoplesoft to populate an advising worksheet for each student attendee. (will probably do this last part somewhat manually culminating in a mail merge).

This project is for Emerging Technology Group. The group will inventory current SOA software and put a plan together for a prototype.

Develop and implement a process to enforce the "ASU Priveledged Account Standard" for all UTO Enterprise Servers and EDNA.

This project is to redesign the way employees are granted access to PeopleSoft. We will be redesigning the current process to request roles.

At present University employees /users submit a request to get access needed for PeopleSoft security roles. The request process is built within the PeopleSoft application. This process includes various approvals and actions to be performed by users, supervisors, data trustees and security analysts at various stages of the request process. These approval steps cause delay for users getting the access they need quickly and in a timely fashion. Users do not necessarily understand the entire process and that also creates some inefficiencies. Training completion or rather incompletion also becomes an issue in approving the access.
There are approximately 55 roles assigned dynamically to employees and students based on certain criteria and also 5 assigned to users programmatically. There are approximately 450 roles available on the access request process.

This project is being proposed to identify an opt-in migration strategy for faculty and staff who would like to use Gmail for ASU rather than Exchange.

During this project, the University Technology Office will be creating a phased migration plan to move as many UTO staff to Gmail for ASU as possible. Some features will restrict who can transition from MS Exchange over to Gmail for ASU now, including public folder use, distribution list management, and inbox delegate access.

Integrate support resource data currently maintained outside CRM in spreadsheets. Project will improve customer service, reduce complexity for Tier One support providers, and provide Tier Two+ with relief from misrouted cases.

Add emergency notifications to the template so the university population is notified through the web should an emergency happen on campus. Add lightweight authentication to the template to enable students to signin and signout from any area of the ASU web.

The account activation process needs to be streamlined to make it easier for someone to activate their account without compromising on security. The purpose of this project is to do design and implement a more streamlined, user-friendly method.

The purpose of this project is to provide an escalated response based on a new direction "just to notify".  In this project, a website will be designed that requires webauth and provides an auditing mechanism to capture offenders login and selection, IP and MAC address.

The following list the process that will occur:

1. User attempts to connect to a P2P download site

2. Audible Magic intercepts connection

3. User is prompted with a drupal site containing legal jargon on
proper use of the ASU network.  Contents of page as as follows:

        - button"accept"  

4.
When user accepts the legal terms, their credentials and current
information(MAC Address, NATED IP, Original IP, date and
time of attempted login) are captured by WebAuth. The attempted
offending information (aka movie they were trying to dl) is captured by
AudibleMagic.  All information is stored in copysense database.

5. User is redirected from site that he/she is attempting to access to www.asu.edu/myasu

6. if Subpoena is served, Help Desk will utilize Illegal Download Application (to be developed)

Project on hold per Laura Ploughe - not a business priority at this time. 

University Business Services (UBS) and University Technology Office (UTO) are enhancing the automation of data between the Blackboard Transaction server and many other servers for enterprise data and transaction systems processing in 2008. The goal is to incorporate implementation of the new Building Blocks Manager which receives PeopleSoft bio-demo data which will then be automatically fed to the Sun Card.

The scope of this project covers only the feed to Sun Card and is limited to Courtesy Affiliate data.

Additional projects will be setup for feeds to ISSAC, Pharos and other future systems as needed.

This project will be upgrading the MICROS point-of-sale software to version 3.2 SP2.

Improve and standardize Authorization, Authentication and Accountability of access to network hardware and other services. Additionally, provide the ability to restrict or grant access to Network Hardware and services based on roles and responsibilities.

PCI hardware, network and software implementation for MICROS point-of-sale application - using wireless devices.

Deploy the JA-SIG Central Authentication Service (CAS) for web single signon, integrated with ASUWebAuth in a high-available clustered environment.

For many ASU staff and faculty, there are procedures that must be done infrequently that have important consequences. Currently, when an end user has questions, they either must search the HRIS website, Help center or create a case through CRM; these options do not provide context-sensitive information about their specific question. As a result, we see end users are “guessing” how to complete vaious transactions. These guesses result in bad data in the system with the unintended consequences of terminating benefits, incorrect pay amounts and many others with serious implications for the employee and students, requiring rework for the business process owners.

The need for UPK documentation is immediate as the problems created by “guessing” is perpetuating problems which could be resolved with available support for end users. Adding the UPK will help more people help them selves, reducing errors and calls to the help desk.

The purpose of this project is to request allocation of web designer/Drupal support resources to update or rebuild our existing Drupal portal.

The Clicker Support web page, at http://clickers.asu.edu, is a Drupal portal providing ASU Faculty and Students with resources necessary to successfully use Student Response Systems. All article content is in Help Center, but the site provides a user interface to information, along with forms to fill out when requesting help or training. Approximately 150 faculty and over 10,000 students may use this site. The site was implemented and created by a student and staff member, both of whom are now gone. The site was hacked at some point and was patched back together for us. We now need to make changes to or rebuild the site to include updated information. The Admin usernames and passwords we have do not work, and we do not have the skills or personnel resources to make these changes ourselves. We are willing to learn to use the Drupal interface but need help.

This project will relocate 8 racks of servers from Fulton Center and Old Main to ISTB1 data center.

Modifications to asu.edu/map include adding dynamically updated views of the campus buses with GPS tracking, increased search functionality and filtration, custom icon functionality, and overall usability improvements.

Creating a centralized catalog for all non-credit offerings. This includes all courses/classes/workshops offered in any method of delivery (online and face to face instruction). Also included will be offerings listed on ASU in the Community.

myCourse Watch (like Perfect Schedule), allows students to sign up for alerts via Email or SMS when seats become available in previously full classes.

ASU Web Devils Student newspaper would like to improve their web-site functionality and add more features. The site is moved to UTO Web Hosting at the end of 2007 and the new site will be implemented in Drupal Content Management System. The project involves training the Student Media staff in Drupal, helping them to come up with new design and layouts, and supporting the new system's feature development.

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

This initiative originated from the Provost's office. It aims to create a standardized rollup structures for reporting and financial purposes across all departments in Arizona State University. It also seeks to create dashboards that reflect the rollup structures in colleges. The project team consists of representatives from multiple departments across Arizona State University. The group meets regularly every Monday afternoon to define the scope and desired requirements. The project timeline will be determined once these two items are completed.

Business continutity software for Security Group

Allow students in the College of Nursing and Healthcare Innovation to register for/complete non-credit courses.

The Oracle Connections Manager project aims to provide a communications routing solution for ASU departmental applications that require connections to the remote EPM and OASIS oracle databases hosted by CMS, but cannot directly communicate with them. Upon successful testing this solution will replace the currently less efficient and more cumbersome Oracle database links solution.

The database links solution requires a local Oracle database to act as an intermediate server or hop between the departmental applications and the remote CMS-hosted databases. To run SQL scripts and access data on the remote databases, the departmental applications have to first connect and forward their SQL statements to the local database. The local database in turn parses the SQL statements, connects to the remote databases using the database links, gets the needed data from the remote tables, executes the SQL statements locally, and returns the results back to the applications.

Our experience has shown that the features of the Oracle database links make this routing solution restrictive and inefficient (performance-wise) for complicated queries without the creation of views or procedures in the remote and local databases. This in turn can make the management and support of database links, security, and the local and remote views and procedures complicated and time-consuming for staff members at ASU and for CMSC.

In order to hopefully resolve the aforementioned performance issues and simplify support, we are testing the use of Oracle Connection Manager as a replacement for database links. The definition, architecture and features of the Oracle Connection Manager can be found in Oracle documentation. Briefly, it is a router (consisting of three processes instead of a full database server for the case of database links) running on a local LINUX host. It relays the SQL statements and database communication between the departmental applications and the remote databases without any local database processing. The SQL statements are parsed and executed entirely by the remote database.

In addition, Oracle Connection Manager has other attractive features such as better network scalability and secure network access control than the database link solution for our purposes. It can multiplex or funnel multiple database connections or sessions across a single network connection, thus reducing network traffic between the applications and the remote databases. It can also act as a firewall proxy by limiting database access to specific hosts or IPs.

For the initial set up, the clients and applications only need to change their Oracle connection configuration to point to the Connection Manager in a UTO local server. They do not need local database accounts. The Connection Manager will then transparently route the connections and database communication to the EPM databases. However, access to the Oracle Connection Manager from departmental applications or local database clients and tools is subject to the local firewall rules in force for the development and production environment at UTO.

Currently, we receive MCCD transcripts via EDI. These EDi tscpts initially go through the Hershey process where some data translation is done prior to loading to PeopleSoft. This project would eliminate that dependency and allow direct loading to PeopleSoft. This would also allow expansion of receiving EDI transcripts from other post secondary institutions.