Sparing Protocols Sample Clauses

Sparing Protocols. 2.2.1. Grid Assurance shall establish Target Inventory Levels for each Equipment Class. 2.2.2. Grid Assurance shall exercise commercially reasonable efforts to acquire and maintain quantities and types of Inventoried Spares in accordance with the Sparing Protocols; provided, however, that this Section 2.2.2 shall not restrict or prevent Grid Assurance from entering into sales of Inventoried Spares in accordance with the terms hereof that will temporarily reduce stockpiles of Inventoried Spares below applicable Target Inventory Levels. 2.2.3. Subject to Section 9.1.2(b) of this Part 2, Grid Assurance may amend the Sparing Protocols from time to time. Any amended Sparing Protocols shall become effective, and become part of the Agreement (in substitution of Schedule 2.2 previously attached hereto) upon delivery thereof by Grid Assurance to Subscriber with a written certification by Grid Assurance that such amended Sparing Protocols have been approved by the Subscriber Advisory Committee. 2.2.4. Grid Assurance shall have exclusive authority to determine: (a) the types of equipment to be procured as Inventoried Spares for each Equipment Class; (b) the Equipment Manufacturers from which Inventoried Spares will be procured; and (c) subject to Section 9.2.2(a) of this Part 2, the terms, conditions and pricing upon which Inventoried Spares are procured. Grid Assurance shall procure Inventoried Spares through competitive processes whenever reasonably practicable, as determined by Grid Assurance based on Good Utility Practice.
Sample 1
AutoNDA by SimpleDocs

Related to Sparing Protocols

  • Protocols Each party hereby agrees that the inclusion of additional protocols may be required to make this Agreement specific. All such protocols shall be negotiated, determined and agreed upon by both parties hereto.

  • Signaling protocol The Parties will interconnect their networks using SS7 signaling where Technically Feasible and available as defined in GR 905 Telcordia Standards including ISDN User Part (ISUP) for trunk signaling and TCAP for CCS-based features in the Interconnection of their networks. All Network Operations Forum (NOF) adopted standards shall be adhered to. Where available, CenturyLink signaling services to link its Signaling Transfer Points (STPs) for CLEC switches which connect to CenturyLink’s STPs via “A” links or for CLEC’s STPs to connect to CenturyLink’s STPs via “D” links which are dedicated to the transport of signaling for local Interconnection, may be ordered from the CenturyLink Tariff.

  • Protocol The attached Protocol shall be an integral part of this Agreement.

  • Random Drug Testing All employees covered by this Agreement shall be subject to random drug testing in accordance with Appendix D.

  • Review Protocol A narrative description of how the Claims Review was conducted and what was evaluated.

  • SHOP DRAWINGS, PRODUCT DATA AND SAMPLES 4.12.1 Shop Drawings are drawings, diagrams, schedules and other, data specially prepared for the Work by the Contractor or any Subcontractor, manufacturer, supplier or distributor to illustrate some portion of the Work. 4.12.2 Product Data are illustrations, standard schedules, performance charts, instructions, brochures, diagrams and other information furnished by the Contractor to illustrate a material, product or system for some portion of the Work. 4.12.3 Samples are physical examples which illustrate materials, equipment or workmanship and establish standards by which the Work will be judged. 4.12.4 The Contractor shall review, approve and submit, with reasonable promptness and in such sequence as to cause no delay in the Work or in the work of the State or any separate contractor, all Shop Drawings, Product Data and Samples required by the Contract Documents. 4.12.5 By approving and submitting Shop Drawings, Product Data and Samples, the Contractor represents that he / she has determined and verified all materials, field measurements, and field construction criteria related thereto, or will do so, and that he / she has checked and coordinated the information contained within such submittals with the requirements of the Work and of the Contract Documents. 4.12.6 The Contractor shall not be relieved of responsibility for any deviation from the requirements of the Contract Documents by the Architect's approval of Shop Drawings, Product Data or Samples under Subparagraph 2.2.7 of these General Conditions unless the Contractor has specifically informed the Architect and the State in writing of such deviation at the time of sub- mission and the Architect and the State has given written approval to the specific deviation. The Contractor shall not be relieved from responsibility for errors or omissions in the Shop Drawings, Product Data or Samples by the Architect's approval thereof. 4.12.7 The Contractor shall direct specific attention, in writing or on resubmitted Shop Drawings, Product Data or Samples, to revisions other than those requested by the Architect on previous submittals. 4.12.8 No portion of the Work requiring submission of a Shop Drawing, Product Data or Sample shall be commenced until the submittal has been approved by the Architect as provided in Subparagraph 2.2.7 of these General Conditions. All such portions of the Work shall be in accordance with approved submittals.

  • Research Use Reporting To assure adherence to NIH GDS Policy, the PI agrees to provide annual Progress Updates as part of the annual Project Renewal or Project Close-out processes, prior to the expiration of the one (1) year data access period. The PI who is seeking Renewal or Close-out of a project agree to complete the appropriate online forms and provide specific information such as how the data have been used, including publications or presentations that resulted from the use of the requested dataset(s), a summary of any plans for future research use (if the PI is seeking renewal), any violations of the terms of access described within this Agreement and the implemented remediation, and information on any downstream intellectual property generated from the data. The PI also may include general comments regarding suggestions for improving the data access process in general. Information provided in the progress updates helps NIH evaluate program activities and may be considered by the NIH GDS governance committees as part of NIH’s effort to provide ongoing stewardship of data sharing activities subject to the NIH GDS Policy.

  • Prescription Drug Plan Retail and mail order prescription drug copays for bargaining unit employees shall be as follows:

  • 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.

  • Loop Testing/Trouble Reporting 2.1.6.1 Telepak Networks will be responsible for testing and isolating troubles on the Loops. Telepak Networks must test and isolate trouble to the BellSouth portion of a designed/non-designed unbundled Loop (e.g., UVL-SL2, UCL-D, UVL-SL1, UCL-ND, etc.) before reporting repair to the UNE Customer Wholesale Interconnection Network Services (CWINS) Center. Upon request from BellSouth at the time of the trouble report, Telepak Networks will be required to provide the results of the Telepak Networks test which indicate a problem on the BellSouth provided Loop. 2.1.6.2 Once Telepak Networks has isolated a trouble to the BellSouth provided Loop, and had issued a trouble report to BellSouth on the Loop, BellSouth will take the actions necessary to repair the Loop if a trouble actually exists. BellSouth will repair these Loops in the same time frames that BellSouth repairs similarly situated Loops to its End Users. 2.1.6.3 If Telepak Networks reports a trouble on a non-designed or designed Loop and no trouble actually exists, BellSouth will charge Telepak Networks for any dispatching and testing (both inside and outside the CO) required by BellSouth in order to confirm the Loop’s working status. 2.1.6.4 In the event BellSouth must dispatch to the end-user’s location more than once due to incorrect or incomplete information provided by Telepak Networks (e.g., incomplete address, incorrect contact name/number, etc.), BellSouth will xxxx Xxxxxxx Networks for each additional dispatch required to repair the circuit due to the incorrect/incomplete information provided. BellSouth will assess the applicable Trouble Determination rates from BellSouth’s FCC or state tariffs.

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