Carrier-to-Carrier Guidelines Ver.17 - Verizon

More documents

Recommendations

Info

Function:OR-10 PON Notifier Exception Resolution TimelinessDefinition:The OR-10 sub-metrics measure the percent of Netlink EDI PON Notifier Exceptions resolved withinthree (3) business days and ten (10) business days from the day of receipt of the completed PON NotifierException trouble ticket template with the PONs in question enumerated with the appropriateidentification.The elapsed time begins with receipt at the Verizon Wholesale Customer Care Center of a completedPON Notifier Exception trouble ticket template with the PONs in question enumerated with theappropriate identification for EDI notifiers (i.e., order acknowledgement (ACK), order confirmation (LSC),provisioning completion (PCN), or billing completion (BCN) notices).PON Notifier Exceptions received after 5:00PM will be considered received the next business day.The PON Notifier Exception is considered resolved when Verizon has either:1. Sent or resent the requested notifier or higher notifier. If the notifier cannot be resent due to CLECsystem availability or capacity, then the PON Notifier Exception shall be considered resolved whenthe resend was attempted as demonstrated in Verizon’s log files (copies of these files will beavailable to CLECs on request).2. Requested the CLEC to resubmit the PON if no Verizon notifiers have been generated.3. Completed the investigation showing that the next action is a CLEC action and that the CLEC hasbeen sent or resent the notifier for the action required (E.g. Query, Jeopardy), or Status File forDuplicate, earlier or later version of PON has been worked, PON previously cancelled, invalid PONnumber.4. Completed work that will allow the PON to proceed to the next step in the business process, andsent the appropriate notifier to the CLEC.5. Notified the CLEC that the Confirmed Due Date plus the notifier production interval has not yetpassed for requested PON Notifier (PCNs, and BCNs) and provided the current work status of thePON (i.e. Provisioning Completed, Notifier not yet produced). For PCNs and BCNs, Trouble Ticketsare not to be initiated prior to or on the Confirmed Due Date; any Trouble Ticket initiated prior to theConfirmed Due Date is automatically considered resolved when the CLEC is provided with electronicnotification that the initiation date is prior to the Confirmed Due Date.CLEC notification for items 2, 3, 4, and 5, will be accomplished via a daily file sent from Verizon to theindividual CLEC. This notification file will be sent every day by 5:00PM. For the purposes of this metricthe PON Notifier Exception(s) trouble ticket templates for Acknowledgements must be submitted withinfive (5) business days of the PON sent date. PON Notifier Exceptions for confirmations must be reportedwithin 30 business days of the PON sent date. PON Notifier Exceptions for PCNs, and BCNs must bereported to Verizon within 30 business days of the PON Confirmed Due Date.VZEAST201003-NY200909Version 17.060
Exclusions:• Non NetLink EDI PON Exception Notifier Trouble Tickets.• Any request for Notifier for orders due/complete more than 30 business days old.• Orders for Products/Services that are not designed to produce the requested notifier (e.g. LIDB).Performance Standard:OR-10-01: 95% resolved within three (3) business days.OR-10-02: 99% resolved within ten (10) business days.Report DimensionsCompany:• CLEC Aggregate• CLEC SpecificGeography:• State SpecificThese sub-metrics are reported at a statespecific level.Sub-MetricsOR-10-01 % of PON Exceptions Resolved Within Three (3) Business DaysProducts for All combinedOR-10-01 andOR-10-02Calculation Numerator DenominatorNumber of PON Notifier Exceptionsresolved within three (3) business days.Total number of PON Notifier Exceptionsresolved in Partner Solutions CustomerCare (PSCC) in the reporting month lessresolved PON Notifier Exceptions that wereincluded as unresolved PON NotifierExceptions in the previous month’sdenominator for metric OR-10-02.OR-10-02 % of PON Exceptions Resolved Within ten (10) Business DaysCalculation Numerator DenominatorNumber of PON Notifier Exceptionsresolved within ten (10) business days.Total Number of PON Notifier Exceptionsresolved in Partner Solutions CustomerCare (PSCC) in the reporting month plusunresolved PON Notifier Exceptions greaterthan ten (10) business days.VZEAST201003-NY200909Version 17.061
Page 1:
Carrier-to-Carrier GuidelinesPerfor
Page 4 and 5:
PR-6 INSTALLATION QUALITY..........
Page 6 and 7:
GE-2-01 % OF ACCESS REQUEST RESPONS
Page 8 and 9:
INTRODUCTIONThis section of the Ver
Page 10 and 11: URL ReferencesVerizon references UR
Page 12 and 13: GENERAL NOTESVerizon North includes
Page 14 and 15: Retail Analog Compare Table, contin
Page 16 and 17: Sub-CodeProduct2200 Resale Specials
Page 18 and 19: Sub-Code6000 Systems MetricsProduct
Page 20 and 21: Function:PO-1 Response Time OSS Pre
Page 22 and 23: Formula:∑ Response Times for each
Page 24 and 25: Function:PO-2 OSS Interface Availab
Page 26 and 27: PO-2 Formula:(Number of hours sched
Page 28 and 29: Report DimensionsCompany:• CLEC A
Page 30 and 31: Change Management Notifications sen
Page 32 and 33: Function:PO-6 Software ValidationDe
Page 34 and 35: Report Dimensions:Company:• CLEC
Page 36 and 37: Section 2Ordering Performance(OR)OR
Page 38 and 39: OR-1 Definition, continued:Notes:(1
Page 42 and 43: Sub-Metrics OR-1 Order Confirmation
Page 44 and 45: Function:OR-2 Reject TimelinessDefi
Page 46 and 47: Performance Standard - Reject Timel
Page 48 and 49: Sub-Metrics - OR-2 Reject Timelines
Page 50 and 51: Function:Definition:Exclusions:•P
Page 52 and 53: Sub-Metrics Timeliness of Completio
Page 54 and 55: Function:OR-6 Order AccuracyDefinit
Page 56 and 57: OR-6-04 % Accuracy - Directory List
Page 58 and 59: Function:Definition:Exclusions:Repo
Page 62 and 63: Function:OR-11 Timeliness of Provid
Page 64 and 65: Function:OR-13 % of Large Job Hot C
Page 66 and 67: Function:PR-1 Average Interval Offe
Page 68 and 69: Sub-Metrics - PR-1 Average Interval
Page 70 and 71: Function:PR-3 Completed within Spec
Page 72 and 73: Sub-Metrics PR-3 % Completed within
Page 76 and 77: Sub-Metrics (continued) PR-4 Missed
Page 78 and 79: Function:PR-5 Facility Missed Order
Page 80 and 81: Sub-Metrics (continued) Facility Mi
Page 82 and 83: Sub-MetricsPR-6-01 % Installation T
Page 84 and 85: Sub-MetricsPR-8-01 Percent Open Ord
Page 86 and 87: Definition.Note: For all types of H
Page 88 and 89: Sub-Metrics - Hot Cut Loops, contin
Page 90 and 91: Function:MR-1 Response Time OSS Mai
Page 92 and 93: Sub-MetricsMR-1-01Average Response
Page 94 and 95: Function:MR-2 Trouble Report RateDe
Page 96 and 97: •MR-2-05Products% CPE/TOK/FOK/NPC
Page 98 and 99: Sub-MetricsMR-3-01 % Missed Repair
Page 100 and 101: Exclusions:• Troubles reported on
Page 102 and 103: Sub-Metrics - Trouble Duration Inte
Page 104 and 105: Function:MR-5 Repeat Trouble Report
Page 106 and 107: Section 5Network Performance(NP)NP-
Page 108 and 109: Report Dimensions - NP-1 Percent Fi
Page 110 and 111:
Report Dimensions:Company:• CLEC
Page 112:
Function:NP-6 NXX Updates (Applicab
Page 115 and 116:
Function:BI-2 Timeliness of Carrier
Page 117 and 118:
Definition, continuedClosure• A c
Page 119 and 120:
Function:BI - 4 DUF Accuracy (Appli
Page 121 and 122:
Function:BI - 6 Completeness of Usa
Page 123 and 124:
Function:BI - 8 Non-Recurring Charg
Page 125 and 126:
Section 7Operator Services & Direct
Page 127 and 128:
Function:OD-3 DA Database Update Ac
Page 129 and 130:
General (GE)Function:GE-1 Directory
Page 131 and 132:
Function:GE-3 Bona Fide Request Res
Page 133 and 134:
Report Dimensions:Company:• CLEC
Page 135 and 136:
GlossaryApplication DateASRVZ Admin
Page 137 and 138:
Cut-Over WindowDedicated FinalTrunk
Page 139 and 140:
2-Wire Digital This service provide
Page 141 and 142:
RejectRun ClockSegmentSOPSpecial Se
Page 143 and 144:
Product identification descriptions
Page 145:
Implementation process for the East
show all

Carrier-to-Carrier Guidelines Ver.17 - Verizon

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?