EDE III Section J-Draft Attachment J.04 Electrical Power Monitoring System (EPMS) Specification.docx

PART III - SECTION J

ATTACHMENT J.4 - ELECTRICAL POWER MONITORING (EPMS) SPECIFICATION

TABLE OF CONTENTS

TABLE OF CONTENTS

2.3.6 GPS Timing System 2.3.5 Communication Network Architecture 2.3.4 Metering 2.2.3 Tower Switch Enclosure 2.2.1 Work Station 2.2 EQUIPMENT OVERVIEW 1.8.9 Software List 1.8.2 Rack and Enclosure Drawings 1.8.2 Rack and Enclosure Drawings 1.8.2 Rack and Enclosure Drawings 1.8 DRAWING AND DOCUMENTATION SUBMITTALS 1.8 DRAWING AND DOCUMENTATION SUBMITTALS Copyright 2003 and 2005 by The American Institute of Architects (AIA) Exclusively published and distributed by Architectural Computer Services, Inc. (ARCOM) for the AIA Verify that Section titles referenced in this Section are correct for this Project's Specifications; Section titles may have changed.

1.0 GENERAL

1.1 RELATED DOCUMENTS

Drawings and general provisions of the Contract apply to this specification

1.2 SUMMARY

1. This specification defines the requirements for both an Electrical Power Monitoring System (EPMS) and an Electrical Power Control System (EPCS). The EPMS system must be a monitoring system only and must not control any equipment. The EPCS system must meet all of the requirements of the EPMS software with the addition of being able to control breakers and equipment. If required, the system must be both a monitoring and control system and be referred to as Electrical Power Monitoring and Control System (EPMCS).

2. The software platform must be a Supervisory Control and Data Acquisition (SCADA) system capable of both monitoring and control.

3. All written material furnished by the Contractor under this Contract, including electronic documents, must not be copyrighted or require the FAA to obtain special permission for reproduction for any purpose. This must include, but not be limited to, Operations and Maintenance Manuals, Training Material, Shop Drawings, As-builts, Software Code, Software Code Documentation, and Hardware/Software Configuration Documentation. The FAA must have the right to reproduce this information, as well as incorporate it into their internal training programs and documents.

4. Refer to the following related sections or manufacturer’s cut-sheets as well as the drawings for details on quantities of monitoring points and work to be performed.

· Automatic Transfer Switches

· Engine Generators

· Paralleling Switchboards

· Switchgear and Switchboards – Attachment J.2 – Switchboard Specification

· Distribution Equipment – Attachment J.3 – Interior Distribution System Specification

· Uninterruptible Power Supply (UPS) – Government-Furnished Equipment (“GFE”) cut sheets supplied upon submission of task or delivery order

· Mini UPS (MUPS) - GFE cut sheets supplied upon submission of task or delivery order

· Static Transfer Switch (STS) – GFE cut sheets supplied upon submission of task or delivery order

· EPMS/EPCS – paragraph 2.3.3 below

1.3 STANDARDS

As applicable to specific equipment, material, work and testing supplied must be in accordance with the latest edition and amendments of all applicable standards, codes, laws and regulations listed below:

· American National Standards Institute (ANSI)

· National Electrical Code (NEC)

· Underwriters' Laboratories, Inc. (UL)

· Institute of Electrical and Electronics Engineers (IEEE)

· National Electrical Manufacturers' Association (NEMA)

· Federal, State and local codes and laws.

Seismic Requirements - All equipment furnished must be in accordance with UBC, Zone 4.

1.4 QUALITY ASSURANCE

The manufacturer of the equipment must have been regularly engaged in the manufacture of the specified remote devices for a period of at least ten (10) years and demonstrate that these products have been utilized in satisfactory use in functioning systems for similar applications. The manufacturer must have at least ten (10) years demonstrated capability in EPMS/EPCS design, installation, and start-up.

1.5 IDENTIFICATION

1.5.1 Nameplates:

Equipment must be labeled in accordance with the instructions in – Equipment Identification and Marking. Provide samples for review.

1.6 PROJECT MANAGEMENT

The contractor must provide the services of a full-time Project Manager to oversee all EPMS/EPCS related activities, functions, meetings, and deliverables for this Contract. This person shall be the main point of contact for EPMS/EPCS related issues between the contractor and the FAA.

The Contractor must design, develop, and deliver a consistent EPMS/EPCS hardware and software product across all FAA projects, per the FAA’s guidance.

1.7 TRAINING

The Contractor must provide EPMS system training in accordance with the requirements in Section C, Training.

1.8 DRAWING AND DOCUMENTATION SUBMITTALS

The following must be submitted in accordance with general provisions of the contract.

1.8.1 Network Drawings

Detailed EPMS/EPCS network drawings showing all point-to-point connection information must be provided to the Government at the time of or prior to gear approval drawings submittals. These drawings must be based on the provided FAA-approved A&E final design drawings and show all connections within the EPMS network.

1.8.1.1 Wiring Details

The network drawings must show both field and factory installed EPMS/EPCS wiring and must clearly identify any field-installed variances from the factory standards. All field wiring must clearly identify all wire types, length constraints, and routing considerations. All field wiring terminations must have detailed connection information including pin information, wire color, shield termination, gear or device terminal block designations, terminating resistors, and special instructions as installed. Proper shielding techniques and methods must be used on all cabling to provide reliable signals and minimal data transmission errors and delays. Cable routing recommendations must be provided as necessary.

