Creating a Robust Infrastructure

Core Team Lead was

Primary Objectives:

  • Identity infrastructure for the future
  • Connections needed
  • Capacity (storage, bandwidth, etc.)
  • What will be required in terms of personnel and finances to maintain and refresh infrastructure?
  • Leveraging the “Cloud”

Summary of Session:

During the IT infrastructure session, participants considered future infrastructure needs and how subsequent distribution and implementation of these needs impacts personnel and resource needs. The meeting included participants from administrative and academic departments, faculty, distributed IT and OIT.

During this session, participants took part in two exercises. The first exercise had participants define the purpose and role of IT infrastructure while highlighting key components unique to UNLV as a whole. In the second exercise, participants were teamed up to consider the main components of IT infrastructure. Each team shared its findings.

Many components of IT infrastructure were discussed, including hardware, software, network, facilities, refresh, etc., that are needed to support and maintain the campus technology environment. In conclusion of the session, it was agreed that the most important components of infrastructure for UNLV future technology planning will be connectivity, resources and trust.

Key outcomes identified to inform the IT Master Plan:

  • Connectivity
    • Includes traditional, wireless, cellular, ISPs, encryption, authentication, and protocols
    • Seeking ways for students, faculty and staff to connect anything, anytime, anywhere
    • Need methods of quantifying, translating, and communicating needs
    • Plan for the thoughtful phase out of outdated technology (e.g., Cable TV)
  • Resources
    • Includes both internal and external, data center and enterprise services, staffing shifts to SMEs who manage programs and develop solutions, and a catalog of services by function ability
    • Seeking ways to be more collaborative, integrative and concentrated on program development as opposed to task-focused
    • Consider reducing local infrastructure and overlapping functions (e.g. web masters)
    • Consider options for focusing IT staff resources on the community they serve and leverage hosted services to strengthen effectiveness.
  • Trust
    • Includes security, reliability, planning, compliance, capacity, planning and program information office
    • Seeking ways to implement ID management, enforce governance policies, simplify and improve customer experience, and increase staff while avoiding duplication of efforts
    • Need satellite systems for ID management