Strategic and Tactical Plan

January 2008 – December 2009

Executive Summary

The Center for Information Technology Services (CITS) has developed a tactical and strategic plan for the next twenty-four months based on input from many campus groups and individuals, including from the school and department representatives on the UMB IT Steering Committee.  What follows is a summary of major projects and action items that will be undertaken to satisfy the identified IT needs of the campus community. 

High Availability/High Reliability of Campus Infrastructure and Systems

The highest identified priority was to undertake the necessary software and infrastructure upgrades to create highly available and reliable services and strengthen the campus Cyberinfrastructure.  To that end, CITS is planning to do the following:

• Re-architect the entire infrastructure for anti-spam, anti-virus, and e-mail delivery to the campus to provide faster mail processing and greater redundancy.  
• Place another network switch at the gateway between the Internet and the campus network to allow fail-over in the event the first one is disabled for any reason.
• Implement a redundant network core in a second campus location. 
• Facilitate the creation of replicated databases for critical systems so that online learning, testing, registration, and web services will be available even if a major hardware or software problem occurs.
• Work with email managers across campus to replace the currently supported email system with one that will meet the needs of the entire campus with faster processing, better management and security functions, and greatly enhanced features.
• Replace the student e-mail system with a more contemporary product. 
• In January 2008, introduce the Accellion product, which is a means of transferring very large files across the campus or world without affecting e-mail quotas.
• Pursue the development of a common facility that would offer computational resources, back-up systems, storage resources, statistical software, research and educational applications that is connected to the high-speed campus network and Internet. 

Enterprise Systems

Enterprise administrative systems have standardized the way the campus does business, eliminated much of the “paper chasing”, and provided integrated processes and reporting.  CITS will continue to build on these positive outcomes by enhancing many systems in the near future. 

CITS will incorporate Central Billing and Working Fund systems into eUMB Financials to take advantage of its built-in security, workflow, standardized data, centralized support, and accessibility.  At the same time the financial system will be enhanced to provide more access, better reporting, and faster processing.  A state-of-the-art system for handling and reporting Non-Resident Alien payroll and tax processing will be developed with Administration and Finance.

The COEUS system, which provides the ability to generate grant proposals, circulate them online for campus approvals and certifications, and ultimately submit the proposals electronically to sponsoring agencies, will be integrated with eUMB Financials.  Awards will be seamlessly loaded into the financial system to take advantage of grant management, effort reporting, and integrated reporting features already developed. 

The Student Information Management System (SIMS) has recently been upgraded to comply with the campus’ new FERPA policy.  A major new version of SIMS will be tested and implemented during the period of this plan. 

• Pilots will be completed for Degree Audit and Prospect/Recruitment modules. 
• A new comprehensive reporting plan will be developed. 
• The ability for students to pay Admissions Application Fees on line will be completed for all schools wishing to implement this feature.

The eUMB Human Resources Management System, including Payroll (HRMS), will undergo a dramatic upgrade in the near future.  Planning for this major change will begin in the spring of 2008.  Individuals’ affiliations and privacy will be managed in a new and better way.  Many new functions will be considered in the planning of this implementation.  These capabilities could include electronic time sheets, individualized leave reporting, and dramatically more hours of access to the system on a daily basis.

During the next twenty-four months, CITS will work with schools and departments to assist with the implementation and use of Document Imaging and Management system.  In addition to providing centralized storage for a potentially massive number of images, CITS will provide technical assessments of available products and assistance in incorporating digitized images and forms into enterprise systems.

Identity Management/Campus Directory Services

Identity Management is the process used to verify that an online user is who he or she purports to be.  This is usually done by requiring entry of a username and password.  Because many of UMB’s systems were built independently, they employ different identity management sources to authenticate users.  This has led to a requirement for multiple user names and passwords for individuals who wish to access more than one system.  To mitigate this problem CITS has built a common Enterprise Directory that includes all potential users of UMB systems.   

• The Enterprise Directory will become the source for authenticating users of CITS maintained systems.
• An immediate goal will be to allow students to use a single ID for access to SURFS, Blackboard, and student e-mail. 
• The Enterprise Directory will be linked to the campus Active Directory.  This connection of directories will allow for the passing of demographic information between the two directories and facilitate the process for account provisioning and decommissioning in CITS and in schools and departments.
• A product called Shibboleth will be used to further enhance the common ID experience by providing single sign-on capabilities as well as the capability to “translate” identities from systems that cannot use the Enterprise Directory directly, further reducing the need for multiple IDs. 
• An Identity Management Web site will be built, which will provide all the information necessary for departmental and school application managers to access and use the Enterprise Directory for authentication to local systems. 
• A new service is available that allows users to select an “Alias” for logging in to enterprise systems.  An Alias is a username chosen by an individual that the Enterprise Directory will recognize as a legitimate ID.  The objective for using this Alias is to reduce the number of usernames that a person must maintain.

