NG 911 PSAP Informational Presentation 5/21/2013 Jerry Christians ECN/MN DPS NG911 Project Manager 5/23/2013 1
Project Goals 1. Review of Program’s Three Phases 2. Project Objectives: Implementing an IP Network to all PSAPs 3. Network Overview 4. Next Gen Components at the PSAP 5. Equipment Installation 6. Required Technicians 7. Resiliency with circuit outage 8. Measure and Monitor Network 9. FoCR (Function of Code R) 10. Migration Methodology 11. Conditional Routing Options 12. 911 Plan Change Letter 13. PSAP Installation Guide 14. Grant Process 15. 5/23/2013 2
Jerry Christians Dana Wahlberg Jake Jacobson MN 911 Project Mgr. MN ECN/DPS. CenturyLink Project Mgr. Larry Hegle Thomas Richard Enterprise Visions Enterprise Visions 5/23/2013 3
Improve call transfer functionality between PSAPs Create an IP network that will connect all Minnesota PSAPs on a statewide Emergency Services IP Network (ESInet). This network is the foundation for Next Generation 911. Improve call routing. (call origination for border telephone exchanges) 5/23/2013 4
Phase 1 completed September 27, 2010 ◦ Phase I provides interoperability among all Minnesota PSAPs – Any PSAP can transfer a 911 call to any other PSAP ◦ An average of over 3,000 Interop Call Transfers made per month! . Phase 2 focused on to two PSAPs: ◦ Carver (CenturyLink Network/Data; IES CPE) –Migrated Nov 1, ◦ 2011 ◦ Kandiyohi (IES Network/Data; IES CPE) – Migrated Mar 1, 2012 Phase 3 migrating remaining MN PSAPS (102 at this time) 5/23/2013 5
Demonstrate CenturyLink Next Gen network is a reliable 1. alternative to the existing EM and ALI circuits. Test methods and processes utilized to install and migrate a 2. PSAP from the legacy EM trunking and ALI to NextGen emergency services IP network (ESInet). Exhibit adequate maintenance support for the PSAP Gateway 3. Modules. Demonstrate ability to interface with the IES database 4. Demonstrate the network monitoring and reporting 5. methodologies used to measure the health and performance of the network elements. Identify and document the PSAP migration strategy for entire 6. project. 5/23/2013 6
Migrate all MN PSAPs to the IP network 1. At the end of 2012, 20 PSAPs had migrated To date, a total of 48 PSAPs have migrated Identify a strategy for removing Legacy Selective Routers out of the network 2. (Phase 4 planning.) Identify the requirements to connect to another Emergency Services Internet 3. Protocol Network (ESInet) Understand and document where the diversity of the network ends to each 4. PSAP and implement a thoroughly tested NG911 solution utilizing NENA standards and open architecture. “Call Origination” Implement Call Origination as PSAPs migrate to ESInet. 5. Call Origination – for phone exchanges in border PSAP areas, directing call to the intended PSAP without having additional step of Call Transfer 5/23/2013 7
104 Minnesota PSAPs to NextGen Network ◦ Network Scope – New Network From Legacy Selective Router (LSR) to the PSAP. Connect PSAPs to the ESInet ALI Links will be migrated the ESInet ◦ ALI Data Scope ALI reporting will be reviewed to ensure there is no impact to existing metrics ◦ Reporting Scope New Network Reporting tools, Control Center (formerly QControl) and Clearview Initial VQES MOS (Mean Opinion Score) test provided upon network and equipment Installation. 5/23/2013 8
Examination of how NextGen applications (GIS, Text Messaging, ◦ video feed, etc) will work with the core 911 service of Voice and ALI. CenturyLink’s 911system to be compatible with the State’s GIS ◦ database as the source GIS data, should the State begin trialing a GIS application. Connecting IES ALI database to ESInet. PSAPs that formerly used IES ◦ as their ALI database service provider will continue to use IES for that function. 5/23/2013 9
Next Generation Applications, such as Text Messaging, IP Alternate Routing or GIS (though can be addressed in separate projects) 5/23/2013 10
5/23/2013 11
New Trunks Legacy Selective Routers (LSRs) to LSRG Legacy Selective Router Gateways IP Network Backbone (LSRGs) in Place LSRG All MN PSAPS Interoperable in using universal 3 Digit Star Codes IP Network Backbone Diverse T1s in Place to the PSAP 5/23/2013 12
The State and CenturyLink have engaged MNIT to utilize their network at selected PSAPs to obtain additional diversity. As of this date, MNIT has provided diversity options for 20 PSAPs IP Network Backbone in Place Diverse T1s to the PSAP 5/23/2013 13
Leg Legacy S Sel elec ective e Rou oute ter Ga Gatewa way VPOP OP VPOP OP Leg Legacy S Sel elec ective e Rou oute ter Ga Gatewa way 5/23/2013 14
“511 Building” in Minneapolis Atomic Data Center in Edina 5/23/2013 15
5/23/2013 16
5/23/2013 17
PSAP G Gat atew eway ay M Man anag ager 5/23/2013 18
PSAP PGMs in cabinet To To Smaller Cabinet, Rack or Wall mount options also available Install Team brings the housing equipment with them at time of Install 5/23/2013 19
5/23/2013 20
5/23/2013 21
1) ECN/MN MN DPS Presenta tatio ion Meetings organized by PSAPs tied to a specific Selective Router and priority of deployment 2) 911 Plan n Chang ange Letter ECN MN DPS to receive a signed 911 Plan Change Letter from PSAP acknowledging its participation 3) Su ) Survey PSAP will be surveyed for operational readiness (power, space, equipment housing, call logger on trunks, test line,etc) 4) Weekly ly Statu tus M Meetin ting PSAP Groups – conference call weekly to discuss status – readiness, installation, pre-migration, migration 5) A Acce ceptance ce PSAP to acknowledge formal acceptance and move into production mode 5/23/2013 22
Stage 1 Site Analysis and Component Preparation Engineering analysis of specific location site survey data Receipt and Inventory of Network Equipment Stage 2 Deployment Kit Creation, Testing and Delivery Staging and configuration of devices Mounting the equipment in the appropriate housing (Rack/cabinet) Build cabling harnesses; Power testing of Equipment Kit preparation for transport and delivery Stage 3 On-site installation Arrive on site as scheduled Verification of deployment kit; Install T ll Team Installation of cabinet/rack deployment kit is is Secure cabinet/rack and providing required bracing Minne nesot ota- Verification of Power; Connection of Network; Connection of site wiring Testing of circuit connectivity ba based d Verification of installation completion 5/23/2013 23
5/23/2013 24
5/23/2013 25
T1 Outag Outage R Resiliency T1 Down Other T1(s) configured to send all voice traffic. ALI traffic for PSAPs utilizing Intrado will also receive both ALI links 5/23/2013 26
• Gateway Equipment will be replaced by Support team • Support Team may move trunks initially to functioning equipment if needed for minimizing disruption. 5/23/2013 27
Device at PSAP (Tektronix PP30) used for MOS Score Centrally located Calculation and other quality measurements. Active Testing Device (Tektronix PP600) Makes and Measures Test Calls to PSAP Example MOS readout (For Phase 1 Network) 5/23/2013 28
CTL Service Manager has access to network reporting tools Spike –when network was down at Carver for TVSS installation In In addition tion, Network O ork Operati tion ons Cen Center er h has as sev ever eral mon monit itoring tool tools Fo For supporti porting N g Next G Gen 5/23/2013 29
Order of PSAP Migration by Legacy Selective Router Alternate by CenturyLink and IES Routers Schedule to commence upon acceptance of Phase II PSAPs 5/23/2013 30
Lessons L Learned t d that a alt ltered pla d planned s d schedu dule Establ blis ishing LATA V VPOPs re requ quired de d depe pendencies o on mult ltipl iple carri rriers rs , , taking a addit dditio ional t l tim ime t than e expected Establ blis ishing de desir ired d div divers rsit ity t to the P PSAP is is chall llengin ing CTL d develop ops d designs of of wha hat i it t can of n offer w with thin i its ts ow own n network capa pabilit bilities a and d re rela latio ionships ips w wit ith o other c carrie rriers, t , this is may not ma not be suf ufficient. t. Appro pproach n now: Whi hile f fol ollow owing the the i inte ntenti tion on of of “b “by LSR” – CTL CTL h has as r reac ached ahe head to to the the first thi t third of of PSAPs i in n the the or order , , to to develop op the the de desig igns s so the S State c can a assess if if div divers rsity is is sufficie ient, a and d then de determine what a addit dditio ional a assis istance m may be be re requ quired, d, su such a as s enga gagi ging g MNIT. Design a De appro pproval a and d subs bsequent pro provis isio ioning w will ill driv drive t the schedule of of mi migrati tion on. 5/23/2013 31
5/23/2013 32
5/23/2013 33
Recommend
More recommend
