Load Shedding The Distributor may carry out Load Shedding in the following circumstances:
(a) Maintenance of Network equipment: if the Distributor wishes to inspect or effect alterations, maintenance, repairs, or additions to any part of the Network, subject to clauses 4.6, 4.8, 4.10, and Schedule 5 as applicable;
(b) Permitted by Service Standards: as permitted by the Service Standards, if the Customer has elected to receive an interruptible or otherwise non-continuous supply of electricity;
(c) Compliance with instructions from the System Operator:
(i) to comply with a request or instruction received from the System Operator in accordance with the Code; or
(ii) if communication with the System Operator has been lost, and the Distributor reasonably believes that, had communication with the System Operator been maintained, the Distributor would have received a request or instruction from the System Operator to shed load in accordance with the Code;
(d) Maintain security and safety: to maintain the security and safety of the Network in order to:
(i) maintain a safe environment, consistent with the Distributor's health and safety policies;
(ii) prevent unexpected short term overloading of the Network;
(iii) prevent voltage levels rising or falling outside of legal requirements;
(iv) manage System Security; and
(v) avoid or mitigate damage to the Network or any equipment connected to the Network;
(e) Compliance with the Code: to comply with the Code or the law; or
(f) Other circumstances: for any other purpose that, in the Distributor’s reasonable opinion, and in accordance with Good Electricity Industry Practice, requires the interruption or reduction of delivery of electricity to any ICP.
ELECTRONIC WORKFLOW SYSTEM OGS reserves the right to incorporate an electronic workflow system that may include elements of the Authorized User RFQ process. OGS reserves the right to post Authorized User Contract usage of Centralized Contracts. For Lot 4 only, when provided for in the RFQ and resultant Authorized User Agreement, the Authorized Users may reimburse travel expenses. All rules and regulations associated with this travel can be found at ▇▇▇▇://▇▇▇.▇▇▇▇▇.▇▇.▇▇/agencies/travel/travel.htm. In no case will any travel reimbursement be charged that exceeds these rates. All travel will be paid only as specified within the Authorized User Agreement and must be billed with the associated services on the same Invoice with receipts attached. The Contractor shall receive prior approval from the Authorized User for any travel that occurs during the term of an Authorized User Agreement. Parking fees and/or parking tickets shall not be paid by an Authorized User. Unless otherwise specified in writing by the Authorized User, a vehicle will not be provided by Authorized User to the Contractor for travel. Therefore, the Contractor will be responsible for ensuring that the Contractor has access to an appropriate vehicle (e.g., personal vehicle or rental vehicle) or common carrier with which to carry out any necessary travel. For the Contractor to obtain reimbursement for the use of a rental vehicle, such use must be justified as the most cost- effective mode of transportation under the circumstances (including consideration of the most effective use of time). The Contractor is responsible for keeping adequate records to substantiate any claims for travel reimbursement. All services provided under the resultant Authorized User Agreement must be performed within CONUS. There are no BONDS for this Contract. However, an Authorized User may require in an RFQ a performance, payment or Bid bond, or negotiable irrevocable letter of credit or other form of security for the faithful performance for the resultant Authorized User Agreement. Pursuant to New York State Executive Law Article 15-A and Parts 140-145 of Title 5 of the New York Codes, Rules and Regulations (“NYCRR”), the New York State Office of General Services (“OGS”) is required to promote opportunities for the maximum feasible participation of New York State-certified Minority- and Women-owned Business Enterprises (“MWBEs”) and the employment of minority group members and women in the performance of OGS contracts.
Drug-Free Workplace Certification As required by Executive Order No. 90-5 dated April 12, 1990, issued by the Governor of Indiana, the Company hereby covenants and agrees to make a good faith effort to provide and maintain a drug-free workplace at the Project Location. The Company will give written notice to the IEDC within ten (10) days after receiving actual notice that the Company, or an employee of the Company in the State of Indiana, has been convicted of a criminal drug violation occurring in the workplace. False certification or violation of this certification may result in sanctions including, but not limited to, suspension of payments under the Agreement, termination of the Agreement and/or debarment of contracting opportunities with the State for up to three (3) years. In addition to the provisions of the above paragraph, if the total amount set forth in the Agreement is in excess of $25,000.00, the Company agrees that it will provide a drug-free workplace by:
A. Publishing and providing to all of its employees a statement notifying them that the unlawful manufacture, distribution, dispensing, possession or use of a controlled substance is prohibited in the Company’s workplace, and specifying the actions that will be taken against employees for violations of such prohibition;
Electronic Road Show The Company has made available a Bona Fide Electronic Road Show in compliance with Rule 433(d)(8)(ii) of the Securities Act Regulations such that no filing of any “road show” (as defined in Rule 433(h) of the Securities Act Regulations) is required in connection with the Offering.
System Logging The system must maintain an automated audit trail which can 20 identify the user or system process which initiates a request for PHI COUNTY discloses to 21 CONTRACTOR or CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY, 22 or which alters such PHI. The audit trail must be date and time stamped, must log both successful and 23 failed accesses, must be read only, and must be restricted to authorized users. If such PHI is stored in a 24 database, database logging functionality must be enabled. Audit trail data must be archived for at least 3 25 years after occurrence.