SECTION 260913 - ELECTRICAL POWER · Web viewProvide screen hotspot objects (poke points) for control functions and for opening diagrams, giving multilevel hyperlinking between diagrams

This master should be used by designers working on Port of Portland construction projects and by designers working for PDX tenants (“Tenants”). Usage notes highlight a few specific editing choices, however the entire section should be evaluated and edited to fit specific project needs.

SECTION 260913 – ELECTRICAL POWER MONITORING AND CONTROL

PART 1 - GENERAL

1.1 DESCRIPTION

A. This section describes devices, components, software, and accessories for the power monitoring, analysis, and control system (PMAC).

1.2 RELATED WORK SPECIFIED ELSEWHERE

A. Section 261100, Substations

1.3 REFERENCES

A. ANSI/IEEE: American National Standards Institute/Institute of Electrical and Electronics Engineers1. ANSI 50/51: Instantaneous/Time-Delay AC Over Current Relay2. ANSI C12.20: Electricity Meters - 0.2 and 0.5 Accuracy Classes

B. CSA: Canadian Standards Associations1. CSA 22.2: Information Technology Equipment - Safety - Part 1: General Requirements

C. FCC: Federal Communications Commission1. FCC Part 15: Radio Frequency Devices

D. IEC: International Electrotechnical Commission1. IEC 1000-22. IEC 1000-43. IEC 1000-5

E. ISO: International Organization for Standardization1. ISO 9000: Quality management systems -- Fundamentals and vocabulary

F. NEC: National Electrical Code

G. UL: Underwriters Laboratories1. UL 508: Standard for Industrial Control Equipment

5/6/2023 ELECTRICAL POWER MONITORING AND CONTROL/tt/file_convert/5aa1c9cb7f8b9a1f6d8c653e/document.doc 260913-1

1.4 SYSTEM DESCRIPTION

A. General:1. The PMAC software shall gather building energy management information. The

information may include several types of energy sources such as natural gas, water, steam, etc., in addition to electrical energy. The PMAC software shall run on server workstations and client workstations. Client workstations will access the PMAC software via the Port intranet.

2. The PMAC system shall allow resources such as workstations, communication lines, PMAC instruments, peripherals, network bridges, application processors, additional printers, additional computer memory, and additional disk storage to be added without the need for software changes.

B. System Integration:1. The PMAC system shall be easily integrated with third-party monitoring devices. The

PMAC system shall be freely scalable and shall be able to support an arbitrary number of server and client workstations.a. Expansion shall not require the replacement of previously installed equipment.

The system design shall anticipate increased requirements for processors, memory, IED (intelligent electronic device) channels, and peripherals.

b. There shall be no single-vendor (proprietary) hardware components required for a workstation to operate as part of the PMAC system.

c. The PMAC software shall include application programs running on server workstations and client workstations. PMAC software running on server workstations and client workstations shall be the primary user interface to the PMAC information and control functions.

d. The functions of the PMAC system shall include, but not be limited to:1) Supervisory control.2) Data acquisition from PMAC instruments and other telemetered data

sources.3) Processing of acquired data.4) Collation of historical data.5) LAN/WAN access to historical data.6) Processing of events.7) Annunciation of alarms.8) Processing of requests from workstations.9) Database generation and modification.10) Customized data display generation and modification.11) PMAC network system configuration.12) Diagnostics and equipment test functions.13) Customized application functions as required.

C. PMAC Instrumentation:1. The PMAC instrumentation shall include, but not be limited to, panel-mounted

metering/monitoring devices, digital and analog input and output devices, display panels, communications devices, and ancillary equipment.

2. Provide appropriate potential transformers and current transformers to supply sensing signals for the PMAC instruments.

ELECTRICAL POWER MONITORING AND CONTROL 5/6/2023260913-2 /tt/file_convert/5aa1c9cb7f8b9a1f6d8c653e/document.doc

3. Installation of PMAC devices and ancillary equipment, and wiring connections to all electrical circuits, PMAC devices, and terminal strips for external devices, shall conform to all local and national electrical codes.

4. Provide shorting switches or test blocks for all meter CT inputs.

D. System Communication:1. The PMAC shall utilize an Ethernet LAN.2. The system shall use a non-proprietary digital packet polling protocol to send data

between each server workstation (or client workstation) and PMAC instruments connected on the data bus. The packet protocol shall provide unit and broadcast addressing, error checking, and bus control transfer capability.

1.5 SUBMITTALS

A. Submit technical data sheets, installation manuals, and/or user documentation manuals that describe product installation and operation, physical data, electrical characteristics, and connection requirements of the PMAC system.

B. Submit shop drawings of the system design.1. Shop drawings shall be new, and prepared utilizing AutoCAD and backgrounds of the

Port-provided reference drawings.2. Shop drawings shall be of the size approved by the Port with title blocks, identifying

drawing number and any reference drawings. Fully dimension all plans and elevations.3. Shop drawings shall include, but not be limited to, the following:

a. Complete floor plans with all systems included as part of the work of the section shown, at 1/8" = 1'-0" scale.

b. Sections of congested areas shall be at 1/4" = 1'-0" scale.4. Shop drawings shall indicate, but not be limited to, the following:

a. Conduit routing and wiring.b. Control and riser diagrams.c. Schematic diagrams.

C. Submit data regarding communication cables.

D. Submit equipment installation details and drawings.

E. Submit operation and maintenance manuals.

F. Submit copies of all data file and application software for reload in the event of a system crash or memory failure.

1.6 QUALITY ASSURANCE

A. The Contractor shall be accredited to ISO 9000 quality assurance standards.

B. The PMAC system shall not be a prototype. Similar systems shall have been field-installed and successfully operated for at least three years.


C. The PMAC instrumentation shall be calibrated at the factory using an instrument that is certified to have been calibrated using standards whose accuracies are traceable to the National Institute of Standards and Technology (NIST) or the National Research Council of Canada (NRC).

1.7 SITE CONDITIONS

A. The PMAC instruments will be subjected to the following environmental conditions:1. Temperature: 32ºF to 122ºF.2. Humidity: 5 percent to 95 percent non-condensing.

1.8 MAINTENANCE

A. Provide preferred technical support service. This service shall include the following:1. Technical consultation via telephone for an unlimited number of hours per month, for the

