Build and Demonstrate H2BUG Prototype Vehicle6 Sample Clauses

Build and Demonstrate H2BUG Prototype Vehicle6. The goals of this subtask are to complete the build of the DOE/DOD H2Rescue vehicle which will serve as the prototype for H2BUG, as well as validate the H2Rescue vehicle in emergency response service. • Complete all procurement activity including Hydrogenic Power Module, battery system, hydrogen storage system, traction motor and inverter, and power export system. • Build and assemble the subsystems for the H2Rescue vehicle including vehicle chassis, fuel cell electric powertrain, and export power system. • Test and validate the H2Rescue vehicle at the Cummins facility in Milpitas, California and at the FEMA's Distribution Center in Tracy, California. • Integrate all subsystems into the vehicle chassis. • Validate and commission the system-level H2Rescue vehicle, including approximately 500 miles of on-road testing. • Conduct operational testing per the DOE/DOD validation scenarios. • Prepare a Prototype Build and Validation Report that will serve as the lessons learned to be incorporated into the H2BUG final design. • Prototype Build and Validation Report
Sample 1
AutoNDA by SimpleDocs

Related to Build and Demonstrate H2BUG Prototype Vehicle6

  • Equipment Procurement If responsibility for construction of the Connecting Transmission Owner’s Attachment Facilities or System Upgrade Facilities or System Deliverability Upgrades is to be borne by the Connecting Transmission Owner, then the Connecting Transmission Owner shall commence design of the Connecting Transmission Owner’s Attachment Facilities or System Upgrade Facilities or System Deliverability Upgrades and procure necessary equipment as soon as practicable after all of the following conditions are satisfied, unless the Developer and Connecting Transmission Owner otherwise agree in writing: 5.5.1 NYISO and Connecting Transmission Owner have completed the Interconnection Facilities Study pursuant to the Interconnection Facilities Study Agreement; 5.5.2 The NYISO has completed the required cost allocation analyses, and Developer has accepted his share of the costs for necessary System Upgrade Facilities and System Deliverability Upgrades in accordance with the provisions of Attachment S of the NYISO OATT; 5.5.3 The Connecting Transmission Owner has received written authorization to proceed with design and procurement from the Developer by the date specified in Appendix B hereto; and 5.5.4 The Developer has provided security to the Connecting Transmission Owner in accordance with Article 11.5 by the dates specified in Appendix B hereto.

  • Procurement procedures 11.1 The Recipient must secure the best value for money and shall act in a fair, open and non-discriminatory manner in all purchases of goods and services.

  • Technical Safeguards 1. USAC and DSS will process the data matched and any data created by the match under the immediate supervision and control of authorized personnel to protect the confidentiality of the data, so unauthorized persons cannot retrieve any data by computer, remote terminal, or other means. 2. USAC and DSS will strictly limit authorization to these electronic data areas necessary for the authorized user to perform their official duties. All data in transit will be encrypted using algorithms that meet the requirements of the Federal Information Processing Standard (FIPS) Publication 140-2 or 140-3 (when applicable). 3. Authorized system users will be identified by User ID and password, and individually tracked to safeguard against the unauthorized access and use of the system. System logs of all user actions will be saved, tracked and monitored periodically. 4. USAC will transmit data to DSS via encrypted secure file delivery system. For each request, a response will be sent back to USAC to indicate success or failure of transmission.

  • Other Methods of Procurement of Goods and Works The following table specifies the methods of procurement, other than International Competitive Bidding, which may be used for goods and works. The Procurement Plan shall specify the circumstances under which such methods may be used: (a) National Competitive Bidding (b) Shopping (c) Direct Contracting

  • Technical Specifications The Technical Specifications furnished on the CD are intended to establish the standards for quality, performance and technical requirements for all labor, workmanship, material, methods and equipment necessary to complete the Work. When specifications and drawings are provided or referenced by the County, these are to be considered part of the Scope of Work, and to be specifically documented in the Detailed Scope of Work. For convenience, the County supplied specifications, if any, and the Technical Specifications furnished on the CD.

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

  • Procurement of Goods and Services (a) If the HSP is subject to the procurement provisions of the BPSAA, the HSP will abide by all directives and guidelines issued by the Management Board of Cabinet that are applicable to the HSP pursuant to the BPSAA. (b) If the HSP is not subject to the procurement provisions of the BPSAA, the HSP will have a procurement policy in place that requires the acquisition of supplies, equipment or services valued at over $25,000 through a competitive process that ensures the best value for funds expended. If the HSP acquires supplies, equipment or services with the Funding it will do so through a process that is consistent with this policy.

  • Particular Methods of Procurement of Goods and Works International Competitive Bidding. Goods and works shall be procured under contracts awarded on the basis of International Competitive Bidding.

  • Project Implementation Manual The Recipient, through the PCU, shall: (i) take all action required to carry out Parts 1.1, 1.3, 1.4, 2, 3.1(b), 3.2, 3.3 and 4 (ii) of the Project in accordance with the provisions and requirements set forth or referred to in the Project Implementation Manual; (ii) submit recommendations to the Association for its consideration for changes and updates of the Project Implementation Manual as they may become necessary or advisable during Project implementation in order to achieve the objective of Parts 1.1, 1.3, 1.4, 2, 3.1(b), 3.2, 3.3 and 4(ii) of the Project; and (iii) not assign, amend, abrogate or waive the Project Implementation Manual or any of its provisions without the Association’s prior agreement. Notwithstanding the foregoing, if any of the provisions of the Project Implementation Manual is inconsistent with the provisions of this Agreement, the provisions of this Agreement shall prevail and govern.

  • Registry Interoperability and Continuity Registry Operator shall comply with the Registry Interoperability and Continuity Specifications as set forth in Specification 6 attached hereto (“Specification 6”).

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