of Attachment Z The Interconnection Customer shall be responsible for all System Upgrade Facility costs as required by Section 32.3.5.3.2 of Attachment Z or its share of any System Upgrade Facilities and System Deliverability Upgrades costs resulting from the final Attachment S process, as applicable, and Attachment 6 to this Agreement shall be revised accordingly.
ATTACHMENT B Applicable California Vehicle Code and Civil Code Provisions Note: Many California laws, which govern a tow Operator’s business and vehicle operations, are included in this attachment. The is list of California statutes included herein is intended as a general guide only and is not meant to be considered all-inclusive. It is the tow Operator’s responsibility to know and comply with all federal and state statutes and all local ordinances relating to his/her business operations, including those that are referred to in this document and those that are not; any new statutes or ordinances that are subsequently adopted; and any amendments, repeals, or modifications of existing statutes and ordinances, including but not limited to those described in this attachment.
APPENDIX F Appendix F, HBITS Processes and Forms, attached hereto, is hereby expressly made a part of this Contract as fully as if set forth at length herein. The Parties agree that the processes and forms set forth in this appendix may be updated as necessary, such as to facilitate the development of a web portal or other automated systems. OGS reserves the right to make changes to these processes and forms without seeking the prior written approval of the Department of Law or OSC, however, OGS agrees that any such changes shall comply with the terms and conditions of this Contract and not be material or substantive in nature. The Parties agree that detailed instructions for the completion of these forms shall be set forth in the “How to Use” document presented on the OGS web site or as part of the web portal or other automated system. Form 8, Monthly Report, shall be submitted electronically in Microsoft Excel 2007 or higher format, which will be separately provided by OGS.
Contract Task Order A-E shall be assigned work via a task order by COUNTY which shall subsequently be referred to as the “Contract Task Order” (hereinafter “CTO”). A CTO for each project shall be developed by A-E in conjunction with COUNTY Project Management staff. The COUNTY Project Manager shall manage all A-E’s work including monitoring the CTO work schedule, quality of deliverables, review of invoiced amounts, adherence to set budget, and internal review of submittal packages. A-E shall follow all requirements as outlined in the CTO; this general Scope of Work, the project specific Scope Statement, and the Architect-Engineer Guide (Rev July 2018). The CTO shall include a detailed Scope Statement, describing tasks to be performed with a specific list of deliverables for each task, schedule of work and cost to complete the work. The schedule of work shall allow enough time for meetings with COUNTY Management staff to review the work progress, provide technical and policy direction, resolve problems and ensure adherence to the work completion schedule. The CTO shall include a cover sheet provided by COUNTY Project Management staff with the appropriate signature blocks and contract information. Once both Parties agree, and all Parties have signed the CTO, COUNTY Management staff shall provide A-E with a Notice to Proceed (NTP) to begin work. A-E shall submit all plans, reports and other documents produced under the CTO to the assigned COUNTY Project Manager within the timeframe indicated in the CTO or as directed by COUNTY Project Management staff.