HFPS Controllers Interface and Monitoring Sample Clauses

HFPS Controllers Interface and Monitoring. The HFPS controller interfaces to the existing PPMS via the existing networks. HFPS controller’s settings as well as operating parameters are monitored by the PPMS and the DCS. A ringed Unit 1-6 fibre optic network installed for the TR sets is retained and re-used for the HFPS design. See drawings in section 9. The HFPS must comply with the following control parameters:  Quench, spark set back  Sparks and arcs per minute  Secondary Current limitSecondary Voltage limit  Secondary Under voltage trip limit  Secondary Under voltage trip delay  Maximum spark rate limitDuty cycleMode of operation  Voltage upper limit fixed at 440V The PPMS interfaces to the existing Unit DCS via an OPC interface employed between the Castlet dual redundant OPC Servers and the ABB Client Servers. Redundant PPMS OPC servers for Unit 1-3 and Unit 4-6 are located in Engineering Xxxx-Xxxx 0 and Engineering Xxxx-Xxxx 0 respectively. These servers are connected to Unit1-6 fibre optic ring via a network of Ethernet switches and optic fibre patch panels. The Contractor ensures that the required unit information by the unit DCS is accessed via this bi-directional OPC interface link. All new control systems are interfaced to the existing Matla process network, Clear Scada and Historian to store historical plant data. The HFPS controller must provide the following information to the PPMS or DCS:  Primary current  Primary Voltage  Secondary Current  Secondary Voltage  Sparking rate and accumulated arcing As a minimum, the following parameters on the HFPS controller must be visible and adjustable on the PPMS or DCS and also allow manual changes from the HFPS Controller system local operation:  Secondary current limit  Secondary Voltage limit  Secondary Under Voltage trip  Secondary Under Voltage trip delay fixed at 40s (Not adjustable)  Sparking rate The system must be able to provide the option to do manual VI curves. The following rapping philosophy is presently applied and must be available on all four fields:  Full power rapping  Power off rapping or reduced power rapping  Rapper queuing (rapping one field at a time per casing  Master rapping (rapping the same field of each casing at the same time)  Clean rapping  Start-up and shut down rapping programmes  Incremental rapping  Automatic test rapping The rapping philosophy above must be sent as a signal from the PPMS to the HFPS controller to control the field power.
Sample 1
AutoNDA by SimpleDocs

Related to HFPS Controllers Interface and Monitoring

  • Contract Monitoring The criminal background checks required by this rule shall be national in scope, and must be conducted at least once every three (3) years. Contractor shall make the criminal background checks required by Paragraph IV.G.1 available for inspection and copying by DRS personnel upon request of DRS.

  • Access to Network Interface Device (NID 2.4.3.1. Due to the wide variety of NIDs utilized by BellSouth (based on subscriber size and environmental considerations), Mpower may access the on-premises wiring by any of the following means: BellSouth shall allow Mpower to connect its loops directly to BellSouth’s multi-line residential NID enclosures that have additional space and are not used by BellSouth or any other telecommunications carriers to provide service to the premise. Mpower agrees to install compatible protectors and test jacks and to maintain the protection system and equipment and to indemnify BellSouth pursuant to Section 8 of the General Terms and Conditions of this Agreement.

  • Network Interconnection Architecture Each Party will plan, design, construct and maintain the facilities within their respective systems as are necessary and proper for the provision of traffic covered by this Agreement. These facilities include but are not limited to, a sufficient number of trunks to the point of interconnection with the tandem company, and sufficient interoffice and interexchange facilities and trunks between its own central offices to adequately handle traffic between all central offices within the service areas at P.01 grade of service or better. The provisioning and engineering of such services and facilities will comply with generally accepted industry methods and practices, and will observe the rules and regulations of the lawfully established tariffs applicable to the services provided.

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

  • Operating and Maintenance Manuals 58.1 If “as built” Drawings and/or operating and maintenance manuals are required, the Contractor shall supply them by the dates stated in the Contract Data.

  • Network Interface Device (NID) 2.7.1 The NID is defined as any means of interconnection of end-user customer premises wiring to BellSouth’s distribution plant, such as a cross-connect device used for that purpose. The NID is a single-line termination device or that portion of a multiple-line termination device required to terminate a single line or circuit at the premises. The NID features two independent xxxxxxxx or divisions that separate the service provider’s network from the end user’s customer-premises wiring. Each chamber or division contains the appropriate connection points or posts to which the service provider and the end user each make their connections. The NID provides a protective ground connection and is capable of terminating cables such as twisted pair cable.

  • Project Monitoring The Developer shall provide regular status reports to the NYISO in accordance with the monitoring requirements set forth in the Development Schedule, the Public Policy Transmission Planning Process Manual and Attachment Y of the OATT.

  • Quality control system (i) The Contractor shall establish a quality control mechanism to ensure compliance with the provisions of this Agreement (the “Quality Assurance Plan” or “QAP”).

  • Trunk Group Architecture and Traffic Routing The Parties shall jointly engineer and configure Local/IntraLATA Trunks over the physical Interconnection arrangements as follows:

  • Service Monitoring Customer gives express consent for Vodafone to monitor Customer’s use of the Service (and disclose and otherwise use the information obtained) only to: (a) the extent allowed by Applicable Law; (b) comply with Applicable Law; (c) protect the Network from misuse; (d) protect the integrity of the public internet and/or Vodafone’s systems and Networks; (e) the extent necessary to determine if Customer has breached any conditions or restrictions on use of the Service; (f) provide the Service; and/or (g) take other actions agreed or requested by Customer.

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