Local Industry Fund Sample Clauses

Local Industry Fund. The provision contained in Article 8, Section 12(b) of the Standard Form of Union Agreement is voided by agreement of the parties. The Employer shall pay to the SMACNA, Northern Illinois Industry Fund, a Fund administered by a Board of Trustees in accordance with the terms of a Trust Document, the hourly contribution rate established by the Industry Fund Trustees, for each hour and part of an hour worked, for each Employee covered by this Agreement, according to the payment procedures outlined in Addendum 12. Sections 17 and 24 of this Addenda constitute one inseparable and indivisible collective bar- gaining agreement in this contract. The forced removal of either fund will result in the removal of the other fund.
Sample 1Sample 2
AutoNDA by SimpleDocs
Local Industry Fund. The Employer shall pay to Capital District SMACNA, forty-seven cents ($0.47) per hour for each hour worked on or after the effective date of this Agreement, by all employees of the Employer covered by this Agreement. Payment shall be made monthly on or before the 20th day of the succeeding month. The Capital District SMACNA chapter will reimburse the Local 83 JATC the fee required for members and/or apprentices welding certifications and upgrades, not to exceed $750 per year. Out of town contractors, (not signatory) to LU 83 shall be responsible for the welding certifications and/or certification updates for the work being performed in LU 83’s jurisdiction. Section 13A The Local Industry Fund shall furnish to the Business Manager of Local #83 annually, a written report describing in reasonable detail the nature of the activities in which it is engaged or which it supports directly or indirectly with any of its funds.
Sample 1
Local Industry Fund. Contributions to the Local Industry Fund by the employers for all employees, journeymen apprentices, shall be at the rate of (per Item 2) per hour for all hours worked.
Sample 1
Local Industry Fund. 8) Sheet Metal Occupational Health Institute Trust (SMOHIT)
Sample 1
Local Industry Fund 
Sample 1

Related to Local Industry Fund

  • INDUSTRY FUND a. The Employer shall contribute and remit such contributions to the Union’s Industry Fund as specified in Schedule “A” for each hour worked by each employee covered by this Agreement.

  • Industry Standards Supplier will implement appropriate technical and organizational security measures that comply with Industry Standards in all applicable goods, services, equipment, software systems and platforms that Supplier uses to access, process and/or store Accenture Data. “Industry Standards” means security measures that are commercially reasonable in the information technology industry and that are designed to ensure the security, integrity, and confidentiality of Accenture Data, and to protect against Security Incidents.

  • Registry Functions Activity Report This report shall be compiled in a comma separated-value formatted file as specified in RFC 4180. The file shall be named “gTLD-activity-yyyymm.csv”, where “gTLD” is the gTLD name; in case of an IDN-TLD, the A-label shall be used; “yyyymm” is the year and month being reported. The file shall contain the following fields: Field # Field Name Description 01 operational-registrars number of operational registrars at the end of the reporting period 02 ramp-up-registrars number of registrars that have received a password for access to OT&E at the end of the reporting period 03 pre-ramp-up-registrars number of registrars that have requested access, but have not yet entered the ramp-up period at the end of the reporting period 06 web-whois-queries number of Web-based Whois queries responded during the reporting period, not including searchable Whois 09 dns-udp-queries-responded number of DNS queries received over UDP transport that were responded during the reporting period 10 dns-tcp-queries-received number of DNS queries received over TCP transport during the reporting period 11 dns-tcp-queries-responded number of DNS queries received over TCP transport that were responded during the reporting period 12 srs-dom-check number of SRS (EPP and any other interface) domain name “check” requests responded during the reporting period 13 srs-dom-create number of SRS (EPP and any other interface) domain name “create” requests responded during the reporting period 14 srs-dom-delete number of SRS (EPP and any other interface) domain name “delete” requests responded during the reporting period 15 srs-dom-info number of SRS (EPP and any other interface) domain name “info” requests responded during the reporting period 16 srs-dom-renew number of SRS (EPP and any other interface) domain name “renew” requests responded during the reporting period 17 srs-dom-rgp-restore-report number of SRS (EPP and any other interface) domain name RGP “restore” requests delivering a restore report responded during the reporting period 18 srs-dom-rgp-restore-request number of SRS (EPP and any other interface) domain name RGP “restore” requests responded during the reporting period 19 srs-dom-transfer-approve number of SRS (EPP and any other interface) domain name “transfer” requests to approve transfers responded during the reporting period 20 srs-dom-transfer-cancel number of SRS (EPP and any other interface) domain name “transfer” requests to cancel transfers responded during the reporting period 21 srs-dom-transfer-query number of SRS (EPP and any other interface) domain name “transfer” requests to query about a transfer responded during the reporting period 22 srs-dom-transfer-reject number of SRS (EPP and any other interface) domain name “transfer” requests to reject transfers responded during the reporting period 23 srs-dom-transfer-request number of SRS (EPP and any other interface) domain name “transfer” requests to request transfers responded during the reporting period 24 srs-dom-update number of SRS (EPP and any other interface) domain name “update” requests (not including RGP restore requests) responded during the reporting period 25 srs-host-check number of SRS (EPP and any other interface) host “check” requests responded during the reporting period 26 srs-host-create number of SRS (EPP and any other interface) host “create” requests responded during the reporting period 27 srs-host-delete number of SRS (EPP and any other interface) host “delete” requests responded during the reporting period 28 srs-host-info number of SRS (EPP and any other interface) host “info” requests responded during the reporting period 29 srs-host-update number of SRS (EPP and any other interface) host “update” requests responded during the reporting period 30 srs-cont-check number of SRS (EPP and any other interface) contact “check” requests responded during the reporting period 32 srs-cont-delete number of SRS (EPP and any other interface) contact “delete” requests responded during the reporting period 33 srs-cont-info number of SRS (EPP and any other interface) contact “info” requests responded during the reporting period 34 srs-cont-transfer-approve number of SRS (EPP and any other interface) contact “transfer” requests to approve transfers responded during the reporting period 35 srs-cont-transfer-cancel number of SRS (EPP and any other interface) contact “transfer” requests to cancel transfers responded during the reporting period 36 srs-cont-transfer-query number of SRS (EPP and any other interface) contact “transfer” requests to query about a transfer responded during the reporting period 37 srs-cont-transfer-reject number of SRS (EPP and any other interface) contact “transfer” requests to reject transfers responded during the reporting period 38 srs-cont-transfer-request number of SRS (EPP and any other interface) contact “transfer” requests to request transfers responded during the reporting period 39 srs-cont-update number of SRS (EPP and any other interface) contact “update” requests responded during the reporting period The first line shall include the field names exactly as described in the table above as a “header line” as described in section 2 of RFC 4180. No other lines besides the ones described above shall be included. Line breaks shall be <U+000D, U+000A> as described in RFC 4180. For gTLDs that are part of a single-instance Shared Registry System, the Registry Functions Activity Report may include the total contact or host transactions for all the gTLDs in the system. REGISTRATION DATA PUBLICATION SERVICES

  • Statewide HUB Program Statewide Procurement Division Note: In order for State agencies and institutions of higher education (universities) to be credited for utilizing this business as a HUB, they must award payment under the Certificate/VID Number identified above. Agencies, universities and prime contractors are encouraged to verify the company’s HUB certification prior to issuing a notice of award by accessing the Internet (xxxxx://xxxxx.xxx.xxxxx.xx.xx/tpasscmblsearch/index.jsp) or by contacting the HUB Program at 000-000-0000 or toll-free in Texas at 0-000-000-0000.

  • Good Industry Practice 11.1.4 all applicable Standards; and

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