Developer Responsbilities
Developer Responsbilities Sample Clauses
Related to Developer Responsbilities
Engineer Responsibilities No subcontract relieves the Engineer of any responsibilities under this contract.
User Responsibilities i. Users are required to follow good security practices in the selection and use of passwords; ii. Users shall ensure that unattended equipment is protected; and iii. Users shall adopt a clear desk policy for papers and removable storage media and a clear screen policy for information processing facilities.
Owner Responsibilities The project owner or the engineer or architect of record acting as the owner’s agent shall fund special inspection services.
Customer Responsibilities Notwithstanding the above, Customer agrees that except as provided by this DPA, Customer is responsible for its secure use of the Services, including securing its account authentication credentials, protecting the security of Customer Data when in transit to and from the Services and taking any appropriate steps to securely encrypt or backup any Customer Data uploaded to the Services.
Member Responsibilities The Member’s responsibilities shall include, but are not limited to: 3.17.1. Inform the CONTRACTOR of the loss or theft of ID cards, 3.17.2. Present ID cards when using health care services, 3.17.3. Be familiar with the CONTRACTOR’s Health Plan Procedures to the best of their abilities, 3.17.4. Call or contact the CONTRACTOR to obtain information and have questions clarified, 3.17.5. Provide participating network Providers with accurate and complete medical information, 3.17.6. Follow the prescribed course of care recommended by the Provider or let the Provider know the reasons the treatment cannot be followed, as soon as possible, And 3.17.7. Make every effort to keep a scheduled appointment or cancel an appointment in advance of when it is scheduled.
Employer Responsibilities Recognizing the inherent risk(s) in a correctional setting, the Employer is obligated to provide a safe workplace and to educate employees on proper safety procedures and use of protective and safety equipment. The Employer is committed to responding to legitimate safety concerns raised by the Union and employees. The Employer will comply with federal and state safety standards, including requirements relating to first aid training, first aid equipment and the use of protective devices and equipment.
Provider Responsibilities The Private Child-Caring Facility (PCC) (a.k.a., Provider) must comply with the following requirements:
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.
ARCHITECT’S RESPONSIBILITIES § 2.1 The Architect shall provide professional services as set forth in this Agreement. The Architect represents that it is properly licensed in the jurisdiction where the Project is located to provide the services required by this Agreement, or shall cause such services to be performed by appropriately licensed design professionals. § 2.2 The Architect shall perform its services consistent with the professional skill and care ordinarily provided by architects practicing in the same or similar locality under the same or similar circumstances. The Architect shall perform its services as expeditiously as is consistent with such professional skill and care and the orderly progress of the Project. § 2.3 The Architect shall identify a representative authorized to act on behalf of the Architect with respect to the Project. § 2.4 Except with the Owner’s knowledge and consent, the Architect shall not engage in any activity, or accept any employment, interest or contribution that would reasonably appear to compromise the Architect’s professional judgment with respect to this Project. § 2.5 The Architect shall maintain the following insurance until termination of this Agreement. If any of the requirements set forth below are in addition to the types and limits the Architect normally maintains, the Owner shall pay the Architect as set forth in Section 11.9. § 2.5.1 Commercial General Liability with policy limits of not less than « » ($ « » ) for each occurrence and « » ($ « » ) in the aggregate for bodily injury and property damage. § 2.5.2 Automobile Liability covering vehicles owned, and non-owned vehicles used, by the Architect with policy limits of not less than « » ($ « » ) per accident for bodily injury, death of any person, and property damage arising out of the ownership, maintenance and use of those motor vehicles, along with any other statutorily required automobile coverage. § 2.5.3 The Architect may achieve the required limits and coverage for Commercial General Liability and Automobile Liability through a combination of primary and excess or umbrella liability insurance, provided such primary and excess or umbrella liability insurance policies result in the same or greater coverage as the coverages
Vendor Responsibilities Note: NO EXCEPTIONS OR REVISIONS WILL BE CONSIDERED IN C-M, O-S, V-W. Indemnification