Disaster Recovery

Preparation for recovery in the event of a disaster that would affect systems operations is a critical ongoing task.  Consequently, many of the steps taken to provide highly available systems are a part of the plans for disaster recovery.  These include creating replicated databases and installing duplicate equipment for failover.  Action plans have also been devised to further insulate the campus from loss of critical operations, including the following. 

• Off-site tape storage will be done twice-weekly at the Iron Mountain Corporation secured facility. 
• Online systems backup and data storage will be created outside of the HS/HSL.  A redundant failover campus location, as well as an off-campus site for equipment and online back-ups of critical systems and data will be pursued.    
• Technology and procedures in the IT Disaster Recovery Plan will be tested. 

Security

Protecting systems from hacking, viruses, and spam attacks requires constant vigilance and adjustments. Re-architecting equipment and systems at the gateway between the Internet and the campus network, upgrading virus and spam management processes, and expanding the use of an enterprise directory will enhance campus IT security.  In addition, a priority during the next twenty-four months will be working with schools and department IT personnel to expand wireless capabilities and access, as well as using the Enterprise Directory as the source for authenticating users to make wireless networks secure.

Customer Service

CITS has always considered customer service the highest priority.  All of the actions alluded to above are in response to customer needs that have been well articulated through the IT Steering Committee and through input collected from other groups and individuals.  Among the many initiatives to be launched to enhance services to customers are three major action items: 

• The hours of the campus ASC Help Desk will be expanded to twenty-four hours a day, seven days a week. 
• CITS will continue to expand communications with the campus, through CITS BITS, e-mail distribution lists, Portal Alerts, and the recently implemented text alert system.  
• In January of 2008, a Campus Master Calendar will be used to record upcoming events and activities.

All of these initiatives provide a means of constant interaction between CITS and the campus community to ensure responsiveness to real needs.

What follows is a detailed listing of activities to meet the prioritized needs of the campus, with approximate timeframes for completion.   

Information Technology Goals, Objectives, Action Items and

Anticipated Completion Dates

Infrastructure (Server, Storage, Database, Network, Voice, Video, Data)

Current Objectives:

• To strengthen the UMB Cyberinfrastructure, particularly in those areas that require an investment in resources.  Cyberinfrastructure includes computational resources; high-speed networking; voice, video, and data infrastructure, and the use of digital technologies; data management and storage; software licenses; research, educational and business applications; support resources; and, secure access to data exchange. 
• To continue building a converged voice, video, data infrastructure while deploying Voice over IP (VoIP). 

Action Items and Anticipated Completion Dates:

• Discuss and identify Cyberinfrastructure needs across campus and pursue opportunities for strengthening the UMB CyberInfrastructure.  (2008) 
• As part of the needs analysis, determine initial interest and demand for using a common high-performance computing center and systems for supporting UMB research and education projects. (2008)
• Based on need and demand, construct a common campus-wide computing facility for use by faculty for research and education projects which offers computational resources, back-up systems, storage resources, software, support personnel, and which is connected to the high-speed campus network and Internet. (2009)
• Participate on national Cyberinfrastructure workgroups and connect with higher education and federal agency sponsored computing grids, so that faculty have access to and can use available Cyberinfrastructure resources outside of the UMB network. (2008 and Ongoing)  
• Implement an electronic file transfer solution (Accellion product) that allows large files to be sent and received via email messages.  (January 2008) 
• Implement new hardware & software used for anti-spam, anti-virus, and message delivery.
• • Re-architect systems (Fall 2007)
  • Acquire new technology solutions (Fall/Winter 2007)
  • Pilot test, evaluate, plan implementation (Winter 2007-2008)
  • Transition to new services (Spring 2008-Summer 2008)
• Active Directory/eDirectory linkage and information passing between the two directories
• • Perform analysis (Winter 2007-2008)
  • Develop implementation plan, including the detailed technology tasks (Winter/Spring 2008)
  • Implement (Spring-Winter 2008)
