North American Portability Management, LLC LNPA Transition Contingency Rollback. Industry Discussion August 16 th, 2017

Transcription

1 North American Portability Management, LLC LNPA Transition Contingency Rollback Industry Discussion August 16 th, 2017

2 Agenda Feedback on the Contingency Rollback Approach Review of feedback received following July session Transaction Report Specification Orientation to reports used to assist resubmission Contingency Rollback Support Testing Development and testing schedule with industry involvement Conclusion and Next Steps Discussion 2

3 About this meeting Welcome to today s presentation! Objectives Facilitators Our goal today is to provide additional detail on the contingency rollback approach, support, and testing This is the second in a series of meetings to prepare for potential rollback following transition Greg Chiasson Principal Chicago, IL William Reilly Director Florham Park, NJ 3

4 Subject Matter Experts A number of subject matter experts are present today and will support the discussion Suzanne Addington NAPM Transition Team Sprint Inc. Teresa Patton NAPM Co-Chair & Transition Team AT&T Inc. Deborah Tucker NAPM Transition Team Verizon Inc. Paul Mazouat LNPA Transition Team iconectiv LLC John Malyar LNPA Transition Team iconectiv LLC Dave Gorton LNPA Transition Team iconectiv LLC Pat White LNPA Transition Team iconectiv LLC 4

5 Contingency Rollback Approach Feedback 5

6 Recap: Industry-Led Contingency Rollback After thorough consideration, the NAPM selected an Industry-Led rollback approach as the best option considering technical, resource, schedule, and contractual constraints In the event of a rollback, NPAC users will re-submit porting and other requests in accordance with their own processes and systems, i.e., the industry leads the effort In industry-led rollback, The Neustar NPAC will be restarted Service providers will re-connect with the Neustar NPAC and resubmit transactions that were sent since the regional cutover Requests should be resubmitted in accordance with the service providers own processes The TOM and NAPM will provide governance and facilitation iconectiv will provide individualized transaction reports and a resubmission aid document to supplement service providers own records and processes 6

7 What we heard from you Following the first session where we introduced the industry-led concept, we received a range of feedback Total 14 7

8 Contingency Rollback Communications Feedback During the initial review of the rollback plan we noted that transition participants will be provided regular reports on status; you asked for additional clarity Question How will you communicate to the Industry about any issues discovered after cutover? Will there be a website to update folks as to the progress of the cutover and if an issue(s) are discovered? If a rollback is required - how will you notify the Industry? Answer Issues will be communicated via a transition conference bridge and WebEx status summary, which will be available to all participants Yes. Status will be provided via the NPAC and NAPM LLC websites. Additionally, the TOM host a live conference call bridge and WebEx If a rollback is required, it will be announced on the live conference bridge and followed with an using the primary contact information on file for each registered provider We will further address these concerns as we detail the communications plan 8

9 Contingency Rollback Approach Feedback You asked for more detail regarding rollback triggers, alternatives considered, and the impact on industry Question How do you define the "time to repair" before you pull the trigger to rollback? Have you looked at a mechanized rollback instead? Doesn't this put too much burden on service providers for resubmission? Answer Time to repair is the TGT s best estimate based on iconectiv s assessment of the difficulty and duration of making a repair A number of mechanized options (including EBDD, MUMP, Peering) were considered but the industry-led option was selected because it best addressed technical, resource, schedule, contractual constraints While Service Providers would need to coordinate and submit requests in the event of a rollback, we should recognize that the industry has successfully handled outages, transitions, and upgrades many times in the past. This rollback approach is the baseline since, even if a mechanized option were available, the data could be damaged and manual recovery required 9

10 Transition Approach Feedback You asked for more detail regarding some areas of the transition and preparation Question What QA is planned during transition? Will SPID migrations be in a blackout state until the Industry has fully cut over to iconectiv's NPAC? What happens to SPID migrations if there is a rollback? Answer iconectiv must successfully complete many layers of QA testing before a migration decision. The QA process for NPAC Release A was summarized in the May TOEP webcast which is available on napmllc.org iconectiv is preparing a SPID migration calendar that will propose limited blackout periods during the transition. Initial versions have already been presented to the LNPA WG for evaluation Participants will resubmit SPID migration requests (as well as MUMP requests and regular porting requests) We report on the progress towards readiness in TOEP sessions and will continue to update you on topics like blackout periods as we approach the planned regional transitions 10

