Trunk Data Exchange. 65.9.1 Each Party agrees to service trunk groups to the blocking criteria in Section 64.3.4 in a timely manner when trunk groups exceed measured blocking thresholds on an average time consistent busy hour for a twenty-one (21) Day study period. The Parties agree that twenty-one (21) Days is the study period duration objective unless mutually agreed otherwise. The study period will not include a holiday.
Trunk Data Exchange. 9.1 Each Party agrees to service trunk groups to the foregoing blocking criteria in a timely manner when trunk groups exceed measured blocking thresholds on an average bouncing busy hour for a twenty (20) day study period. The Parties agree that twenty (20) days is the study period duration objective. However, a study period on occasion may be less than twenty (20) days but at minimum must be at least three (3) business days to be utilized for engineering purposes, although with less statistical confidence.
Trunk Data Exchange. 8.1 A Trunk Group utilization report (TIKI) is available upon request. The report is provided in MS-Excel format.
Trunk Data Exchange. 20.1 MCIm has requested and AT&T ILLINOIS shall provide Data Interexchange Carrier (DIXC) traffic data for all trunk groups terminating in MCIm’s network. A trunk group utilization report (TIKI) is also available, upon request. The TIKI report is provided in a MS-Excel format.
Trunk Data Exchange. 9.1 Each Party agrees to service trunk groups to the foregoing blocking criteria in a timely manner when trunk groups exceed measured blocking thresholds on an average time consistent busy hour for a twenty-one (21) day study period. The Parties agree that twenty-one (21) days is the study period duration objective. However, a study period on occasion may be less than twenty-one (21) days but at minimum must be at least three (3) business days to be utilized for engineering purposes, although with less statistical confidence. 9.2 Exchange of traffic data enables each Party to make accurate and independent assessments of trunk group service levels and requirements. Parties agree to establish a timeline for implementing an exchange of traffic data. Implementation shall be within three (3) months of the date, or such date as agreed upon, that the trunk groups begin passing live traffic. The traffic data to be exchanged will be the Originating Attempt Peg Count, Usage (measured in Hundred Call Seconds), Overflow Peg Count, and Maintenance Usage (measured in Hundred Call Seconds) on a seven (7) day per week, twenty-four (24) hour per day, fifty-two