duration of the warranty period.2. Free upgrades to new firmware for PMAC instrumentation for the duration of the

warranty period.

PART 2 - PRODUCTS

2.1 PMAC INSTRUMENTS

A. Manufacturers: Square D, or pre-bid approved equal.

Add or delete instruments as required.

B. Circuit Monitors (CM-4000):1. Circuit monitors shall provide true rms metered values. Information provided by each

circuit monitor shall include frequency, temperature, current, demand current, voltage, real power, reactive power, apparent power, demand power, predicted demand power, power factor, accumulated energy, accumulated reactive energy, total harmonic distortion (THD) of each current and voltage, and K-factor of each current.

2. The current and voltage signals shall be digitally sampled at a rate high enough to provide true rms accuracy to the 255th harmonic (based on fundamental of 50/60 Hz).

3. Circuit monitors shall be rated for an operating temperature range of -25°C to 70°C and shall have an overcurrent withstand rating of 500 amps for 1 second.

4. Setup parameters required by the circuit monitors shall be stored in nonvolatile memory and retained in the event of a control power interruption.

5. Circuit monitors shall accept metering inputs of up to 600Vac direct connection or from industry standard instrument transformers (120Vac secondary PTs and 5 A secondary CTs). Connection to 480Y/277Vac circuits shall be possible without use of PTs.a. PT primaries through 1.2 MV shall be supported.b. CT primaries through 32 kA shall be supported.c. The circuit monitor shall be accurate to 0.04 percent of reading plus/minus

0.025 percent of full scale for voltage and current metering and 0.08 percent of reading plus 0.025 percent for power.


d. The circuit monitor’s energy readings shall meet the revenue accuracy requirements of ANSI C12.20 0.2 class metering.

e. Annual recalibration by users shall not be required to maintain published accuracy.f. Voltage and current for all phases shall be sampled simultaneously to assure high

accuracy in conditions of low power factor or large waveform distortions (harmonics).

6. Circuit monitors shall be capable of application in three-phase, three- or four-wire systems. A fourth CT input shall be available to measure neutral or ground current. If the fourth CT is not used, then a residual current shall be calculated by vectoral addition of the phase currents. In four-wire connections the circuit monitor shall utilize the circuit neutral common reference and not earth ground, to provide metering accuracy.

7. Circuit monitors shall be capable of being applied without modification at nominal frequencies of 50, 60, or 400 Hz.

8. Circuit monitors shall operate properly over a wide range of control power including 100-305Vac or 100-300Vdc. Connections to 18-60Vdc shall also be available.

9. Ride-through capability shall be available for backup control power for up to 2 seconds.10. Circuit monitor displays shall allow the user to select English, French, or Spanish

language. The circuit monitor display shall also allow the user to select a date/time format and to create additional screens for user-specified views and/or custom quantities without overwriting existing standard screens. The circuit monitor display shall provide local access to the following metered quantities as well as the minimum and maximum value of each instantaneous quantity since the last min/max reset:a. Current, per phase rms, three-phase average and neutral (if applicable).b. Voltage, phase-to-phase, phase-to-neutral, and three-phase average (phase-to-

phase and phase-to-neutral).c. Real power, per phase and three-phase total.d. Reactive power, per phase and three-phase total.e. Apparent power, per phase and three-phase total.f. Power factor, per phase and three-phase total.g. Frequency.h. Demand current, per phase and three-phase average.i. Demand real power, three-phase total.j. Demand apparent power, three-phase total.k. Accumulated energy, (MWh and MVARh).l. Total harmonic distortion (THD), current and voltage, per phase.m. K-factor, current, per phase.n. Reset of the following electrical parameters shall also be allowed from the circuit

monitor display:1) Peak demand current.2) Peak demand power (kW) and peak demand apparent power (kVA).3) Energy (MWh) and reactive energy (MVARh).

11. Setup for system requirements shall be allowed from the circuit monitor display. Setup provisions shall include:a. CT rating.b. PT rating.c. System type (three-phase, 3-wire; three-phase, 4-wire).d. Demand interval (5-60 min.).e. Watt-hours per pulse.

12. Circuit monitors shall provide a hardware security switch to protect all revenue related metering configuration from unauthorized/accidental changes. The circuit monitor shall


support the use of a wire seal to further deter inadvertent configuration changes and provide visual tamper indication.

13. For ease in operator viewing, two displays shall be offered for local viewing of circuit monitor data. The liquid crystal display (LCD) shall include backlighting. The enhanced vacuum fluorescent display (VFD) shall be automatically activated by a proximity sensor as the operator approaches.

14. Circuit monitors shall communicate via RS-232, RS-485, and Ethernet simultaneously.15. Circuit monitors shall provide Modbus communications using Modbus TCP via an

Ethernet network at 10/100Mbaud using UTP or Fiber connections. The circuit monitor shall provide the capability to communicate to 31 additional Modbus devices existing on RS-485 daisy chains and report data back to the PMAC application software or across the Ethernet network to other software applications.

16. Circuit monitor displays shall provide an RS-232 communications port on board the metering module as well as an IR RS-232 communications port located on the display. The display port shall be completely accessible during normal operation and shall not require exposure of the operator to life-threatening voltage when in use. The operator shall be able to quickly connect a small personal computer (PC) to either the module port or the display port without use of tools or splices. Both the metering module port and the display port shall have all of the communication functionality of the standard hard-wired port. When a connection is made to either the metering module port or the display port, the circuit monitor shall continue simultaneous operation of all communication ports associated with the circuit monitor.

17. It shall be possible to field upgrade the firmware in the circuit monitor to enhance functionality. These firmware upgrades shall be done through either the display port or communication connection. Circuit monitor disassembly or changing of integrated circuit chips shall not be required. It shall not be necessary to de-energize the circuit or the equipment to upgrade the firmware.

18. All power demand calculations shall be done by any one of the following calculation methods, selectable by the user:a. Thermal demand calculated using a sliding window and updated every second.

The sliding window length shall be defined by the user from 1 to 60 minutes, with 1-minute increments.

b. Block interval, with optional sub-intervals. The window length shall be set by the user from 1 to 60 minutes in 1-minute intervals. The user shall be able to set the sub-interval length from 1 to 30 minutes in 1-minute intervals.

c. External pulse synchronization, utilizing a synch pulse provided externally. An optional status input shall be used to sense the pulse.

