Project Information Meeting Sample Clauses

Project Information Meeting. (i) The ENGINEER conducted one (1) project information meeting that was attended by two
Sample 1
AutoNDA by SimpleDocs
Project Information Meeting. After Labor Day, around the time of the Check Plan Submittal to the CLIENT, the PROFESSIONAL and CLIENT will present the design to the property owners and tenants within the project limits at a Project Information Meeting. The PROFESSIONAL will be responsible for preparing an aerial display drawing for the meeting that will depict the project details, attending the meeting, and responding to property owner questions. The CLIENT will be responsible for notifying the owners, tenants, and residents along the project corridor of the meeting.
Sample 1

Related to Project Information Meeting

  • Project Information Except for confidential information designated by the City as information not to be shared, Consultant agrees to share Project information with, and to fully cooperate with, those corporations, firms, contractors, public utilities, governmental entities, and persons involved in or associated with the Project. No information, news, or press releases related to the Project, whether made to representatives of newspapers, magazines, or television and radio stations, shall be made without the written authorization of the City’s Project Manager.

  • - CLEC INFORMATION CLEC agrees to work with Qwest in good faith to promptly complete or update, as applicable, Qwest’s “New Customer Questionnaire” to the extent that CLEC has not already done so, and CLEC shall hold Qwest harmless for any damages to or claims from CLEC caused by CLEC’s failure to promptly complete or update the questionnaire.

  • Budget Information Funding Source Funding Year of Appropriation Budget List Number Amount EPIC 18-19 301.001F $500,000 EPIC 20-21 301.001H $500,000 R&D Program Area: EDMFO: EDMF TOTAL: $ 1,000,000 Explanation for “Other” selection Reimbursement Contract #: Federal Agreement #:

  • CENTURYLINK OSS INFORMATION 57.1 Subject to the provisions of this Agreement and Applicable Law, CLEC shall have a limited, revocable, non-transferable, non-exclusive right to use CenturyLink OSS Information during the term of this Agreement, for CLEC’s internal use for the provision of Telecommunications Services to CLEC End Users in the State.

  • Verizon OSS Information 8.5.1 Subject to the provisions of this Section 8, in accordance with, but only to the extent required by, Applicable Law, Verizon grants to CBB a non-exclusive license to use Verizon OSS Information.

  • Root-­‐zone Information Publication ICANN’s publication of root-­‐zone contact information for the TLD will include Registry Operator and its administrative and technical contacts. Any request to modify the contact information for the Registry Operator must be made in the format specified from time to time by ICANN at xxxx://xxx.xxxx.xxx/domains/root/.

  • Confidentiality and Safeguarding of University Records; Press Releases; Public Information Under this Agreement, Contractor may (1) create, (2) receive from or on behalf of University, or (3) have access to, records or record systems (collectively, University Records). Among other things, University Records may contain social security numbers, credit card numbers, or data protected or made confidential or sensitive by Applicable Laws. [Option (Include if University Records are subject to FERPA.): Additional mandatory confidentiality and security compliance requirements with respect to University Records subject to the Family Educational Rights and Privacy Act, 20 United States Code (USC) §1232g (FERPA) are addressed in Section 12.41.] [Option (Include if University is a HIPAA Covered Entity and University Records are subject to HIPAA.): Additional mandatory confidentiality and security compliance requirements with respect to University Records subject to the Health Insurance Portability and Accountability Act and 45 Code of Federal Regulations (CFR) Part 160 and subparts A and E of Part 164 (collectively, HIPAA) are addressed in Section 12.26.] Contractor represents, warrants, and agrees that it will: (1) hold University Records in strict confidence and will not use or disclose University Records except as (a) permitted or required by this Agreement, (b) required by Applicable Laws, or (c) otherwise authorized by University in writing; (2) safeguard University Records according to reasonable administrative, physical and technical standards (such as standards established by the National Institute of Standards and Technology and the Center for Internet Security [Option (Include if Section 12.39 related to Payment Card Industry Data Security Standards is not include in this Agreement.):, as well as the Payment Card Industry Data Security Standards]) that are no less rigorous than the standards by which Contractor protects its own confidential information; (3) continually monitor its operations and take any action necessary to assure that University Records are safeguarded and the confidentiality of University Records is maintained in accordance with all Applicable Laws and the terms of this Agreement; and (4) comply with University Rules regarding access to and use of University’s computer systems, including UTS165 at xxxx://xxx.xxxxxxxx.xxx/board-of-regents/policy-library/policies/uts165-information-resources-use-and-security-policy. At the request of University, Contractor agrees to provide University with a written summary of the procedures Contractor uses to safeguard and maintain the confidentiality of University Records.

  • zone Information Publication ICANN’s publication of root-zone contact information for the TLD will include Registry Operator and its administrative and technical contacts. Any request to modify the contact information for the Registry Operator must be made in the format specified from time to time by ICANN at xxxx://xxx.xxxx.xxx/domains/root/.

  • Confidential System Information HHSC prohibits the unauthorized disclosure of Other Confidential Information. Grantee and all Grantee Agents will not disclose or use any Other Confidential Information in any manner except as is necessary for the Project or the proper discharge of obligations and securing of rights under the Contract. Grantee will have a system in effect to protect Other Confidential Information. Any disclosure or transfer of Other Confidential Information by Xxxxxxx, including information requested to do so by HHSC, will be in accordance with the Contract. If Grantee receives a request for Other Confidential Information, Xxxxxxx will immediately notify HHSC of the request, and will make reasonable efforts to protect the Other Confidential Information from disclosure until further instructed by the HHSC. Grantee will notify HHSC promptly of any unauthorized possession, use, knowledge, or attempt thereof, of any Other Confidential Information by any person or entity that may become known to Grantee. Grantee will furnish to HHSC all known details of the unauthorized possession, use, or knowledge, or attempt thereof, and use reasonable efforts to assist HHSC in investigating or preventing the reoccurrence of any unauthorized possession, use, or knowledge, or attempt thereof, of Other Confidential Information. HHSC will have the right to recover from Grantee all damages and liabilities caused by or arising from Grantee or Grantee Agents’ failure to protect HHSC’s Confidential Information as required by this section. IN COORDINATION WITH THE INDEMNITY PROVISIONS CONTAINED IN THE UTC, Xxxxxxx WILL INDEMNIFY AND HOLD HARMLESS HHSC FROM ALL DAMAGES, COSTS, LIABILITIES, AND EXPENSES (INCLUDING WITHOUT LIMITATION REASONABLE ATTORNEYS’ FEES AND COSTS) CAUSED BY OR ARISING FROM Grantee OR Grantee AGENTS FAILURE TO PROTECT OTHER CONFIDENTIAL INFORMATION. Grantee WILL FULFILL THIS PROVISION WITH COUNSEL APPROVED BY HHSC.

  • CONTRACT INFORMATION 1. The State of Arkansas may not contract with another party:

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