In Attendance:

Neustar has agreed to provide certification of the Supplemental Test Plan. This step will be part of the R3.0 Project Plan and will be a prerequisite to beginning Turn Up testing in Region 1. Bob Angevine - GTE expressed a concern that perhaps these test runs should be observable by an SP. This team also reiterated that the Supplemental and Primary Test Plans should include ALL requirements. Appendix D will provide a trace matrix to ensure that all requirements are accounted for in one of the test phases.

The team asked that there be a specific go/no go Neustar decision based on their acceptance of R3.0 from their vendor. In addition, the number of defects and their severity levels should be identified to the customers at this time. Marcel Champagne advised the team that this decision and info would be provided on the 6/15/00 testing call. Note: The Chair of this subcommittee would like this date on the Release 3.0 Project Plan.

Bob Angevine once again raised the concern that the test plan is posted on the secure web site, Marcel Champagne stated that this can be done with the permission of the PEs.

Beth Watkins raised an issue about Disaster Recovery. We must have the ability to change over from one site to another (Chicago – Tarrytown) with replication turned on. It is important to validate this ability due to the fact we are changing to an object-oriented database (oodb) and there is higher risk with this implementation. The team agreed that a disaster recovery test must be performed in Region 1 on the test bed. Disaster Recovery testing will also be performed in the production environment (see Rollout Strategy). The expectation of this team is that on 7/3/00 both flavors of test bed releases will be available to SPs i.e. 3.0 OODB and 2.X Oracle. Both test beds will be available until all 8 regions have converted to R3.0 – OODB. Marcel Champagne will provide verification that Neustar can support this configuration.

David Heath Neustar validated that Neustar will provide required testing resources to support the rollout strategy.

All other testing and rollout strategies were worked out and documented in the "Release 3.0 Rollout Strategy".

In our last meeting we discussed Release 3.0 Functional Requirements Specifications (FRS) Section 12 – "Migration for National Pooling". Mindi Patterson had pointed out previously that there would be no specific test cases in the Turn Up Test Plan to validate the migration plan requirements.

Test cases should have been added to 3.0 Test Plan. will add a migration test case(s). To be provided with next issue of test plan.

It had also been previously identified that Neustar will provide a pipe delimited conversion file for the pooling EDR conversion.

We will get a sample migration file prior to actual 3.0 installation. ( per Mindi same model as BDD Same as BDD format defined in 3.0 FRS )

Cindy Brown – Worldcom – raised a concern about LSMS that have inaccurate data on contaminated TNs. Subcommittee recommendation will include that SPs validate contaminated TNs prior to EDR migration. In addition, 3.0 conversion M&P should include that NPAC personnel validate that there are no "failed sp’s" in the existing pooled blocks.(for all 1k TNs, whether pooled or ported). It is recommended that this process be worked on an ongoing basis. One week prior to cutover NPAC personnel will ensure that no errant (failed sp’s) blocks exist.

In addition the Service Providers (SPs) validated that the desire is to convert to NPAC Release 3.0 region by region. This would not be national simultaneous cutover. It is acknowledged that SPs present in more than 1 region would have to possibly support both 1.4 and 3.0.

We identified 2 conversion options. They are as follows:

The following strawman processes were identified:

EDR Conversion with NPAC Install

1. 2 week prior to install Neustar will provide a full BDD (current snapshot) of pooled production data in 3.0 format. This will allow SPs to test their ability to accept load this data.
2. Starting Monday prior to conversion weekend there is to be a moratorium on all pooling activities i.e. add, delete or modify
3. Friday evening before taking NPAC system down for 3.0 installation, Neustar will create migration files for EDR SPs of all existing pooled blocks in EDR block object format

5. 1 week (5 business days) after R3.0 installation there is to be a moratorium on pooling adds, changes and deletions.

• will require LLCs to instruct NPAC personnel to prohibit changes/deletions for this period
• there is nothing to physically prevent SPs from changing/deleting over SOA unless an emergency situation

1. A sample migration file is needed as soon as possible enabling the SP/vendors to validate file structure WHEN WILL SEE?
2. A migration file is required for facilitating Turn Up testing. This is need by 7/1/00
3. A complete migration file of the entire NPAC region is required to validate production data integrity.