FEDLINK Delivery Orders Sample Clauses

FEDLINK Delivery Orders. LC/Contracts issues a delivery order to the vendor for each FEDLINK customer using the vendor’s service in the transfer pay mode under the LC/FEDLINK BOA. LC/Contracts may also issue delivery order modifications that reflect amendments to customers’ purchase agreements - to change services or adjust funding levels. Upon receipt of the official LC delivery order, the vendor may begin service for the customer, under the terms of the current BOA. The vendor shall not begin, renew, cancel or convert to the LC/FEDLINK BOA, any service for any FEDLINK customer until a delivery order for that service, for the current fiscal year has been received. The vendor shall not provide services to the customer in excess of the “not to exceed” (NTE) dollar amount indicated on the original delivery order or as amended by any delivery order modification. The Government is not liable for services or products provided, which exceed the NTE dollar amount. Authority to provide service under an LC delivery order expires on September 30 of each fiscal year, unless specifically stated otherwise on the delivery order.
View SourceView Similar (5)
FEDLINK Delivery Orders. LC/Contracts issues a delivery order to the vendor for each FEDLINK customer using the vendor’s service in the transfer pay mode under the LC/FEDLINK BOA. LC/Contracts may also issue delivery order modifications that reflect amendments to customers’ purchase agreements - to change services or adjust funding levels. Upon receipt of the official LC delivery order, the vendor may begin service for the customer, under the terms of the current BOA. The vendor shall not begin, renew, cancel or convert to the LC/FEDLINK BOA, any service for any FEDLINK customer until a delivery order for that service, for the current fiscal year has been received. The vendor shall not provide services to the customer in excess of the “not to exceed” (NTE) dollar amount indicated on the original delivery order or as amended by any delivery order modification. The Government is not liable for services or products
View Source

Related to FEDLINK Delivery Orders

  • Project Delivery Order Procedures Status of TIPS Members as Related to This Agreement

  • Project Delivery Order Procedures The TIPS Member having approved and signed an interlocal agreement, or other TIPS Membership document, may make a request of the awarded vendor under this Agreement when the TIPS Member has services that need to be undertaken. Notification may occur via phone, the web, email, fax, or in person. Upon notification of a pending request, the awarded vendor shall make contact with the TIPS Member as soon as possible, but must make contact with the TIPS Member within two working days. Scheduling of projects (if applicable) may be accomplished when the TIPS Member issues a Purchase Order and/or an Agreement or Contract that will serve as “the notice to proceed” as agreed by the Vendor and the TIPS Member. The period for the delivery order will include the mobilization, materials purchase, installation and delivery, design, weather, and site cleanup and inspection. No additional claims may be made for delays as a result of these items. When the tasks have been completed the awarded vendor shall notify the client and have the TIPS Member or a designated representative of the TIPS Member inspect the work for acceptance under the scope and terms in the Purchase Order and/or Agreement or Contract. The TIPS Member will issue in writing any corrective actions that are required. Upon completion of these items, the TIPS Member will issue a completion notice and final payment will be issued per the contractual requirements of the project with the TIPS Member. Any Construction contract prepared by the TIPS Member’s Legal Counsel may alter the terms of this subsection, “Scheduling of Projects”.

  • Delivery of Software 1. SAP will deliver the Software as described in the Documentation and the Price List and will also provide the appropriate license key for the relevant End User. With regard to the features, quality and functionality of the Software the product description in the Documentation and the Price List is solely decisive. SAP does not own any additional features, quality or functionality. Distributor can, in particular, not assert any additional feature, quality or functionality from any public statements, publications or advertisements by SAP except to the extend SAP has expressly confirmed such additional feature, quality or functionality in writing. Any representation, warranty, undertaking or guarantee regarding additional features, quality or functionality is effective only if expressly confirmed by SAP’s management in writing. 2. After acceptance of an order, SAP will deliver to Distributor one copy of the relevant Software: a) on discs or other data media (“Physical Shipment”); or b) by making it available for downloading through the internet (usually on the SAP ServiceMarket Place (▇▇▇▇://▇▇▇▇▇▇▇.▇▇▇.▇▇▇/swdc)) (“Electronic Delivery”). 3. The relevant Software and Documentation will be deemed delivered (including but not limited for the purpose of fixed delivery dates or timely delivery) and the risk passes to Distributor: a) in case of Physical Shipment, when the relevant disc or other data media thereof is handed over to the freight carrier (FCA - Free Carrier (named place of delivery), Incoterms 2010); or b) in case of Electronic Delivery, when SAP has made an electronic copy thereof available for downloading and has informed Distributor accordingly, (“Delivery”). 4. Upon Distributor’s request or if stipulate in the order, SAP may agree to provide Software and/or the appropriate license key directly to the relevant Open Ecosystem Partner instead (“Open Ecosystem Partner Delivery”). In case of Open Ecosystem Partner Delivery, the provisions set out in this Article 5 (Delivery of Software) will apply analogously; delivery to Distributor will be deemed to occur upon Delivery to the Open Ecosystem Partner. 5. Upon Distributor’s request or if stipulate in the order, SAP may agree to provide Software and/or the appropriate license key directly to the relevant End User instead (“End User Delivery”). In case of End User Delivery, the provisions set out in this Article 5 (Delivery of Software) will apply analogously; delivery to Distributor will be deemed to occur upon Delivery to the End User. 6. SAP might be entitled to suspend the delivery of the Software, Maintenance Services, applicable license key or both to Distributor, Open Ecosystem Partner or End User or both as further set out in this Sell On Premise Distribution Model as well as the Distribution GTCS. 7. If Distributor receives a new copy of the Software, Documentation and/or other SAP Materials that replaces previously provided Software, Documentation and/or other SAP Materials, Distributor must distribute that newest copy provided and either destroy or upon SAP’s request return previous copies. 8. Distributor must not make the Software, Documentation and/or other SAP Materials available to the Open Ecosystem Partner or End User by any means other than by delivering the Software, Documentation and/or other SAP Materials as originally provided by SAP. Distributor’s right to pass on the Software, Documentation and/or other SAP Materials is subject to the provisions of this Agreement.

  • Daily Order Confirmation All Agreement purchase orders will be approved daily by TIPS and sent to vendor. The vendor must confirm receipt of orders to the TIPS Member (customer) within 24 business hours. • Vendor custom website for TIPS: If Vendor is hosting a custom TIPS website, then updated pricing must be posted by 1st of each month.

  • Delivery of Fund Documents The Trust has furnished the Adviser with copies, properly certified or authenticated, of each of the following: