Service Coordination Group Milestones National SMS Interim Text Preparation and Implementation Activities Dates re end of 3Q13 Dates re May 15, 2014 Responsible Notes (re Verizon plan) (note overlap cases) Milestone Events and Dates, for major enabling activities to be developed Background & History - see Appendix H [Early actions by individual carriers should provide input to the below activities] Organize Stakeholders regarding NENA/APCO led Work Team by 4/15/2013 Hixson/English 1. Investigation and Resolution of Open Questions (see Appendix A for detail) 4/15-5/15/2013 Appendix A 2. Development of Planning and Impacts Info for 9-1-1 Authorities 5/1-6/1/2013 Outline in Appendix B 3. Delivery of Initial 9-1-1 Authority Info 6/1-6/15/2013 includes sessions at NENA2013 Conference 4. Develop Common Procedures and Service Operations (Carriers, TCC Operators, Public Safety) 5/15-7/1/2013 [Converge early carrier actions and procedures into common M&P] 5/15-7/15/2013 [Coordinate ATIS Guidelines to Implement TCCs with overall plans] 5/15-9/1/2013 5. Provide Info on this Plan and Objectives as Recommendations through SC1 and EAAC to the FCC 6/1/2013 6/1/2013 SC1 and Co-chairs 6. Develop Consumer Education (led by FCC?) 6/1- 8/1/2013 7. Deliver Consumer Education 8/1/-11/15/2013 8. Update 9-1-1 Authority Education and Deliver 7/1-9/15/2013 9. Develop PSAP Operations Education 9/15-10/15/2013 10. Deliver PSAP Operations Education 10/15-12/15/2013 Train the Trainer? 12. Develop Common Testing Plan 11/15/2013- 1/15/2014 Appendix C 13. Develop national multicarrier Deployment Plan 8/1/2013 2/1/2014 14. Accomplish Testing 7/15-8/15/2013 2/1-3/1/2014 15. Deploy Nationally 8/16-9/30/2013 4/1-5/15/2014 16. Review Results and Make Any Adjustments 10/1-12/1/2013 5/16-7/16/2014 Service Coordination Group Work List sample SMS Interim Text Resolution and Development Issues Issue Carriers TCC NENA APCO ATIS FCC Notes 9-1-1 Text charges X Originating Response from PSAP PSAP callback Method for PSAP callbacks after `session' terminated TTY Limitations Summarize TTY interface experiences to date X Questions sent out TTY feasability tests? Fully define PSAP interface options and variations X X X TCC doing SMS <> TTY Baudot conversion Further definition needs, re accuracy issues, and any mitigating capabilities · Through E9-1-1 voice channel · Through non-E9-1-1 transport TCC <> central web server, and related limitations TCC <>IP PSAP with local text server - no ESInet, but with local IP network among a set of PSAPs - when using ESInet without NG9-1-1 core services/system TCC interface to ESInet that is running NG9-1-1 capabilities supporting text (but without carrier MMES IP capability)