Project Roles Sample Clauses

Project Roles. PD/PI Co PD/PI Faculty Community College Faculty Technical School Faculty K-12 Teacher Postdoctoral (scholar, fellow or other postdoctoral position) Other Professional Technician Staff Scientist (doctoral level) Statistician Graduate Student (research assistant) Non-Student Research Assistant Undergraduate Student Technical School Student High School Student Consultant Research Experience for Undergraduates (REU) Participant Other (specify)
AutoNDA by SimpleDocs
Project Roles. A general description of the roles defined for the organizational project structured is provided as follows. The role participation and their detailed responsibilities are described in the implementation approach.
Project Roles. Customer, through its Administrators, will assign a role to each User of a Project as further described in the Documentation. A User’s role will dictate the permissions such User has with respect to such Project.
Project Roles. IMPLEMENTOR commits to provide consultants to execute this project according to the agreed scope with at least, but not limited to, the following key roles: ❑ Project Manager– to cover the project management activities.
Project Roles. Prior to commencement of Services, Client and Gensler will each provide the names of their key Project team members, including the primary contact person and the person authorized to make decisions for Gensler and the Client:
Project Roles. Project Manager Kahoa shall provide a Project Manager as the primary point of contact to coordinate between the Client and Kahoa. The Project Manager’s responsibilities include: ● Providing the Client with progress reports ● Facilitating and guiding Agile process meetings, including, sprint planning, backlog refinement, sprint reviews, and sprint retrospectives ● Coordinating with the Client and managing team members for timely resolutions and to remove roadblocks ● Properly addressing and coordinating any staffing requirements ● Planning and coordinating training for the team on the Agile processes or other information vital to the project, if needed. ● Team leadership, coaching, and mentoring ● Owning and driving the Agile sprint cadence Development & Design Team This cross-functional team is responsible for the design and development activities within each Sprint and includes members who are skilled in areas such as UX design, user testing, database management, coding, architecture, QA testing, DevOps, and cloud resource management. Our team of expert-level developers and designers will help you build the software that your company needs using modern languages and techniques created over years of experience overcoming roadblocks and finding the right solutions at the right time for our clients.
Project Roles. The roles of the Parties in conducting the Project shall be as follows:
AutoNDA by SimpleDocs
Project Roles. The roles of the Parties in conducting the Project shall be as follows: a. Both Parties shall ensure that the Project is coordinated and consistent with all local, regional, and state transportation plans. b. Each Party shall seek to reach consensus on key project issues prior to conducting their respective roles and responsibilities. c. FDOT will conduct the preliminary engineering and environmental analysis via a PD&E Study and coordinate with County on the operations planning for the commuter rail service, particularly as it affects Broward County Transit services, freight service, and intercity passenger rail; coordinate with private entities such as Grupo México Transportes/Florida East Coast Railroad (GMXT/FEC) and Brightline as necessary to complete the technical analysis; as well as coordinate with the FTA, U.S. Coast Guard (USCG), and other federal, state and local agencies as may be necessary. d. FDOT will be responsible for the meetings and public outreach required of the PD&E/NEPA process. The County, with FDOT technical support, will be responsible for all Stakeholder and MPO meetings as well as non-PD&E public outreach events. e. County will be responsible for all consensus-building activity with the Stakeholders, including GMXT/FEC, Brightline, and the municipalities within the County to support selection of the station locations.
Project Roles. [***] [***] Certain information in this document has been omitted and filed separately with the Securities and Exchange Commission. Confidential treatment has been requested with respect to the omitted portions. [***] PROPOSED PACKAGE INSERTINTENDED USE AND INDICATION FOR USE [***] TECHNOLOGY – PRINCIPLES OF THE PROCEDURE [***] [***] Certain information in this document has been omitted and filed separately with the Securities and Exchange Commission. Confidential treatment has been requested with respect to the omitted portions. [***] [***] Certain information in this document has been omitted and filed separately with the Securities and Exchange Commission. Confidential treatment has been requested with respect to the omitted portions. KIT CONFIGURATIONS [***] [***] Certain information in this document has been omitted and filed separately with the Securities and Exchange Commission. Confidential treatment has been requested with respect to the omitted portions. [***] HANDLING AND STORAGE [***] CLINICAL CHEMISTRY ANALYZER [***] DESIGN CHARACTERISTICS [***] [***] Certain information in this document has been omitted and filed separately with the Securities and Exchange Commission. Confidential treatment has been requested with respect to the omitted portions. [***] [***] Eight pages have been omitted and filed separately with the Securities and Exchange Commission. Confidential treatment has been requested with respect to the omitted portions. [***] REPORTING REQUIREMENTS [***] PROJECT TIMELINE [***] [***] Certain information in this document has been omitted and filed separately with the Securities and Exchange Commission. Confidential treatment has been requested with respect to the omitted portions. [***] IDE REGULATORY TIMELINE [***] MARKET CLEARANCE, TRIAL PERFORMANCE, AND REGULATORY TIMELINE [***] [***] Certain information in this document has been omitted and filed separately with the Securities and Exchange Commission. Confidential treatment has been requested with respect to the omitted portions. [***] TECHNICAL RISK MANAGEMENT [***] [***] Certain information in this document has been omitted and filed separately with the Securities and Exchange Commission. Confidential treatment has been requested with respect to the omitted portions. [***]
Project Roles. [With respect to a Project, User with certain administrative privilege may allocate specific accessibility of the Service to other Users (including Third-Party Users as permitted under Section 3.3) involved in such Project by designating roles to such other Users.]
Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!