Reporting Points Sample Clauses
The "Reporting Points" clause defines specific moments or events during a contract or project when one party is required to provide updates or reports to the other party. Typically, these points may be tied to the completion of key milestones, the occurrence of certain events, or at regular intervals such as monthly or quarterly. For example, a contractor might be required to submit progress reports after each project phase or immediately following any incident affecting the work. This clause ensures that all parties remain informed about the status of the project, promoting transparency and enabling timely responses to issues as they arise.
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.
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. ...
Reporting Points. For each month with no contract transactions, the Contractor must submit a confirmation as specified in paragraph (b)(3) of this clause.