Instructions for Operators This agreement is intended to be provided to an Operator from a LEA. The Operator should fully read the agreement and is requested to complete the below areas of the agreement. Once the Operator accepts the terms of the agreement, the Operator should wet sign the agreement and return it to the LEA. Once the LEA signs the agreement, the LEA should provide a signed copy of the agreement to the Operator. Cover Page Box # 3 Official Name of Operator Cover Page Box # 4 Date Signed by Operator Recitals Box #5 Contract Title for Service Agreement Recitals Box #6 Date of Service Agreement Article 7 Boxes #7-10 Operator’s designated representative Signature Page Boxes #15-19 Authorized Operator’s representative signature Exhibit A Box #25 Description of services provided Exhibit B All Applicable Boxes Operator notates if data is collected to provide the described services. Defines the schedule of data required for the Operator to provide the services outlined in Exhibit A Exhibit D All Applicable Boxes (Optional Exhibit): Defines deletion or return of data expectations by LEA Exhibit E All Applicable Boxes (Optional Exhibit): Operator may, by signing the Form of General Offer of Privacy Terms (General Offer, attached as Exhibit E), be bound by the terms of this DPA to any other Subscribing LEA who signs the acceptance in said Exhibit. Exhibit F Boxes # 25-29 A list of all Subprocessors used by the Operator to perform functions pursuant to the Service Agreement, list security programs and measures, list Operator’s security measures
Reservations for Registry Operations The following ASCII labels must be withheld from registration or allocated to Registry Operator at All Levels for use in connection with the operation of the registry for the TLD: WWW, RDDS and WHOIS. The following ASCII label must be allocated to Registry Operator at All Levels for use in connection with the operation of the registry for the TLD: NIC. Registry Operator may activate WWW, RDDS and WHOIS in the DNS, but must activate NIC in the DNS, as necessary for the operation of the TLD. None of WWW, RDDS, WHOIS or NIC may be released or registered to any person (other than Registry Operator) or third party. Upon conclusion of Registry Operator’s designation as operator of the registry for the TLD all such withheld or allocated names shall be transferred as specified by ICANN. Registry Operator may self-allocate and renew such names without use of an ICANN accredited registrar, which will not be considered Transactions for purposes of Section 6.1 of the Agreement. Registry Operator may activate in the DNS at All Levels up to one hundred (100) names (plus their IDN variants, where applicable) necessary for the operation or the promotion of the TLD. Registry Operator must act as the Registered Name Holder of such names as that term is defined in the then-current ICANN Registrar Accreditation Agreement (RAA). These activations will be considered Transactions for purposes of Section 6.1 of the Agreement. Registry Operator must either (i) register such names through an ICANN-accredited registrar; or (ii) self-allocate such names and with respect to those names submit to and be responsible to ICANN for compliance with ICANN Consensus Policies and the obligations set forth in Subsections 3.7.7.1 through 3.7.7.12 of the then-current RAA (or any other replacement clause setting out the terms of the registration agreement between a registrar and a registered name holder). At Registry Operator’s discretion and in compliance with all other terms of this Agreement, such names may be released for registration to another person or entity. Registry Operator may withhold from registration or allocate to Registry Operator names (including their IDN variants, where applicable) at All Levels in accordance with Section 2.6 of the Agreement. Such names may not be activated in the DNS, but may be released for registration to another person or entity at Registry Operator’s discretion. Upon conclusion of Registry Operator’s designation as operator of the registry for the TLD, all such names that remain withheld from registration or allocated to Registry Operator shall be transferred as specified by ICANN. Upon ICANN’s request, Registry Operator shall provide a listing of all names withheld or allocated to Registry Operator pursuant to Section 2.6 of the Agreement. Registry Operator may self-allocate and renew such names without use of an ICANN accredited registrar, which will not be considered Transactions for purposes of Section 6.1 of the Agreement.
Operations Fire An “Operations Fire” is a fire caused by Purchaser’s Operations other than a Neg- ligent Fire.
Rent Rolls; Operating Histories The Seller has obtained a rent roll (the “Certified Rent Roll(s)”) other than with respect to hospitality properties certified by the related Mortgagor or the related guarantor(s) as accurate and complete in all material respects as of a date within 180 days of the date of origination of the related Mortgage Loan. The Seller has obtained operating histories (the “Certified Operating Histories”) with respect to each Mortgaged Property certified by the related Mortgagor or the related guarantor(s) as accurate and complete in all material respects as of a date within 180 days of the date of origination of the related Mortgage Loan. The Certified Operating Histories collectively report on operations for a period equal to (a) at least a continuous three-year period or (b) in the event the Mortgaged Property was owned, operated or constructed by the Mortgagor or an affiliate for less than three years then for such shorter period of time, it being understood that for mortgaged properties acquired with the proceeds of a Mortgage Loan, Certified Operating Histories may not have been available.
CERTIFICATION REGARDING USE OF CONTRACT FUNDS FOR LOBBYING This provision is applicable to all Federal-aid construction contracts and to all related subcontracts which exceed $100,000 (49 CFR 20).
1. The prospective participant certifies, by signing and submitting this bid or proposal, to the best of his or her knowledge and belief, that:
a. No Federal appropriated funds have been paid or will be paid, by or on behalf of the undersigned, to any person for influencing or attempting to influence an officer or employee of any Federal agency, a Member of Congress, an officer or employee of Congress, or an employee of a Member of Congress in connection with the awarding of any Federal contract, the making of any Federal grant, the making of any Federal loan, the entering into of any cooperative agreement, and the extension, continuation, renewal, amendment, or modification of any Federal contract, grant, loan, or cooperative agreement.
b. If any funds other than Federal appropriated funds have been paid or will be paid to any person for influencing or attempting to influence an officer or employee of any Federal agency, a Member of Congress, an officer or employee of Congress, or an employee of a Member of Congress in connection with this Federal contract, grant, loan, or cooperative agreement, the undersigned shall complete and submit Standard Form-LLL, "Disclosure Form to Report Lobbying," in accordance with its instructions.
2. This certification is a material representation of fact upon which reliance was placed when this transaction was made or entered into. Submission of this certification is a prerequisite for making or entering into this transaction imposed by 31 U.S.C. 1352. Any person who fails to file the required certification shall be subject to a civil penalty of not less than $10,000 and not more than $100,000 for each such failure.
3. The prospective participant also agrees by submitting its bid or proposal that the participant shall require that the language of this certification be included in all lower tier subcontracts, which exceed $100,000 and that all such recipients shall certify and disclose accordingly. This provision is applicable to all Federal-aid projects funded under the Appalachian Regional Development Act of 1965.
1. During the performance of this contract, the contractor undertaking to do work which is, or reasonably may be, done as on-site work, shall give preference to qualified persons who regularly reside in the labor area as designated by the DOL wherein the contract work is situated, or the subregion, or the Appalachian counties of the State wherein the contract work is situated, except:
a. To the extent that qualified persons regularly residing in the area are not available.
b. For the reasonable needs of the contractor to employ supervisory or specially experienced personnel necessary to assure an efficient execution of the contract work.
c. For the obligation of the contractor to offer employment to present or former employees as the result of a lawful collective bargaining contract, provided that the number of nonresident persons employed under this subparagraph (1c) shall not exceed 20 percent of the total number of employees employed by the contractor on the contract work, except as provided in subparagraph (4) below.
2. The contractor shall place a job order with the State Employment Service indicating (a) the classifications of the laborers, mechanics and other employees required to perform the contract work, (b) the number of employees required in each classification, (c) the date on which the participant estimates such employees will be required, and (d) any other pertinent information required by the State Employment Service to complete the job order form. The job order may be placed with the State Employment Service in writing or by telephone. If during the course of the contract work, the information submitted by the contractor in the original job order is substantially modified, the participant shall promptly notify the State Employment Service.
3. The contractor shall give full consideration to all qualified job applicants referred to him by the State Employment Service. The contractor is not required to grant employment to any job applicants who, in his opinion, are not qualified to perform the classification of work required.
4. If, within one week following the placing of a job order by the contractor with the State Employment Service, the State Employment Service is unable to refer any qualified job applicants to the contractor, or less than the number requested, the State Employment Service will forward a certificate to the contractor indicating the unavailability of applicants. Such certificate shall be made a part of the contractor's permanent project records. Upon receipt of this certificate, the contractor may employ persons who do not normally reside in the labor area to fill positions covered by the certificate, notwithstanding the provisions of subparagraph (1c) above.
5. The provisions of 23 CFR 633.207(e) allow the contracting agency to provide a contractual preference for the use of mineral resource materials native to the Appalachian region.
6. The contractor shall include the provisions of Sections 1 through 4 of this Attachment A in every subcontract for work which is, or reasonably may be, done as on-site work.
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).
Contractor Sales Reporting Vendor Management Fee Contractor Reports Master Contract Sales Reporting. Contractor shall report total Master Contract sales quarterly to Enterprise Services, as set forth below. Master Contract Sales Reporting System. Contractor shall report quarterly Master Contract sales in Enterprise Services’ Master Contract Sales Reporting System. Enterprise Services will provide Contractor with a login password and a vendor number. The password and vendor number will be provided to the Sales Reporting Representative(s) listed on Contractor’s Bidder Profile. Data. Each sales report must identify every authorized Purchaser by name as it is known to Enterprise Services and its total combined sales amount invoiced during the reporting period (i.e., sales of an entire agency or political subdivision, not its individual subsections). The “Miscellaneous” option may be used only with prior approval by Enterprise Services. Upon request, Contractor shall provide contact information for all authorized purchasers specified herein during the term of the Master Contract. If there are no Master Contract sales during the reporting period, Contractor must report zero sales. Due dates for Master Contract Sales Reporting. Quarterly Master Contract Sales Reports must be submitted electronically by the following deadlines for all sales invoiced during the applicable calendar quarter: March 31: April 30 June 30: July 31 September 30: October 31 December 31: January 31 Vendor Management Fee. Contractor shall pay to Enterprise Services a vendor management fee (“VMF”) of 1.50 percent on the purchase price for all Master Contract sales (the purchase price is the total invoice price less applicable sales tax). The sum owed by Contractor to Enterprise Services as a result of the VMF is calculated as follows: Amount owed to Enterprise Services = Total Master Contract sales invoiced (not including sales tax) x .0150. The VMF must be rolled into Contractor’s current pricing. The VMF must not be shown as a separate line item on any invoice unless specifically requested and approved by Enterprise Services. Enterprise Services will invoice Contractor quarterly based on Master Contract sales reported by Contractor. Contractors are not to remit payment until they receive an invoice from Enterprise Services. Contractor’s VMF payment to Enterprise Services must reference this Master Contract number, work request number (if applicable), the year and quarter for which the VMF is being remitted, and the Contractor’s name as set forth in this Master Contract, if not already included on the face of the check. Failure to accurately report total net sales, to submit a timely usage report, or remit timely payment of the VMF, may be cause for Master Contract termination or the exercise of other remedies provided by law. Without limiting any other available remedies, the Parties agree that Contractor’s failure to remit to Enterprise Services timely payment of the VMF shall obligate Contractor to pay to Enterprise Services, to offset the administrative and transaction costs incurred by the State to identify, process, and collect such sums. The sum of $200.00 or twenty-five percent (25%) of the outstanding amount, whichever is greater, or the maximum allowed by law, if less. Enterprise Services reserves the right, upon thirty (30) days advance written notice, to increase, reduce, or eliminate the VMF for subsequent purchases, and reserves the right to renegotiate Master Contract pricing with Contractor when any subsequent adjustment of the VMF might justify a change in pricing. Annual Master Contract Sales Report. Upon request, Contractor shall provide to Enterprise Services a detailed annual Master Contract sales report. Such report shall include, at a minimum: Product description, part number or other Product identifier, per unit quantities sold, and Master Contract price. This report must be provided in an electronic format that can be read by compatible with MS Excel. Small Business Inclusion. Upon Request by Enterprise Services, Contractor shall provide, within thirty (30) days, an Affidavit of Amounts Paid. Such Affidavit of Amounts Paid either shall state, if applicable, that Contractor still maintains its MWBE certification or state that its subcontractor(s) still maintain(s) its/their MWBE certification(s) and specify the amounts paid to each certified MWBE subcontractor under this Master Contract. Contractor shall maintain records supporting the Affidavit of Amounts Paid in accordance with this Master Contract’s records retention requirements.
LIST OF SUB-PROCESSORS The controller has authorised the use of the following sub-processors:
PAYMENT OF SUBCONTRACTORS Contractor shall pay any of its subcontractors not later than seven (7) days after receipt of any progress payment, unless otherwise agreed to in writing, the respective amounts allowed Contractor on account of the work performed by subcontractor(s), to the extent of each subcontractor’s interest therein, except as otherwise provided in Business and Professions Code Section 7108.5.
Production Report and Lease Operating Statements Within 60 days after the end of each fiscal quarter, a report setting forth, for each calendar month during the then current fiscal year to date, the volume of production and sales attributable to production (and the prices at which such sales were made and the revenues derived from such sales) for each such calendar month from the Oil and Gas Properties, and setting forth the related ad valorem, severance and production taxes and lease operating expenses attributable thereto and incurred for each such calendar month.
