Research Use Reporting To assure adherence to NIH GDS Policy, the PI agrees to provide annual Progress Updates as part of the annual Project Renewal or Project Close-out processes, prior to the expiration of the one (1) year data access period. The PI who is seeking Renewal or Close-out of a project agree to complete the appropriate online forms and provide specific information such as how the data have been used, including publications or presentations that resulted from the use of the requested dataset(s), a summary of any plans for future research use (if the PI is seeking renewal), any violations of the terms of access described within this Agreement and the implemented remediation, and information on any downstream intellectual property generated from the data. The PI also may include general comments regarding suggestions for improving the data access process in general. Information provided in the progress updates helps NIH evaluate program activities and may be considered by the NIH GDS governance committees as part of NIH’s effort to provide ongoing stewardship of data sharing activities subject to the NIH GDS Policy.
Drug Testing Procedures a. The testing procedures and safeguards provided in this policy shall be adhered to by any laboratory personnel administering departmental drug tests.
Technical Specification As enumerated in Special Conditions of Contract/Scope of Work/attached Drawing/ Details/Schedule of Rates.
Technical Specifications The Technical Specifications furnished on the CD are intended to establish the standards for quality, performance and technical requirements for all labor, workmanship, material, methods and equipment necessary to complete the Work. When specifications and drawings are provided or referenced by the County, these are to be considered part of the Scope of Work, and to be specifically documented in the Detailed Scope of Work. For convenience, the County supplied specifications, if any, and the Technical Specifications furnished on the CD.
AML/KYC Procedures “AML/KYC Procedures” means the customer due diligence (CDD) procedures of a Reporting Financial Institution pursuant to the anti-money laundering or similar requirements of the jurisdiction concerned to which such Reporting Financial Institution is subject.
NEGOTIATING PROCEDURES 4.01 A request for professional negotiations shall be submitted in writing by the SHTA to the Board or its designated representative or by the Board’s designated representative to SHTA before April 1 of the year (approximately 90 calendar days) of the expiration of the existing Agreement. A copy of the notice shall be filed with the State Employment Relations Board. A mutually convenient meeting shall be held by April 15th in which both parties shall exchange negotiation packages which shall include additions to, deletions from or revisions of the existing agreement. No new items shall be introduced for negotiations during said negotiations except what may be mutually agreed upon by both negotiation teams.
Induction Procedures a) The parties to this Agreement acknowledge that it is in the interests of the industry that all new employees and employers on a building project understand their obligations to this Agreement and are introduced to their jobs in a manner which will help them work safely and efficiently.
Conformity Assessment Procedures 1. Each Party shall give positive consideration to accepting the results of conformity assessment procedures of other Parties, even where those procedures differ from its own, provided it is satisfied that those procedures offer an assurance of conformity with applicable technical regulations or standards equivalent to its own procedures.
NEGOTIATIONS PROCEDURES Section 1. Negotiations shall commence pursuant to Article 4 of this Agreement and the Parties will structure their Agreement per the four (4) Agency groups set forth below: HUMAN SERVICES: Department of Human Services-Oregon Health Authority, Employment Department; INSTITUTIONS: Oregon Youth Authority (Youth Correctional Facilities), Oregon Health Authority Institutions: Oregon State Hospital (OSH), Pendleton State-Delivered Secure Residential Treatment Facility (Pendleton Cottage), OYA Administration and Field Services; ODOT: Oregon Department of Transportation (ODOT), Forestry, Oregon Parks and Recreation Department (OPRD), Oregon Department of Aviation (ODOA), Oregon Department of Fish & Wildlife (ODFW), Department of Geology and Mineral Industries (DOGAMI), Department of Agriculture, Water Resources Department, Oregon Watershed Enhancement Board; SPECIAL AGENCIES: Justice, Revenue, Higher Education Coordinating Commission, Workers’ Compensation Board, Department of Consumer & Business Services (DCBS), Bureau of Labor and Industries (BOLI), Veterans’ Affairs, Board of Nursing, Oregon Medical Board, Board of Dentistry, Board of Pharmacy, Mortuary and Cemetery Board, Oregon Mental Health Regulatory Agency, Board of Medical Imaging, Board of Massage Therapists, Occupational Therapy Licensing Board, Board of Examiners for Speech Pathology & Audiology, Board of Naturopathic Medicine, Education, Library, Treasury, Commission for the Blind, Public Employees Retirement System (PERS), Special Schools, State Scholarship, Department of Administrative Services, Oregon Housing & Community Services (OHCS), Oregon State Board of Examiners for Engineering and Land Surveying (OSBEELS), and Teachers Standards and Practices Commission.
Escrow Format Specification 3.1. Deposit’s Format. Registry objects, such as domains, contacts, name servers, registrars, etc. will be compiled into a file constructed as described in draft-xxxxx-xxxxxxx-registry-data-escrow, see Part A, Section 9, reference 1 of this Specification and draft-xxxxx-xxxxxxx-dnrd-objects-mapping, see Part A, Section 9, reference 2 of this Specification (collectively, the “DNDE Specification”). The DNDE Specification describes some elements as optional; Registry Operator will include those elements in the Deposits if they are available. If not already an RFC, Registry Operator will use the most recent draft version of the DNDE Specification available at the Effective Date. Registry Operator may at its election use newer versions of the DNDE Specification after the Effective Date. Once the DNDE Specification is published as an RFC, Registry Operator will implement that version of the DNDE Specification, no later than one hundred eighty (180) calendar days after. UTF-8 character encoding will be used.