Attempt to Resolve Alleged Design Error with Consultant Clause Samples

Attempt to Resolve Alleged Design Error with Consultant. After the meeting(s) with the consultant have been completed regarding the consultant’s alleged design error(s), there are three possible scenarios: • It is determined via mutual agreement that there is not a consultant design error(s). If this is the case, then the process will not proceed beyond this point. • It is determined via mutual agreement that a consultant design error(s) occurred. If this is the case, then the Director of Public Works or Agency Engineer, or their representatives, negotiate a settlement with the consultant. The settlement would be paid to the agency or the amount would be reduced from the consultant’s agreement with the agency for the services on the project in which the design error took place. The agency is to provide LP, through the Region Local Programs Engineer, a summary of the settlement for review and to make adjustments, if any, as to how the settlement affects federal reimbursements. No further action is required. • There is not a mutual agreement regarding the alleged consultant design error(s). The consultant may request that the alleged design error(s) issue be forwarded to the Director of Public Works or Agency Engineer for review. If the Director of Public Works or Agency Engineer, after review with their legal counsel, is not able to reach mutual agreement with the consultant, proceed to Step 5.
View SourceView Similar (55)
Attempt to Resolve Alleged Design Error with Consultant. After the meeting(s) with the consultant have been completed regarding the consultant’s alleged design error(s), there are three possible scenarios: • It is determined via mutual agreement that there is not a consultant design error(s). If this is the case, then the process will not proceed beyond this point. • It is determined via mutual agreement that a consultant design error(s) occurred. If this is the case, then the Director of Public Works or AGENCY Engineer, or their representatives, negotiate a settlement with the CONSULTANT. The settlement would be paid to the agency or the amount would be reducedfrom the CONSULTANT’S agreement with the AGENCY for the services on the project in which the design error took place. • There is not a mutual agreement regarding the alleged consultant design error(s). The CONSULTANT may request that the alleged design error(s) issue be forwarded to the Director of Public Works or AGENCY Engineer for review. If the Director of Public Works or AGENCY Engineer, after review with their legalcounsel, is not able to reach mutual agreement with the consultant, proceed to arbitration or litigation. The purpose of this exhibit is to describe a procedure regarding claim(s) on a consultant agreement. The following procedures should only be utilized on consultant claims greater than $1,000. If the consultant’s claim(s) total a $1,000 or less, it would not be cost effective to proceed through the outlined steps. It is suggested that the Director of Public Works or AGENCY Engineer negotiate a fair and reasonable price for the consultant’s claim(s) that total $1,000 or less. This exhibit will outline the procedures to be followed by the CONSULTANT and the AGENCY to consider a potential claim by the CONSULTANT.
View SourceView Similar (9)
Attempt to Resolve Alleged Design Error with Consultant. After the meeting(s) with the consultant have been completed regarding the consultant’s alleged design error(s), there are three possible scenarios: • It is determined via mutual agreement that there is not a consultant design error(s). If this is the case, then the process will not proceed beyond this point. • It is determined via mutual agreement that a consultant design error(s) occurred. If this is the case, then the Director of Public Works or Agency Engineer, or their representatives, negotiate a settlement with the consultant. The settlement would be paid to the agency or the amount would be reduced from the consultant’s agreement with the agency for the services on the project in which the design error took place. The agency is to provide LP, through the Region Local Programs Engineer, a summary of the settlement for review and to make adjustments, if any, as to how the settlement affects federal
View SourceView Similar (4)