d. Sliding block interval with continuous sliding 1-second sub-intervals.e. The default demand calculation method shall be a 15-minute continuous sliding

block.19. The following demand readings shall be reported by the circuit monitor:

a. Average demand current, per phase.b. Peak demand current, per phase.c. Average demand for real power, reactive power, and apparent power.d. Predicted demand for real power, reactive power, and apparent power.e. Peak demand for real power, reactive power, and apparent power.

20. Circuit monitors shall also provide generic demand capability to supply demand calculations on any metered parameter.

21. Circuit monitors shall be capable of receiving a broadcast message over the communications network that can be used to synchronize demand calculations by several


circuit monitors. This message need not be addressed specifically to any one circuit monitor.

22. The following energy readings shall be reported by the circuit monitor:a. Accumulated energy.b. Accumulated reactive energy.c. Accumulated apparent energy.d. Reactive energy by quadrant.e. For real and reactive energy reported values, separate totals for energy flow in each

direction shall be kept, as well as an arithmetic sum.f. Each circuit monitor shall be capable of operating a solid state KYZ output relay to

provide output pulses for a user definable increment of reported energy. Minimum relay life shall be in excess of one billion operations.

23. Circuit monitors shall include current and voltage waveform capture capability. Waveform capture shall be user selectable for 12, 24, 36, 48, or 60 cycles of data, user-specified up to 30 seconds.a. Waveform capture shall be initiated either from a PC workstation running the

PMAC software or by the circuit monitor as a user-defined response to an alarm condition.

b. Waveform capture manually triggered from the PMAC software shall be captured at 512 samples/cycle for one cycle providing harmonic content up to the 255th harmonic for Ia, Ib, Ic, I4, Va, Vb, Vc, and Vg.

c. Two types of waveform capture shall be available for response to an alarm condition.1) The first type shall support up to 512 samples/cycle resolution for 12 cycles

with user defined 2 to 10 pre-event cycles.2) The second type shall offer variable resolution for up to 30 seconds of

continuous waveform recording. The circuit monitor shall be capable of triggering the second type of waveform capture on the occurrence (pickup) of an event and continue recording until the event ends (dropout) for up to 30 seconds maximum duration.

d. The circuit monitor shall transmit waveform samples over the network to the PC workstation for display, archival, and analysis.

e. Each voltage and current of all the phases shall be sampled concurrently so that proper phase relationships are maintained, so that harmonic flow analysis can be performed, and so that the effect of a disturbance can be observed on all phase voltages and currents.

f. Harmonic analysis performed on the captured waveforms shall resolve harmonics through the 255th using PMAC software.

g. All waveforms shall reflect actual circuit performance. Waveforms synthesized or composed over time will not be acceptable.

24. Data logging may be accomplished either within the circuit monitor, at the PC workstation, or both. Each circuit monitor shall be able to log data, alarms and events, and multiple waveforms. The monitors shall offer 8MB of onboard nonvolatile memory, which can be field upgraded without requiring disassembly or removal of the circuit monitor. Onboard data logs shall be communicated to the PC workstation upon demand or at scheduled intervals. Logged information to be stored in each circuit monitor includes:a. Up to 14 separate data logs shall be configurable by the user. Each log entry shall

be date- and time-stamped. The type of data for the log shall be selected from a list of over 150 monitored values. Each log entry shall be user configurable to


consist of from one to over 75 values of instantaneous data. It shall be possible to set up each log to record data at independent user-defined intervals. In addition, it shall be possible for a user to define an event or new minimum/maximum conditions that will trigger log file entries.

b. Data logs shall be configurable by users to be fill and hold or circular (FIFO).c. A minimum/maximum log file shall include the time, date, and value for the

minimum and maximum of each of the instantaneous metered values since last reset. A minimum/maximum/average log shall record the minimum/maximum/average readings for pre-defined quantities at a user-specified interval.

d. An alarm and event log shall contain time, date, event information, and coincident information for each user-defined alarm or event. This log shall have a capacity of up to 1,000 events.

e. Waveform logs shall store captured waveforms as defined by the user. Waveform log entries shall be scheduled at user-defined intervals, externally triggered, or forced in response to a user-defined event. Waveform logs shall be either fill and hold or circular (FIFO) as defined by the user.

f. The PMAC software shall enable the user to allocate onboard circuit monitor memory for each logging function.

25. Circuit monitors shall provide preconfigured, field-replacable input/output (I/O) modules and also provide I/O options to be configured as applicable to each installation:a. Option One - One solid state output suitable for KYZ pulse initiation; four solid

state status inputs; three (10A) mechanical output relays.b. Option Two – Four solid state status inputs; four analog inputs (4-20 mA).c. Option Three – Four inputs (32Vdc); 2 solid state outputs (60Vdc); 1 analog input

(0-5Vdc); 1 analog output (4-20mA).d. Option Four - Eight solid state status inputs (120Vac).e. Option Five – Configurable I/O options including solid state input modules for

120Vac, 200Vac, and 32Vdc; solid state outputs modules for 120Vac, 240Vac, 60Vdc, 240Vdc; analog input modules for 0-5Vdc, 4-20mA; analog output module for 4-20mA.

26. Time synchronization to 1 millisecond between monitors shall be accomplished via GPS synchronization.

27. Alarm events shall be a combination of factory pre-configured events and user-definable events. Multiple levels of alarms shall be configurable for each metered parameter.a. The following classes of events shall be available as alarm events:

1) Over/under current.2) Over/under voltage.3) Current imbalance.4) Phase loss, current.5) Phase loss, voltage.6) Voltage imbalance.7) Over kVA.8) Over kW or kVAR into/out of load.9) Over/under frequency.10) Under power factor, true or displacement.11) Over THD.12) Over K-factor.13) Over demand, current or power.14) Reverse power.


15) Phase reversal.16) Status input change.17) End of incremental energy interval.18) End of demand interval.19) Over/under analog inputs.20) Current sag/swell.21) Voltage sag/swell.

b. For each over/under metered value alarm, the user shall be able to define a pick-up, drop-out, and delay.

c. There shall be four alarm severity levels in order to prioritize event importance.d. Indication of an alarm condition shall be given on the local display as well as

reported to the PMAC software.e. The circuit monitor shall calculate key electrical parameters at 100ms intervals for