• Upgrade enterprise directory servers and software  (Spring 2008)                             
• Upgrade campus enterprise forest to Active Directory 2008 (Fall 2008)
• Undertake planning and implementation of Microsoft Exchange 2007   
• • Undertake planning (Spring/Summer 2008)
  • Exchange 2007 implementation (Fall 2008-Spring 2009)   
• Develop process and plan for replacing the student email system    
• • Undertake research and explore options (Winter 2007/2008)
  • Develop an implementation plan to move the services (review technology, processes, and create a timeline of activities) (Spring/Summer 2008)
  • Implementation (Fall 2008-Spring 2009)
  • Launch (Summer 2009)   
• Retire the existing Continuing Education Server and integrate into the Enterprise Blackboard server. (Fall 2008)
• Upgrade Howard Hall to a redundant core infrastructure (Early 2008)
• Investigate with Facilities Management and propose a solution for a redundant network core in a second campus location (Spring-Summer 2008)
• Implement a redundant network core in a second campus location  (2009)
• To continue to build and maintain a converged voice, video and data infrastructure and deploy IP telephony (VoIP)
• • Continue to work with Administration and Finance to build the financial models for deployment of a contemporary communications infrastructure and VoIP in new and existing campus buildings (Ongoing)
  • Articulate these financial models to the campus community (Ongoing)
  • Consult and work with Facilities Management and school and department IT personnel, as well as with vendor personnel to implement and support this new infrastructure and VoIP in new buildings as well as when opportunities arise in existing buildings (renovations, department moves, facilities and technology upgrades)
  • • Expand VoIP implementations in the Dental, Social Work, and Law Schools (Ongoing)
    • Homeland Security in 300 Russell Street (December 2007)
    • Bio-Park Building 2 (Spring-Summer 2008)
    • Administration Building (September 2008)
    • Campus Center (April 2009)
    • Pharmacy Hall (June 2011)
    • HSF 3 (2015-2020)
