Assemble Non-Farebox Revenue Data Sample Clauses

Assemble Non-Farebox Revenue Data. The Contractor shall review for completeness and accuracy the information provided by MTA regarding the non-farebox revenue data: • City general fund revenues • City parking revenuesSales tax revenue • Non-farebox operating revenues: parking, advertising, concessions, school contracts, real estate operations • State/Regional Funding • 5307 Urbanized area formula grants • 5309 Fixed Guideway Modernization grants The Contractor shall review near-term projections of the sales tax applied by the City and SFCTA. The Contractor shall develop a long-range sales tax revenue model that is consistent with the macroeconomic forecasts of inflation and interest rates that shall be applied in the financial analysis. The Contractor shall review potential funding sources based on current work with SPUR to develop a list of potential funding sources for enhancing MTA’s revenue. This information shall form the basis of this task, which shall identify a wide range of potential funding sources, the amount of revenue that could be generated from each source, the likelihood and process for receiving funds, and the degree of support for funding. The Contractor shall summarize the data and manner in which it shall be applied in the analysis in a technical memorandum and shall provide a copy of the memorandum in electronic form to the MTA Project Manager and Controller’s Project Manager.
AutoNDA by SimpleDocs

Related to Assemble Non-Farebox Revenue Data

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

  • Gross Revenue 16.1.1 For the purposes of this PPP Agreement and its Schedules, Gross Revenue shall be defined as:

  • 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: For Calendar Quarter Ending Master Contract Sales Report Due 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 0.74 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 .0074. 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.

  • The OCN, From XXX, and Invoice Number will control the invoice sequencing The From XXX will be used to identify to <<customer_name>> which BellSouth XXX is sending the message. BellSouth and <<customer_name>> will use the invoice sequencing to control data exchange. BellSouth will be notified of sequence failures identified by <<customer_name>> and resend the data as appropriate. THE DATA WILL BE PACKED USING ATIS EMI RECORDS.

  • Trunk Group Architecture and Traffic Routing The Parties shall jointly engineer and configure Local/IntraLATA Trunks over the physical Interconnection arrangements as follows:

  • Originating Switched Access Detail Usage Data A category 1101XX record as defined in the EMI Telcordia Practice BR-010-200- 010.

  • Revenue Metering The Connecting Transmission Owner’s revenue metering will be located on the generator side of the 115kV breaker at the Xxxxx Solar Collector Substation and will consist of: • three (3) combination current/voltage transformer (“CT/VT”) units (manufacturer and model ABB/Xxxxxxx KXM-550, GE Grid Solutions KOTEF 000.XX, or other equivalent specified by Connecting Transmission Owner); and • one (1) revenue meter. The ratios of the CTs and VTs will be provided by Connecting Transmission Owner upon its review of the Interconnection Customer’s design documents. (Note: Connecting Transmission Owner’s revenue metering CTs and VTs cannot be used to feed the Interconnection Customer’s check meter.) SERVICE AGREEMENT NO. 2556

  • Terminating Switched Access Detail Usage Data A category 1101XX record as defined in the EMI Telcordia Practice BR-010-200- 010.

  • Net Metering If you generate electricity from a renewable generating facility to offset your electricity consumption and/or use net metering at any time during the term of this Agreement, you must notify Starion.

  • SERVICE MONITORING, ANALYSES AND ORACLE SOFTWARE 11.1 We continuously monitor the Services to facilitate Oracle’s operation of the Services; to help resolve Your service requests; to detect and address threats to the functionality, security, integrity, and availability of the Services as well as any content, data, or applications in the Services; and to detect and address illegal acts or violations of the Acceptable Use Policy. Oracle monitoring tools do not collect or store any of Your Content residing in the Services, except as needed for such purposes. Oracle does not monitor, and does not address issues with, non-Oracle software provided by You or any of Your Users that is stored in, or run on or through, the Services. Information collected by Oracle monitoring tools (excluding Your Content) may also be used to assist in managing Oracle’s product and service portfolio, to help Oracle address deficiencies in its product and service offerings, and for license management purposes.

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