File Format Changes Sample Clauses

File Format Changes. You shall have thirty (30) days from receipt of notice from UPS of a change to the File Format in which to implement such change(s).
AutoNDA by SimpleDocs

Related to File Format Changes

  • File Format Standard Registry Operator (optionally through the CZDA Provider) will provide zone files using a subformat of the standard Master File format as originally defined in XXX 0000, Section 5, including all the records present in the actual zone used in the public DNS. Sub-­‐format is as follows:

  • Project Changes 1.8.1. All changes shall be administered per the UGC.

  • Program Changes Contractor agrees to inform the County of any alteration in program or service delivery at least thirty (30) days prior to the implementation of the change, or as soon as reasonably feasible.

  • Shift Changes When an employee is assigned to a specific shift and that assignment is changed, the employee shall be given seven (7) calendar days’ notice prior to the change.

  • Contract Changes Changes may not be made in the terms and conditions of this contract without the agreement and written permission of the Director of Housing.

  • SCOPE CHANGES The Commissioner reserves the right to require, by written order, changes to the scope of the Contract, by altering, adding to or deducting from the Bid Specifications, such changes to be within the general scope of the Contract. If any such change causes an increase or decrease in the cost of, or the time required for, performance of any part of the work under the Contract, whether or not changed by the order, the Commissioner shall, upon notice from Contractor as hereafter stated, make an equitable adjustment in the Contract price, the delivery schedule or both and shall modify the Contract. The Contractor must assert its right to an adjustment under this clause within thirty days from the date of receipt of the written order. However, if the Commissioner decides that the facts justify it, the Commissioner may provide an adjustment without receipt of a proposal. Failure to agree to any adjustment shall be a dispute under the Disputes clause, provided, however, that nothing in this clause shall excuse the Contractor from proceeding with the Contract as changed.

  • Change Order Formats Formats for Lump Sum Change Orders and for Change Orders based upon either a force account or upon unit pricing with an indeterminate number of units are in Section 7, Forms.

  • Demographic, Classification and Wage Information XXXXXX agrees to coordinate the accumulation and distribution of demographic, classification and wage data, as specified in the Letter of Understanding dated December 14, 2011, to CUPE on behalf of Boards of Education. The data currently housed in the Employment Data and Analysis Systems (EDAS) will be the source of the requested information.

  • Classification Changes When the University determines that a revision of a class specification for positions covered by this agreement is needed, and such revision affects the collective bargaining unit designation, the University shall notify AFSCME in writing of the proposed change. AFSCME shall notify the University, in writing, within fifteen (15) days of receipt of the proposed changes, of any comments it has concerning the proposed changes or of its desire to discuss the proposed changes.

  • Report Structure Provides an analysis of each error type (by error code). The report is in descending order by count of each error code and provides the following: • Error Type (by error code) • Count of each error type • Percent of each error type • Cumulative percent • Error Description • CLEC Caused Count of each error code • Percent of aggregate by CLEC caused count • Percent of CLEC caused count • BellSouth Caused Count of each error code • Percent of aggregate by BellSouth caused count • Percent of BellSouth by BellSouth caused count. Data Retained Relating to CLEC Experience Relating to BellSouth Performance • Report Month • Total Number of Lsrs Received • Total Number of Errors by Type (by Error Code) - CLEC caused error • Report Month • Total Number of Errors by Type (by Error Code) - BellSouth System Error SQM Disaggregation - Analog/Benchmark SQM Level of Disaggregation SQM Analog/Benchmark • Not Applicable • Not Applicable SEEM Measure SEEM Measure No Tier I Tier II O-5: Flow-Through Error Analysis SEEM Disaggregation - Analog/Benchmark SEEM Disaggregation SEEM Analog/Benchmark • Not Applicable • Not Applicable O-6: CLEC LSR Information O-6: CLEC LSR Information Definition A list with the flow through activity of LSRs by CC, PON and Ver, issued by each CLEC during the report period. Exclusions • Fatal Rejects • LSRs submitted manually Business Rules The CLEC mechanized ordering process includes all LSRs, including supplements (subsequent versions) which are submitted through one of the three gateway interfaces (TAG, EDI, and LENS), that flow through and reach a status for a FOC to be issued. The CLEC mechanized ordering process does not include LSRs which are submitted manually (for example, fax and courier). Calculation Not Applicable

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