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.
Construction Progress Schedule A schedule indicating proposed activity sequences and durations, milestone dates for receipt and approval of pertinent information, preparation, submittal, and processing of Shop Drawings and Samples, delivery of materials or equipment requiring long-lead time procurement, and proposed date(s) of Material Completion and Occupancy and Final Completion. The schedule will be developed to represent the sixteen or seventeen CSI Specification Divisions. It shall have a minimum number of activities as required to adequately represent to Owner the complete scope of work and define the Project’s critical path and associated activities. If the Project is to be phased, then each individual Phase should be identified from start through completion of the overall Project and should be individually scheduled and described, including any Owner’s occupancy requirements and showing portions of the Project having occupancy priority. The format of the schedule will have dependencies indicated on a monthly grid identifying milestone dates such as construction start, phase construction, structural top out, dry-in, rough-in completion, metal stud and drywall completion, equipment installation, systems operational, Material Completion and Occupancy Date, final inspection dates, Punchlist, and Final Completion date.
Construction Progress Schedule; Overall Project Schedule The Contractor shall submit for review by the Design Professional and approval by the Owner a Construction Progress Schedule based upon the Design Professional’s Preliminary Design and Construction Schedule and prepared using a CPM (Critical Path Method) process within sixty days after the Effective Date of the Contract, utilizing a full-featured software package in a form satisfactory to the Design Professional and Owner, showing the dates for commencement and completion of the Work required by the Contract Documents, including coordination of mechanical, plumbing, and electrical disciplines, as well as coordination of the various subdivisions of the Work within the Contract. Milestones must be clearly indicated and sequentially organized to identify the critical path of the Project. The Construction Schedule will be developed to represent the CSI specification divisions. It shall have the minimum number of activities required to adequately represent to the Owner the complete scope of Work and define the Project’s (and each Phase’s if phased) critical path and associated activities. The format of the Construction Progress Schedule will have dependencies indicated on a monthly grid identifying milestone dates such as construction start, phase construction, structural top out, dry-in, rough-in completion, metal stud and drywall completion, equipment installation, systems operational, inspections for Material Completion and Occupancy Date, and Final Completion Date. The Contractor shall submit, along with the Construction Progress Schedule, the Submittal Schedule for approval by the Design Professional, correlating the associated approval dates for the documents with the Construction Progress Schedule. Upon recommendation by the Design Professional and approval by the Owner, the Construction Progress Schedule shall become the Overall Project Schedule, which shall be utilized by the Design Professional, Owner and Contractor. The Contractor must provide the Design Professional and the Owner with monthly updates of the Overall Project Schedule indicating completed activities and any changes in sequencing or activity durations, including approved change orders. See also Article 3.3.5.
Supervisory Control and Data Acquisition (SCADA) Capability The wind plant shall provide SCADA capability to transmit data and receive instructions from the ISO and/or the Connecting Transmission Owner for the Transmission District to which the wind generating plant will be interconnected, as applicable, to protect system reliability. The Connecting Transmission Owner for the Transmission District to which the wind generating plant will be interconnected and the wind plant Developer shall determine what SCADA information is essential for the proposed wind plant, taking into account the size of the plant and its characteristics, location, and importance in maintaining generation resource adequacy and transmission system reliability in its area.
Summer Session A. All ASEs employed in the Summer Session shall receive the same general range adjustment as ASEs received in the preceding Fall term.
Punch List If, at any time after the Project has been Physically Completed, there shall exist any item or items requiring completion or correction, then the Developer agrees to use all reasonable diligence to complete or correct such item or items so that each conforms to the Final Plans. The parties shall make a Punch-List of the items requiring completion or correction (the "Punch List"). Each item on the Punch-List shall be assigned a reasonable value based upon the reasonable cost of completion or correction of the same or such other value as may be required by the Owner's lender ("Punch-List Amount"). The Developer shall give its written undertaking to complete each such item within forty-five (45) days (or such other period of time as is mutually agreed upon by the parties).
Supplemental JBoss Software Conditions Software Access and Software Maintenance for Supplemental JBoss Software is intended and available for Development Purposes only and for up to 25 users for each 16 Core Band Subscription of Red Hat JBoss Middleware Software that you purchased. If you deploy or use the Supplemental JBoss Software for Production Purposes or for more than 25 users, you agree to purchase the appropriate Software Subscriptions for each Unit that you deploy or use. Red Hat’s Open Source Assurance Program applies only to the Red Hat JBoss Middleware Software Subscription that you purchased (such as Red Hat JBoss Enterprise Application Platform in the example above) and does not apply to Supplemental JBoss Software. JBoss xPaaS Subscriptions (defined below) are not considered Supplemental JBoss Software. Each installation and use of JBoss xPaaS Subscriptions Software for either Development Purposes or Production Purposes is a Unit and requires a paid Software Subscription.
ROAD GRADE AND ALIGNMENT STANDARDS Purchaser shall follow these standards for road grade and alignment except as designed: Grade and alignment must have smooth continuity, without abrupt changes in direction. Maximum grades may not exceed 18 percent favorable and 12 percent adverse. Minimum curve radius is 60 feet at centerline. Maximum grade change for sag vertical curves is 5% in 100 feet. Maximum grade change for crest vertical curves is 4% in 100 feet.
Course Curriculum, Instruction, and Grading X. Xxxx College courses offered as dual credit, regardless of where they are taught, follow the same syllabus, course outline, textbook, grading method, and other academic policies as the courses outlined in the Hill College catalog.
Completion of Punch List items 14.4.1 All items in the Punch List shall be completed by the Concessionaire within 90 (ninety) days of the date of issue of the Provisional Certificate and for any delay thereafter, other than for reasons solely attributable to the Authority or due to Force Majeure, the Authority shall be entitled to recover Damages from the Concessionaire to be calculated and paid for each day of delay until all items are completed, at the lower of (a) 0.1% (zero point one per cent) of the Performance Security, and (b) 0.2% (zero point two per cent) of the cost of completing such items as estimated by the Independent Engineer. Subject to payment of such Damages, the Concessionaire shall be entitled to a further period not exceeding 120 (one hundred and twenty) days for completion of the Punch List items. For the avoidance of doubt, it is agreed that if completion of any item is delayed for reasons solely attributable to the Authority or due to Force Majeure, the completion date thereof shall be determined by the Independent Engineer in accordance with Good Industry Practice, and such completion date shall be deemed to be the date of issue of the Provisional Certificate for the purposes of Damages, if any, payable for such item under this Clause 14.4.1.