1.8.1.2 Communications

Device communication type information such as IP addresses, MODBUS addresses, and any additional setup information must be clearly listed.

1.8.1.3 Points List and Alarming

A detailed list of all monitored points must be defined in the drawing set. All digital points must have “Alarm On” point high or low detail listed. FAA defined alarm naming must be shown on the points list.

1.8.1.4 Drawing Categories

Drawings must be split up by signal types (communications, timing, sequence of events, points list, etc.).

1.8.1.5 Submittals

There will be three main drawing submittals: Approval, Issued for Construction, and As Built. During onsite validation and testing, drawings must be redlined as necessary. All contractor and FAA redlines must be incorporated into the As Built drawing submittal.

1.8.2 Rack and Enclosure Drawings

Detailed drawings must be included for each custom device enclosure, tower switch enclosure, and server rack. These drawings must include detailed parts lists, elevation drawings with dimensions, interior device mounting details, detailed point-to-point wiring detail, and device designations.

1.8.3 PLC I/O Wiring Diagram

The PLC I/O wiring diagram must breakdown the relationship between hardware and software for all the PLC drops. The breakdown must indicate what is physically connected to each terminal of the PLC then associate that connection to a software address and/or variable name.

1.8.4 COTS Documentation

The contractor must supply all available documentation for each piece of equipment in the EPMS/EPCS system. Documentation must include but not be limited to (if available):

· User’s Guides

· Installation Guides

· Operation and Manuals

· Device Wiring Diagrams and Schematics

· Electrical Characteristics

· Descriptive Literature

· Datasheets

· Replacement Guides

· Troubleshooting Guides

· Quick References

· Handbooks

· Programmers Manuals

· Administrative Manual

· Cybersecurity Guides

Documentation must be submitted in electronic format upon acceptance of the system.

1.8.5 Operations and Maintenance Manual – User Level

The contractor must furnish operating and maintenance (O&M) instructions for the complete arrangement of equipment and devices supplied in the system and for the EPMS/EPCS software application. This manual must document the FAA specific system architecture and software application. This manual must provide user level instruction. No administrative content shall be included in the document.

1.8.5.1 Descriptions of Operation and Maintenance

The operation and maintenance manual must describe in detail the following:

· The hardware components and their function in the system.

· The network architecture

· Types of communications

· Diagram of Data Flows

· List of communication ports and protocols

· Monitored data

· User level operation of all included software

· Connecting with all client types

· Alarm list and description

· Control scheme (EPCS only)

· Recommended maintenance and schedules

· Troubleshooting

· Lowest Replaceable Unit (LRU) List

1.8.5.2 User Level Software Operation

The manual must provide thorough instructions on how to navigate through the SCADA application. It must describe how to locate and operate all included user level features. User level operations are defined as all non-administrative operations of the software as defined by the FAA. At a minimum, the following software features must be covered in detail:

· Active One-lines

· Floorplans

· Alarm and Event Log

· Third Party Device Screens

· Metering

· Legend

· Trending

· Reporting

· Meter Configuration

· Maintenance Mode

· Paging

1.8.5.3 Site Specific Content

The manual must cover all operation of the project/site specific system and software. A generic manual may be developed for all projects/sites if site specific content and operation can be conveyed by describing components, navigation, and theory of operation used to create the custom content in a generic fashion.

1.8.5.4 Maintenance

Maintenance of the EPMS/EPCS shall be limited to the replacement of the major components as LRU items. Self-diagnostics and troubleshooting algorithms must be incorporated to minimize the technicians’ time to troubleshoot the system. The O&M manual must include detailed maintenance descriptions and a list of LRU items. See the training requirements in Section C, the Statement of Work.

1.8.6 Operations and Maintenance Instructions – Administrative Level The contractor must provide an operation and maintenance manual that covers all administrative functions of the hardware and software in the EPMS/EPCS system not covered in the user level O&M manual. This manual must contain the following at a minimum:

· Network drawing file location and update instructions

· Device replacement and configuration instructions

· User security administration instructions (add/remove/edit users and access level)

· Administrative screens and functions

· Debugging tools

· Configuration tools (paging, maintenance mode, meter configuration, etc.)

· Required Windows services list

· Required Software List

· Troubleshooting guide

· Software application startup/shutdown procedures

· Communication ports in use

· LRU configuration

· Firmware upgrade procedures (reference COTS documents if necessary)

1.8.7 Data Backup Plan/Instruction

The contractor must provide a document defining their recommendation of data backup methodology in detail. It must include but not be limited to:

· Filenames and locations of files that contain historical data and are updated on a regular basis (ex: Alarm log files, waveform captures, data log files, database files, diagnostic logs, etc.).

· Recommended backup frequency

· Recommendations for external backup

1.8.8 Server, Workstation, VDT, and GUI Project Configuration Document The contractor must provide a document defining all that is required for a new server, workstation, and VDT to be configured for purposes of consistency in new installation by the contractor or replacement/modification by the FAA. It must include but not limited to:

· Separate sections for server configuration, workstation configuration, and Video Display Terminal (VDT) configuration

· Loading the operating system and any other required applications

· Computer names (per FAA defined template)

· Site specific user account and password setup (per FAA defined template)

· Folder/file structure configuration

· Required drive partitioning

· Site specific passwords

· Communication configuration

· Time sync configuration

· Project/file naming

· IP address schemes (FAA Defined)

