Common use of Trunk Data Exchange Clause in Contracts

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. 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-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 Managementtwo

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 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-semi- annual basis upon request. Exchange of data on one-way groups is optional. 3.12. Network Management

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-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 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 Managementtwo

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-fifty- two (52) weeks per year basis. These reports shall be made available on a semi-semi- annual basis upon request. Exchange of data on one-way groups is optional. 3.12. Network Management

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-semi- annual basis upon request. Exchange of data on one-way groups is optional. 3.12. Network Management

Trunk Data Exchange. 3.11.1 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. 3.11.2 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 As an example, 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 basisbasis or similar report structure, as mutually agreed by the Parties. These reports shall be made available at a minimum on a semi-annual basis upon request. Exchange of data on one-way groups is optional. 3.12. Network Management.