Related to Attempt to Resolve Alleged Design Error with Consultant

  • SCOPE OF ARCHITECT’S BASIC SERVICES 3.1 The Architect’s Basic Services consist of those described in this Article 3 and include usual and customary structural, mechanical, and electrical engineering services. Services not set forth in this Article 3 are Supplemental or Additional Services. § 3.1.1 The Architect shall manage the Architect’s services, research applicable design criteria, attend Project meetings, communicate with members of the Project team, and report progress to the Owner. § 3.1.2 The Architect shall coordinate its services with those services provided by the Owner and the Owner’s consultants. The Architect shall be entitled to rely on, and shall not be responsible for, the accuracy, completeness, and timeliness of, services and information furnished by the Owner and the Owner’s consultants. The Architect shall provide prompt written notice to the Owner if the Architect becomes aware of any error, omission, or inconsistency in such services or information. § 3.1.3 As soon as practicable after the date of this Agreement, the Architect shall submit for the Owner’s approval a schedule for the performance of the Architect’s services. The schedule initially shall include anticipated dates for the commencement of construction and for Substantial Completion of the Work as set forth in the Initial Information. The schedule shall include allowances for periods of time required for the Owner’s review, for the performance of the Owner’s consultants, and for approval of submissions by authorities having jurisdiction over the Project. Once approved by the Owner, time limits established by the schedule shall not, except for reasonable cause, be exceeded by the Architect or Owner. With the Owner’s approval, the Architect shall adjust the schedule, if necessary, as the Project proceeds until the commencement of construction. § 3.1.4 The Architect shall not be responsible for an Owner’s directive or substitution, or for the Owner’s acceptance of non-conforming Work, made or given without the Architect’s written approval. § 3.1.5 The Architect shall contact governmental authorities required to approve the Construction Documents and entities providing utility services to the Project. The Architect shall respond to applicable design requirements imposed by those authorities and entities. § 3.1.6 The Architect shall assist the Owner in connection with the Owner’s responsibility for filing documents required for the approval of governmental authorities having jurisdiction over the Project.

  • Indemnification by Subcontractors To the fullest extent permitted by law, an Interconnection Party that uses a subcontractor to carry out any of the Interconnection Party’s obligations under this Appendix 2 shall require each of its subcontractors to indemnify, hold harmless and defend each other Interconnection Party, its representatives and assigns from and against any and all claims and/or liability for damage to property, injury to or death of any person, including the employees of any Interconnection Party or of any Affiliate of any Interconnection Party, or any other liability incurred by the other Interconnection Party or any of its Affiliates, including all expenses, legal or otherwise, to the extent caused by any act or omission, negligent or otherwise, by such subcontractor and/or its officers, directors, employees, agents and assigns, that arises out of or is connected with the operation of the facilities of either Interconnected Entity described in this Appendix 2; provided, however, that no Interconnection Party or Affiliate thereof shall be entitled to indemnity under this Section 18.3 in respect of any injury, loss, or damage to the extent that such loss, injury, or damage results from the negligence or willful misconduct of the Interconnection Party or Affiliate seeking indemnity.

  • CLAIM FILING AND PROVIDER PAYMENTS This section provides information regarding how a member may file a claim for a covered healthcare service and how we pay providers for a covered healthcare service. Network providers file claims on your behalf. Non-network providers may or may not file claims on your behalf. If a non-network provider does not file a claim on your behalf, you will need to file it yourself. To file a claim, please send us the provider’s itemized bill, and include the following information: • your name; • your member ID number; • the name, address, and telephone number of the provider who performed the service; • date and description of the service; and • charge for that service. Please send your claim to the address listed in the Contact Information section. Claims must be filed within one calendar year of the date you receive a covered healthcare service. Claims submitted after this deadline are not eligible for reimbursement. This timeframe does not apply if you are legally incapacitated. We pay network providers directly for covered healthcare services. Network providers agree not to bill, charge, collect a deposit from, or seek reimbursement from you for a covered healthcare service, except for your share under the plan. When you see a network provider, you are responsible for a share of the cost of covered healthcare services. Your share includes the deductible, if one applies, and the copayment, as listed in the Summary of Medical Benefits. The covered healthcare service may also have a benefit limit, which caps the amount we will reimburse the provider for that service. You will be responsible for any amount over the benefit limit, up to the allowance. Your provider may request these payments at the time of service, or may bill you after the service. If you do not pay your provider, the provider may decline to provide current or future services or may pursue payment from you, such as beginning collection proceedings. Some of our agreements with network providers include alternative payment methods such as incentives, risk-sharing, care coordination, value-based, capitation or similar payment methods. Your copayments are determined based on our allowance at the date the service is rendered. Your copayment may be more or less than the amount the network provider receives under these alternative payment methods. Your copayment will not be adjusted based on these alternative payment methods, or for any payment that is not calculated on an individual claim basis. Our contracts with providers may establish a payment allowance for multiple covered healthcare services, and we may apply a single copayment based on these arrangements. In these cases, you will typically be responsible for fewer copayments than if your share of the cost had been determined on a per service basis.

  • Verizon OSS Information 8.5.1 Subject to the provisions of this Section 8 and Applicable Law, Verizon grants to Reconex a non-exclusive license to use Verizon OSS Information. 8.5.2 All Verizon OSS Information shall at all times remain the property of Verizon. Except as expressly stated in this Section 8, Reconex shall acquire no rights in or to any Verizon OSS Information. 8.5.2.1 The provisions of this Section 8.5.2 shall apply to all Verizon OSS Information, except (a) Reconex Usage Information, (b) CPNI of Reconex, and (c) CPNI of a Verizon Customer or a Reconex Customer, to the extent the Customer has authorized Reconex to use the Customer Information. 8.5.2.2 Verizon OSS Information may be accessed and used by Reconex only to provide Telecommunications Services to Reconex Customers. 8.5.2.3 Reconex shall treat Verizon OSS Information that is designated by Verizon, through written or electronic notice (including, but not limited to, through the Verizon OSS Services), as “Confidential” or “Proprietary” as Confidential Information of Verizon pursuant to Section 10 of the Agreement. 8.5.2.4 Except as expressly stated in this Section 8, this Agreement does not grant to Reconex any right or license to grant sublicenses to other persons, or permission to other persons (except Reconex’s employees, agents or contractors, in accordance with Section 8.5.2.5 below, to access, use or disclose Verizon OSS Information. 8.5.2.5 Reconex’s employees, agents and contractors may access, use and disclose Verizon OSS Information only to the extent necessary for Reconex’s access to, and use and disclosure of, Verizon OSS Information permitted by this Section 8. Any access to, or use or disclosure of, Verizon OSS Information by Reconex’s employees, agents or contractors, shall be subject to the provisions of this Agreement, including, but not limited to, Section 10 of the Agreement and Section 8.5.2.3 above. 8.5.2.6 Reconex’s license to use Verizon OSS Information shall expire upon the earliest of: (a) the time when the Verizon OSS Information is no longer needed by Reconex to provide Telecommunications Services to Reconex Customers; (b) termination of the license in accordance with this Section 8; or (c) expiration or termination of the Agreement. 8.5.2.7 All Verizon OSS Information received by Reconex shall be destroyed or returned by Reconex to Verizon, upon expiration, suspension or termination of the license to use such Verizon OSS Information. 8.5.3 Unless sooner terminated or suspended in accordance with the Agreement or this Section 8 (including, but not limited to, Section 2.2 of the Agreement and Section 8.6.1 below), Reconex’s access to Verizon OSS Information through Verizon OSS Services shall terminate upon the expiration or termination of the Agreement. 8.5.3.1 Verizon shall have the right (but not the obligation) to audit Reconex to ascertain whether Reconex is complying with the requirements of Applicable Law and this Agreement with regard to Reconex’s access to, and use and disclosure of, Verizon OSS Information. 8.5.3.2 Without in any way limiting any other rights Verizon may have under the Agreement or Applicable Law, Verizon shall have the right (but not the obligation) to monitor Reconex’s access to and use of Verizon OSS Information which is made available by Verizon to Reconex pursuant to this Agreement, to ascertain whether Reconex is complying with the requirements of Applicable Law and this Agreement, with regard to Reconex’s access to, and use and disclosure of, such Verizon OSS Information. The foregoing right shall include, but not be limited to, the right (but not the obligation) to electronically monitor Reconex’s access to and use of Verizon OSS Information which is made available by Verizon to Reconex through Verizon OSS Facilities. 8.5.3.3 Information obtained by Verizon pursuant to this Section 8.5.3.3 shall be treated by Verizon as Confidential Information of Reconex pursuant to Section 10 of the Agreement; provided that, Verizon shall have the right (but not the obligation) to use and disclose information obtained by Verizon pursuant to this Section 8.5.3.3 to enforce Verizon’s rights under the Agreement or Applicable Law.