Project steps Sample Clauses

Project steps. Literature research Search for suitable physiological data processing techniques. Working hours: 20 Physiological data processing model development Exploring hardware attributes, detecting unsuitable influences, model development. Working hours: 80
Sample 1
AutoNDA by SimpleDocs
Project steps. This project will be completed in accordance with Pro-Dex’s Product Development Procedure. An outline of the steps Pro-Dex and Mako will take to design and test the BCDS is presented below:
Sample 1
Project steps. Literature research and formulating hypotheses - 3 ECTS Purpose & goal To gain knowledge on (i) the various aspects of stereotypes and prejudice and ways of measuring their expression, (ii) potential individual differences in stereotyping, (iii) assessing cognitive abilities, primarily the inhibition control.
Sample 1
Project steps. Literature research October 11th – November 5th Preliminary literature was provided by project supervisor serving both as an introductory and inspirational reading on the topic of mirror neurons. Further reading consisted mostly of journal papers discussing mirror neuron system in context of action execution/observation and connection with autism spectrum disorder (x.x. Xxxxxxxxxx et al. 2001, Xxxxxxx et al. 2007, Xxxxxxxx 2009). Acquired insight into this topic was demonstrated during the literature review meeting and by submitting a research draft comprising of an introduction to mirror neuron research and outlines for our own project, prior to the first journal club. Formulating hypotheses We expect certain levels of mu rhythm suppression in each tested condition, except the white noise. Stronger suppression is expected in human and with-object conditions. Planning of experiment
Sample 1
Project steps. Initial Literature Research (Overview) Total Working Hours (WH)/ECTS: 3 / 10 Working- package (WP) Start – End WH / ECTS Activities Resources required Mile- stones (M) WP_INIT_1 10.17 2 Initial survey of existing literature to identify areas that merit closer examination within broad topic. Identify areas of focus Computer, access to papers, journals M1_Lit_1
Sample 1
Project steps. Initial Literature Research (Overview) Total Working Hours (WH)/ECTS: 1 / 5 Working- package (WP) Start – End WH / ECTS Activities Resources required Mile- stones (M) WP_INIT_1 10.17 – 11.17 0,5 Read introductory literature on working with artificial neural networks. Familiarize with uses and applications of different types of networks Access to literature, journals M1_Lit WP_INIT_2 10.17 – 11.17 0,5 Search for and read tutorials and carry out introductory exercises Access to tutorials M2_Tut Conceptualisation Total WH/ECTS: 0 / 5 Working- package (WP) Start – End WH / ECTS Activities Resources required Mile- stones (M) WP_CONCEPT_1 10.17 – 11.17 0 Pick a simple, well-defined problem or problems to test newly skills on – no conceptualisation of own problem Co-operation with supervisor M3_Con Programming/Implementing the Model Total WH/ECTS: 2 / 5 Working- package (WP) Start – End WH / ECTS Activities Resources required Mile- stones (M) WP_IMP_1 11.17 – 01.18 2 Implement one or several small artificial neural networks. Iterative testing and application of different types of networks to develop broad competences. Training of model. Computer, access to tools, programming environment, time with supervisor, tutorials M4_Prog Running and Analysing the Model Total WH/ECTS: 1.5 / 5 Working- package (WP) Start – End WH / ECTS Activities Resources required Mile- stones (M)
Sample 1
Project steps. Recherché & literature research In preparation for this project, we already researched the literature and found a sensible study paradigm by Xxxxx et al. (2008) and thought about possible modifications. After methodological reasoning and in contrast to the majority of clinical studies concerning placebo, we settled for a similar study design with healthy subjects, as there are no confounding effects due to disease. However, a psychological approach with evaluation of personality traits would add an important perspective and more insight into the phenomenon. The Milestones of these steps have already been passed, but the final study design has still to be discussed: Already Passed Milestones: Milestone Date Rough project idea 01.10.2011 Discussion with Urban Xxxxxx and Xxxxx Xxxxx 11.10.2011 Discussion with Svezdan Pirtosek 12.10.2011 Discussion with Jure Bon 25.10.2011 First Discussion with Xxxx Xxxxxxxxx 26.10.2011 (final supervisor) Milestones in the future: Milestone Date Presentation of Placebo study and Theoretical background in Cognitive Journal Club 16.11.2011 Start of the Project 21.11.2011 Deadline for preliminary results mid January Deadline for Data Analysis end January Deliverables: A Laboratory Journal documenting the work with the subjects in the experiment as well as the training for the phenomenological subgroup. A dataset in table format of preliminary results including physiological data and phenomenological protocols due mid January. A statistical analysis of the given dataset due end of January. A final report in form of a paper. Formulating hypotheses The original hypothesis was formed in beginning of October and followed by a vivid discussion with a manifold of competences in the University of Ljubljana (see milestones above). Our working hypotheses propose that (1) the expectation of the enhancement will lead to the measurable changes in physical and cognitive performance in susceptible individuals under placebo condition compared to their performance under control or baseline condition, and (2) expectation- induced performance enhancement will correlate with certain personality traits. Planning of experiment Steps Done/ due to on Literature Research Sept - Dec 2011 Formulation of hypothesis 01.10 2011 Presentation and discussion of hypothesis and background 16.11.2011 Second round of discussion Hypothesis adaption end of November Final Presentation and end of November Discussion(research meeting) Start of Experiment 01.12.2011 Start...
Sample 1
AutoNDA by SimpleDocs
Project steps. The first step of this project is dedicated to the definition of a common data interface to acquire data and measurements coming from sensors, IS machine, process variables and cold end inspection systems, with the objective of storing them in an integrated database, organised according to a coherent and statistically meaningful data structure. Starting with a defined and populated information base, a large data analysis methodology is developed to correlate hot end and cold end data and measurements (with the support of a container tracking system), with the target of identifying the key process parameters able to describe: Correlation between HE measurements. Geometrical characteristics of containers.
Sample 1
Project steps. Project Kickoff For Portrait and Gallery projects, you will be matched with a Project Manager (PM) to lead the project, starting with a quick questionnaire to get the ball rolling. All logos, photos, colors, etc., are collected. If you choose a Portrait design solution, we also ask for examples of site designs you like. For Portrait and Gallery projects, you and your dedicated PM will have a call to go over all of the details of the project, including timeline, project scope, and expectations. If you opt for a Portrait design, we’ll discuss what look and feel you want for your site and what should be featured on the homepage, header, navigation, etc. A design plan is drawn up and handed over to the design team. For Sketches projects, you will select your design and answer a questionnaire through email to send us your logo, colors, and photos. Design Process Once your design is ready, we review it internally to ensure it meets all of your requirements and follows best practices for a friendly user experience. Your PM will present an initial mock-up website design and coordinate revisions, if needed. Three rounds of revisions are included in Portrait. One round of revisions is included in Gallery. Sketches are designed to be used out of the box.
Sample 1

