File Cabinet Sample Clauses

File Cabinet. NAPE/AFSCME will be permitted to maintain one NAPE/AFSCME provided file cabinet at each major work site (Nebraska Department of Education Office Building in Lincoln and other NDE offices) for use by NAPE/AFSCME representatives, unless the location of such cabinet is not practicable.
Sample 1See All (4)
AutoNDA by SimpleDocs
File Cabinet. ‌ The City will allow the Union to place, at its own cost, a file cabinet on City premises. Said cabinet is the property of the Union and shall be locked and accessible to the Union. The file cabinet will be standard size and be located in the copy room at the main fire station. The Union will hold the City harmless for any negligence, not on the part of the City, for damages or breaches of security to the file cabinet.
Sample 1
File Cabinet. The Board shall provide the Council with space for a file cabinet in the building to which the Council President is assigned for use in implementing the terms of this Agreement.
Sample 1Sample 2
File Cabinet. Provided space is available, the District agrees to furnish suitable space within a fire station for the Union’s file cabinet. The location shall be mutually agreeable and must not interfere with the operations of the District. All costs for the file cabinet and folders shall be borne by the Union.
Sample 1Sample 2
File Cabinet. SECTION 11.1 It is agreed that the Union shall be permitted to have one (1) file cabinet upon the premises of each manned Fire station within the City, and that the use of such file cabinet shall be limited to storage of official Uniondocuments. SECTION 11.2 The Union shall ensure that said file cabinet is kept secure and locked, and the parties agree that only Union officers and officials shall have access to the Union file cabinet. SECTION 11.3 The Union shall be responsible for the purchase and maintenance of such file cabinet, which shall at all times be treated as theproperty solely of the Union. SECTION 11.4 The Union shall be permitted to place such file cabinet in a location to be designated by the Fire Division Chief. SECTION 11.5 The Union shall be permitted to have such file cabinet upon the Fire Division premises so long as the Chief, in their discretion, determines that the space occupied by the file cabinet is not required for Fire Division use and so long as the Chief, in their discretion, does not find that the location of the file cabinet on the Fire Division premises interferes with, interrupts, or disrupts the operation of the Division. SECTION 11.6 For any of the reasons mentioned in Section 11.5 above, the Chief, in the exercise of their discretion, may require the removal of such file cabinet from the Fire Division premises. The Chiefs decision to require removal of the file cabinet shall not be subject to the Grievance Procedure contained elsewhere herein or be otherwise appealable.
Sample 1Sample 2
File Cabinet. The Association will have a permanent location for a filing cabinet in a general office area with the location to be determined by the Superintendent.
Sample 1
File Cabinet. The school committee agrees to provide a lockable file cabinet in each school and location serviced by itinerants (e.g., school psychologists, occupational therapists, physical therapists, speech and language pathologists) for secure storage of student records.
Sample 1
AutoNDA by SimpleDocs
File Cabinet. The Employer shall provide to the Union a file cabinet to store Union correspondence and other such material.
Sample 1

