CFMA Resolution Sample Clauses

CFMA Resolution. If the LHIN provides notice under subsection 24(1) of the CFMA, then the resolution of the issue or dispute will thereafter be governed by the dispute resolution provisions of the CFMA.
AutoNDA by SimpleDocs
CFMA Resolution. If the MOHLTC provides notice under subsection 24(1) of the CFMA, then the resolution of the issue or dispute will thereafter be governed by the dispute resolution provisions of the CFMA.

Related to CFMA Resolution

  • Problem Resolution The parties shall meet and attempt to resolve all disputes and differences that may arise between the parties hereto concerning construction, interpretation, performance, operations, or breach of the matters referred to in this Agreement prior to seeking any legal remedy.

  • Error Resolution If you believe that you did not authorize an electronic fund transaction, if you need a copy of a transaction receipt from a Merchant, if you think your statement or receipt is wrong, or if you need more information about a transaction listed on the statement or receipt, you should call or write us at the phone number or address shown at the end of these Regulatory Disclosures under “UMB Contact Information” You should report errors no later than sixty (60) days after information is available to you on your periodic statement or in your electronic statement information concerning the transaction that you believe to be in error or which you believe is a problem. Include the following information: (a) your name and your HSA Deposit Account number; (b) describe the error or the transaction you are unsure about and explain as clearly as you can why you believe it is an error or why you need more information; and (c) the dollar amount of the suspected error. If you tell us orally, we may require that you send us your complaint or questions in writing within ten (10) business days. We will determine whether an error occurred within ten (10) business days after we hear from you and will correct any error promptly. If we need more time, however, we may take up to 45 days to investigate your complaint or question. If we decide to do this, we will credit your account within ten (10) business days for the amount you think is in error so that you will have the use of the money during the time it takes us to complete our investigation. If we ask you to put your complaint or question in writing and we do not receive it within ten (10) business days, we may not credit your account. For errors involving new accounts, point-of-sale, or foreign-initiated transactions, we may take up to 90 days to investigate your complaint or question. For new accounts, we may take up to 20 business days to credit your account for the amount you think is in error. We will tell you the results within three (3) business days after completing our investigation. If we decide that there was no error, we will send you a written explanation. You may ask for copies of the documents that we used in our investigation.

  • Issue Resolution For resolution of issues between CONTRACTOR and ADMINISTRATOR with respect to the 17 implementation and operation of this Agreement or COUNTY’s policies and procedures regarding 18 services described herein, the following sequential steps shall apply:

  • DNS resolution RTT Refers to either “UDP DNS resolution RTT” or “TCP DNS resolution RTT”.

  • Formal Resolution 1. Service Provider or TJJD staff who wish to submit problems for resolution may do so in writing, including all relevant information and a recommended resolution (Statement of Problem). 2. The Statement of Problem will be submitted to the designated contact unless the problem specifically involves the designated contact, in which case, it will be submitted to the designated contact’s supervisor. 3. Problems are to be addressed within ten (10) working days; a written decision will be sent to the individual or program that submitted it, with copies retained by the designated contact and the designated contact’s supervisor.

  • Corporate Resolution As of the date hereof, Seller shall have received from Purchaser a certified copy of its corporate resolution approving the execution and delivery of this Agreement and the consummation of the transactions contemplated hereby, together with such other certificates of incumbency and other evidences of corporate authority as Seller or its counsel may reasonably request.

  • UDP DNS resolution RTT Refers to the RTT of the sequence of two packets, the UDP DNS query and the corresponding UDP DNS response. If the RTT is 5 times greater than the time specified in the relevant SLR, the RTT will be considered undefined.

  • TCP DNS resolution RTT Refers to the RTT of the sequence of packets from the start of the TCP connection to its end, including the reception of the DNS response for only one DNS query. If the RTT is 5 times greater than the time specified in the relevant SLR, the RTT will be considered undefined.

  • Disputes Resolution It is the intent of the parties to communicate on a regular basis in a positive and effective manner. The parties agree to communicate areas of concern as they arise and to address those concerns in a professional manner. Any disputes between the Commission and the School which arise under, or are by virtue of, this Contract and which are not resolved by mutual agreement, shall be decided by the full Commission in writing, within 90 calendar days after a written request by the School for a final decision concerning the dispute; provided that where a disputes resolution process is defined for a particular program area (e.g., IDEA, Section 504, etc.), the Parties shall comply with the process for that particular program area; and further provided that the parties may mutually agree to utilize the services of a third-party facilitator to reach a mutual agreement prior to decision by the full Commission. Subject to the availability of an appeal under Ch. 302D, HRS, or BOE administrative rules or procedures, any such decision by the full Commission shall be final and conclusive.

  • DNSSEC proper resolution There is a valid DNSSEC chain of trust from the root trust anchor to a particular domain name, e.g., a TLD, a domain name registered under a TLD, etc.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!