EMPLOYEE FILES 10.01 A copy of any completed formal evaluation which is to be placed in an employee’s file shall be first reviewed with the employee. The employee shall initial such evaluation as having been read and shall have the opportunity to add her or his views to such evaluation prior to it being placed in her or his file. It is understood that such evaluations do not constitute disciplinary action by the Employer against the employee. Having provided a written request to the Director of Care, or her designate, an employee shall be entitled to her personnel file for the purpose of reviewing any evaluations or formal disciplinary notations contained therein, in the presence of the Director of Care, at a mutually agreeable time. 10.02 The Employer will accommodate reasonable requests for copies of performance appraisals and records of discipline in an employee's file. 10.03 Letters of discipline shall be removed from an employee's file eighteen (18) months following the receipt of such letters provided that the employee's disciplinary record has remained discipline free over the eighteen (18) months period. Leaves of absence in excess of thirty (30) continuous calendar days will not count towards the eighteen (18) months period noted above.
Local Circuit Switching Capability, including Tandem Switching Capability 4.2.1 Local circuit switching capability is defined as: (A) line-side facilities, which include, but are not limited to, the connection between a loop termination at a main distribution frame and a switch line card; (B) trunk-side facilities, which include, but are not limited to, the connection between trunk termination at a trunk-side cross-connect panel and a switch trunk card; (C) switching provided by remote switching modules; and (D) all features, functions, and capabilities of the switch, which include, but are not limited to: (1) the basic switching function of connecting lines to lines, line to trunks, trunks to lines, and trunks to trunks, as well as the same basic capabilities made available to BellSouth’s customers, such as a telephone number, white page listings, and dial tone; and (2) all other features that the switch is capable of providing, including but not limited to customer calling, customer local area signaling service features, and Centrex, as well as any technically feasible customized routing functions provided by the switch. Any features that are not currently available but are technically feasible through the switch can be requested through the BFR/NBR process. 4.2.2 Notwithstanding BellSouth’s general duty to unbundle local circuit switching, BellSouth shall not be required to unbundle local circuit switching for Lightyear when Lightyear serves an end-user with four (4) or more voice-grade (DS-0) equivalents or lines served by BellSouth in one of the following MSAs: Atlanta, GA; Miami, FL; Orlando, FL; Ft. Lauderdale, FL; Charlotte-Gastonia-Rock Hill, NC; Greensboro-Winston Salem-High Point, NC; Nashville, TN; and New Orleans, LA, and BellSouth has provided non-discriminatory cost based access to the Enhanced Extended Link (EEL) throughout Density Zone 1 as determined by NECA Tariff No. 4 as in effect on January 1, 1999. 4.2.3 In the event that Lightyear orders local circuit switching for an end user with four (4) or more DS0 equivalent lines within Density Zone 1 in an MSA listed above, BellSouth shall charge Lightyear the market based rates in Exhibit B for use of the local circuit switching functionality for the affected facilities. If a market rate is not set forth in Exhibit B, such rate shall be negotiated by the Parties.
Zone File Access Agreement Registry Operator will enter into an agreement with any Internet user, which will allow such user to access an Internet host server or servers designated by Registry Operator and download zone file data. The agreement will be standardized, facilitated and administered by a Centralized Zone Data Access Provider, which may be ICANN or an ICANN designee (the “CZDA Provider”). Registry Operator (optionally through the CZDA Provider) will provide access to zone file data per Section 2.1.3 of this Specification and do so using the file format described in Section 2.1.4 of this Specification. Notwithstanding the foregoing, (a) the CZDA Provider may reject the request for access of any user that does not satisfy the credentialing requirements in Section 2.1.2 below; (b) Registry Operator may reject the request for access of any user that does not provide correct or legitimate credentials under Section 2.1.2 below or where Registry Operator reasonably believes will violate the terms of Section 2.1.5. below; and, (c) Registry Operator may revoke access of any user if Registry Operator has evidence to support that the user has violated the terms of Section 2.1.5 below.