Related to Project steps

  • Project Staff Contractor shall appoint to the Project Staff: (i) individuals with suitable training and skills to provide the Work, and (ii) sufficient staffing to adequately provide the Work. Contractor shall make commercially reasonable efforts consistent with sound business practices to honor the specific request of the JBE with regard to assignment of its employees. The JBE may require Contractor to remove any personnel from the Project Staff that interact with any personnel of the Judicial Branch Entities or JBE Contractors (including, without limitation, the Contractor Project Manager) upon providing to Contractor a reason (permitted by law) for such removal. Contractor may, with the JBE’s consent, continue to retain such member of the Project Staff in a role that does not interact with any personnel of the Judicial Branch Entities or

  • Project Schedule Construction must begin within 30 days of the date set forth in Appendix A, Page 2, for the start of construction, or this Agreement may become null and void, at the sole discretion of the Director. However, the Recipient may apply to the Director in writing for an extension of the date to initiate construction. The Recipient shall specify the reasons for the delay in the start of construction and provide the Director with a new start of construction date. The Director will review such requests for extensions and may extend the start date, providing that the Project can be completed within a reasonable time frame.

  • Project Coordination The Engineer shall coordinate all subconsultant activity to include quality and consistency of deliverables and administration of the invoices and monthly progress reports. The Engineer shall coordinate with necessary local entities.

  • Project Plans The Contractor: must carry out the Contractor's Activities in accordance with, and otherwise implement, the Project Plans; and for the purposes of subparagraph (i), must: prepare Project Plans based, where applicable, on the draft Project Plans lodged by the Contractor in its tender for the Contractor's Activities, and otherwise in accordance with the requirements of the Contract and submit them to the Contract Administrator so as to ensure that there is no delay or disruption to the Contractor's Activities and in any event no later than the number of days specified in the Contract Particulars after the Award Date for each Project Plan; not commence any of the Contractor's Activities to which any Project Plan applies, unless the Contract Administrator has had the number of days specified in the Contract Particulars for each Project Plan to review the Project Plan and has not rejected the Project Plan; if any Project Plan is rejected, submit an amended Project Plan to the Contract Administrator; in any event, finalise each Project Plan so as to ensure that there is no delay or disruption to the Contractor's Activities and in any event in accordance with the requirements of the Contract to the satisfaction of the Contract Administrator; after each Project Plan has been finalised: regularly review, update and amend each Project Plan in accordance with the process set out in each Project Plan (and otherwise at least on each anniversary of the Award Date); update or amend a Project Plan on request of the Contract Administrator; and continue to correct any defects in or omissions from a Project Plan (whether identified by the Contract Administrator or the Contractor), and submit an updated or amended Project Plan to the Contract Administrator, after which: the Contractor must continue to comply with the requirements of the then current Project Plan until the process in subparagraph (ii) has been completed in respect of the updated or amended Project Plan; and subsubparagraphs B - E will apply (to the extent applicable); and document and maintain detailed records of all: reviews, updates, amendments and submissions of each Project Plan; audits or other monitoring of each Project Plan; and training and awareness programs and communications provided to Contractor and subcontractor personnel in respect of each Project Plan (including each updated or amended Project Plan). The Contractor will not be relieved from compliance with any of its obligations under the Contract or otherwise at law or in equity as a result of: the implementation of, and compliance with, the requirements of any Project Plan; any direction by the Contract Administrator concerning a Project Plan or the Contractor's compliance or non-compliance with a Project Plan; any audit or other monitoring by the Contract Administrator or anyone else acting on behalf of the Commonwealth of the Contractor's compliance with a Project Plan; or any failure by the Contract Administrator, or anyone else acting on behalf of the Commonwealth, to detect any defect in or omission from a Project Plan including where any such failure arises from any negligence on the part of the Contract Administrator or other person.

  • PROJECT SERVICES Landlord shall furnish services as follows:

  • Project Specific Milestones In addition to the milestones stated in Section 212.5 of the Tariff, as applicable, during the term of this ISA, Interconnection Customer shall ensure that it meets each of the following development milestones:

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

  • Project Deliverables The Contractor shall provide each of the following deliverables in writing to the City for review and approval to achieve the project objectives.

  • Vendor Encouraging Members to bypass TIPS agreement Encouraging entities to purchase directly from the Vendor or through another agreement, when the Member has requested using the TIPS cooperative Agreement or price, and thereby bypassing the TIPS Agreement is a violation of the terms and conditions of this Agreement and will result in removal of the Vendor from the TIPS Program.

  • Project Scope The physical scope of the Project shall be limited to only those capital improvements as described in Appendix A of this Agreement. In the event that circumstances require a change in such physical scope, the change must be approved by the District Committee, recorded in the District Committee's official meeting minutes, and provided to the OPWC Director for the execution of an amendment to this Agreement.

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