BID EVALUATION The Commissioner reserves the right to accept or reject any and all Bids, or separable portions of Bids, and waive technicalities, irregularities, and omissions if the Commissioner determines the best interests of the State will be served. The Commissioner, in his/her sole discretion, may accept or reject illegible, incomplete or vague Bids and his/her decision shall be final. A conditional or revocable Bid which clearly communicates the terms or limitations of acceptance may be considered, and Contract award may be made in compliance with the Bidder’s conditional or revocable terms in the Bid.
Annual Evaluations The purpose of the annual evaluation is to assess and communicate the nature and extent of an employee's performance of assigned duties consistent with the criteria specified below in this Policy. Except for those employees who have received notice of non-reappointment pursuant to the BOT- UFF Policy on Non- reappointment, every employee shall be evaluated at least once annually. Personnel decisions shall take such annual evaluations into account, provided that such decisions need not be based solely on written faculty performance evaluations.
Performance Evaluations Employee performance shall be evaluated and communicated on a yearly basis as required under County policy. Performance evaluations are used to demonstrate to employees that they are valued; record how an employee’s performance meet the requirements of the job; create a job history record; identify employee strengths and areas for enhancement; assist the employee and supervisor in an effort to attain the highest level of performance; and reinforce performance standards. Every effort will be made to include substantiated information within an employee’s performance evaluation. Non-recurring discipline history which is more than two (2) years old will not be referenced in performance evaluations. The County shall ensure employee performance evaluations are conducted in accordance with County and departmental policy. Performance evaluations and disciplinary matters shall only be conducted by County employees. When an employee who does not agree with the overall rating he/she receives on his/her written performance evaluation, he/she shall discuss and attempt to resolve the differences with his/her immediate supervisor. If discussion with his/her immediate supervisor does not result in resolution of the differences, the employee may file a written request to meet with the next level of management. Said request shall state the unresolved issues and the specific changes in the written performance evaluation the employee is seeking. The appropriate manager shall meet with the employee to discuss the unresolved issues. If the issues are not resolved to the employee’s satisfaction following discussion with the appropriate manager, the employee may within thirty (30) working days file a written request for a meeting with the department head. Within fourteen (14) working days of receipt of a written request stating the unresolved issues and the desired changes in the written performance evaluation, the department head shall meet with the employee to discuss the issues. Within ten (10) working days of said meeting, the department head shall respond in writing to the employee. The decision of the Department Head shall be final and not subject to the grievance procedure. An employee may submit a written response to his/her evaluation that shall be placed in his/her personnel file.
Student Evaluations Student evaluations shall be completed by the end of the 12th week of the fall semester.
EMPLOYEE EVALUATIONS 6.1 Administrators will meet with new employees to discuss their job description within one (1) month of hire. The Administrator and new employee will sign off on the job description and it will be forwarded to the Human Resources Department for inclusion in the employee‘s personnel file. The Human Resources Department will compile and distribute a list showing each employee‘s evaluator prior to November 1st of each year. Bargaining unit job descriptions will be made available via the District‘s web site.
6.2 Evaluations will transpire as follows for employees that are receiving satisfactory ratings:
a. New hires—regular part-time (school year employees) will be evaluated at three (3) and six (6) working months.
b. New hires—full time (12 month employees) will be evaluated at three (3), six (6) and twelve (12) months.
c. After the initial year of employment, each employee shall be evaluated at least once annually by March 31st.
6.3 Criteria for evaluating bargaining unit members will be based on the performance categories outlined on the evaluation form as related to the job description of their specific position assignment.
6.4 Evaluation reports shall include feedback regarding strengths and weaknesses (if any) demonstrated by the employee. Prior to an employee receiving a rating less than “Meets Expectations,” the employee shall be advised of the performance concern and provided with a clear statement of any deficiency and a statement defining acceptable performance. This shall occur within a reasonable time prior to the final evaluation to allow the employee a chance to demonstrate improvement.
6.5 In the event an employee is evaluated overall as “Does Not Meet Expectations,” the district, in consultation with the employee and the Association, will provide the employee a written plan of improvement (See Employee Plan of Improvement form in Appendix). The plan shall clearly define all areas of deficiency, provide clear and attainable performance goals, and outline supports (if any) to be given, including any necessary training at the District’s expense. The employee will be given a reasonable amount of time, not to exceed sixty (60) working days, to meet job performance expectations. During the improvement period, feedback will be provided through a minimum of three scheduled meetings. Following the completion of the plan, the supervisor shall notify the employee in writing of the outcome. Failure to demonstrate satisfactory improvement may constitute grounds for termination.
6.6 The bargaining unit member shall be given a copy of their evaluation, and any data collection sheets (with the submitters name excluded) used in the evaluation.
6.7 Under the law there is no right to Association Representation at evaluation conferences.
6.8 Any information shared with the evaluating administrator for the evaluation process shall be recorded on Data Collection Sheet(s), with the exception of those unit members that have supervising teachers. Supervising teachers will work directly with the evaluating administrator to share performance information for inclusion in the unit member‘s evaluation.
6.9 Employees shall have the right to respond to evaluations in writing. Such written response shall be attached to the evaluation if received within 5 days.
6.10 No bargaining unit member shall be required to sign a blank or incomplete evaluation form.
Account Types The Financial Institution agrees that each Collateral Account is, and will be maintained as, either a “securities account” (as defined in Section 8-501 of the UCC) or a “deposit account” (as defined in Section 9-102(a)(29) of the UCC).
Self-Evaluation Each regular faculty member shall provide a self-evaluation. It shall address, among other items, the faculty member's fulfillment of professional responsibilities as referenced in Section 18.2.3 and an assessment of his or her own performance. The faculty member will share the self-evaluation with the Faculty Evaluation Committee and the first-level manager or designee. The self-evaluation will become part of the evaluation report.
Alternate Billed Calls 1.1 The Parties will engage in settlements of intraLATA intrastate alternate-billed calls (e.g., collect, calling card, and third-party billed calls) originated or authorized by their respective Customers in accordance with an arrangement mutually agreed to by the Parties.
Trunk Types 2.2.1 In interconnecting their networks pursuant to this Attachment, the Parties will use, as appropriate, the following separate and distinct trunk groups:
2.2.1.1 Interconnection Trunks for the transmission and routing of Reciprocal Compensation Traffic, translated LEC IntraLATA toll free service access code (e.g., 800/888/877) traffic, and IntraLATA Toll Traffic, between their respective Telephone Exchange Service Customers, Tandem Transit Traffic, and, Measured Internet Traffic, all in accordance with Sections 5 through 8 of this Attachment;
2.2.1.2 Access Toll Connecting Trunks for the transmission and routing of Exchange Access traffic, including translated InterLATA toll free service access code (e.g., 800/888/877) traffic, between Ymax Telephone Exchange Service Customers and purchasers of Switched Exchange Access Service via a Verizon access Tandem in accordance with Sections 9 through 11 of this Attachment; and
2.2.1.3 Miscellaneous Trunk Groups as mutually agreed to by the Parties, including, but not limited to: (a) choke trunks for traffic congestion and testing; and, (b) untranslated IntraLATA/InterLATA toll free service access code (e.g. 800/888/877) traffic.
2.2.2 Other types of trunk groups may be used by the Parties as provided in other Attachments to this Agreement (e.g., 911/E911 Trunks) or in other separate agreements between the Parties (e.g., directory assistance trunks, operator services trunks, BLV/BLVI trunks or trunks for 500/555 traffic).
2.2.3 In accordance with the terms of this Agreement, the Parties will deploy One-Way Interconnection Trunks (trunks with traffic going in one direction, including one-way trunks and uni-directional two-way trunks) and/or Two-Way Interconnection Trunks (trunks with traffic going in both directions).
2.2.4 Ymax shall establish, at the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA, separate Interconnection Trunk group(s) between such POI(s) and each Verizon Tandem in a LATA with a subtending End Office(s) to which Ymax originates calls for Verizon to terminate.
2.2.5 In the event the volume of traffic between a Verizon End Office and a technically feasible Point of Interconnection on Verizon’s network in a LATA, which is carried by a Final Tandem Interconnection Trunk group, exceeds (a) the Centium Call Seconds (Hundred Call Seconds) busy hour equivalent of one (1) DS1 at any time; (b) 200,000 minutes of use for a single month; and/or; (c) 600 busy hour Centium Call Seconds (BHCCS) of use for a single month: (i) if One-Way Interconnection Trunks are used, the originating Party shall promptly establish new or augment existing End Office One-Way Interconnection Trunk groups between the Verizon End Office and the technically feasible Point of Interconnection on Verizon’s network; or,
Scheduled Outages (a) Commencing at least sixty (60) days before Initial Synchronization and throughout the Delivery Term, Seller shall, no later than January 1, April 1, July 1 and October 1 of each year, submit to SCE, using the Web Client, Seller’s schedule of proposed planned outages (“Outage Schedule”) for the subsequent twenty-four month period.
(b) Seller shall provide the following information for each proposed planned outage:
(i) Start date and time;
(ii) End date and time; and
(iii) Capacity online, in MW, during the planned outage.
(c) Within thirty (30) days after SCE’s receipt of an Outage Schedule, SCE shall notify Seller in writing of any reasonable request for changes to the Outage Schedule, and Seller shall, consistent with Prudent Electrical Practices, accommodate SCE’s requests regarding the timing of any planned outage.
(d) Seller shall cooperate with SCE to arrange and coordinate all Outage Schedules with the CAISO.
(e) If a condition occurs at the Generating Facility which causes Seller to revise its planned outages, Seller shall promptly provide Notice to SCE, using the Web Client, of such change (including an estimate of the length of such planned outage) as required in the CAISO Tariff after the condition causing the change becomes known to Seller.
(f) Seller shall promptly prepare and provide to SCE upon request, using the Web Client, all reports of actual or forecasted outages that SCE may reasonably require for the purpose of enabling SCE to comply with Section 761.3 of the California Public Utilities Code or any Applicable Law mandating the reporting by investor owned utilities of expected or experienced outages by electric energy generating facilities under contract to supply electric energy.