· Alarm naming (FAA Defined)

· Point/breaker change of state consistency (aux, trip, etc.)

· Any SCADA FAA project specific parameters or configurations

· Database configuration

· Required software and drivers

· Network drawing file location and update instructions

1.8.9 Software/Driver List

This document must list all software and drivers used throughout the EPMS/EPCS system including versions.

1.8.10 EPMS/EPCS Hardware List

This document must list all hardware used throughout the EPMS/EPCS system including firmware versions and device model numbers.

1.8.11 Ethernet IP Address List

This document must list all EPMS/EPCS device IP addresses by device name.

1.8.12 Computer Name, Username, and Password List

This document must list all computer names, usernames, and passwords for all server, workstation, and VDT computers.

2.0 PRODUCTS

2.1 MANUFACTURERS

Individual components can be from different sources, integrated package and support for the EPMS must be from the single contractor supplying the switchboard.

2.2 EQUIPMENT OVERVIEW

The following equipment must be included and integrated into a complete electrical power monitoring system (EPMS). Refer to Section 2.6 of this document for additional equipment requirements.

· 2.2.1 Work Station (See Section 2.6.2 for additional details)

· Two 240-inch (minimum) monitors

· One computer

· One printer (if required)

· Desk with chair

· 2.2.2 Server Rack (See Section 2.6.3 for additional details)

· Cabinet.

· LAN Switch, 48 port with redundant power supply (depending on the number of devices in the system).

· Server.

· Monitor.

· Global Positioning System (GPS) with antenna, receiver, and accessories.

· Uninterruptable Power Supply (UPS).

· Must accept two separate Power Sources with local disconnecting means. Dual input circuit breakers.

· All devices are dual corded. Dual power distribution strips.

· Pullout keyboard and mouse.

· 2.2.3 Tower Switch Enclosure (If required; See Section 2.6.4 for additional details)

· Wall-mount vented enclosure.

· DIN-mount Ethernet LAN Switch.

· DIN mount mini UPS

· Input Circuit Breaker

· Termination boards.

2.2.4 Custom Enclosures

As required, provide stand-alone enclosure(s) to house EPMS devices such as power quality meters, sequence of events recorders, Ethernet gateways, etc. Enclosures must be wall mountable and include input circuit breaker, terminal blocks, and required power supplies. A mini UPS shall be optional.

2.3 EPMS/EPCS SYSTEM OVERVIEW

2.3.1 Summary

The Electrical Power Monitoring System (EPMS) must gather, display, and alarm on data from various defined remote devices throughout the power system as defined by the FAA. It must be a server/client monitoring system. The EPMS is defined to include, but not to be limited to, remote devices for monitoring, protection, device communication interface hardware, intercommunication wiring, monitoring stations, software configuration, ancillary equipment, startup, and training services.

2.3.2 Turnkey Solution

Once provided with an FAA defined EPMS/EPCS network design the contractor must provide a complete, ready-to-use system that requires no further configuration or setup once commissioned. The contractor must be responsible for the complete process from design to installation and testing.

2.3.3 EPMS/EPCS Software

The EPMS software must be a SCADA based Human-Machine Interface (HMI) system. The EPMS software must not be perform any control functions on equipment unless required by FAA system design. The control system would fall under the EPCS category, and all requirements listed in this document would apply with the addition of Section 2.3, EPCS System Overview. All requirements of the control and monitoring system will be defined by the FAA. The software must have FAA defined GUI screens showing animated power flow one-lines and device diagrams. It must be capable of capturing, logging, and annunciating on system events and device changes of state.

2.3.4 Metering

Strategically placed power quality meters must be utilized throughout the system to capture anomalies. These meters must be capable of real-time power monitoring and waveform capture on sag, swell, transient events, etc. Sequence of events recorders must be utilized to capture high speed changes of state of defined devices with a high degree of accuracy. Circuit breaker trip units with metering and communications capabilities must be utilized for branch circuit monitoring. Communication to other devices must be utilized to bring data in to the software.

2.3.5 Communication Network Architecture

The EPMS must be a Isolated network and GPS timing system. It must not be connected to any other system (unless determined by the FAA to accommodate paging/emailing capability) and must be fully capable of operating independent of any other network.

2.3.6 GPS Timing System

The EPMS must use a GPS timing system to distribute synchronized time to all required monitoring/control devices and computers. This is to ensure accurate time synchronization throughout the monitoring/control system. It must consist of a GPS antenna and receiver for timing distribution.

2.3.7 Battery Backup Power

All specified EPMS hardware (including but not limited to power meters, computers, tower Ethernet switch, and server rack components) must have UPS or battery backed power. This must be in the form of integrated mini UPS devices and/or facility critical power circuits as defined by FAA design drawings.

2.3.8 Client Computers

Client computers must be used throughout the system to provide access to the user interface. The system must include one operator workstation desktop computer with printer. In addition, the system must utilize a touch-screen interface with screens as required by the design drawings. These are referred to as Video Display Terminals (VDT). If required, a wireless tablet solution must be provided.

2.3.9 Integrated EPMS Devices

EPMS devices must be integrated as much as possible into the switchgear and panelboards as required by the FAA design. These devices must come fully wired and installed into the gear. They must be located in compartments such that they are isolated from any exposed bussing. External power circuits shall be provided by the FAA for control power. Gear must have factory wired terminal blocks for easy field connection of control power circuits. If more than one Ethernet based device exists, individual homeruns to server switches preferred Any consolidating switches must have the ability to isolate data flows. If external wiring is needed due to but not limited to PLC I/O, SER inputs, or time sync wiring all wiring must be terminated to terminal strips that are easily accessible for field wiring. Testing must be accomplished by the contractor in the factory to ensure all wiring is installed properly.

