Technical Board Sample Clauses

Technical Board. A committee that oversees the development of the XXXXX software shall be set up.
Sample 1Sample 2Sample 3See All (5)
AutoNDA by SimpleDocs
Technical Board. The Technical Board shall be established by the Customer for the purposes of this Call Off Contract on which the Supplier and the Customer shall be represented. The Technical Board members, frequency and location of board meetings and planned start date by which the board shall be established shall be set out in Annex 2 to this Schedule. In the event that either Party wishes to replace any of its appointed board members, that party shall notify the other in writing of the proposed change for agreement by the other Party (such agreement not to be unreasonably withheld or delayed). Notwithstanding the foregoing it is intended that each Customer board member has at all times a counterpart Supplier board member of equivalent seniority and expertise. Each Party shall ensure that its board members shall make all reasonable efforts to attend board meetings at which that board member’s attendance is required. If any board member is not able to attend a board meeting, that person shall use all reasonable endeavours to ensure that a delegate attends the Technical Board meeting in his/her place (wherever possible) is properly briefed and prepared and that he/she is debriefed by such delegate after the board meeting. The Technical Board shall be accountable to the Project Managers for oversight of the technology used by the Supplier and ensuring that technological choices are made to maximise the long term value of the Services. The Technical Board shall: assure compliance with the overall technical architecture of the Customer and with Government IT Strategy (as defined at xxxxx://xxx.xxx.xx/government/uploads/system/uploads/attachment_data/file/85968/uk-government-government-ict-strategy_0.pdf); grant dispensations for variations from such compliance where appropriate; assure the coherence and consistency of the systems architecture for the provision of the Services; monitor developments in new technology and reporting on their potential benefit to the provision of the Services; provide advice, guidance and information on technical issues; and assure that the technical architecture for the provision of the Services is aligned to the requirements specified in Call Off Schedule 2 (Goods and Services) and has sufficient flexibility to cope with future requirements of the Customer.] 12/08/2013 GUIDANCE NOTE: PLEASE POPULATE BELOW DETAILS OF THE TECHNICAL BOARD, MEMBERS, FREQUENCY AND LOCATION OF BOARD MEETINGS AND PLANNED START DATE. CALL OFF SCHEDULE 7: STANDARDS [G...
Sample 1Sample 2See All (5)
Technical Board. The Technical Board shall be established by the Customer for the purposes of this Lease Agreement on which the Supplier and the Customer shall be represented.
Sample 1
Technical Board. 16 3.3.1 Composition and responsibilities of the Technical Board 16 3.3.2 Decision making in the Technical Board 18 3.4.1 General responsibilities 19 3.4.2 Responsibilities towards the Co-ordinator, the Technical Board and the Project Board 20 3.4.3 Responsibilities towards each other 20 4.1 Intellectual Property Rights 21
Sample 1
Technical Board. The Technical Board (TB) manages the numerous technological activities encompassed by the develo3pment and implementation of the Project’s Activity Areas, in particular with regard to: • The timely delivery to the PMB and the Coordinator of: o Reports about the activities and results of the project activities; o Communication of delay in the performance of a project activity; o Communication, analysis, and documentation of breach of responsibilities of any partner and a proposal of remedies; o The proposals for the admission of new partners to the Grant Agreement and to the Consortium Agreement; o Proposal of changes to the Annex I of the Grant Agreement; • The formulation and approval of: o An implementation plan for the project activities for the future period; o Tasks and related budgets exchange between the partners in an Activity Area when such exchange has no impact beyond the scope of the Activity Area and its budget. The TB is chaired by the Technical Director for the duration of the project and includes the gCube Software, VRE Development, and Infrastructure Managers; Work Package Leaders; and one representative for each of the interfaced e-Infrastructures (i.e. GENESI-DR, DRIVER, INSPIRE, and AquaMaps). The TB will meet in person four times per year, with telephone conferences held every two weeks if deemed necessary by the TD. Electronic voting outside the quarterly meeting of the TB is authorised.
Sample 1
Technical Board. The body taking day-to-day technical decisions, for the execution of activities described in GA - Annex 1
Sample 1
Technical Board 
Sample 1Sample 2
AutoNDA by SimpleDocs

Related to Technical Board

  • Technical Committee 1. The Technical Committee shall comprise: (a) nine experts representing different regions of the Agreement Area, in accordance with a balanced geographical distribution; (b) one representative from the International Union for Conservation of Nature and Natural Resources (IUCN), one from the International Waterfowl and Wetlands Research Bureau (IWRB) and one from the International Council for Game and Wildlife Conservation (CIC); and (c) one expert from each of the following fields: rural economics, game management, and environmental law. The procedure for the appointment of the experts, the term of their appointment and the procedure for designation of the Chairman of the Technical Committee shall be determined by the Meeting of the Parties. The Chairman may admit a maximum of four observers from specialized international inter- governmental and non-governmental organizations. 2. Unless the Meeting of the Parties decides otherwise, meetings of the Technical Committee shall be convened by the Agreement secretariat in conjunction with each ordinary session of the Meeting of the Parties and at least once between ordinary sessions of the Meeting of the Parties. 3. The Technical Committee shall: (a) provide scientific and technical advice and information to the Meeting of the Parties and, through the Agreement secretariat, to Parties; (b) make recommendations to the Meeting of the Parties concerning the Action Plan, implementation of the Agreement and further research to be carried out; (c) prepare for each ordinary session of the Meeting of the Parties a report on its activities, which shall be submitted to the Agreement secretariat not less than one hundred and twenty days before the session of the Meeting of the Parties, and copies shall be circulated forthwith by the Agreement secretariat to the Parties; and (d) carry out any other tasks referred to it by the Meeting of the Parties. 4. Where in the opinion of the Technical Committee there has arisen an emergency which requires the adoption of immediate measures to avoid deterioration of the conservation status of one or more migratory waterbird species, the Technical Committee may request the Agreement secretariat to convene urgently a meeting of the Parties concerned. These Parties shall meet as soon as possible thereafter to establish rapidly a mechanism to give protection to the species identified as being subject to particularly adverse threat. Where a recommendation has been adopted at such a meeting, the Parties concerned shall inform each other and the Agreement secretariat of measures they have taken to implement it, or of the reasons why the recommendation could not be implemented. 5. The Technical Committee may establish such working groups as may be necessary to deal with specific tasks.

  • Technical Advisory Committee (TAC The goal of this subtask is to create an advisory committee for this Agreement. The TAC should be composed of diverse professionals. The composition will vary depending on interest, availability, and need. TAC members will serve at the CAM’s discretion. The purpose of the TAC is to: • Provide guidance in project direction. The guidance may include scope and methodologies, timing, and coordination with other projects. The guidance may be based on: o Technical area expertise; o Knowledge of market applications; or o Linkages between the agreement work and other past, present, or future projects (both public and private sectors) that TAC members are aware of in a particular area. • Review products and provide recommendations for needed product adjustments, refinements, or enhancements. • Evaluate the tangible benefits of the project to the state of California, and provide recommendations as needed to enhance the benefits. • Provide recommendations regarding information dissemination, market pathways, or commercialization strategies relevant to the project products. The TAC may be composed of qualified professionals spanning the following types of disciplines: • Researchers knowledgeable about the project subject matter; • Members of trades that will apply the results of the project (e.g., designers, engineers, architects, contractors, and trade representatives); • Public interest market transformation implementers; • Product developers relevant to the project; • U.S. Department of Energy research managers, or experts from other federal or state agencies relevant to the project; • Public interest environmental groups; • Utility representatives; • Air district staff; and • Members of relevant technical society committees. • Prepare a List of Potential TAC Members that includes the names, companies, physical and electronic addresses, and phone numbers of potential members. The list will be discussed at the Kick-off meeting, and a schedule for recruiting members and holding the first TAC meeting will be developed. • Recruit TAC members. Ensure that each individual understands member obligations and the TAC meeting schedule developed in subtask 1.11. • Prepare a List of TAC Members once all TAC members have committed to serving on the TAC. • Submit Documentation of TAC Member Commitment (such as Letters of Acceptance) from each TAC member. • List of Potential TAC Members • List of TAC Members • Documentation of TAC Member Commitment

  • Training Committee The parties to this Agreement may form a Training Committee. The Training Committee will be constituted by equal numbers of Employer nominees and ETU employee representatives and have a charter which clearly states its role and responsibilities. It shall monitor the clauses of this Agreement which relate to training and ensure all employees have equal access to training.

  • Technical Proposal The technical proposal may be presented in free format. It shall not exceed ten pages, not counting the CVs. It shall respect the following page limit and structure: • Technical methodology (max. 7 pages) • Quality management (max. 1 page) • Project management (max. 1 page) • Resource management (proposal (max. 1 page) + CVs of experts)

  • Management Board The Management Board is responsible for the overall strategic direction of the Integrated Service. Its functions and terms of references are set out in Schedule 3 Part I to this Agreement.

  • MINISTRY/SCHOOL BOARD INITIATIVES ETFO will be an active participant in the consultation process to develop a Ministry of Education PPM regarding Ministry/School Board Initiatives.

  • Technical Consultations If a Party has a significant concern with respect to food safety, plant health, or animal health, or an SPS measure that the other Party has proposed or implemented, that Party may request technical consultations with the other Party. The Party that is the subject of the request should respond to the request without undue delay. Each Party shall endeavour to provide the information necessary to avoid a disruption to trade and, as the case may be, to reach a mutually acceptable solution.

  • TRANSITION COMMITTEE A transition committee comprised of the employee representatives and the employer representatives, including the Crown, will be established by January 31, 2016 to address all matters that may arise in the creation of the Trust.

  • School Board Any reference to School Board or District in this Agreement shall mean the District and/or its designated officials.

  • Joint Consultation Committee 8.01 On the request of either party, the parties must meet at least once every four (4) months, for the purpose of discussing issues relating to the workplace that affect the parties or any employee bound by the Agreement. 8.02 The purpose of the consultation committee is to promote the cooperative resolution of workplace issues, to xxxxxx the development of work related skills and to promote workplace productivity, and to identify opportunities for improved patient care. 8.03 Up to two (2) employees who are members of the joint consultation committee shall be granted leave without loss of pay or receive straight-time regular wages while attending meetings of the committee, up to a maximum of two (2) hours’ pay. 8.04 Pay for such meetings will be limited to two (2) hours and employees attending such meetings will not receive overtime wages.

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