Technology Steering Group January 31, 2007 Academic Affairs Technology Steering Group February 13, 2008.
Published byModified over 6 years ago
Presentation on theme: "Technology Steering Group January 31, 2007 Academic Affairs Technology Steering Group February 13, 2008."— Presentation transcript:
Technology Steering Group January 31, 2007 Academic Affairs Technology Steering Group February 13, 2008
Technology Steering Group January 31, 2007 Banner Project Update Milestones To Date June 2003SHU strategic plan calls for replacement of the Plus2000 administrative system June 2004Administrative System Selection Task Team convened March 2005Administrative System Selection Task Team recommends Banner admin system (top rated HE admin system by Gartner, Inc.) June 2005Contacts for Banner implementation approved by University’s Board of Regents Sept 2005Banner Project kickoff; implementation teams convened August 2006Banner Admissions becomes first Banner module to go “live”
Technology Steering Group January 31, 2007 Banner Project Update Milestones To Date Feb 2007Banner Financial Aid module goes “live” March 2007Banner Registration module goes “live” July 2007Banner Finance and Banner Student A/R modules go “live” Oct 2007Banner data warehousing and reporting system (the Banner Operational Data Store [ODS]) installed Dec 2007Banner HR/Payroll goes “live” Jan 2008First payroll run from Banner / last production job (W-2’s) run from Plus2000
Technology Steering Group January 31, 2007 Banner Project Update (Cont.) Short term objectives for Banner (Feb – March 2008) –Complete academic history conversion and end of term processing –Complete implementation of Financial Aid updates and enhancements to FA to streamline upcoming FA processing –Complete implementation of CORE One Step to improve online processing of admissions applications and housing deposits –Complete configuration of Banner Operational Data Store and deploy additional reports to meet immediate operational needs
Technology Steering Group January 31, 2007 Banner Project Update (Cont.) Short term objectives for Banner (Feb – March 2008) (Cont.) –Schedule Banner Finance INB training and access for budget managers that manage multiple orgs and accounts –Upgrade to Banner 7.5.1 to support document imaging and identity management projects –Gather requirements for desired Banner enhancements, prioritize requests, develop project plans and assign resources to approved enhancements
Technology Steering Group January 31, 2007 Banner Project Update (Cont.) Intermediate Range Banner Objectives (April – Dec 2008) –Support implementation team’s “Phase II” projects to use Banner to improve service and streamline processes –Expand the use of the Banner data warehousing features for reporting, including “ad hoc” reporting for end users –Implement the Banner Luminis portal to enable easier access to Banner information and services for students, faculty, and administrators; integrate Banner services with SHU Web site to provide authoritative information to external constituencies
Technology Steering Group January 31, 2007 Banner Project Update (Cont.) Intermediate Range Banner Objectives (April – Dec 2008) (Cont.) –Implement Banner document imaging and Banner workflow modules to support teams’ projects to improve service and streamline processes –Implement Banner identity management modules to enable account management and integration of other systems with Banner –Begin implementing high priority Banner enhancements
Technology Steering Group January 31, 2007 The IT Challenge The core of any IT infrastructure is the directory service, a list of all users authorized to access campus systems and which systems and data each user is able to access. The University’s current directory service is based on a combination of Lotus Notes / Lotus Domino and Novell While Lotus Notes and Novell were considered state-of-the-art as recently as five years ago, these systems have been superseded by other directory services.
Technology Steering Group January 31, 2007 The IT Challenge The current Lotus Notes and Novell directory services do not easily support integration with Banner / Oracle and do not support other strategic technology initiatives, such as Network Access Controll via Cisco Clean Access. The Lotus Notes / Novell directory infrastructure does not easily support the IT security and control recommendations of the University’s external auditors and compliance with the current regulatory environment
Technology Steering Group January 31, 2007 The Proposed Solution Replace the current Lotus Notes / Novell directory infrastructure with one based on Microsoft Active Directory (AD) and the Oracle Identity Management (OIM) Suite Replace the current Lotus Notes / Lotus Domino email and calendaring system with one based on Microsoft Outlook / Microsoft Exchange –Microsoft Exchange system for faculty, staff, and administrators will be hosted on campus –Microsoft Exchange system for students will be hosted by Microsoft. Students will keep their hosted email account after graduation (after graduation their alumni accounts will be funded through ads; note there will NOT be ads in the hosted student email)
Technology Steering Group January 31, 2007 The Proposed Solution (Cont.) Other components of the proposed solution: –The Blackboard Content System will be users’ primary online repository for digital documents. Users’ allocations on the Bb Content System have been increased to 1GB for students and 2GB for faculty, staff, and admins. Faculty, staff and admin allocations will be increased on request in 1GB increments to a max of 5GB on online storage. This will replace users’ personal Novell directories (their “‘Z:’ drive”). –For departmental shared Novell drives (e.g., ‘G:’, ‘H:’, etc., drives) IT will implement a Windows server environment to support shared folders. –IT will implement Cisco Clean Access to ensure that all users of the campus network are appropriately authenticated (no anonymous logins) and that users’ laptops are up to date with operating system patches, have up to date antivirus / anti-malware software, etc.
Technology Steering Group January 31, 2007 Planning Issues IT is completing upgrade of Lotus Notes system to enable users to access their email and calendar using MS Outlook 2003. For anyone using the MS Outlook client, the server change from Lotus Domino to MS Exchange will be relatively simple. One strategy would be to being migrating the community to MS Outlook 2003 as their mail client for their Lotus Notes email and calandar; in this scenario we would switch the Lotus Notes email servers to “read only” in August and direct all incoming email to the MS Exchange servers. All users will have a new format for their email address, for example, of the form: firstname.lastname@example.org (current users would be able to use their shortname as an alias for their new email address). Users who have archived email on their desktop / laptop computer can continue to read that email using the Lotus Notes client.
Technology Steering Group January 31, 2007 Proposed MS Exchange / Banner Luminis Timeline March 2008Pilot Banner Luminis Portal and MS Exchange. “Z:” drives will be decommissioned for most users. April 2008Begin MS Outlook installation and training for University community. Users can begin accessing their Lotus Notes email and calendar via MS Outlook. August 2008Lotus Domino servers switched to “Read Only”. All incoming email will be directed to MS Exchange servers. Banner Luminis portal will replace the current Bb Community System portal for all users.
Technology Steering Group January 31, 2007 Questions?