Trunk Types 2.2.1 In interconnecting their networks pursuant to this Attachment, the Parties will use, as appropriate, the following separate and distinct trunk groups: 2.2.1.1 Interconnection Trunks for the transmission and routing of Reciprocal Compensation Traffic, translated LEC IntraLATA toll free service access code (e.g., 800/888/877) traffic, and IntraLATA Toll Traffic, between their respective Telephone Exchange Service Customers, Tandem Transit Traffic, and, Measured Internet Traffic, all in accordance with Sections 5 through 8 of this Attachment; 2.2.1.2 Access Toll Connecting Trunks for the transmission and routing of Exchange Access traffic, including translated InterLATA toll free service access code (e.g., 800/888/877) traffic, between Ymax Telephone Exchange Service Customers and purchasers of Switched Exchange Access Service via a Verizon access Tandem in accordance with Sections 9 through 11 of this Attachment; and 2.2.1.3 Miscellaneous Trunk Groups as mutually agreed to by the Parties, including, but not limited to: (a) choke trunks for traffic congestion and testing; and, (b) untranslated IntraLATA/InterLATA toll free service access code (e.g. 800/888/877) traffic. 2.2.2 Other types of trunk groups may be used by the Parties as provided in other Attachments to this Agreement (e.g., 911/E911 Trunks) or in other separate agreements between the Parties (e.g., directory assistance trunks, operator services trunks, BLV/BLVI trunks or trunks for 500/555 traffic). 2.2.3 In accordance with the terms of this Agreement, the Parties will deploy One-Way Interconnection Trunks (trunks with traffic going in one direction, including one-way trunks and uni-directional two-way trunks) and/or Two-Way Interconnection Trunks (trunks with traffic going in both directions). 2.2.4 Ymax shall establish, at the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA, separate Interconnection Trunk group(s) between such POI(s) and each Verizon Tandem in a LATA with a subtending End Office(s) to which Ymax originates calls for Verizon to terminate. 2.2.5 In the event the volume of traffic between a Verizon End Office and a technically feasible Point of Interconnection on Verizon’s network in a LATA, which is carried by a Final Tandem Interconnection Trunk group, exceeds (a) the Centium Call Seconds (Hundred Call Seconds) busy hour equivalent of one (1) DS1 at any time; (b) 200,000 minutes of use for a single month; and/or; (c) 600 busy hour Centium Call Seconds (BHCCS) of use for a single month: (i) if One-Way Interconnection Trunks are used, the originating Party shall promptly establish new or augment existing End Office One-Way Interconnection Trunk groups between the Verizon End Office and the technically feasible Point of Interconnection on Verizon’s network; or,
Project Specific Milestones In addition to the milestones stated in Section 212.5 of the Tariff, as applicable, during the term of this ISA, Interconnection Customer shall ensure that it meets each of the following development milestones: 6.1 Substantial Site work completed. On or before December 31, 2020 Interconnection Customer must demonstrate completion of at least 20% of project site construction. At this time, Interconnection Customer must submit to Interconnected Transmission Owner and Transmission Provider initial drawings, certified by a professional engineer, of the Customer Interconnection Facilities. 6.2 Delivery of major electrical equipment. On or before December 31, 2021, Interconnection Customer must demonstrate that all generating units have been delivered to Interconnection Customer’s project site.
Laboratory Testing All laboratories selected by UPS Freight for analyzing Controlled Substances Testing will be HHS certified.
SHOP DRAWINGS, PRODUCT DATA AND SAMPLES 4.12.1 Shop Drawings are drawings, diagrams, schedules and other, data specially prepared for the Work by the Contractor or any Subcontractor, manufacturer, supplier or distributor to illustrate some portion of the Work. 4.12.2 Product Data are illustrations, standard schedules, performance charts, instructions, brochures, diagrams and other information furnished by the Contractor to illustrate a material, product or system for some portion of the Work. 4.12.3 Samples are physical examples which illustrate materials, equipment or workmanship and establish standards by which the Work will be judged. 4.12.4 The Contractor shall review, approve and submit, with reasonable promptness and in such sequence as to cause no delay in the Work or in the work of the State or any separate contractor, all Shop Drawings, Product Data and Samples required by the Contract Documents. 4.12.5 By approving and submitting Shop Drawings, Product Data and Samples, the Contractor represents that he / she has determined and verified all materials, field measurements, and field construction criteria related thereto, or will do so, and that he / she has checked and coordinated the information contained within such submittals with the requirements of the Work and of the Contract Documents. 4.12.6 The Contractor shall not be relieved of responsibility for any deviation from the requirements of the Contract Documents by the Architect's approval of Shop Drawings, Product Data or Samples under Subparagraph 2.2.7 of these General Conditions unless the Contractor has specifically informed the Architect and the State in writing of such deviation at the time of sub- mission and the Architect and the State has given written approval to the specific deviation. The Contractor shall not be relieved from responsibility for errors or omissions in the Shop Drawings, Product Data or Samples by the Architect's approval thereof. 4.12.7 The Contractor shall direct specific attention, in writing or on resubmitted Shop Drawings, Product Data or Samples, to revisions other than those requested by the Architect on previous submittals. 4.12.8 No portion of the Work requiring submission of a Shop Drawing, Product Data or Sample shall be commenced until the submittal has been approved by the Architect as provided in Subparagraph 2.2.7 of these General Conditions. All such portions of the Work shall be in accordance with approved submittals.
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.
Project/Milestones Taxpayer provides refrigerated warehousing and logistic distribution services to clients throughout the United States. In consideration for the Credit, Taxpayer agrees to invest in a new refrigeration and distribution facility in the XxXxxxxxx Park area of Sacramento, California, and hire full-time employees (collectively, the “Project”). Further, Taxpayer agrees to satisfy the milestones as described in Exhibit A (“Milestones”) and must maintain Milestones for a minimum of three (3) taxable years thereafter. In the event Taxpayer employs more than the number of full-time employees, determined on an annual full-time equivalent basis, than required in Exhibit A, for purposes of satisfying the “Minimum Annual Salary of California Full-time Employees Hired” and the “Cumulative Average Annual Salary of California Full-time Employees Hired,” Taxpayer may use the salaries of any of the full-time employees hired within the required time period. For purposes of calculating the “Minimum Annual Salary of California Full-time Employees Hired” and the “Cumulative Average Annual Salary of California Full-time Employees Hired,” the salary of any full-time employee that is not employed by Taxpayer for the entire taxable year shall be annualized. In addition, the salary of any full-time employee hired to fill a vacated position in which a full-time employee was employed during Taxpayer’s Base Year shall be disregarded.
MSAA Indicator Technical Specification Document This Agreement shall be interpreted with reference to the MSAA Indicator Technical Specifications document.
Random Testing Notwithstanding any provisions of the Collective Agreement or any special agreements appended thereto, section 4.6 of the Canadian Model will not be applied by agreement. If applied to a worker dispatched by the Union, it will be applied or deemed to be applied unilaterally by the Employer. The Union retains the right to grieve the legality of any imposition of random testing in accordance with the Grievance Procedure set out in this Collective Agreement.
Stability Testing Patheon may be requested to conduct stability testing on the Products in accordance with the protocols set out in the Specifications for the separate fees and during the time periods set out in Schedule C to a Product Agreement. Patheon will not make any changes to these testing protocols without prior written approval from Client. If a confirmed stability test failure occurs, Patheon will notify Client within one Business Day, after which Patheon and Client will jointly determine the proceedings and methods to be undertaken to investigate the cause of the failure, including which party will bear the cost of the investigation. Patheon will not be liable for these costs unless it has failed to perform the Manufacturing Services in accordance with the Specifications, cGMPs, and Applicable Laws. Patheon will give Client ail stability test data and results at Client’s request.
PRICE LISTS AND PRODUCT INFORMATION Contractors should provide an electronic version of the proposed price list in an Excel format or pdf on a jump drive. Also provide a dealer list, if applicable in an Excel format with "read and write" capabilities on the same jump drive. No costs or expenses associated with providing this information in the required format shall be charged to the State of Arkansas. At the time of contract renewal contractor will furnish OSP with an updated dealer list and published price list.