NETWORK PLANNING TASK FORCE FY06 Network Strategic Discussions

1
NETWORK PLANNING TASK FORCE FY06 Network
Strategic Discussions
11/7/05
2
Meeting Schedule FY 2006

• Summer Planning Sessions (2)
• July 18
• August 01
• Fall Focus Groups (2)
• September 19
• Fall Meetings (6)
• October 03 Security Priority Setting
• October 17 Network Priority Setting
• October 31 Strategic Security Discussions
• November 07 Network Strategic Discussions
• November 21-Final Strategic Discussions/Summary
  of needed decisions
• December 5 Consensus/Prioritization/Rate
  Setting

3
Agenda

• Wireless
• VoIP
• High speed connectivity to desktops/ servers

4
Wireless (Current Status)

• 400 ISC and School/Center access points.
• Approximately 20 of campus has wireless
  connectivity.
• Awaiting final approval for complete College
  House and Sansom Place wireless installations
  (500 APs).
• Discussions currently underway for Wireless in 21
  Greek houses. (42 APs)
• Many large-scale installations pending New
  McNeil, Life Sciences, Bennett Hall.
• Any other big installations pending?
• By Fall 2006, Penn could have about 50 wireless
  connectivity.

5
Wireless Strategic Discussion

• What are we trying to accomplish?
• 100 of campus with wireless?
• ISC managing all infrastructure centrally?
• If all pending installations are approved and
  completed Penn, will be about 50 wireless.
• What other strategies may we employ to get a
  campus-wide deployment?

6
Wireless (Supporting Proposals) FY 07

• ISC to capitalize access point hardware, using a
  3-year depreciation schedule.
• Deploy next generation of wireless technology.
• Costs for hardware depreciation,
  hardware/software support, staff, etc. will be
  about 27/month per AP.
• It is currently 27/month without hardware
  depreciation.
• How is the subsidy working for public wireless IP
  addresses?
• Should we subsidize all wireless IP addresses?

7
New Wireless Support Costs (Monthly Fee Per
Access Point)

• Cost Breakdown
• Hardware depreciation 13
• Hardware/software maintenance 5
• Staff costs per AP 9
• TOTAL 27
• Monthly charges in FY04 and 05 were 30 and 27
  respectively, without hardware capitalization.

8
Voice (Current Status)

• 25,000 Verizon Centrex users including on-campus
  students.
• Most work is outsourced
• MACs slow and costly
• Local calls costly
• LD service with Paetec.
• Over 12,000 voicemail users
• Several different, legacy ACDs
• Negotiated low-cost phone line and usage
  contracts.
• Developed programs with three cellular phone
  service providers for members of the University
  community.

9
Voice Plans (FY 06)

• Developing flexible, cost-effective services
  based on VoIP.
• Performing RD into
• Unified Messaging to access and manage voice mail
  through either a telephone or an electronic mail
  program.
• Software-based telephones (Softphones).
• Telephone directory services via interactive
  voice response (IVR)
• Telephone set portability, using VoIP handsets
  that can autoconfigure anywhere on any IP
  network.
• Products that support agent call handling and
  distribution for call centers (Automatic Call
  Distribution - ACD).

10
Voice Plans (FY 07)

• Explore integration of Instant Messaging and
  Video Conferencing (Integrated Communications) in
  user-specified ways (Presence).
• Explore dual mode cellular/802.11 devices that
  work as conventional cell phones as well as
  on-campus wireless devices.
• Perform RD into location-based services,
  supporting user location for emergency services
  as well as customized user services based on a
  user's specific location.

11
Voice Communications (Why change?)

• Drivers
• Penns voice infrastructure, especially
  building-to-building copper cables are 25-100
  years old, very costly to maintain and can take a
  long time to replace, thus making basic phone
  service not as reliable.
• There is very little voice infrastructure
  redundancy.
• Legacy voice mail and ACD systems are costly to
  operate and lack enhanced functionality.
• Verizon MACs are inflexible and costly.
• Potentially recover lost revenue from students
• 1.5M in last 5 years
• Increase operational efficiencies
• Need to manage only one infrastructure.
• Architecture to enable competition between
  service providers.
• Via IP technology- same connection
• LEC and LD services
• Position for voice-enabled applications
  Pennintouch/SFS.

12
VoIP (Global Advantages)

• Vendor independence.
• Operational economies of scale.
• Modern communications services lead to a more
  efficient work environment.
• Increase/remain competitive as a modern Hi-Tech
  institution.

13
Voice Communications (Business Process Changes)

• We are considering no new building feeds with
  copper cables.
• We need to replace legacy KSUs (Eagles, Extrom).
• We are encouraging voice customers to make only
  one technology leap forward
• Delay upgrades to a legacy voice system
• Upgrade to VoIP
• We will be replacing our ACD and voice mail
  systems to IP-based ones.

14
Challenges / Risks

• Infrastructure
• Move forward fast enough to avoid costly
  building-to-building telephone cable upgrades.
• Customer communication/training
• We will effect all 25,000 voice customers.
• Staffing
• New positions are a challenge. We are moving
  towards insourcing and will need more staff.
• Financial
• While we are reasonably confident that expenses
  will not increase, it may be a challenge to
  maintain the 1M voice cross-subsidy to the
  network.
• Technology Leader
• First large scale implementation of open-source
  solution.
• Dependency on Verizon
• Need their cooperation for the smoothest
  transition to a modern telephony architecture
• Verizon is slow to migrate to new technologies
  (Recent acquisition of MCI might help.)
• We can move forward without Verizon, but may have
  issues with
• Slowness of number portability
• Number changes may be necessary
• Dialing plans may need to change from 5 vs 10
  digits
• 911/511 Support
• VoIP phones will not work without power.

15
VoIP Pilot (Current Status)

• Campus pilot started with Vet School on 11/3
• Nursing and CETS scheduled for November.
• Van Pelt and Med School Computing for December.
• Additional schools scheduled for 2006.
• Goal - 500 participants for June 2006.
• ProDesk support services in place
• Customer and LSP programs in place
• LSP training
• Web site (http//www.upenn.edu/computing/voice/voi
  p/)
• Reference materials
• Entire campus completed in 5 years or less with
  good business drivers and most technical issues
  resolved.

16
High-speed Connectivity for desktops and servers

• School/Center Needs
• Increase desktop/server speeds
• Lower charges for 100 and 1000Mbps connections.
• 100Mbps charges have decreased from 30/month to
  16.
• ISC concerns
• Increase bandwidth to users will increase costs
  for
• Campus backbone (building and router interfaces)
• Internet
• Should we restrict bandwidth to buildings?
• Should we restrict outbound bandwidth on IP
  addresses? (like we do for residential students)