Technology Steering Group January 31, 2007 SHU Summer 2008 Technology Upgrades Presented to the College of Arts and Science Chairs April 8, 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 – April 2008) –Complete academic history conversion, end of term processing, and awarding of May 2008 degrees –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 – April 2008) (Cont.) –Schedule Banner Finance INB training and access for budget managers that manage multiple orgs and accounts –Upgrade to Banner 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 (May – 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 (May – 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 Banner Project Update (Cont.) The Banner Luminis Portal: –A PORTAL refers to a set of technologies intended to consolidate information from a variety of sources and provide the infrastructure for single sign-on, enabling users to seamlessly move between information sources without having to re-authenticate. –Seton Hall University currently has a very good portal, based on Blackboard’s Community System, that consolidates the Blackboard Learning System, campus , library systems (such as Voyager and EZProxy). –The current Blackboard Community System portal also provides single sign-on to Banner Self Service [BSS].

Technology Steering Group January 31, 2007 Banner Project Update (Cont.) The Banner Luminis Portal (cont.): –The Banner Luminis portal extends these services by providing: Predefined “channels” (technically, “portlets”) that provide direct display of Banner information in the portal. Examples of channels/portlets include: –Academic standing (displays credits obtained and credits in progress, GPA, academic, administrative, or bursar holds, etc.) –Procurement (displays purchase order requisitions waiting for approval) –Admissions (displays admissions applications pending review and approval) –Reports (displays commonly used reports for various functional areas) “Communication Central”, a means of pushing communications to targeted audiences (including department, major, year, etc.) –NOTE: Broadcast is going away!

Technology Steering Group January 31, 2007 Banner Project Update (Cont.) The Banner Luminis Portal (cont.): –The Banner Luminis portal extends these services by providing: Predefined “channels” (technically, “portlets”) that provide direct display of Banner information in the portal. Examples of channels/portlets include: –Academic standing (displays credits obtained and credits in progress, GPA, academic, administrative, or bursar holds, etc.) –Procurement (displays purchase order requisitions waiting for approval) –Admissions (displays admissions applications pending review and approval) –Reports (displays commonly used reports for various functional areas) “Communication Central”, a means of pushing communications to targeted audiences (including department, major, year, etc.) –NOTE: Broadcast is going away!

Technology Steering Group January 31, 2007 Banner Project Update (Cont.) The Banner Luminis Portal (cont.): –The Banner Luminis portal extends these services by providing: Predefined “channels” (technically, “portlets”) that provide direct display of Banner information in the portal. Examples of channels/portlets include: –Academic standing (displays credits obtained and credits in progress, GPA, academic, administrative, or bursar holds, etc.) –Procurement (displays purchase order requisitions waiting for approval) –Admissions (displays admissions applications pending review and approval) –Reports (displays commonly used reports for various functional areas) “Communication Central”, a means of pushing communications to targeted audiences (including department, major, year, etc.) –NOTE: Broadcast is going away!

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 the automation of account generation from Banner, the Banner Document Management System, or Network Access Control 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 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 account after graduation (after graduation their alumni accounts will be funded through ads; note there will NOT be ads in the hosted student )

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 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 account after graduation (after graduation their alumni accounts will be funded through ads; note there will NOT be ads in the hosted student )

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 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 account after graduation (after graduation their alumni accounts will be funded through ads; note there will NOT be ads in the hosted student )

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 Users will be able to access their new MS Exchange account using either the MS Outlook client or using a Web browser (the MS Outlook Web Access, a.k.a. “OWA”). Faculty, staff, and administrators will be able to begin converting to MS Exchange in July. Using the MS Outlook client, users will be able to access BOTH their new MS Exchange account and their old on the Lotus Notes server. Faculty, staff, and administrators will be converted during training sessions where their calendar and address book will be migrated to their MS Exchange account, they will learn how to use the MS Outlook client, and their MS Outlook client will be configured to access their old Lotus Notes .

Technology Steering Group January 31, 2007 Planning Issues (cont.) Users who do not covert before the Christmas Break will be cut over during the break. They will be able to access their using MS OWA, but their calendars and address books will not be converted. Users will receive new account names of the form (NOTE: current users will retain their current address IN ADDITION to their new addess; sent to EITHER address will be routed to their new MS Exchange account.) Students will be converted during the fall 2008 semester. The target time period is just before Thanksgiving recess to ensure any account issues are resolved before finals.

Technology Steering Group January 31, 2007 Other IT Initiatives UITS is upgrading the campus Internet connection, providing redundant connections to the Internet and doubling the capacity of the current connection. UITS is working to eliminate single points of failure in the campus network. Phase I of this effort is underway, including: –Upgrading the data center network to accommodate load balancing, ensuring critical services (Web, Blackboard, Banner, Luminis, LDAP, DNS) have redundant servers with automatic failover. –Upgrading the campus network by adding connection between Corrigan and McNulty Halls and adding a second enterprise class network router in each of Corrigan and McNulty Halls, enabling the campus to recover (including continued Internet access to / from the campus) in the event any one of these building is taken “off line”.

Technology Steering Group January 31, 2007 For More Information: IT News and Announcements Blog Office of the CIO Web Site

Technology Steering Group January 31, 2007 Questions?