Presentation is loading. Please wait.

Presentation is loading. Please wait.

NPTF Wireless Discussion. 3/3/20032 Agenda Goals Strategy Current status Future plans Challenges Options.

Similar presentations


Presentation on theme: "NPTF Wireless Discussion. 3/3/20032 Agenda Goals Strategy Current status Future plans Challenges Options."— Presentation transcript:

1 NPTF Wireless Discussion

2 3/3/20032 Agenda Goals Strategy Current status Future plans Challenges Options

3 3/3/20033 Goals To meet the wireless needs of the Penn community for schools and centers inside and outside and public space both inside and outside. To have a common authentication approach with strong security and ease of administration. To have seamless roaming from one wireless LAN to another. To determine a sustainable funding model for one- time and all ongoing operational expenses.

4 3/3/20034 Strategy Adopt a phased approach. Allow technologies to mature. Find a secure, scalable and cost-effective design choice. Determine a funding model. Allow outside service providers offerings to mature to provide us with potential alternatives to PennNet wireless service.

5 3/3/20035 Current Status (Phase One) FY ’01-’02 Small, school-sponsored pilots Schools paying for their locations Mostly MAC address authentication

6 3/3/20036 Current Status (Phase One)

7 3/3/20037 Current Status (Phase Two) FY ‘03 Wider school and center-sponsored deployments Pilots for central authentication technologies using PennKey University Square College Houses Houston Hall Determine a sustainable funding model in conjunction with NPTF for public spaces

8 3/3/20038 Wireless - Phase Two

9 3/3/20039 Wireless – What We’re Learning From the Pilots University Square Not much valuable data due to low usage attributable to bad weather in October & November. College Houses (H&H) Again, not much data. Vendor technical problems have resulted in not wanting to advertise the service widely by College House staff. Houston Hall Service activated within the last 10 days.

10 3/3/200310 Wireless – What We’re Learning From the Pilots (Continued) Some progress being made on vendor related technical issues with authentication device. Auto logout not working Network management and monitoring not working DHCP lease problems Some OS/client connection problems Fledgling market offers few vendor alternatives at this time We expect to have an operational service in late June

11 3/3/200311 Future Plans (Phase Three) FY ’04 Operational central authentication deployments Van Pelt Library Wharton Conversion of existing MAC address locations to central authentication with PennKey using school/center funding. Staged school/center funded deployments. More public space deployments FY ‘05 and beyond Seamless roaming from one wireless LAN to another. Campus-wide deployments including public spaces.

12 3/3/200312 Challenges – Where Will the Money Come From? ISC will work with NPTF to determine key public spaces in which wireless should be deployed. College Green College Houses Sponsors need be identified to make these key public deployments happen.

13 3/3/200313 College Green Costs (Est. 5 APs) One Time Hardware$13,000 Labor (ISC & Contractor)$18,300 Fiber Circuit (3)$ 7,500 TOTAL$38,500

14 3/3/200314 College Green Costs (Est. 5 APs) Ongoing (Annually) Hardware (APs, Private Subnet)$3,235 Port Costs (APs, Auth. Device)$ 775 Fiber Circuit (3)$3,600 Hardware Maintenance (Auth. Device)$1,200 IP Address Charges (50)$6,072 TOTAL$14,882

15 3/3/200315 Outsourcing Option We could completely outsource our public space areas to 3 rd party providers. Some cellular service providers are beginning to “bundle” voice and wireless LAN services. (Sprint, Nextel) Support challenges could exist with a mixed wireless environment caused by users being able to use subscription service in some areas on campus and non- subscription wireless (school-funded deployments) in others.


Download ppt "NPTF Wireless Discussion. 3/3/20032 Agenda Goals Strategy Current status Future plans Challenges Options."

Similar presentations


Ads by Google