11 Contingency Rollback Risk Feedback You expressed some concerns regarding contingency rollback risk areas as well Question Could this plan put customers at risk of losing service or their phone numbers? What happens if a service provider doesn t resubmit transactions during a rollback? Answer End users cannot lose their numbers, but porting could be halted or delayed during a rollback recovery period. This risk drives our focus on readiness for transition and QA of the incoming NPAC so a rollback can be avoided. Service providers are expected to resubmit transactions in accordance with existing norms for failed transactions. TGT and TOM will monitor progress in the event of a rollback. Risk is our primary and continual focus. The Transition Governance Team (TGT) and TOM will monitor performance and handle rollback governance throughout the transition to manage any issues 11

12 Additional Miscellaneous Feedback You communicated some additional questions as well Question Will historical files be available after transition? Will contingency rollback presentation materials be available for those of us calling in? Will this presentation require any special software? Answer The entire NPAC database is being transferred including the LEAP (but not WDNC) history files Materials for public presentations are always made available at the napmllc.org website No, only your web browser is required 12

13 Transaction Report Specification 13

14 Contingency Rollback Details If a rollback is declared, participants will coordinate and resubmit activity according to their individual processes Monitor Assess Decide Act Transition Pre-Rollback Point of Failure Rollback NAPM TOM maintains open conference bridges and WebEx for communications Transition completed Industry NAPM iconectiv Neustar Maintain Neustar NPAC system in quiescent, state Begin logging NPAC requests Begin monitoring performance Critical failure reported to TGT with description of the problem and impact, to the extent known at that time iconectiv engineering works to resolve Transition Governance Team Assess failure status Announce rollback on the open conference bridge Transaction Report provided to each participant Transaction reports will be provided to support resubmission Begin allowing connections to the NPAC, with data as-of the close of transition Re-associate with Neustar NPAC Begin normal porting. Evaluate the Transaction Report and begin resubmitting transactions to re-sync through the usual interfaces (SOA, LTI, etc.) 14

15 What are the expectations and support provided in the event of a rollback? Industry Roles and Expectations Mechanized Users Neustar network configurations must be preserved to allow quick reconnection. LSMS and SOA systems will need to be re-associated and resynchronized LTI Users LTI users will need to revert to their Neustar LTI login credentials. Since no local system is involved, a resynchronization is not needed, but LTI users should be prepared for failed transactions and slow/delayed porting with larger operators Ancillary Service Users Little impact on ELEP and WDNC users is expected Support Provided Current industry processes and supplemental support mechanisms will be available Current service provider processes for handling errors and resubmissions iconectiv-generated transaction report iconectiv request resubmission aid NAPM / TOM coordination bridge NPAC help desk today we will further discuss the iconectiv-generated transaction report 15

