Warranty Management Sample Clauses

POPULAR SAMPLE Copied 3 times
Warranty Management. A primary focus of RÖCHLING’s customers is to minimize expenses attributed to raw material performance after vehicle sale. Financial liability associated with warranty is increasingly significant, as consumer awareness improves and OEM customers extend warranty coverages. OEM customers have stipulated that warranty costs will be shared with their supply base. As such, SUPPLIERS will be expected to participate in warranty activities including: • Warranty returns reviews/analysis • Improvement actions • Warranty cost responsibility When RÖCHLING is involved in a warranty, campaign or recall issue, with financial consequences based on RÖCHLING’s customers’ warranty or recall policies, the SUPPLIER undertakes to refund all damages and costs charged to and/or incurred by RÖCHLING according to the costs-by-cause principle for the individual cases to be reimbursed. Warranty, campaign or recall issue are handled in accordance with OEM agreements and requirements, including escalation process and deadlines. See the RÖCHLING warranty agreements in their latest revision for further details and requirements.
View SourceView Similar (2)
Warranty Management. Seller shall verify and enforce or assist Buyer’s Personnel with verifying and enforcing all warranties applicable to the Facility Assets.
View SourceView Similar (2)
Warranty Management. Collection, repair and manufacturer's warranty management
View Source
Warranty Management. The PM needs to provide the equipment manuals and a comprehensive checklist or table with all the constructed items having a warranty requirement. This checklist should list the item number, item location in the work and the date of acceptance by the owner. It should also list the date of warranty expiration and the date of warranty inspection. PRHFA has the right to make a warranty inspection which could take place 30 days prior to the warranty expiration date. ▇▇▇▇▇ ▇▇▇▇▇ Act. If applicable, a ▇▇▇▇▇-▇▇▇▇▇ Compliance Plan that clearly describes the processes the Program Management Firm will be implementing to ensure that all applicable ▇▇▇▇▇-▇▇▇▇▇ requirements are adhered to throughout the whole rehabilitation process. The ▇▇▇▇▇-▇▇▇▇▇ Compliance Plan must provide a description of the documentation that will be monitored and the frequency with which the Program Management Firms will be monitoring it.
View Source
Warranty Management. Seller may retain an independent third-party warranty management company to coordinate and perform warranty services during the warranty period. The contact information and procedures to be followed will be provided to Buyer at Closing.
View Source
Warranty Management. DISTRIBUTOR shall resolve all warranty claims with the VAR with respect to an End User. Warranty returns shall only be credited against DISTRIBUTOR's account if the Products are determined to be defective and the End Users have followed the procedures set forth in GUPTA's End User License Agreement.
View Source
Warranty Management. Buyer must notify Seller in writing concerning any Product allegedly defective or otherwise not in conformity with Seller’s Warranty as soon as practicable, but in no event later than one hundred twenty (120) days after discovery of such defect or nonconformity subject to the express Warranty Period set forth above. ▇▇▇▇▇'s written notice must set forth with particularity the nature and extent of the defect or nonconformity.
View Source
Warranty Management. The Contractor shall report to the KO (via the COR) all defects in workmanship, material, parts, or improper installation by others and found by the Contractor to be covered by a warranty prior to performing repair work. The Contractor is responsible for knowing which equipment and components are covered by the original warranty and the warranty duration. The KO (via the COR) will provide available warranty documents.
View Source
Warranty Management. The Contractor shall manage any Non-Conformance Reports made by, and on behalf of, the Authority and inform the Authority once these have been raised in accordance with Clause 2.5
View Source

