Staffing Levels To the extent legislative appropriations and PIN authorizations allow, safe staffing levels will be maintained in all institutions where employees have patient, client, inmate or student care responsibilities. In July of each year, the Secretary or Deputy Secretary of each agency will, upon request, meet with the Union, to hear the employees’ views regarding staffing levels. In August of each year, the Secretary or Deputy Secretary of Budget and Management will, upon request, meet with the Union to hear the employees’ views regarding the Governor’s budget request.
Service Level Expectations Without limiting any other requirements of the Agreement, the Service Provider shall meet or exceed the following standards, policies, and guidelines:
WORKPLACE FLEXIBILITY The employer must ensure that any Individual Flexibility Agreement (IFA) is genuinely agreed to by the employer and the employee and result in the employee being better off overall at the time the IFA is made than the employee would have been if no IFA had been agreed to.
8.1 Notwithstanding any other provision of the Agreement, the employer and an individual employee may agree to vary the application of certain terms of the Agreement to meet the genuine individual needs of the employer and the individual employee. The terms the employer and the individual employee may agree to vary are the application of those permitted under Section 172 of the FW Act, and relates only to:-
8.1.1 arrangements for when work is performed;
8.1.2 salary sacrifice arrangements;
8.1.3 reduction in ordinary hours; and
8.1.4 are not unlawful terms under Section 194 of the FW Act.
8.2 The employer and the individual employee must have genuinely made the IFA without coercion or duress. An IFA can only be entered into after the individual employee has commenced employment with the employer.
8.3 The IFA between the employer and the individual employee must:
8.3.1 be confined to a variation in the application of one or more of the terms listed in Clause 8.1; and
8.4 The IFA between the employer and the individual employee must also:
8.4.1 be in writing, name the parties to the IFA and be signed by the employer and the individual employee and, if the employee is under eighteen (18) years of age, the employee’s parent or guardian;
8.4.2 state each term of the Agreement that the employer and the individual employee have agreed to vary;
8.4.3 detail how the application of each term has been varied by agreement between the employer and the individual employee;
Business Continuity Registry Operator shall maintain a business continuity plan, which will provide for the maintenance of Registry Services in the event of an extraordinary event beyond the control of the Registry Operator or business failure of Registry Operator, and may include the designation of a Registry Services continuity provider. If such plan includes the designation of a Registry Services continuity provider, Registry Operator shall provide the name and contact information for such Registry Services continuity provider to ICANN. In the case of an extraordinary event beyond the control of the Registry Operator where the Registry Operator cannot be contacted, Registry Operator consents that ICANN may contact the designated Registry Services continuity provider, if one exists. Registry Operator shall conduct Registry Services Continuity testing at least once per year.
Performance Levels (a) The Performance Levels which apply to the performance by the respective Parties of their obligations under this Agreement are set out in Part 1 of Schedule 5. A failure by either Party to achieve the relevant Performance Level will not constitute a breach of this Agreement and the only consequences of such failure as between the Parties shall be the consequences set out in this Clause 5.6.
(b) If the Operator does not comply with the Operator Performance Level then the Access Holder must pay to QR Network the amount determined in accordance with Schedule 5 as part of the invoice issued by QR Network for Access Charges and other charges for the Billing Period immediately following QR Network becoming entitled to that amount. Where there is no next Billing Period, the Operator must pay such amount to QR Network within fourteen (14) days after receipt of a Tax Invoice from QR Network.
(c) If QR Network does not comply with the QR Network Performance Level then QR Network will credit to the Access Holder the amount determined in accordance with Schedule 5 by way of a deduction from the invoice issued by QR Network for Access Charges and other charges for the Billing Period immediately following the Access Holder becoming entitled to that amount. Where there is no next Billing Period, QR Network must pay such amount to the Access Holder within fourteen (14) days after receipt of a Tax Invoice from the Access Holder.
(d) The Parties must, if requested by either Party, meet to review the Performance Levels subject to such review not occurring within six (6) Months after the Commitment Date or any previous review of the Performance Levels. If either Party notifies the other that it considers that the Performance Levels are no longer appropriate, the Parties may agree on varied Performance Levels and any associated variations to the Agreement including the Base Access Charges and the Train Service Description. If the Parties are unable to agree to such variations, then the existing Performance Levels shall continue to apply unless varied by QR Network in accordance with the provisions of Clause 5.6(e).
(e) In the event that the Access Holder and/or the Operator
(i) does not comply in any material respect with the Train Service Description; and
(ii) the Access Holder fails to demonstrate to the reasonable satisfaction of QR Network when requested to do so, that the Access Holder will consistently comply with the Train Service Description for the remainder of the Term then, following consultation with the Access Holder, QR Network will be entitled to:
(iii) vary the Train Service Description to a level it reasonably expects to be achievable by the Access Holder for the remainder of the Term having regard to the extent of previous compliance with the Train Service Description (ignoring, for the purpose of assessing previous compliance, any non-compliance to the extent that the non-compliance was attributable to a Railway Operator (other than the Access Holder) or to QR Network); and
(iv) vary the Agreement (including, without limitation, the Operator Performance Level and the Base Access Charges) to reflect the impact of the change in the Train Service Description.
(f) The Access Holder shall be entitled to dispute any variation proposed by QR Network pursuant to Clause 5.6(e) and such dispute will be referred to an expert for resolution in accordance with Clause 17.3.
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.
Business Continuity Planning Supplier shall prepare and maintain at no additional cost to Buyer a Business Continuity Plan (“BCP”). Upon written request of Buyer, Supplier shall provide a copy of Supplier’s BCP. The BCP shall be designed to ensure that Supplier can continue to provide the goods and/or services in accordance with this Order in the event of a disaster or other BCP-triggering event (as such events are defined in the applicable BCP). Supplier’s BCP shall, at a minimum, provide for: (a) the retention and retrieval of data and files; (b) obtaining resources necessary for recovery, (c) appropriate continuity plans to maintain adequate levels of staffing required to provide the goods and services during a disruptive event; (d) procedures to activate an immediate, orderly response to emergency situations; (e) procedures to address potential disruptions to Supplier’s supply chain; (f) a defined escalation process for notification of Buyer, within two (2) business days, in the event of a BCP-triggering event; and (g) training for key Supplier Personnel who are responsible for monitoring and maintaining Supplier’s continuity plans and records. Supplier shall maintain the BCP and test it at least annually or whenever there are material changes in Supplier’s operations, risks or business practices. Upon Xxxxx’s written and reasonable request, Supplier shall provide Buyer an executive summary of test results and a report of corrective actions (including the timing for implementation) to be taken to remedy any deficiencies identified by such testing. Upon Xxxxx’s request and with reasonable advance notice and conducted in such a manner as not to unduly interfere with Supplier’s operations, Supplier shall give Buyer and its designated agents access to Supplier’s designated representative(s) with detailed functional knowledge of Supplier’s BCP and relevant subject matter.
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.
Business Continuity Plan The Warrant Agent shall maintain plans for business continuity, disaster recovery, and backup capabilities and facilities designed to ensure the Warrant Agent’s continued performance of its obligations under this Agreement, including, without limitation, loss of production, loss of systems, loss of equipment, failure of carriers and the failure of the Warrant Agent’s or its supplier’s equipment, computer systems or business systems (“Business Continuity Plan”). Such Business Continuity Plan shall include, but shall not be limited to, testing, accountability and corrective actions designed to be promptly implemented, if necessary. In addition, in the event that the Warrant Agent has knowledge of an incident affecting the integrity or availability of such Business Continuity Plan, then the Warrant Agent shall, as promptly as practicable, but no later than twenty-four (24) hours (or sooner to the extent required by applicable law or regulation) after the Warrant Agent becomes aware of such incident, notify the Company in writing of such incident and provide the Company with updates, as deemed appropriate by the Warrant Agent under the circumstances, with respect to the status of all related remediation efforts in connection with such incident. The Warrant Agent represents that, as of the date of this Agreement, such Business Continuity Plan is active and functioning normally in all material respects.
Service Level In the event that League InfoSight discovers or is notified by you of the existence of Non-Scheduled Downtime, we will use commercially reasonable efforts to determine the source of the problem and attempt to resolve it as quickly as possible.
