SOFTWARE PRODUCT SPECIFIC TERMS Sample Clauses

SOFTWARE PRODUCT SPECIFIC TERMS. 12.1 Serena® Business Manager (“SBM”) and TeamTrack®. SBM and TeamTrack are licensed on the basis of Servers and Seats. Each SBM Seat allows a designated Seat to use and participate in all activities and functionality of Serena Business Manager that pertain to workflow applications to which the Seat has been granted access at runtime, including the workflow, workflow roles, transition items, sending and receiving notifications, creating reports, and creating dashboards. A Seat is required for each managed administrator of SBM. Existing SBM Named User, Concurrent User and Requestor licenses remain valid unless converted in accordance with Section 2.3. A Server license allows execution of a single Instance of the Software on a single Server. Existing Named User and Concurrent User licenses are for use on a single Server unless otherwise specified in writing by the parties. A “Requestor” is a user who is permitted to submit issues and view status only. Customer may allow a third party to use the Requestor license, subject to Customer’s indemnification of Xxxxxx against any claims that nay arise from such use of the Software. Customer may transfer Named User licenses to accommodate personnel changes, provided that such transfers do not result in sharing of Named User licenses. Customer may change from time to time the employees who are designated to use the Software under a Named User or Seat license, provided that the number of users does not exceed the total number of licensed Named Users or Seats, as applicable and such use complies with this Agreement.
Sample 1Sample 2See All (8)
AutoNDA by SimpleDocs
SOFTWARE PRODUCT SPECIFIC TERMS. 8.1 Solutions Business Manager (“SBM”) (formerly Serena® Business Manager and formerly TeamTrack™). SBM and TeamTrack are licensed on the basis of Servers and Seats. Each SBM Seat allows a designated Seat to use and participate in all activities and functionality of Solutions Business Manager that pertain to workflow applications to which the Seat has been granted access at runtime, including the workflow, workflow roles, transition items, sending and receiving notifications, creating reports, and creating dashboards. A Seat is required for each managed administrator of SBM. Existing SBM Named User, Concurrent User and Requestor licenses remain valid unless converted. A Server license allows execution of a single Instance of the Software on a single Server. Existing Named User and Concurrent User licenses are for use on a single Server unless otherwise specified in writing by the parties. A “Requestor” is a user who is permitted to submit issues and view status only. You may allow a third party to use the Requestor license, subject to Your indemnification of Xxxxxx against any claims that may arise from such use of the Software. You may transfer Named User licenses to accommodate personnel changes, provided that such transfers do not result in sharing of Named User licenses. You may change from time to time the employees who are designated to use the Software under a Named User or Seat license, provided that the number of users does not exceed the total number of licensed Named Users or Seats, as applicable and such use complies with this Agreement. 8.2 Service Support Manager ("SSM") (formerly Serena® Service Manager). SSM is licensed on the basis of Seats and Concurrent Users. Each SSM license may use and participate in all activities and functionality of SBM that pertain to workflow applications to which the SSM license has been granted access at runtime, including the workflow, workflow roles, transition items, sending and receiving notifications, creating reports, and creating dashboards. Each SSM license includes one SBM Connect for Sharepoint User license. You may access the Service Request Center functionality installed with SSM only to the extent You have purchased a requisite number of Service Request Center licenses. 8.3 Service Support Manager Content ("SSM Content") (formerly Serena® Service Manager Content). SSM Content is licensed on the basis of Seats and Concurrent Users. Each SSM Content license allows for You to use Your existing SBM lic...
Sample 1

