Billing and Ordering: Task Identification Forms
BOTF001.DOC - 14KB - Work in conjunction with the Network Operations SWG, as part of a joint OBSWG/NOSWG task force, to identify all data elements required to issue, confirm and provision orders requesting the installation of trunks from LEC to LEC.
BOTF002.DOC - 12KB - Identify and define all data elements required to completely bill interconnecting (LEC to LEC) trunks. This would include data elements required to validate all billed items.
BOTF003.DOC - 39936 bytes - Work in conjunction with the Network Operations SWG, as part of a joint OBSWG/NOSWG task force, to identify the standard service intervals to completely order an interconnection circuit from initiation to circuit acceptance. This will include intervals for escalation and expedite requests.
BOTF004.DOC - 12,800 bytes - Work in conjunction with the Network Operations SWG, as part of a joint OBSWG/NOSWG task force, to identify and define the minimum data elements required to order CCS7 trunks from LEC to LECs
BOTF005.DOC - 12,288 bytes - Identify the minimum data elements required to bill for CCS7 interconnections
BOTF006.DOC - 12,288 bytes - Identify the standard service intervals to completely order CCS7 trunks (LEC to LEC) from initiation to acceptance of service
BOTF007.DOC - 15KB - Work in conjunction with the Network Operations SWG, as part of a joint OBSWG/NOSWG task force, to identify and define the minimum data elements required to order A Links from CLEC to Primary STP
BOTF008.DOC - 10KB - Identify the minimum data elements required to bill for trunks from CLEC Switch to STP
BOTF009.DOC - 22KB - Work in conjunction with the Network Operations SWG, as part of a joint OBSWG/NOSWG task force, to identify the standard service intervals required to order A Links from CLEC to STP from initiation to acceptance of service
BOTF010.DOC - 12172 bytes - Define the term "Transiting" as it applies to the Ordering and Billing of circuits and traffic.
BOTF011.DOC - 11285 bytes - Define the term "Transport" as it applies to the Ordering and Billing of circuits and traffic
BOTF012.DOC - 15,360 bytes - Work in conjunction with the Network Operations SWG, as part of a joint OBSWG/NOSWG task force, to identify all data elements required to issue, confirm and provision orders requesting the installation of interconnecting transport circuits.
BOTF013.DOC - 13,824 bytes - Work in conjunction with the Network Operations SWG, as part of a joint OBSWG/NOSWG task force, to identify all data elements required to issue, confirm and provision orders requesting the installation of interconnecting transit circuits.
BOTF014.DOC - 21 KB - Define the minimum service intervals to completely order interconnecting transit circuits from initiation to acceptance of service
BOTF015.DOC -22KB - Define the minimum service intervals to completely order interconnecting transport circuits from initiation to confirmed due date
BOTF016.DOC - 12,800 bytes - Define the minimum data elements required to bill for interconnecting transport circuits (MRC and NRC)
BOTF017.DOC - 11,776 bytes - Define the minimum data elements required to bill for interconnecting transit circuits (MRC and NRC)
BOTF018.DOC - 13KB - Working in conjunction with Network Operations identify and define minimum data elements required to order all types of unbundled loops from initiation of order to acceptance of service. Service may be requested specific to available technology.
BOTF019.DOC - 13KB - Identify and define the minimum data elements required to bill for all types of unbundled loops. Loop types may be specific to technology
BOTF020.DOC - 12,800 bytes - Working in conjunction with Network Operations define the minimum data elements required to bill for the repair of unbundled loops
BOTF021.DOC - 12,288 bytes - This should be a function of Network Operations. Task is to confirm this is being undertaken to identify data elements to initiate a "repair" ticket (Network Operations?).
BOTF022.DOC - 11,776 bytes - TASK DESCRIPTION: Define "Commecting Links" within the scope of 97-8, Attachment A, as it applies to Ordering and Billing.
BOTF023.DOC - 12,800 bytes - TASK DESCRIPTION: Work in conjuction with the Network Operations SWG, as part of a joint OBSWG/NOSWG task force, to indentify all data elements required to issue, confirm and provision orders requesting the installation of Connecting Links.
BOTF024.DOC - 18,432 bytes - Identify and define the minimum data elements required to bill for Connecting Links from initiation to confirmed due date
BOTF025.DOC - 13,312 bytes - TASK DESCRIPTION: Work in conjuction with the Network Operations SWG, as part of a joint OBSWG/NOSWG task force, to identify standard intervals for odering Connecting links, from initiation to acceptance of service. This will include excalation and expedite intervals.
BOTF026.DOC - 11,776 bytes - Identify the standard billing intervals for all circuit types.
BOTF027.DOC - 13KB - To identify the standard interval for any interruption of end user service. This will include the timely update of NPAC-SMS following the transfer of the local loop within the AP facility.
BOTF028.DOC - 10351 bytes - Work in conjunction with the Network Operations SWG, as part of a joint OBSWG/NOSWG task force, to define "Riser Space" and IDF, within the scope of 97-8, Attachemnt A, as it applies to Ordering and Billing
BOTF029.DOC - 12,800 bytes - To identify the data elements that must be exchanged when a customer migrates between LECs when the LEC requires a local loop.
BOTF030.DOC - 13312 bytes - To identify the PIC/CARE data elements that need to be exchanged between a LEC and IXC when an end customer migrates between LECs
BOTF031.DOC - 9043 bytes - In all instances of ordering determine, based on agreed upon service intervals, the appropriate penalties to be applied when these service intervals are not achieved. Also, a method of determining when and how these penalties will be applied. Penalties will be applied to both Competitive and Incumbent Local Exchange Carriers.
BOTF032.DOC - 12,800 bytes - Work in conjunction with the Network Operations SWG, as part of a joint OBSWG/NOSWG task force, to identify all data elements required to issue, confirm and provision orders requesting the installation of trunks from CLEC to LEC.
BOTF033.DOC - 12,288 bytes - Identify the minimum data elements required to bill for CLEC to IXC interconnections
BOTF034.DOC - 13KB - Work in conjunction with the Network Operations SWG, as part of a joint OBSWG/NOSWG task force, to identify the standard service intervals to completely order an CLEC to LEC interconnection circuit from initiation to circuit acceptance. This will include intervals for escalation and expedite requests.
BOTF035.DOC - 17KB - Work in conjunction with the Network Operations SWG, as part of a joint OBSWG/NOSWG task force, to identify the standard service intervals to completely order an unbundled loop from initiation to circuit acceptance. This will include intervals for escalation and expedite requests.
BOTF036.DOC - 14KB - To establish the initial version of the Canadian Local Ordering Guide (CLOG), which will incorporate all data elements and service intervals for ordering and billing activities in the Canadian local market. The local ordering guide will parallel the existing CAOG.
BOTF037.DOC - 21KB - Review relevant sections of the generic CSG, Stentor proposed LEC interconnection agreement and the MCI Metro agreement and prepare a consolidated document to be submitted as the Ordering and Billing input into the Master Agreement.
BOTF038.DOC - 12,288 bytes - To establish a charter document and operational procedures for the ongoing management of changes to ordering and billing activities used in the Canadian Local Market
BOTF039.DOC - 12,800 bytes - Work in conjunction with the Numbering Sub-working group as part of a joint task force, to identify all data elements required to order telephone numbers.
BOTF040.DOC - 12,800 bytes - Work in conjunction with the Numbering Sub-working group as part of a joint task force, to identify and define all data elements required to bill for telephone numbers. This would include data elements required to validate billed items.
BOTF041.DOC - 12,800 bytes - Work in conjunction with the Operator Services Sub-working group as part of a joint task force, to identify and define all data elements required to order Message Relay Service.
BOTF042.DOC - 12,800 bytes - Work in conjunction with the Operator Services Sub-working group as part of a joint task force, to identify and define all data elements required to bill Message Relay Service.
BOTF043.DOC - 13,312 bytes - Work in conjunction with the LNP SWG, as part of a joint OBSWG/LNPSWG task force, to identify all data elements required for LNP.
BOTF044.DOC - 13,312 bytes - Identify and define all data elements required to completely bill LNP. This would include data elements required to validate all billed items.
BOTF045.DOC - 12,800 bytes - Establish a joint task force with the Directory and Operator Services SWG to determine the joint work that will need to be undertaken regarding ordering and billing for operator-to-operator interconnection and other items relating to the work being done in the DOSWG.
BOTF046.DOC - 12,800 bytes - To finalize the format/layout for the end customer data elements exchanged between LECs as originally submitted to in the April 30 OBSWG report dated 97 04 30.
BOTF047.DOC - 20295 bytes - Identify where and how the subscriber payment history database is kept. Determine all the guidelines and steps of how the database can be updated. Define all relevent subscriber payment history data elements.
BOTF048.DOC - 37860 bytes - Work in conjunction with the Network Operations SWG, as part of a joint OBSWG/NOSWG task force, to identify the standard service intervals to completely order an CLEC to LEC interconnection circuit from initiation to circuit acceptance. This will include intervals for escalation and expedite requests.
BOTF049.DOC - 7KB - Define the minimum data elements required to bill for interconnecting transport circuits (MRC and NRC)
BOTF050.DOC - 13KB - Define the minimum data elements required to dispute a bill and design a Notice of Billing Dispute (NBD).
BOTF052.DOC - 12,288 bytes - End User Dispute Migration - To identify the processes required to migrate an end user to the LEC of his or her choice as a result of a dispute.
BOTF053.DOC - 12,288 bytes - Confilicting order of Migration - To identify the processes required to manage pending migration orders which are received from two LECs for the same end user.
BOTF054.DOC - 11,264 bytes - Potential charges for unauthorized customer transfers - To identify whether charges should apply for the nauthorized transfer of an end customer from one local provider to another.
BOTF055.DOC - 12288 bytes - In conjunction with the Network Operations SWG, determine the impact of decision 98-108. Review the ordering and provisioning processes for each loop sub-type to determine whether or not the current service intervals will be impacted.
- Date modified: