Trunk Data Exchange Sample Clauses

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.
AutoNDA by SimpleDocs
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

Related to Trunk Data Exchange

  • Data Exchange Each Party shall furnish to the other Party real-time and forecasted data as required by ERCOT Requirements. The Parties will cooperate with one another in the analysis of disturbances to either the Plant or the TSP’s System by gathering and providing access to any information relating to any disturbance, including information from oscillography, protective relay targets, breaker operations, and sequence of events records.

  • Local Interconnection Data Exchange for Billing 7.7.1 There are certain types of calls or types of Interconnection that require exchange of Billing records between the Parties, including, for example, alternate billed and Toll Free Service calls. The Parties agree that all call types must be routed between the networks, accounted for, and settled among the Parties. Certain calls will be handled via the Parties' respective operator service platforms. The Parties agree to utilize, where possible and appropriate, existing accounting and settlement systems to xxxx, exchange records and settle revenue.

  • Shift Exchanges In no event shall any overtime be payable as a result of employees voluntarily exchanging shifts.

  • Shift Exchange The Employer and the Union agree that shift exchanges are a useful process to allow employees more flexibility and improved work/life balance. Employees within an institution who have the same job classification will be allowed to exchange full shifts for positions in which they are qualified. The shift exchange process will not be used to circumvent the bid system or the supervisory chain of command. Shift exchanges will be in accordance with the following:

  • Disturbance Analysis Data Exchange The Parties will cooperate with one another and the NYISO in the analysis of disturbances to either the Large Generating Facility or the New York State Transmission System by gathering and providing access to any information relating to any disturbance, including information from disturbance recording equipment, protective relay targets, breaker operations and sequence of events records, and any disturbance information required by Good Utility Practice.

  • Local Number Portability Database 10.6.1 The Permanent Number Portability (PNP) database supplies routing numbers for calls involving numbers that have been ported from one local service provider to another. BellSouth agrees to provide access to the PNP database at rates, terms and conditions as set forth by BellSouth and in accordance with an effective FCC or Commission directive.

  • Data Encryption Contractor must encrypt all State data at rest and in transit, in compliance with FIPS Publication 140-2 or applicable law, regulation or rule, whichever is a higher standard. All encryption keys must be unique to State data. Contractor will secure and protect all encryption keys to State data. Encryption keys to State data will only be accessed by Contractor as necessary for performance of this Contract.

  • Switched Exchange Access Service The offering of transmission and switching services for the purpose of the origination or termination of Toll Traffic. Switched Exchange Access Services include but may not be limited to: Feature Group A, Feature Group B, Feature Group D, 700 access, 800 access, 888 access and 900 access.

Time is Money Join Law Insider Premium to draft better contracts faster.