16 Transaction Report Specification Overview iconectiv will provide the Transaction Report Specification no later than August 25 th for service providers to use as a design guide In November, service providers will receive a resubmission aid with various use cases and recommendations, followed by example reports near the end of January 2018 The following worksheets describe the transactions that can occur for the major objects that NPAC users can Remove New SP Old SP New SP Old SP originate. Column Cancel From Activate Disconnect Create Create Modify Modify Number Column Name Example Value Format Conflict 1 Transaction Timestamp yyyymmddhhmmss.fff Required Required Required Required Required Required Required Required Column enumerated, either New SP Create, Old Block SP Create, New SP Modify, Old SP Each Worksheet Numberdefines Column the Name set of data that can occur Example in transactions Value for Format the object as well as what data is Block Modify Modify, Cancel, Remove From Conflict, Create 2 Request Type New SP Create Activate, or Disconnect. Required Required Required Required Required Required Required Required required, optional, 1 or Transaction N/A for Timestamp each transaction yyyymmddhhmmss.fff 4 alphanumeric; if NPAC originates, will Required 3 Initiator SPID 0001 be NPAC Required Required enumerated, Required either Required Block Required Create Required or Required Required 2 Request Type 10 digits for single TN, Block 10 digits Create followed Block Modify Required Required The first 4 row Version TN of each worksheet will contain by "-" followed the by column 4 digits for TN names Range Required identifying Required 4 alphanumeric; the Note 1attributes Note 1 if NPAC that Note 1 originates, can Note appear 1 Note will in 1 Note 1 5 Version ID to 10 digits N/A N/A Note 1 Note 1 Note 1 Note 1 Note 1 Note 1 transactions for 3 the Initiator object. SPID The set of attributes 0001 be NPAC enumerated: Active, for Pending, a particular object will always be fixed. The remaining Required Required Conflict,Disconnect Pending, Cancel- yyyymmddhhmmss, seconds are rows 6will Status contain transactions Pending that occur Pending for that object. Each N/Aworksheet will Note be 2 in Note a CSV 2 format N/A N/A with pipe N/A N/A 7 LNP Type4 Scheduled LSPP Activity Date enumerated, either LSPP or LISP Required Required expected N/A to be N/A 00 N/A N/A N/A Required N/A Required character ( ) used 5 as NPA-NXX-X the delimiter between fields If an attribute for an 7 digits object in N/A for a transaction or Required is Note 1 optional 8 for Old SPID a 6transaction Block IDand 0002does not appear Always 4 alphanumeric in a transaction Required request, Required 1 to then 10 N/Adigits the pipes Required for Note the 3 object Note 3 will N/A be N/A Note 1 9 Old SP Due Date yyyymmddhhmmss N/A Required N/A Optional N/A N/A N/A N/A present 7 New Current SPID 0001 Always 4 alphanumeric 10 Old SP Authorization FALSE enumerated, either TRUE or FALSE N/A Required N/A Optional N/A N/A N/A RequiredN/A Required Intro with no value (if the last attribute listed for an object is N/A or does not appear, the ending pipe enumerated: Wireline, Wireless, Class 2 character 11 Cause will Code not appear). 51 enumerated, either 50, 51, 52, 53, or 54 N/A Optional N/A Optional N/A N/A N/A N/A 12 Old SP Medium Timer Indicator TRUE enumerated, either TRUE or FALSE N/A Optional VoIP, N/A VoWIFI, Optional Prepaid N/A Wireless, N/A Class N/A N/A 13 New Current 8 SPID SV Type 0001 Always 4 alphanumeric Wireline Required Required 1 VoIP, Required SV TYPE N/A 6 Note 3 Note 3 OptionalRequiredOptional 14 New SP Due Date yyyymmddhhmmss Required N/A Optional Optional N/A N/A N/A N/A 15 New SP Medium 9 Timer LRN Indicator TRUE enumerated, either TRUE or FALSE Optional N/A Always Optional 10 digits Optional N/A N/A RequiredN/A Optional 16 PTO Indicator TRUE enumerated, either TRUE or FALSE Required N/A always N/A9 digits, N/Aleading N/A zero pad N/A as N/A N/A 10 CLASS DPC ICONECTIV enumerated: CONFIDENTIAL Wireline, Wireless, Class - 2 RESTRICTED needed ACCESS VoIP, VoWIFI, Prepaid Wireless, Class Optional Optional 17 Type Wireline 1 VoIP, SV TYPE 6 Optional N/A Optional N/A N/A N/A N/A N/A always 3 digits, leading zero pad as must be "PENDING" (only specified for This document SV 17 New Version 11 and Data Status CLASS the confidential SSNPENDING information Undo-Cancel Requests) it 000 contains shall N/A be distributed, N/A needed Optional routed N/A or N/A made N/A available N/A Optional solely N/A Optional 18 LRN Always 10 digits Optional N/A Optional N/A N/A N/A N/A N/A to authorized persons having a need to always know 9 digits, leading within zero pad iconectiv, as except always with 9 written digits, leading permission zero pad of as iconectiv. 19 CLASS DPC 12 Column LIDB DPC needed Optional N/A needed Optional N/A N/A N/A OptionalN/A Optional NPA-NXX NPA-NXX NPA-NXX always 3 digits, leading zero pad as 20 CLASS SSN Number 000 Column Telcordia Name needed Technologies, Example Inc. Optional dba Value iconectiv. N/A always Optional 3 digits, Format N/Aleading N/A zero pad N/A as N/A N/A Create Modify Delete always 9 digits, leading zero pad as 13 LIDB 1 SSN Transaction Timestamp needed 21 LIDB DPC needed Optional N/A Optional yyyymmddhhmmss.fff N/A N/A N/A N/A OptionalN/A Optional Required Required Required always 3 digits, leading zero pad as always 9 digits, enumerated, leading zero either pad as 22 LIDB SSN 000 needed Optional N/A Optional N/A N/A N/A NPA-NXX N/A N/A 14 Number ISVM DPC Pool always 9 digits, leading zero pad Blocks as needed Create, NPA-NXX Delete, Optional or NPA- Optional 23 ISVM DPC needed Optional N/A Optional N/A N/A N/A N/A N/A always 3 digits, leading zero pad as 2 Request Type New SP Create NXX Modify Required Required Required 15 ISVM SSN Column 000 needed Optional Optional NPA-NXX 4 alphanumeric; if NPAC originates, 3 Number Initiator SPIDColumn Name 0001 Example always 9 Value digits, leading zero pad will be NPAC Format as Required Required NPA-NXX Required Create Delete 16 CNAM DPC needed Optional Optional 4 Service 1 Provider Transaction ID Timestamp always 3 digits, Always leading 4 zero alphanumeric pad yyyymmddhhmmss.fff as Required Required Required Required 17 CNAM 5 SSN needed Always 6 digits NPA-NXX enumerated, Optional either LRN Optional Required Create or Note 1 Note 1 6 NPA-NXX Column NPA-NXX-X NPA-NXX-X NPA-NXX-X 2 IDRequest Type LRN always Create 9 digits, 1 leading to 10 digits zero pad LRN as Delete N/A Note Required 1 Note 1 Required 18 WSMSC 7 DPC Effective Timestamp Number Column Name needed yyyymmddhhmmss Example Value Optional Format Optional Required Required Create N/A Modify Delete 1 Transaction Timestamp alphanumeric; yyyymmddhhmmss.fff if NPAC originates, always 3 digits, leading zero pad as Required Required Required 19 WSMSC SSN 3 Initiator SPID needed will be NPAC Optional enumerated, Optional either LRN Create Required or Required 4 Service 2 Provider Request ID Type 0001 NPA-NXX-X Always Create 4 alphanumeric LRN Delete Required Required Required Required 20 Alternative SPID 0003 Always 4 alphanumeric Optional Optional 3 Initiator SPID NPAC Will always be NPAC Required Required Required 21 Alt-End User Location LRN 5 Value to 12 digits, leading zero allowed Always 6 digits Optional Optional Required Note 1 4 Service Provider ID 0001 Always 4 alphanumeric Required Required Required 22 Alt-End User Location 6 Type LRN ID always 2 digits, leading zero allowed 1 to 10 digits Optional Optional N/A Note 1 23 Alt-Billing ID A40P 1 to 4 alphanumeric characters Optional Optional 5 NPA-NXX-X Always 7 digits Required Note 1 Note 1 24 Voice URI sip:user@example.com 1 to 255 characters Optional Optional 6 ID to 10 digits N/A Note 1 Note 1 25 MMS URI 7 mms: to 255 characters Effective Timestamp Optional yyyymmddhhmmss Optional Required Required N/A 26 SMS URI 8 sms: Pseudo 1 LRN to 255 Indicator characters NPA-NXX-X FALSE Optional enumerated, Optional either TRUE or FALSE Required N/A N/A 27 Last Alternative SPID X342 Always 4 alphanumeric Optional yyyymmddhhmmss, Optional seconds are 28 SOA Origination Flag Scheduled Activity Date yyyymmddhhmmss Optional expected to Optional be 00 N/A N/A Optional 30 Suppress Initiator SPID FALSE enumerated, either TRUE or FALSE Optional Optional 31 Suppress Grantor SPID FALSE enumerated, either TRUE or FALSE Optional Optional 32 Suppress Delegate SPID FALSE enumerated, either TRUE or FALSE Optional Optional 33 Suppress Other SPID FALSE enumerated, either TRUE or FALSE N/A N/A 34 Suppress Other SPID Delegates FALSE enumerated, either TRUE or FALSE N/A N/A The specification will include: 1. An Excel file, organized into tabs for ease of analysis (shown at left) 2. A Word document describing how to use the report The specification will be distributed by to the primary contact of each registered user 16