the purpose of alarming and recording of data during an event. The recorded data shall be comprised of RMS readings for I, V, kW, kVAR, kVA, and True PF. 1-10 seconds of pre-event and up to 5 minutes of post event data can be recorded.

28. Output Relay Control:a. Relay outputs shall operate either by user command sent over the communication

link, or in response to user-defined alarm event.b. Output relays shall close in either a momentary or latched mode, as defined by the

user.c. Each output relay used in a momentary contact mode shall have an independent

timer that can be set by the user.d. Individual relay outputs shall be controllable by multiple alarms in a wired “OR”

configuration.29. Circuit monitors shall include sag and swell detection capability characterized by the

following features:a. Circuit monitors shall continuously monitor for disturbances in the currents and

incoming voltage. There shall be zero blind time; each cycle shall be individually monitored.

b. Disturbance events less than 1/2 cycle in length shall be detected.c. The user shall be able to set a threshold and delay for determining when an event

has occurred. The threshold shall be user-defined as either a fixed setpoint or a relative setpoint. When using the relative setpoint, the circuit monitor shall set the nominal current or voltage equal to its present average value. The circuit monitor shall automatically adjust the nominal current and voltage values to avoid nuisance alarms caused by gradual daily variations of currents and voltages.

d. Upon detecting a disturbance, the circuit monitor shall be capable of:1) Logging a waveform of the event with all phase currents, voltages, and/or a

high-speed 100ms RMS event recording.2) Operating any output relay on an optional I/O module.3) Recording the disturbance into an event log with a date and time stamp to

the millisecond.4) Causing an operator alarm at the PC workstation.

e. All data and waveform logs shall be communicated over the local area network or through the front panel communications port so that the user may view and analyze the data using the PMAC software and workstation.

30. Circuit monitors with the transient detection option (CVMT), utilized to detect, analyze, and assist in the mitigation of damaging transient overvoltages, shall include the following capabilities:


a. Transient waveform capture that records the signal on each of the three voltage inputs at a rate not less than 83,333 samples per cycle (5 MHz/channel) for a 60 Hz system.

b. Transient waveform capture that captures voltage transient peaks up to 5kV peak for L-N, 4-wire, direct connections; and up to 10kV peak for L-L, 3-wire, direct connections.

c. Adjustable meter triggering thresholds to avoid nuisance alarms.d. Voltage peak measurements that are accurate to within 5 percent of the transient’s

actual peak magnitude.e. High-resolution waveform capture of a transient and a simultaneous lower

resolution (over a longer duration) disturbance waveform capture when a transient alarm is triggered.

f. Means by which application software can associate the transient waveform capture with the related disturbance waveform capture.

g. Ethernet capability to provide HTML summary of transient events.h. Maintenance of at least 50 transient waveform captures in non-volatile memory.i. A count of the total number of transients and the number of transients per phase.j. The following register-based data, stored in non-volatile memory when a transient

is recorded:1) Date/time of transient.2) Unique ID.3) Peak voltage magnitude.4) Duration of the peak.5) Rise-time.6) Average voltage over the duration of the transient.

31. Circuit monitors shall be designed to run customized programs to greatly expand the functionality for the particular installation.a. These programs shall be written in a circuit monitor programming language similar

to a compiled “BASIC” language. The programming language shall include the following capabilities:1) Scheduled tasks.2) Event tasks.3) Math functions including: add, subtract, multiple, divide, sine, cosine,

square root, etc.4) Logical functions including: AND, OR, XOR, NOT, shift, etc.5) Loop commands.6) Compare statements.7) Counters and timers.

b. Custom programming services shall be available from the circuit monitor manufacturer.

c. Changing programs shall not require physical modifications to the circuit monitor, such as changing computer chips or cards. Changes shall be done via either of the communications ports.

d. Examples of custom programs include:1) Metering of specialized utility rate structures, including real time pricing

and curtailable rates.2) Data reduction using smart data logging.3) Automatic monthly logging/reset of kWH and peak demand.4) Statistical profile analysis of metered quantities.5) CBEMA power quality analysis.


6) Calculations for IEEE-519 verification.7) Metering of combined utilities: gas, water, steam, and electric.8) Non-critical control schemes, such as load control or power factor

correction, based on multiple conditions (e.g. time of day and input status).32. Advanced harmonic information shall be available via the circuit monitor. This shall

include the calculation of the harmonic magnitudes and angles for each phase voltage and current through the 255th harmonic.a. This information shall be available for all three phases, current and voltage, plus

the neutral current. To ensure maximum accuracy for analysis, the current and voltage information for all phases shall be obtained simultaneously from the same cycle.

b. The circuit monitor shall have a minimum of 100k of onboard memory to log harmonic magnitudes and angles.

c. The harmonic magnitude shall be reported as a percentage of the fundamental or as a percentage of the rms values, as selected by the user.

C. Power Meter:1. The power meter shall be accurate to 0.25 percent of reading plus 0.05 percent of full

scale for voltage and current sensing, and 0.5 percent of reading plus 0.05 percent of full scale for power and energy, accurate through the 31st harmonic.a. These accuracies shall be maintained for both light and full loads.b. Annual recalibration by users shall not be required to maintain these accuracies.c. Voltage and current for all phases shall be sampled simultaneously to assure high

accuracy.2. The meter shall be listed per UL 508, CSA recognized under C22.2, CE compliant, and

tested for EMC in accordance with the IEC 1000-2, 1000-4, 1000-5 series of electrical tests (level 4), FCC compliant per FCC Part 15, Class A, and vibration and temperature tested. The meter module shall be rated for an operating temperature range of 0°C to 60°C.

3. Metering inputs shall utilize current transformers for the current inputs. The power meter shall be rated 5A nominal and 10A full scale. In addition, it shall be industrially and utility hardened to have an overload withstand rating of 15A continuous and 500A for 1 second.

4. The device shall not require potential transformers or control power transformers when applied at 600V or less. The power meter shall accept control power over a range of 90-600Vac, 50 or 60 Hz, or 100-350Vdc.

5. The power meter shall have built-in RS-485 data communications to allow multipoint communication to multiple computer workstations, programmable controllers, and other host devices, up to a data rate of 19,200 baud.

6. Information shall be available from the display or via RS-485 communications. It shall be possible to perform the setup via the display. No dip switches or other hardware adjustments shall be required for setup.

