Software utilization Sample Clauses

Software utilization. Insofar as the delivery also includes software, the Buyer has a non-exclusive right to utilize the supplied software together with the documentation. The software is provided for use on the article supplied for this purpose. The software may not be used on more than one system. The Buyer may only copy, revise or translate the software or transform the object code into a source code within legally permissible bounds (§§ 69 a ff. UrhG [Urheberrechtsgesetz = German Copyright Act]). The Buyer undertakes not to remove any manufacturer's information - in particular any copyright notations - or to alter them without the Supplier's prior express permission. The Supplier or the provider of the software retains all other rights to the software and its documentation including the rights to all copies. The granting of sublicenses is not permitted.
AutoNDA by SimpleDocs
Software utilization. 8.1. When E-Merchant utilizes any software provided by Novum the following shall apply: a. E-Merchant is responsible for technical adaptation and implementation of the chosen software. The software used shall only be a solution approved by Novum and Novum may notify E-Merchant that the software is no longer approved for use. In this event E-Merchant shall upgrade to new software approved by Novum within a reasonable time specified by Novum. b. E-Merchant acknowledges that the installation of the software is subject to: (1) the availability of suitable communication lines and Terminals; and (2) the cooperation of E-Merchant with the electric and communication companies. Novum will have no liability to E-Merchant if any installation is delayed or cannot be completed for reasons not caused by the act or neglect of Novum. The E-Merchant acknowledges that its TPI, as applicable, has the same access and is also bound by Novum’s rules and regulations. 8.2. When E-Merchant does not utilize any software provided by Novum the following shall apply: For e-commerce, E-Merchant shall use software that includes fraud screening of Authorisation and Transactions. The software shall be designed specifically for the region or the industry where E-Merchant is doing business to assist in keeping Chargeback and fraud rates below the Chargeback and fraud limits as they may change from time to time. E-Merchant shall further apply the utmost diligence and forthrightness in protecting against and responding to any ADC Event or potential ADC Event. E-Merchant acknowledges and agrees that Novum and/or Card Payment Schemes have the right and need to obtain full disclosure (as determined by Novum and/or Card Payment Schemes) concerning the causes and effects of an ADC Event or potential ADC Event as well as the authority to impose assessments, recover costs, and administer compensation, if appropriate, to E-Merchant that have incurred costs, expenses, losses, and/or other liabilities in connection with ADC Events and potential ADC Events. At the time that the ADC Event or Potential ADC Event has occurred E-Merchant is fully responsible for resolving all outstanding issues and liabilities to the satisfaction of Novum.
Software utilization. A. Software shall be utilized in connection with submittal preparation and information management. Requirements of this section are in addition to requirements of all other contract requirements. Users will be provided a playbook for full application use instructions.
Software utilization. 1.1 The licensee is entitled to install the software on a hard disk or other data storage medium or to utilize the software online; the licensee is entitled to install the software on a file server for use in a local network for purposes of (i) permanent installation on hard disks or other storage media or (ii) operating the software via a network of this type; the licensee is entitled to make back-up copies of the software.
Software utilization. 3.1.1.1. Unlimited App User login accounts (agent logins)

