Acceptance of Hardware and Software Sample Clauses

Acceptance of Hardware and Software. Acceptance or rejection of the items to be delivered under the Contract shall be determined on the basis of the Contractor demonstrating to the satisfaction of ASG’s delivery and acceptance requirements identified in Article 4 of this Contract and in Appendix C hereto that the items have been constructed in accordance with the appropriate specifications and have satisfactorily concluded testing in accordance with the test plans and procedures approved by ASG. Non flight-deliverables shall be accepted according to an acceptance test procedure to be proposed by the Contractor and agreed by ASG.
Sample 1Sample 2
AutoNDA by SimpleDocs
Acceptance of Hardware and Software. Acceptance or rejection of the items to be delivered under the Contract shall be determined on the basis of the Contractor demonstrating to the satisfaction of Astrium that the items have been constructed in accordance with the appropriate specifications and have satisfactorily concluded testing in accordance with the test plans and procedures approved by Astrium. Acceptance of the DC DC Converters shall be on successful completion of the SES DRB.
Sample 1
Acceptance of Hardware and Software. Acceptance or rejection of the items to be delivered under the Contract shall be determined on the basis of the Contractor demonstrating compliance acceptance criteria and/or with relevant requirements, as confirmed by the Prime Contractor that the items have been constructed in accordance with the appropriate specifications and have satisfactorily concluded testing in accordance with the test plans and procedures approved by the Prime Contractor. Acceptance of flight items to be delivered under the Contract shall be determined on the basis of the Contractor demonstrating to the satisfaction of the Prime Contractor and the Agency that the items have been constructed in accordance with the appropriate specifications and have satisfactorily concluded testing in accordance with the test plans and procedures approved by the Prime Contractor and the Agency in related ADs. Acceptance of non-flight items shall take place after successful completion of their Acceptance Review, having gone through and successfully passed the individual acceptance tests and procedure to be proposed by the Contractor and agreed by the Prime Contractor. Acceptance of other items shall take place after successful completion of their Acceptance Review, having gone through and successfully passed the individual acceptance tests and procedure to be proposed by the Contractor and agreed by the Prime Contractor.
Sample 1
Acceptance of Hardware and Software. Acceptance or rejection of the items to be delivered under the Contract shall be determined on the basis of the Contractor's evidence that the items have been constructed in accordance with the appropriate specifications and have satisfactorily concluded testing in accordance with the test plans and procedures approved by Micos in related ADs herein. Acceptance of the Telescope EM, OM(R) and PFM including its associated supporting hardware, software and documentation and all other items covered by this Contract shall take place as follows: i. The Preliminary Acceptance of the Flight HW shall take place at successful completion of the Subsystem Delivery Review Board (DRB), as defined in the GSOW in Appendix C hereto; Such acceptance shall release the consent to ship. ii. The Final Acceptance (as defined in section 11.3.5 of GSOW in Appendix C) of the Flight HW shall take place after review of the delivered documentation (updated EIDP), closure of all actions from DRB, after successful completion of the Post Delivery Inspection (according to the procedure outlined in section 11.3.4 of GSOW in Appendix C hereto), successful integration/test of the Sub- system at Instrument level and successful completion of Sub-system Final Acceptance (AR) as defined in GSOW section 11.3.4 and closure of the actions of Qualification Review (QR) defined in the section 1.2.1.5. iii. Acceptance of all other items shall take place after successful completion of their DRBs, having gone through and successfully passed the individual acceptance tests and Post-Delivery Inspection (according to the procedure outlined in section 11.3.4 of GSOW in Appendix C hereto). Procedure shall be proposed by the Contractor and agreed by Micos.
Sample 1
Acceptance of Hardware and Software. Acceptance or rejection of the items to be delivered under the Contract shall be determined on the basis of the Contractor demonstration to the satisfaction of ALCATEL that the items have been constructed in accordance with the appropriate specifications and have satisfactorily concluded testing in accordance with ALCATEL approved test plans and procedures.
Sample 1
Acceptance of Hardware and Software. Acceptance or rejection of the Contract Items to be delivered under the Contract shall be determined on the basis of the Contractor demonstrating to the satisfaction of TAS-F that the Contract Items have been constructed in accordance with the appropriate specifications and have satisfactorily concluded testing in accordance with the test plans and procedures approved by TAS-F. Preliminary acceptance of any hardware by TASF shall be pronounced against successful results from tests at the facility of the Contractor during the TRB and DRB. Such preliminary acceptance releases shipment of the item. The final acceptance shall be pronounced by TAS-F after review of the delivered documentation (EIDP), closure of all actions from DRB and QR and successful completion of the dedicated satellite FAR or PSR (whichever is the earlier). Such Final Acceptance shall release the warranty of the Contract Items. Non flight-Contract Items shall be accepted according to an acceptance test procedure to be proposed by the Contractor and agreed by TAS-F.
Sample 1

Related to Acceptance of Hardware and Software

  • Hardware and Software In order to use the Services, you must obtain and maintain, at your expense, compatible hardware and software as specified by Credit Union from time to time. Credit Union is not responsible for any third party software you may need to use the Services. Any such software is accepted by you as is and is subject to the terms and conditions of the software agreement you enter into directly with the third party software provider at time of download and installation.

  • Required hardware and software The minimum system requirements for using the DocuSign system may change over time. The current system requirements are found here: xxxxx://xxxxxxx.xxxxxxxx.xxx/guides/signer-guide- signing-system-requirements.

  • Equipment and Software To use the Mobile Remote Deposit Services, you must obtain and maintain at your expense, compatible equipment and software that we may specify from time to time.

  • Hardware and Software Requirements In order to access and retain Disclosures electronically, you must satisfy the following computer hardware and software requirements: access to the Internet; an email account and related software capable of receiving email through the Internet; a web browser which is SSL-compliant and supports secure sessions, and hardware capable of running this software.

  • Software and Documentation Licensee may make as many copies of the Software necessary for it to use the Software as licensed. Each copy of the Software made by Licensee must contain the same copyright and other notices that appear on the original copy. Licensee will not modify the Documentation. Documentation may: (a) only be used to support Licensee’s use of the Software; (b) not be republished or redistributed to any unauthorized third party; and (c) not be distributed or used to conduct training for which Licensee, or any other party, receives a fee. Licensee will not copy any system schema reference document related to the Software.

  • 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 (xxxx://xxxxxxx.xxx.xxx/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.

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

  • Hardware Warranty Company warrants that for a period of one (1) year from delivery of Hardware, Hardware will be free from defects in material and workmanship in normal use, but does not cover any of the following: (i) improper installation, maintenance, adjustment, repair or modification by Customer or a third party; (ii) misuse, neglect, or any other cause other than ordinary use, including without limitation, accidents or acts of God; (iii) improper environment, excessive or inadequate heating or air conditioning, electrical power failures, surges, water damage or other irregularities; (iv) third party software or software drivers; or (v) damage during shipment.

  • Third Party Software 1. The Software may contain third party software that requires and/or additional terms and conditions. Such required third party software notices and/or additional terms and conditions are located at xxxx://xxx.xxxxxxxxx.xxx/thirdparty/index.html and are made a part of and incorporated by reference into this XXXX. By accepting this XXXX, You are also accepting the additional terms and conditions, if any, set forth therein.

  • Licensed Software Computer program(s) provided by Contractor in connection with the Deliverables, subject to Section 14 of this Contract.

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