Trunk Data Exchange. 65.9.1 Each Party agrees to service trunk groups to the blocking criteria in Section 59.2.3 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. 3.11.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.
3.11.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 (52) weeks per year basis. These reports shall be made available on a semi-annual basis upon request. Exchange of data on one-way groups is optional. 3.12. Network Management
Trunk Data Exchange. 7.1 A Trunk Group utilization report (TIKI) is available upon request. The report is provided in 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 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.
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 exchange of traffic data upon request. 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
Trunk Data Exchange. 74.13.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.
74.13.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
Trunk Data Exchange. 3.11.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.
3.11.2 Exchange of traffic data enables each Party to make accurate and independent assessments of trunk group service levels and requirements. Upon request of either Party the Parties agree to establish a timeline for implementing an exchange of traffic data. Implementation shall be such date as agreed upon, after the trunk groups begin passing live traffic. The traffic data to be exchanged will be as agreed by the Parties. These reports shall be made available on a semi-annual basis upon request. Exchange of data on one-way groups is optional. 3.12. Network Management
Trunk Data Exchange. 20.1 AT&T MICHIGAN shall provide Data Interexchange Carrier (DIXC) traffic data for all trunk groups terminating in Climax’s network.
20.2 The Parties agree to exchange traffic data on trunks and to implement such an exchange within three
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.
20.2 The Parties agree to exchange traffic data on trunks and to implement such an exchange within three (3) months of the date that trunking is established and the trunk groups begin passing live traffic, or another date as agreed to by the Parties. Exchange of traffic data will permit each company to have knowledge of the offered and overflow load at each end of the two-way trunk group, and thereby enable accurate and independent determination of performance levels and trunk requirements. The Parties agree to the electronic exchange of data. Parties agree to establish a timeline for implementing an exchange of traffic data utilitizing the DIXC process via network data mover (NDM)/FTP computer to computer File Transfer Process (FTP).
20.3 DIXC traffic data will include, but not be limited to, the following:
20.3.1 Usage (total usage measured in centum call seconds)
20.3.2 Peg Count (Peg count of originating call attempts including overflow)
20.3.3 Overflow (Peg count of originating call attempts failing to find an idle trunk)
20.3.4 Maintenance Usage (total maintenance usage measured in centum call seconds)
20.3.5 Maintenance Busy Counts (total count of trunks made maintenance busy)
20.4 DIXC traffic data shall be collected as follows:
20.4.1 Hourly on the clock hour
20.4.2 Twenty-four (24) hours per day (0000-2400)
20.4.3 Seven (7) days per week (including holidays)
20.4.4 Fifty-two (52) weeks per year
Trunk Data Exchange