Related to Software utilization

  • MWBE Utilization Plan A. In accordance with 5 NYCRR § 142.4, Bidders are required to submit a completed Utilization Plan on Form MWBE 100 with their bid. B. The Utilization Plan shall list the MWBEs the Bidder intends to use to perform the Contract, a description of the Contract scope of work the Bidder intends the MWBE to perform to meet the goals on the Contract, and the estimated or, if known, actual dollar amounts to be paid to an MWBE. By signing the Utilization Plan, the Bidder acknowledges that making false representations or including information evidencing a lack of good faith as part of, or in conjunction with, the submission of a Utilization Plan is prohibited by law and may result in penalties including, but not limited to, termination of a contract for cause, loss of eligibility to submit future bids, and/or withholding of payments. Any modifications or changes to the agreed participation by New York State Certified MWBEs after the Contract award and during the term of the Contract must be reported on a revised MWBE Utilization Plan and submitted to OGS. C. By entering into the Contract, Bidder/Contractor understands that only sums paid to MWBEs for the performance of a commercially useful function, as that term is defined in 5 NYCRR § 140.1, may be applied towards the achievement of the applicable MWBE participation goal. When an MWBE is serving as a broker on the Contract, only 25 percent of all sums paid to a broker shall be deemed to represent the commercially useful function performed by the MWBE. D. OGS will review the submitted MWBE Utilization Plan and advise the Bidder of OGS acceptance or issue a notice of deficiency within 30 days of receipt. E. If a notice of deficiency is issued; Bidder agrees that it shall respond to the notice of deficiency, within 7 business days of receipt, by submitting to OGS a written remedy in response to the notice of deficiency. If the written remedy that is submitted is not timely or is found by OGS to be inadequate, OGS shall notify the Bidder and direct the Bidder to submit, within 5 business days of notification by OGS, a request for a partial or total waiver of MWBE participation goals on Form BDC 333. Failure to file the waiver form in a timely manner may be grounds for disqualification of the bid or proposal. F. OGS may disqualify a Vendors Submission as being non-responsive under the following circumstances: (a) If a Bidder fails to submit an MWBE Utilization Plan; (b) If a Bidder fails to submit a written remedy to a notice of deficiency; (c) If a Bidder fails to submit a request for waiver; or (d) If OGS determines that the Bidder has failed to document good faith efforts. G. If awarded a Contract, Contractor certifies that it will follow the submitted MWBE Utilization Plan for the performance of MWBEs on the Contract pursuant to the prescribed MWBE goals set forth in clause IV-A of this Section. H. Bidder/Contractor further agrees that a failure to submit and/or use such completed MWBE Utilization Plan shall constitute a material breach of the terms of the Contract. Upon the occurrence of such a material breach, OGS shall be entitled to any remedy provided herein, including but not limited to, a finding of Contractor non- responsiveness.

  • Software Upgrades All Software Releases (including all Error corrections made available pursuant to this Agreement) that RSA in its sole discretion: (a) deems to be logical improvements to the Software; (b) make generally available to all licensees of the Software; and (c) does not separately price or market.

  • Service Availability You understand that Service availability is at all times conditioned upon the corresponding operation and availability of the communication systems used in communicating your instructions and requests to the Credit Union. We will not be liable or have any responsibility of any kind for any loss or damage thereby incurred by you in the event of any failure or interruption of such communication systems or services resulting from the act or omission of any third party, or from any other cause not reasonably within the control of the Credit Union.

  • Utilization Utilization shall be defined as Trunks Required as a percentage of Trunks In Service. 1 During implementation the Parties will mutually agree on an Economic Centum Call Seconds (ECCS) or some other means for the sizing of this trunk group. 4.6.3.1 In A Blocking Situation (Over-utilization): 4.6.3.1.1 In a blocking situation, CLEC is responsible for issuing ASRs on all two-way Local Only, Local Interconnection, Third Party and Meet Point Trunk Groups and one-way CLEC originating Local Only and/or Local Interconnection Trunk Groups to reduce measured blocking to design objective blocking levels based on analysis of trunk group data. If an ASR is not issued, AT&T-21STATE will issue a TGSR. CLEC will issue an ASR within three (3) business days after receipt and review of the TGSR. CLEC will note “Service Affecting” on the ASR. 4.6.3.1.2 In a blocking situation, AT&T-21STATE is responsible for issuing ASRs on one-way AT&T-21STATE originating Local Only and/or Local Interconnection Trunk Groups to reduce measured blocking to design objective blocking levels based on analysis of trunk group data. If an ASR is not issued, CLEC will issue a TGSR. AT&T- 21STATE will issue an ASR within three (3) business days after receipt and review of the TGSR. 4.6.3.1.3 If an alternate final Local Only Trunk Group or Local Interconnection Trunk Group is at seventy-five percent (75%) utilization, a TGSR may be sent to CLEC for the final trunk group and all subtending high usage trunk groups that are contributing any amount of overflow to the alternate final route. 4.6.3.1.4 If a direct final Meet Point Trunk Group is at seventy-five percent (75%) utilization, a TGSR may be sent to CLEC. If a direct final Third Party Trunk Group is at ninety percent (90%) utilization, a TGSR may be sent to CLEC.

  • EPP service availability Refers to the ability of the TLD EPP servers as a group, to respond to commands from the Registry accredited Registrars, who already have credentials to the servers. The response shall include appropriate data from the Registry System. An EPP command with “EPP command RTT” 5 times higher than the corresponding SLR will be considered as unanswered. If 51% or more of the EPP testing probes see the EPP service as unavailable during a given time, the EPP service will be considered unavailable.

  • DNS name server availability Refers to the ability of a public-­‐DNS registered “IP address” of a particular name server listed as authoritative for a domain name, to answer DNS queries from an Internet user. All the public DNS-­‐registered “IP address” of all name servers of the domain name being monitored shall be tested individually. If 51% or more of the DNS testing probes get undefined/unanswered results from “DNS tests” to a name server “IP address” during a given time, the name server “IP address” will be considered unavailable.

  • System Availability Although we will try to provide continuous access to the Service, we cannot and do not guarantee that the Service will be available 100% of the time and will not be liable in the event Service is unavailable. Actual service or network performance is dependent on a variety of factors outside of our control. If you notify us within twenty-four (24) hours and we confirm an outage consisting of a period of two (2) hours in any calendar month, and not due to any service, act, or omission of you, a third party, your applications, equipment or facilities, or reasons outside of our control, you shall be eligible for a service credit. A service credit shall be computed as a pro-rated charge for one day of the regular monthly fees for the Service in the next monthly statement. Intermittent service outages for periods of less than two (2) hours are not considered service outages. Outages caused by routine scheduled maintenance are also not considered an outage. You shall receive advance notice no less than forty-eight (48) hours in advance of our scheduled maintenance. Scheduled maintenance will be performed between 12:00 a.m. and 6:00 a.m. CST.

  • Software Use Case Red Hat Enterprise Linux Developer Suite Subscription Services for Red Hat Enterprise Linux Developer Suite are available for Development Purposes only.

  • Software Updates XXXXX agrees to keep current with software licensed from Skyward and will install new versions on a timeline approved by XXXXX governance. This timeline will be communicated by NWRDC to the Districts.

  • Start-Up and Synchronization Consistent with the mutually acceptable procedures of the Developer and Connecting Transmission Owner, the Developer is responsible for the proper synchronization of the Large Generating Facility to the New York State Transmission System in accordance with NYISO and Connecting Transmission Owner procedures and requirements.

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