7. The power meter shall be installed as part of a PMAC system. The RS-485 communications shall provide communications links up to 10,000 feet long.

8. The power meter shall communicate using:a. The Modbus RTU and JBus protocol and connect to any host devices with a

Modbus-compatible port.b. The POWERLOGIC protocol and shall connect to any host devices with a

POWERLOGIC compatible port.


c. The three protocols mentioned above shall reside in the meter from the factory and be field selectable as part of setup.

9. The data communications shall be optically isolated to provide reliable operation.10. When connected via the network to a POWERLOGIC computer, the power meter shall

provide logging, trending, and alarming information.11. Each power meter shall be equipped with a backlit, two-line LCD display.12. To facilitate ease in mounting, the display shall be capable of being mounted up to

50 feet from the metering module using RJ-11 terminated communications cable. Regardless of mounting configuration, the display shall be optically isolated from the power meter module.

13. The display shall scale readings automatically, without the need for multipliers.14. All setup information and reset commands shall be password protected.15. The power meter shall provide diagnostics to troubleshoot improperly wired installations.16. A KYZ pulse initiator for communication of kWh, kVARh, or kVAh information to third

party energy management systems shall be provided.17. The power meter shall provide the following:

a. Current, per phase.b. Voltage, phase-to-phase and phase-neutral.c. Real power (kW), per phase and three-phase total.d. Reactive power (kVAR), per phase and three-phase total.e. Apparent power (kVA), per phase and three-phase total.f. Power factor (true), per phase and three-phase total.g. Frequency readings.h. Real energy (kWh), three-phase total.i. Reactive energy (kVARh), three-phase total.j. Apparent energy (kVAh), three-phase total.k. Energy accumulation modes, signed, absolute, energy in, energy out.l. Neutral current measurements.m. Demand current, per phase and neutral, present and peak.n. Real power demand (kWd) readings, three-phase total, present and peak.o. Reactive power demand (kVARd) readings, three-phase total, present and peak.p. Apparent power demand (kVAd) readings, three-phase total, present and peak.q. THD readings, voltage and current, per phase.r. Date and time stamping, peak demands, power up/restart and resets.s. Onboard alarms for over/under voltages (per phase L-L, L-N), over/under currents

(per phase, neutral), over/under frequency, current unbalance (per phase), and voltage unbalance (per phase L-L, L-N).

t. Minimum and maximum readings.u. Onboard memory.v. Advanced demand calculations, including:

1) User-defined demand intervals.2) User-defined sliding or rolling block demand.3) Synchronization of demand interval to utility pulse.4) Predicted power demand for real, reactive, and apparent power.

D. Low Voltage Power Circuit Breaker Trip Units:1. Circuit breaker trip units shall have power monitoring capabilities as specified below.

Trip units alone or trip units in combination with meter modules can be used. Meter modules, if used, must comply with applicable parts of this specification.


2. Electronic trip units shall be UL listed as field-replaceable and upgradeable without special adjustments to the mechanism.

3. Electronic trip units shall be true RMS current sensing.4. Trip units shall provide local trip indication and capability to indicate local and remote

reason for trip (e.g. overload, short circuit, or ground fault).5. Trip units shall be capable of communicating on MODBUS networks.6. Each circuit breaker trip unit shall provide real time metering. Metering functions

include:a. Current (per phase, neutral, ground fault, earth leakage, three-phase maximum, and

fault). A loading capacity as a percent of the rating shall also be calculated.b. Voltage (per phase and between phases). Voltage imbalance shall also be metered.c. Power (three-phase total real, reactive, and apparent power).d. Energy (apparent energy, real energy, and reactive energy).e. Demand:

1) Current (actual and predicted).2) Real power (actual, predicted, and peak).3) Apparent power (actual, predicted, and peak).4) Reactive power (actual, predicted, and peak).

f. Frequency7. Power and energy readings shall be accurate to 2.5 percent of reading.8. Trip units shall provide protective function and trip information including:

a. Circuit breaker frame size and rating.b. Trip settings.c. Cause of trip.d. Device status (open, closed, or tripped).e. Breaker position status (racked in, racked out, test position).f. Number of mechanical operations.

9. Trip units shall include an integral, graphical display to indicate the following:a. Metered values (numeric).b. Per-phase metered values by bar chart.c. Trip settings.

10. Trip units shall be powered from within the circuit breaker without the need for an external power source.

E. Molded Case Circuit Breaker Electronic Trip Units:1. Molded case circuit breaker electronic trip units shall provide the following breaker/trip

unit information to the PMAC network:a. Breaker frame type (i.e., LE, ME, NE, PE, SE).b. Breaker sensor rating.c. Rating plug.d. Protective settings.

2. Molded case circuit breaker electronic trip units shall provide individual phase and ground ammeter information to the PMAC network.

3. Molded case circuit breaker electronic trip units shall provide the following trip information to the PMAC network:a. Date/time of last trip.b. Type of last trip (overload, short circuit, ground fault).c. Magnitude of phase and ground fault at time of last trip.

4. Molded case circuit breaker electronic trip units shall provide the following maintenance information to the PMAC network:


a. Number of overload trips.b. Number of short circuit trips.c. Number of ground fault trips.

F. Transformer Temperature Monitors:1. Transformer temperature monitors shall be provided for each dry-type and cast resin

transformer furnished and installed. Transformer temperature monitors shall be UL listed.

2. The transformer temperature monitors shall provide the following information to the PMAC network:a. Coil temperatures (phases A, B, and C).b. Hottest coil temperature.c. Fan relay status.d. Alarm relay status.e. Emergency over-temperature relay status.f. Setpoints for fans, alarm, and over-temperature relays.

G. Electronic Motor Protective Devices:1. Electronic motor protective devices as noted on the project drawings shall be able to

model (learn) the thermal loading of the motor and cool down characteristics to maximize protection during continuous and load cycling operation.

2. Each unit shall be equipped with industry standard RS-485 data communications and shall utilize the same data communication cables as the other power monitoring devices in the system.

3. Historical operating information such as running hours since last commissioning, number of starts/trips since last commissioning, number of overload trips/ground fault trips and similar data shall be displayed on the front of the device. Such information shall be available via data communications to programmable logic controllers and PC workstations throughout the PMAC network for control, alarming, data logging, and event recording.