2.3.10 Open Protocol

The EPMS will utilize open protocol standards such as Ethernet TCP/IP; Modbus over Ethernet TCP/IP; and Serial Modbus Remote Terminal Unit (RTU).

2.4 TIMING REQUIREMENTS

2.4.1 Time Sync

2.4.1.1 Standard

GPS time standard must be implemented as part of the EPMS for proper sequence of operations and events. GPS timing must be used for maintaining a 1-millisecond resolution throughout the monitoring system.

2.4.1.2 Requirements

GPS timing signal must be transmitted in the form of both Network Timing Protocol (NTP) and Precision Time Protocol (PTP), with PTP being preferred. All devices capable of receiving/synching to NTP must be wired and configured for NTP, including but not limited to the server, workstation, VDT's, meters and third-party equipment. All devices capable of receiving/synching to NTP and PTP must be wired and configured for NTP and PTP, including but not limited to sequence of events recorders, meters, and third-party equipment. If a device is capable of synching to both, PTP must be used. The server, workstation, and VDT’s must all sync to the NTP source.

2.4.2 Time Stamping

All logged and displayed data on any computer in the system must show time stamps that are synched to the GPS source and are formatted the same throughout. Time stamping must occur at the device where the event occurred.

2.4.2.1 High-Speed Stamping

All points indicated on the FAA defined points list associated with the below listed equipment must be time and date stamped to an interval no longer than 1-millisecond sync with all other devices through the use of GPS timing. Necessary EPMS hardware and associated equipment alarm/status contacts must be provided in order to meet the 1-millisecond requirement as defined by the FAA design drawings. The software will show and log event and alarm times out to an interval no longer than 1-millisecond in the sequence in which they occurred.

· Switchboards/Panelboards - Sequence of event recorders and power quality meter.

· Any other specified point wired to either a sequence of event recorder or power quality meter digital input.

2.4.2.2 Polling-Based Timing System

The hardware listed below must have a Polling-based timing system for maintaining an interval no longer than 1-second resolution throughout the monitoring system. The software will show and log event and alarm times out to an interval no longer than 1-second in the sequence in which they occurred. Where possible time stamping must occur at the device where the event occurred. All points indicated on the points list associated with the below listed equipment must be time and date stamped to an interval no longer than 1-second through the use of Polling-based timing. Necessary EPMS hardware and associated equipment status/alarm contacts must be provided in order to meet the interval no longer than 1-second requirement.

· Switchboards/Panelboards – Circuit breaker trip units and meters without millisecond time sync capability

· Generators – Modbus RTU or TCP/IP.

· UPS Systems - Modbus RTU or TCP/IP.

· Static Transfer Switches (STS) - Modbus RTU or TCP/IP.

· Automatic Transfer Switches (ATS) – Modbus RTU or TCP/IP

2.5 COMMUNICATION REQUIREMENTS

Encrypted communication where technically possible should take precedence over unencrypted communications. The EPMS must be able to utilize the following standard communications configurations, as a minimum, at the same time:

1. Modbus TCP/IP communications for meters, trip units, Ethernet gateways, third party devices and equipment, sequence of events recorders, etc. must be utilized if available. CAT-6 Ethernet cable must be used for cable runs of less than 325 feet.

2. All EPMS TCP/IP devices mustsupport IPv6, be static, and adhere to FAA defined IP address scheme.

3. If Modbus TCP/IP is not available for a particular device, Modbus RTU communications must be used. Direct RS485 communications must be used for cable runs of less than 3000 feet . Longer RS485 runs can be achieved with the use of a RS485 repeater. RS485 supports communication with up to 32 devices per communication string. Each string must consist of an approved 22 AWG (or greater) twisted pair shielded cable for RS485 communications.

4. GPS time sync signal distribution must be in the form of PTP and (NTP). The GPS receiver must be a PTP and NTP server.

5. PTP capability is preferred, however if this feature is not available, a network device must be configured as the NTP server. All Computers and third-party devices capable of NTP syncing must be configured to sync to the NTP server. If a device requires an additional Ethernet connection for NTP time synching, a second cable must be run. Time sync signal must be sensed by all devices connected to the time sync base unit reliably.

5. Ethernet communications of either CAT-6 or fiber optic (single mode unless otherwise required or specified) must be supported and must conform to the 802.3 Ethernet communications standards.

2.6 EPMS/EPCS HARDWARE REQUIREMENTS

All EPMS/EPCS hardware components (with exception to the server rack components, workstation components, tower switch enclosure components, and optional custom enclosure components) must be integrated into the switchgear, switchboards, and panelboards per the FAA design.

2.6.1 System Server

System server must ensure a maximum 1-second refresh rate at workstations and video display terminals (VDT) equipped with industrial PCs. The EPMS/EPCS server must include 1 to 2 factory supplied server computers with at least the following features:

· Rack mount server or approved equivalent

· Server class hardware that meets or exceeds recommended hardware and software performance requirements for the applicable operating system and EPMS/EPCS applications.

· Three hot swappable hard disk drives or approved equivalent configured for on board RAID 5 with enough storage capacity to accommodate 2 year’s worth of data accumulation.

