INCIDENT REPORTING AND NOTIFICATION RESPONSIBILITIES Sample Clauses

INCIDENT REPORTING AND NOTIFICATION RESPONSIBILITIES. A. FISMA defines “incident” as “an occurrence that (A) actually or imminently jeopardizes, without lawful authority, the integrity, confidentiality, or availability of information or an information system; or (B) constitutes a violation or imminent threat of violation of law, security policies, security procedures, or acceptable use policies.” B. USAC and DSS agree to report and track incidents in accordance with the most current version of Department of Homeland Security and the United States Computer Emergency Readiness Team (US-CERT) guidelines. Upon detection of an incident related to this interconnection, the Party experiencing the incident will promptly notify the other Party’s System Security Contact(s) named below: C. If the Party experiencing the incident cannot speak with the other Party’s System Security Contacts within one (1) hour, or if contacting the System Security Contact is not practical (e.g., outside of normal business hours), then this contact information shall be used: D. If either USAC or DSS experiences a loss of PII provided under this Agreement, the Party that experienced the loss incident will also comply with the PII breach reporting and security requirements set forth by OMB M-17-12, “Preparing and Responding to a Breach of Personally Identifiable Information” (January 3, 2017). E. USAC and DSS agree to notify all the Security Contact(s) named in this Agreement as soon as possible, but no later than one (1) hour, after the discovery of a breach (or suspected breach) involving PII. The Party that experienced the incident will also be responsible for following its internal established procedures, including: F. In the event of any incident arising from or in connection with this Agreement, each Party will be responsible only for costs and/or litigation arising from a breach of the Party’s own systems; USAC is responsible only for costs and litigation associated with breaches to USAC systems, and DSS is responsible only for breaches associated with DSS systems.
Sample 1Sample 2Sample 3See All (42)
AutoNDA by SimpleDocs
INCIDENT REPORTING AND NOTIFICATION RESPONSIBILITIES. A. DHS/FEMA and SBA agree to report and track incidents in accordance with the most recent, final version of NIST Special Publication 800-61.4 Upon detection of an incident related to this interconnection, the agency experiencing the incident will promptly notify the other agency's System Security Contact(s) below: ▪ DHS/FEMA will promptly notify the following contact at SBA simultaneously: SBA Office of Capital Access - Disaster Lending System Operations Center: (000) 000-0000, and SBA Office of Chief Information Officer (OCIO) Chief Information Security Officer, Xxxxxx Xxxxx, 000- 000-0000. ▪ SBA will promptly notify, the following contact at DHS/FEMA simultaneously: Information System Security Officer (ISSO), Recovery Technology Programs Division (RTPD), Disaster Assistance Improvement Program (DAIP) via email at: XXXX-Xxxxxxx-XXXX-XXXX@xxxx.xxx.xxx. 4 Xxxxxxxxx, P., Xxxxxx, T., Xxxxxx, X., & Xxxxxxxx, K. (2012, August). Computer Security Incident Handling Guide (Unit, Department of Commerce, National Institute of Standards and Technology). Retrieved from xxxx://xxxxxxx.xxxx.xxx.xxxxx 1bs/Special Publications/NIST.SP.800-61r2.pdf. B. If the federal agency experiencing the incident is unable to speak with the other federal agency's System Security Contacts within one (1) hour, or if contacting the System Security Contact is not practical (e.g., outside of normal business hours), then the following contact information shall be used: C. If either DHS/FEMA and SBA experience an exposure of PII provided under the terms of this Agreement, the federal agency that experienced the loss incident will also comply with the PII breach reporting and security requirements set forth by OMB M-17-12 "Preparing for and Responding to a Breach of Personally Identifiable Information" (January 3, 2017). D. Neither SBA nor FEMA shall be liable for any cause of action arising from the possession, control, or use by a State or local government of survivor/registrant PII, or for any loss, claim, damage or liability, of whatsoever kind or nature, which may arise from or in connection with this Agreement or the use of survivor/registrant PII. E. DHS/FEMA and SBA agree to notify all the Security Contact(s) named in this Agreement as soon as possible, but no later than one (1) hour, after the discovery of a breach (or suspected breach) involving PII. The agency that experienced the incident will also be responsible for following its internal established procedures, including: F. In t...
Sample 1Sample 2See All (10)
INCIDENT REPORTING AND NOTIFICATION RESPONSIBILITIES. A. DHS/FEMA and HUD agree to report and track incidents in accordance with the most current, final version of NIST Special Publication 800-61.2 Upon detection of an incident related to this interconnection, the agency experiencing the incident will promptly notify the other agency’s System Security Contact(s) below: • DHS/FEMA will promptly notify the following contact at HUD simultaneously: REAC Office within the Office of Public and Indian Housing. • HUD will promptly notify the following contact at DHS/FEMA simultaneously: Information System Security Officer (ISSO), Recovery Technology Programs Division (RTPD), Disaster Assistance Improvement Program (DAIP). B. If the federal agency experiencing the incident is unable to speak with the other federal agency’s System Security Contacts within one (1) hour, or if contacting the System Security Contact is not practical (e.g., outside of normal business hours), then the following contact information shall be used: C. If either DHS/FEMA and HUD experience an exposure or of personally identifiable information (PII) provided under the terms of this Agreement, the federal agency that experienced the loss incident will also comply with the PII breach reporting and security requirements set forth by OMB M-17-12 “Preparing for and Responding to a Breach of Personally Identifiable Information” (January 3, 2017) and its agency breach response plan. D. Neither HUD nor FEMA shall be liable for any cause of action arising from the possession, control, or use of survivor/registrant PII by an entity other than HUD or FEMA, or for any loss, claim, damage or liability, of whatsoever kind or nature, which may arise from or in connection with this Agreement or the use of survivor/registrant PII.
Sample 1Sample 2See All (5)
INCIDENT REPORTING AND NOTIFICATION RESPONSIBILITIES. A. USAC and DCF agree to report and track incidents in accordance with the most current, final version of NIST Special Publication 800-53. Upon detection of an incident related to this interconnection, the Party experiencing the incident will promptly notify the other Party’s System Security Contact(s) named below: B. If the Party experiencing the incident cannot speak with the other Party’s System Security Contacts within one (1) hour, or if contacting the System Security Contact is not practical (e.g., outside of normal business hours), then this contact information shall be used: C. If either USAC or DCF experiences a loss of PII provided under this Agreement, the Party that experienced the loss incident will also comply with the PII breach reporting and security requirements set forth by OMB M-17-12, “Preparing and Responding to a Breach of Personally Identifiable Information” (January 3, 2017). D. USAC and DCF agree to notify all the Security Contact(s) named in this Agreement as soon as possible, but no later than one (1) hour, after the discovery of a breach (or suspected breach) involving PII. The Party that experienced the incident will also be responsible for following its internal established procedures, including: E. In the event of any incident arising from or in connection with this Agreement, each Party will be responsible only for costs and/or litigation arising from a breach of the Party’s own systems; USAC is responsible only for costs and litigation associated with breaches to USAC systems and DCF is responsible only for breaches associated with DCF systems.
Sample 1Sample 2See All (5)
INCIDENT REPORTING AND NOTIFICATION RESPONSIBILITIES. A. USAC and the Department agree to report and track incidents in accordance with the most current, final version of NIST Special Publication 800-53. Upon detection of an incident related to this interconnection, the Party experiencing the incident will promptly notify the other Party’s System Security Contact(s) named below: B. If the Party experiencing the incident cannot speak with the other Party’s System Security Contacts within one (1) hour, or if contacting the System Security Contact is not practical (e.g., outside of normal business hours), then this contact information shall be used: C. USAC and the Department agree to notify all the Security Contact(s) named in this Agreement as soon as possible, but no later than one (1) hour, after the discovery of a breach (or suspected breach) involving PII. The Party that experienced the incident will also be responsible for following its internal established procedures, including: D. In the event of any incident arising from or in connection with this Agreement, each Party will be responsible only for costs and/or litigation arising from a breach of the Party’s own systems; USAC is responsible only for costs and litigation associated with breaches to USAC systems and the Department is responsible only for breaches associated with the Department systems.
Sample 1
INCIDENT REPORTING AND NOTIFICATION RESPONSIBILITIES. A. FISMA defines “incident” as “an occurrence that (A) actually or imminently jeopardizes, without lawful authority, the integrity, confidentiality, or availability of information or an information system; or (B) constitutes a violation or imminent threat of violation of law, security policies, security procedures, or acceptable use policies.” B. USAC and DSS agree to report and track incidents in accordance with the most current version of Department of Homeland Security and the United States Computer Emergency Readiness Team (US-CERT) guidelines. Upon detection of an incident related to this interconnection, the Party experiencing the incident will promptly notify the other Party’s System Security Contact(s) named below: C. If the Party experiencing the incident cannot speak with the other Party’s System Security D. If either USAC or DSS experiences a loss of PII provided under this Agreement, the Party that experienced the loss incident will also comply with the PII breach reporting and security requirements set forth by OMB M-17-12, “Preparing and Responding to a Breach of Personally Identifiable Information” (January 3, 2017). E. USAC and DSS agree to notify all the Security Contact(s) named in this Agreement as soon as possible, but no later than one (1) hour, after the discovery of a breach (or suspected breach) involving PII. The Party that experienced the incident will also be responsible for following its internal established procedures effective at the time of the incident.
Sample 1
INCIDENT REPORTING AND NOTIFICATION RESPONSIBILITIES. A. VA and SBA agree to report and track incidents in accordance with the most recent, final version of NIST Special Publication 800-61, Rev. 2.1 Upon detection of an incident related to this interconnection, the agency experiencing the incident will promptly notify the other agency's System Security Contact(s) below: 1 Xxxxxxxxx, P,, Xxxxxx, T., Xxxxxx, X., & Xxxxxxxx, K. (2012, August). Computer Security Incident Handling Guide (Unit, Department of Commerce, National Institute of Standards and Technology). Retrieved from xxxx://xxxxxxx.xxxx.xxx/nistp 1bs/Special Publications/NIST.SP.800-61r2.pdf. ▪ VA will promptly notify the following contact at SBA: SBA Office of Chief Information Officer (OCIO) Chief Information Security Officer: 202-205- 0101. ▪ SBA will promptly notify xxx@xx.xxx, and the following contacts at VA simultaneously: i. VA Privacy Officer, Xxxx Xxxxxx: (000) 000-0000, xxxx.xxxxxx@xx.xxx ii. VA Chief Information Security Officer, Xxxxxxx Xxxxxxxx: (202) 270- 1878, xxxxxxx.xxxxxxxx@xx.xxx
Sample 1
AutoNDA by SimpleDocs
INCIDENT REPORTING AND NOTIFICATION RESPONSIBILITIES. A. jeopardizes, without lawful authority, the integrity, confidentiality, or availability of information or an information system; or (B) constitutes a violation or imminent threat B. USAC and OIT agree to report and track incidents in accordance with the most current version of Department of Homeland Security and the United States Computer Emergency Readiness Team (US-CERT) guidelines. Upon detection of an incident related to this C. If the Party experiencing the Contacts within one (1) hour, or if contacting the System Security Contact is not practical (e.g., outside of normal business hours), then this contact information shall be used: Office of Information Security, OIT, XXXX@xxxxx.xx.xx: (000) 000-0000 D. If either USAC or OIT experiences a loss of PII provided under this Agreement, the Party that experienced the loss incident will also comply with the PII breach reporting and security requirements set forth by OMB M-17- E. USAC and OIT agree to notify all the Security Contact(s) named in this Agreement as soon as possible, but no later than one (1) hour, after the discovery of a breach (or suspected breach) involving PII. The Party that experienced the incident will also be responsible for following its internal established procedures, including: F. In the event of any incident arising from or in connection with this Agreement, each Party
Sample 1
INCIDENT REPORTING AND NOTIFICATION RESPONSIBILITIES. A. jeopardizes, without lawful authority, the integrity, confidentiality, or availability of information or an information system; or (B) constitutes a violation or imminent threat B. USAC and the Agencies agree to report and track incidents in accordance with the most current version of Department of Homeland Security and the United States Computer Emergency Readiness Team (US-CERT) guidelines. Upon detection of an incident related to this interconnection, the Party experiencing the incident will promptly notify System Security Contact(s) named below: USAC will promptly notify these contacts at the Agencies simultaneously: Wisconsin Department of Health Services Xxxxx Xxxxx, Chief Information Security Officer 0 Xxxx Xxxxxx Xxxxxx Madison, WI 53703 Xxxxx.Xxxxx@xxx.xxxxxxxxx.xxx Office: (000) 000-0000 Cell: (000) 000-0000 Wisconsin Department of Revenue Xxxxx Xxxxxxxx, Exchange Agreement Coordinator 0000 Xxxxxxx Xxxx Madison, WI 53713 Office: (000) 000-0000 The Agencies will promptly notify xxxxxxxx@xxxx.xxx and the following contacts at USAC simultaneously: USAC Privacy Officer, Xxxxx Xxxxxxxx: (000) 000-0000 USAC Director of Information Security, Xxxxx Xxxx: (000) 000-0000 As soon as possible after notifying the Agencies of an incident, or receiving notification of an incident from the Agencies, USAC will report the incident to the Operations Center (NSOC) at XXXX@xxx.xxx or (000) 000-0000 within one (1) hour of notification. C. If the Party experiencing the Contacts within one (1) hour, or if contacting the System Security Contact is not practical (e.g., outside of normal business hours), then this contact information shall be used: Wisconsin Department of Health Services Xxxxxxxx Xxxxxxx, Deputy Chief Information Security Officer 0 Xxxx Xxxxxx Xxxxxx Madison, WI 53703 Xxxxxxxx.Xxxxxxx@xxx.xxxxxxxxx.xxx Office: (000) 000-0000 Cell: (000) 000-0000 Wisconsin Department of Revenue Xxxx Xxxxxx, Chief Information Security Officer 0000 Xxxxxxx Xxxx Madison, WI 53713 xxxxxxx.xxxxxx@xxxxxxxxx.xxx Office: (000) 000-0000 D. If either USAC or the Agencies experiences a loss of PII provided under this Agreement, the Party that experienced the loss incident will also comply with the PII breach reporting and security requirements set forth by OMB M-17- E. USAC and the Agencies agree to notify all the Security Contact(s) named in this Agreement as soon as possible, but no later than one (1) hour, after the discovery of a breach (or suspected breach) involving PII. The ...
Sample 1

