Service Names and Levels of Access are defined in the Service Descriptions Sample Clauses

This clause establishes that the specific names of services and the corresponding levels of access granted to users are detailed within separate Service Descriptions documents. In practice, this means that rather than listing all service features and access rights within the main agreement, these details are referenced and maintained in dedicated descriptions, which can be updated as needed. The core function of this clause is to ensure clarity and flexibility by centralizing service details in a single location, reducing ambiguity and simplifying updates to service offerings.
Service Names and Levels of Access are defined in the Service Descriptions. Gartner may periodically update the names and the deliverables for each Service. If Client adds Services or upgrades the level of service or access, an additional Service Agreement will be required.
View SourceView Similar (15)

Related to Service Names and Levels of Access are defined in the Service Descriptions

  • Access to Services Subject to and in accordance with the terms of this Agreement, including any Schedules, Company grants You a non-exclusive, non-sublicensable, nontransferable, non-assignable, revocable license for the term of this Agreement to access and use the Services. Services may only be used by Your Users for internal business purposes only. You agree to comply with the terms and conditions of this Agreement, including any Schedules, and with all applicable Company procedures and policies that further define use of the Services. You acknowledge and agree that the actions of any of Your Users with respect to the Services will be deemed to be actions by You and that any breach by any of Your Users of the terms of this Agreement, including any Schedule, will be deemed to be a breach by You.

  • Detailed Description of Services / Statement of Work Describe fully the services that Contractor will provide, or add and attach Exhibit B to this Agreement.

  • Service Descriptions 2.4.1 The switch’s LRN software determines if the called party is in a portable NXX. If the called party is in a portable NXX, a query is launched to the LNP database to determine whether or not the called number is ported. 2.4.2 When the called number with a portable NXX is ported, an LRN is returned to the switch that launched the query. Per industry standards, the LRN appears in the Called Party Number (CdPN) field of the SS7 message and the called number then appears in the GAP (Generic Address Parameter) field. 2.4.3 When the called number with a portable NXX is not ported, the call is completed as in the pre-LNP environment. 2.4.4 The Forward Call Identifier (FCI) field entry is changed from 0 to 1 by the switch triggering the query when a query is made, regardless of whether the called number is ported or not. 2.4.5 The WSP shall populate the Jurisdictional Identification Parameter (JIP) field with the first six (6) digits (NPA NXX format) of the appropriate LRN of the originating switch.

  • Access to the Services ID’s for access to Vendor Core Research and Analyst Inquiry may not be shared. Access to the Services is restricted to the number of named individuals (each a “Licensed User”) as identified in the Customer Purchase Order.

  • Use of the Services 1.1 We will make the Oracle services listed in Your order (the “Services”) available to You pursuant to this Agreement and Your order. Except as otherwise stated in this Agreement or Your order, You have the non- exclusive, worldwide, limited right to use the Services during the period defined in Your order, unless earlier terminated in accordance with this Agreement or Your order (the “Services Period”), solely for Your internal business operations. You may allow Your Users (as defined below) to use the Services for this purpose, and You are responsible for their compliance with this Agreement and Your order. 1.2 The Service Specifications describe and govern the Services. During the Services Period, we may update the Services and Service Specifications (with the exception of the Data Processing Agreement as described below) to reflect changes in, among other things, laws, regulations, rules, technology, industry practices, patterns of system use, and availability of Third Party Content (as defined below). Oracle updates to the Services or Service Specifications will not materially reduce the level of performance, functionality, security or availability of the Services during the Services Period of Your order. 1.3 You may not, and may not cause or permit others to: (a) use the Services to harass any person; cause damage or injury to any person or property; publish any material that is false, defamatory, harassing or obscene; violate privacy rights; promote bigotry, racism, hatred or harm; send unsolicited bulk e-mail, junk mail, spam or chain letters; infringe property rights; or otherwise violate applicable laws, ordinances or regulations; (b) perform or disclose any benchmarking or availability testing of the Services; (c) perform or disclose any performance or vulnerability testing of the Services without Oracle’s prior written approval, or perform or disclose network discovery, port and service identification, vulnerability scanning, password cracking or remote access testing of the Services; or (d) use the Services to perform cyber currency or crypto currency mining ((a) through (d) collectively, the “Acceptable Use Policy”). In addition to other rights that we have in this Agreement and Your order, we have the right to take remedial action if the Acceptable Use Policy is violated, and such remedial action may include removing or disabling access to material that violates the policy.