Requirement to Comply Sample Clauses

Requirement to Comply. Employees who fail to comply with the requirements set forth in this Section shall be discharged by the Employer within thirty (30) days after receipt of written notice to the Employer from the Union, unless the employee fulfills the membership obligations set forth in this Agreement.
AutoNDA by SimpleDocs
Requirement to Comply. To the extent applicable, the Business Associate’s obligations to carry out a covered entity’s obligation under subpart E of 45 CFR Part 164 is the same.
Requirement to Comply. You are required to cause any transferor and transferee described in this Article 14 to perform all of the obligations imposed on such persons under this Article 14. Any failure by you or any transferor and transferee described in this Article 14 to comply with the provisions of this Section prior to the transfer of any interest in you, the Restaurant or this Agreement shall constitute an event of default under this Agreement.
Requirement to Comply. BART’s AB 2923 Development Principles, adopted by the BART Board of Directors in August 2020, states that “if a jurisdiction shares BART’s commitment to regional climate, housing, and equity goals – as evidenced by zoning BART property for the highest feasible density, use and height – BART commits to encouraging consistency with that jurisdiction’s objective design standards in its development agreements.” Consistent with the Development Principles, BART agrees that a zoning of a minimum of 75 units per acre and at least 7 stories in height satisfies the Development Principles of this policy. BART agrees to enforce the City’s Objective Design Standards through its ENA and other real estate agreements, provided that the resulting ODS are consistent with applicable state law, including but not limited to SB 35, and with all other requirements for the ODS established by this MOA, and so long as they do not diminish the zoning envelope by more than ten percent (10%) below what AB 2923 heights and floor-area-ratio would allow, as calculated based on the maximum square footage that could be built with a reasonable circulation framework and open space provided, utilizing the methodology attached hereto as Exhibit D. In addition, BART shall, in its ENA, require the developer to make good faith efforts to cooperate with the City in the development of Objective Design Standards so that they can be brought forward for review and approval. In the event the City cannot adopt the ODS within 9 months of execution of the ENA due to occurrences or circumstances beyond the City's reasonable control, including but not limited to, acts of God, fire, strikes or other labor disturbances, riots, civil commotion, war, sabotage, pandemic, failure of the developer to make good faith efforts to cooperate with the City in the development of the Objective Design Standards, or any other cause similar to those herein specified which cannot be controlled by the City, then the City Manager and General Manager may agree to extend the deadline for adoption of the ODS to a mutually agreeable, later date.

Related to Requirement to Comply

  • Provide Data in Compliance with Applicable Laws LEA shall provide Student Data for the purposes of obtaining the Services in compliance with all applicable federal, state, and local privacy laws, rules, and regulations, all as may be amended from time to time.

  • Requirements At its own expense, Supplier must maintain insurance policy(ies) in effect at all times during the performance of this Contract with insurance company(ies) licensed or authorized to do business in the State of Minnesota having an “AM BEST” rating of A- or better, with coverage and limits of insurance not less than the following:

  • Standards Compliance DNS. 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”).

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