Reasonable Suspicion Testing All Employees Performing Safety-Sensitive Functions
A. Reasonable suspicion testing for alcohol or controlled substances may be directed by the Employer for any employee performing safety-sensitive functions when there is reason to suspect that alcohol or controlled substance use may be adversely affecting the employee’s job performance or that the employee may present a danger to the physical safety of the employee or another.
B. Specific objective grounds must be stated in writing that support the reasonable suspicion. Examples of specific objective grounds include but are not limited to:
1. Physical symptoms consistent with alcohol and/or controlled substance use;
2. Evidence or observation of alcohol or controlled substance use, possession, sale, or delivery; or
3. The occurrence of an accident(s) where a trained manager, supervisor or lead worker suspects alcohol or other controlled substance use may have been a factor.
Audit and Inspection of Plants, Places of Business and Records (a) The State and its agents, including, but not limited to, the Connecticut Auditors of Public Accounts, Attorney General and State’s Attorney and their respective agents, may, at reasonable hours, inspect and examine all of the parts of the Contractor’s and Contractor Parties’ plants and places of business which, in any way, are related to, or involved in, the performance of this Contract.
(b) The Contractor shall maintain, and shall require each of the Contractor Parties to maintain, accurate and complete Records. The Contractor shall make all of its and the Contractor Parties’ Records available at all reasonable hours for audit and inspection by the State and its agents.
(c) The State shall make all requests for any audit or inspection in writing and shall provide the Contractor with at least twenty-four (24) hours’ notice prior to the requested audit and inspection date. If the State suspects fraud or other abuse, or in the event of an emergency, the State is not obligated to provide any prior notice.
(d) The Contractor will pay for all costs and expenses of any audit or inspection which reveals information that, in the sole determination of the State, is sufficient to constitute a breach by the Contractor under this Contract. The Contractor will remit full payment to the State for such audit or inspection no later than 30 days after receiving an invoice from the State. If the State does not receive payment within such time, the State may setoff the amount from any moneys which the State would otherwise be obligated to pay the Contractor in accordance with this Contract's Setoff provision.
(e) The Contractor shall keep and preserve or cause to be kept and preserved all of its and Contractor Parties’ Records until three (3) years after the latter of (i) final payment under this Contract, or (ii) the expiration or earlier termination of this Contract, as the same may be modified for any reason. The State may request an audit or inspection at any time during this period. If any Claim or audit is started before the expiration of this period, the Contractor shall retain or cause to be retained all Records until all Claims or audit findings have been resolved.
(f) The Contractor shall cooperate fully with the State and its agents in connection with an audit or inspection. Following any audit or inspection, the State may conduct and the Contractor shall cooperate with an exit conference.
(g) The Contractor shall incorporate this entire Section verbatim into any contract or other agreement that it enters into with any Contractor Party.
FLORIDA CONVICTED/SUSPENDED/DISCRIMINATORY COMPLAINTS By submission of an offer, the respondent affirms that it is not currently listed in the Florida Department of Management Services Convicted/Suspended/Discriminatory Complaint Vendor List.
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.
Technical Feasibility of String While ICANN has encouraged and will continue to encourage universal acceptance of all top-‐level domain strings across the Internet, certain top-‐level domain strings may encounter difficulty in acceptance by ISPs and webhosters and/or validation by web applications. Registry Operator shall be responsible for ensuring to its satisfaction the technical feasibility of the TLD string prior to entering into this Agreement.
Location of Improvements; No Encroachments All improvements which were considered in determining the Appraised Value of the Mortgaged Property lay wholly within the boundaries and building restriction lines of the Mortgaged Property, and no improvements on adjoining properties encroach upon the Mortgaged Property. No improvement located on or being part of the Mortgaged Property is in violation of any applicable zoning law or regulation;
Effect and invariability of the Clauses These Clauses set out appropriate safeguards, including enforceable data subject rights and effective legal remedies, pursuant to Article 46(1) and Article 46(2)(c) of Regulation (EU) 2016/679 and, with respect to data transfers from controllers to processors and/or processors to processors, standard contractual clauses pursuant to Article 28(7) of Regulation (EU) 2016/679, provided they are not modified, except to select the appropriate Module(s) or to add or update information in the Appendix. This does not prevent the Parties from including the standard contractual clauses laid down in these Clauses in a wider contract and/or to add other clauses or additional safeguards, provided that they do not contradict, directly or indirectly, these Clauses or prejudice the fundamental rights or freedoms of data subjects.
Accounts Not Required to Be Reviewed, Identified, or Reported Unless the Reporting Finnish Financial Institution elects otherwise, either with respect to all Preexisting Individual Accounts or, separately, with respect to any clearly identified group of such accounts, where the implementing rules in Finland provide for such an election, the following Preexisting Individual Accounts are not required to be reviewed, identified, or reported as U.S.
Conformity of production 8.1. Procedures concerning conformity of production shall comply with those set out in the 1958 Agreement, Schedule 1 (E/ECE/TRANS/505/Rev.3) and meet the following requirements:
8.2. A vehicle approved pursuant to this Regulation shall be so manufactured as to conform to the type approved by meeting the requirements of paragraph 5. above;
8.3. The Type Approval Authority which has granted approval may at any time verify the conformity of control methods applicable to each production unit. The normal frequency of such inspections shall be once every two years.
FORMAT AND CONTENT FOR REGISTRY OPERATOR MONTHLY REPORTING Registry Operator shall provide one set of monthly reports per gTLD, using the API described in draft-‐xxxxxx-‐icann-‐registry-‐interfaces, see Specification 2, Part A, Section 9, reference 5, with the following content. ICANN may request in the future that the reports be delivered by other means and using other formats. ICANN will use reasonable commercial efforts to preserve the confidentiality of the information reported until three (3) months after the end of the month to which the reports relate. Unless set forth in this Specification 3, any reference to a specific time refers to Coordinated Universal Time (UTC). Monthly reports shall consist of data that reflects the state of the registry at the end of the month (UTC).
