Reporting Points Sample Clauses

Reporting Points. (i) The acceptable points at which transactional data may be reported include– (A) Issuance of an invoice; or (B) Receipt of payment. (ii) The Contractor must determine whether to report transactional data on the basis of invoices issued or payments received.
Sample 1Sample 2Sample 3See All (4)
AutoNDA by SimpleDocs
Reporting Points. Reporting points are listed in each geographic area appendix. The charts enclosed depict these reporting points. • Pilots should report approaching reporting points. Position reports should be given when approaching a frequency changeover line on both frequencies. • Normal traffic will fly on the right side of rivers, valleys, mountain passes, shorelines, or waterways except where noted in a Specific Area Procedure or when confronted with weather, traffic or other conflicts. • If weather requires deviation from standard or Specific Area Traffic patterns, radio position calls should include this information and be transmitted on CTAF as conditions warrant. • Formation flying as contemplated by 14 CFR 91.111(c), only occurs when an aircraft is flown solely with reference to another aircraft and within 500 feet of the referenced aircraft (see FAA Order 8900.1, Volume 3, Chapter 6, Section 1, Subparagraph 3- 143A22). Formation flying is not authorized under this LOA. • Communications should be brief. Who, Where, Altitude, Intentions. • There should be no unnecessary conversations on CTAF. Unnecessary communications should only be conducted if an aircraft is capable of monitoring multiple frequencies and can continue to monitor the CTAF. • Companies should thoroughly train all pilots on the routes, altitudes, frequencies, and procedures explained in the Letter of Agreement and maintain a record of training. Management will disseminate any changes to the LOA in a timely fashion and should encourage pilots to report any deviations made or witnessed. • Aircraft inbound to the airport shall establish communications with the Juneau Air Traffic Control Tower at the appropriate VFR reporting points as listed on the Juneau Sectional (points are listed on the inset of the Juneau sectional chart). • Aircraft departing shall make a position report on the appropriate CTAF frequency prior to passing the inbound VFR reporting points. • During times of high traffic volume (summer season only), the tower may assign a separate frequency (120.70) for traffic operating north of the runway and east of Auke Mountain. Listen to the ATIS to determine if this frequency is in use. • General Guidelines for Juneau Airport: o Recommended Traffic Pattern Altitudes ▪ Helicopters: 500 feet MSL ▪ Fixed Wing 1000 feet MSL ▪ Large Turbine: 1500 feet MSL or Above o Aircraft are expected to follow routes and altitudes listed in the LOA unless a deviation is requested and approved by Juneau ATCT. ...
Sample 1
Reporting Points. For each month with no contract transactions, the Contractor must submit a confirmation as specified in paragraph (b)(3) of this clause.
Sample 1

Related to Reporting Points

  • Sales Reporting Requirements This is a requirement of the TIPS Contract and is non-negotiable. By submitting this proposal, Vendor certifies that Vendor will properly report all TIPS sales. With the exception of TIPS Automated Vendors, who have signed an exclusive agreement with TIPS regarding reporting, all TIPS Sales must be reported to TIPS by either: (1) Emailing the purchase order or similar purchase document (with Vendor’s Name, as known to TIPS, and the TIPS Contract Name and Number included) to TIPS at xxxxxx@xxxx-xxx.xxx with “Confirmation Only” in the subject line of the email within three business days of Vendor’s acceptance of the order, or; (2) Within 3 business days of the order being accepted by Vendor, Vendor must login to the TIPS Vendor Portal and successfully self-report all necessary sale information within the Vendor Portal and confirm that it shows up accurately on your current Vendor Portal statement. No other method of reporting is acceptable unless agreed to by the Parties in writing. Failure to report all sales pursuant to this provision may result in immediate cancellation of Vendor’s TIPS Contract(s) for cause at TIPS’ sole discretion.

  • Monthly Reporting Within twenty (20) calendar days following the end of each calendar month, Registry Operator shall deliver to ICANN reports in the format set forth in Specification 3 attached hereto (“Specification 3”).

  • CONTRACT SALES REPORTING Contractor shall report total contract sales quarterly to Enterprise Services, as set forth below.

  • 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.

  • Child Abuse Reporting Requirements A. Grantees shall comply with child abuse and neglect reporting requirements in Texas Family Code Chapter 261. This section is in addition to and does not supersede any other legal obligation of the Grantee to report child abuse. B. Grantee shall use the Texas Abuse Hotline Website located at xxxxx://xxx.xxxxxxxxxxxxxx.xxx/Login/Default.aspx as required by the System Agency. Grantee shall retain reporting documentation on site and make it available for inspection by the System Agency.

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