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,
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.
Vendor Contracts (a) THIRD-PARTY ASO CONTRACTS.
(i) ATI shall use its Reasonable Efforts to amend each administrative services only contract with a third-party administrator that relates to any of the ATI Health and Welfare Plans (an "ASO Contract") in existence as of the date of this Agreement to permit Water Pik to participate in the terms and conditions of such ASO Contract from Immediately After the Distribution Date until December 31, 2000. ATI shall use its Reasonable Efforts to cause all ASO Contracts into which ATI enters after the date of this Agreement but before the Close of the Distribution Date to allow Water Pik to participate in the terms and conditions thereof effective Immediately After the Distribution Date on the same basis as ATI.
(ii) ATI shall have the right to determine, and shall promptly notify Water Pik of, the manner in which Water Pik's participation in the terms and conditions of ASO Contracts as set forth above shall be effectuated. The permissible ways in which Water Pik's participation may be effectuated include automatically making Water Pik a party to the ASO Contracts or obligating the third party to enter into a separate ASO Contract with Water Pik providing for the same terms and conditions as are contained in the ASO Contracts to which ATI is a party (or such other arrangement as to which ATI and Water Pik shall mutually agree). Such terms and conditions shall include the financial and termination provisions, performance standards, methodology, auditing policies, quality measures, reporting requirements and target claims. Water Pik hereby authorizes ATI to act on its behalf to extend to Water Pik the terms and conditions of the ASO Contracts. Water Pik shall fully cooperate with ATI in such efforts, and Water Pik shall not perform any act, including discussing any alternative arrangements with any third party, that would prejudice ATI's efforts.
Account Types The Financial Institution agrees that each Collateral Account is, and will be maintained as, either a “securities account” (as defined in Section 8-501 of the UCC) or a “deposit account” (as defined in Section 9-102(a)(29) of the UCC).
Covered Contracts and Contractors If the Contract exceeds $100,000 and the Contractor employed more than 40 full-time employees on a single working day during the previous 12 months in Minnesota or in the state where it has its principle place of business, then the Contractor must comply with the requirements of Minnesota Statute § 363A.36 and Minnesota Rule Parts 5000.3400-5000.3600. A Contractor covered by Minnesota Statute § 363A.36 because it employed more than 40 full-time employees in another state and does not have a certificate of compliance, must certify that it is in compliance with federal affirmative action requirements.
Third Party Contractors Tenant shall obtain and deliver to Landlord, Third Party Contractor’s certificates of insurance and applicable endorsements at least seven (7) business days prior to the commencement of work in or about the Premises by any vendor or any other third-party contractor (collectively, a “Third Party Contractor”). All such insurance shall (a) name Landlord as an additional insured under such party’s liability policies as required by Section 10.3.1 above and this Section 10.6, (b) provide a waiver of subrogation in favor of Landlord under such Third Party Contractor’s commercial general liability insurance, (c) be primary and any insurance carried by Landlord shall be excess and non-contributing, and (d) comply with Landlord’s minimum insurance requirements.
Vendor’s Subcontractors TIPS recognizes that many vendors operate in the open market through the use of subcontractors. For that reason, TIPS permits Vendor to utilize subcontractors as authorized and permitted by the TIPS Member Customer. However, all purchase documents must include: (1) Vendor’s Name, as known to TIPS, and; (2) Vendor’s TIPS Contract Name and Number under which it is making the TIPS Sale. Vendor must report the sale pursuant to the terms herein and Vendor agrees that it is legally responsible for all reporting and fee payment as described herein for TIPS Sales even when subcontractors are utilized. The TIPS Administration Fee is assessed on the amount paid by the TIPS Member to Vendor. The Parties intend that Vendor shall be responsible and for actions of subcontractors during a TIPS Sale. Vendor agrees that it is voluntarily authorizing subcontractors and in doing so, Xxxxxx agrees that it is doing so at its own risk and agrees to protect, indemnify, and hold TIPS harmless in accordance with Sections 14-17 above related to subcontractor TIPS Sales made pursuant to this Agreement or purporting to be made pursuant to this Agreement that may be asserted against Vendor whether rightfully brought or otherwise. The Parties further agree that it is no defense to Vendor’s breach of this Agreement that a subcontractor caused Vendor of breach this Agreement.
Contracts with Subcontractors a. Grantee may enter into contracts with subcontractors unless restricted or otherwise prohibited in the Contract.
b. Grantees are prohibited from subcontracting with for-profit organizations under this Contract.
c. Prior to entering into a subcontract agreement equaling or exceeding $100,000, Grantee will obtain written approval from the System Agency.
d. Grantee will obtain written approval from System Agency before modifying any subcontract agreement to cause the agreement to exceed $100,000.
e. Grantee will establish written policies and procedures for competitive procurement and monitoring of subcontracts and will develop a subcontracting monitoring plan.
f. monitor subcontractors for both financial and programmatic performance and will maintain pertinent records.
g. submit quarterly monitoring reports to the System Agency in a format determined by the System Agency.
h. ensure that subcontracts are fully aware of the requirements placed upon them by state/federal statutes, rules, and regulations and by the provisions of this Contract.
i. ensure all subcontracts, must be in writing and include the following:
1. Name and address of all parties and the subcontractor’s Vendor Identification Number (VIN) or Employee Identification Number (EIN);
2. Detailed description of the services to be provided;
3. Measurable method and rate of payment and total not-to-exceed amount of the contract;
4. Clearly defined and executable termination clause; and
5. Beginning and ending dates that coincide with the dates of the Contract.
j. ensure and be responsible for the performance of the subcontractor(s).
k. not contract with a subcontractor, at any tier, that is debarred, suspended, or excluded from or ineligible for participation in federal assistance programs or if the subcontractor would be otherwise ineligible to abide by the terms of this Contract.
Vendors Any vendors engaged by Tenant to perform services in or to the Premises including, without limitation, janitorial contractors and moving contractors shall be coordinated with any work being performed by or for Landlord and in such manner as to maintain harmonious labor relations and not to damage the Building or the Property or interfere with Building construction or operation and shall be performed by vendors first approved by Landlord.
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.
