Operations reporting. 9.4.1 National Grid NTS will, in accordance with the Uniform Network Code Operations Reporting Manual, and subject to paragraph 9.4.3, publish each month and at such other intervals as may be specified in such manual, information relating to:
(a) the implementation by National Grid NTS of certain provisions of the Code, including the Operational Balancing Steps taken by National Grid NTS;
(b) the operations of Users pursuant to certain provisions of the Code.
9.4.2 For the purposes of the Code the "Uniform Network Code Operations Reporting Manual" is the document so entitled prepared and (subject to paragraph 9.4.5) governed in accordance with [Section V12 of the UNC TPD].
9.4.3 In accordance with the Uniform Network Code Operations Reporting Manual, the form in which information under paragraph 9.4.1(b) is provided:
(a) to a User, will identify that User in the context of the information which relates to that User, but will not identify any other User in the context of the information which relates to such other User;
(b) to the Authority, will identify each User in the context of the information which relates to such User;
(c) to any other person, will not identify any User in the context of the information which relates to such User.
9.4.4 Each User hereby authorises National Grid NTS to publish in accordance with paragraph 9.4.1 such information relating to such User, in such form, as is provided for in the Uniform Network Code Operations Reporting Manual.
9.4.5 If National Grid NTS proposes to revise the Uniform Network Code Operations Reporting Manual, it shall obtain prior approval by Panel Majority of the Uniform Network Code Committee, and if such revision materially increases the extent of the information relating to Users to be published pursuant thereto:
(a) National Grid NTS will notify Users of its proposal not less than one month before implementing such proposal;
(b) any User may, within 14 Days after National Grid NTS's notification under paragraph (a), notify National Grid NTS that the User objects to such revision, providing reasonable details of the grounds for the User's objection;
Operations reporting. The SBWMA shall cause the Facilities’ Contractor to compile information and report on any of its Facilities operations, in accordance with the CIWMA and this Agreement.
Operations reporting. During the term of the Agreement, S&M Contractor shall keep Client informed of the performance of the Plant, of any qualitative and/or quantitative changes in production, and of any anomalies and unscheduled extraordinary maintenance interventions, by means of a monthly report issued to Client and, at Lender’s request (which may be a standing request), to Lender. S&M Contractor shall also inform Client if any feedstock values are out of specifications. Operational and analysis data shall be provided in Excel tables with graphs indicating the main parameters and any variations thereof. S&M Contractor shall compile a detailed monthly report of the operation of the Plant, indicating: • Feedstock fed in (quantity and quality) • COD load • average degradation yield • biogas produced and its composition • electrical energy produced • any faults and maintenance The above data shall be regularly monitored and recorded.
Operations reporting. 11.1 The Contractor shall evaluate Service performance in accordance with the Account Management provisions.
11.2 The Contractor shall provide the BBC with such additional statistical information and data regarding the Services and Licensing as the BBC may reasonably request from time to time.
Operations reporting. During operations, the OEM is expected to produce atleast monthly (but also on ad-hoc basic) technical reports highlighting:
i. Total user experienced downtime and measure taken to limit it in the future
ii. Number of tickets raised, resolutions at 2nd and 3rd level – time for resolution (at 25%, 50% and 75% percentile), current backlog, etc.
iii. Number of technical faults incurred
iv. Number of change requests executed, vs. current backlog
v. Description of the major change executed and of the ones planned for the next month vi. Average and peak utilization of HW and network resources, e.g. RAM, CPUs, bandwidth
Operations reporting. Information from vehicle operations shall be recorded by the drivers on manifests (trip sheets). The information recorded on this form shall be reviewed by Contractor staff for errors and completeness. Upon verification, the information shall be compared to RouteMatch data and enter any updates on a daily basis into RouteMatch and forwarded to the City on the third business day following each week. The verified trip data shall be available to the City in electronic format and provided weekly or upon request. The complete month’s data (comprised of the weekly submittals for that month) shall be submitted with the Monthly Operating Report by the tenth calendar day of the following month. Original manifests must be delivered to City on a weekly basis, on the third business day, with the weekly reports. Use of “white- out” correction fluids or tapes is not allowed. City expects all such reported information to be complete and accurate. Any changes that are determined to be needed after submission to City cannot be made without prior City authorization and the reasons for the change(s) must be fully documented. Failure to provide reports in compliance with these standards may result in assessment of penalties as described in Task 8. On a monthly basis, and using the above weekly operating data, Contractor shall prepare a Monthly Operating Report which shall be submitted to the City with the monthly invoice on or before 5 p.m. of the tenth calendar day of the following month. The Monthly Operating Report shall include the monthly operating data indicated above and, at a minimum, the following additional reports: Service date Vehicle number Driver’s name and number Line assignment Bus run number Bus block number Clock in time Pull out time Pull out odometer reading In service time In service odometer reading Out of service time Out of service odometer reading Pull in time Pull in odometer reading Clock out time Fuel start time Fuel end time Fuel odometer reading Vehicle Revenue Hours (VRH) by City and County Vehicle Revenue Hours (VRH) Vehicle Revenue Miles (VRM) by City and County Vehicle Revenue Miles (VRM) Vehicle Productivity (Passengers per revenue hour) Vehicle Productivity (Passengers per revenue hour) Total Vehicle Miles by City and County Total Vehicle Miles Deadhead Hours by City and County Deadhead Hours Deadhead Miles by City and County Deadhead Miles Scheduled Trips (To include late cancels/customer schedule Trips Total Passengers by City and County,...
Operations reporting. BOC shall provide NEA a written report monthly in a form similar to that contained in Exhibit D. The Operations report shall be delivered to NEA thirty (30) days following the end of each month. 4.
Operations reporting. The Contractor shall provide bilingual recorded messaging and telephone recording software for all calls processed through this telephone number. The Contractor shall provide Spanish speaking dispatching staff during all hours of service, and additionally, might require other dispatching staff that speaks other language(s)—this potential additional requirement can potentially be driven by Corona’s population change. The contractor is responsible for providing the reporting tools necessary to meet the requirements called out in Task 6. Contractor shall be responsible for ongoing service and support of the telephone reporting system software, as well as all peripheral computer and power supply equipment required for its operation. Contractor shall provide telephone headsets for all reservation staff to facilitate the efficient and comfortable accomplishment of their assigned duties. Such headsets shall be well maintained, and Contractor shall provide spare headsets so that equipment is available to reservations staff at all times. Sufficient staffing, workstations, and telephone lines will be provided to support the Performance Standards set by the City for call reservationist telephone services in Task 5.
Operations reporting. The PH-MCO must submit reports as specified by the Department to enable the Department to monitor the PH-MCO’s internal operations and service delivery. These reports include, but are not limited to, the following:
Operations reporting. The Contractor shall provide concise daily reports to the Company covering, as a minimum, major activities and items of concern during operations. These daily reports shall be transmitted to the Company’s office in Aberdeen and be supported offshore by daily meetings between the Contractor and the Company Operations Representatives and teleconference calls between the FPSO and Contractor’s and Company’s office. Meetings will be held in Aberdeen on a monthly basis with ad hoc meetings and conference calls with the FPSO as required. The Contractor shall supply plans and schedules covering work on the FPSO. The Contractor shall also provide incident reports, potential incident reports, annual inspection reports and other single occurrence reports as requested by the Company. Daily reports may include any information which is not commercially sensitive. Production data and well data for the Ettrick Field shall be reported by Contractor daily in a format to be mutually agreed prior to the Effective Date.
