REVISION CYCLES Sample Clauses

REVISION CYCLES. Once documentation is "in-print," Frontier will revise the printed end-user manual(s) as necessary to accurately support the Product. Frontier and Cisco will agree upon a reasonable revision cycle, determined by anticipated Product enhancements, documentation errors, and/or changes. (a) Frontier will issue Software release notes or hardware errata in a timely manner, and ship them with their related Cisco Documentation. (b) Frontier will notify Cisco within thirty (30) days of Frontier's intent to revise a printed document. (c) Document revisions will include all relevant Product enhancements and new technical information. (d) Document revisions will receive alpha, beta, and final draft reviews by Cisco. Cisco retains sole and final draft sign-off approval. (e) With each revision, Frontier will provide electronic copies of files, as specified in Section 7.3. (f) Frontier will reprint revised documentation as specified in Section 7.5.
Sample 1Sample 2
AutoNDA by SimpleDocs
REVISION CYCLES. Once documentation is "in-print," AGE will revise the printed end-user manual(s) as necessary to accurately support the Product. AGE and LMS will agree upon a reasonable revision cycle, determined by anticipated Product enhancements, documentation errors, and/or changes. (a) AGE will notify LMS within thirty (30) days of AGE's intent to revise a printed document. (b) Document revisions will include all relevant Product enhancements and new technical information. (c) Document revisions will receive alpha, beta, and final draft reviews by AGE. AGE retains sole and final draft sign-off approval. (d) With each revision, AGE will provide electronic copies of files, as specified in Section 7.3. (f) AGE will reprint revised documentation as specified in Section 7.5.
Sample 1Sample 2
REVISION CYCLES. The Customer will have two opportunities (“Revision Cycles”) per feature or milestone to bring necessary in-scope changes to the attention of the Contractor. Once a feature or milestone has been reviewed twice by the Customer any changes to that feature or milestone will be considered out-of-scope and require a change order, regardless of whether the changes would initially have been considered in-scope or not. Also, once a feature or milestone has been accepted by the Customer, any additional changes will be considered out-of-scope and require a change order, regardless of whether the changes would initially have been considered in- scope or not.
Sample 1
REVISION CYCLES. Licensor will revise the Documentation and End User Documentation manual(s) as necessary to accurately support the Software. Licensor and Cisco shall agree upon a reasonable revision cycle, determined by anticipated Software enhancements, End User Documentation and/or Documentation Errors and/or changes. 5.1. Licensor shall issue Software release notes or errata in a timely manner, and provide them to Cisco in a timely manner. 5.2. Licensor shall notify Cisco within thirty (30) days of Licensor's intent to revise the End User Documentation and/or Documentation. 5.3. End User Documentation and/or Documentation revisions shall include all relevant Software enhancements and new technical information. 5.4. End User Documentation revisions shall be reviewed by Cisco. Cisco retains sole and final draft sign-off approval. 5.5. With each revision, Licensor shall provide electronic copies of files, as specified in Section 4 of this Exhibit.
Sample 1

Related to REVISION CYCLES

  • Performance Improvement Plan timely and accurate completion of key actions due within the reporting period 100 percent The Supplier will design and develop an improvement plan and agree milestones and deliverables with the Authority 3.2 The Authority may from time to time make changes to the KPIs measured as set out in paragraph 3.1 above and shall issue a replacement version to the Supplier. The Authority shall give notice In Writing of any such change to the KPIs measured and shall specify the date from which the replacement KPIs must be used for future reports. Such date shall be at least thirty (30) calendar days following the date of the notice to the Supplier.

  • Mileage Measurement Where required, the mileage measurement for LIS rate elements is determined in the same manner as the mileage measurement for V&H methodology as outlined in NECA Tariff No. 4.

  • Flexible Work Schedule A flexible work schedule is any schedule that is not a regular, alternate, 9/80, or 4/10 work schedule and where the employee is not scheduled to work more than 40 hours in the "workweek" as defined in Subsections F. and H., below.

  • Television Equipment Recycling Program If this Contract is for the purchase or lease of covered television equipment, then Contractor certifies that it is compliance with Subchapter Z, Chapter 361 of the Texas Health and Safety Code related to the Television Equipment Recycling Program.

  • Service Specification The Parties have agreed upon the scope and specification of the Services provided under this Service Agreement in the Service Specification.

  • Flexible Work Schedules An employee may request a modification of their current work schedule to another schedule. The Employer, or its designees, may approve or deny flexible work schedules and retain the responsibility for determining exemptions from, or terminations of, flexible work schedules which adversely affect the operation of the Minnesota Judicial Branch or the level of service to the public.

  • Improvement Plan A detailed, written plan collaboratively developed between the teacher and evaluator, utilized when a teacher receives an Evaluation Rating of ineffective. The approved form for the Improvement Plan is attached to this agreement as Appendix .

  • Upgrades If this copy of the Software is an upgrade from an earlier version of the Software, it is provided to you on a license exchange basis. You agree by your installation and use of such copy of the Software to voluntarily terminate your earlier XXXX and that you will not continue to use the earlier version of the Software or transfer it to another person or entity unless such transfer is pursuant to Section 3.

  • Claims Review Population A description of the Population subject to the Claims Review.

  • Power Factor Design Criteria Developer shall design the Large Generating Facility to maintain an effective power delivery at demonstrated maximum net capability at the Point of Interconnection at a power factor within the range established by the Connecting Transmission Owner on a comparable basis, until NYISO has established different requirements that apply to all generators in the New York Control Area on a comparable basis. The Developer shall design and maintain the plant auxiliary systems to operate safely throughout the entire real and reactive power design range. The Connecting Transmission Owner shall not unreasonably restrict or condition the reactive power production or absorption of the Large Generating Facility in accordance with Good Utility Practice.

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