· DVD read/write drive, 17-inch rack mountable flat-panel monitor, video card, (2) onboard Gigabit Ethernet ports, remote 101-key enhanced keyboard, mouse, and dual AC power supplies.

· The operating system must be Windows Server with a minimum of 10 user license CALs.

· A minimum of 4 USB ports.

· Server must come equipped with Adobe Reader or approved equivalent.

· Server must meet software Contractor’s recommended requirements for all applications required by EPMS/EPCS software suite.

· Server must provide out-of-band management that includes remote screen viewing fully capable of health monitoring and remote reboot abilities.

· 2.6.2 EPMS/EPCS Workstation

· The EPMS project must include 1 workstation with the following features:

· Business class workstation or approved equivalent complete with desk and chair.

· One computer with minimum quad core 3.0 Ghz, 8 MB Cache CPU with 4 GB RAM, two 250 GB hard drives, DVD read/write drive, two 20-inch flat-panel monitors, dual video card, full-size 101-key enhanced keyboard, optical mouse, and external speakers.

· A minimum of 4 USB ports.

· Microsoft Windows operating system

· Workstation must come equipped with Microsoft Office Professional, and Adobe Reader and Internet Explorer, latest editions or approved equivalents.

· 2.6.3 Server Rack

· The EPMS/EPCS server rack must house the following equipment:

· Cabinet with front and rear access.

· LAN Switch, 24 or 48 port with redundant power supply and patch panel (depending on the number of devices in the system).

· Server on pullout slides.

· Monitor.

· GPS with antenna, receiver, and accessories.

· Uninterruptable Power Supply with aux contacts wired to a nearby I/O device for monitoring UPS and battery status.

· Must accept two separate Power Sources with local disconnecting means. All devices are dual corded. Dual input circuit breakers clearly labeled with voltage level.

· Dual power distribution strips.

· Pullout keyboard and mouse.

· For enclosed rack designs, furnish vents, fans, and/or filters as specified by rack design with enclosed rack

· For open rack designs with adequate convection airflow, no additional vents, fans, or filters are required

· Grounding strips

· Receptacles (where required)

· 2.6.4 Tower Switch Enclosure (if required)

· The EPMS/EPCS tower switch enclosure must be used when Ethernet runs going up the Air Traffic Control Tower exceed the Ethernet cable maximum distance. The tower Ethernet switch must house the following equipment:

· Wall-mount vented enclosure

· DIN-mount Ethernet LAN Switch

· DIN mount mini UPS with aux contacts wired a nearby I/O device for UPS and battery monitoring.

· Input circuit breaker for incoming power feed

· Termination boards

· Fast Ethernet Switches: The EPMS/EPCS project must include Fast Ethernet Switches with the following features:

· Rack mount switch or approved equivalent with 48/24 network ports for 10, 100, 1000 Base-T, 2 SFP transceiver slots, and 1 management port.

· Full duplex, auto sensing, flow control, layer 2 switching.

· Status indicators with link activity, speed, collision status, duplex mode, power, redundant power.

· Redundant power supply.

2.6.5 Printers

Provide 1 color inkjet or color laser network printer.

2.6.6 Touch-Screen Monitors, VDTs

The EPMS/EPCS project must include touch-screen monitors with industrial PCs meeting the minimum requirements (quantities determined for each project):

· 20-inch analog resistive or capacitive touch-screen.

· 1280 by 1024 resolution 256 colors (minimum). Resolution must support the software requirements.

· Dual core, 2.0 GHz CPU (minimum)

· 4 GB RAM (minimum)

· Windows operating system.

· 120GB hard drive.

· 10/100 Mbit/s Ethernet connection (minimum).

· 24, 48 or 125 VDC, 120 VAC.

2.6.7 Mobile Tablet

The EPMS graphics screens must be capable of being viewed on a mobile tablet. The tablet must have a touch interface for navigating screens and a battery life with a minimum of 2 hours. Additional tablet specifications shall be determined by the contractor. If custom screens are required for proper viewing on the tablet, these must be developed and tested as well. Mobile tablet must meet the security requirements as specified in attached J.05 Cybersecurity Requirements for network access.

2.6.8 Distributed Processing Modbus Masters and Protocol Converters The EPMS/EPCS project must include the required Distributed Processing Modbus Masters and Proprietary Protocol Converters as indicated on the drawings.

2.6.9 Power Quality Meter

2.6.9.1 Basic Measurements

· Revenue Grade metering that meets or exceeds ANSI C12.20 Class 0.2 and IEC687 (Accuracy)

· Instantaneous 3-phase voltage, current, frequency, power factor.

· Energy: bi-directional, absolute, net, time-of-use, loss compensation.

· Energy Demand: rolling block, predicted, and thermal.

· Harmonics: individual harmonic distortion up to the 63rd or better.

· Transient detection: 17us at 60Hz, and sag/swell recording or better.

2.6.9.2 Basic Inputs

· Five voltage inputs capable of measuring three phases, neutral, and ground for 480/277V and 208/120V systems.

· Four current inputs capable of measuring three phases, and neutral.

2.6.9.3 Basic Compliance Monitoring

· ANSI C37.90.1 (Surge Withstand)

· ANSI C62.41 (Surge)

· ANSI/IEEE C37.90.1 – Surge Withstand

· IEC 1000-4-4 – Fast Transient

· IEC 1000-4-5 – Surge Immunity

