CHAPTER 3.0 - ICO Conversion Implementation Schedule

3.2 Implementation Schedule

Table C. Implementation Schedule

Activity	Explanation / Time Frame
1. Overview Meeting	This meeting should be scheduled by the BSS Customer Operations within one(1) month after the Letter of Intent is signed.
2. Mapping	The ICO, BST, and the county / city / parish coordinate maps of territory so the mapping can be accomplished. Meeting may be in conjunction with activity 1 but no later than two (2) weeks after.
3. Assign ESNs on maps and provide ELT information to BST	The ICO, BST, and City / County / Parish jointly assign the ESNs to the maps, once the jurisdictional boundaries (police, fire, and ambulance services) are identified. The City / County / Parish will provide the ELT information at this time. This activity should be completed approximately 3-6 weeks after the completion of activity 2 above.
4. MSAG Preparation	ICO develops MSAG information. Method of providing MSAG information to be used for conversion will be negotiated with the BST AFIG Supervisor. (See Options below)
	a) Provide interim MSAG data) Provide interim MSAG data	(Option 1) ICO provides interim MSAG data tape to BST AFIG Supervisor tape according to section entitled "Interim Master Street Address Guide"of this guide.
	b) Provide interim MSAG data	(Option 2) If no data tape is created, provide list of MSAG streets to BST AFIG.
	c) Provide MSAG Data Tape	(Option 3) Provide MSAG Data tape to INTRADO. This option is only available if the ICO has provided verification that a TN/MSAG compare has been completed for ICO data.
5. Receive MSAG Print	MSAG print is received from BST if option 1) or 2) above was used; MSAG print received from INTRADO if option 3) is used.
6. TN Tape Preparation	ICO creates TN load according to TN Database Conversion and Updates of this guide. ICO validation of customer records should occur in order to achieve a INTRADO benchmark of less than 5% error rate on TN load.
7. Provide NXX Notification	Provide to BST AFIG supervisor during initial overview all existing NXXs involved in the county implementation. Form provided in TAB 7 of this guide. Also use the same form to advise BST of new NXXs during implementation and to advise of new NXXs after the cutover date.
8. Provide TN Data Tape	Provide TN Data tape to INTRADO and begin daily update process. See section entitled TN Database Conversion and Updates for instructions.
9. Receive TN Error	BST conducts training. Should be about one (1) week after activity 9.
10. Begin TN Error Correction	Should begin approximately one (1) week after activity 10.
11. Complete TN Error Correction	Every effort should be made to correct TN errors prior to call through testing. Should be handled one (1) week prior to date in activity 13. TN error correction will be ongoing since discrepancies will result from service order updates.
12. Call Through Testing Begins	Six (6) weeks prior to cut date.
13. Handle 911 Inquiry Forms	All 911 Inquiry forms generated during call through testing should be handled by the ICO as appropriate. All 911 Inquiry forms should be handled one (1) week prior to date in activity 15.
14. Cut Date	The date the E911 System is cut live to the public.