Block Transfer Credit Agreement Specifications Sample Clauses

Block Transfer Credit Agreement Specifications i. CC diploma and certificate program graduates must meet AU admission requirements defined as the successful completion of a two or three-year diploma program or a one-year certificate program with a minimum overall average of B (3.00 GPA) to be eligible for block transfer credit recognition. The following CC diploma program will be considered as part of the exceptional transfer credit framework: • Aboriginal Community Advocacy Program [ACA – two-year] (Appendix A summarizes credit recognition based on the transfer agreement between AU and CC)
AutoNDA by SimpleDocs

Related to Block Transfer Credit Agreement Specifications

  • Schedules of Specific Commitments 1. Each Party shall set out in a schedule the specific commitments it undertakes under Article 3 (National Treatment), Article 4 (Market Access) and Article 5 (Additional Commitments). With respect to sectors where such commitments are undertaken, each schedule shall specify:

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

  • Equipment Specifications All equipment must meet the contract specifications and all federal and State safety codes and regulations in effect at the date of manufacture. All equipment must be Original Equipment Manufacturer (OEM) equipment unless otherwise stated in the contract. Items Offered as New. All products, materials, supplies, replacement parts, and equipment offered and furnished must be new, of current manufacturer production, and must have been formally announced by the manufacturer as being commercially available, unless otherwise stated in this Contract.

  • ADDITIONAL SPECIAL CONTRACT CONDITIONS A. Special Contract Conditions revisions: the corresponding subsections of the Special Contract Conditions referenced below are replaced in their entirety with the following:

  • Assignment Amendments Waiver and Contract Complete 8.1 The Contractor may neither assign nor transfer any rights or obligations under this Agreement without the prior consent of the Authority and a fully executed Assignment Agreement, executed and approved by the same parties who executed and approved this Agreement, or their successors in office. Any attempted assignment without said consent shall be void and of no effect. The Authority may assign or otherwise transfer or dispose of all or a portion of this Agreement in its sole discretion and without the consent of the Contractor. The Contractor shall execute all consents reasonably required to facilitate such assignment or other transfer.

  • Change Orders and Contract Amendments 33.1 The Procuring Entity may at any time order the Supplier through notice in accordance GCC Clause 8, to make changes within the general scope of the Contract in any one or more of the following:

  • TIPS Sales and Supplemental Agreements If awarded, when making a sale under this awarded contract, the terms of the specific TIPS order, including but not limited to: shipping, freight, insurance, delivery, fees, bonding, cost, delivery expectations and location, returns, refunds, terms, conditions, cancellations, defects, order assistance, etc., shall be controlled by the purchase agreement (Purchase Order, Contract, AIA Contract, Invoice, etc.) (“Supplemental Agreement” as used herein) entered into between the TIPS Member Customer and Vendor only. TIPS is not a party to any Supplemental Agreement. All Supplemental Agreements shall include Vendor’s Name, as known to TIPS, and TIPS Contract Name and Number. Vendor accepts and understands that TIPS is not a legal party to TIPS Sales and Vendor is solely responsible for identifying fraud, mistakes, unacceptable terms, or misrepresentations for the specific order prior to accepting. Vendor agrees that any order issued from a customer to Vendor, even when processed through TIPS, constitutes a legal contract between the customer and Vendor only. When Vendor accepts or fulfills an order, even when processed through TIPS, Vendor is representing that Vendor has carefully reviewed the order for legality, authenticity, and accuracy and TIPS shall not be liable or responsible for the same. In the event of a conflict between the terms of this TIPS Vendor Agreement and those contained in any Supplemental Agreement, the provisions set forth herein shall control unless otherwise agreed to and authorized by the Parties in writing within the Supplemental Agreement. The Supplemental Agreement shall dictate the scope of services, the project delivery expectations, the scheduling of projects and milestones, the support requirements, and all other terms applicable to the specific sale(s) between the Vendor and the TIPS Member.

  • Contract Amendment This Contract may be amended only by a writing signed by all 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.

  • Schedule of Specific Commitments 1. Each Party shall set out in a schedule the specific commitments it undertakes under Article 106 (National Treatment), Article 000 (Xxxxxx Xxxxxx) and Article 108 (Additional Commitments). With respect to sectors where such commitments are undertaken, each Schedule shall specify: (a) terms, limitations and conditions on market access; (b) conditions and qualifications on national treatment; (c) undertakings relating to additional commitments referred to in Article 108 (Additional Commitments); and (d) where appropriate, the time-frame for implementation of such commitments and the date of entry into force of such commitments. 2. Measures inconsistent with both Articles 106 (National Treatment) and 000 (Xxxxxx Xxxxxx) are inscribed in the column relating to Article 107 (Market Access). In this case, the inscription is considered to provide a condition or qualification to Article 106 (National Treatment) as well. 3. The Parties' Schedules of Specific Commitments are set out in Annex 6 (Schedules of Specific Commitments).

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