4. The electronic motor protective devices shall provide fault diagnosis data such as pre-trip motor and ground fault currents, unbalance ratio, and maximum stator RTD temperature.

5. Each motor circuit noted on the drawings shall be equipped with a circuit monitor to provide extensive power monitoring information.

6. The electronic motor protective devices shall accept dc control power.7. The electronic motor protective devices shall be UL listed.

H. Digital Protective Relays:1. Digital protective relays shall be installed as shown on the drawings. These relays shall

accept three-phase inputs from industry standard current transformers with 1 or 5 amp nominal secondaries.

2. The digital protective relays shall provide three-phase overcurrent protection (ANSI 50/51) and ground overcurrent protection (ANSI 50/51G or 50/51N).

3. The user shall be able to select a variety of time current curves from several different families. Families of curves shall include definite time, inverse, very inverse, extremely inverse and ultra inverse. All families of curves shall be suitable for coordination in typical medium voltage applications. The ultra inverse curves shall be provided to enhance coordination with fuses.

4. A front panel keypad and display shall be provided. From this front panel it shall be possible to:


a. Select time-current characteristic curves.b. Set CT ratios.c. Display phase current information.d. Observe digital relay trip status.e. Gather diagnostic information about the relay.f. View cause of trip.

5. An optional communication port shall be factory available. Over the communications provided by this port it shall be possible to:a. Communicate at up to 19.2 k baud over the PMAC network.b. Operate the breaker by command.c. Communicate instantaneous rms currents per phase and ground and demand

currents per phase to the PMAC software.d. Communicate breaker status, and type of trip including fault magnitude to the

PMAC software.e. Communicate the digital relay settings to the PMAC software.

6. There shall be two options for control power for the relay:a. Option 1: 120Vac.b. Option 2: 48/125Vdc.

7. Digital protective relays shall be UL listed.

2.2 PMAC SOFTWARE

A. General:1. The PMAC shall be supplied with user friendly application software suitable for

operation on client workstations.2. The software shall be developed by the manufacturer of the monitoring devices and shall

be designed specifically for power monitoring.3. The software shall operate on the following Port operating systems:

a. Network: Microsoft Windows.b. Desktop: Microsoft Windowsc. Internet: Microsoft Internet Information Server.

4. Submit a list of software needed and indicate which packages are being supplied.5. Submit minimum requirements for server and client workstations.6. Describe, in detail, the procedure to be used to allow the PMAC software to support

additional monitoring devices at a future date, including graphics.7. The PMAC software shall be configured, not programmed, and ready to use. This

configuration shall include preparation of all graphics, displays, switchgear elevations, and interactive one-line diagrams. Device status, basic load information, event logs, and data logging shall be available from switchgear elevations.

8. Provide any development keys or programming tools needed by the user to make modifications to the screens, interactive one-line diagrams, or displays.

9. The PMAC software shall support an unlimited number of IEDs.

B. Network:1. The PMAC network shall:

a. Utilize an Ethernet high-speed backbone.b. Interface to the existing Port Token Ring network.c. Support autonomous communications with an unlimited number of IEDs and

metering points.


d. Support multiple concurrent serial communications links.e. Support easy addition of IEDs and metering points.f. Require no proprietary network communication hardware.g. Support automatic alarm call-back for any IED equipped with this capability.h. Support any combination of the following communication channels directly to

IEDs as applicable:1) RS-485.2) RS-232.3) Ethernet (TCP/IP).

i. Support any combination of the following communication protocols directly to IEDs:1) TCP/IP.2) Modbus RTU.

j. Support all of the following features for networked server and client workstations:1) Non-proprietary network protocol, Ethernet TCP/IP, between workstations

and PMAC software and IEDs.2) Windows user and domain accounts.3) Network redundancy between workstations as provided by Windows.

C. Data Storage and Data Sharing:1. Server workstations shall be able to:

a. Autonomously retrieve, from any or all IEDs in the PMAC network, log records of the following type:1) Event log records containing device event information.2) Historical log records containing numerical and Boolean data.3) Historical log records containing waveform data.

b. Autonomously retrieve log records containing system event information.c. Dynamically manage database tables to reflect changes in the configuration of any

IED’s waveform log or data log, with no need to shutdown and restart any software.

d. Allow access to stored data to an unlimited number of concurrent users on an unlimited number of workstations.

e. Allow access to all data logs for the current configuration of each IED, and for previous configurations of each IED.

f. Report the occurrence of events to all user interface software components that are in use for event and alarm indication. To ensure fast event annunciation, all event information shall be made available to the user interface software and the database software concurrently.

g. Support user-initiated changes to its configuration with the following abilities:1) Support on-line changes.2) Suffer no interruption to its operation while changes are being made.3) Require no restart once the changes have been performed.

2. The PMAC software shall support a database storage component that provides the ability to autonomously store historical log records to a Microsoft SQL server database.

3. The PMAC software shall include a database management component that provides the ability to: a. Selectively remove a range of records from the database.b. Archive database files on compact disc or other Port-approved off-line storage

media.


4. The PMAC software shall support standard Windows copy and paste functions from table and chart views of historical and event data logs, making the information available to other Windows applications through the Windows clipboard.

5. The PMAC software shall include a dynamic data exchange (DDE) component that provides the ability to:a. Make real-time information obtained from IEDs available to any number of DDE

software clients.b. Make real-time information obtained from the object processing software

component available to any number of DDE software clients.

D. Object Processing:1. The object processing software shall autonomously collate information (objects) that has

been acquired from multiple sources, using diverse protocols, and allow the information to be processed for user-defined analysis and logging purposes.

2. The object processing software shall be readily upgraded to interface with additional modules and protocols as required, without losing the existing configuration.

3. The object processing software shall provide the following:a. The ability to interface with multiple protocols concurrently, including Modbus

RTU.b. The ability to obtain and process information from an arbitrary number of IEDs

simultaneously.c. The ability to combine setpoints, scheduling, and arithmetic capability in a PC

environment.d. The ability to support time-of-use energy and demand calculations.e. The ability to make real-time information obtained from IEDs available to any

number of DDE software clients.f. The ability to import information from DDE server software.g. The ability to establish priority calls to telephony systems (e.g. pagers, fax) as a

