 |
Unbundled usage charges on CABS Y40 and Y42 bills are mainly in the form of total MOU for each usage rate element per Verizon central office. For rate elements that apply on a per call or query basis, the total number of calls or queries is displayed instead of MOU.
In order to verify the accuracy of the charges on a particular bill, the UNE CLEC will need the following sources of information:
- DUF records
- CABS unbundled usage bills
- Verizon-North unbundled call scenarios
- NECA (National Exchange Carrier Association) FCC tariff # 4
- LERG (Local Exchange Routing Guide)
- Applicable tariff or Verizon/UNE CLEC contract rates and charges
- Record of UNE CLEC's end user telephone numbers
- Record of UNE CLEC's dedicated trunk port locations (if applicable)
The basic objectives of the bill verification process are as follows:
- Identify DUF records that should be included as current usage in current bill
- Identify all DUF records belonging to specified EOS (end office switch
- Assign a specific call scenario to each DUF record identified in objective 2
- Calculate MOU and call totals for each call scenario
- Apply NCTA to each Conversation MOU total requiring Access MOU
- Calculate MOU totals for each per MOU rate element
- Calculate call or query totals for each per call or query rate element
- Calculate OWS (Operator Work Second) totals for each per OWS rate element *
- Reconcile DUF per EOS totals with bill per EOS totals
- Verify accuracy of usage charges
* NOTE: Until the ATIS/OBF group makes an EMI record field available to contain OWS, it will not be possible for Verizon to include this information in the DUF. So the accuracy of these charges cannot currently be verified.
|
|
| back to top |
|
|
|
Objective 1: Identify DUF records that should be included as current usage in current bill |
|
The usage section of each Y40 and Y42 bill displays the start and end dates covered by the current usage charges on the bill. To achieve objective 1, the UNE CLEC must select the DUF records that fall between those two inclusive dates. Sometimes usage that has been transmitted in the DUF is not posted immediately to the billing system, misses the current bill and is included in the next one. When this occurs, charges for that usage will appear in a separate section with its own start and end dates. This enables a CLEC to reconcile a discrepancy from a previous month's bill validation process.
|
|
| back to top |
|
|
|
Objective 2: Identify all DUF records belonging to specified EOS |
|
Unbundled usage charges are totaled by EOS. To achieve objective 2, the UNE CLEC must assign each DUF record to its proper EOS. LERG and NECA 4 can be used for this purpose based on the NPA-NXX of the relevant UNE line number. DUF records include the true location of ported numbers.
|
|
| back to top |
|
|
|
Objective 3: Assign a specific call scenario to each DUF record identified in objective 2 |
|
To achieve objective 3, the UNE CLEC must identify some or all of the following attributes of the call:
- Call type
- Ownership of originating end user
- Ownership of terminating end user
- Ownership of trunk port used
- Ownership of originating switch
- Ownership of terminating switch
- Call routing method
Call Type
The Call Type may be one of the following:
- Local Intra-Switch
- Local Inter-Switch
- IntraLATA Toll
- IntraLATA Access (including access OS & DA calls)
- InterLATA Interstate Access (including access 800, 900, OS & DA calls)
- Terminating Access
- Local 800 Intra-Switch
- Local 800 Inter-Switch
- IntraLATA 800
- PhoneSmart
- Directory Assistance
- Busy Line Verify
- Busy Line Verify & Interrupt
- 0+ Calling Card
- 0+ Collect
- 0+ Bill to Third
- Directory Assistance with Call Completion
- 0- Operator Handled
- Circuit Switched Data
- Packet Switched Data
- Information Provider
- Operator Applied DA Credit
- Automated Coin Toll
The individual DUF record indicates which of the above call types applies.
Originating End User
Ownership of the originating end user may be one of the following:
- CLEC
- Verizon or another CLEC
- Not applicable (e.g., Terminating Access Call)
The individual DUF record includes the 10 digit originating end user number, and the CLEC's record of its unbundled end user telephone numbers determines ownership.
Terminating End User
Ownership of the terminating end user may be one of the following:
- CLEC
- Verizon or another CLEC
- Not applicable (e.g., Originating Access Call)
The individual DUF record includes the 10 digit terminating end user number, and the CLEC's record of its unbundled end user telephone numbers determines ownership.
Trunk Port
Ownership of the trunk port used may be one of the following:
The individual DUF record includes the NPA NXX that identifies the originating switch, and the CLEC's record of its dedicated trunk port locations determines ownership of the trunk port used.
Originating Switch
Ownership of the originating switch may be one of the following:
- Verizon
- CLEC
- Another CLEC
- Not applicable (e.g., Terminating Access Call)
The NECA FCC tariff # 4 indicates the ownership of the originating switch.
Terminating Switch
Ownership of the terminating switch may be one of the following:
- Verizon
- CLEC
- Another CLEC
- Not applicable (e.g., Originating Access Call)
The NECA FCC tariff # 4 indicates the ownership of the terminating switch.
Call Routing Method
Call routing method may be one of the following:
- Direct Routed (End Office to End Office)
- Tandem Routed (via Verizon Tandem Switch)
The individual DUF record indicates the call routing method for all access calls. In addition, all calls that pass through a TOPS (Traffic Operator Position System) are classified as tandem routed. All other local and intraLATA toll calls will be automatically billed as direct routed, and will therefore not carry an unbundled Transit Tandem Switching Charge (TTSC).
|
|
| back to top |
|
|
|
Objective 4: Calculate MOU and call totals for each call scenario |
|
To achieve objective 4, the UNE CLEC must first separate DUF records within each call scenario by the following call types:
- Circuit Switched Data—EMI record 10 01 62 or 11 01 62
- Packet Switched Data—EMI record 10 12 20 or 11 12 20
- Analog (Voice)—All other EMI records
Next, within each call type, the UNE CLEC must separate DUF records by TOD (Time of Day). Use the start and end time of each DUF record together with the TOD parameters published in the applicable tariff or Verizon/UNE CLEC contract.
When a call spans more than one TOD period, the MOU are split between all time of days included in the call, but the call itself is assigned only to the time of day in which the call is initiated.
Calculate MOU and call totals for each sub-group and round MOU totals up or down to the nearest whole minute.
|
|
| back to top |
|
|
|
Objective 5: Apply NCTA to each Conversation MOU total requiring Access MOU |
|
All per MOU rate elements are applied using Access Time, except the following, which are applied using Conversation Time:
- Whenever applied: UNRCC, UCRCC, ALSC
- Only when applied to terminating access calls: ULSC, USTPC, TTSC, UTTC 2
All terminating DUF records and all originating intraLATA DUF records carry Conversation Time. Originating access DUF records carry Access Time.
To achieve objective 5, all MOU totals for non-access call scenarios must first be converted from Conversation MOU to Access MOU using NCTA (Non-Conversation Time Additive). Non-Conversation Time is the portion of total Access Time which a caller spends connected to the network either before a called party picks up or during a call attempt which does not complete.
The NCTA formula can be found in state tariffs, together with state specific constants to be used when applying the formula.
NOTE: UNRCC, UCRCC and ALSC only apply to local and intraLATA toll call scenarios, so it's never necessary to convert access MOU in originating access DUF records to conversation MOU.
|
|
| back to top |
|
|
|
Objective 6: Calculate MOU totals for each per MOU rate element |
|
the UNE CLEC must first determine which per MOU rate elements apply in each call scenario. Then MOU totals, either alone or combined, are created to match sub-group categories on the bill. For example, TTSC (Transit Tandem Switching Charge) is billed in the following 3 tier sub-groups:
- Tier 1: ORIG LOCAL / ORIG IXC TOLL / TERM IXC TOLL
- Tier 2: ANALOG / CIRCUIT SWITCHED DATA / PACKET SWITCHED DATA
- Tier 3: DAY / EVENING / NIGHT or PEAK / OFF PEAK
|
|
| back to top |
|
|
|
Objective 7: Calculate call or query totals for each per call or query rate element |
|
To achieve objective 7, the UNE CLEC must first determine which per call or query rate elements apply in each call scenario. Then call totals are created to match sub-group categories on the bill. Most per call rate elements are grouped by originating NPA-NXX. Some have a single total per EOS.
Totals for per call or per query rate elements need not be split by time of day, because rates for these rate elements do not vary by time of day.
|
|
| back to top |
|
|
|
Objective 8: Calculate OWS totals for each per OWS rate element |
|
To achieve objective 8, the UNE CLEC must first determine which per OWS rate elements apply in each call scenario. Then OWS totals are created to match sub-group categories on the bill.
OWS are billed in rounded full minutes against a per minute rate equal to 60 times the tariffed per work second rate.
NOTE: Until the EMI record supports a field for operator work time it's not possible to verify the accuracy of the billing of per OWS rate elements against the DUF.
|
|
| back to top |
|
|
|
Objective 9: Reconcile DUF per EOS totals with bill per EOS totals |
|
To achieve objective 9, the CLEC must compare the DUF derived MOU total for each per MOU rate element sub-group, and the DUF derived call/query total for each per call/query rate element, with the equivalent total on the bill.
|
|
| back to top |
|
|
|
Objective 10: Verify accuracy of usage charges |
|
To achieve objective 10, the CLEC must refer to the applicable tariff or Verizon/CLEC contract for all UNE usage rates, and compare them to the rates indicated on the bill and to the totals after multiplying by MOU or number of calls/queries.
|
|
| back to top |
|
|
|
|
|
