Search Stanford:

Pages on this Project

• E911 Project Staffing
• Meeting Minutes

• QUICK LINKS
  • answers.stanford.edu
  • apple.stanford.edu
  • computing.stanford.edu
  • courses.stanford.edu
  • datarates.stanford.edu
  • dell.stanford.edu
  • departmentphone.stanford.edu
  • email.stanford.edu
  • ess.stanford.edu
  • helpsu.stanford.edu
  • myitserviceshelp.stanford.edu
  • orderithelp.stanford.edu
  • software.stanford.edu
  • studentphone.stanford.edu
  • techtraining.stanford.edu
  • tools.stanford.edu
  • unixcomputing.stanford.edu
  • vpn.stanford.edu
  • web.stanford.edu
  • windows.stanford.edu
• SERVICES
  • IT Services Only
  • All Campus Providers
    → computing.stanford.edu
• GETTING HELP
  • Stanford Answers
  • HelpSU: IT Help Desk
  • Training
• PROJECTS
• ABOUT US
  • What We Do
  • Organization Chart
  • Jobs
  • Contact info
• INTERNAL
• SEARCH

  • Search IT Services:
     

• IT Services Internal
• IT Services Projects
• E911 for VoIP

E911 for VoIP Project

Background and Overview

E911 voice services are critical to providing timely responses in emergency situations. All traditional telephones on Stanford’s campus have their building’s address in the AT&T Public Safety Answering Point (PSAP) data base. When someone dials 9-911 (or 911) from a traditional telephone on campus, the PSAP knows the proper address for dispatching of emergency services.

Stanford’s VoIP sets and service provide a different set of challenges. Sets can be moved between buildings and service can be moved by logging into a different set. This creates a mis-match between the original building address information in the PSAP and the actual location of the set. Currently ITS is deploying VoIP sets with a disclaimer approved by OGC that states if a customer moves a phone, that customer must contact ITS and have the address location updated for 911 purposes. In spite of this “requirement”, we know that this does not always happen. Today ITS processes approximately 50 work requests for VOIP phone moves per month. Not having the proper address location information for the VoIP service means the PSAP could dispatch emergency services to the wrong address.

The RedSky E911 Manager allows automated management of location data for all VoIP telephones by establishing real-time location discovery of IP phones on the network. This product is tightly integrated with the CS2100 product to automatically track, manage and deliver life-saving location identification information for re-located VoIP sets on the Stanford campus.

Risks of Not Doing Project

1. Incorrect location/address information in PSAP could result in delayed emergency services because they are sent to the wrong address.
2. The University could have significant liability issues.

Project Team

Role	Primary Responsibilities
Project Sponsor	Bert Stubbs
Project Manager	TBD
Product Manager	Christine Moe
Business Owner	Bert Stubbs
Operations Owner	Christine Moe
Client	N/A — Infrastructure Project

Outcomes

1. Provide real-time address/location information for 911 calls from ITS supported VoIP wired sets.
2. Allow additional VoIP set mobility on campus. This could eliminate the need for a client to cut a work order to move their voice service from one VoIP enabled building to another.

Outputs

Output	Description
Procurement	Procure equipment and associated peripherals.
Installation of RedSky system and integration with CS2100
Test on the University VoIP network	Configure all equipment and test functionality and integration with campus VoIP Network.
Test on the Hospital network.	Configure all equipment and test functionality and integration with Hospital Network.

Project Metrics

Project Metric	Target
911 calls from a moved VoIP set or service shows appropriate address/location information at the PSAP	100%

Timeline

Project Phase	Major Milestone	Estimated Completion Date
Initiation	Charter Approved	8/31/2007
Planning	Kick-off Meeting	9/15/2007
Execution	Equipment Ordered	September 2007
	Install and integrate with CS2100	November 2007
	Deploy to ITS pilot group	December 2007
	Deploy to Hospital pilot group	February 2008
	Expand to all VoIP locations on campus	April 2008
Monitor & Control	QC Plan Developed	November 2007
(Testing/QC)	Test with VoIP deployment in ITS buildings	December 2007
	Test with Hospitals’ networks	February 2008
Closing	Closing Meeting

Project Scope

1. Implement E911 relocation for all ITS provided VoIP wired sets.
2. Integrate with Pinnacle system so new location information is updated in records when a set is moved.
3. Review Phone Move process to determine impact of E911 automation.

Issues, Risks, and Mitigating Factors

Issue/Risk	Likeli-hood (HML)	Impact (HML)	Mitigation
Network architecture or security will not allow discovery of sets.	L	H	None — gating factor.