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.
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.
SYSTEM AGENCY DATA A. As between the Parties, all data and information acquired, accessed, or made available to Grantee by, through, or on behalf of System Agency or System Agency contractors, including all electronic data generated, processed, transmitted, or stored by Grantee in the course of providing data processing services in connection with Xxxxxxx’s performance hereunder (the “System Agency Data”), is owned solely by System Agency.
Shift Exchanges In no event shall any overtime be payable as a result of employees voluntarily exchanging shifts.
Non-State Agency Authorized Users Authorized Users other than State Agencies are permitted to make purchases through state Centralized Contracts where permitted by law, the Contract or the Commissioner.
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.
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:
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.
Per-‐Registrar Transactions Report This report shall be compiled in a comma separated-‐value formatted file as specified in RFC 4180. The file shall be named “gTLD-‐transactions-‐yyyymm.csv”, where “gTLD” is the gTLD name; in case of an IDN-‐TLD, the A-‐label shall be used; “yyyymm” is the year and month being reported. The file shall contain the following fields per registrar: Field # Field name Description 01 registrar-‐name Registrar’s full corporate name as registered with IANA 02 iana-‐id For cases where the registry operator acts as registrar (i.e., without the use of an ICANN accredited registrar) 9999 should be used, otherwise the sponsoring Registrar IANA id should be used as specified in xxxx://xxx.xxxx.xxx/assignments/registrar-‐ids 03 total-‐domains total domain names under sponsorship in any EPP status but pendingCreate that have not been purged 04 total-‐nameservers total name servers (either host objects or name server hosts as domain name attributes) associated with domain names registered for the TLD in any EPP status but pendingCreate that have not been purged 05 net-‐adds-‐1-‐yr number of domains successfully registered (i.e., not in EPP pendingCreate status) with an initial term of one (1) year (and not deleted within the add grace period). A transaction must be reported in the month the add grace period ends.
Information Exchange As soon as reasonably practicable after the Effective Date, the Parties shall exchange information regarding the design and compatibility of the Interconnection Customer’s Interconnection Facilities and Participating TO’s Interconnection Facilities and compatibility of the Interconnection Facilities with the Participating TO’s Transmission System, and shall work diligently and in good faith to make any necessary design changes.
