TASK WP4.3: RFTECH Sample Clauses

TASK WP4.3: RFTECH. Progress towards objectives The RFTech network follows the pattern of events anticipated in the contract, with, in addition, participation in external events tightly linked to the RFTech objectives, plus a few topical workshops. # Topic Organizers Time Place Registrants 1 Integrated Circuits for Low Level RF RFTech 24-26 May 2012 Warsaw / Poland ~300 2 Higher Order Modes in SC RF CI, ICFA, ASTeC, IoP, RFTech 25-27 Jun 2012 Daresbury/ UK 59 3 Advanced Low Level RF Control RFtech 6-8 Aug 2012 Lodz / Poland 43 4 Computing in Accelerator Physics U. Rostock, EuroLumi, RFTech, CST 19-25 Sep 2012 Warnemünde, Germany about 100 from EU, US, Russia, and Japan 5 Low Level RF for XFEL RFTech 19-21 Feb 2013 Xxxxxx/ Poland 55 6 4th Annual RFTech Meeting RFTech 24-26 Feb 2013 Annecy/ France 33 These workshops provided excellent opportunities to share experience among several fields of RF technology, from low-level systems to solid-state power amplifiers. More specifically, the 4th RFTech workshop covered a large range of RF topics, including C- band RF, X-band RF, reliability, LLRF, RF diagnostics, reliability, costing, breakdown, operation, klystron lifetime, and RF efficiency; and it also addressed RF issues for many important present or planned accelerator facilities, e.g. SPIRAL2, MYRRHA/MAX, CLIC, TESLA, XXX-XX, LHeC ERL, TLEP, LHC, FLASH, PS Booster, MedAustron, and SwissFEL. Participants came from DESY, CERN, INF-INFN, TUD, UROS, GANIL, PSI, LPSC/CNRS, UJF, TUL, and ISE-WUT. RFTech also organized or co-organized several topical workshops related to low-level RF control, as well as special sessions at the MixDes2012 Conference on Mixed Design for Integrated Circuits and Systems with applications to accelerator RF systems, and at the ICAP’13 on accelerator RF related computing. Some RFTech experts also attended the IEEE Conference workshop on Real Time techniques, RT2012, in June 2012. An important result is a (so far draft) report on strategy/results for cavity design, LLRF & HPRF systems and design integration, and costing tools. Contractual milestones and deliverables
AutoNDA by SimpleDocs

Related to TASK WP4.3: RFTECH

  • Technology Research Analyst Job# 1810 General Characteristics Maintains a strong understanding of the enterprise’s IT systems and architectures. Assists in the analysis of the requirements for the enterprise and applying emerging technologies to support long-term business objectives. Responsible for researching, collecting, and disseminating information on emerging technologies and key learnings throughout the enterprise. Researches and recommends changes to foundation architecture. Supports research projects to identify and evaluate emerging technologies. Interfaces with users and staff to evaluate possible implementation of the new technology in the enterprise, consistent with the goal of improving existing systems and technologies and in meeting the needs of the business. Analyzes and researches process of deployment and assists in this process.

  • Design Development Phase Services 3.3.1 Based on the Owner’s approval of the Schematic Design Documents, and on the Owner’s authorization of any adjustments in the Project requirements and the budget for the Cost of the Work, the Architect shall prepare Design Development Documents for the Owner’s approval. The Design Development Documents shall illustrate and describe the development of the approved Schematic Design Documents and shall consist of drawings and other documents including plans, sections, elevations, typical construction details, and diagrammatic layouts of building systems to fix and describe the size and character of the Project as to architectural, structural, mechanical and electrical systems, and other appropriate elements. The Design Development Documents shall also include outline specifications that identify major materials and systems and establish, in general, their quality levels.

  • Technology Transfer Subject to the terms of the Development Supply Agreement, as soon as reasonably practicable, but in no event later than the fifth (5th) anniversary of the Effective Date, Alnylam shall initiate a technology transfer to MedCo, or to its Third Party manufacturer(s) of Licensed Product, selected by MedCo and reasonably acceptable to Alnylam, of Alnylam Know-How that is reasonably necessary or useful for the Manufacture of the Licensed Product, and shall make available its personnel on a reasonable basis to consult with MedCo or such Third Party manufacturer(s) with respect thereto, all at MedCo’s expense, including the Costs reasonably incurred by Alnylam in connection with such technology transfer activities. MedCo shall reimburse Alnylam such Costs incurred with respect to such Manufacturing technology transfer within [***] days after receipt of an invoice therefor. Alnylam and its Affiliates shall keep complete and accurate records in sufficient detail to enable the payments payable hereunder to be determined. Alnylam shall not be required to perform technology transfer to more than one Third Party manufacturer for each stage of the Licensed Product supply chain (i.e., Bulk Drug Substance, Bulk Drug Product and Finished Product). Promptly after MedCo’s written request, Alnylam shall use Commercially Reasonable Efforts to assign to MedCo any manufacturing agreement between Alnylam and a Third Party that is solely related to the manufacture of Licensed Products. Such assignment shall be subject to the terms and conditions of such agreement, including any required consents of such Third Party and MedCo’s written agreement to assume all the obligations of Alnylam under such agreement to be undertaken after such assignment, but Alnylam shall remain solely responsible for its obligations under such agreement arising prior to such assignment. Except as provided in the immediately preceding sentence, MedCo shall be solely responsible for contracting with such Third Party manufacturer (and any other Third Party manufacture to whom Alnylam has initiated technology transfer as set forth in this Section 5.3) for the supply of such Licensed Product and Alnylam shall have no obligations under such agreement between MedCo and such Third Party manufacturer. Alnylam shall use Commercially Reasonable Efforts to obtain any such consent in a form reasonably acceptable to MedCo.

  • Software Development Software designs, prototypes, and all documentation for the final designs developed under this agreement must be made fully transferable upon direction of NSF. NSF may make the software design, prototype, and documentation for the final design available to competitors for review during any anticipated re-competition of the project.

  • Support and Maintenance Services Information about Teradici’s support and maintenance for the Licensed Product may be found at xxxxx://xxxx.xxxxxxxx.xxx.

  • Software License Agreement 1) Customers acquiring software licenses under the Contract shall hold, use and operate such software subject to compliance with the Software License Agreement set forth in Appendix D of this Contract. No changes to the Software License Agreement terms and conditions may be made unless previously agreed to between Vendor and DIR. Customers may not add, delete or alter any of the language in Appendix D; provided however, that a Customer and Vendor may agree to additional terms and conditions that do not diminish a term or condition in the Software License Agreement, or in any manner lessen the rights or protections of Customer or the responsibilities or liabilities of Vendor. Order Fulfiller shall make the Software License Agreement terms and conditions available to all Customers at all times.

  • Statement of Work The Contractor shall provide the services and staff, and otherwise do all things necessary for or incidental to the performance of work, as set forth below:

  • Technical Support Services 2.1 The technical support services (the "Services"): Party A agrees to provide to Party B the relevant services requested by Party B, which are specified in Exhibit 1 attached hereto ("Exhibit 1").

  • Development Schedule The Project shall substantially comply with the specific timetables and triggers for action set forth in Article 5 of this Agreement. The parties acknowledge that, as provided in G.S. 160A-400.25(b), the failure to meet a commencement or completion date shall not, in and of itself, constitute a material breach of this Agreement pursuant to G.S. 160A-400.27 but must be judged based upon the totality of the circumstances.

  • Routine Maintenance Services PM1.03.2-1 Respond immediately to restrict all access to Highway Crossing Infrastructure, as directed by the Province.

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