Budget Envelopes and Target Prices Document Sample Clauses

Budget Envelopes and Target Prices Document. (A) The SoS shall be responsible at all times for maintaining an up-to-date version of the Budget Envelopes and Target Prices Document. Where any Budget Envelope or Target Price is agreed and/or revised in accordance with this Clause 31, the SoS shall produce a revised version of the Budget Envelopes and Target Prices Document (for the purposes of this Clause 31, the “Revised Budget Envelopes and Target Prices Document”) incorporating the details of such amendments with the next sequential issue marked on each page together with a cover page clearly named with the issue number and date of issue and a record of changes from the preceding version.
AutoNDA by SimpleDocs
Budget Envelopes and Target Prices Document 

Related to Budget Envelopes and Target Prices Document

  • EODUF Packing Specifications 7.3.1 The data will be packed using ATIS EMI records. A pack will contain a minimum of one (1) message record or a maximum of ninety-nine thousand nine hundred and ninety-nine (99,999) message records plus a pack header record and a pack trailer record. One transmission can contain a maximum of ninety-nine (99) packs and a minimum of one (1) pack.

  • ODUF Packing Specifications 6.3.1 The data will be packed using ATIS EMI records. A pack will contain a minimum of one (1) message record or a maximum of ninety-nine thousand nine hundred and ninety-nine (99,999) message records plus a pack header record and a pack trailer record. One transmission can contain a maximum of ninety-nine (99) packs and a minimum of one (1) pack.

  • Packing Specifications 7.3.1 A pack will contain a minimum of one message record or a maximum of 99,999 message records plus a pack header record and a pack trailer record. One transmission can contain a maximum of 99 packs and a minimum of one pack.

  • Table 7b - Other milestones and targets Reference Number Select stage of the lifecycle Please select target type from the drop-down menu Description (500 characters maximum) Is this a collaborative target? Baseline year Baseline data Yearly milestones (numeric where possible, however you may use text) Commentary on your milestones/targets or textual description where numerical description is not appropriate (500 characters maximum)

  • Technical Standards Applicable to a Wind Generating Plant i. Low Voltage Ride-Through (LVRT) Capability A wind generating plant shall be able to remain online during voltage disturbances up to the time periods and associated voltage levels set forth in the standard below. The LVRT standard provides for a transition period standard and a post-transition period standard.

  • Budget Schedule Subrecipient agrees that the expenditures of any and all funds under this Contract will be in accordance with the Budget Schedule, a copy of which is attached hereto as Attachment C, and which by this reference is incorporated herein and made a part hereof as if fully set forth.

  • Billing Specifications 55.6.1 The Parties agree that billing requirements and outputs will be consistent with the Ordering & Billing Form (OBF) and also with Telcordia Technologies Billing Output Specifications (BOS).

  • Background and Narrative of Budget Reductions 2. Assumptions Used in the Deficit Reduction Plan: - EBF and Estimated New Tier Funding: - Equal Assessed Valuation and Tax Rates: - Employee Salaries and Benefits: - Short and Long Term Borrowing: - Educational Impact: - Other Assumptions: - Has the district considered shared services or outsourcing (Ex: Transportation, Insurance) If yes please explain: ESTIMATED LIMITATION OF ADMINISTRATIVE COSTS (School Districts Only) (For Local Use Only)

  • Escrow Format Specification 3.1. Deposit’s Format. Registry objects, such as domains, contacts, name servers, registrars, etc. will be compiled into a file constructed as described in draft-xxxxx-xxxxxxx-registry-data-escrow, see Part A, Section 9, reference 1 of this Specification and draft-xxxxx-xxxxxxx-dnrd-objects-mapping, see Part A, Section 9, reference 2 of this Specification (collectively, the “DNDE Specification”). The DNDE Specification describes some elements as optional; Registry Operator will include those elements in the Deposits if they are available. If not already an RFC, Registry Operator will use the most recent draft version of the DNDE Specification available at the Effective Date. Registry Operator may at its election use newer versions of the DNDE Specification after the Effective Date. Once the DNDE Specification is published as an RFC, Registry Operator will implement that version of the DNDE Specification, no later than one hundred eighty (180) calendar days after. UTF-8 character encoding will be used.

  • MSAA Indicator Technical Specification Document This Agreement shall be interpreted with reference to the MSAA Indicator Technical Specifications document.

Time is Money Join Law Insider Premium to draft better contracts faster.