Breach, and Compliance Sample Clauses

Breach, and Compliance. Any violation of the terms of this Agreement shall be grounds for immediate termination of this Agreement. AHRQ shall determine whether a data recipient has violated any term of the Agreement. AHRQ shall determine what actions, if any, are necessary to remedy a violation of this Agreement, and the data recipient(s) shall comply with pertinent instructions from AHRQ. Actions taken by AHRQ may include but not be limited to providing notice of the termination or violation to affected parties and prohibiting data recipient(s) from accessing HCUP data in the future.
AutoNDA by SimpleDocs
Breach, and Compliance. In the event of non-compliance with the terms of this Agreement, written notice of the same may be delivered to the Developer by the City and, if the Developer has not corrected such non-compliance within 30 days after receipt of such notice, the City may institute such proceedings as may be necessary or desirable in its opinion to cure and remedy such default, including but not limited to the remedy of specific performance; provided, if such non- compliance cannot be cured within such 30-day period, then the Developer shall be afforded additional time to cure such non-compliance so long as the Developer, within such 30-day period, commences the curing of such failure and diligently in good faith prosecutes the same to completion and furnishes evidence thereof to the City. Notwithstanding the foregoing, the City’s sole remedy for the Developer’s
Breach, and Compliance. Any violation of the terms of this Agreement shall be grounds for immediate termination of this Agreement. AHRQ shall determine whether a data recipient has violated any term of the Agreement. AHRQ shall determine what actions, if any, are necessary to remedy a violation of this Agreement, and the data recipient(s) shall comply with pertinent instructions from AHRQ. Actions taken by AHRQ may include but not be limited to providing notice of the termination or violation to affected parties and prohibiting data recipient(s) from accessing SyH-DR in the future. In the event AHRQ terminates this Agreement due to a violation or finds the data recipient(s) to be in violation of this Agreement, AHRQ may direct that the undersigned data recipient(s) immediately return all copies of the SyH-DR to AHRQ or its designee without refund of purchase fees.

