Synchronized Event Operation Sample Clauses

Synchronized Event Operation. 3.5 Synchronized Event Operation The windows below can be operated in synchronization using a selected event. Event list window, TIME PLOT window, Event voltage fluctuation win- dow, Event data window Normal Event Normal event refers to any event not marked "WDU" in the Event List window or a point marked with red triangle event mark " " in the TIME PLOT window. TIME PLOT window Event list window Selecting events Selecting an Event You can select an event in the windows below. EVENT LIST window Activate the window and use the mouse to click a nor- mal event or use the up/down cursor key on the key- board to select the event. TIME PLOT window Activate the window and use the right/left cursor key on the keyboard to select a normal event "". You can also select a normal event by clicking "" di- rectly. Synchronized Display Selecting an event displays the following in each window: Event List window A normal event is selected. TIME PLOT window A triangle event mark " " outlined in red is dis-
Sample 1
AutoNDA by SimpleDocs
Synchronized Event Operation. WDU Event WDU event refers to an event with event voltage fluctuation graph data. A WDU event exists when an event is marked "WDU" in the Event List window or marked with a blue triangle event mark " " in the TIME PLOT window. TIME PLOT window Event list window Selecting events Selecting an Event You can select an event in the windows below. EVENT LIST window Activate the window and use the mouse to click a WDU event or use the up/down cursor key on the key- board to select the event. TIME PLOT window Activate the window and use the right/left cursor key on the keyboard to select a WDU event "". You can also select a WDU event by clicking "" di- rectly. Synchronized Display Selecting an event displays the following in each window: Event List window A WDU event is selected. TIME PLOT window A triangle event mark " " outlined in blue is dis- played. Event Voltage Fluctuation window The event voltage fluctuation graph of the selected WDU event is displayed. Event Data window The data of the selected WDU event is displayed. TIME PLOT Window Chapter 4 The TIME PLOT window in the 9624 program is equivalent to the same screen on the 3196 POWER QUALITY ANALYZER. When a high-capacity PC Card is used with the 3196, long-period recordings that cannot be displayed on the screen of the 3196 (SYS- TEM - RECORDING - When Memory Full: LOOP) can be displayed on the computer. The 9624 is capable of analyzing this long-period TIME PLOT file data. Window Display Click the (Open new TIME PLOT window) button or select View - Open new TIME PLOT window on the menu bar. Up to four windows can be open at the same time by pressing the but- ton or selecting from the menu bar repeatedly. ❖ 4.5, "Cursor Measurements"(page 34) ❖ 4.6, "Scrolling a Graph"(page 35) ❖ 4.7, "Selecting Events"(page 36) Window Display The four types of TIME PLOT window show RMS, voltage, harmonic and interharmonic variations. Activate a TIME PLOT window, then select a TIME PLOT window you wish to view from the TIME PLOT menu on the menu bar or right-click and select the window on the popup menu. The TIME PLOT window cannot be displayed unless the read data includes an ITV file. Also, the windows that can be selected depend on the contents of the type setting of the data to be recorded on the SYSTEM - MAIN - RECORDING screen of the 3196.
Sample 1