• Investigate a campus feed for Plasma/LCD TV’s on campus (fosters campus unity, helps in emergency/disaster management). (2008-2009)
• Investigate a remote TV studio for campus (similar to http://ucsdnews.ucsd.edu/thisweek/2004/oct/10_18_experts.asp). (2008-2009)
• Investigate the possibility of strengthening and expanding cellular coverage in campus buildings.  (2008)
• Document every building’s copper/fiber connections as well as switch configurations for the campus. (Ongoing)
• Implement new DNS services for the campus (Winter/Spring 2008)
• Provide storage and associated technical support for a campus document imaging/management system. (TBD)
• Continue to explore the current and future needs for network infrastructure to support the use of the new technologies utilized by the schools. (Ongoing)
• Work on the vendor contracts to allow for more buying power, ease of support, and standardization of core elements. (Ongoing)
• Complete the selection and implementation of a load testing tool for performance testing. (January 2008)
• Conduct Storage Area Network (SAN) capacity planning to accommodate current and near-term production system growth.  (Jan-June, 2008)
• Install and configure Oracle Data Guard for stand-by environments.  The applications targeted for stand-by environments are Blackboard, SIMS and CMS (Site Executive).  This will first be tested in a development environment and later moved to production. (Jan-June 2008)
• Install and configure Oracle for the new Blackboard development and production database servers. (Jan-June, 2008)
• Perform application and/or database upgrades, hotfixes and patches as necessary. (On-going, based on application requirements)
• Revisit Oracle backup strategy (e.g. RMAN, scripts) based on requirements and improved Oracle features.  (On-going)
• Investigate current Oracle features to address regulatory requirements regarding databases. (On-going)

Enterprise Systems

Current Objectives:

• To continue implementing, upgrading and maintaining state-of-the-art information systems.
• To expand access and availability of enterprise systems.
• To provide support for enterprise systems.
• To monitor the data integrity of UMB mission-critical systems databases.

Action Items and Anticipated Completion Dates:

• Complete Web Admissions Credit Card rollout. (Feb., 2008)
• Expand availability of eUMB enterprises systems by 3 hours/day. (Feb., 2008)
• Continue investigating additional contemporary methods and technologies, and if feasible, proceeding to further expand the availability of the system (Ongoing)
• Complete enhancements to the EHS Training application. (March 2008)
• Implement Non-Resident Alien solution and create new interface to the State Central Payroll Bureau. (Spring 2008)
• Complete Archibus implementation (May 2008)
• Complete critical tools and database upgrades for Financials, RAVEN, and Portal. (May 2008)
• Create new faculty training and support opportunities for Blackboard and QuestionMark. (Spring 2008)
• Complete incorporation of Central Billing into eUMB. (Summer 2008)
• Work with Administration and Finance to implement a new solution to replace the existing Check Tracking System for student refund management. (TBD)
• Support Blackboard hardware upgrades and stabilization. (July 2008)
• Complete the COEUS implementation through conversion, proposal development, Institute Proposal, Award Modules, Reporting, and interfaces. (October 2008)
• Complete implementation of Asset Management Module. (Winter 2007)
• Complete pilots for CAPP (Degree Audit) and Prospect Recruiting. (Winter, 2008/2009)
• Replace Working Fund system with eUMB functions. (Early 2009)
• Support Campus implementation of Document Imaging/Management Solutions. (TBD)
• Begin planning for HRMS and Portal upgrades to new versions with new functional capabilities. (Start Spring 2008: at least 18 month project.)

Campus Directory Services, Identity Management 

• To enhance a common ID, single sign-on infrastructure and authentication solution that meets enterprise-wide needs.
• To grow the use of the common ID by linking additional applications to the enterprise directory.
• To educate the campus regarding the use of an Alias as a personal ID to access systems and applications that are linked to the directory.
• To continue to maintain and update the enterprise directory that includes all faculty, students and affiliates of our user community; and, an identity management system which provides improved security, better and easier systems administration, and enhanced services to users in our enterprise.
• To build a campus-wide identity management, account provisioning and de-provisioning solution that uses the common enterprise directory and allows the use of a common ID (Alias) for authenticating to the UMB network and campus applications.    

Action Items and Anticipated Completion Dates:

• Create a campus-wide group to discuss Directory Services, Identity Management, and related technologies (e.g. Shibboleth).
• • Provide regular information exchange between CITS and campus schools in order to leverage these technologies (Winter 2007-2008 and Ongoing)
• Work with Applications staff to reduce the number of userids, utilizing the enterprise directory for authentication
• • Work with the SIMS/Banner team to configure Banner & SURFS to authenticate using the myUMBid and password
  • • Perform analysis (Winter 2007-2008)
    • Configure Banner and SURFS (Spring 2008)
    • Implement (Summer/Fall 2008)
  • Work with the Blackboard team to configure Blackboard to authenticate using the myUMBid and password
  • • Perform analysis (Winter 2007-2008)
    • Bring up Shibboleth services (Winter/Spring 2008)
    • Configure Blackboard (Summer 2008)
    • Implement (Summer/Fall 2008)
  • Work with the Student Email team to analyze & configure student email system to authenticate using the myUMBid and password
  • • Undertake research and explore options (Winter 2007/2008)
    • Begin technology review process, implementation planning (Spring 2008)
    • Implement and launch (Summer-Fall 2008)
• Creation/Launch of ID Management Web site (Spring 2008)
• Active Directory-Directory Services Linkage information passing
• • Perform analysis (Winter 2007-2008)
  • Campus Enterprise Active Directory Forest
  • • Test reading/writing attributes and pass demographic information to/from the Enterprise Directory to/from the campus enterprise Active Directory forest (Spring 2008)
    • Implement (Spring-Winter 2008)
    • • Begin writing scripts to populate Global Address List  (Summer 2008)
      •  Determine requirements for account provisioning/decommissioning (Winter 2008)
  • Work with entities not in the campus Enterprise Forest (ongoing)
• “Day Zero” account creation & access to UMB systems
• • Perform Analysis and develop timeline (Spring 2008)
  • Develop initial functionality and application list to be included
  • • Re-write existing STUB record system using new toolset (JAVA) (Fall  2008)
    • Roll out initial functionality (Winter/Spring 2009)
  • Develop follow on functionality and application list
  • • User self registration (Fall 2009)
    • • Users will have the capability to self register on the day they arrive on campus establishing their presence in the Enterprise Directory
  • Continue to develop follow-on functionality (2009, Ongoing)
  • • Replace current “affiliate” system
    • Implement levels of assurance and interfaces to existing systems

Disaster Recovery

Current Objective:

• To take the necessary measures to ensure that the University can respond to any crisis, which may temporarily affect critical services such as the Internet, network, web, email, voice, data, video communications, and any necessary University function.

Action Items and Anticipated Completion Dates:

• Off-site tape storage will be done twice-weekly at the Iron Mountain Corporation secured facility. (Winter 2007-2008) 
• • Test the restoration of the backup media from off-site storage (Early 2008)
• Online systems backup and data storage will be created outside of the HS/HSL.  A redundant failover campus location, as well as an off-campus site for equipment and online back-ups of critical systems and data will be pursued. (2008)    
• Install a second network switch for redundancy at the core location in Howard Hall (Early 2008)
• Investigate with Facilities Management and propose a solution for a redundant network core in a second campus location (Spring-Summer 2008)
• Implement a redundant network core in a second campus location (2009)
• Investigate a campus feed for Plasma/LCD TV’s on campus (fosters campus unity, helps in emergency/disaster management). (2008-2009)
• Continue to promote the use of the UMB text messaging solution for emergency communications and disaster management. (Ongoing)
• D/R Maintenance and Training
• • Create procedures for testing D/R Plan to address D/R Plan scenarios
  • • Loss of Backup Storage (Spring 2008)
    • Loss of Voice Services
    • • Document the testing of temporarily rerouting voice and data services from any campus building, based on the SSW implementation. (Spring 2008)
• Backup Computer Facilities:
• • Test the restoration of a Campus Active Directory schema via VMWare in a lab environment. (Summer 2008)
  • Relocate development hardware for critical application to a remote site (e.g. Howard Hall) (Summer 2008)
  • Create stand-by databases for critical applications. (Summer 2008)
  • Loss of Campus Active Directory Forest (Summer 2008)
• Test technology and procedures in the disaster recovery plan (Summer/Fall 2008)
• Complete the documentation on D/R testing and any new procedures (Winter 2008/2009)

Technology Security

Current Objectives:

Action Items and Anticipated Completion Dates:

• Implement new hardware & software to strengthen the current infrastructure for anti-spam, anti-virus, and message delivery prior to the implementation and migration to a new architecture and new technologies for anti-spam, anti-virus, and message delivery. (Winter 2007-2008)
• Implement a campus web-based VPN server (Spring/Summer 2008)
• Reconfigure central services into protected VLAN’s and DMZ’s (Summer 2008)
• Enhance wireless security while expanding campus wireless infrastructure (Summer 2008)
• Extend quarterly scans to include schools/departments (Fall 2008)

Service Delivery

Current Objectives:

• To meet the service and support needs of the campus and school community by continuing to develop the operations in the Assistance and Service Center; advance ASC staff knowledge and the technology available to them for processing and resolving service requests; to coordinate and collaborate with other help desks and service operations in the schools, UPI, and hospital; and, to proactively inform the campus community about UMB technology as well as the status of specific requests and problems.
• To provide technical assistance for enterprise-wide systems and technologies and to expeditiously respond to the service calls from campus constituencies pertaining to these technologies.
• To provide training for enterprise systems.
• To facilitate a software acquisition program for students, faculty and staff.
• To provide timely, accurate, up-to-date information for students, faculty, staff, and administrators on the CITS computing/technology website and via electronic communications.
• To create and foster open channels of communication to better inform the campus community and to aid in the evaluation of the effectiveness of services and support.
• To treat UMB students, faculty, staff, colleagues, and co-workers as treasured customers, and provide excellent service to the UMB community.

Action Items and Anticipated Completion Dates:

• Expand Help Desk service hours to 24 hours a day and 7 days a week. (Early 2008)
• Provide regular communications (CITS Bits, email, text alerts) (Ongoing)  
• Upgrade the T-Metrics Help Desk call management software (Spring 2008)
• Replace the T-Metrics hardware with a more powerful server (Spring 2008)
• Implement a “knowledgebase” to replace Frequently Asked Questions (FAQs) (Summer 2008)
• Streamline the process for providing email and Blackboard IDs for new students (August, 2008)
• Investigate new help desk software as a replacement for Remedy (2008).    
• Further structure/develop the software licensing office to provide greater volume purchasing power for the campus commonly used software products. (Ongoing)
• Continue to coordinate and offer training in the use of enterprise systems. (Ongoing)
• • Create a model for campus wide training in all essential enterprise systems.
  • Develop an online infrastructure to support and deliver the training.                                                                         

Technology for Teaching and Learning

Current Objectives:

• To implement and upgrade enterprise course management, web and media software in order to support faculty use of contemporary instructional technologies. 
• To facilitate the delivery of education to students anytime and anywhere by providing web systems that are available 24 hours a day, 7.days a week. 
• To ensure that the technologies available to faculty (the Internet, campus network, enterprise software, etc.) work reliably.
• To support faculty instructional and research initiatives that send and receive voice, video, and data across the campus network and the Internet.
• To create an enterprise support structure for faculty such that teaching with technology is an exciting, easy transition and not a burden fraught with difficulties.

Action Items and Anticipated Completion Dates:

• Leverage the enterprise directory so that students and faculty have a single login to multiple applications.
• Develop a structured online faculty development environment that would include available resources and services for faculty.
• • Consult with colleagues at other institutions that have created online faculty development environments.
  • Identify a list of relevant UMB and school specific resources and services.
  • Design a template for this environment. 
  • Complete and distribute this online faculty development environment to faculty.
• Develop a standard training program that could be used by either the enterprise training group or individual schools.  Regardless of the platform, it would allow the schools to share both training content and user data.  The program would do the following:
• • Deliver text, image, Flash, etc. training.
  • Develop campus-wide multimedia training, including the use of audio/video technologies.
  • Create training and support program for faculty in using Blackboard, QuestionMark, and other eLearning software. (Spring 2008)
• Installation and configuration of new Blackboard architecture (Summer 2008)
• Install and configure Oracle for the new Blackboard development and production database servers. (Summer 2008)
• Create an AV support team, that would include support for Mediasite, Crestron, and other products used in classrooms.
• • Leverage school and department Audio Visual needs and create a campus-wide AV team.  The AV team would discuss needs, acquire and share knowledge, and coordinate the purchase, implementation and support of AV technologies across the schools.
  • Creation of a support structure for basic or common end-user issues while using Mediasite for lecture viewing.
  • Creation of a group devoted to the continued support of the campus enterprise Mediasite installation directing use, advising on maintenance/support, sharing best practices, and providing advisement for other MediaSite related administrative issues.
  • Leverage the support offered by Crestron Corp. to acquire additional knowledge and enhance the software and hardware capabilities of the Crestron device.
• Reduce the number of Blackboard accounts to one per person.
• Continue efforts to introduce iTunes U in the schools, HS/HSL and departments.
• Coordinate and facilitate the development of a “program guide” for initiating distance learning programs. 
• Develop an understanding of the “Domain Security” model provided as a part of the Blackboard Community System.  Articulate guidelines for the use of this functionality by schools and departments on campus.
• Develop the Blackboard Branding model to allow each school the ability to tailor it to their student body.
• Implement Guest Access in Blackboard to allow enrollment of faculty in order to facilitate curriculum development and review.
• Continue planning of Symposium with continued support and representation from the Education Technology Committee (ETC).
• Continue to use contemporary technologies to support the delivery of content to remote locations.
• Continue to introduce and coordinate technological innovations that may have application across all schools.

IT Architecture for Interconnected Wireless Computing

Current Objective:

• To expand the campus wireless network and use the enterprise directory and a common ID for access to the Internet and school and department sub-networks. 

Action Items and Anticipated Completion Dates:

• Enhance wireless security while expanding campus wireless infrastructure (Summer 2008)
• • Implement a wireless environment such that a user will be able to authenticate to the wireless network as faculty/staff, student, or guest.  Once that authentication is complete, users will be able to move to other areas of the campus and use a common ID for authenticating and using a wireless network. 
  • The campus wireless will be activated in the Schools of Social Work, Law, Pharmacy, Dental, A&F in the Saratoga Garage, the new Administration building, new Campus Center and in the HS/HSL.   Additional departments and schools will be brought online as opportunities develop.
  • Authentication will be in conjunction with the campus enterprise directory.  Currently there are three wireless VLANs (Faculty/Staff, Student and Guest).  Once the directory services connection has been established, there will be consolidation to one wireless VLAN.   Based on the credentials of an individual at authentication, users will be routed to the appropriate network, i.e., the faculty/staff, student, or guest VLAN.

Web Development, Environments

Current Objective:

• To serve as an intuitive and useful tool for gaining access to information resources and for raising the visibility of UMB programs, services, and activities.

Action Items and Anticipated Completion Dates:

• Complete Diet/Nutrition Study Application (Dec. 31, 2007)
• Expand infrastructure and complete CMS hardware/software separation (Dec., 2007)
• Work with System Alliance to ensure the stability and reliability of the SiteExecutive content management system. (Ongoing)
• Complete Comprehensive Campus Calendar (January 2008)
• Train school/department representatives in the use of this master calendar. (Winter 2007)
• Complete ORD Technology Application (Phase 2) (Jan. 31, 2008)
• Complete WAP online directory lookup (January 2008)
• Complete Nursing Global Health Website. (Winter 2007)
• Complete HR “Careers in Baltimore Healthcare” website. (Jan., 2008)
• Continue to work with schools/units in redesigning websites and designing and building web applications. (Ongoing)