Related to INCIDENT REPORTING AND NOTIFICATION RESPONSIBILITIES

  • Customer’s Responsibilities 9.1 If and to the extent applicable or under the control of the Customer, Customer shall provide complete and accurate information regarding requirements for the Project and the Site(s), including, without limitation, constraints, space requirements, underground or hidden facilities and structures, and all applicable drawings and specifications. 9.2 Customer shall prepare, file for, and use commercially reasonable efforts to obtain all Required Approvals necessary to perform its obligations under this Agreement. 9.3 Customer shall reasonably cooperate with Company as required to facilitate Company’s performance of the Work.

  • The Publisher’s Responsibilities Subject always to the other provisions of this Clause below, the Publisher will undertake the production, publication and distribution of the Contribution and the Work in print and/or electronic form at its own expense and risk within a reasonable time after acceptance of the Work unless the Publisher is prevented from or delayed in doing so due to any circumstances beyond its reasonable control. The Publisher shall have the entire control of such production, publication and distribution determined in its sole discretion in relation to any and all editions and versions of the Contribution and the Work, including in respect of all the following matters: (a) distribution channels, including determination of markets; (b) determination of the range and functions of electronic formats and/or the number of print copies produced; (c) publication and distribution of the Contribution, the Work, or parts thereof as individual content elements, in accordance with market demand or other factors; (d) determination of layout and style as well as the standards for production; (e) setting or altering the list price, and allowing for deviations from the list price (if permitted under applicable jurisdiction); (f) promotion and marketing as the Publisher considers most appropriate. All rights, title and interest, including all intellectual property or related rights in the typography, design and/or look-and-feel of the Contribution shall remain the exclusive property of and are reserved to the Publisher. All illustrations and any other material or tangible or intangible property prepared at the expense of the Publisher including any marketing materials remain, as between the Parties, the exclusive property of the Publisher. The provisions of this subclause shall continue to apply notwithstanding any termination of, and/or any reversion of rights in the Contribution to the Author, under this Agreement. Without prejudice to the Publisher's termination and other rights hereunder including under the Clause "The Author's Responsibilities", it is agreed and acknowledged by the Parties that nothing in this Agreement shall constitute an undertaking on the part of the Publisher to publish the Contribution unless and until: (i) any and all issues in relation to the Work (including all necessary revisions, consents and permissions) raised by the Publisher have been resolved to the Publisher’s satisfaction, and (ii) the Publisher has given written notice of acceptance in writing of the final manuscript of the entire Work to the Editor. If following (i) and (ii) above the Publisher has not published the Contribution in any form within a reasonable period and the Author has given written notice to the Publisher requiring it to publish within a further reasonable period and the Publisher has failed to publish in any form, then the Author may terminate this Agreement by one month's written notice to the Publisher and all rights granted by the Author to the Publisher under this Agreement shall revert to the Author (subject to the provisions regarding any third party rights under any subsisting licence or sub-licence in accordance with the Clause "Termination"). The Author may also give such written notice requiring publication on the same terms as above if the Publisher has published the Contribution but subsequently ceases publishing the Contribution in all forms so that it is no longer available. This shall be the Author's sole right and remedy in relation to such non-publication and is subject always to the Author's continuing obligations hereunder including the Clause "Warranty".

  • Our Responsibilities This notice describes how medical information about you may be used and disclosed and how you can get access to this information. This notice took effect on September 23, 2013. We are required to maintain the privacy of your protected health information and we will follow the terms of this notice while it is in effect. • Your past, present, or future physical or mental health or condition • Providing you health care • The past, present, or future payment for providing you health care We collect your information as necessary to provide you with health insurance products and services and to administer our business. We may also disclose this information to nonaffiliated third parties as described in this notice. The types of information we may collect and disclose include: • Information you or your employer provide on applications and other forms, such as names, addresses, social security numbers, and dates of birth • Information about your interactions with us or others (such as providers) regarding your medical information or claims • Information you provide in person, by phone, in email, or through visits to our website • You can ask to see or get a copy of your health and claims records and other health information we have about you. • We will provide a copy or a summary of your health and claims records, usually within 30 days of your request. We may charge a reasonable, cost-based fee. • We may ask that you submit your request in writing. Please note, if you want to obtain copies of your medical records, you should contact the practitioner or facility. We do not generate, modify, or maintain complete medical records. • You may also request that we send a copy of your information to a third party. We may ask that you submit a written, signed authorization form permitting us to do so and we may charge a reasonable fee for copying and mailing your personal information. • You can ask us to correct your health and claims records if you think they are incorrect or incomplete. • We may say no to your request, but we’ll tell you why in writing within 60 days. • You can ask us to contact you in a specific way (for example, home or office phone) or to send mail to a different address. • We will consider all reasonable requests, and must say “yes” if you tell us you would be in danger if we do not. • All requests should be made in writing. • It may take a short period of time for us to implement your request. • We will comply with your request if it is reasonable and continues to permit us to collect premiums and pay claims under your policy, including issuing certain explanations of benefits and policy information to the BlueShield of Northeastern New York is a division of HealthNow New York Inc., an independent licensee of the BlueCross BlueShield Association. 15049R_NENY_12_19 f11011 subscriber of the policy. For example, even if you request confidential communications: ο We will mail the check for services you receive from a nonparticipating provider to you but made payable to the subscriber ο Accumulated payment information such as deductibles (in which your information might appear), will continue to appear on explanations of benefits sent to the subscriber ο We may disclose to the subscriber, as the contract holder, policy details such as eligibility status or certificates of coverage • You can ask us not to use or share certain health information for treatment, payment, or our operations. • We are not required to agree to your request, but if we do, we will abide by our agreement (except when necessary for treatment in an emergency). • You have the right to authorize individuals to act on your behalf with respect to your information. You must identify your authorized representatives on a HIPAA-compliant authorization form (available on our website) and explain what type of information they may receive. • You have the right to revoke an authorization except for actions already taken based on your authorization. • You can complain if you feel we have violated your rights by contacting us using the information listed on page 4. • You can file a complaint with the U.S. Department of Health and Human Services Office for Civil Rights. • We will not retaliate against you for filing a complaint. • With your family, close friends, or others involved with your health care or payment for your care when you are present and have given us permission to do so. If you are not present, if it is an emergency, or you are not able to give us permission, we may give your information to a family member, friend, or other person if sharing your information is in your best interest. In these cases, the person requesting your information must accurately verify details about you (e.g., name, identification number, date of birth, etc.) and prove involvement with your health care or payment for your health care by providing details relevant to the information requested. For example, if a family member calls us with prior knowledge of a claim (e.g., provider’s name, date of service, etc.), we may confirm the claim’s status, patient responsibility, etc. We will only disclose information directly relevant to that person’s involvement with your health care or payment for your health care. • In a disaster relief situation. In these cases we never share your information unless you give us written permission: • Marketing purposes • Sale of your information • Disclose your psychotherapy notes • Make certain disclosures of information considered sensitive in nature, such as HIV/AIDS, mental health, alcohol or drug dependency, and sexually transmitted diseases. Certain federal and state laws require that we limit how we disclose this information. In general, unless we obtain your written authorization, we will only disclose such information as provided for in applicable laws. We typically use or share your health information in the following ways: • We can use your health information and share it with professionals who are treating you.

  • Your Responsibilities 7.1 You are responsible for installing and configuring, and using the Service, Software, and Hardware, including account set up and configuration settings (unless NCR Voyix provides remote support for any of the foregoing as part of your subscription to the Service), compliance with applicable laws and regulations, and establishing any payment processing or other services certified by NCR Voyix for use with the Service (including through NCR Voyix’s wholly owned affiliates). You are solely responsible for reviewing any default or automated settings and configuring applicable settings to meet all legal, regulatory and other requirements applicable to your business. NCR shall have no liability in connection with such settings or configurations. You acknowledge that NCR Voyix does not provide legal, tax or accounting advice. You will provide NCR Voyix access to your network, system, data, and relevant information as reasonably required to perform the Service. You acknowledge that NCR Voyix personnel may require, and you will provide, the ability to access and correct transaction or input data while the Service is being provided to you. NCR Voyix is not responsible for any damage caused by errors or omissions in any information, instructions, data, or scripts you or a third party provides on your behalf in connection with the Service, or any actions NCR Voyix takes at your direction. 7.2 To use the Service, you must maintain internet access at your own expense. NCR VOYIX IS NOT RESPONSIBLE FOR AND DOES NOT WARRANT THE PERFORMANCE OF ANY INTERNET SERVICE OR OTHER PROVIDER OR ITS SERVICES, AND YOU AGREE THAT NCR VOYIX HAS NO LIABILITY TO YOU FOR SUCH PERFORMANCE OR SERVICES. 7.3 Title to hardware, software, systems, documentation, and other intellectual property NCR Voyix uses to provide the Service will remain with NCR Voyix or its licensors, unless otherwise agreed in writing. You will take reasonable actions to protect NCR Voyix’s intellectual property rights. 7.4 You are responsible for complying with all rules, bylaws, programs, and regulations of the payment card networks in connection with your use of the Service, Software and Hardware, as applicable. You will defend and indemnify NCR Voyix against any claim or loss resulting from your failure to fulfill your responsibilities under this Section. 7.5 Certain Services may perform analysis of transaction records designed to identify transaction patterns and activity that may be indicative of fraud. You acknowledge that the indicia reported by such Services may not necessarily be the result of fraudulent activity. You are responsible for performing its own evaluation of any results. NCR Voyix does not guarantee the detection of fraudulent transactions. 7.6 You are responsible for all data, information, materials and instructions (“Customer Instructions”) provided to NCR Voyix by you or on your behalf. NCR Voyix is entitled to rely upon Customer Instructions. In no event will NCR Voyix be liable with respect to any loss, liability, cost, damage, or expense arising out of a claim by you or any third party to the extent that claim arises as a result of NCR Voyix’s compliance with Customer Instructions.

  • Reporting Responsibility a) Vendor shall be responsible for reporting all services purchased under the Contract. Vendor shall file the monthly reports, subcontract reports, and pay the administrative fees in accordance with the due dates specified in this section. b) DIR shall have the right to verify required reports and to take any actions necessary to enforce its rights under this section, including but not limited to compliance checks of Vendor’s applicable Contract. Vendor will provide all required documentation at no cost.

  • Client’s Responsibilities (a) Client agrees to advise Consultant regarding Client's Project requirements and to provide all relevant information, surveys, data and previous reports accessible to Client which Consultant may reasonably require. (b) Client shall designate a Project Representative to whom all communications from Consultant shall be directed and who shall have limited administrative authority on behalf of Client to receive and transmit information and make decisions with respect to the Project. Said representative shall not, however, have authority to bind Client as to matters of governmental policy or fiscal policy, nor to contract for additions or obligations exceeding a value which is the lesser of $5000 or 5% of the maximum contract price. (c) Client shall examine all documents presented by Consultant, and render decisions pertaining thereto within a reasonable time. The Client's approval of any drawings, specifications, reports, documents or other materials or product furnished hereunder shall not in any way relieve Consultant of responsibility for the professional adequacy of its work. (d) Client shall perform its obligations and render decisions within a reasonable time under the circumstances presented. Based upon the nature of Client and its requirements, a period of 14 days shall be presumed reasonable for any decision not involving policy decision or significant financial impact, when all information reasonably necessary for Client to responsibly render a decision has been furnished. A period of 46 days shall be presumed reasonable for Client to act with respect to any matter involving policy or significant financial impact. The above periods of presumed reasonableness shall be extended where information reasonably required is not within the custody or control of Client but must be procured from others.

  • City Responsibilities 2.8.1 CITY shall make available to CONSULTANT all technical data that is in CITY'S possession, reasonably required by CONSULTANT relating to the SERVICES. 2.8.2 CITY shall provide access to and make all provisions for CONSULTANT to enter upon public and private lands, to the fullest extent permitted by law, as reasonably required for CONSULTANT to perform the SERVICES. 2.8.3 CITY shall examine all reports, correspondence, and other documents presented by CONSULTANT upon request of CITY, and render, in writing, decisions pertaining thereto within a reasonable time so as not to delay the work of CONSULTANT. 2.8.4 It is expressly understood and agreed that all work done by CONSULTANT shall be subject to inspection and acceptance by CITY and approval of SERVICES shall not forfeit the right of CITY to require correction, and nothing contained herein shall relieve CONSULTANT of the responsibility of the SERVICES required under the terms of this Contract until all SERVICES have been completed and accepted by CITY.

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