Related to Breach, and Compliance

  • Performance and Compliance Purchaser shall have performed all of the covenants and complied, in all material respects, with all the provisions required by this Agreement to be performed or complied with by it on or before the Closing.

  • Litigation and Compliance ‌ (a) Except as disclosed in the Disclosure Letter, to the best of GLC’s knowledge, there are no actions, suits, claims or proceedings, whether in equity or at law or, any Governmental investigations pending or threatened: (i) against or affecting GLC or the GLC Subsidiaries or with respect to or affecting any asset or property owned, leased or used by GLC or the GLC Subsidiaries; or (ii) which question or challenge the validity of this Agreement, or the Amalgamation or any action taken or to be taken pursuant to this Agreement, or the Amalgamation; nor is GLC aware of any basis for any such action, suit, claim, proceeding or investigation. (b) There is not outstanding against GLC or the GLC Subsidiaries, any judgment, decree, injunction, rule, order or award of any court, Governmental entity, commission, board, bureau, agency, or arbitrator. (c) Each of GLC and the GLC Subsidiaries has conducted and is conducting its business in compliance with, and is not in default or violation under, and has not received notice asserting the existence of any default or violation under, any Law applicable to its business or operations, except for non-compliance, defaults and violations which would not, in the aggregate, have a Material Adverse Effect on GLC. (d) Neither GLC nor any of its assets, including the GLC Subsidiaries, is subject to any judgment, order or decree entered in any lawsuit or proceeding which has had, or which is reasonably likely to have, a Material Adverse Effect on GLC or which is reasonably likely to prevent GLC from performing its obligations under this Agreement. (e) To the best knowledge of GLC, each of GLC and the GLC Subsidiaries has duly filed or made all reports and returns required to be filed by it with any Government and has obtained all permits, licenses, consents, approvals, certificates, registrations and authorizations (whether Governmental, regulatory or otherwise) which are required in connection with its business and operations, except where the failure to do so has not had and will not have a Material Adverse Effect on GLC.

  • OSHA Compliance To the extent applicable to the services to be performed under this Agreement, Contractor represents and warrants, that all articles and services furnished under this Agreement meet or exceed the safety standards established and promulgated under the Federal Occupational Safety and Health Law (Public Law 91-596) and its regulations in effect or proposed as of the date of this Agreement.

  • INDEMNITY/COMPLIANCE 4.1 A-E shall indemnify, defend with counsel approved in writing by COUNTY, and hold harmless, the COUNTY, its agents, officers, and employees from employer sanctions and any other liability which may be assessed against A-E or the COUNTY or both in connection with any alleged violation of any Federal or State statutes or regulations pertaining to the eligibility for employment of any persons performing work under this CONTRACT. 4.2 All PROJECTS/SERVICES submitted by A-E shall be complete and shall be carefully checked prior to submission. A-E understands that COUNTY's checking is discretionary, and A-E shall not assume that COUNTY will discover errors and/or omissions. If COUNTY discovers any errors or omissions prior to approving A-E's PROJECTS/SERVICES, the PROJECTS/SERVICES will be returned to A-E for correction. Should COUNTY or others discover errors or omissions in the work submitted by A-E after COUNTY's approval thereof, COUNTY's approval of A-E's PROJECTS/SERVICES shall not be used as a defense by A-E.

  • FERPA Compliance In connection with all FERPA Records that Contractor may create, receive or maintain on behalf of University pursuant to the Underlying Agreement, Contractor is designated as a University Official with a legitimate educational interest in and with respect to such FERPA Records, only to the extent to which Contractor (a) is required to create, receive or maintain FERPA Records to carry out the Underlying Agreement, and (b) understands and agrees to all of the following terms and conditions without reservation:

  • CEQA Compliance The District has complied with all assessment requirements imposed upon it by the California Environmental Quality Act (Public Resource Code Section 21000 et seq. (“CEQA”) in connection with the Project, and no further environmental review of the Project is necessary pursuant to CEQA before the construction of the Project may commence.

  • Labor Compliance Contractor shall perform the Work of the Project while complying with all the applicable regulations, including section 16000, et seq., of Title 8 of the California Code of Regulations and is subject to labor compliance monitoring and enforcement by the Department of Industrial Relations.

  • ETHICS COMPLIANCE All Bidders/Contractors and their employees must comply with the requirements of Sections 73 and 74 of the Public Officers Law, other State codes, rules, regulations and executive orders establishing ethical standards for the conduct of business with New York State. In signing the Bid, Bidder certifies full compliance with those provisions for any present or future dealings, transactions, sales, contracts, services, offers, relationships, etc., involving New York State and/or its employees. Failure to comply with those provisions may result in disqualification from the Bidding process, termination of contract, and/or other civil or criminal proceedings as required by law.

  • PCI Compliance A. The Acquiring Bank will provide The Merchant with appropriate training on PCI PED and/or DSS rules and regulations in respect of The Merchants obligations. Initial training will be provided and at appropriate intervals as and when relevant changes are made to such rules and regulations. B. The Acquiring Bank will ensure that The Merchant is kept informed of any relevant new, or changes to, PCI PED and/or DSS compliance rules and regulations. C. The Merchant will comply with PCI PED and/or DSS, and resulting obligations, in respect of establishing, and maintaining, the required security controls. D. The Merchant will ensure that all its appropriate staff (existing and new) are knowledgeable in their responsibilities with respect to PCI PED and/or DSS compliance. E. The Merchant must be able to demonstrate compliance with PCI PED and/or DSS and maintain measures necessary to successfully pass regular compliance certification checks. F. The Merchant will notify The Acquiring Bank immediately should it become evident that data security standards have been compromised. The Merchant will also provide all assistance necessary to assist The Acquiring Bank and its agents to investigate and obtain any required evidence of a security breach. G. The Merchant hereby agrees and undertakes to fully indemnify The Acquiring Bank from and against all actions, claims, losses, charges, costs and damages which The Acquiring Bank may suffer or incur as a result of The Merchants failure to comply with PCI PED and/or DSS. H. Further to the conditions set out in Section 34 below, The Acquiring Bank reserves the right to terminate this agreement with The Merchant if The Merchant: i. Refuses to accept, or commence, any remedial action(s) required under its obligation to PCI PED and/or DSS. ii. Fails to maintain its PCI PED and/or DSS obligations and/or consistently fails compliance certification checks. iii. Receives continuing penalties Fraud notifications or alerts of in any case where the Acquiring bank may be asked by the schemes to take action against the Merchant. اهيلع ةقداصملا تمت دق هنأ نم ةيلمع يأ ذيفنت دعب دكأتلا رجاتلا ىلع بجي .10 لمحتب هرارقإ متو ةقاطبلا لماح ةطساوب بولطملا وحنلا ىلعو ةرشابم .ةيلمعلا كلت ذيفنت نع هتيلوؤسم لماك يأ تحت ةيلمع نم رثكأ ىلإ ةيلمعلا ةميق ميسقتب موقي لاأب رجاتلا دهعتي .11 لاير )500( ةميقب نيتيلمع ذفني نأ لاثملا ليبس ىلعف ،قلاطلإا ىلع فرظ ةعباتلا عفدلا ةقاطب سفن مادختساب لاير )1000( يلامجلإا اهغلبم عئاضبل اذه ربتعي ثيحب ؛ىرخأ عفد تاقاطب ةيأ وأ تاعوفدملل ةيدوعسلا ةكبشلل ءاغلإ و زاهجلا فاقيا ةلاحلا هذه يف كنبلل قحيو ،اًمامت ًاروظحم فرصتلا .ةيقافتلاا ةكبشلا ةقاطبب لقأ وأ رثكأ وأ لايرب ةرركم تايلمع ءارجإ رجاتلل قحي لا .12 غلابم وأ تايلمع ددع قيقحت ضرغب هب ةصاخلا نامتئلاا ةقاطب وأ ةيدوعسلا ءاغلإ و زاهجلا فاقيا كنبلل قحيو .هيلع ةررقملا موسرلا عفد بنجتل تايلمع .رجاتلا باسح نم ةررقملا موسرلا مصخ يف قحلاب ظافتحلاا عم ةيقافتلاا لمحُي نل هلاعأ ةحضوملا تامازتللااو تاءارجلإاب ديقتلا مدعو هقافخإ نأ رجاتلا رقي وأ فيلاكت وأ تابلاطم وأ ىوعد ةيأ نع اهريغ وأ تناك ةينوناق ،ةيلوؤسم ةيأ كنبلا ةراسخ وأ ةيمكارتلا رارضلأا وأ رئاسخلا كلذ يف امب رئاسخ وأ رارضأ وأ فيراصم مازتللااب رجاتلا للاخإ ببسب رجاتلا كنب اهدبكتي وأ اهل ضرعتي دق يتلا ،حابرلأا مدع ببسب ركذ امم يلأ رجاتلا كنب ضرعت لاح يفو .ةدراولا تابلطتملاو تاميلعتلاب ىوعد نم هيلع بترتي دق ام عيمج رجاتلا لمحتي ،ةروكذملا تاءارجلإاب رجاتلا مازتلا مدع ةجيتن رجاتلا كنب قحلت دق رئاسخ وأ رارضأ وأ فيراصم وأ فيلاكت وأ تابلاطم وأ .تاءارجلإاو طورشلاو تابلطتملا هذهب رجاتلا مازتلا عفدلا تاقاطب ةعانص رايعم عم قفاوتلا .9 PCI Compliance مادختساب ةصاخلا دعاوقلا ىلع بسانملا بيردتلا رجاتلل رجاتلا كنب مدقي .أ ،عفدلا تاقاطب ةعانصب قلعتت يتلاو ةيرسلا ةيصخشلا ماقرلأا لاخدإ زاهج تامازتلاب قلعتي اميف عفدلا تاقاطب ةعانص تانايب ةيامح رايعم ىلع اًضيأو تارييغت يأ ىلع وأ ديدج وه ام ىلع رجاتلا علاطإ ماود نم رجاتلا كنب دكأتي .ب ماقرلأا لاخدإ زاهج مادختساب ةصاخلا مازتللاا دعاوقو تاعيرشتلاب ةقلاع تاذ تانايب ةيامح رايعمب وأ ،عفدلا تاقاطبب قلعتي ام لك وأ ةيرسلا ةيصخشلا .عفدلا تاقاطب ةعانص ،عفدلا تاقاطبل ةيرسلا ةيصخشلا ماقرلأا لاخدإ ئدابمو ريياعمب رجاتلا مزتلي .ج قلعتي اميف ةرداصلا اهتاعيرشتو ،عفدلا تاقاطب تانايب نمأ ريياعمب اًضيأو .ةبولطملا ةيامحلا طباوض قيبطتو سيسأتب )نيدجتسملاو نييلاحلا( نيصتخملا نيفظوملا علاطإ نم رجاتلا دكأتي .د ةيصخشلا ماقرلأا لاخدإب ةصاخلا مازتللاا دعاوقب قلعتي اميف مهتايلوؤسمب .عفدلا تاقاطب تانايب نمأ ريياعمو ،عفدلا تاقاطبل ةيرسلا ةيصخشلا ماقرلأا لاخدإب ةصاخلا مازتللاا دعاوق حضوي نأ رجاتلا ىلع بجي .ـه ةظفاحملاو ،عفدلا تاقاطب تانايب نمأ ريياعم كلذكو عفدلا تاقاطبل ةيرسلا مازتللاا ىدمل ةيرودلا تارابتخلاا ةداهش زايتجلا ةيرورضلا ريياعملا ىلع .حاجنب ريياعم كاهتنا نم ققحتلا روف رجاتلا كنب راعشإب رجاتلا موقي نأ بجي .و كنب ةدعاسمل يرورض وه ام لك ميدقت رجاتلا ىلع بجي اًضيأو ،ةيامحلا ةبولطملا نيهاربلاو ةلدلأا يف قيقحتلا نم نيصتخملا هيفظومو رجاتلا .ةيامحلا قارتخا تابثلإ رجاتلا كنبل ةلماكلا ةيامحلاب ةيقافتلاا هذه بجومب رجاتلا مزتليو دهعتي .ز تابلاطم وأ ىوعد ةيأ نع ،اهريغ وأ تناك ةينوناق ،ةيلوؤسم ةيأ هليمحت مدعو رارضلأا وأ رئاسخلا كلذ يف امب رئاسخ وأ رارضأ وأ فيراصم وأ فيلاكت وأ ببسب رجاتلا كنب اهدبكتي وأ اهل ضرعتي دق يتلا ،حابرلأا ةراسخ وأ ةيمكارتلا كنب ظفتحي ،هاندأ 34 مقر ةداملا يف اهعضو مت يتلا طورشلا ىلإ ةفاضإ .ح :يتلآاب رجاتلا مايق ةلاح يف رجاتلا عم ةيقافتلاا هذه ءاهنإ قحب رجاتلا هتامازتلا هيلع هيلمت بولطم يزارتحا ءارجإ يأ ذاختا وأ لوبق هضفر .i وأ عفدلا تاقاطبل ةيرسلا ةيصخشلا ماقرلأا لاخدإ ئدابمو ريياعمب .عفدلا تاقاطب تانايب نمأ ريياعمب ماقرلأا لاخدإ ئدابمو ريياعمو دعاوقب مازتللااو ةظفاحملا يف هقافخإ .ii ،عفدلا تاقاطب تانايب نمأ ريياعمب وأ عفدلا تاقاطبل ةيرسلا ةيصخشلا .مازتللاا تارابتخا زايتجا يف لشفلا و/وأ تاريذحتلاو تاهيبنتلا هملاتسا وأ هيلع ةرمتسملا تامارغلا ضرف .iii تاعوفدملا ماظن لبق نم ةيلمع يأ صوصخب ريوزتلاب ةقلعتملا مزلالا ءارجلإا ذاختا رجاتلا كنب نم بلطي دق اهللاخ نم يتلاو ،يملاعلا 10. Transaction(s) to be in Saudi Riyals: All MADA-POS transactions must be denominated in Saudi Riyals (SR).

  • Standards Compliance Registry Operator shall comply with relevant existing RFCs and those published in the future by the Internet Engineering Task Force (IETF), including all successor standards, modifications or additions thereto relating to the DNS and name server operations including without limitation RFCs 1034, 1035, 1123, 1982, 2181, 2182, 2671, 3226, 3596, 3597, 4343, and 5966. DNS labels may only include hyphens in the third and fourth position if they represent valid IDNs (as specified above) in their ASCII encoding (e.g., “xn--ndk061n”).

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