- » Account Request
- » Alumni Account Request
- » Calendar Request
- » Access Request
- » Disk Quota Increase
- » Exiting Employee
- » Request Forms and Processes
(ITS Staff only)
As part of the ITS Planned Abandonment initiatives, we will conduct a thorough evaluation of the data and processes remaining in Banner, our legacy student information system. On conclusion of the evaluation, we will develop and implement a plan to migrate that data to an alternate solution so that Banner can be retired and we no longer need to maintain and support it.
8/18/15: It has been decided that the effort required to convert the SPAIDEN Banner form to Apex would be greater than the benefit. PeopleSoft is the system of record, and any data that needs to be retrieved from the Banner database which is not already served by an Apex-Banner Forms application can be requested via a Help Desk ticket assigned to a programmer. The Banner Forms server will be retired during the 9/20/15 ITS maintenance window; all Banner users have been notified that any Banner data not available through Apex forms may be requested via the Help Desk.
6/24/15: Ken is targeting completion of the SPAIDEN Banner form in Apex before the 7/14/15 retirement of the Banner server. If the form is not completed in time, or if the decision is made to defer changing the name-change process outside of PeopleSoft HR and Campus Solutions until the rollout of Fischer Phase 2, manual processes can substitute in the short term.
5/28/15: Research has started into recreating the SPAIDEN Banner form in Apex; Ken anticipates completing within the next 60 days. Plans by the SysAdmin group to retire the Banner server before Fischer go-live are being reviewed.
4/30/15: Ken and Travis have determined that these final forms are not essential, so the request to recreate them in Apex has been withdrawn; other paths exist to access this data if and when it is needed. Ken has proposed recreating the SPAIDEN Banner form, frequently used by the Help Desk for email address updates, in Apex, although it would be retired or changed to read-only once Fischer Phase 2 is live. Ken anticipates delivering this new form in May.
4/1/15: Ken Thrift will begin working with Travis Brunner to design the layout of the last three Banner forms needed by Student Records, with design anticipated to be complete by the end of April. The project end dates have been revised based on estimated Fischer completion dates, with time allowance for the completion of the final Banner retirement activities.
1/28/15: The end date for this project has been updated to align with the Fischer end date. Translation of the last three Banner forms to Apex is planned for March/April 2015.
10/29/14: While the project remains on hold pending the Fischer implementation, resources (Ken Thrift) have been identified to develop Apex applications for the three additional Banner forms recently discovered by the Registrar's office. That work is not expected to start until December/January; the project end date will be updated once the Fischer end date is confirmed and an estimated completion date for these last Banner forms is set.
9/23/14: While the project remains on hold pending the Fischer implementation, the Registrar's office has identified three additional Banner forms that require Apex applications to permit continued access to the database information. We are now identifying programming resources to complete these final forms. An audit of all access to Banner over the last six months is complete; the only discovered access is limited to the Registrar's office (for this recently identified data) and the Technology Help Desk (for the processes that will continue until Fischer replaces them). We hae also reconfirmed that retiring Banner will not impact On Demand Data requests that have not yet transitioned to the campus data warehouse. Based on the available information, we anticipate being able to close this project by December 2014.
7/15/14: Since the remaining open items on this project are dependent on the Fischer implementation, this project will be placed on hold until that time.
6/23/14: CEEE is now successfully using a new Apex front-end form to access Banner data. While they are accessing Banner data on the Gamma server, they are no longer using the Banner application to do so, a situation which may change further when a final decision is made regarding a new CRM solution. The remaining open items are dependent on the Fischer implementation.
5/28/14: Development has begun on the Apex front-end forms to replace the Banner application forms for CEEE's use in viewing SSN and credit card information as well as historic data stored in Banner tables. If the college chooses to migrate to a new CRM solution, this will remain view-only for historic information viewing, as the data will be secured in the new CRM solution. If CEEE defers moving to a new CRM, a secured Apex data entry page will be constructed to tie to the database housing the Banner table data. The remaining open items are dependent on the Fischer implementation.
4/16/14: Apex security has been completed. Research continues on a few remaining uses of Banner data, primarily related to functionality that will be migrated to the Fischer Identity Management System and alternate solutions for CEEE to store data currently being secured in Banner tables, which may require an extension of the time to closure for this project.
3/25/14: Testing has been successfully completed on Student Records and Student Financial Services Apex applications, and security is now being created, tied to corresponding PeopleSoft permissions. Research continues on a few remaining uses of Banner data, primarily related to functionality to be migrated to the Fischer Identity Management System and alternate solutions for CEEE to store data currently being secured in Banner tables, which may require that we extend the time to closure of this project.
2/28/14: Apex applications have been created to permit continued access to certain database information needed by Student Records and Student Financial Services; these are currently being tested. Research continues on a few remaining uses of Banner data but we remain on schedule to retire the Banner application in July, with data contents available via the Gamma server and Apex applications.
1/22/14: From an initial list of 13 actionable areas, five have been identified for retirement in July 2014 when the Fischer Identity Management system is implemented, five have been identified as requiring an alternative data storage resource (for example, Apex application or Data Warehouse), two require further research, and one has been closed.
11/22/13: An initial planning meeting has been held to enable us to begin compiling the inventory of remaining Banner forms and data that need to be migrated elsewhere in order to retire the Banner application. The team is meeting with identified business areas and will regroup in December to review the results of their research and to identify specific tasks and timelines.
10/22/13: This project has been approved by the President and VPs as an ITS priority for 2013-14.