Reliability Requirements. Unless otherwise specifically provided for herein, the Parties acknowledge that Customer and NCPA are both individually responsible for compliance with the WECC and NERC Reliability Standards and criteria applicable to the functions for which each Party are respectively registered with NERC. The references to WECC and NERC Reliability Standards, if any, throughout this Agreement do not make any alteration or enlargement of the requirements or standards applicable to each Party beyond their individual registrations with NERC; provided, however, NCPA shall perform certain functions on behalf of, or in coordination with, Customer pursuant to Appendix F.
Reliability Requirements. System to function normally after 500 use-cycles (See appendix I for details of use cycle) minimum. Warranty (parts and labor) period is one year from date of shipment from original distributor. Warranty period does not extend on handpiece or motor controller repaired under warranty except for replaced components (which are covered for one year). MTBF to be determined to establish PM cycles.
Reliability Requirements. During the term hereof, the parties agree to cooperate in good faith with each other and provide such data and information, including service and reliability data, statistics and analyses relating to failure rates, failure mechanisms and repair times to one another on a quarterly basis or as otherwise reasonably requested by either party as necessary or appropriate to determine whether and to what extent the Products satisfy GenMark’s reasonable reliability requirements (which shall be consistent with industry standards). All such information shall be subject to the confidentiality provisions of Article VII hereof. If one or more Product(s) fails to achieve such reliability requirements during the term hereof, the parties agree to mutually perform an analysis to determine the root cause(s) for such failure(s).
Reliability Requirements. As used herein, “Reliability Requirements” shall mean the document attached as Exhibit C, approved by both Parties, setting forth the reliability requirements necessary to meet the Product Requirements Document. After the Effective Date, the Reliability Requirements shall not be modified without each party’s specific written consent. The parties will prepare a more detailed Reliability Program Plan during Phase 1, which shall cover all development related activities in detail. STRATEC and Gen-Probe shall update the Reliability Program Plan during the development to include learnings from prior phase(s) and cover the post launch reliability activities.
Reliability Requirements. Measurement of product performance will be based on data obtained in the field as described in section 3.4.2 of this Exhibit. Solectron is also responsible for meeting NCR’s Reliability, Availability, Serviceability, Usability, and Interchangeability (RASUI) requirements as defined below.
Reliability Requirements. As used herein, “Reliability Requirements” shall mean the document attached as Exhibit C, approved by both Parties, setting forth the reliability requirements necessary to meet the Product Requirements Document. After the Effective Date, the Reliability Requirements shall not be modified without each party’s specific written consent.
Reliability Requirements. 4.1 Insertions The card and insert can be inserted, read and written 20,000 times.
Reliability Requirements. [Req.73] Under stated conditions the aggregation infrastructure needs to run the processes constantly without any breakdowns. Upgrades and maintenance of the components of the infrastructure must be possible without downtime of the whole infrastructure. [Req.74] Backups must be able to run automatically and regularly, to ensure that after breakdown content will be restored with no loss of information and at a speed limited only by the hardware performance. Worst-case is the loss of Raw Data or Enriched Data of the last week (worst-case scenario is therefore that the processing work of one week needs to be rescheduled). Besides computational resources such a process would only involve minimal human resources – all the mapping/normalization specifications must be backup on a daily basis. [Req.75] The Raw Data Repository, as being the reference data, needs to be incrementally backup on a daily basis.
Reliability Requirements. The City and ETA recognize that no system will run perfectly all the time but that the system must be reliable and when there are failures or delays those issues must be addressed promptly. The parties, therefore, have agreed to the reliability requirements and performance guarantees outlined in the Service Level Agreement, attached to the Agreement as Exhibit B.
Reliability Requirements. I3.1 Any prolonged data interruptions shall be Promptly reported to the other Partys’ Controlling Authority and such report shall identify the nature of the problem, points affected, a nd a nticipated duration of the problem.
