SUBMISSION OF THE MONTHLY MI REPORT 4.1 The completed MI Report shall be completed electronically and returned to the Authority by uploading the electronic MI Report computer file to MISO in accordance with the instructions provided in MISO.
4.2 The Authority reserves the right (acting reasonably) to specify that the MI Report be submitted by the Supplier using an alternative communication to that specified in paragraph 4.1 above such as email. The Supplier agrees to comply with any such instructions provided they do not materially increase the burden on the Supplier.
Financial Statements Statistical Data 2.6.1. The financial statements, including the notes thereto and supporting schedules included in the Registration Statement and Prospectus, fairly present the financial position and the results of operations of the Company at the dates and for the periods to which they apply. Such financial statements have been prepared in conformity with generally accepted accounting principles of the United States, consistently applied throughout the periods involved, and the supporting schedules included in the Registration Statement present fairly the information required to be stated therein. No other financial statements or supporting schedules are required to be included in the Registration Statement. The Registration Statement discloses all material off-balance sheet transactions, arrangements, obligations (including contingent obligations), and other relationships of the Company with unconsolidated entities or other persons that may have a material current or future effect on the Company’s financial condition, changes in financial condition, results of operations, liquidity, capital expenditures, capital resources, or significant components of revenues or expenses. There are no pro forma or as adjusted financial statements which are required to be included in the Registration Statement and the Prospectus in accordance with Regulation S-X which have not been included as so required.
2.6.2. The statistical, industry-related and market-related data included in the Registration Statement and the Prospectus are based on or derived from sources which the Company reasonably and in good faith believes are reliable and accurate, and such data agree with the sources from which they are derived.
CMI/RAI MDS Report Recognizing the mutual objective of quality resident care, the Employer agrees to meet through the Union Management Committee with the Union as soon as practicable after the receipt of the annual CMI/RAI MDS report. The Employer agrees to provide the Union with staffing levels, and staffing mix information; the impact of related payroll costs on staffing levels and a written notice of the CMI/RAI MDS report for the facility. The purpose of this meeting is to discuss the impact of the CMI/RAI MDS report on the staffing levels in the Home, quality resident care, and provide the Union with an opportunity to make representation in that regard. The parties shall meet as necessary to discuss other changes or workload issues. The parties may invite additional participants to attend the meeting to support constructive review and discussion.
Updated Information Submission by Interconnection Customer The updated information submission by the Interconnection Customer, including manufacturer information, shall occur no later than one hundred eighty (180) Calendar Days prior to the Trial Operation. The Interconnection Customer shall submit a completed copy of the Electric Generating Unit data requirements contained in Appendix 1 to the LGIP. It shall also include any additional information provided to the Participating TO and the CAISO for the Interconnection Studies. Information in this submission shall be the most current Electric Generating Unit design or expected performance data. Information submitted for stability models shall be compatible with the Participating TO and CAISO standard models. If there is no compatible model, the Interconnection Customer will work with a consultant mutually agreed to by the Parties to develop and supply a standard model and associated information.
eXtensible Business Reporting Language The interactive data in eXtensible Business Reporting Language included or incorporated by reference in the Registration Statement fairly presents the information called for in all material respects and has been prepared in accordance with the Commission’s rules and guidelines applicable thereto.
Technical Report 64 23.3 Return Location...............................................64 23.4
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.
Root-‐zone Information Publication ICANN’s publication of root-‐zone contact information for the TLD will include Registry Operator and its administrative and technical contacts. Any request to modify the contact information for the Registry Operator must be made in the format specified from time to time by ICANN at xxxx://xxx.xxxx.xxx/domains/root/.
Evaluation Cycle Goal Setting and Development of the Educator Plan
A) Every Educator has an Educator Plan that includes, but is not limited to, one goal related to the improvement of practice; one goal for the improvement of student learning. The Plan also outlines actions the Educator must take to attain the goals established in the Plan and benchmarks to assess progress. Goals may be developed by individual Educators, by the Evaluator, or by teams, departments, or groups of Educators who have the similar roles and/or responsibilities. See Sections 15-19 for more on Educator Plans.
B) To determine the goals to be included in the Educator Plan, the Evaluator reviews the goals the Educator has proposed in the Self-Assessment, using evidence of Educator performance and impact on student learning, growth and achievement based on the Educator’s self-assessment and other sources that Evaluator shares with the Educator. The process for determining the Educator’s impact on student learning, growth and achievement will be determined after ESE issues guidance on this matter. See #22, below.
C) Educator Plan Development Meetings shall be conducted as follows:
i) Educators in the same school may meet with the Evaluator in teams and/or individually at the end of the previous evaluation cycle or by October 15th of the next academic year to develop their Educator Plan. Educators shall not be expected to meet during the summer hiatus.
ii) For those Educators new to the school, the meeting with the Evaluator to establish the Educator Plan must occur by October 15th or within six weeks of the start of their assignment in that school
iii) The Evaluator shall meet individually with Educators with PTS and ratings of needs improvement or unsatisfactory to develop professional practice goal(s) that must address specific standards and indicators identified for improvement. In addition, the goals may address shared grade level or subject matter goals.
D) The Evaluator completes the Educator Plan by November 1st. The Educator shall sign the Educator Plan within 5 school days of its receipt and may include a written response. The Educator’s signature indicates that the Educator received the plan in a timely fashion. The signature does not indicate agreement or disagreement with its contents. The Evaluator retains final authority over the content of the Educator’s Plan.
Originating Switched Access Detail Usage Data A category 1101XX record as defined in the EMI Telcordia Practice BR-010-200- 010.
