School Official For the purposes of this DPA and pursuant to 34 CFR § 99.31(b), a School Official is a contractor that: (1) Performs an institutional service or function for which the agency or institution would otherwise use employees; (2) Is under the direct control of the agency or institution with respect to the use and maintenance of Student Data including Education Records; and (3) Is subject to 34 CFR § 99.33
Consider Operator as School Official The Parties agree that Operator is a “school official” under FERPA and has a legitimate educational interest in personally identifiable information from education records. For purposes of the Service Agreement and this DPA, Operator: (1) provides a service or function for which the LEA would otherwise use employees; (2) is under the direct control of the LEA with respect to the use and maintenance of education records; and
School Official Designation Pursuant to Article I, Paragraph 1 of the DPA Standard Clauses, and in accordance with FERPA, ISSRA and SOPPA, in performing its obligations under the DPA, the Provider is acting as a school official with legitimate educational interest; is performing an institutional service or function for which the LEA would otherwise use its own employees; is under the direct control of the LEA with respect to the use and maintenance of Student Data; and is using Student Data only for an authorized purpose and in furtherance of such legitimate educational interest.
Consider Provider as School Official The Parties agree that Provider is a “school official” under FERPA and has a legitimate educational interest in personally identifiable information from education records received from the LEA pursuant to the DPA. For purposes of the Service Agreement and this DPA, Provider: (1) provides a service or function for which the LEA would otherwise use employees; (2) is under the direct control of the LEA with respect to the use and maintenance of education records; and (3) is subject to the requirements of FERPA governing the use and redisclosure of personally identifiable information from the education records received from the LEA.
Official Personnel File Only one (1) official personnel file shall be kept for each employee at the appropriate personnel office. Records of previous discipline not found in the official personnel file cannot be used against an employee in any future disciplinary proceeding. Grievances shall not be kept in the employee’s official personnel file. Employees shall be informed as to where their personnel file is maintained.
E6 Publicity, Media and Official Enquiries The Contractor shall not:
SBC-12STATE 47.1.1 The terms contained in this Agreement and any Appendices, Attachments, Exhibits, Schedules, and Addenda constitute the entire agreement between the Parties with respect to the subject matter hereof, superseding all prior understandings, proposals and other communications, oral or written between the Parties during the negotiations of this Agreement and through the execution and/or Effective Date of this Agreement. This Agreement shall not operate as or constitute a novation of any agreement or contract between the Parties that predates the execution and/or Effective Date of this Agreement.
KEY OFFICIALS A. The technical representatives for the Federal Agencies are as follows:
Publicity, Media and Official Enquiries 22.1 Without prejudice to the Authority’s obligations under the FOIA, neither Party shall make any press announcements or publicise the Contract or any part thereof in any way, except with the written consent of the other Party.
22.2 Both Parties shall take reasonable steps to ensure that their Personnel comply with clause 22.1.
AT&T-12STATE acknowledges that CLEC may have an embedded base of one-way trunks ordered and installed prior to the Effective Date of this Agreement that were used for termination of CLEC’s Section 251(b)(5)/IntraLATA Toll Traffic to AT&T-12STATE (Embedded Base). To the extent that CLEC has such an Embedded Base, CLEC shall only augment trunk groups in the Embedded Base with the mutual agreement of the Parties. CLEC shall not order any new one-way trunk groups following the Effective Date of this Agreement. Moreover, the Parties agree that the Embedded Base will be converted to two-way trunk groups under the following circumstances:
4.2.1.1 With reasonable notification from AT&T-12STATE and upon AT&T-12STATE’s request, CLEC shall convert all of its Embedded Base to two-way trunks.
4.2.1.2 At any time an Embedded Base trunk group (either originating or terminating) requires augmentation, AT&T-12STATE can require the associated originating and terminating trunks to be converted to a single two-way trunk group prior to the augmentation.
4.2.1.3 When any network changes are to be performed on a project basis (i.e., central office conversions, tandem re-homes, etc.), upon request and reasonable notice by AT&T-12STATE, CLEC will convert all of its Embedded Base affected by the project within the intervals and due dates required by the project parameters.
4.2.1.4 In addition to the foregoing, CLEC may choose, at any time, to convert its Embedded Base to two-way trunk groups.
4.2.1.5 The Parties will coordinate any trunk group migration, trunk group prioritization and implementation schedule. AT&T-12STATE agrees to develop a cutover plan within thirty (30) days of notification to CLEC of the need to convert pursuant to Section 4.2.1.1 above and Section 4.2.1.3 above.