17 Transaction Report Intro Each Worksheet defines the set of data that can occur in transactions for the object, as well as what data is required, optional, or N/A File structure Worksheets will be in a CSV format with a pipe character ( ) used as the delimiter The first row of each worksheet will contain the column names identifying the attributes that can appear in transactions for the object. The remaining rows will contain transactions that occur for that object. 1. Transaction Timestamp Request Type Initiator SPID Version TN Version ID Status LNP Type Old SPID Old SP Due Date Old SP Authorization Cause Code Old SP Medium Timer Indicator New Current SPID New SP Due Date New SP Medium Timer Indicator PTO Indicator SV Type New Version Status LRN CLASS DPC CLASS SSN LIDB DPC LIDB SSN ISVM DPC ISVM SSN CNAM DPC CNAM SSN WSMSC DPC WSMSC SSN End User Location Value End User Location Type Billing ID Alternative SPID Alt-End User Location Value Alt-End User Location Type Alt-Billing ID Voice URI MMS URI SMS URI Last Alternative SPID Customer Disconnect Date Effective Release Date SuppressInitiator SPID SuppressGrantor SPID SuppressDelegate SPID SuppressOther SPID SuppressOther SPID Delegates New SP Create SP Pending LSPP SP99 SP FALSE FALSE Wireless mms: sms: Old SP Create SP LSPP SP FALSE 50 TRUE SP Activate SP SP Old SP Modify SP Pending SP01 TRUE TRUE Example SV worksheet with 4 transactions Notes If an attribute for an object is N/A for a transaction, or is optional for a transaction and does not appear in that request, the pipes for the object will be present with no value If the last attribute listed for an object is N/A or does not appear, the ending pipe character will not appear The set of attributes for a particular object will always be fixed. 17

