Scientific and Technical Project Objectives Sample Clauses

Scientific and Technical Project Objectives. On the basis of the previous discussion, we are planning to analyse existing GALS solutions with stretchable or data-driven clocking, and GALS solutions with an asynchronous FIFO interconnect and independent local clocking. During the project we will select optimal GALS architectures for the target applications and define the communication interfaces (8th month of the project). The suggested "optimal" solutions should be based on the existing GALS architectures. However, it is expected that selected the GALS design could incorporate several optimized features in terms of hardware complexity, performance, power dissipation and EMI. We will consider also integration of the GALS interfaces into the NoC application scenario. The criteria for selecting and generating the optimal GALS architecture are based on conformity to the rules and directions and to the probable target application named in Section B1. The proposed solution should have scalable interfaces and, where possible, its source code will be offered as an open core. In this project, a GALS framework providing interoperability between design tools for rapid design and prototyping will be proposed. This design flow will be based on commercial CAD tools and on the existing Balsa framework [BAR00] with extensions to mixed synchronous-asynchronous systems. Balsa has until now been used for designing pure asynchronous circuits. The main idea is to integrate the Balsa language and tools in a system level design environment, where Balsa will be seen just as any other language, in order to allow mixed descriptions of synchronous and asynchronous circuits. Consequently, we will generate a system level design tool that is able to handle IP blocks referring to Balsa, Verilog, VHDL and SystemC specifications with an open plug-in interface to easily accept new languages and tool flows. The emphasis will be on a graphical system-level design environment acting as a controller and interoperability layer between conventional CAD tools. Firstly, a tool flow will handle the dependencies, file format requirements and incompatibilities between tools, and will control the sequential execution of format conversion, compilation, synthesis and simulation tools. A co- simulation back-plane will provide interoperability between the simulators and emulators from different vendors, enabling the co-simulation and co-debugging of unrelated languages and hardware targets (internal version 19th month of the project, final version 3...
Sample 1
AutoNDA by SimpleDocs

Related to Scientific and Technical Project Objectives

  • For Product Development Projects and Project Demonstrations  Published documents, including date, title, and periodical name.  Estimated or actual energy and cost savings, and estimated statewide energy savings once market potential has been realized. Identify all assumptions used in the estimates.  Greenhouse gas and criteria emissions reductions.  Other non-energy benefits such as reliability, public safety, lower operational cost, environmental improvement, indoor environmental quality, and societal benefits.  Data on potential job creation, market potential, economic development, and increased state revenue as a result of the project.  A discussion of project product downloads from websites, and publications in technical journals.  A comparison of project expectations and performance. Discuss whether the goals and objectives of the Agreement have been met and what improvements are needed, if any.

  • Development Plan document specifying the work program, schedule, and relevant investments required for the Development and the Production of a Discovery or set of Discoveries of Oil and Gas in the Contract Area, including its abandonment.

  • Program Objectives In performing its responsibilities with respect to the management and administration of the Program, each party shall be guided by the following Program objectives:

  • TECHNICAL TASKS Products that require a draft version are indicated by marking “(draft and final)” after the product name in the “Products” section of the task/subtask. If “(draft and final)” does not appear after the product name, only a final version of the product is required. Subtask 1.1 (Products) describes the procedure for submitting products to the CAM.

  • Additional Information for Product Development Projects Outcome of product development efforts, such copyrights and license agreements. • Units sold or projected to be sold in California and outside of California. • Total annual sales or projected annual sales (in dollars) of products developed under the Agreement. • Investment dollars/follow-on private funding as a result of Energy Commission funding. • Patent numbers and applications, along with dates and brief descriptions.  Additional Information for Product Demonstrations: • Outcome of demonstrations and status of technology. • Number of similar installations. • Jobs created/retained as a result of the Agreement.

  • DEVELOPMENT OR ASSISTANCE IN DEVELOPMENT OF SPECIFICATIONS REQUIREMENTS/ STATEMENTS OF WORK Firms and/or individuals that assisted in the development or drafting of the specifications, requirements, statements of work, or solicitation documents contained herein are excluded from competing for this solicitation. This shall not be applicable to firms and/or individuals providing responses to a publicly posted Request for Information (RFI) associated with a solicitation.

  • Project Plan Development of Project Plan Upon the Authorized User’s request, the Contractor must develop a Project Plan. This Project Plan may include Implementation personnel, installation timeframes, escalation procedures and an acceptance plan as appropriate for the Services requested. Specific requirements of the plan will be defined in the RFQ. In response to the RFQ, the Contractor must agree to furnish all labor and supervision necessary to successfully perform Services procured from this Lot. Project Plan Document The Contractor will provide to the Authorized User, a Project Plan that may contain the following items: • Name of the Project Manager, Contact Phone Numbers and E-Mail Address; • Names of the Project Team Members, Contact Phone Numbers and E-Mail Address; • A list of Implementation milestones based on the Authorized User’s desired installation date; • A list of responsibilities of the Authorized User during system Implementation; • A list of designated Contractor Authorized Personnel; • Escalation procedures including management personnel contact numbers; • Full and complete documentation of all Implementation work; • Samples of knowledge transfer documentation; and • When applicable, a list of all materials and supplies required to complete the Implementation described in the RFQ. Materials and Supplies Required to Complete Implementation In the event that there are items required to complete an Implementation, the Contractor may request the items be added to its Contract if the items meet the scope of the Contract. Negotiation of Final Project Plan If the Authorized User chooses to require a full Project Plan, the State further reserves the right for Authorized Users to negotiate the final Project Plan with the apparent RFQ awardee. Such negotiation must not substantively change the scope of the RFQ plan, but can alter timeframes or other incidental factors of the final Project Plan. The Authorized User will provide the Contractor a minimum of five (5) business days’ notice of the final negotiation date. The Authorized User reserves the right to move to the next responsible and responsive bidder if Contractor negotiations are unsuccessful.

  • 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.

  • Research, Science and Technology Cooperation 1. The aims of cooperation in research, science and technology, carried out in the mutual interest of the Parties and in compliance with their policies, will be: (a) to build on existing agreements already in place for cooperation on research, science and technology; (b) to encourage, where appropriate, government agencies, research institutions, universities, private companies and other research organizations in the Parties to conclude direct arrangements in support of cooperative activities, programs or projects within the framework of this Agreement, specially related to trade and commerce; and (c) to focus cooperative activities towards sectors where mutual and complementary interests exist, with special emphasis on information and communication technologies and software development to facilitate trade between the Parties. 2. The Parties will encourage and facilitate, as appropriate, the following activities including, but not limited to:

  • Research Project 3.1 These Materials and Data will be used by Recipient's PI solely in connection with the Research Project, as named and described in the attached research application (insert Research Project name below):

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