Quality Specifications SANMINA-SCI shall comply with the quality specifications set forth in its Quality Manual, incorporated by reference herein, a copy of which is available from SANMINA-SCI upon request.
Technical Specifications The Technical Specifications furnished on the CD are intended to establish the standards for quality, performance and technical requirements for all labor, workmanship, material, methods and equipment necessary to complete the Work. When specifications and drawings are provided or referenced by the County, these are to be considered part of the Scope of Work, and to be specifically documented in the Detailed Scope of Work. For convenience, the County supplied specifications, if any, and the Technical Specifications furnished on the CD.
Quality Requirements Performance Indicator Heading Indicator (specific) Threshold Method of Measurement Frequency of monitoring Consequence of Breach QUALITY Patient Safety - Incidents I1 Number of incidents Adverse incidents include the following: clinical or non clinical adverse events that have potential to cause avoidable harm to a patient, including medical errors or adverse events related to medical devices or other equipment. Clinical or non- clinical accidents, accidental injuries to staff and members of the public, verbal, physical or psychological abuse or harassment, unusual or dangerous occurrences, damage to trust property, plant or equipment, fire or flood, security, theft or loss, near misses are identified as any event where under different circumstances significant injury or loss may have occurred Number of recorded incidents in the contract month Monthly Remedial Action Plan brought to Performance Meeting following breach; action under Module C Clause 32 if needed I2 Number of Sis Definition of SUI according to trust policy and national guidance Number of Serious Untoward Incidents reported in contract month Monthly Remedial Action Plan brought to Performance Meeting following breach; action under Module C Clause 32 if needed S1 Percentage of eligible staff received child safeguarding training at level 2 (as identified in LSCB training strategy) 95% Number received training/ Number of identified staff requiring training Monthly S2 Percentage of eligible staff received adult safeguarding awareness training at level 2 ( as identified in K&M Safeguarding Vulnerable Adults training strategy) 95% Number of staff trained/ Number of identified staff requiring training Monthly
Construction Requirements a) All Life and Safety and applicable Building Codes will be strictly enforced (i.e., tempered glass, fire dampers, exit signs, smoke detectors, alarms, etc.). Prior coordination with the Building Manager is required.
Functional Requirements Applications must implement controls that protect against known vulnerabilities and threats, including Open Web Application Security Project (OWASP) Top 10 Risks and denial of service (DDOS) attacks.
Minimum Requirements Consultant shall, at its expense, procure and maintain for the duration of the Agreement insurance against claims for injuries to persons or damages to property which may arise from or in connection with the performance of the Agreement by the Consultant, its agents, representatives, employees or subconsultants. Consultant shall also require all of its subconsultants to procure and maintain the same insurance for the duration of the Agreement. Such insurance shall meet at least the following minimum levels of coverage:
Performance Requirements 1. Neither Party may impose or enforce any of the following requirements, or enforce any commitment or undertaking, in connection with the establishment, acquisition, expansion, management, conduct or operation of an investment of an investor of a Party or of a non-Party in its territory:
Maintenance Requirements The Contractor shall ensure and procure that at all times during the Maintenance Period, the Project Highway conforms to the maintenance requirements set forth in Schedule-E (the “Maintenance Requirements”).
Service Requirements Grantee shall:
Changes to Specifications All Specifications and any changes thereto agreed to by the parties from time to time shall be in writing, dated and signed by the parties. Any change to the Packaging process shall be deemed a Specification change. No change in the Specifications shall be implemented by PCI, whether requested by Client, requested by PCI or requested or required by any Regulatory Authority, until the parties have agreed in writing to such change, the implementation date of such change, and any increase or decrease in costs, expenses or fees associated with such change (including any change to Pricing). PCI shall respond promptly to any request made by Client for a change in the Specifications, and both parties shall use commercially reasonable, good faith efforts to agree to the terms of such change in a timely manner. As soon as possible after a request is made for any change in Specifications, PCI shall notify Client of the costs associated with such change and shall provide such supporting documentation as Client may reasonably require. Client shall pay all costs associated with such agreed upon changes. If there is a conflict between the terms of this Agreement and the terms of the Specifications, this Agreement shall control. PCI reserves the right to postpone effecting changes to the Specifications, or in the case of changes requested or required by any Regulatory Authority postpone Packaging under this Agreement, until such time as the parties agree to and execute the required written amendment.