18 Transaction Report - SV Data Tab The SV Data tab will provide a list of all porting requests submitted by the Service Provider: New SP Create, Old SP Create, New SP Modify, Old SP Modify, Cancel, Remove from Conflict, Activate, Disconnect Remove New SP Old SP New SP Old SP Column Cancel From Create Create Modify Modify Number Column Name Example Value Format Conflict Activate Disconnect 1 Transaction Timestamp yyyymmddhhmmss.fff Required Required Required Required Required Required Required Required 2 Request Type New SP Create enumerated, either New SP Create, Old SP Create, New SP Modify, Old SP Modify, Cancel, Remove From Conflict, Activate, or Disconnect. Required Required Required Required Required Required Required Required 3 Initiator SPID alphanumeric; if NPAC originates, will be NPAC Required Required Required Required Required Required Required Required 4 Version TN digits for single TN, 10 digits followed by "-" followed by 4 digits for TN Range Required Required Note 1 Note 1 Note 1 Note 1 Note 1 Note 1 5 Version ID to 10 digits N/A N/A Note 1 Note 1 Note 1 Note 1 Note 1 Note 1 6 Status Pending enumerated: Active, Pending, Conflict,Disconnect Pending, Cancel- Pending N/A N/A Note 2 Note 2 N/A N/A N/A N/A 7 LNP Type LSPP enumerated, either LSPP or LISP Required Required N/A N/A N/A N/A N/A N/A 8 Old SPID 0002 Always 4 alphanumeric Required Required N/A Required Note 3 Note 3 N/A N/A 9 Old SP Due Date yyyymmddhhmmss N/A Required N/A Optional N/A N/A N/A N/A 10 Old SP Authorization FALSE enumerated, either TRUE or FALSE N/A Required N/A Optional N/A N/A N/A N/A 11 Cause Code 51 enumerated, either 50, 51, 52, 53, or 54 N/A Optional N/A Optional N/A N/A N/A N/A List continues to 46 attributes 18

19 Transaction Report Number Pool Blocks The Number Pool Block tab will provide a list of all pool block activity: Block Create, Block Modify Column Block Number Column Name Example Value Format Create Block Modify 1 Transaction Timestamp yyyymmddhhmmss.fff Required Required 2 Request Type Block Create enumerated, either Block Create or Block Modify Required Required 3 Initiator SPID alphanumeric; if NPAC originates, will be NPAC Required Required 4 Scheduled Activity Date yyyymmddhhmmss, seconds are expected to be 00 Required Required 5 NPA-NXX-X digits Required Note 1 6 Block ID to 10 digits N/A Note 1 7 New Current SPID 0001 Always 4 alphanumeric Required Required 8 SV Type Wireline enumerated: Wireline, Wireless, Class 2 VoIP, VoWIFI, Prepaid Wireless, Class 1 VoIP, SV TYPE 6 Optional Optional 9 LRN Always 10 digits Required Optional 10 CLASS DPC always 9 digits, leading zero pad as needed Optional Optional 11 CLASS SSN 000 always 3 digits, leading zero pad as needed Optional Optional 12 LIDB DPC always 9 digits, leading zero pad as needed Optional Optional 13 LIDB SSN 000 always 3 digits, leading zero pad as needed Optional Optional 14 ISVM DPC always 9 digits, leading zero pad as needed Optional Optional List continues to 34 attributes always 3 digits, leading zero pad as 15 ISVM SSN 000 needed Optional Optional always 9 digits, leading zero pad as 19

