Reference file Sample Clauses

Reference file. The goal of Queen’s University is to maintain a full campus map of each building and surrounding landscape. This file will contain links to each campus building model together in a master project. This model will be updated as projects are completed. The campus map will contain master site coordinates which will be synchronized with each campus building model. Each new project will start from the existing building model and will contain any necessary site coordinates, structural grids, and datum levels which should not be altered. All disciplines not already contained in the building model at the beginning of a project must obtain coordinates, grids, and levels from the provided model. The Project Manager to manage project start and confirm the most up to date model is being used and ensure preservation of coordinates, grids, and levels.
Sample 1
AutoNDA by SimpleDocs
Reference file. This file consists of all business TIN’s linked to the health insurance business operations of a VDSA partner. Current versions of the six Standard Data Files and the TIN Reference File immediately follow. In the VDSA itself, in Section III, Purpose of this Agreement, reference is made to Attachments A through G. The Data Files below are those Attachments, still labeled A through G. The Business Rules that apply to these Data Files can be found in Section III of the User Guide. Please note that headers and trailers are part of the files they start and finish. They are not stand-alone documents and you may not submit headers and trailers as separate files. However, headers and trailers are not to be included when determining the record count in a submission. Once again we remind you that from time to time the information provided here will change. All significant updates to the material in the most recent version of this User Guide are described on the Cover Page of this document. Always check the Effective Date shown on the Cover Page, on Page 1, and in the footer on each page to be sure you are using the most recent version.
Sample 1

Related to Reference file

  • Reference Materials The Board agrees to continue to make available to employees the reference materials maintained by the district. Principals are encouraged to provide additional reference materials of high use in schools where feasible.

  • Grievance File Records involving the processing of an employee's grievance, such as the grievance form, step appeals/responses, and settlement documents, will be kept in a file separate from the employee’s personnel file. It is not the intent of this section to exclude from the employee's personnel file final disciplinary action documents, including those that result from a settlement agreement.

  • Separate Grievance File All documents, communications and records dealing with the processing of a grievance shall be filed in a separate grievance file and shall not be kept in the personnel file of any of the participants.

  • Appendix A – HRIS File Each Board shall provide to the Trustees of the ETFO ELHT directly, or provide authorization through its Insurance Carrier of Record to gather and provide to the Trustees, the following information within one (1) month of notification from the Trustees. The following information shall be provided in the formats agreed to by the Trustees of the ETFO ELHT and the employer representatives:

  • Employee File 27.01 Upon request to their immediate supervisor, employees are entitled to read, review and be provided with one (1) copy of any document in their human resources file at a mutually agreed time. The Senior Union Official, or designate, with the written authority of the employee, shall be entitled to review the employee's human resource file in the workplace, in order to facilitate the investigation of a grievance. The employee or the Senior Union Official, as the case may be, shall give the Employer seven (7) days' notice prior to examining the file. Employees shall have the right to rebut in writing any document, including but not limited to disciplinary notices and evaluations, in their human resources file. Such rebuttals, other than grievances, shall be attached to the document and placed in the personnel file.

  • Authoritative Root Database To the extent that ICANN is authorized to set policy with regard to an authoritative root server system (the “Authoritative Root Server System”), ICANN shall use commercially reasonable efforts to (a) ensure that the authoritative root will point to the top-­‐level domain nameservers designated by Registry Operator for the TLD, (b) maintain a stable, secure, and authoritative publicly available database of relevant information about the TLD, in accordance with ICANN publicly available policies and procedures, and (c) coordinate the Authoritative Root Server System so that it is operated and maintained in a stable and secure manner; provided, that ICANN shall not be in breach of this Agreement and ICANN shall have no liability in the event that any third party (including any governmental entity or internet service provider) blocks or restricts access to the TLD in any jurisdiction.

  • Grievance Files Written grievances and responses will be maintained separately from the employee’s personnel file.

  • Line Information Database 9.1 LIDB is a transaction-oriented database accessible through Common Channel Signaling (CCS) networks. For access to LIDB, e-Tel must purchase appropriate signaling links pursuant to Section 10 of this Attachment. LIDB contains records associated with End User Line Numbers and Special Billing Numbers. LIDB accepts queries from other Network Elements and provides appropriate responses. The query originator need not be the owner of LIDB data. LIDB queries include functions such as screening billed numbers that provides the ability to accept Collect or Third Number Billing calls and validation of Telephone Line Number based non-proprietary calling cards. The interface for the LIDB functionality is the interface between BellSouth’s CCS network and other CCS networks. LIDB also interfaces to administrative systems.

  • Line Information Database (LIDB 9.1 BellSouth will store in its Line Information Database (LIDB) records relating to service only in the BellSouth region. The LIDB Storage Agreement is included in this Attachment as Exhibit B.

  • Privacy Statement 6.1. The Parties agree to keep all information related to the signing and fulfillment of this Agreement confidential, and not to disclose it to any third parties, except for subcontractors involved in this agreement, unless prior written consent is obtained from the other Party. Should subcontractors be engaged under this agreement, they are required to adhere to its terms and conditions.

Time is Money Join Law Insider Premium to draft better contracts faster.