Modify Trouble Report. Allows NAS to modify the trouble severity (for example; change from “service affecting” to “out of service”) and trouble narrative on a TR until it has been cleared. This transaction is currently only supported for POTS.
Modify Trouble Report Sample Clauses
Related to Modify Trouble Report
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
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.
Scale Reports Forest Service shall pro- vide Purchaser a copy of Forest Service scaler’s record, if requested in writing.
GRIEVANCE REPORT Attachment I (Grievance Report) will be used in the processing of all grievances.
Title Report If no Additional Mortgage Policy is required with respect to such Additional Mortgaged Property, a title report issued by the Title Company with respect thereto, dated not more than 30 days prior to the date such Additional Mortgage is to be recorded and satisfactory in form and substance to Administrative Agent;
Adverse Report (a) The Employer shall notify an employee of any dissatisfaction concerning his/her work within ten (10) calendar days of the Employer's becoming aware of the matter giving rise to the dissatisfaction. This notification shall include particulars of work performance which led to such dissatisfaction. If this procedure is not followed, such expression of dissatisfaction shall not become part of his/her record for use against him/her at any time. The employee's written reply to such notification of dissatisfaction shall become part of his/her record.
Technical Standards Applicable to a Wind Generating Plant i. Low Voltage Ride-Through (LVRT) Capability A wind generating plant shall be able to remain online during voltage disturbances up to the time periods and associated voltage levels set forth in the standard below. The LVRT standard provides for a transition period standard and a post-transition period standard.
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.
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. If the Interconnection Customer's data is materially different from what was originally provided to the Participating TO and the CAISO for the Interconnection Studies, then the Participating TO and the CAISO will conduct appropriate studies pursuant to the LGIP to determine the impact on the Participating TO’s Transmission System and affected portions of the CAISO Controlled Grid based on the actual data submitted pursuant to this Article 24.3. The Interconnection Customer shall not begin Trial Operation until such studies are completed and all other requirements of this LGIA are satisfied.
Preliminary Engineering In order to receive City review and approval of the Extensions, Developer shall furnish two (2) copies of the plat map, topographic map and proposed roads profile sheets in electronic format prior to the City’s ordering of the engineering plans from its Engineer. The contour elevation and road profile elevations shall be referenced to NAVD ‘88 datum. In the event Developer’s engineer prepares the construction plans and specifications, the above information shall be a part of the extension construction plans to be reviewed and approved by the City’s Engineer. The final plat map shall be to the scale of 1-inch = 20 feet. The contour map shall have a scale of 1-inch = 20 feet and contour intervals of two (2) feet or less. The road profile sheets shall be to the scale of 1-inch = 20 feet. Developer shall provide a minimum of one benchmark, datum being NAVD ‘88, on the project site; and the elevation and location of the benchmark shall be indicated on the maps furnished by Developer.