20 Transaction Report Other tabs NPA-NXX NPA-NXX-X Column Number Column Name Example Value Format NPA-NXX Create NPA-NXX Modify NPA-NXX Delete 1 Transaction Timestamp yyyymmddhhmmss.fff Required Required Required enumerated, either NPA-NXX Create, NPA-NXX Delete, or NPA- 2 Request Type New SP Create NXX Modify Required Required Required Column NPA-NXX-X NPA-NXX-X NPA-NXX-X 4 alphanumeric; if NPAC originates, Number 3 Column Initiator SPID Name Example 0001 Value Format will be NPAC Required Create Required Modify Required Delete 1 4 Transaction Service Provider Timestamp ID yyyymmddhhmmss.fff Always 4 alphanumeric Required Required Required Required Required Required 5 NPA-NXX enumerated, Always 6 digits either LRN Create or Required Note 1 Note Request NPA-NXX Type ID NPA-NXX-X Create LRN 1 to 10 Delete digits N/A Required Note Required 1 Note Required 1 37 Initiator Effective SPID Timestamp NPAC Will yyyymmddhhmmss always be NPAC Required Required N/A Required 4 Service Provider ID 0001 Always 4 alphanumeric Required Required Required NPA-NXX-X first 4 attributes same as NPA-NXX 5 NPA-NXX-X Always 7 digits Required Note 1 Note 1 6 NPA-NXX-X ID to 10 digits N/A Note 1 Note 1 7 Effective Timestamp yyyymmddhhmmss Required Required N/A NPA-NXX-X Pseudo 8 LRN Indicator FALSE enumerated, either TRUE or FALSE Required N/A N/A yyyymmddhhmmss, seconds are 9 Scheduled Activity Date expected to be 00 N/A N/A Optional LRN Column Number Column Name Example Value Format LRN Create LRN Delete 1 Transaction Timestamp yyyymmddhhmmss.fff Required Required enumerated, either LRN Create or 2 Request Type LRN Create LRN Delete Required Required 4 alphanumeric; if NPAC originates, will be NPAC Required Required 3 Initiator SPID Service Provider ID 0001 Always 4 alphanumeric Required Required 5 LRN Always 6 digits Required Note 1 6 LRN ID to 10 digits N/A Note 1 20

21 Report Distribution Actual transaction reports (i.e., not the specification), including the example reports, will be loaded to the regular iconectiv SFTP site for download This will be the same location used for Ad-Hoc reports and SPs may use their regular SFTP credentials Since files will be individual for each SPID and region, SPs may receive multiple files Every primary user (SP) will be given access and assigned credentials during onboarding 21

22 Feedback and Questions Transaction Report Specification documents will be distributed no later than August 25 th to the primary contact for each registered iconectiv NPAC user When you receive the specification, please review and provide feedback as soon as possible so that any issues or questions can be addressed. Feedback and questions should be ed to If you do not receive the specification, please contact iconectiv using the same address so that we can ensure that you receive a copy If you have additional comments or concerns please do not hesitate to reach out to the TOM through the comments box at look under the LNPA Transition tab 22

23 Contingency Rollback Support Testing 23

24 Preparation Timeline iconectiv has already begun to develop supporting material. Testing the reports and processes will follow Review/Assess Test Note: Dates are subject to change Today Ready mid-march 2018 Overall TOM/TT iconectiv Industry Industry participant preparation and involvement will be needed to execute this plan 24

25 Opportunities to get involved Industry participants will be able to begin reviewing the report specification and start their internal preparations in just a few days. 18 Aug Report spec distributed 27 Nov Resubmission aid distributed 21 Aug 30 Jan 4 Oct 30 Jan Example reports provided 31 Jan 13 Mar Note: Dates are subject to change Today Ready mid-march 2018 Overall TOM/TT iconectiv Industry 25

26 Conclusions and Next Steps 26

27 Conclusions and next steps Today we reviewed your feedback on the contingency rollback plan and provided further detail on the transaction reports and schedule Upcoming next steps include: Providing an update on the Transaction Report Specification, and any feedback received, during the September 6 th TOEP session Arranging a separate session to address and describe any resulting changes if there is substantial feedback Updating the industry on readiness of the resubmission aid and example reports at the October TOEP Facilitating additional rollback working sessions at various checkpoints, e.g., availability of the rollback resubmission aid, example reports, etc. 27

28 Discussion 28

29 Thank you for your participation