Related to SOFTWARE PRODUCT SPECIFIC TERMS

  • Product Specific Terms these terms apply to specific Products referenced in this section.

  • Product Specifications (a) Supplier shall manufacture all Products according to the Specifications in effect as of the date of this Agreement, with such changes or additions to the Specifications of the Products related thereto as shall be requested by Buyer in accordance with this Section or as otherwise agreed in writing by the Parties. All other Products shall be manufactured with such Specifications as the Parties shall agree in writing. (b) Buyer may request changed or additional Specifications for any Product by delivering written notice thereof to Supplier not less than one hundred twenty (120) days in advance of the first Firm Order for such Product to be supplied with such changed or additional Specifications. Notwithstanding the foregoing, if additional advance time would reasonably be required in order to implement the manufacturing processes for production of a Product with any changed or additional Specifications, and to commence manufacture and delivery thereof, Supplier shall so notify Buyer, and Supplier shall not be required to commence delivery of such Product until the passage of such additional time. (c) Supplier shall be required to accommodate any change of, or additions to, the Specifications for any Product, if and only if (i) in Supplier’s good faith judgment, such changed or additional Specifications would not require Supplier to violate good manufacturing practice, (ii) the representation and warranty of Buyer deemed made pursuant to Subsection (e) below is true and correct, and (iii) Buyer agrees to reimburse Supplier for the incremental costs and expenses incurred by Supplier in accommodating the changed or additional Specifications, including the costs of acquiring any new machinery and tooling. For the avoidance of doubt, such costs and expenses shall be payable by Buyer separately from the cost of Products at such time or times as Supplier shall request. (d) Supplier shall notify Buyer in writing within thirty (30) days of its receipt of any request for changed or additional Specifications (i) whether Supplier will honor such changed or additional Specifications, (ii) if Supplier declines to honor such changed or additional Specifications, the basis therefor and (iii) if applicable, the estimated costs and expenses that Buyer will be required to reimburse Supplier in respect of the requested changes or additions, as provided in Subsection (c) above. Buyer shall notify Supplier in writing within fifteen (15) days after receiving notice of any required reimbursement whether Buyer agrees to assume such reimbursement obligation. (e) By its request for any changed or additional Specifications for any Product, Buyer shall be deemed to represent and warrant to Supplier that the manufacture and sale of the Product incorporating Buyer’s changed or additional Specifications, as a result of such incorporation, will not and could not reasonably be expected to (i) violate or conflict with any contract, agreement, arrangement or understanding to which Buyer and/or any of its Affiliates is a party, including this Agreement and any other contract, agreement, arrangement or understanding with Supplier and/or its Affiliates, (ii) infringe on any trademark, service xxxx, copyright, patent, trade secret or other intellectual property rights of any Person, or (iii) violate any Applicable Law. Buyer shall indemnify and hold Supplier and its Affiliates harmless (including with respect to reasonable attorneys’ fees and disbursements) from any breach of this representation and warranty.

  • Software License Terms (a) Software that is made available by a Provider to Recipient in connection with any Service (any such Software being referred to herein as “TSA-Licensed Software”) provided hereunder will be subject to the terms set forth in this Section 3.5 except as otherwise provided in the applicable Service Schedule. The Provider hereby grants to the Recipient a non-exclusive, non-transferable license to use, in object code form, any TSA-Licensed Software that is made available by the Provider pursuant to a Service Schedule. For the avoidance of doubt, the Provider that makes available any TSA-Licensed Software in connection with the provision of any Service retains the unrestricted right to enhance or otherwise modify such TSA-Licensed Software at any time, provided that such enhancements or other modifications do not disrupt the provision of such Service to the Recipient. (b) The Recipient may not exceed the number of licenses, agents, tiers, nodes, seats, or other use restrictions or authorizations, if any, specified in the applicable Service Schedule. Some TSA-Licensed Software may require license keys or contain other technical protection measures. The Recipient acknowledges that the Provider may monitor the Recipient’s compliance with use restrictions and authorizations remotely, or otherwise. If the Provider makes a license management program available which records and reports license usage information, the Recipient agrees to appropriately install, configure and execute such license management program. (c) Unless otherwise permitted by the Provider, the Recipient may only make copies or adaptations of the TSA-Licensed Software for archival purposes or when copying or adaptation is an essential step in the authorized use of TSA-Licensed Software. If the Recipient makes a copy for backup purposes and installs such copy on a backup device, the Recipient may not operate such backup installation of the TSA-Licensed Software without paying an additional license fee, except in cases where the original device becomes inoperable. If a copy is activated on a backup device in response to failure of the original device, the use on the backup device must be discontinued when the original or replacement device becomes operable. The Recipient may not copy the TSA-Licensed Software onto or otherwise use or make it available on, to, or through any public or external distributed network. Licenses that allow use over the Recipient’s intranet require restricted access by authorized users only. (d) The Recipient must reproduce all copyright notices that appear in or on the TSA-Licensed Software (including documentation) on all permitted copies or adaptations. Copies of documentation are limited to internal use. (e) Notwithstanding anything to the contrary herein, certain TSA-Licensed Software may be licensed under the applicable Service Schedule for use only on a computer system owned, controlled, or operated by or solely on behalf of the Recipient and may be further identified by the Provider by the combination of a unique number and a specific system type (“Designated System”) and such license will terminate in the event of a change in either the system number or system type, an unauthorized relocation, or if the Designated System ceases to be within the possession or control of the Recipient. (f) The Recipient will not modify, reverse engineer, disassemble, decrypt, decompile, or make derivative works of the TSA-Licensed Software. Where the Recipient has other rights mandated under statute, the Recipient will provide the Provider with reasonably detailed information regarding any intended modifications, reverse engineering, disassembly, decryption, or decompilation and the purposes therefor. (g) The Recipient may permit a consultant or subcontractor to use TSA-Licensed Software at the licensed location for the sole purpose of providing services to the Recipient. (h) Upon expiration or termination of the Service Schedule under which TSA-Licensed Software is made available, the Recipient will destroy the TSA-Licensed Software. The Recipient will remove and destroy or return to the Provider any copies of the TSA-Licensed Software that are merged into adaptations, except for individual pieces of data in the Recipient’s database. The Recipient will provide certification of the destruction of TSA-Licensed Software, and copies thereof, to the Provider. The Recipient may retain one copy of the TSA-Licensed Software subsequent to expiration or termination solely for archival purposes. (i) The Recipient may not sublicense, assign, transfer, rent, or lease the TSA-Licensed Software to any other person except as permitted in this Section 3.5. (j) The Recipient agrees that the Provider may engage a third party designated by the Provider and approved by the Recipient (such approval not to be unreasonably withheld) to audit the Recipient’s compliance with the Software License terms. Any such audit will be at the Provider’s expense, require reasonable notice, and will be performed during normal business hours. Such third party will be required to execute a non-disclosure agreement that restricts such third party from disclosing confidential information of the Recipient to the Provider, except to the extent required to report on the extent to which the Recipient is not in compliance with the Software License terms.

  • Software Products Save as otherwise set forth in the Agreement, the right to use any Software Product is personal to the Licensee, for its own internal use, and is non-transferable, except with the Licensor’s prior written consent, in which case the Licensee shall cause the assignee or sub-licensee to agree to the terms of this Software License.

  • MSAA Indicator Technical Specification Document This Agreement shall be interpreted with reference to the MSAA Indicator Technical Specifications document.

  • ODUF Packing Specifications 6.3.1 A pack will contain a minimum of one message record or a maximum of 99,999 message records plus a pack header record and a pack trailer record. One transmission can contain a maximum of 99 packs and a minimum of one pack.

  • Packing Specifications 7.3.1 A pack will contain a minimum of one message record or a maximum of 99,999 message records plus a pack header record and a pack trailer record. One transmission can contain a maximum of 99 packs and a minimum of one pack.

  • Country Specific Terms Appendix A contains additional terms and conditions of the Agreement applicable to Participants residing in those countries. In addition, Appendix A also contains information and notices of exchange control and certain other issues of which the Participant should be aware.

  • Escrow Format Specification 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.

  • New Products You agree to comply with NASD Notice to Members 5-26 recommending best practices for reviewing new products.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!