Feature Requests Sample Clauses

Feature Requests. If Google deems a Request as a Feature Request, Google will log such Request for consideration to add to a future update or release of the Solution and will consider the matter closed. Google is under no obligation to respond to or resolve any Feature Request or to include any such Feature Request in any future update or release.
AutoNDA by SimpleDocs
Feature Requests. We encourage users to suggest their ideas for improving the Products/Services. We shall have all rights to such requests, suggestions, and any content that is part of that request.
Feature Requests. If a Request is deemed by Learning Objects to be a Feature Request, Learning Objects will log such Feature Request for consideration to include in a future update or release of the Service and
Feature Requests. All requests from the Client for Development or Consultancy should be notified to Supplier by one of the following means:
Feature Requests. 6.5.1 We welcome client feedback relating to feature requests. Feedback will be assessed as part of a larger development roadmap and proposed changes will be considered in the context of wider company strategy.
Feature Requests. OSA holders may submit Trouble Tickets requesting additional features or functionality be added to the rXg general release software. Trouble Tickets of this nature may be responded to with a description and timing of the modification to a future rXg software release containing the requested functionality. If the feature requested is not scheduled for a future release the Operator may wish to request a quote for the feature to be added within their desired timeframe and expense. These Trouble Tickets will be referred to the designated RG Nets account manager. There is a non-discounted fee for preparing a formal Statement of Work.
Feature Requests. OSA holders may submit Trouble Tickets requesting an additional features or functionality be added to the rXg general release code. Trouble Tickets of this nature may be responded to with a description and timing of an addition or modification to a future rXg revision release containing the requested feature or functionality. If the feature requested is not scheduled for a future release the Operator may wish to request a quote for the feature to be added within their desired timeframe and expense. These tickets will be responded with a quotation for Feature Request Professional Service if the request is deemed by RG Nets to be of value to rXg customers. Completed Feature Requests will be made available in a future revision update and included in the rXg firmware for general release.
AutoNDA by SimpleDocs
Feature Requests. Certain support requests are more accurately viewed as requests for additional features for the System. Where appropriate and in its discretion, Toybox is entitled to treat a User request as a feature request (and not a support request) and to add the request to its roadmap (or reject the request), as it sees fit.

Related to Feature Requests

  • Service Requests In support of services outlined in this Agreement, the Service Provider will respond to service related incidents and/or requests submitted by the Customer within the following time frames:

  • Change Requests 4.1.1. Either party can request changes to the Service.

  • Advance Requests Borrower may request that Lender make an Advance by delivering to Lender an Advance Request therefor and Lender shall be entitled to rely on all the information provided by Borrower to Lender on or with the Advance Request. The Lender may honor Advance Requests, instructions or repayments given by the Borrower (if an individual) or by any Authorized Person.

  • Leave Requests All requests for leaves of absence must be in writing.

  • Purchase Order Pricing/Product Deviation If a deviation of pricing/product on a Purchase Order or contract modification occurs between the Vendor and the TIPS Member, TIPS must be notified within five (5) business days of receipt of change order. TIPS reserves the right to terminate this agreement for cause or no cause for convenience with a thirty (30) days prior written notice. Termination for convenience is conditionally required under Federal Regulations 2 CFR part 200 if the customer is using federal funds for the procurement. All purchase orders presented to the Vendor, but not fulfilled by the Vendor, by a TIPS Member prior to the actual termination of this agreement shall be honored at the option of the TIPS Member. The awarded Vendor may terminate the agreement with ninety (90) days prior written notice to TIPS 0000 XX Xxx Xxxxx, Xxxxxxxxx, Xxxxx 00000. The vendor will be paid for goods and services delivered prior to the termination provided that the goods and services were delivered in accordance with the terms and conditions of the terminated agreement. This termination clause does not affect the sales agreements executed by the Vendor and the TIPS Member customer pursuant to this agreement. TIPS Members may negotiate a termination for convenience clause that meets the needs of the transaction based on applicable factors, such as funding sources or other needs. Usually, purchase orders or their equal are issued by participating TIPS Member to the awarded vendor and should indicate on the order that the purchase is per the applicable TIPS Agreement Number. Orders are typically emailed to TIPS at xxxxxx@xxxx-xxx.xxx. • Awarded Vendor delivers goods/services directly to the participating member. • Awarded Vendor invoices the participating TIPS Member directly. • Awarded Vendor receives payment directly from the participating member. • Fees are due to TIPS upon payment by the Member to the Vendor. Vendor agrees to pay the participation fee to TIPS for all Agreement sales upon receipt of payment including partial payment, from the Member Entity or as otherwise agreed by TIPS in writing and signed by an authorized signatory of TIPS.

  • Work Order (s) means a detailed scope of work for a Service required by Transnet, including timeframes, Deliverable, Fees and costs for the supply of the Service to Transnet, which may be appended to this Agreement from time to time.

  • Purchase Order A Customer may use purchase orders to buy commodities or contractual services pursuant to the Contract and, if applicable, the Contractor must provide commodities or contractual services pursuant to purchase orders. Purchase orders issued pursuant to the Contract must be received by the Contractor no later than the close of business on the last day of the Contract’s term. The Contractor is required to accept timely purchase orders specifying delivery schedules that extend beyond the Contract term even when such extended delivery will occur after expiration of the Contract. Purchase orders shall be valid through their specified term and performance by the Contractor, and all terms and conditions of the Contract shall survive the termination or expiration of the Contract and apply to the Contractor’s performance. The duration of purchase orders for recurring deliverables shall not exceed the expiration of the Contract by more than twelve months. Any purchase order terms and conditions conflicting with these Special Contract Conditions shall not become a part of the Contract.

  • Completion of Requests (a) A Request for a Loan will not be regarded as having been duly completed unless: (i) it identifies the Facility under which the Loan is to be made; (ii) it identifies the Borrower; (iii) the Utilisation Date is a Business Day falling within the Availability Period applicable to the relevant Facility; (iv) the amount of the Loan requested is: (A) a minimum of US$10,000,000 and an integral multiple of US$1,000,000; (B) the maximum undrawn amount available under the relevant Facility on the proposed Utilisation Date; or (C) such other amount as the Facility Agent may agree; (v) the proposed Term complies with this Agreement; and (vi) the proposed currency complies with this Agreement. (b) Only one Loan may be requested in a Request.

  • Network Upgrades The Transmission Owner shall design, procure, construct, install, and own the Network Upgrades described in Attachment 6 of this Agreement. If the Transmission Owner and the Interconnection Customer agree, the Interconnection Customer may construct Network Upgrades that are located on land owned by the Interconnection Customer. Unless the Transmission Owner elects to pay for Network Upgrades, the actual cost of the Network Upgrades, including overheads, shall be borne initially by the Interconnection Customer.

  • Notice of Network Changes If a Party makes a change in the information necessary for the transmission and routing of services using that Party’s facilities or network, or any other change in its facilities or network that will materially affect the interoperability of its facilities or network with the other Party’s facilities or network, the Party making the change shall publish notice of the change at least ninety (90) days in advance of such change, and shall use reasonable efforts, as commercially practicable, to publish such notice at least one hundred eighty (180) days in advance of the change; provided, however, that if an earlier publication of notice of a change is required by Applicable Law (including, but not limited to, 47 CFR 51.325 through 51. 335) notice shall be given at the time required by Applicable Law.

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