Standard Development Organisations (SDO) (secondary stakeholders Sample Clauses

Standard Development Organisations (SDO) (secondary stakeholders. Standard development organisations have the authority to endorse official standards for given applications. XXXXXXXXXXXX.xx aims at spreading the carbon footprint methodologies to these actors in order to xxxxxx the development of targeted application standards and getting feedback from practitioners, while continuously fostering at the same time the interest towards XXXXXXXXXXXX.xx’s primary outcomes. Overall Description ICT Intensive SMEs are the main end-users of XXXXXXXXXXXX.xx’s outcomes: the project main objective is to increase the adoption of carbon footprint calculation methodologies in the ICT sector, as well as fostering energy efficiency solutions and their application onto organisational processes in Europe. At the same time, the project wants to promote and to showcase these “green” solutions on the web platform, acting as the point of convergence for buyers (ICT intensive SMEs) and sellers (ICT solutions Providers). For this reason, ICT intensive SMEs and ICT suppliers are selected as primary stakeholders. Public Administrators, as well as Standard Development Organisations, have an important role, as secondary stakeholders, for the dissemination and the fostering of methodologies’ adoptions in the business sector. Two are the reasons their importance: public administrators, if actively engaged with XXXXXXXXXXXX.xx as the project wants to do, will act as local promoters of the carbon footprint calculation methodologies, spreading externally the project’s values within their region and, internally, stimulating the policy regulations to take into account energy efficiency solutions that XXXXXXXXXXXX.xx is supporting. Finally, XXXXXXXXXXXX.xx wants to engage with Standard development organisations in order to xxxxxx an active debate on carbon footprint standards and to encourage the collaboration between this D3.1 Stakeholders Engagement Plan Dissemination Level (PU) type of organisations and XXXXXXXXXXXX.xx. The European citizens are listed as “other stakeholders” because they may be indirectly interested in the outcomes and purposes of XXXXXXXXXXXX.xx in two ways: as direct end-users of “green” initiatives or simply as people interested in their local and European environment. Each stakeholder and the motivation standing under the definition of primary or secondary are specifically described in the following sections, regarding each cluster. Primary stakeholders are the main target users of the XXXXXXXXXXXX.xx’s online platform and a consiste...
AutoNDA by SimpleDocs

Related to Standard Development Organisations (SDO) (secondary stakeholders

  • Technical and Organisational Measures (1) Before the commencement of processing, the Supplier shall document the execution of the necessary Technical and Organisational Measures, set out in advance of the awarding of the Order or Contract, specifically with regard to the detailed execution of the contract, and shall present these documented measures to the Client for inspection. Upon acceptance by the Client, the documented measures become the foundation of the contract. Insofar as the inspection/audit by the Client shows the need for amendments, such amendments shall be implemented by mutual agreement.

  • Recruitment Through Jobcentre Plus 5.1 One of the key objectives of the Department for Work and Pensions is to move people from welfare into work. DWP has a Great Britain-wide network of Jobcentre Plus offices that provide job broking services for unemployed people. The Contractor is therefore required to notify Jobcentre Plus when recruiting staff for any entry-level job vacancies located within Great Britain, which may arise from the delivery of their contract to the Authority.

  • Table C - Receiving Organisation Enterprise The Receiving Organisation/Enterprise will provide financial support to the trainee for the traineeship: Yes ☐ No ☐ If yes, amount (EUR/month): ……….. The Receiving Organisation/Enterprise will provide a contribution in kind to the trainee for the traineeship: Yes ☐ No ☐ If yes, please specify: …. The Receiving Organisation/Enterprise will provide an accident insurance to the trainee (if not provided by the Sending Institution): Yes ☐ No ☐ The accident insurance covers: - accidents during travels made for work purposes: Yes ☐ No ☐ - accidents on the way to work and back from work: Yes ☐ No ☐ The Receiving Organisation/Enterprise will provide a liability insurance to the trainee (if not provided by the Sending Institution): Yes ☐ No ☐ The Receiving Organisation/Enterprise will provide appropriate support and equipment to the trainee. Upon completion of the traineeship, the Organisation/Enterprise undertakes to issue a Traineeship Certificate within 5 weeks after the end of the traineeship. By signing this document, the trainee, the Sending Institution and the Receiving Organisation/Enterprise confirm that they approve the Learning Agreement and that they will comply with all the arrangements agreed by all parties. The trainee and Receiving Organisation/Enterprise will communicate to the Sending Institution any problem or changes regarding the traineeship period. The Sending Institution and the trainee should also commit to what is set out in the Erasmus+ grant agreement. The institution undertakes to respect all the principles of the Erasmus Charter for Higher Education relating to traineeships. Commitment Name Email Position Date Signature Trainee Trainee Responsible person12 at the Sending Institution Supervisor13 at the Receiving Organisation During the Mobility Table A2 - Exceptional Changes to the Traineeship Programme at the Receiving Organisation/Enterprise (to be approved by e-mail or signature by the student, the responsible person in the Sending Institution and the responsible person in the Receiving Organisation/Enterprise) Planned period of the mobility: from [month/year] ……………. till [month/year] ……………. Traineeship title: … Number of working hours per week: … Detailed programme of the traineeship period: Knowledge, skills and competences to be acquired by the end of the traineeship (expected Learning Outcomes): Monitoring plan: Evaluation plan: After the Mobility Table D - Traineeship Certificate by the Receiving Organisation/Enterprise Name of the trainee: Name of the Receiving Organisation/Enterprise: Sector of the Receiving Organisation/Enterprise: Address of the Receiving Organisation/Enterprise [street, city, country, phone, e-mail address], website: Start date and end date of traineeship: from [day/month/year] …………………. to [day/month/year] ……………….. Traineeship title: Detailed programme of the traineeship period including tasks carried out by the trainee: Knowledge, skills (intellectual and practical) and competences acquired (achieved Learning Outcomes): Evaluation of the trainee: Date: Name and signature of the Supervisor at the Receiving Organisation/Enterprise:

  • Framework Management Structure 2.1.1 The Supplier shall provide a suitably qualified nominated contact (the “Supplier Framework Manager”) who will take overall responsibility for delivering the Goods and/or Services required within this Framework Agreement, as well as a suitably qualified deputy to act in their absence.

  • Red Hat Enterprise Linux Developer Suite Red Hat Enterprise Linux Developer Suite provides an open source development environment that consists of Red Hat Enterprise Linux with built-in development tools, certain Red Hat Enterprise Linux Add-Ons, Red Hat Enterprise Linux for Real Time, Smart Management and access to Software Maintenance, but no Development or Production Support. If you use any of the Subscription Services or Software associated with Red Hat Enterprise Linux Developer Suite for Production Purposes, or use the Red Hat Enterprise Linux Software Subscription entitlement independently, you agree to purchase the applicable number of Units of the applicable Software Subscription. Red Hat does not provide Production Support or Development Support for Red Hat Enterprise Developer Suite.

  • Technical and Organizational Measures The following sections define SAP’s current technical and organizational measures. SAP may change these at any time without notice so long as it maintains a comparable or better level of security. Individual measures may be replaced by new measures that serve the same purpose without diminishing the security level protecting Personal Data.

  • Appropriate Technical and Organizational Measures SAP has implemented and will apply the technical and organizational measures set forth in Appendix 2. Customer has reviewed such measures and agrees that as to the Cloud Service selected by Customer in the Order Form the measures are appropriate taking into account the state of the art, the costs of implementation, nature, scope, context and purposes of the processing of Personal Data.

  • Vlastnictví Zdravotnické zařízení si ponechá a bude uchovávat Zdravotní záznamy. Zdravotnické zařízení a Zkoušející převedou na Zadavatele veškerá svá práva, nároky a tituly, včetně práv duševního vlastnictví k Důvěrným informacím (ve smyslu níže uvedeném) a k jakýmkoli jiným Studijním datům a údajům.

  • New Teacher Orientation The Association shall have the opportunity to participate in the opening in-service day including speakers for the sole purpose of greeting new faculty members and informing them of the opportunities available to them through joining their professional association.

  • International Olympic Committee; International Red Cross and Red Crescent Movement As instructed from time to time by ICANN, the names (including their IDN variants, where applicable) relating to the International Olympic Committee, International Red Cross and Red Crescent Movement listed at xxxx://xxx.xxxxx.xxx/en/resources/registries/reserved shall be withheld from registration or allocated to Registry Operator at the second level within the TLD. Additional International Olympic Committee, International Red Cross and Red Crescent Movement names (including their IDN variants) may be added to the list upon ten (10) calendar days notice from ICANN to Registry Operator. Such names may not be activated in the DNS, and may not be released for registration to any person or entity other than Registry Operator. Upon conclusion of Registry Operator’s designation as operator of the registry for the TLD, all such names withheld from registration or allocated to Registry Operator shall be transferred as specified by ICANN. Registry Operator may self-­‐allocate and renew such names without use of an ICANN accredited registrar, which will not be considered Transactions for purposes of Section 6.1 of the Agreement.

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