result of a specified system occurrence.h. The ability to launch any software application on any network workstation, as a

result of a specified system occurrence.i. The ability to initiate and manage scheduled communication connections to IEDs.j. The ability to schedule trigger actions throughout the PMAC network.k. The ability to send control commands to any IED in the PMAC network.

4. User Interface:a. The PMAC software shall support an unlimited number of each of the following

types of graphical user interface components:1) User display software.2) Device configuration software.3) Network configuration software.

b. The user display component shall provide the graphical interface to power monitoring, analysis, and control functions through an arbitrary number of user diagrams.

c. The device configuration component shall provide the ability to graphically configure IEDs with software modularity, through an arbitrary number of device setup diagrams.

d. The network configuration component shall provide a graphical representation of the power monitoring network, and the ability to change the configuration of this network so that all PMAC software components can adapt to the new configuration.


e. All graphical user interface components shall support operation in the language of the operating system, with all text strings displayed in the local language.

f. All graphical user interface components shall provide security in the form of user accounts and passwords. In particular, the software shall provide:1) The ability for users to log on by entering a valid user name and password at

a logon display.2) The ability to restrict changes to the account and passwords information to

authorized users.3) The ability to change the account list to add and remove users.4) The ability to change the account list to change passwords.5) No fewer than four levels of security access for an arbitrary number of

users. As a default, each software component shall support the following user authorization levels:a) Guest: The viewer shall be permitted to call any display for viewing,

but no supervisory control functions or functions which change the data base or the behavior of the system shall be permitted.

b) Operator: The operator shall be permitted to perform all the functions necessary for the monitoring and control of the power system. These functions include display requests, supervisory control, data entry, and acknowledgment of alarms.

c) Controller: The controller shall be permitted to perform all the functions of an operator, as well as to make changes to the configuration of any system component, and to perform all display and database maintenance functions.

d) Supervisor: The supervisor shall be permitted to perform all the functions of a controller, as well as to make changes to the user authorization levels.

6) User log-on and log-off processed as events and stored in the system database.

g. All software components shall provide user interface tools common to Windows applications, including scroll bars, a status bar, drop down menus, pop up menus, reducing displays to icons, and enlarging icons to displays.

h. The user display software component shall provide the following:1) The ability to restrict access to diagrams within the user’s authority,

allowing the user to control and view the electrical network using objects in these diagrams.

2) The ability to display any information made available by the communications software component.

3) The ability to create, edit, save, and view diagrams that can:a) Define an area of responsibility (AOR) that is an arbitrary partition of

the network model.b) Support graphic characters, symbols, and pictures.c) Import standard electric utility graphical object libraries including

transformer, busbar, switch, and line segment objects in popular graphical formats, and to import user files from other Windows graphical applications.

d) Create user-configured system diagrams.e) Present an arbitrary number of diagrams at the same time.f) Modify display formats.g) Pan and zoom any diagram screen.


h) View multiple diagrams and selective circuit displays simultaneously, and to manipulate different areas of the same diagram in multiple windows.

i) Use animation, including changing shape, changing color, flashing symbols, and graphic and compressed video files.

j) Enable the user to reduce clutter in a diagram by placing grouped information in separate windows.

k) Provide screen hotspot objects (poke points) for control functions and for opening diagrams, giving multilevel hyperlinking between diagrams.

4) The ability to create, edit, save, and view the following types of display objects:a) Text objects that provide the ability to display static text on the screen

for messages, instructions, and labeling.b) Alphanumeric objects that can display numeric values, Boolean

(status) values, and textual values using dynamic text, analog dials, formatted numerics, bar charts, or scrolling strip-chart displays.

c) Status objects that can display Boolean (status) values, and textual values using dynamic text, or animation via bitmap files or AVI files.

d) Data log viewer objects that can display selected data and waveform log records from the system database.

e) Event log viewer objects that can display selected event log records from the system database.

f) Control objects that provide iconic buttons, toggle buttons, text buttons, and custom buttons.

5) The ability to view data using features that:a) Support selection of log records stored in the system database

according to structured query language (SQL) criteria.b) Support graphical representation of user-selected data values as a

function of time (data trending displays).c) Support selection and display of data values sorted according to time

stamp, source IED, value label, or value.d) Support selection and display of data values within a range of time

stamp, source IED, value label, or value.e) Support selection and display of multiple sets of data values

simultaneously, using distinct colors and line styles to differentiate curves.

f) Display curves that consist of a set of point-to-point line segments drawn using the data set.

g) Support two cursors that indicate data points. The cursors shall be used in conjunction with a numeric display panel which indicates the following:(1) Cursor locations in the scale coordinates of the curve.(2) The mean value between the cursors.(3) The minimum and maximum value between the cursors.

h) Display a movable legend that provides a visual key for the operator. The line style and data marker symbol shall be shown along with a textual descriptor. The user shall be able to interactively position the legend.


i) Support printing of any plot on any network-attached printer, in color or black and white, depending upon printer capability.

j) For waveform displays, provide a button that creates a separate window that displays a histogram of the frequency content (harmonic distortion) of the signal.

k) Support overlays of multiple waveforms or trend graphs.l) Support graphical representation of disturbance information with

reference overlays (e.g. ITIC [CBEMA] voltage tolerance envelope).6) The ability to manage event and alarm information using features that:

a) Display system and IED events stored in the system database according to SQL criteria.

b) Display events sorted according to time stamp, source IED, priority level, cause or effect.

c) Display events within a range of time stamps, source IEDs, priority levels, causes or effects.

d) Support user-defined alarm priority levels for categories of displayed events.

e) Annunciate alarms only at the operating station(s) for which the user interface has been configured to do so.

f) Annunciate alarm conditions, using any combination of the following techniques:(1) Visual indicators (color, flashing title bar).(2) Audible indicators.(3) Computer network messaging.(4) Launching any executable within an operating system shell.(5) Priority call to telephony systems (e.g. pagers, fax).

g) Support user-defined acknowledgment authorization levels for categories of alarms displayed on each or all workstation(s).

h) Accept alarm acknowledgment from authorized users for individual or groups of alarms.

i) Record the user name and time of acknowledgment of an alarm condition.

7) Support to supervisory control of “on/off” (two-state) devices using the following consecutive actions:a) The operator will open a diagram containing the control action(s). If

