Bruincard System Problem Resolution
Bruincard System Problem Resolution Sample Clauses
Related to Bruincard System Problem 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.
Grievance Resolution If a grievance is resolved at Step 2 or 3 in the procedure as provided herein, the grievant concerned shall indicate acceptance of the resolution by affixing his/her signature in the appropriate space indicated. If the employee has been represented by the Union at the Step of the procedure at which a resolution is reached, the Union representative shall also sign the appropriate document acknowledging that the employee has accepted the resolution. Decisions on grievances where an employee represents him/herself shall not be considered precedent setting or binding with regard to any future grievances filed with respect to the same or similar matters.
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.
DNS resolution RTT Refers to either “UDP DNS resolution RTT” or “TCP DNS resolution RTT”.
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.
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.
Recognition of the U.S. Special Resolution Regimes (i) In the event that any Underwriter that is a Covered Entity becomes subject to a proceeding under a U.S. Special Resolution Regime, the transfer from such Underwriter of this Agreement, and any interest and obligation in or under this Agreement, will be effective to the same extent as the transfer would be effective under the U.S. Special Resolution Regime if this Agreement, and any such interest and obligation, were governed by the laws of the United States or a state of the United States. (ii) In the event that any Underwriter that is a Covered Entity or a BHC Act Affiliate of such Underwriter becomes subject to a proceeding under a U.S. Special Resolution Regime, Default Rights under this Agreement that may be exercised against such Underwriter are permitted to be exercised to no greater extent than such Default Rights could be exercised under the U.S. Special Resolution Regime if this Agreement were governed by the laws of the United States or a state of the United States. As used in this Section 16(e):
Conflict Resolution The Parties agree to resolve issues that may arise in the course of this partnership and shall act reasonably and in good faith in the event a conflict or disagreement should arise in the interpretation or implementation of the obligation, terms, and/or responsibilities of the Parties to this Agreement. Throughout the conflict resolution process it is important to balance the need to be responsive to the District’s instructional needs as well as the College’s responsibility to provide a quality dual credit program while also maintaining accreditation. Conflicts should be resolved at the lowest level possible with an understanding that, if no agreement is reached, there is a procedure for advancing the conflict through each Party’s organization. The key approach will be to maintain communications with early discussion sought on issues/conflicts and solutions summarized in writing after each discussion. In order to be collaborative, the College must be able to communicate with the administrators on campus in which the dual credit students/programs are present. Each Party shall designate an administrative liaison for the purpose of resolving concerns at both the campus (liaison must be Principal or other designated campus administrator) and College level (Director, Dual Credit Programs). If a resolution is not found at that initial level, the conflict resolution process shall move to a designated District level administrator (such as a District Director or Assistant Superintendent of Instruction) and a designated College level administrator (Director, Prospective Student Relations and Enrollment Management). If the conflict continues then the process shall proceed to the District Superintendent and the Vice Chancellor, Student Affairs of the College. If a resolution is not found through those initial levels, a request may be made that the matter be handled through the Parties’ respective legal counsel.
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.
