We use cookies on our site to analyze traffic, enhance your experience, and provide you with tailored content.

For more information visit our privacy policy.

Job Service Registrants Sample Clauses

Job Service Registrants. ADARE Project researcher acquisition of or access to Job Service registrant information is important for several reasons: • Job Service registrant information can be used for comparison group purposes to test the sensitivity of WIA net impact estimates to the defined comparison group. • Traditional Job Service activities are being integrated into One-Stop locations and delivery of services at different speeds and completeness among the ADARE Project states. Coverage of Job Service activities and client flows is important to cast the researcher’s descriptive and analytical net as far as possible to include partner services and client mixes. • New Job Service performance indicator reporting has started so employment and earnings statistical series will be available for comparative use. The minimum core of needed items includes: • Job Service Registrant social security number. • Registration date, so the time sequence of various service exposures can be defined. Further inquiry within each of the ADARE Project states needs to occur before deciding on a common definition of Job Service action items to be included in each researcher’s request for Job Service administrative records. Job referral and results documentation is of highest priority, but definitions and completeness are expected to be uneven among the ADARE Project states.

Related to Job Service Registrants

  • Registration Data Directory Services Until ICANN requires a different protocol, Registry Operator will operate a WHOIS service available via port 43 in accordance with XXX 0000, and a web-­‐based Directory Service at <whois.nic.TLD> providing free public query-­‐based access to at least the following elements in the following format. ICANN reserves the right to specify alternative formats and protocols, and upon such specification, the Registry Operator will implement such alternative specification as soon as reasonably practicable. Registry Operator shall implement a new standard supporting access to domain name registration data (SAC 051) no later than one hundred thirty-­‐five (135) days after it is requested by ICANN if: 1) the IETF produces a standard (i.e., it is published, at least, as a Proposed Standard RFC as specified in RFC 2026); and 2) its implementation is commercially reasonable in the context of the overall operation of the registry. 1.1. The format of responses shall follow a semi-­‐free text format outline below, followed by a blank line and a legal disclaimer specifying the rights of Registry Operator, and of the user querying the database. 1.2. Each data object shall be represented as a set of key/value pairs, with lines beginning with keys, followed by a colon and a space as delimiters, followed by the value. 1.3. For fields where more than one value exists, multiple key/value pairs with the same key shall be allowed (for example to list multiple name servers). The first key/value pair after a blank line should be considered the start of a new record, and should be considered as identifying that record, and is used to group data, such as hostnames and IP addresses, or a domain name and registrant information, together. 1.4. The fields specified below set forth the minimum output requirements. Registry Operator may output data fields in addition to those specified below, subject to approval by ICANN, which approval shall not be unreasonably withheld.

  • Periodic Access to Thin Registration Data In order to verify and ensure the operational stability of Registry Services as well as to facilitate compliance checks on accredited registrars, Registry Operator will provide ICANN on a weekly basis (the day to be designated by ICANN) with up-­‐to-­‐date Registration Data as specified below. Data will include data committed as of 00:00:00 UTC on the day previous to the one designated for retrieval by ICANN.

  • Description of Administration Services on a Continuous Basis (a) PNC will perform the following administration services with respect to each Portfolio: (i) Prepare quarterly broker security transactions summaries; (ii) Prepare monthly security transaction listings; (iii) Supply, in the form requested, various customary Portfolio and Fund statistical data on an ongoing basis; (iv) Prepare and ensure the filing of the Funds’ annual and semi-annual reports with the SEC on Forms N-SAR and N-CSR and the Fund’s quarterly reports with the SEC on Form N-Q; (v) If mutually agreed by PNC and VP Distributors in writing, prepare (or assist in the preparation of) and ensure the filing of (or coordinate filing of, as may be mutually agreed) such other reports with the SEC as may be required by the SEC and that would be primarily fulfilled using books and records maintained by PNC under the terms of this Agreement; (vi) Assist in the preparation of registration statements and other filings relating to the registration of Shares; (vii) Monitor each Portfolio’s status as a regulated investment company under Sub-chapter M of the Internal Revenue Code of 1986, as amended (“Sub-Chapter M”); (viii) Coordinate contractual relationships and communications between the Funds and their contractual service providers; (ix) Prepare expense budgets, accrual review and expense reports as needed; (x) Provide read-only on-line access to accounting system as requested; (xi) Provide electronic transmissions of holdings, transactions, security master, general ledger, NAV, security pricing data, and cash activity as specified; (xii) Coordinate printing and mailing of annual and semi-annual financial statements; (xiii) Prepare reports for Fund Boards and attend Board meetings when and as requested; (xiv) Prepare, execute, and file each Portfolio’s Federal and state tax returns, including closed funds, and appropriate extensions after review and approval by the Fund’s independent registered public accounting firm; (xv) Prepare, execute, and file each Portfolio’s federal excise returns (Form 8613) after review and approval by the Fund’s independent registered public accounting firm; (xvi) Prepare annual tax provisions and financial tax disclosures; (xvii) Prepare tax cost for semi-annual and Form N-Q filings updated for current year-to-date wash sales and prior year known Schedule M adjustments; (xviii) Prepare dividend calculations, including accompanying analysis and earnings summary in accordance with applicable policy (as such policy is provided in writing by VP Distributors to PNC), and maintain dividend history; (xix) Prepare required disclosures for shareholder reporting, including Form 1099-DIV reporting and supporting materials such as QDI, DRD, income from U.S. Obligations, income from State obligations, income from AMT obligations, tax-exempt income, and Florida intangibles; (xx) Monitor and propose procedures as needed for tax considerations in the following areas: corporate actions, consent income, bad debt/restructurings, new instruments, premium amortization, and legislation and industry developments on an ad hoc basis; and (xxi) Prepare and deliver, to the extent available to PNC, survey information when and in the form requested.

  • FORMAT AND CONTENT FOR REGISTRY OPERATOR MONTHLY REPORTING Registry Operator shall provide one set of monthly reports per gTLD, using the API described in draft-­‐xxxxxx-­‐icann-­‐registry-­‐interfaces, see Specification 2, Part A, Section 9, reference 5, with the following content. ICANN may request in the future that the reports be delivered by other means and using other formats. ICANN will use reasonable commercial efforts to preserve the confidentiality of the information reported until three (3) months after the end of the month to which the reports relate. Unless set forth in this Specification 3, any reference to a specific time refers to Coordinated Universal Time (UTC). Monthly reports shall consist of data that reflects the state of the registry at the end of the month (UTC).

  • The Web Services E-Verify Employer Agent agrees to, consistent with applicable laws, regulations, and policies, commit sufficient personnel and resources to meet the requirements of this MOU.

  • Bulk Registration Data Access to Icann Periodic Access to Thin Registration Data. In order to verify and ensure the operational stability of Registry Services as well as to facilitate compliance checks on accredited registrars, Registry Operator will provide ICANN on a weekly basis (the day to be designated by ICANN) with up-to-date Registration Data as specified below. Data will include data committed as of 00:00:00 UTC on the day previous to the one designated for retrieval by ICANN.

  • Notification of Employees A. Written notice of layoff shall be given to an employee or sent by mail to the last known mailing address at least fourteen (14) calendar days prior to the effective date of the layoff. Notices of layoff shall be served on employees personally at work whenever practicable. B. It is the intent of the parties that the number of layoff notices initially issued shall be limited to the number of positions by which the work force is intended to be reduced. Additional notices shall be issued as other employees become subject to layoff as a result of employees exercising reduction rights under Section 5. C. The notice of layoff shall include the reason for the layoff, the proposed effective date of the layoff, the employee's hire date, the employee's layoff points, a list of classes in the employee's occupational series within the layoff unit, the employee's rights under Sections 5. and 6. and the right of the employee to advise the County of any objection to the content of the layoff notice prior to the proposed effective date of the layoff.

  • CONTRACTOR CUSTOMER SERVICE REPRESENTATIVE Contractor shall designate a customer service representative (and inform Enterprise Services of the same) who shall be responsible for addressing Purchaser issues pertaining to this Contract.

  • Our Service The services that you have selected and the charges for those services are confirmed in Section 9 - Your Consent at the end of this agreement. We agree to provide the services selected and you agree to pay us for those services. Any advice or recommendation that we offer to you, will only be given after we have assessed your needs and considered your financial objectives and attitude to any risks that may be involved. We will also take into account any restrictions that you wish to place on the type of products you would be willing to consider.

  • Log and Load Reporting Service This contract may at the States discretion, require the services of a State approved third party log and load reporting service. Purchaser shall ensure log volume measurement, weight, or scale and weight data for each load is received by the log and load reporting service within 1 business day of logs being measured or weighed. If during the term of this contract, the State discontinues use of the Log and Load Reporting Service, the State will notify the Purchaser in writing, and will approve an alternative log and load reporting process. Determination of volume and grade of any forest products shall be conducted by a state approved third party scaling organization and in accordance with the Westside log scaling and grading rules and Xxxxxxxx Volume Table, revised July 1, 1972, contained in the Northwest Log Rules Eastside and Westside Log Scaling Handbook (developed and produced by the Northwest Log Rules Advisory Group) and in effect on the date of confirmation of this contract. Special scaling specifications shall be noted on the State’s Brand Designation form which is hereby incorporated to this contract by reference. Forest Product measurement and weighing facilities required by this contract must be approved by the State. Forest products sold under the contract which require log scaling shall be scaled, measured, or counted by a State approved third party log scaling organization. Forest products sold under the contract which require weighing shall be weighed at a location that meets Washington State Department of Agriculture approval. Prior to forest products being hauled, the Contract Administrator must authorize in writing the use of State approved measurement and/or weighing facilities that are at or en-route to final destinations. Forest products from this sale shall be measured or weighed at facilities, which are currently approved for use by the State and are currently authorized for this sale. The State reserves the right to verify load volume and weights with State employees or contractors at the State's own expense. The State reserves the right to revoke the authorization of previously approved measurement locations.