Related to Warranty Management

  • Property Management (a) Borrower shall (i) cause Manager to manage the Properties in accordance with the Management Agreement, (ii) diligently perform and observe all of the terms, covenants and conditions of the Management Agreement on the part of Borrower to be performed and observed, (iii) promptly notify Lender of any default under the Management Agreement of which it is aware, (iv) promptly deliver to Lender a copy of each financial statement, business plan, capital expenditures plan, report and estimate received by it under the Management Agreement, and (v) promptly enforce the performance and observance of all of the covenants required to be performed and observed by Manager under the Management Agreement in a commercially reasonable manner. If Borrower shall default in the performance or observance of any material term, covenant or condition of the Management Agreement on the part of Borrower to be performed or observed, then, without limiting Lender’s other rights or remedies under this Agreement or the other Loan Documents, and without waiving or releasing Borrower from any of its Obligations hereunder or under the Management Agreement, Lender shall have the right, but shall be under no obligation, to pay any sums and to perform any act as may be appropriate to cause all the material terms, covenants and conditions of the Management Agreement on the part of Borrower to be performed or observed. In no event shall the fee payable to Manager for any Interest Period exceed the Management Fee Cap for such Interest Period and in no event shall Borrower pay or become obligated to pay to Manager, any transition or termination costs or expenses, termination fees, or their equivalent in connection with the Transfer of a Property or the termination of the Management Agreement. (b) If any one or more of the following events occurs: (i) the occurrence of an Event of Default, (ii) Manager shall be in material default under the Management Agreement beyond any applicable notice and cure period (including as a result of any gross negligence, fraud, willful misconduct or misappropriation of funds), or (iii) Manager shall become insolvent or a debtor in any bankruptcy or insolvency proceeding, then Lender shall have the right to require Borrower to replace the Manager and enter into a Replacement Management Agreement with (x) a Qualified Manager selected by Borrower that is not an Affiliate of Borrower or (y) another property manager chosen by Borrower and approved by Lender; provided, that such approval shall be conditioned upon Borrower delivering a Rating Agency Confirmation as to such property manager. If Borrower fails to select a new Qualified Manager or a replacement Manager that satisfies the conditions described in the foregoing clause (y) and enter into a Replacement Management Agreement with such Person within sixty (60) days of Lender’s demand to replace the Manager, then Lender may choose the replacement property manager provided that such replacement property manager is a Qualified Manager or satisfies the conditions set forth in the foregoing clause (y).

  • Quality Management Grantee will: 1. comply with quality management requirements as directed by the System Agency. 2. develop and implement a Quality Management Plan (QMP) that conforms with 25 TAC § 448.504 and make the QMP available to System Agency upon request. The QMP must be developed no later than the end of the first quarter of the Contract term. 3. update and revise the QMP each biennium or sooner, if necessary. ▇▇▇▇▇▇▇’s governing body will review and approve the initial QMP, within the first quarter of the Contract term, and each updated and revised QMP thereafter. The QMP must describe ▇▇▇▇▇▇▇’s methods to measure, assess, and improve - i. Implementation of evidence-based practices, programs and research-based approaches to service delivery; ii. Client/participant satisfaction with the services provided by ▇▇▇▇▇▇▇; iii. Service capacity and access to services; iv. Client/participant continuum of care; and v. Accuracy of data reported to the state. 4. participate in continuous quality improvement (CQI) activities as defined and scheduled by the state including, but not limited to data verification, performing self-reviews; submitting self-review results and supporting documentation for the state’s desk reviews; and participating in the state’s onsite or desk reviews. 5. submit plan of improvement or corrective action plan and supporting documentation as requested by System Agency. 6. participate in and actively pursue CQI activities that support performance and outcomes improvement. 7. respond to consultation recommendations by System Agency, which may include, but are not limited to the following: i. Staff training; ii. Self-monitoring activities guided by System Agency, including use of quality management tools to self-identify compliance issues; and iii. Monitoring of performance reports in the System Agency electronic clinical management system.

  • Patch Management All workstations, laptops and other systems that process and/or store County PHI or PI must have critical security patches applied, with system reboot if necessary. There must be a documented patch management process which determines installation timeframe based on risk assessment and vendor recommendations. At a maximum, all applicable patches must be installed within 30 days of vendor release.

  • Security Management The Contractor shall comply with the requirements of the DOD 5200.1-M and the DD Form 254. Security of the Contractor’s electronic media shall be in accordance with the above documents. Effective Program Security shall require the Contractor to address Information Security and Operations Security enabled by the Security Classification Guides. The Contractor’s facility must be able to handle and store material up to the Classification Level as referenced in Attachment J-01, DD Form 254.

  • NETWORK MAINTENANCE AND MANAGEMENT 38.1 The Parties will work cooperatively to implement this Agreement. The Parties will exchange appropriate information (for example, maintenance contact numbers, network information, information required to comply with law enforcement and other security agencies of the government, escalation processes, etc.) to achieve this desired result. 38.2 Each Party will administer its network to ensure acceptable service levels to all users of its network services. Service levels are generally considered acceptable only when End Users are able to establish connections with little or no delay encountered in the network. Each Party will provide a twenty four (24)-hour contact number for Network Traffic Management issues to the other’s surveillance management center. 38.3 Each Party maintains the right to implement protective network traffic management controls, such as “cancel to”, “call gapping” or seven (7)-digit and ten (10)-digit code gaps, to selectively cancel the completion of traffic over its network, including traffic destined for the other Party’s network, when required to protect the public-switched network from congestion as a result of occurrences such as facility failures, switch congestion or failure or focused overload. Each Party shall immediately notify the other Party of any protective control action planned or executed. 38.4 Where the capability exists, originating or terminating traffic reroutes may be implemented by either Party to temporarily relieve network congestion due to facility failures or abnormal calling patterns. Reroutes shall not be used to circumvent normal trunk servicing. Expansive controls shall be used only when mutually agreed to by the Parties. 38.5 The Parties shall cooperate and share pre-planning information regarding cross-network call-ins expected to generate large or focused temporary increases in call volumes to prevent or mitigate the impact of these events on the public-switched network, including any disruption or loss of service to the other Party’s End Users. Facsimile (FAX) numbers must be exchanged by the Parties to facilitate event notifications for planned mass calling events. 38.6 Neither Party shall use any Interconnection Service provided under this Agreement or any other service related thereto or used in combination therewith in any manner that interferes with or impairs service over any facilities of AT&T-21STATE, its affiliated companies or other connecting telecommunications carriers, prevents any carrier from using its Telecommunications Service, impairs the quality or the privacy of Telecommunications Service to other carriers or to either Party’s End Users, causes hazards to either Party’s personnel or the public, damage to either Party’s or any connecting carrier’s facilities or equipment, including any malfunction of ordering or billing systems or equipment. Upon such occurrence either Party may discontinue or refuse service, but only for so long as the other Party is violating this provision. Upon any such violation, either Party shall provide the other Party notice of the violation at the earliest practicable time. 38.7 AT&T TENNESSEE hereby commits to provide Disaster Recovery to CLEC according to the plan below. 38.7.1 AT&T TENNESSEE Disaster Recovery Plan 38.7.2 In the unlikely event of a disaster occurring that affects AT&T TENNESSEE’s long-term ability to deliver traffic to a CLEC, general procedures have been developed by AT&T TENNESSEE to hasten the recovery process in accordance with the Telecommunications Service Priority (TSP) Program established by the FCC to identify and prioritize telecommunication services that support national security or emergency preparedness (NS/EP) missions. A description of the TSP Program as it may be amended from time to time is available on AT&T TENNESSEE’s Wholesale – Southeast Region Web site. Since each location is different and could be affected by an assortment of potential problems, a detailed recovery plan is impractical. However, in the process of reviewing recovery activities for specific locations, some basic procedures emerge that appear to be common in most cases. 38.7.3 These general procedures should apply to any disaster that affects the delivery of traffic for an extended time period. Each CLEC will be given the same consideration during an outage, and service will be restored as quickly as possible. AT&T TENNESSEE reserves the right to make changes to these procedures as improvements become available or as business conditions dictate. 38.7.4 This plan will cover the basic recovery procedures that would apply to every CLEC.