Originating Switched Access Detail Usage Data A category 1101XX record as defined in the EMI Telcordia Practice BR-010-200- 010.
Reporting on Utilization of Subject Inventions 1. The Performer agrees to submit, during the term of the Agreement, an annual report on the utilization of a subject invention or on efforts at obtaining such utilization that are being made by the Performer or its licensees or assignees. Such reports shall include information regarding the status of development, date of first commercial sale or use, gross royalties received by the Performer, and such other data and information as the agency may reasonably specify. The Performer also agrees to provide additional reports as may be requested by DARPA in connection with any march-in proceedings undertaken by DARPA in accordance with Paragraph I of this Article. DARPA agrees it shall not disclose such information to persons outside the Government without permission of the Performer, unless required by law.
2. All required reporting shall be accomplished, to the extent possible, using the i-Edison reporting website: xxxxx://x-xxxxxx.xxxx.xxx.xxx/iEdison/. To the extent any such reporting cannot be carried out by use of i-Edison, reports and communications shall be submitted to the Agreements Officer and Administrative Agreements Officer.
PREVAILING WAGE RATES - PUBLIC WORKS AND BUILDING SERVICES CONTRACTS If any portion of work being Bid is subject to the prevailing wage rate provisions of the Labor Law, the following shall apply:
Loop Testing/Trouble Reporting 2.1.6.1 Telepak Networks will be responsible for testing and isolating troubles on the Loops. Telepak Networks must test and isolate trouble to the BellSouth portion of a designed/non-designed unbundled Loop (e.g., UVL-SL2, UCL-D, UVL-SL1, UCL-ND, etc.) before reporting repair to the UNE Customer Wholesale Interconnection Network Services (CWINS) Center. Upon request from BellSouth at the time of the trouble report, Telepak Networks will be required to provide the results of the Telepak Networks test which indicate a problem on the BellSouth provided Loop.
2.1.6.2 Once Telepak Networks has isolated a trouble to the BellSouth provided Loop, and had issued a trouble report to BellSouth on the Loop, BellSouth will take the actions necessary to repair the Loop if a trouble actually exists. BellSouth will repair these Loops in the same time frames that BellSouth repairs similarly situated Loops to its End Users.
2.1.6.3 If Telepak Networks reports a trouble on a non-designed or designed Loop and no trouble actually exists, BellSouth will charge Telepak Networks for any dispatching and testing (both inside and outside the CO) required by BellSouth in order to confirm the Loop’s working status.
2.1.6.4 In the event BellSouth must dispatch to the end-user’s location more than once due to incorrect or incomplete information provided by Telepak Networks (e.g., incomplete address, incorrect contact name/number, etc.), BellSouth will xxxx Xxxxxxx Networks for each additional dispatch required to repair the circuit due to the incorrect/incomplete information provided. BellSouth will assess the applicable Trouble Determination rates from BellSouth’s FCC or state tariffs.
System Upgrade Facilities and System Deliverability Upgrades Connecting Transmission Owner shall design, procure, construct, install, and own the System Upgrade Facilities and System Deliverability Upgrades described in Appendix A hereto. The responsibility of the Developer for costs related to System Upgrade Facilities and System Deliverability Upgrades shall be determined in accordance with the provisions of Attachment S to the NYISO OATT.
Monthly Data Download Not later than fifteen (15) days after the end of each month, beginning with the month in which the Commencement Date occurs and ending with the Final Shared-Loss Recovery Month, Assuming Bank shall provide Receiver:
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).
Trunk Group Architecture and Traffic Routing 5.2.1 The Parties shall jointly establish Access Toll Connecting Trunks between CLEC and CBT by which they will jointly provide Tandem-transported Switched Exchange Access Services to Interexchange Carriers to enable such Interexchange Carriers to originate and terminate traffic from and to CLEC's Customers.
5.2.2 Access Toll Connecting Trunks shall be used solely for the transmission and routing of Exchange Access and non-translated Toll Free traffic (e.g., 800/888) to allow CLEC’s Customers to connect to or be connected to the interexchange trunks of any Interexchange Carrier that is connected to the CBT access Tandem.
5.2.3 The Access Toll Connecting Trunks shall be one-way or two-way trunks, as mutually agreed, connecting an End Office Switch that CLEC utilizes to provide Telephone Exchange Service and Switched Exchange Access Service in the given LATA to an access Tandem Switch CBT utilizes to provide Exchange Access in the LATA.
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.
Monthly MWBE Contractor Compliance Report A. In accordance with 5 NYCRR § 142.10, Contractor is required to report Monthly MWBE Contractor Compliance to OGS during the term of the Contract for the preceding month’s activity, documenting progress made towards achievement of the Contract MWBE goals. OGS requests that all Contractors use the New York State Contract System (“NYSCS”) to report subcontractor and supplier payments made by Contractor to MWBEs performing work under the Contract. The NYSCS may be accessed at xxxxx://xx.xxxxxxxxxxxxxx.xxx/. This is a New York State- based system that all State agencies and authorities will be implementing to ensure uniform contract compliance reporting throughout New York State.
B. When a Contractor receives a payment from a State agency, it is the Contractor’s responsibility to pay its subcontractors and suppliers in a timely manner. On or after the first day of each month, the Contractor will receive an email or fax notification (“audit notice”) indicating that a representative of its company needs to log-in to the NYSCS to report the company’s MWBE subcontractor and supplier payments for the preceding month. The Contractor must also report when no payments have been made to a subcontractor or supplier in a particular month with entry of a zero dollar value in the NYSCS. Once subcontractor and supplier payments have been entered into the NYSCS, the subcontractor(s) and supplier(s) will receive an email or fax notification advising them to log into the NYSCS to confirm that they actually received the reported payments from the Contractor. It is the Contractor’s responsibility to educate its MWBE subcontractors and suppliers about the NYSCS and the need to confirm payments made to them in the NYSCS.
C. To assist in the use of the NYSCS, OGS recommends that all Contractors and MWBE subcontractors and suppliers sign up for the following two webinar trainings offered through the NYSCS: “Introduction to the System – Vendor training” and “Contract Compliance Reporting - Vendor Training” to become familiar with the NYSCS. To view the training schedule and to register visit: xxxxx://xx.xxxxxxxxxxxxxx.xxx/events.asp
D. As soon as possible after the Contract is approved, Contractor should visit xxxxx://xx.xxxxxxxxxxxxxx.xxx and click on “Account Lookup” to identify the Contractor’s account by company name. Contact information should be reviewed and updated if necessary by choosing “Change Info.” It is important that the staff member who is responsible for reporting payment information for the Contractor be listed as a user in the NYSCS. Users who are not already listed may be added through “Request New User.” When identifying the person responsible, please add “- MWBE Contact” after his or her last name (i.e., Xxxx Xxx – MWBE Contact) to ensure that the correct person receives audit notices from the NYSCS. NYSCS Technical Support should be contacted for any technical support questions by clicking on the links for “Contact Us & Support” then “Technical Support” on the NYSCS website.
E. If Contractor is unable to report MWBE Contractor Compliance via the NYSCS, Contractor must submit a Monthly MWBE Contractor Compliance Report on Form MWBE 102 to OGS, by the 10th day of each month during the term of the Contract, for the preceding month’s activity to: OGS MWBE Office, 00xx Xxxxx Xxxxxxx Xxxxx, Xxxxxx Xxxxx Xxxxx, Xxxxxx, XX 00000. Phone: 000-000-0000; Fax: 000-000-0000.
F. It is the Contractor’s responsibility to report subcontractor and supplier payments. Failure to respond to payment audits in a timely fashion through the NYSCS, or by paper to OGS, may jeopardize future payments pursuant to the MWBE liquidated damages provisions in clause IX below.
