Maintenance of Hosted and Punch-out Catalogs Sample Clauses

Maintenance of Hosted and Punch-out Catalogs. Supplier will provide its Catalog(s) to UC in a file format that will interface seamlessly with UC’s eProcurement systems. These Catalog files will be in compliance with each UC Location’s eProcurement system. UC makes no guarantee of a Go Live Schedule for establishment of a new catalog Systemwide, as each Location is a separate enablement and subject to resource availability. Timelines will be estimated and adjusted by UC as needed for concurrent implementations. For Hosted Catalogs, Supplier must provide UC with updated versions of the Catalog file with, at a minimum, full descriptions and images that Supplier currently utilizes for items offered in its proprietary websites and Punch-out Catalogs. The parties will update each other regarding eCommerce specifications as needed from time to time. Supplier must notify UC’s Contract Administrator at least three (3) weeks in advance of the proposed Go Live Date if it will be requesting additions, deletions, or modifications to the Catalogs. After such advance notification, Supplier must provide UC with Catalog files containing the requested additions, deletions, or modifications with no less than the lead time specified in Section 10 of this appendix. In addition, for price file updates with a mutually agreed upon activation of January 1, Supplier must submit proposed files at least five (5) weeks prior to the first working day in January. Upon UC’s approval of the new Catalog file, UC and Supplier will confirm the Go Live Date; the updated version of the Catalog file will be made effective on that Go Live date. If UC rejects a Catalog more than once because it does not meet UC’s acceptance criteria, the Contract Administrator will suspend Supplier’s price/content change until the date of Supplier’s next acceptable contracted change. If there is a conflict between a price in a Hosted Catalog and a Punch-out Catalog, UC will be invoiced at the lower price. Supplier must notify UC in advance when substituting items, changing SKU numbers or changing the number of items in a package in any Catalog. Content in Supplier catalog is limited to the categories specified in this agreement, with additional categories allowed at UC’s discretion. Supplier agrees that UC may block Catalog items at the category and/or SKU level. The University will require Supplier to clearly identify products as Hazardous Materials, Radioactive, and Controlled Substances in the Supplier’s catalog, whether Hosted or Punch-out. For Punch-out...
Sample 1Sample 2Sample 3See All (8)
AutoNDA by SimpleDocs

Related to Maintenance of Hosted and Punch-out Catalogs

  • Maintenance Manual No later than 60 (sixty) days prior to the Project Completion Date, the Contractor shall, in consultation with the Authority’s Engineer, evolve a maintenance manual (the “Maintenance Manual”) for the regular and preventive maintenance of the Project Highway in conformity with the Specifications and Standards, safety requirements and Good Industry Practice, and shall provide 5 (five) copies thereof to the Authority’s Engineer. The Authority’s Engineer shall review the Maintenance Manual within 15 (fifteen) days of its receipt and communicate its comments to the Contractor for necessary modifications, if any.

  • Operation and Maintenance Manuals Receipts for transmittal of Operation and Maintenance Manuals, Brochures and Data to the Design Professional (or Commissioning Agent) as required by Section 6.1.1.5.

  • Maintenance of Listing The Company will use commercially reasonable efforts to effect and maintain the listing of (x) the Units and Warrants on the NYSE (or another national securities exchange) until the consummation of the Business Combination or until such earlier time at which the Liquidation occurs, and (y) the Common Stock on the NYSE (or another national securities exchange) until five years from the date of the consummation of the Business Combination or until such earlier time at which Liquidation occurs.

  • Minimum Customer Support Requirements for TIPS Sales Vendor shall provide timely and commercially reasonable support for TIPS Sales or as agreed to in the applicable Supplemental Agreement.

  • XXX Hosting 10.1 XXX Hosting is not required for resale in the BellSouth region.

  • Maintenance and Support Services As long as you are not using the Help Desk as a substitute for our training services on the Tyler Software, and you timely pay your maintenance and support fees, we will, consistent with our then-current Support Call Process:

  • Limitations on Reverse Engineering, Decompilation, and Disassembly You may not reverse engineer, decompile, or disassemble the Software, except and only to the extent that such activity is expressly permitted by applicable law notwithstanding this limitation.

  • Aircraft Maintenance Operator shall, at its own expense, cause the Aircraft to be inspected, maintained, serviced, repaired, overhauled, and tested in accordance with FAR Part 91 so that the Aircraft will remain in good operating condition and in a condition consistent with its airworthiness certification and shall take such requirements into account in scheduling the Aircraft hereunder, including but not limited compliance with applicable airworthiness directives and service bulletins. Performance of maintenance, preventive maintenance or inspection shall not be delayed or postponed for the purpose of scheduling the Aircraft unless such maintenance or inspection can safely be conducted at a later time in compliance with applicable laws, regulations and requirements, and such delay or postponement is consistent with the sound discretion of the pilot-in-command. In the event that any non-standard maintenance is required during the term and will interfere with User’s requested or scheduled flights, Operator, or Operator’s pilot-in-command, shall notify User of the maintenance required, the effect on the ability to comply with User’s requested or scheduled flights and the manner in which the parties will proceed with the performance of such maintenance and conduct of such flight(s). In no event shall Operator be liable to User or any other person for loss, injury or damage occasioned by the delay or failure to furnish the Aircraft under this Agreement, whether or not maintenance-related.

  • Maintenance and Support Company is solely responsible for providing any maintenance and support services with respect to the Company application, as specified in this Agreement, or as required under applicable law. You acknowledge that each App Distributor has no obligation whatsoever to furnish any maintenance and support services with respect to the Company application. (3) WARRANTY: Company is solely responsible for any product warranties, whether express or implied by law, to the extent not effectively disclaimed. In the event of any failure of the Company application to conform to any applicable warranty, you may notify an App Distributor, and the App Distributor, in accordance with its terms and policies, may refund the purchase price, if any, paid for the Company application, and to the maximum extent permitted by applicable law, an App Distributor will have no other warranty obligation whatsoever with respect to the Company application, and any other claims, losses, liabilities, damages, costs or expenses attributable to any failure to conform to any warranty will be Company’s sole responsibility. (4)

  • Routine Maintenance (i) CRC shall be responsible for Routine Maintenance when necessary or desirable to maintain the Shared Assets in a safe operating condition, and to permit and facilitate (A) the performance by CRC of its obligations pursuant to this Agreement, and (B) the use of Shared Assets by the Operators in accordance with this Agreement.

Time is Money Join Law Insider Premium to draft better contracts faster.