Related to Synchronized Event Operation

  • Planned Outages Seller shall schedule Planned Outages for the Project in accordance with Good Industry Practices and with the prior written consent of Buyer, which consent may not be unreasonably withheld or conditioned. The Parties acknowledge that in all circumstances, Good Industry Practices shall dictate when Planned Outages should occur. Seller shall notify Buyer of its proposed Planned Outage schedule for the Project for the following calendar year by submitting a written Planned Outage schedule no later than October 1st of each year during the Delivery Term. The Planned Outage schedule is subject to Buyer’s approval, which approval may not be unreasonably withheld or conditioned. Buyer shall promptly respond with its approval or with reasonable modifications to the Planned Outage schedule and Seller shall use its best efforts in accordance with Good Industry Practices to accommodate Xxxxx’s requested modifications. Notwithstanding the submission of the Planned Outage schedule described above, Seller shall also submit a completed Outage Notification Form to Buyer no later than fourteen (14) days prior to each Planned Outage and all appropriate outage information or requests to the CAISO in accordance with the CAISO Tariff. Seller shall contact Buyer with any requested changes to the Planned Outage schedule if Seller believes the Project must be shut down to conduct maintenance that cannot be delayed until the next scheduled Planned Outage consistent with Good Industry Practices. Seller shall not change its Planned Outage schedule without Buyer’s approval, not to be unreasonably withheld or conditioned. Seller shall use its best efforts in accordance with Good Industry Practices not to schedule Planned Outages during the months of July, August, September and October. At Buyer’s request, Seller shall use commercially reasonable efforts to reschedule Planned Outage so that it may deliver Product during CAISO declared or threatened emergency periods. Seller shall not substitute Energy from any other source for the output of the Project during a Planned Outage.

  • Processing operations The personal data transferred will be subject to the following basic processing activities:

  • Scheduled Outages (a) Commencing at least sixty (60) days before Initial Synchronization and throughout the Delivery Term, Seller shall, no later than January 1, April 1, July 1 and October 1 of each year, submit to SCE, using the Web Client, Seller’s schedule of proposed planned outages (“Outage Schedule”) for the subsequent twenty-four month period.

  • Downtime Due to the nature of server provision, downtime and lost transmissions may occur as part of routine maintenance. You are advised to maintain a copy of your account status and details of Content purchased.

  • Access Toll Connecting Trunk Group Architecture 9.2.1 If CBB chooses to subtend a Verizon access Tandem, CBB’s NPA/NXX must be assigned by CBB to subtend the same Verizon access Tandem that a Verizon NPA/NXX serving the same Rate Center Area subtends as identified in the LERG.

  • Transmission System Operation The NTO shall be responsible for ensuring that all actions related to the operation, maintenance and modification of its facilities that are designated as NTO Transmission Facilities Under ISO Operational Control and NTO Transmission Facilities Requiring ISO Notification are performed in accordance with the terms of this Agreement, all Reliability Rules and all other applicable reliability rules, standards and criteria, all operating instructions, ISO Tariffs, and ISO Procedures.

  • Interconnection Point The Service Provider is responsible for connecting to the LFC Network at the Interconnection Point. The LFC may only change an Interconnection Point if a change is necessary to protect the security or integrity of that Interconnection Point in order to maintain the continuity of supply of the Wholesale Services. In the event of any such change:

  • System Logging The system must maintain an automated audit trail which can 20 identify the user or system process which initiates a request for PHI COUNTY discloses to 21 CONTRACTOR or CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY, 22 or which alters such PHI. The audit trail must be date and time stamped, must log both successful and 23 failed accesses, must be read only, and must be restricted to authorized users. If such PHI is stored in a 24 database, database logging functionality must be enabled. Audit trail data must be archived for at least 3 25 years after occurrence.

  • Problem Solving Employees and supervisors are encouraged to attempt to resolve on an informal basis, at the earliest opportunity, a problem that could lead to a grievance. If the matter is not resolved by informal discussion, or a problem-solving meeting does not occur, it may be settled in accordance with the grievance procedure. Unless mutually agreed between the Employer and the Union problem-solving discussions shall not extend the deadlines for filing a grievance. The Union Xxxxxxx or in their absence, the Local Union President, or Area Xxxxxxx, or Chief Xxxxxxx, either with the employee or alone, shall present to the appropriate supervisor a written request for a meeting. If the supervisor agrees to a problem- solving meeting, this meeting shall be held within fourteen (14) calendar days of receipt of the request. The supervisor, employee, Union Xxxxxxx, and up to one (1) other management person shall attempt to resolve the problem through direct and forthright communication. If another member of management is present that person will not be hearing the grievance at Step Two, should it progress to that Step. The employee, the Union Xxxxxxx or in their absence, the Local Union President, or Area Xxxxxxx, or Chief Xxxxxxx, may participate in problem-solving activities on paid time, in accordance with Article 31, Union Rights, Section 1H.

  • Interconnection Points 8.5.1 The IP of a Party (“Receiving Party”) for Measured Internet Traffic delivered to the Receiving Party by the other Party shall be the same as the IP of the Receiving Party for Reciprocal Compensation Traffic under Section 7.1 above.

Time is Money Join Law Insider Premium to draft better contracts faster.