· IEC 868 – Flicker Meter

· IEC 61000-4-15 – Flicker Meter

· EN 50160 FLICKER AND COMPLIANCE MONITORING

2.6.9.4 Basic Event Recording

· Disturbance Waveform Capture

· Steady State Waveform Capture

2.6.9.5 Basic Communication Features

· Modbus TCP/IP

· Synchronization with other Meters via GPS clock or other of equal resolution.

2.6.9.6 IEEE 1159 Power Quality Monitoring Needs

· Impulsive transient detection to 1ms duration

· High, medium, and low frequency oscillatory transients

· Instantaneous sags and swells

· Momentary sags, swells, and interruptions

· Temporary sags, swells, and interruptions

· Long duration interruptions, overvoltages, and undervoltages

· Voltage Imbalance

· DC Offset

· Harmonics (to the 100th order)

· Interharmonics (0-6 kHz)

· Notching

· Broad-band noise

· Voltage fluctuations (flicker)

· Power frequency variations

2.6.9.7 Advanced Features

· Trending analysis, with the potential option for forecasting

· Memory logging

· Min/max/average log

· Alarm/event log

· Synchronization with other PQMs (GPS clock or cross-triggering)

· Adaptive waveform capture

· Disturbance waveform capture

· Steady-state waveform capture

· Waveshape alarm

· Disturbance alarm

· Digital input/output capability with alarming

· Setpoint-driven alarms (voltage, real and apparent power, current, power factor)

· IEC, ANSI accuracy compliance

2.6.10 Sequence of Events Recorder

Sequence of Event Recorders meeting the following requirements (Note any exceptions taken with a detailed description):

· I/O: Distributed I/O modules.

· Event Time Stamping: Events must be recorded to the 1 millisecond accuracy and must be logged in the sequence in which they occurred.

· Logging: Logging must take place onboard. SCADA software application must access the onboard log to retrieve events. Device must retain events onboard when device power is lost.

· Communications must beEthernet based connection.

· Time Sync: The module must be capable of receiving a PTP or NTP time syncing signal with PTP being the preferred method.

· Debounce: The module must contain circuitry or software filter to ensure that “chatter” or “bounce” encountered during contact change does not initiate erroneous alarms.

· Power: 24, 48 or 125 VDC, 120 VAC

· On-board Event Memory: 5000 events minimum

· Configuration: Must be configurable via internal web server/web page interface along with a serial connection over RS-232.

· Operating Conditions: Operating Temperature: -20 C to +85 C, Humidity: 0 to 95% non-condensing

· Standards: Device must meet all international standards for Electromagnetic Emissions FCC Part 15 Subpart B, Class A Class A Digital Device, Radiated Emissions EN55011 (CISPR 11) Radiated/Conducted Emissions (Group 1, Class A) EN55022 (CISPR 22) Radiated/Conducted Emissions (Class A) EN50081-2 Electromagnetic Compatibility, emissions.

2.6.11 Ethernet Gateway

· Communications: Ethernet gateway must provide means to convert a 10/100BaseT Modbus TCP/IP to a Modbus RTU over RS-485.

· Configuration: The gateway must be configurable via web interface along with a serial connection over RS-232.

· Power: 24 Vdc or 120 Vac

2.6.12 GPS Time Sync System

· GPS system must be comprised of receivers, cables, antennas and associated mounting hardware and must be provided and configured for interfacing to the EPMS hardware. GPS hardware is to be provided by the EPMS supplier. GPS receiver must be mounted in the server rack. Antenna must be field mounted by installation contractor.

· Receiver must provide at a minimum PTP, and NTP output.

· Contractor must supply in-line antenna cable surge suppressor. This field will be installed by an installation contractor.

2.6.13 Mini UPS

· Battery Backed Power: All necessary and specified EPMS hardware (including but not limited to power meters, computers, tower ethernet switch, and server rack components) must have UPS or battery backed power for a minimum of 15 minutes on total loss of commercial power. Server rack equipment (server, ethernet switch, and GPS receiver) must have UPS or battery backed power for a minimum of 30 minutes on total loss of commercial power. This must be in the form of integrated mini UPS devices and/or facility critical power circuits as defined by FAA design drawings.

· Monitoring: UPS must have monitoring capabilities including but not limited to “Load Not Supported by UPS" and "Battery Fault". These must be wired to a terminal block.

· Maintenance: All mini UPS’s must have the capability to perform a self-test to verify proper UPS operation.

2.6.14 Programmable Logic Controls (PLCs)

EPCS PLCs must meet the following minimum requirements:

2.6.14.1 Power Supply Module

All PLC drops must be capable of accepting the DC voltages 5V, 24V, 48V, and 125V and AC voltages 24V and 120V as the supply power of the entire drop.

2.6.14.2 Input modules

· All PLC drops must be capable of accept the DC voltages 5V, 24V, 48V, and 125V and AC voltages 24V and 120V as Discrete Digital inputs.

· The system must contain circuitry to ensure that “chatter” or “bounce” encountered during contact change does not initiate an erroneous signal.

2.6.14.3 Output modules

· All output PLCs must activate by either applied voltage or dry-contact closure.

· Dry-contact closure must be either solid state (ex. triac) or relay contacts.

· Relay contact type outputs must be voltage free, isolated from ground, and fully independent from each other, with a minimum contact rating of 2 amps.

· Output PLC using applied voltage as its output must have modules capable of producing DC voltages 5V, 24V, 48V, or 125V or AC voltage 24V, 48V, or 125V.