user authorizations do not permit access by the current user, the selection shall be rejected.

b) The operator will select the control action using the cursor. A point that is successfully selected shall be highlighted.

c) Immediate response to operator requests is required for each activity and each step of an operator procedure. Responses shall comprise changes in the displayed information and/or descriptive messages. The messages shall be concise and explicit. Where an operator error is involved, the system shall provide unambiguous message(s) clearly defining the error.

d) Control actions executed on an IED shall be confirmed by user input through an additional message.

e) In addition to the rejection criteria outlined above, the control request shall be canceled prior to the execution if the CANCEL function is selected.


f) Upon the completion, rejection, cancellation, or malfunction of a control request, the request shall be considered terminated and the device status symbol shall change back to its condition before the point selection.

g) Failures shall result in the automatic deselection of the point; controls shall not be automatically retried.

8) Processing of the following as events and storage in the system database:a) Changes to any user diagram.b) The failure of a device to respond to a supervisory control action.

E. Device Configuration:1. Device configuration shall provide the following:

a. Access to PMAC resources defined by the user’s authorization level determined during log on.

b. The ability to restrict access to configuration of IEDs within the user’s authority.c. The ability to configure IEDs or software components in the PMAC network, with

no need to restart any device or software after configuration.d. The ability to configure an arbitrary number of IEDs at the same time.e. The ability to configure device log formats (parameters to log, depth, and roll-

over) for IEDs with log capability.f. The ability to configure onboard parameter calculations for IEDs with

programmable arithmetic capability.g. The ability to rapidly configure the PMAC Log Acquisition software component to

acquire and store all PMAC data, event, waveform, and system logs from all IEDs in the PMAC network.

h. The ability to undo changes to an IED before they are transmitted to it.i. The ability to find any module quickly (tooltray).j. The ability to configure any IED that complies with the modular architecture using

configuration diagrams with the following features:1) Graphical representation of the IED functionality.2) Cut, copy, and paste functionality from one device to another (or to the same

device).3) Annotatable IED configuration diagrams.4) Display the capabilities of any IED in a toolbar that is dynamically updated.

k. The ability to create frameworks of modules that may be stored on disk and subsequently applied to other IEDs. The graphical appearance of the framework shall be retained.

F. Network Configuration:1. Network configuration shall provide the following:

a. Access to PMAC resources defined by the user’s authorization level determined during log on.

b. The ability to configure site communication parameters for monitoring sites in the PMAC network.

c. The ability to add workstations and sites to the network configuration.d. The ability to configure workstation and site parameters.e. The ability to add IEDs to the network configuration.f. The ability to create logical groups of IEDs.g. The ability to assign a logical name to any IED.


h. The ability to remove workstations, sites, groups and IEDs from the network configuration.

PART 3 - EXECUTION

3.1 INSTALLATION

A. A manufacturer-certified technician shall install and completely check, calibrate, and test all connected hardware and software to ensure that the system performs in accordance with the specifications.

B. Installation shall be supervised and tested by the manufacturer of the system equipment.

C. Power supply and communications wiring connections shall be performed in accordance with the guidelines set out in the product documentation.

D. Current and voltage sensing connections to PMAC instrumentation shall be made using appropriately rated CT shorting blocks and PTs.

3.2 SYSTEM STARTUP

A. Provide on-site system startup including a demonstration of the PMAC instrument capabilities.

B. Provide on-site commissioning of the PMAC instrument to statically and dynamically test the operation of the system throughout the range of operating conditions.

3.3 TRAINING

A. Provide on-site training in operation and maintenance. Conduct a minimum of three 4-hour training sessions (one early morning, one late afternoon, and one make-up) for both operation and maintenance (total of six). Conduct a follow-up training session six months after completion of the project.

B. Training sessions shall include a walk-through of the completed facilities identifying the location, address, and means of access to every new device. Training shall include electronic files, documentation, manuals, and hands-on exercises necessary to enable Port maintenance electricians and engineers to operate and maintain the PMAC system, or reload data and software in the event of a system crash.

C. Offer regularly scheduled factory training for configuration and use of PMAC instrumentation and software.


3.4 TESTING AND REPORTS

A. Upon completion of the system’s installation, an approved representative of the system manufacturer shall be employed to conduct a thorough test of the system and submit a written report of the findings to the Port.

B. Supply an installation test procedure form, to be used during testing and initialed by the Port and the Contractor. The form shall follow a consistent format. The installation tests shall not take place until the Port approves the installation test procedure form. The test procedure shall:1. Include overall test schedule that provides time for unstructured testing.2. Contain test number, name, and description for each test.3. Define each step-by-step procedure, providing the expected response for each step and

providing space for the actual response.4. Contain minimal reference to other documents.5. Be structured so that simpler tests generally run first.6. Provide space for approval by both the Port and the Contractor at each test.

C. Exercise every function of the equipment under test to ascertain the integrity of the equipment. Testing shall include verification of the following:1. The functional operation of each PMAC instrument.2. Transmission of all data from the PMAC instruments and the existing meters to the

PMAC software.3. Operator-initiated control functions through graphic interface.4. Operation of each breaker.5. Report based on induced harmonics.

D. The tests shall be witnessed by the Port. Tests which require device operation that would affect an operating load shall occur between the hours of 1:30 a.m. and 4:30 a.m.

E. At least one week prior to the test, notify the Port in writing that the equipment is ready for testing.

F. In the event that the tests are not successful in the first pass, correct deficiencies and notify the Port at least two days in advance that testing is ready to resume.

G. Document and maintain in a problem log file discrepancies found during testing. Describe the subsequent correction. The Port will verify proper operation of the system and its equipment. Faulty and/or incorrect operation of major functions may, at the discretion of the Port, be cause for suspending or restarting any test, pending correction of that problem. Minor discrepancies shall be noted, corrected, and retested. The Port may also request that other system equipment that may be impacted by a correction also be retested.

H. All system acceptance testing reports shall be submitted to the Port and must be approved before acceptance of the system.


3.5 ADJUSTING

A. Offer field services to assist on-site personnel with reconfiguration of the factory default for site-specific requirements.

END OF SECTION 260913


Documents

SECTION 260913 - ELECTRICAL POWER · Web viewProvide screen hotspot objects (poke points) for control functions and for opening diagrams, giving multilevel hyperlinking between diagrams