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.
(2) The Supplier shall establish the security in accordance with Article 28 Paragraph 3 Point c, and Article 32 GDPR in particular in conjunction with Article 5 Paragraph 1, and Paragraph 2 GDPR. The measures to be taken are measures of data security and measures that guarantee a protection level appropriate to the risk concerning confidentiality, integrity, availability and resilience of the systems. The state of the art, implementation costs, the nature, scope and purposes of processing as well as the probability of occurrence and the severity of the risk to the rights and freedoms of natural persons within the meaning of Article 32 Paragraph 1 GDPR must be taken into account. [Details in Appendix 1]
(3) The Technical and Organisational Measures are subject to technical progress and further development. In this respect, it is permissible for the Supplier to implement alternative adequate measures. In so doing, the security level of the defined measures must not be reduced. Substantial changes must be documented.
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.
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. 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] ……………. Knowledge, skills and competences to be acquired by the end of the traineeship (expected Learning Outcomes): Address of the Receiving Organisation/Enterprise [street, city, country, phone, e-mail address], website:
Function of Joint Health and Safety Committee All incidents involving aggression or violence shall be brought to the attention of the Joint Health and Safety Committee. The Employer agrees that the Joint Health and Safety Committee shall concern itself with all matters relating to violence to staff.
Utilities and Appliances (1) The owner must provide all utilities needed to comply with the HQS.
(2) The owner is not responsible for a breach of the HQS caused by the tenant’s failure to:
(a) Pay for any utilities that are to be paid by the tenant.
(b) Provide and maintain any appliances that are to be provided by the tenant.
Foreign Terrorist Organizations Contractor represents and warrants that it is not engaged in business with Iran, Sudan, or a foreign terrorist organization, as prohibited by Section 2252.152 of the Texas Government Code.
Reactive Power and Primary Frequency Response 9.6.1 Power Factor Design Criteria
Disaster Services In the event of a local, state, or federal emergency, including natural, man-made, criminal, terrorist, and/or bioterrorism events, declared as a state disaster by the Governor, or a federal disaster declared by the appropriate federal official, Grantee may be called upon to assist the System Agency in providing the following services:
i. Community evacuation;
ii. Health and medical assistance;
iii. Assessment of health and medical needs;
iv. Health surveillance;
v. Medical care personnel;
vi. Health and medical equipment and supplies;
vii. Patient evacuation;
viii. In-hospital care and hospital facility status;
ix. Food, drug and medical device safety;
x. Worker health and safety;
xi. Mental health and substance abuse;
xii. Public health information;
xiii. Vector control and veterinary services; and
xiv. Victim identification and mortuary services.
Requester and Approved User Responsibilities The Requester agrees through the submission of the DAR that the PI named has reviewed and understands the principles for responsible research use and data management of the genomic datasets as defined in the NIH Security Best Practices for Controlled-Access Data Subject to the GDS Policy. The Requester and Approved Users further acknowledge that they are responsible for ensuring that all uses of the data are consistent with national, tribal, and state laws and regulations, as appropriate, as well as relevant institutional policies and procedures for managing sensitive genomic and phenotypic data. The Requester certifies that the PI is in good standing (i.e., no known sanctions) with the institution, relevant funding agencies, and regulatory agencies and is eligible to conduct independent research (i.e., is not a postdoctoral fellow, student, or trainee). The Requester and any Approved Users may use the dataset(s) only in accordance with the parameters described on the study page and in the 1 If contractor services are to be utilized, PI requesting the data must provide a brief description of the services that the contractor will perform for the PI (e.g., data cleaning services) in the research use statement of the DAR. Additionally, the Key Personnel section of the DAR must include the name of the contractor’s employee(s) who will conduct the work. These requirements apply whether the contractor carries out the work at the PI’s facility or at the contractor’s facility. In addition, the PI is expected to include in any contract agreement requirements to ensure that any of the contractor’s employees who have access to the data adhere to the NIH GDS Policy, this Data Use Certification Agreement, and the NIH Security Best Practices for Controlled-Access Data Subject to the GDS Policy. Note that any scientific collaborators, including contractors, who are not at the Requester must submit their own DAR. Addendum to this Agreement for the appropriate research use, as well as any limitations on such use, of the dataset(s), as described in the DAR, and as required by law. Through the submission of this DAR, the Requester and Approved Users acknowledge receiving and reviewing a copy of the Addendum which includes Data Use Limitation(s) for each dataset requested. The Requester and Approved Users agree to comply with the terms listed in the Addendum. Through submission of the DAR, the PI and Requester agree to submit a Project Renewal or Project Close-out prior to the expiration date of the one (1) year data access period. The PI also agrees to submit an annual Progress Update prior to the one (1) year anniversary2 of the project, as described under Research Use Reporting (Term 10) below. By approving and submitting the attached DAR, the Institutional Signing Official provides assurance that relevant institutional policies and applicable local, state, tribal, and federal laws and regulations, as applicable, have been followed, including IRB approval, if required. Approved Users may be required to have IRB approval if they have access to personal identifying information for research participants in the original study at their institution, or through their collaborators. The Institutional Signing Official also assures, through the approval of the DAR, that other institutional departments with relevant authorities (e.g., those overseeing human subjects research, information technology, technology transfer) have reviewed the relevant sections of the NIH GDS Policy and the associated procedures and are in agreement with the principles defined. The Requester acknowledges that controlled-access datasets subject to the NIH GDS Policy may be updated to exclude or include additional information. Unless otherwise indicated, all statements herein are presumed to be true and applicable to the access and use of all versions of these datasets.
Existing utilities and roads Notwithstanding anything to the contrary contained herein, it shall be the responsibility of the Contractor to ensure that the respective entities owning the existing roads, right of way, level crossings, structures, or utilities on, under or above the Site are enabled by it to keep them in continuous satisfactory use, if necessary, by providing suitable temporary diversions with the authority of the controlling body of that road, right of way or utility.
