REVIEW OF WEB-BASED REPORTING SYSTEM Clause Samples

REVIEW OF WEB-BASED REPORTING SYSTEM. Report on the Implementation of the Agreement
View Source
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. 9.2 In the course of completing their reports, respondents identified a number of issues which were presented for consideration at AC6. The AC reviewed the issues identified and endorsed some modifications to the reporting format and process: i. Timing of request for report completion AC6 agreed that in future, three months be provided for Parties to complete their implementation reports, i.e. requests will be made six months prior to the deadline for submission of AC docs. ii. Antarctic and disputed sites AC6 expressed a preference for all Antarctic sites (south of 60°) to be included in each Party‟s report, so that only one AC report per Party needs to be submitted. iii. AC Report Section D: Funding received and provided This section generated some questions as to the merit of asking for this information, as well as the level of detail able to be presented in the current format. Although AC6 Members felt that this question could be useful in generating capacity indicators in the future, and should therefore be retained, they expressed concern regarding the availability and confidentiality of information needed to answer this question, as well as the complexity of compiling this information. Members agreed that to reflect this, the question could be qualified with “where readily available”. iv. Accessing bycatch forms outside AC Report The AC agreed with the SBWG recommendation that the fisheries component be made available outside of the AC reporting process so that it can be updated on an ongoing basis, as happens with population and breeding site data. v. Overlapping information requested for AC and MoP reports a) AC report section D asks for research and capacity building information, while the MoP report requests information on research pro...
View Source

Related to REVIEW OF WEB-BASED REPORTING SYSTEM

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

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

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

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