Process of Reporting Sample Clauses

Process of Reporting. 4.1. Access to data reporting platform and SFTP Server 4.2. Converting data to ACER XML file, report submission by HUPX Ltd. to ACER 4.3. Receipt and validation of data by ACER
AutoNDA by SimpleDocs
Process of Reporting. While on a retraining leave, unit members shall submit brief progress reports quarterly. A final report shall be submitted to the College President within three (3) months after returning to the District.
Process of Reporting. 11.6.7.1 Within three (3) months after returning to regular duties, the recipient shall submit a report to the Professional Standards Committee. The Committee will review the report and recommend approval or disapproval to the College President. Upon approval of the College President, the report is transmitted to the Chancellor. 11.6.7.2 The recipient’s report will include methods for sharing the results of studies, projects or activities with colleagues, the college, and the community, where appropriate. 11.6.7.3 A copy of the report will be filed at the college library and in the Chancellor’s office. 11.6.7.4 A self-evaluation will be filed with the Professional Standards Committee at the end of one (1) year following return from leave.
Process of Reporting. 4.1. Access to data reporting platform and SFTP Server
Process of Reporting. 9.12.7.1 Within three months after returning to regular duties, the recipient shall submit a report to the Professional Standards Committee. The Committee will review the report and recommend approval or disapproval to the College President. Upon approval of the President, the report is transmitted to the Chancellor. 9.12.7.2 The recipient’s report will include methods for sharing the results of studies,
Process of Reporting 

Related to Process of Reporting

  • Project Monitoring Reporting and Evaluation The Recipient shall furnish to the Association each Project Report not later than forty-five (45) days after the end of each calendar semester, covering the calendar semester.

  • Reporting Procedures Enter in the XXX Entity Management area the information that XXX requires about each proceeding described in paragraph 2 of this award term and condition. You do not need to submit the information a second time under assistance awards that you received if you already provided the information through XXX because you were required to do so under Federal procurement contracts that you were awarded.

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

  • Monthly Reporting Within twenty (20) calendar days following the end of each calendar month, Registry Operator shall deliver to ICANN reports in the format set forth in Specification 3 attached hereto (“Specification 3”).

  • Annual Reporting Within 90 days after the close of each of its respective fiscal years, audited, unqualified consolidated financial statements (which shall include balance sheets, statements of income and retained earnings and a statement of cash flows) for Provider for such fiscal year certified in a manner acceptable to the Agent by independent public accountants acceptable to the Agent.

  • Research Use Reporting To assure adherence to NIH GDS Policy, the PI agrees to provide annual Progress Updates as part of the annual Project Renewal or Project Close-out processes, prior to the expiration of the one (1) year data access period. The PI who is seeking Renewal or Close-out of a project agree to complete the appropriate online forms and provide specific information such as how the data have been used, including publications or presentations that resulted from the use of the requested dataset(s), a summary of any plans for future research use (if the PI is seeking renewal), any violations of the terms of access described within this Agreement and the implemented remediation, and information on any downstream intellectual property generated from the data. The PI also may include general comments regarding suggestions for improving the data access process in general. Information provided in the progress updates helps NIH evaluate program activities and may be considered by the NIH GDS governance committees as part of NIH’s effort to provide ongoing stewardship of data sharing activities subject to the NIH GDS Policy.

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