Frequency of Data Exchanges Sample Clauses

Frequency of Data Exchanges. Matching will be conducted when this agreement is effective and thereafter no less frequently than quarterly (anticipated to occur during the first year in November, February, May, and August). On a quarterly basis, one or more of the SPAAs may elect not to participate in a scheduled match.
Sample 1Sample 2Sample 3See All (5)
AutoNDA by SimpleDocs
Frequency of Data Exchanges. Matches will be conducted at least quarterly; during the first year, they are anticipated to occur in November, February, May, and August. PARIS has run on a quarterly basis since 1999; the dates of the matches are established each year. Each participating SPAA is informed of the dates and has the option to participate in each match. This approach enables States to operate more effectively depending on how they are organized and how much funding they have to dedicate to the project. It is expected that the option for a match will be provided six times during the initial 18-month term of the agreement. During the 12 month renewal period, if any, the option for a match would be provided four additional times.
Sample 1Sample 2Sample 3
Frequency of Data Exchanges. OCSE Responsibilities
Sample 1Sample 2Sample 3
Frequency of Data Exchanges. Subsection 453(j)(8) of the Social Security Act (42 U.S.C. § 653(j)(8)) requires comparison and disclosure to assist states to carry out their responsibilities under UC to the extent and with the frequency that the Secretary determines to be effective. The Secretary has determined that comparisons and disclosures at a frequency established by the state agency are effective in assisting states to carry out responsibilities under UC. The state agency may request weekly comparisons and disclosures of new hire and quarterly disclosures of wage information.
Sample 1
Frequency of Data Exchanges. Subsection 453(j)(3) of the Social Security Act (42 U.S.C. § 653(j)(3)) requires comparison and disclosure to assist states to carry out their responsibilities under TANF to the extent and with the frequency that the Secretary determines to be effective. The Secretary has determined that comparisons and disclosures at a frequency established by the state agency are effective in assisting states to carry out responsibilities under TANF. The state agency may request monthly comparisons and disclosures for comparison against the new hire file and quarterly for comparison with the quarterly wage and unemployment insurance files.
Sample 1

Related to Frequency of Data Exchanges

  • Frequency of Evaluations 36.2.1 Employee work performance will be evaluated during probationary and trial service periods and annually thereafter. If the supervisor identifies a performance concern during the evaluation period, the supervisor may provide feedback. The supervisor will provide written documentation to the employee with a copy kept in the supervisor’s working file.

  • Frequency of Evaluation Short form employees shall be evaluated one (1) time per year, which evaluation shall be completed no later than June 1.

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

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

  • Specific Order Processes and Requirements 1. Distributor will order Software from SAP using and filling out completely such forms and minimum order requirements as SAP may prescribe from time to time and must comply with any then-current order process for the specific Software product. Where applicable, Distributor agrees to use the electronic means provided by SAP for placing orders.

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

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

  • Service Order Process Requirements 53.5.1 CenturyLink will accept orders for As-Is Transfer of services from CenturyLink to CLEC where CenturyLink is the End User’s current local exchange carrier.

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

  • Other Procurement Procedures The following procurement methods may be used for the procurement of works and goods that the Bank agrees meets the requirements established in the provisions of Section III of the Procurement Policies:

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