REVIEW OF WEB-BASED REPORTING SYSTEM Sample Clauses

REVIEW OF WEB-BASED REPORTING SYSTEM. 9.1 The Secretariat presented AC6 Doc 16 Rev1, summarising progress with the development of a web-based system for Implementation Reports. Following discussions at AC5, the reporting template (see AC5 Doc 16) was incorporated into the ACAP database as two independent sections – an Advisory Committee Report, addressing reporting requirements arising from the Agreement‟s Action Plan, to be completed preceding each Advisory Committee Meeting; and a MoP Report, for Parties‟ reports on their progress in implementing the Agreement, to be completed triennially prior to the AC preceding a Meeting of Parties. National Contact Points and Observers were provided with login details and invited to complete both reports online.
Sample 1
AutoNDA by SimpleDocs
REVIEW OF WEB-BASED REPORTING SYSTEM. 10. Report on the Implementation of the Agreement
Sample 1

Related to REVIEW OF WEB-BASED REPORTING SYSTEM

  • Loop Testing/Trouble Reporting 2.1.6.1 Think 12 will be responsible for testing and isolating troubles on the Loops. Think 12 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, Think 12 will be required to provide the results of the Think 12 test which indicate a problem on the BellSouth provided Loop.

  • Project Monitoring Reporting Evaluation A. The Project Implementing Entity shall monitor and evaluate the progress of its activities under the Project and prepare Project Reports in accordance with the provisions of Section 5.08(b) of the General Conditions and on the basis of indicators agreed with the Bank. Each such report shall cover the period of one

  • Accounting System Requirement The Contractor shall maintain an adequate system of accounting and internal controls that meets Generally Accepted Accounting Principles or “GAAP.”

  • Registry Performance Specifications Registry Performance Specifications for operation of the TLD will be as set forth in Specification 10 attached hereto (“Specification 10”). Registry Operator shall comply with such Performance Specifications and, for a period of at least one (1) year, shall keep technical and operational records sufficient to evidence compliance with such specifications for each calendar year during the Term.

  • Requirement to Utilize HUB Compliance Reporting System Pursuant to Texas Administrative Code, Title 34, Part 1, Sections 20.285(f) and 20.287(b), TFC administers monthly administration HSP-PAR compliance monitoring through its HUB Compliance Reporting System commonly known as B2G. PSP and PSP’s subcontractors/subconsultants shall submit required PAR information into the B2G system. Any delay in the timely submission of PAR information into the B2G system will be treated as an invoicing error subject to dispute under Texas Government Code Section 2251.042.

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

  • Quarterly Contractor Performance Reporting Customers shall complete a Contractor Performance Survey (Exhibit I) for each Contractor on a Quarterly basis. Customers will electronically submit the completed Contractor Performance Survey(s) to the Department Contract Manager no later than the due date indicated in Contract Exhibit D, Section 17, Additional Special Contract Conditions. The completed Contractor Performance Survey(s) will be used by the Department as a performance-reporting tool to measure the performance of Contractors. The Department reserves the right to modify the Contractor Performance Survey document and introduce additional performance-reporting tools as they are developed, including online tools (e.g. tools within MyFloridaMarketPlace or on the Department's website).

  • Testing/Trouble Reporting 1.15.1 TWTC will be responsible for testing and isolating troubles on Network Elements. TWTC must test and isolate trouble to the AT&T network before reporting the trouble to the Network Elements Customer Wholesale Interconnection Network Services (CWINS) Center. Upon request from AT&T at the time of the trouble report, TWTC will be required to provide the results of the TWTC test which indicate a problem on the AT&T network. Version: 4Q06 Standard ICA 11/30/06

  • Switching System Hierarchy and Trunking Requirements For purposes of routing ECI traffic to Verizon, the subtending arrangements between Verizon Tandem Switches and Verizon End Office Switches shall be the same as the Tandem/End Office subtending arrangements Verizon maintains for the routing of its own or other carriers’ traffic (i.e., traffic will be routed to the appropriate Verizon Tandem subtended by the terminating End Office serving the Verizon Customer). For purposes of routing Verizon traffic to ECI, the subtending arrangements between ECI Tandem Switches and ECI End Office Switches shall be the same as the Tandem/End Office subtending arrangements that ECI maintains for the routing of its own or other carriers’ traffic.

  • COVID-19 Protocols Contractor will abide by all applicable COVID-19 protocols set forth in the District’s Reopening and COVID-19 Mitigation Plan and the safety guidelines for COVID-19 prevention established by the California Department of Public Health and the Ventura County Department of Public Health.

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