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 Serena 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 2Sample 3See All (15)
AutoNDA by SimpleDocs

Related to SOFTWARE PRODUCT SPECIFIC TERMS

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

  • Product Specifications The Company agrees that all Products sold to Xxxx hereunder shall conform to the respective specifications set forth on Schedule A or to such other specifications as are from time to time agreed upon by the Parties.

  • 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.

  • 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 The data will be packed using ATIS EMI records. A pack will contain a minimum of one (1) message record or a maximum of ninety-nine thousand nine hundred and ninety-nine (99,999) message records plus a pack header record and a pack trailer record. One transmission can contain a maximum of ninety-nine (99) packs and a minimum of one (1) 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.

  • EODUF Packing Specifications 7.3.1 The data will be packed using ATIS EMI records. A pack will contain a minimum of one (1) message record or a maximum of ninety-nine thousand nine hundred and ninety-nine (99,999) message records plus a pack header record and a pack trailer record. One transmission can contain a maximum of ninety-nine (99) packs and a minimum of one (1) pack.

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

  • Billing Specifications 55.6.1 The Parties agree that billing requirements and outputs will be consistent with the Ordering & Billing Form (OBF) and also with Telcordia Technologies Billing Output Specifications (BOS).

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