2.6.15 Warranty

Servers, workstations, video display terminals, printers, and switches must be covered by warranties in accordance with the provisions of Section H.

2.7 EPMS/EPCS SOFTWARE REQUIREMENTS

2.7.1 Overview

The EPMS/EPCS SCADA software platform must be commercial off-the-shelf (COTS), requiring no custom code development. The EPMS/EPCS server software must be designed on a Microsoft Windows-based platform and have on-line full-screen editing to facilitate the programming and monitoring of the system. The EPMS/EPCS server, application client (thick client), and web-based (thin client) locations will allow the monitoring of vital system parameters and provide a scalable system for future expansions without replacement of the EPMS/EPCS hardware or software. The proposed SCADA software platform must support unlimited web-based and thick clients and unlimited monitoring points for server and clients.

The SCADA software application must communicate with all monitored devices to gather data for purposes of displaying, trending, logging, and alarming data. The application must also be capable of remotely controlling breakers and devices in the system if required by the FAA (see Section 2.3 EPCS/EPMS).

2.7.2 Configuration

The Contractor must maintain a standard configuration across FAA SCADA projects. Software configuration standardization must also be maintained for the following:

· Point/breaker change of state consistency (aux, trip, etc.)

· Project/file naming

· User account, access levels, and site specific password setup (per FAA definition)

· Database configuration

· Alarm nomenclature, behavior, and priority (per FAA definition)

· Project specific parameters GUI one-line device symbols, colors, fonts, animation, behavior, navigation, third party device screens, etc.

2.7.3 Server and Clients

2.7.3.1 Configuration

Server GUI must not be used on a frequent basis, only for configuration purposes by an administrator. Servers must be configured so that it only can be accessed by an admin. Users can only access server through a client from EPMS workstations. Server must have auto-reboot capability enabled so that upon return from a power failure, the server automatically reboots, logs in, and all necessary programs automatically launch without user intervention. The server must lock itself out immediately.

The Contractor must maintain a standard server, workstation, and VDT configuration across FAA projects. The FAA will provide a template to achieve consistency in the following areas:

· Computer names (per FAA defined template)

· Site specific user account, groups, and password setup (per FAA definition)

· IP address schemes (per FAA definition)

Configuration standardization must also be maintained for the following:

· Folder/file structure configuration

· Required drive partitioning

· Communication configuration

· Time sync configuration

2.7.3.2 Distributed Processing and Redundancy

SCADA software processing must be capable of being distributed across multiple processors and/or servers for higher redundancy and/or performance. Software must be configured to distribute processes across multiple processors as a standard configuration. If required by the FAA design, dual servers with redundant processes on both servers must be utilized. A copy of the software must run on the second server in a hot standby configuration.

2.7.3.3 Clients

The EPMS software must have the main application running on the server machine and be configured for both web-based clients and thick clients (if available). Dedicated EPMS workstations and VDT’s must be configured as thick clients. If tokens are required, they must be soft key tokens, as opposed to physical tokens. The web-based clients must require no loading of software to view all the EPMS screens, data, meter configuration, and waveforms. Any computer that is connected to the EPMS network and has a properly configured IP address and compatible browser must be able to connect as a web-based client. The web-client at a minimum must be fully compatible with the latest version of Microsoft Edge.

2.7.4 Monitored Data

The SCADA software must communicate to all monitoring devices in order to gather data for purposes of displaying, trending, logging, and alarming data. These devices include breaker trip units, protective relays, third party equipment, and any digital meters on the electrical distribution system. Additional analog and discrete statuses required to be monitored as required by the FAA system design must be tied back to I/O units and communicated back to the power monitoring software.

The EPMS software must be able to take incoming monitored data and perform mathematical and logical operations for control, viewing, logging or alarming.

2.7.5 Graphics and Display

The EPMS SCADA software must include a graphical package that allows specific configurable custom graphic screens to match customer one-line drawings and floor plans to match facility design drawings as agreed upon by the FAA. They must accurately and clearly depict real-time power flow throughout the monitored portion of the system. FAA will define colors, naming/numbering schemes, and general arrangement of screens. The software must be capable of supporting any number of screens and the FAA must not be limited in the number of screens requested. Screens must have a consistent look and navigational structure. This custom interface will be referred to as the SCADA application.

2.7.5.1 Screens

The EPMS software must provide the following screens as standard in the software.

· Active One-lines

· Alarm Log

· Event Log

· Floor Plans

· Third Party Devices

· Legend

· Network Drawings

2.7.5.2 Template

Throughout the user interface the screens must have a consistent template that contains the following information listed below. Exceptions may be made as necessary if approved by the FAA.

1. Minimum of last three unacknowledged alarms sorted by active then inactive.

2. A compact navigational scheme that is intuitive and user-friendly for both touch screen and mouse interfaces. Touch screens must provide a 1 touch accessible on screen keyboard. One or two left click/touch access must be provided to the following at a minimum:

a. One-lines

b. Floorplans

c. Alarm logs

d. User Login

e. Legend

3. Small FAA defined logo

4. Site name

5. Time and date

6. Currently logged in user

2.7.5.3 Navigation

The SCADA application must incorporate an intuitive and user-friendly navigational control scheme that allows the user to navigate between screens. The navigational controls must be designed for use with both pointer (mouse) and touch screen interfaces. They must have a consistent look throughout the application so that the function of each control is clear before it is activated by the user.

