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 (Services) and has sufficient flexibility to cope with future requirements of the Customer.] 12/08/2013 ANNEX 2 TO PART B: TECHNICAL BOARD GUIDANCE NOTE: PLEASE POPULATE BELOW DETAILS OF THE TECHNICAL BOARD, MEMBERS, FREQUENCY AND LOCATION OF BOARD MEETINGS AND PLANNED START DATE. CALL O...
Technical Board. A committee that oversees the development of the XXXXX software shall be set up.
Technical Board. 2.1 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.
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.
Technical Board. The body taking day-to-day technical decisions, for the execution of activities described in GA - Annex 1 • Composed by WP leaders (including XXXX Meta-WP) • Chaired by Technical Manager • Ensures smooth overall progress and synchronization • Expected to meet “rather often” • Coordinate WPs (e.g., towards Milestones and Deliverables) • Lean and effective structure • Any act of the TB is public (e.g., minute meetings) Other relevant stuff in the CA (1/2) • Associated Partner • Inserted in CA, so as to avoid additional document • Specific provisions are included for AP (obligations, responsibilities) to make it in line with other members (bound by signature of GA) • GA is an attachment to CA, so that AP can be made aware of provisions therein Other relevant stuff in the CA (2/2) • Payments: • Constraints: • Coordinator is obliged by GA to “monitor” project execution • Technical (dealt within TB) and financial dimensions • Excess payment: if no refund within 30 days, Partner is in “substantial breach” of CA • Admin processes can be lengthy • Procedures should not affect spending capacity • At any given time each Partner should have enough money in the pocket (but... Partners need to be aware they won’t ever receive > ~85% budget during project lifetime) • How we tackle: try and avoid occurrence of over-payments via non-automatic payments and internal monitoring • Pre-financing distributed in full, according to project initial budget • Other payments distributed as soon as internal reporting shows Partner used >75% of what already received so far Thanks for your attention!
Technical Board
