NOTICE TO PROCEED AND SCHEDULE The CONSULTANT shall begin the work to be performed under this Contract only upon receipt of the written notice to proceed from the LPA, and shall deliver the work to the LPA in accordance with the schedule contained in Appendix "C" which is herein attached to and made an integral part of this Contract.
DISTRIBUTION OF CONTRACTOR PRICE LIST AND CONTRACT APPENDICES Contractor shall provide Authorized Users with electronic copies of the Contract, including price lists and Appendices, upon request. OGS CENTRALIZED CONTRACT MODIFICATIONS Contract Updates will be handled as provided in Appendix C – Contract Modification Procedures.
Weekend Scheduling It is the policy of the Employer to schedule those nurses who so desire every other weekend off, with the exception of those nurses who have signed an authorization to work consecutive weekends. Nurses who have volunteered to work consecutive weekends may withdraw such authorization upon two (2) weeks’ written notice prior to the date a new schedule must be posted.
APPENDIX 1 TO THE STANDARD CONTRACTUAL CLAUSES Data exporter The data exporter is the entity identified as “Customer” in the DPA Data importer The data importer is Amazon Web Services, Inc., a provider of web services. Data subjects Data subjects are defined in Section 1.3 of the DPA. Categories of data The personal data is defined in Section 1.3 of the DPA.
Dispatch and Scheduling 4.3.1 The Power Producer shall be required to schedule its power as per the applicable Regulations / Requirements / Guidelines of CERC / GERC / SLDC / RLDC and maintain compliance to the Grid Code requirements and directions, as specified by SLDC / RLDC from time to time. Any deviation from the schedule will attract the provisions of applicable Regulation / Guidelines / Directions and any financial implication on account of this shall be to the account of the Power Producer.
Second Schedule Second Schedule THIS AGREEMENT under seal made the twenty-seventh day of October One thousand nine hundred and sixty-four BETWEEN THE HONOURABLE XXXXX XXXXX, M.L.A. Premier and Treasurer of the State of Western Australia acting for and on behalf of the said State and instrumentalities thereof from time to time (hereinafter called “the State”) of the one part and HAMERSLEY IRON PTY. LIMITED a company incorporated under the Companies Xxx 0000 of the State of Victoria and having its registered office and principal place of business in that State at 00 Xxxxxxx Xxxxxx Melbourne and its registered office in the State of Western Australia at 37 Saint George’s Terrace Perth (hereinafter called “the Company” which expression will include the successors and assigns of the Company including where the context so admits the assignees and appointees of the Company under clause 20 of the agreement hereinafter referred to) of the other part.
Per-‐Registrar Transactions Report This report shall be compiled in a comma separated-‐value formatted file as specified in RFC 4180. The file shall be named “gTLD-‐transactions-‐yyyymm.csv”, where “gTLD” is the gTLD name; in case of an IDN-‐TLD, the A-‐label shall be used; “yyyymm” is the year and month being reported. The file shall contain the following fields per registrar: Field # Field name Description 01 registrar-‐name Registrar’s full corporate name as registered with IANA 02 iana-‐id For cases where the registry operator acts as registrar (i.e., without the use of an ICANN accredited registrar) 9999 should be used, otherwise the sponsoring Registrar IANA id should be used as specified in xxxx://xxx.xxxx.xxx/assignments/registrar-‐ids 03 total-‐domains total domain names under sponsorship in any EPP status but pendingCreate that have not been purged 04 total-‐nameservers total name servers (either host objects or name server hosts as domain name attributes) associated with domain names registered for the TLD in any EPP status but pendingCreate that have not been purged 05 net-‐adds-‐1-‐yr number of domains successfully registered (i.e., not in EPP pendingCreate status) with an initial term of one (1) year (and not deleted within the add grace period). A transaction must be reported in the month the add grace period ends.
Unit Weekend Schedule A unit weekend schedule may be developed in order to meet the Hospital’s need for weekend staff, and individual nurses’ preference for a weekend work schedule. A unit weekend schedule is defined as a schedule in which a full-time nurse works a weekly average of thirty (30) hours and is paid for 37.5 hours at her or his regular straight time hourly rate. The schedule must include two 11.25 hour tours, which fall within a weekend period as determined by the Hospital and the Association. A nurse working a weekend schedule will work every weekend except as provided for in the provisions below. If the Hospital and the Association agree to a unit weekend schedule, the introduction of that schedule and the manner in which the position(s) are filled, shall be determined by the local parties and recorded in the Appendix of Local Provisions. This unit schedule may be discontinued by either party with notice as determined within the Appendix of Local Provisions. The opportunity for an individual nurse to discontinue this schedule shall be resolved by the local parties:
APPENDIX 2 TO THE STANDARD CONTRACTUAL CLAUSES This Appendix forms part of the Clauses and must be completed by the parties. Description of the technical and organisational security measures implemented by the data importer in accordance with Clauses 4(d) and 5(c) (or document/legislation attached):
SALES AND ORDER PROCESSING CHARGE Contractor shall sell its products to END USERS based on the pricing and terms of this Agreement. H-GAC will invoice Contractor for the applicable order processing charge when H-GAC receives notification of an END USER order. Contractor shall remit to H-GAC the full amount of the applicable order processing charge, after delivery of any product or service and subsequent END USER acceptance. Payment of the Order Processing Charge shall be remitted from Contractor to H-GAC, within thirty (30) calendar days or ten (10) business days after receipt of an END USER’s payment, whichever comes first, notwithstanding Contractor’s receipt of invoice. For sales made by Contractor based on this Agreement, including sales to entities without Interlocal Agreements, Contractor shall pay the applicable order processing charges to H-GAC. Further, Contractor agrees to encourage entities who are not members of H-GAC’s Cooperative Purchasing Program to execute an H-GAC Interlocal Agreement. H-GAC reserves the right to take appropriate actions including, but not limited to, Agreement termination if Contractor fails to promptly remit the appropriate order processing charge to H-GAC. In no event shall H-GAC have any liability to Contractor for any goods or services an END USER procures from Contractor. At all times, Contractor shall remain liable to pay to H-GAC any order processing charges on any portion of the Agreement actually performed, and for which compensation was received by Contractor.