2.7.6 Active One-line

2.7.6.1 Overview

The Active One-line must be a representation of the power system’s one-line drawing that is animated and colored based on logical combinations of monitored data throughout the system.

2.7.6.2 Components

1. Equipment and Gear – Representation of switchgear, switchboards, panelboards, and third party devices typically containing buses, breakers, meters, and other symbols enclosed in an identifying border and clearly labeled.

2. Symbols – Representation of breakers, switches, fuses, meters, third party equipment, transformers, or other various devices throughout the power system.

3. Power Flow Lines – Representation of power conductor paths between pieces of gear and equipment.

4. Buses – Representation of busing inside of a piece of gear or equipment.

2.7.6.3 Animation

1. Power Flow Lines and Buses

· Power flow lines and buses must be colored based upon whether or not they are in one of three states: Red for Energized, Green for De-Energized, and Magenta for Unknown.

· Any line or bus that is not monitored, cannot be calculated, or cannot be logically determined must be colored black.

· Lines crossing between screens must be shown on both screens and animated identically. Navigation must be provided to follow the continuation of the lines between screens. Labels must also be provided stating the destination gear/device at the beginning/ending points of the lines.

· Power flow lines and buses are animated based on metered values and/or the logical combination of metered values and breaker states.

2. Symbols

· If possible, symbols must be colored and animated based on the state of the monitored device as defined by the FAA.

· Breakers and switches are animated with a standard breaker symbol depicting open/closed/tripped/withdrawn state.

· UPS, Static Transfer Switches, Automatic Transfer Switches, and Generators must be colored and animated according to their internal operation as defined by the FAA. Third party device states must be provided in dynamic text form near the respective symbols.

· Transformers must be colored to match connected power flow lines.

· All other symbols’ animation will be defined by the FAA as required.

· Any symbol or bus within a symbol whose state cannot be determined due to loss of communication or other reasons must be animated in such a way as to clearly identify it is in an unknown state.

· Any symbol or bus within a symbol that is not monitored, cannot be calculated, or cannot be logically determined must be colored black.

· Symbols must be standard electrical symbols.

4. Power Flow Methodology

· All power flow lines and buses must be animated based on either voltage read from a meter, under voltage relay, or other voltage sensing devices directly monitoring them whenever available. Lines directly tied to a third party device input or output must be animated based on metered values available from the device.

· No lines or buses may be animated based upon a device whose communication rate does not allow the animation refresh rate to meet the minimum requirements for real-time monitoring as specified in section 3.7(E)(10) Refresh Rate.

· Lines and buses not directly metered must be animated using logical combinations of metered buses and breaker states. Logic must continue through the one-line until a metered bus or device is reached.

· Where possible, animated lines and buses must derive their state not only from devices upstream but downstream devices as well.

· An animated line or bus state that cannot be determined due to device communication failures or conflicting logical states must display a third animated state and have the color Magenta. In the case where multiple voltage sources can animate a line or bus and the sources conflict (energized, de-energized, or unknown) the following precedence must be followed:

· If at least one source is energized animate as energized.

· If no source is energized and at least one is unknown animate as unknown.

5. Scripting Active one-line screens must have the capability to have animation driven based on custom written code where necessary to properly animate the state of a line, bus, breaker, device status, alarm message, or other visual indication.

2.7.6.4 One-line Screens

1. Detailed one-line screen

· The SCADA application must have a detailed representation of the power system one-line including power flow, gear buses and interconnection, breakers, third party devices and statuses, meter locations/values, etc. as defined by the FAA. This must be based on the FAA defined one-line and must include all equipment within the power system.

· One-line screens must contain as many devices as possible while still maintaining a neat, uniform, and readable appearance. As necessary, multiple screens may be used to divide the power system in to manageable sections. The FAA must be involved in the screen division process. Screens must be linked together for ease of navigation.

· Power flow lines must be shown between all monitored pieces of equipment. Switchboards, panelboards, switchgear, and third party devices must have borders around them and must be clearly labeled. They must link to the respective FAA floor plan drawings. Third party devices must be clearly labeled and link to their respective detailed screens. Breakers must be clearly labeled with FAA defined names and breakers with metering must have links to their respective detailed screens. Identify “Normally Open” breakers with the text “N.O.”. Power meters must have symbols shown on the one-lines and must link to their respective detailed screens.

· The power flow methodology as described in Section 3.7(E)(c)(c) Power Flow Methodology must be used to animate detailed one-lines. Meters, UVR's, and analog voltage readings must be used to animate lines/buses if available as defined by the FAA design.

2. Overview screen

· The SCADA application must have an overview screen(s) representing the whole power system and animated power flow in a simplified block diagram format as defined by the FAA. It must show at a minimum animated gear energized states, third party device statuses, and power flow lines between them.

· The whole power system must fit on one screen unless otherwise agreed upon by the FAA. Switchboards, panelboards, switchgear ,and devices must be clearly labeled. Each switchboard, panelboard, switchgear, and device box must be linked to their corresponding detailed one-line screen. Third party device status text must be clearly shown near each device.

· Eachdepicted equipment must have an FAA-defined abnormal state (any breaker in gear abnormal state – open/closed/tripped, third party device in an abnormal state, etc.). If any abnormal condition exists for a piece of gear or device, it must indicate this clearly.

· The power flow methodology as described in Section 3.7(E)(c)(c) Power Flow…