Frequency of Data Exchange Sample Clauses

Frequency of Data Exchange. The frequency of the data exchange will be real-time, event based. Whenever the user clicks on any link or action on the Efiling portal or bank website, respective API of the Efiling or Bank gets invoked and synchronous response is received.
AutoNDA by SimpleDocs
Frequency of Data Exchange. The exchange of CSC demographic information and Proxy Academic information will occur continuously using the procedures described in this Agreement.
Frequency of Data Exchange. Identifier User requirement Remarks UR DAEX 1 The data provided by „Export/Exit” country shall be available as defined in the SLA. UR DAEX 2 The data exchange should not disrupt the work of Customs transaction systems. to be defined at national level Table 14: Frequency of data exchange
Frequency of Data Exchange. Repetitive: DOL will provide Data to Contractor weekly (Or additional dates upon request, additional fees apply).

Related to Frequency of Data Exchange

  • Frequency of Evaluation 1. Probationary employees shall be evaluated at least once during their probationary period.

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

  • FORMAT AND CONTENT FOR REGISTRY OPERATOR MONTHLY REPORTING Registry Operator shall provide one set of monthly reports per gTLD, using the API described in draft-­‐xxxxxx-­‐icann-­‐registry-­‐interfaces, see Specification 2, Part A, Section 9, reference 5, with the following content. ICANN may request in the future that the reports be delivered by other means and using other formats. ICANN will use reasonable commercial efforts to preserve the confidentiality of the information reported until three (3) months after the end of the month to which the reports relate. Unless set forth in this Specification 3, any reference to a specific time refers to Coordinated Universal Time (UTC). Monthly reports shall consist of data that reflects the state of the registry at the end of the month (UTC).

  • SYSTEM AGENCY DATA A. As between the Parties, all data and information acquired, accessed, or made available to Performing Agency by, through, or on behalf of System Agency or System Agency contractors, including all electronic data generated, processed, transmitted, or stored by Performing Agency in the course of providing data processing services in connection with Performing Agency’s performance hereunder (the “System Agency Data”), is owned solely by System Agency.

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

  • Pricing for Registry Services (a) With respect to initial domain name registrations, Registry Operator shall provide ICANN and each ICANN accredited registrar that has executed the registry-­‐registrar agreement for the TLD advance written notice of any price increase (including as a result of the elimination of any refunds, rebates, discounts, product tying or other programs which had the effect of reducing the price charged to registrars, unless such refunds, rebates, discounts, product tying or other programs are of a limited duration that is clearly and conspicuously disclosed to the registrar when offered) of no less than thirty (30) calendar days. Registry Operator shall offer registrars the option to obtain initial domain name registrations for periods of one (1) to ten (10) years at the discretion of the registrar, but no greater than ten (10) years.

  • Monthly Data Download Not later than fifteen (15) days after the end of each month, beginning with the month in which the Commencement Date occurs and ending with the Final Shared-Loss Month, Assuming Institution shall provide Receiver:

  • Product Changes Vocera shall have the right, in its absolute discretion, without liability to End User, to update to provide new functionality or otherwise change the design of any Product or to discontinue the manufacture or sale of any Product. Vocera shall notify End User at least 90 days prior to the delivery of any Product which incorporates a change that adversely affects form, fit or function (“Material Change”). Vocera shall also notify End User at least 90 days prior to the discontinuance of manufacture of any Product. Notification will be made as soon as reasonably practical for changes associated with regulatory or health and safety issues.

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

  • Contract Changes Changes may not be made in the terms and conditions of this contract without the agreement and written permission of the Director of Housing.

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