Job Postings and Applications If a vacancy or a new job is created for which union personnel might reasonably be recruited, the following shall apply:
(a) If the vacancy or new job has a duration of thirty (30) calendar days or more, the vacancy or new job including salary range, a summary of the job description, the required qualifications, the hours of work, including start and stop times and days off, the work area and the commencement date shall, before being filled, be posted for a minimum of seven (7) calendar days, in a manner which gives all employees access to such information, provided that no employees shall be entitled to relieve other regular employees under this clause on more than two (2) occasions in one calendar year unless the Employer and the Union otherwise agree in good faith.
(b) Notwithstanding (a) above, if a temporary absence is one of less than ninety (90) calendar days, the work of the absent employee may be performed by employees working in float pool positions, where float pools exist.
(c) Notwithstanding (a) above, if the vacancy is a temporary one of less than ninety (90) calendar days and the work is not being performed by a float employee, the position shall not be posted and instead shall be filled as follows:
(i) where practicable by qualified regular employees who have indicated in writing their desire to work in such position consistent with the requirements of Article 14. Should a vacancy under this Article result in backfilling of more than one (1) vacancy (including the initial vacancy) the second (2nd) vacancy may be filled by an employee registered for casual work unless the Employer and the Union agree otherwise in good faith. If the application of this paragraph requires the Employer to pay overtime to the employee pursuant to Article 19, the proposed move shall not be made. An employee who accepts work under this provision is not eligible to work in another Article 16.01(c) assignment that conflicts with the accepted one. Probationary employees and employees undergoing a qualifying period shall not be considered for a 16.01(c) assignment in a different classification.
(ii) by employees registered for casual work in accordance with the casual addendum.
(iii) in cases of unanticipated or unplanned temporary absences, such temporary absence may first be filled under (c)(ii) for a period of up to seven (7) days.
(d) A part-time employee who has accepted a casual assignment which conflicts with a temporary vacancy referred to in paragraph (c)(i) above shall be considered unavailable for such temporary vacancy. A part-time employee who has accepted a temporary vacancy referred to in paragraph (c)(i) above which conflicts with a casual assignment shall be considered unavailable for such casual assignment. Where an employee declines an offer to work under (c)(i) the Employer need not offer the work again to that employee under (c)(ii), if she/he is also registered for casual work.
(e) Existing local agreements will be in force and effect (including termination clauses) unless changed by mutual agreement by the parties at the local level.
(f) Where the local agreement covering access to work by part-time employees (former “15.01c”) does not contain a termination clause, the agreement may be terminated on giving of six (6) months’ notice by either party.
(g) By mutual agreement, the parties may vary the job posting process set out in Article 16.01.
Scope and Application This Appendix will apply to all work undertaken within the Employer’s Workshop(s) by employees mainly engaged at the Workshop.
License Type Your license to a Product will be under a Named User or CPU license type, as specified on an order. Each Named User license to a Product entitles a Named User to access and use that Product in one production environment and up to two non-production environments. Each CPU license to a Product entitles you to assign the Product to a single CPU in one production environment and up to two non-production environments, for use in support of an unspecified number of Named Users.
Purpose and Application This document (“DPA”) is incorporated into the Agreement and forms part of a written (including in electronic form) contract between SAP and Customer. This DPA applies to Personal Data processed by SAP and its Subprocessors in connection with its provision of the Cloud Service. This DPA does not apply to non-production environments of the Cloud Service if such environments are made available by SAP, and Customer shall not store Personal Data in such environments.
License Types (a) A Team License shall mean a subscription license that provides a limited number of licenses to a set amount of developers for a named Customer. Customer must procure enough active licenses for each individual who has Programmatic Access. A Team License only grants rights to a named Customer and does not extend any right, in any form, to any parent or subsidiary company of Customer. A Team License cannot be used as a floating license.
(b) A Project License shall mean a subscription license which covers one named Customer application. The license fees are based on the total number of developers working on a named project, regardless of whether such developers are directly using the Licensed Product. For the purposes of pricing and license administration, a “Project Group” is deemed to be a distinct Customer software team within a Customer’s business unit that works towards a distinct business purpose for the benefit of a single application. Customer is required to identify the name of each such Project Group to Syncfusion; such name must be unambiguous in nature. It is acknowledged and agreed by Customer that each identified Project Group shall exist for a valid business purpose and not just as a means for consolidating software licenses to minimize license fees that are otherwise due. If, in the sole opinion of Syncfusion, multiple Customer teams would each individually meet the above definition of a Project Group, such multiple teams shall not be combined for the purpose of consolidating licenses under a single Project Group. Customer is responsible for providing information about each such Project Group to Syncfusion. By entering into this Agreement, Customer represents that after the effective date, it will not withhold information that Syncfusion requires to properly license each such Project Group, and further agrees that any misrepresentation in this regard constitutes a material breach of this Agreement.
(c) A Division License shall mean a subscription license which will cover one named Division and allow for development work on more than one project within such Division. A Division shall mean a business unit within Customer’s organization that works towards a distinct business purpose. Customer is required to identify the name of such Division to Syncfusion; such name must be unambiguous in nature. License fee determinations will be at the sole discretion of Syncfusion and be based on such factors including, but not limited to, Customer’s Division size, developer count, and the scope of the Division’s business purpose. By entering into this Agreement, Customer acknowledges that it is responsible for providing information about the named Customer Division to Syncfusion sufficient for Syncfusion to price the Division License, and Customer represents that it will not withhold information that Syncfusion requires to properly license each such named Customer division, and further agrees that any misrepresentation in this regard constitutes a material breach of this Agreement.
(d) A Global License shall mean a subscription license for all development for a named Customer, where the license fees are based on the overall size of a named Customer. A Global License only grants rights to a named Customer and does not extend any right, in any form, to any parent or subsidiary company of Customer.
(e) A Retail License shall mean a single named user, non-transferable license to use the Licensed Product. Retail Licenses will only made available to Customers in Syncfusion’s sole discretion and only when the number of such End-Users is finite and readily ascertainable. Accordingly, Syncfusion will make a determination as to whether or not the provision of Retail Licenses is appropriate under the circumstances applicable to any given Customer, and Syncfusion reserves the right, in its sole discretion, to refuse to make available Retail Licenses to a Customer and instead require a given Customer to procure a Project License, Division License, or Global License as circumstances dictate. A Retail License only grants rights to a named Customer and does not extend any right, in any form, to any parent or subsidiary company of Customer.