License Types Description Sample Clauses

License Types Description 
AutoNDA by SimpleDocs

Related to License Types Description

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

  • License Types The following License Types may be offered with respect to individual Software products or product families. Additional license types may be specified with respect to certain products or product groups as set forth in the Product Specific Terms. The License Type will be specified in an LSDA.

  • Service Descriptions Available services for Transitional and Enhanced Supervision Services a. One (1) one-to-one meeting with the Contractor per week for case management services.

  • Services Description 2.1 ‘Ethernet’ – shall mean the provision of a fibre or copper or radio or optical data circuit or any mix of fibre, copper, radio and optical between two locations based on IEEE 802.3 standard.

  • Task Description This task includes activities associated with permit-required monitoring conducted in accordance with the conditions specified by state or federal regulatory agencies. All monitoring tasks must be located within or adjacent to the Project area and follow the Department’s Regional Coastal Monitoring Program and FWC's marine turtle and shorebird monitoring programs. Guidance for monitoring of nearshore resources is available in the Department's Standard Operation Procedures For Nearshore Hardbottom Monitoring Of Beach Nourishment Projects. The Local Sponsor must submit work products directly to the appropriate state or federal regulatory agencies in accordance with permit conditions to be eligible for reimbursement under this task, unless otherwise directed.

  • Topic Description Licensee Responsibilities Licensee must:  Take appropriate steps to ensure the security, integrity, and confidentiality of Confidential Information and must comply with all relevant applicable laws and regulations, including laws protecting borrower privacy.  Not disclose Confidential Information to third parties, without Xxxxxx Mae’s prior written approval, except on a need‐to‐know basis to Licensee’s partners, Topic Description affiliates, officers, employees, directors, contractors, counsels, agents or representatives, provided they are subject to confidentiality obligations at least as stringent as those set forth in this Section A3.  Not use Confidential Information in any way that could be viewed as a conflict of interest, a breach of confidentiality or privacy, or the gaining of an unfair advantage from the relationship with Xxxxxx Xxx.  Implement commercially reasonable measures meeting or exceeding industry standards to ensure the security, integrity, and confidentiality of Confidential Information, including using industry‐standard encryption for data in transit and virus checking programs designed to prevent the transmission and receipt of viruses and other malicious code, implementing appropriate disaster recovery and back‐up procedures, implementing appropriate procedures to prevent disclosure of data and other materials to a party other than the intended recipient, and employing methods for securely disposing or destroying such information.  These measures must meet, at least, the same level of protection that the Receiving Party seeks for its own information of a similar nature.  Licensee must collaborate with Xxxxxx Mae in assessing the sufficiency of these measures and Licensee’s information security program, upon reasonable request.  Instruct its Related Parties who may receive Confidential Information about the requirements of this Section A3, and the processes and procedures necessary to comply with them.  Comply with all reasonable security policies and procedures required by Xxxxxx Xxx related to the access and use of Xxxxxx Mae’s systems or any Licensed Materials.  Not transmit to Xxxxxx Mae’s systems any materials that contain bugs, viruses, worms or other functions, routines, devices or instructions which may create any unauthorized access or damage to, or interruption in the functioning of, the Licensed Application or Xxxxxx Mae’s systems. Restrictive Legends  Licensee must abide by and reproduce and include any restrictive legend or proprietary rights notice that appears in or on any Confidential Information of Xxxxxx Xxx or any Third‐Party Licensor (or other third‐party owner) that it is authorized to reproduce.  Licensee also agrees that it will not remove, alter, cover or distort any trademark, trade name, copyright or other proprietary rights notices, legends, symbols or labels appearing on or in any Confidential Information of Xxxxxx Mae or any Third‐Party Licensor (or other third‐party owner). Required Actions in Case of Data Breach  Licensee must address any Data Breach with prompt and effective corrective action, including cooperation with Xxxxxx Xxx in the investigation and remediation of such Data Breach, as well as prompt disclosure and notification where legally required; and  Licensee must promptly notify Xxxxxx Mae of any Data Breach in writing ‐‐ at xxxxxxx_xxxxxxxxxxxx@xxxxxxxxx.xxx ‐‐ and must take all steps reasonably requested by Xxxxxx Xxx to mitigate the consequences of such Data Breach.

  • Specific Provisions for Access Rights to Software For the avoidance of doubt, the general provisions for Access Rights provided for in this Section 9 are applicable also to Software. Parties’ Access Rights to Software do not include any right to receive source code or object code ported to a certain hardware platform or any right to receive respective Software documentation in any particular form or detail, but only as available from the Party granting the Access Rights.

  • Service Description The Parties will provide Common Channel Signaling (CCS) to one another via Signaling System 7 (SS7) network Interconnection, in accordance with prevailing industry standards. Use of a third party provider of SS7 trunks is permitted.

  • System Description The DLCS is a network consisting of devices which are remotely controlled over RF transmission equipment by the PowerCAMPTM Software or equivalent. CL&P shall have access to the PowerCAMP™ LMS (as defined below) via the web interface. The PowerCAMPTM LMS shall include the software and hardware necessary to manage the Control Devices installed at the End-use Equipment at Participating Facilities. The PowerCAMPTM LMS includes AER’s PowerCAMPTM Server and PowerCAMPTM Suite, networking equipment, and third party software. PowerCAMPTM LMS Hardware

  • Contract Description The Description and Location of the Contract and related project(s) are as follows.

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