Related to File Cabinet

  • File Naming Conventions Files will be named according to the following convention: {gTLD}_{YYYY-MM-DD}_{type}_S{#}_R{rev}.{ext} where: {gTLD} is replaced with the gTLD name; in case of an IDN-TLD, the ASCII-compatible form (A-Label) must be used; {YYYY-MM-DD} is replaced by the date corresponding to the time used as a timeline watermark for the transactions; i.e. for the Full Deposit corresponding to 2009-08-02T00:00Z, the string to be used would be “2009-08-02”; {type} is replaced by: “full”, if the data represents a Full Deposit; “diff”, if the data represents a Differential Deposit; “thin”, if the data represents a Bulk Registration Data Access file, as specified in Section 3 of Specification 4; {#} is replaced by the position of the file in a series of files, beginning with “1”; in case of a lone file, this must be replaced by “1”. {rev} is replaced by the number of revision (or resend) of the file beginning with “0”: {ext} is replaced by “sig” if it is a digital signature file of the quasi-homonymous file. Otherwise it is replaced by “ryde”.

  • Removal After Your Tax Filing Deadline If you are correcting an excess contribution after your tax filing deadline, including extensions, remove only the amount of the excess contribution. The six percent excess contribution penalty tax will be imposed on the excess contribution for each year it remains in the IRA. An excess withdrawal under this method will only be taxable to you if the total contributions made in the year of the excess exceed the annual applicable contribution limit.

  • File Search Reports File search reports have been obtained from each Uniform Commercial Code filing office identified with respect to such Grantor in Section 2 hereof, and such search reports reflect no liens against any of the Collateral other than those permitted under the Credit Agreement.

  • File Format Standard Registry Operator (optionally through the CZDA Provider) will provide zone files using a subformat of the standard Master File format as originally defined in XXX 0000, Section 5, including all the records present in the actual zone used in the public DNS. Sub-format is as follows: Each record must include all fields in one line as: <domain-name> <TTL> <class> <type> <RDATA>. Class and Type must use the standard mnemonics and must be in lower case. TTL must be present as a decimal integer. Use of /X and /DDD inside domain names is allowed. All domain names must be in lower case. Must use exactly one tab as separator of fields inside a record. All domain names must be fully qualified. No $ORIGIN directives. No use of “@” to denote current origin. No use of “blank domain names” at the beginning of a record to continue the use of the domain name in the previous record. No $INCLUDE directives. No $TTL directives. No use of parentheses, e.g., to continue the list of fields in a record across a line boundary. No use of comments. No blank lines. The SOA record should be present at the top and (duplicated at) the end of the zone file. With the exception of the SOA record, all the records in a file must be in alphabetical order. One zone per file. If a TLD divides its DNS data into multiple zones, each goes into a separate file named as above, with all the files combined using tar into a file called <tld>.zone.tar.

  • COVID-19 Vaccine Passports Pursuant to Texas Health and Safety Code, Section 161.0085(c), Contractor certifies that it does not require its customers to provide any documentation certifying the customer’s COVID-19 vaccination or post-transmission recovery on entry to, to gain access to, or to receive service from the Contractor’s business. Contractor acknowledges that such a vaccine or recovery requirement would make Contractor ineligible for a state-funded contract.

  • Reactive Power and Primary Frequency Response 9.6.1 Power Factor Design Criteria

  • Directory Listing and Directory Distribution 41 5. Voice Information Service Traffic 43 6. Intercept and Referral Announcements 44 7. Originating Line Number Screening (OLNS) 44 8. Operations Support Systems (OSS) Services 44 9. Poles, Ducts, Conduits and Xxxxxx-xx-Xxx 00 00. Telephone Numbers 51 11. Routing for Operator Services and Directory Assistance Traffic 51 12. Unauthorized Carrier Change Charges 52 13. Good Faith Performance 52 INTERCONNECTION ATTACHMENT. 53 1. General 53 2. Points of Interconnection and Trunk Types 53 3. Alternative Interconnection Arrangements 57 4. Initiating Interconnection 58 5. Transmission and Routing of Telephone Exchange Service Traffic 59

  • Proposing Integration Activities in the Planning Submission No integration activity described in section 6.3 may be proposed in a CAPS unless the Funder has consented, in writing, to its inclusion pursuant to the process set out in section 6.3(b).

  • Form 15 Filing Prior to January 30 of the first year in which the Depositor is able to do so under applicable law, the Depositor shall file a Form 15 relating to the automatic suspension of reporting in respect of the Trust Fund under the Exchange Act.

  • FINAL BILLING SUBMISSION Unless otherwise provided by the System Agency, Grantee shall submit a reimbursement or payment request as a final close-out invoice not later than forty-five (45) calendar days following the end of the term of the Contract. Reimbursement or payment requests received after the deadline may not be paid.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!