SPECIFICATIONS - Power Rich System

lynxfatkidneyedΔίκτυα και Επικοινωνίες

26 Οκτ 2013 (πριν από 3 χρόνια και 5 μήνες)

329 εμφανίσεις


SCADA Expert
Power RICH System
-
Enterprise
Edition

2013 R1 Release Notes

Page
1

of 6



















SPECIFICATION

FOR THE

POWER MONITOR

and CONTROL

SYSTEM

(PMCS)

SCADA (Supervisory Control And Data Acquisition)






Revision Date:

10/26/2013 8:04 AM




SCADA Expert
Power RICH System
-
Enterprise
2013 R1 Release Notes

Page
2

of 6

SPECIFICATION for

POWER
MONITOR and CONTROL
SYSTEM

TABLE OF CONTENTS

Paragraph





Title





Page

1.0

SCOPE

................................
................................
................................
................................
.....

5

1.1

General

................................
................................
................................
...................

5

1.2

Work to be provided by Seller

................................
................................
...............................

5

1.2

The work includes, but not
limited to, the items listed below:

...............................

5

1.3

Work to be provided by THE BUYER

................................
................................
.................

6

1.3.1

Enclosure
See Section 4.4 for Seller specifications

................................
................

6

1.3.2

Cabling

................................
................................
................................
....................

6

1.3.3

Equipment Power

................................
................................
................................
....

6

1.3.4

Hardware

................................
................................
................................
.................

6

1.3.5

Configuration of Protection Devices

................................
................................
......

6

2.0

CODES AND STANDARDS

................................
................................
................................
.

6

3.0

QUALIFICATIONS

................................
................................
................................
...............

8

4.0

TECHNICAL REQUIREMENTS

................................
................................
........................

8

4.1

Description of Services

................................
................................
...........................

8

4.2

Design Requirements

................................
................................
..............................

8

4.3

Placement

................................
................................
................................
................

8

4.4

Enclosure (in areas with no environmental control)

................................
...............

9

4.5

Spares

................................
................................
................................
......................

9

4.6

Warranty

................................
................................
................................
.................

9

4.7

Field Qualify Control (Installation & Commissioning of PMCS)

..........................

9


SCADA Expert
Power RICH System
-
Enterprise
2013 R1 Release Notes

Page
3

of 6

4.8

Packaging, Shipping, and Storage

................................
................................
........

10

4.9

Equipment Marking

................................
................................
..............................

10

5.0

INSTALLATION

................................
................................
................................
.

10

6.0

TESTING

................................
................................
................................
...............................

11

6.1

Factory Testing

................................
................................
................................
.....

11

6.2

Manufacturer’s Certification

................................
................................
.................

11

6.3

Training

................................
................................
................................
.................

11

6.4

Administrative Training

................................
................................
................................
.......

12

7.0

DRAWINGS AND SUBMITTALS

................................
................................
....................

12

8.0

MANUFACTURING AND PERFORMANCE DATA REQUIRED

.............................

13

8.1

Submittals by Seller

................................
................................
..............................

13

9.0

TECHNICAL DATA

................................
................................
................................
............

15

9.1

PMCS Operations

................................
................................
................................
.

15

9.2

PMCS Software

................................
................................
................................
....

16

9.2.3

Connectivity / Historian Highlights
................................
................................
.....................

19

9.2.4

Reports

................................
................................
................................
................................
...

21

9.2.4.1 Data Export Tool

................................
................................
................................
..

21

9.3

Drawing Graphic Capability

................................
................................
.................

32

9.4

System Component Detailed Specifications

................................
.........................

33

9.4.A 2013 R1 Additional Features

................................
................................
................................
.

34

Power RICH System
-
Enterprise Edition now part

of StruxureWare Software
Applications and Suites

................................
................................
.........................

34

Server Improvements

................................
................................
................................
......

34


SCADA Expert
Power RICH System
-
Enterprise
2013 R1 Release Notes

Page
4

of 6

Integrated Server Backup

................................
................................
................................
..

35

Driver Developments

................................
................................
................................
......

36

Dynacard Data Export Tool

................................
................................
............................

36

Schneider Electric Rod Pump Controller driver

................................
...........................

36

User Interface

................................
................................
................................
...................

37

New and Improved Symbol Library

................................
................................
..............

39

Power RICH System
-
Enterprise Edition Mobile

................................
..........................

39

Example Projects

................................
................................
................................
.............

40

9.5

Product Summary

................................
................................
................................
.................

41

See 2013 R1 Added features above.

................................
................................
................................
.

41

9.6

Minimum System Devices

................................
................................
....................

45

9.7

Minimum Display Parameters from Devices

................................
........................

46

9.8

PMCS Equipment supplied by Seller

................................
................................
...

47





SCADA Expert
Power RICH System
-
Enterprise
2013 R1 Release Notes

Page
5

of 6

SPECIFICATION for

POWER CONTROL AND MONITO
RING SYSTEM

1.0

SCOPE

1.1

General


1.1.1

This specification covers the furnishing, installation, and testing of a
complete, ready
-
for
-
operation Power Control and Monitor System
(
PMCS
).

1.1.2

Seller shall bear the responsibility that the equipment has been designed,
fabricated, and tested in accordance with all codes, standards, and
governmental regulations applicable and performs under the conditions
and to the stands specified herein

1.1.3

No departure shall be made from codes, standards, regulations, or this
Specificatio
n unless waived or modified in writing by THE BUYER.
Seller shall provide a statement as to compliance with this Specification
without exception and/or if there are any exceptions these shall be
described in detail and included in Seller’s proposal. Sell
er shall add a
statement that no other exceptions are taken to this Specification


1.2

Work to be provided by Seller

1.2

The work includes, but not limited to, the items listed below:

a.

Furnish, install, and commission a complete, ready
-
for
-
use ABB Power
RICH

System, a Power Control and Monitoring System or THE BUYER
approved equal. The
PMCS

shall monitor, through metering, all
protective devices, analog (4
-
20ma) devices, and discrete devices (digital
on/off). The protective and sensor devices monitored may
be in high
voltage,
medium

and low voltage switchgear and other substation areas.
This system shall include, but is not limited to software, IO Server (Host,
if only one), network hardware and software for remote communications
with other substations and
users, UPS, device hardware for the IO Server,
communication converters, printers, testing, correcting, startup at site(s),
commissioning (testing for customer sign
-
off), training of operator and
administrative personnel, after sale technical support, and
graphical
screens. All graphical screens and screen transition must be approved via
a sign
-
off by the THE BUYER prior to completion and installation at the
customer’s site(s).



1.2.2

The work also includes all items necessary or usually supplied for sale,

efficient,
continuous, and convenient operation of the equipment within the scope of this
Specification, whether or not, such items are specially referred to in this
Specification.


SCADA Expert
Power RICH System
-
Enterprise
2013 R1 Release Notes

Page
6

of 6


1.3

Work to be provided by THE BUYER

1.3.1

Enclosure

See Section 4.4 for Seller

specifications

1.3.2

Cabling

All communication cabling and network cabling between communication
converters and the substation relays, circuit breakers, meters, and switches to be
performed by THE BUYER

or BUYER’s assignment
. Installations of any
antennas, as
necessary, are performed by THE BUYER.

1.3.3

Equipment Power

The 120VAC power required for the IO Server computer, UPS, and the
communications converters.

1.3.4

Hardware

All protection devices, sensors, circuit breakers, meters, and switches used the
project.

1.3.5

Configur
ation of Protection Devices

All of the protection device configuration or other remote device configuration
will be by THE BUYER or designated by THE BUYER.


2.0

CODES AND STANDARDS

2.1

It is not THE BUYER’s intent to specify all details of construction, but the
i
nstalled equipment shall in all respects conform to high standards of engineering,
design, materials, construction, and workmanship and shall be capable of
operating efficiently and satisfactority under the service conditions stated in this
Specification.


2.2

The design of the equipment and accessories shall be as recommended by Seller
and shall comply with all applicable federal, state, and local statues, in addition to
the regulations, specifications, and requirements in effect at the time of purchase
order
of the following codes and standards, as applicable:


ANSI


American National Standard Institute

ASTM


American Society of Testing and Materials

FCC


Federal Communication Commission


SCADA Expert
Power RICH System
-
Enterprise
2013 R1 Release Notes

Page
7

of 6

ICEA


Insulated Cable Engineers Association

IEEE


Institute of Electrical

and Electronic Engineers

NEC


National Electrical Code

NEMA


National Electrical Manufacturers Association

NESC


National Electrical Safety Code

OSHA


Occupational Safety and Health Administration

UL


Underwriters’ Laboratory


2.3

The
PMCS

shall comply with the applicable portions of ANSI/IEEE 802.3 and
802.11, the Ethernet standards and NEMA. All computers (IO Servers and any
network Nodes or Clients) shall comply with FCC emission standards specified
in Part 15, Subpart J for Class A.

2.4

Al
l computers (IO Servers and any network Nodes or Clients) shall meet the
Microsoft Windows NT certification test software program, available from
Microsoft’s Web Site at no charge. All computers must meet this test even if
they operate with other Windows
versions.

2.5

The
PMCS

Database shall comply with standards for SQL (Structured Query
Language) utilized with database acquisition and exchange of data
(Client/Server) and ODBC driver support. The software shall provide network
servers that include data excha
nge data with other software applications, such as
Microsoft Excel or Corel Quattro Pro spreadsheets. The software shall meet OLE
and OPC (OLE for Process Control)
and OPC
-
DA, OPC
-
HDA, OPC
-
A&E,
as
outlined by the OPC foundation. The software shall provide

direct interfacing to
any supplied Dynamic Link Library (DLL) utilizing all the DLL run
-
time
functions. The software shall meet all of the list below Data Exchange method
standards:

SQL client/server

ODBC client/server

MAPI

Email

HTML

Windows API

Native d
BASE

DLL

ASCII files

TCP/IP

Serial

OPC
Client &
Server

2.6

These codes, standards, and regulations set forth minimum requirements that may
be exceeded by Seller if, in their judgement and with THE BUYER’s acceptance,

SCADA Expert
Power RICH System
-
Enterprise
2013 R1 Release Notes

Page
8

of 6

superior or more economical designs or mate
rials are available for successful and
continuous operation of Seller’s equipment and as required by this Specification.

2.7

In the event of any apparent conflict between standards, codes, or this
Specification, Seller shall refer the conflict to THE BUYER for

written
resolution. THE BUYER’s resolution shall be binding.

2.8

Seller shall provide a list of major codes and standards, with their effective dates,
actually used for the construction of Seller’s equipment.

2.9

The equipment, material, and services furnished s
hall comply with and not
prevent THE BUYER’s compliance with all applicable standards of the Code of
Federal Regulation, Title 29, Chapter XVII, OSHA, Department of Labor, Part
1910 (Occupational Safety and Health Standards) and Part 1926 (Safety and
Healt
h Regulations for Construction).


3.0

QUALIFICATIONS

The manufacturer of the equipment shall be regularly engaged in the manufacture of the
specified
PMCS

for at least five (5) years and demonstrate that these products have been
satisfactorily used in functional systems for similar applications. The manufacturer shall
have at least five (5) years demonstrated capability in
PMCS

design, installation, and
st
artup.


4.0

TECHNICAL REQUIREMENTS

4.1

Description of Services



The application and project requirements for the equipment covered by this
Specification are described in Section 9.


4.2

Design Requirements

4.2.1

Project unique data, ratings, and requirements shall be as sp
ecified in
Paragraph 9.1. These ratings shall be the basis of Seller’s guarantee of
performance.

4.2.2

Equipment shall be fabricated and equipped with accessories in
accordance with Seller’s standard practices when such practices do not
conflict with this Speci
fication.

4.3

Placement

4.3.1

The IO Server or Host system shall be housed to facilitate rapid access to
case for maintenance. The monitor and pointing device shall be oriented
to facilitate ease of use.


SCADA Expert
Power RICH System
-
Enterprise
2013 R1 Release Notes

Page
9

of 6

4.3.2

Clutter and debris shall be avoided so access is not restrict
ed to the IO
Server or Host and the communication wiring.

4.4

Enclosure (in areas with no environmental control)

The IO Server
(s)

or Host shall be enclosed in a NEMA 12 computer cabinet. The
enclosure shall be provided with air conditioning, when equipment re
quired,
controlling temperature extremes.

4.5

Spares

A spare parts list shall include, but not be limited to, the following: any line
drivers (MODEM), converters, power supplies, network interface cards (NIC),
communication boards, surge protection, uninterru
ptible power source (UPS),
and other miscellaneous hardware as spare parts that are viewed as necessary for
a MTTR (Mean Time To Repair) of fifteen (15) minutes.

4.6

Warranty

4.6.1

Seller shall warrant the equipment hardware and software supplied from
date of final

acceptance. The warranty shall include the following
provisions:

a.

One (1) year free software update service with optional annual
renewal for a set fee.

b.

One (1) year free telephone technical support to trained
(administrative class) personnel with optional

annual renewal for a
set fee.

c.

Warranty on all hardware supplied under this system shall be for
one (1) year from date of final acceptance.

4.7

Field Qualify Control (Installation & Commissioning of
PMCS
)

4.7.1

Furnish the services of a manufacturer’s representative

for a minimum
period of three 8
-
hour days to assist the customer in start
-
up and testing of
the system. The representative shall be factory
-
trained and shall have a
thorough knowledge of the software, hardware, and system programming
and functionality.
The manufacturer’s representative shall provide not
less than the following services:

a.

Setting all address of all field devices.

b.

Verifying and troubleshooting the integrity of the data lines to the
field devices.

c.

Correcting any data line problems and see th
at any defective and
non
-
functioning equipment is replaced by those responsible for its
replacement.

d.

Coordinating and solving any possible warranty problems (punch
lists items).


SCADA Expert
Power RICH System
-
Enterprise
2013 R1 Release Notes

Page
10

of 6

e.

Configuring the
PMCS

software to match all the field devices.

f.

Providing all te
sting, corrections, and retesting and providing
written documentation that the entire system is performing to
maximum standards to meet all requirements of the contact
documents. This shall be in the form of a checkoff list
(commissioning sign
-
off sheets)

with all functions and parameters
to be checked. The device serial number, model ID, catalog
number, and parameter tag identification, along with the initials of
the assigned contract officer and manufacturer’s representative
shall be delivered.

4.7.2

Seller s
hall provide three (3) signed copies of the certification
(commissioning sign
-
off sheets described in Section 4.7.1, f) before final
payment is made.

4.8

Packaging, Shipping, and Storage

4.8.1

All equipment shall be adequately prepared for shipment and for a one
-
yea
r period of storage.

4.8.2

After completion of factory assembly and testing, the equipment shall be
disassembled into the minimum number of parts practicable to facilitate
rapid installation.

4.8.3

Seller shall provide storage and handling instruction including
descri
ptions for periodic inspection and/or storage maintenance to
ascertain that no deterioration will occur during storage. One set of these
instructions shall be fastened securely to the outside of each shipping unit.

4.8.4

Each component shall be properly packed
and protected before shipment
so that it shall reach the site without damage and with all surfaces clean
inside and out. To prevent damage during shipment, Seller shall carefully
pack and brace all components either within the shipping container or on
the

carrier.

4.8.5

Equipment shall be adequately supported for shipment. All loose parts
shall be boxed for shipment. Each box shall be appropriately marked for
identification purposes.

4.8.6

To facilitate rapid installation, all equipment shall be shop assembled to
ma
ximum extent particle, except as noted in paragraph 4.8.2, before
shipment to site.

4.9

Equipment Marking


All packaged equipment and other separate components that are match marked for field
assembly shall be clearly marked by letters and numbers so that
they can be identified
and cross
-
checked with shipping papers and applicable assembly drawings.

5.0

INSTALLATION

The installation of the
PMCS

at the site shall only include the connection to the field
devices (via Seller
-
furnished communication converters and
THE BUYER
-
furnished

SCADA Expert
Power RICH System
-
Enterprise
2013 R1 Release Notes

Page
11

of 6

cables) and the troubleshooting and verification that all parameters and devices
communicate with the
PMCS
. All hardware devices external to the
PMCS

computer(s)
is excluded except for one (1) UPS, one (1) printer, ##
of
communication
converters
(
RS
-
232 to RS
-
485 & Fiber Optic), and Ethernet switches


The provision of all data wiring and equipment within the plant such as jacks, outside
telephone lines, connections to building distribution frames, wiring, MODEMS,
conduits, connection to

computer backbones and networks distributed throughout the
plant, cover plates, and all connection for a complete installation will be completed by
THE BUYER. The Seller’s installation personnel shall assist in all troubleshooting and
testing of the fina
l assembly, but all wiring responsibility is with THE BUYER.


6.0

TESTING

6.1

Factory Testing

6.1.1

The following standard factory testing shall be performed on the software
and hardware provided:

a.

Configure and load all software (including backup and restore).

b.

Test and
operate computer system and software in a simulated
system mode for a minimum of 24 hours.

c.

Demonstrate full system functionality.

Field Testing (Commissioning Second Phase)

6.1.2

Verify complete system operation in the presence of the contracting
officer’s techn
ical representative including all hardware, software, and all
communication devices.

6.1.3

Verify networking performance with all interfacing by other
manufacturers.

6.1.4

Item 6.2

may be included in the items under Section 4.7 and sign
-
off.

6.2

Manufacturer’s Certificati
on

The Seller’s representative shall certify in writing that the equipment has been
installed, adjusted, and tested in accordance with the manufacturer’s
recommendations.

6.3

Training

6.3.1

Seller shall provide the following training class for up to three (3) Buyer’
s
personnel:

a.

Hands
-
on training of the
PMCS

as to its operation and
administration functions.


SCADA Expert
Power RICH System
-
Enterprise
2013 R1 Release Notes

Page
12

of 6

b.

Class sha
ll be four (4)

days at the
manufacturer’s facility

or
optionally at extra cost at BUYER Facility
.

c.

Explanation of system operations, additions to the syste
m, create
and modify screens, create and modify objects, network
configurations, THE BUYER’s configuration and equipment.

d.

Video (VMS) taping of the training session is permitted at THE
BUYER’s expense and with THE BUYER’s personnel.

6.3.2

Seller shall provide on
e (1) year of 24
-
hour technical telephone support to
trained personnel described in Section 6.4.1, a through d.

6.3.3

General operator training shall be performed with the operators during or
after commissioning. This is not the administrative class outline in
6.4.1.


6.4

Administrative Training

6.4.1

Agenda of Administrative Training

as required

goes here.

6.4.2

A class of 3 people (minimum) with a Maximum of 10 people for 4 days
to cover the administrative training will be trained by Manufacturer
Agent.

6.4.3

Class content will

cover the database building of object, templates,
instances,
menu navigation, user accounts, development and real
-
time
operations, importing of objects, importing AutoCAD, animation of
devices, and IEC61131
-
3 functional block design for special functions.


7.0

DRAWINGS AND SUBMITTALS

7.1

System description includes an overview of the system architecture for
networking, expansion, data, and control. This shall be part of the preliminary
design review process.

Both parties will sign
-
off on the Project Requirements

Specifications (A Scope of work with details of the project deliverables and
constraints.).

7.2

Note that all submittals will be in Electronic Format (Email or Data Transfer in a
compatible format).

7.3

Bill of materials for the
PMCS

will include

a complete listing of all hardware,
software, training, start
-
up, and commissioning services being supplied under this
Specification.

7.4

Hardware and software description shall be provided for all devices that
communicate with the
PMCS
, including sensor devi
ces gathering data to be
transmitted over a network to the IO Server(s).

7.5

Typical software screen displays shall be provided in color prints, on
CD
, or via
electronic file transfer (Email attachments) in a compatible format for
presentation software. Graph
ic formats like GIF, JPEG, BMP, TIFF, and
Microsoft Office products are acceptable formats. This shall be part of the
preliminary design review process

and a sign
-
off by the BUYER and End
-
User.
.


SCADA Expert
Power RICH System
-
Enterprise
2013 R1 Release Notes

Page
13

of 6

7.6

Block diagrams of the system indicating major devices, equipm
ent, and
PMCS

wiring shall be a part of the system screens for maintenance reference. This shall
be part of the preliminary design review process.

7.7

Written overview of the entire
PMCS
.

7.8

A final acceptance test plan with sign
-
off provisions for each parameter

checked
shall be submitted for customer approval before delivery. This test plan and sign
-
off shall then be used for commissioning. See Section 4.7, 5.0, and 6.0.

7.9

PMCS

operation and maintenance manuals shall be supplied for all equipment
and software su
pplied from the manufacturer. For the software, the “User Guide”
and the “Reference Manual” is considered the operation and maintenance
manuals.

Most all of the manuals are in PDF format and printable by the
BUYER, and not allowed to be copied by copyrig
hts onj the products.


8.0

MANUFACTURING AND PERFORMANCE DATA REQUIRED

8.1

Submittals by Seller

Item Description

Seller’s Submittal Date

THE BUYER’s review
requ楲id⁢ef潲e
f慢r楣慴楯iⰠ獨ipmen琠tr
f楮a氠l慹aent

Preliminary system
description, spare parts list;
descriptive bulletins; and
catalog information

With Proposal

NO

Certification that the
equipment contains no toxic
or hazardous materials

With Proposal

NO

An overall schedule of work
including software
generation, design reviews,
and equipment delivery
dates in sufficient detail to
demonstrate Seller’s ability
to perform the work within
the specified time.

With Proposal

NO

A statement as to
compliance with this
Specification without
exception and/or if there are
any exceptions, a detailed
description of

them

With Proposal

NO

Bill of materials

With Proposal

No


SCADA Expert
Power RICH System
-
Enterprise
2013 R1 Release Notes

Page
14

of 6

A complete list of all
drawings, diag
r
ams,
screens, descriptions, and
data, by title, which Seller
expects to provide

2 Weeks ARO (After
Receipt of Order)

NO


List of Codes and
Standards, with ef
fective
actually used in
construction of equipment

2 Weeks ARO

NO

Detailed system description,
Device hardware, and
software descriptions, block
diagrams, screen designs,
written overview and
performance data

6 Weeks ARO

YES

Final acceptance test plan

8
Weeks ARO

YES

Notification of factory
Testing

2 Weeks prior to testing

NO

Statement that system
successfully completed all
factory testing

At shipment

YES

Certified factory testing
results

2 Weeks after test
completion

No

Documents for record

2 Weeks p
rior to shipment

NO

Installation data and storage
procedures

2 Weeks prior to shipment

No

Commissioning sign
-
off
sheets

At completion of
commissioning

YES








8.1.2

The project schedule shall include key engineering interfaces, specific
information
required by THE BUYER, dates for placement of suborders,
start of software generation or configuration, tests, and preparation.

8.1.3

Seller shall submit to THE BUYER the following records:

a.

Comprehensive product quality report including Certificate of
Compliance.

b.

Equipment furnished when applicable (software only does not
require the drawings)

8.1.4

One copy of instructions applicable to each component shall be shipped
with the component.


SCADA Expert
Power RICH System
-
Enterprise
2013 R1 Release Notes

Page
15

of 6


9.0

TECHNICAL DATA

9.1

PMCS

Operations

The
PMCS

shall be capable of operating

on IO Server
(s)

and

Host computer
consisting of a system with the following features:

9.1.1

A Pentium
4
class computer (2
.4

G
Hz or higher),
single or dual core,

2
Giga
bytes

of RAM or more,
80

Gigabytes or more of hard drive on the
SATA

bus, video graphics on th
e PCI

Express

bus or AGP bus

supporting
2 monitor outputs and 64 MB of RAM
, a full
-
size keyboard (101 or more
keys), a PS/2 pointing device (mouse, trackball, or equivalent),
4 or more
USB ports, 2 more USB 2.0 ports
, two spare PCI slots
,

and color inkjet
printer (HP preferred).

Client computers can be 2 GHz with
1

GB of
RAM, and dual graphic display capable.

9.1.2

The operating system shall be Microsoft Windows
XP Professional or
2003 Server or higher.

9.1.3

The system shall
Auto
-
reboot capacity upon return from pow
er off in the
event that the UPS does not function or when the UPS power has
shutdown the system. The Auto
-
reboot will restart the computer
operating system (OS) and then restart the
PMCS

software with user input
only for log
-
in of the user. The system w
ill restart in READ ONLY
or
GUEST
mode until log
-
in has been done by an authorized user. A UPS is
required for the IO Server
s

or Host computer, see 9.1.
10
.

9.1.4

The IO Server(s) shall be use
able as a

workstations and shall have
capacity to display multiple monitors. The master and redundant backup
server shall be supplied with, a minimum of two (2) 19 inch or larger
LCD, high resolution monitors. The software must handle various screen
sizes without

distortion (Vector Graphics).

9.1.5

LCD monitors shall

be at least 19 inch or larger with the following
requirements: Dynamic Contract Ration of 3000:1; Brightness of 300
cd/m2; Viewing Angle 170° Horizontal, 160° Vertical;
Response

Time of
5 ms (gray to gray);

Native/Optimum Resolution 1680 x 1050; Color
Capability 16.7 Million colors.

9.1.6

The
PMCS

shall be capable of communicating with serial ports
and
Ethernet (802.x) simultaneously

using mixed OPEN protocols
.

9.1.7

The
PMCS

shall provide automatic
alarm
sys
tem based

on detected faults

in the IO Server
(s)

(Host) and
Clients (Full Display and Web)

computers
in
a

graphical header on each display screen
.

The remote device alarms
shall be displayed in the graphical header on each display screen as field
alarms. Provide a

direct path to the alarm display screen with
acknowledgement,
acknowledgement with comment, display alarm
details,
and a direct “GOTO” device screen causing the alarm.

9.1.8

The
PMCS

shall have the capacity of
having configuration changes to the
database, graph
ics, and PMCS without shutting down or compiling.

SCADA Expert
Power RICH System
-
Enterprise
2013 R1 Release Notes

Page
16

of 6

Switching between design mode and run
-
time mode will not require a
restart of the system or interfere with the continuous use by the operators.
All modifications will immediately appear when configured.

9.1.9

Each field device must have a field adjustable unique address for
gathering data

by the
PMCS

software.

9.1.10

The
PMCS

IO Server
(s)

or Host shall operate on 120 VAC and be
supplied with a UPS to support system operation for approximately

one
-
half
(1
/2
) hour witho
ut shutting down. This provides for an orderly
shutdown and easy restart of the
PMCS
. The
PMCS

will support UPS
software for notification of the network of a shutdown in advance of the
shutdown.

9.1.11

The
PMCS

shall provide the ability to detect faults in the
IO Server
(s)
,
remote protection devices, communications network, or auxiliary devices
such as analog temperature and report these alarms via a contact signal to
another system, auto
-
dialer, alarm horns, personnel alphanumeric pager,
and other similar remot
e contact device that may be provided by THE
BUYER.

9.1.12

The
PMCS

design shall be capable of providing remote Form C, contact
alarm indication at up to several hundred locations anywhere on the
network for these type of occurrences:

a.

Alarm and
-
or trip signal fro
m any other device on the system.

b.

Alarms above the setpoint on a
n
y Form C transducer.

9.1.13

All communication system components shall have a dielectric isolation of
2200 volts minimum line
-
to
-
ground without damage to the
communication device.

9.1.14

The
PMCS

shall be capable of interfacing with any existing or new
customer supplied broadband network
s

via RS
-
232, Ethernet,
and
-
or RS
-
485 interface. The
PMCS

will interface to other types of controls systems
such as Johnson
Controls
Me
d
a
-
Sys, Honeywell, Bailey,
Fo
xboro,
Delta
V,
etc., via OPC, Client or Server, other master/slave protocols,

ODBC,
SQL, XML, and other interface tools
.

9.1.15

Any communications converters shall be all in one type (RS
-
232/RS
-
485/Fiber Optic) provide for interchangeable port communication
co
nversion

9.2

PMCS

Software

9.2.1

Application Development



The
PCMS

software shall incorporate an integrated multi
-
user
development environment allowing all personnel to work simultaneously
on a project. The
PCMS

system shall have an object
-
based architecture
that
allows development of reusable templates containing all the
operational characteristics essential for system deployment. At a low
level, these objects can represent single devices, such as breakers or
motors, incorporating all associated tags, mimics, alar
ms and events,
security, and communication parameters. At a high level, the objects

SCADA Expert
Power RICH System
-
Enterprise
2013 R1 Release Notes

Page
17

of 6

represent entire sub
-
systems, such as an electrical substation or liftstation,
comprised of groups of object devices. Libraries of industry
-
specific
templates can be easil
y built and replicated throughout a system. When
modification to a replicated sub
-
system is required, only a single change
need be performed on the source template to effect change throughout the
multiple instances of the template within the system.


The
P
CMS

system shall have an

Integrated Development Environment
(IDE)
tool to develop and test the system. The IDE shall be integrated
into the Display Client allowing engineers to work on the system live with
no compilation of code or the need to shutdown th
e server following an
addition or change
. Any work done within the Display Client is
immediately incorporated into the system and becomes live. In addition,
multiple clients shall be able to simultaneously be connected to the
PCMS

server, each giving its
end
-
user the ability to perform individual tasks and
objectives. This allows teams of engineers to work in a fully collaborative
environment, developing the
PCMS

system database without the need to
merge the work of individual contributors.


The IDE shall
provide all the necessary tools for efficient configuration of
database objects. These include as a minimum: edit toolbar, alignment
toolbar, operating toolbar, navigate and debug toolbars, as well as,
cut/copy and paste, drag and drop, and context sensiti
ve object menus.
Localized object
-
based context sensitive menus allow the engineers fast
access to all functions that can be performed on or with a database object.
System commands shall also be part of an object menu and shall be
available at any point i
n the database allowing for easy access during the
creation of new objects and instances of template objects.




Online Configuration


The system database configurations shall be able to be modified on line.
This includes activating the configurations when

modified, as well as,
propagating the changes to standby and performance system nodes.
Display Client caches shall be updated when next accessed. Features that
can be modified online without disrupting system operation include:


add communication channels


add devices to an existing channel


add points to an existing device


modify channel, device & point attributes


enable / disable or modify event and historic recording
attributes


add or modify mimics


add or modify pre
-
defined trends


alarm redirection
strategies including paging, SMS, e
-
mail


system administration


security

Most server characteristics shall be capable to be modified on line
including:


SCADA Expert
Power RICH System
-
Enterprise
2013 R1 Release Notes

Page
18

of 6


Historian characteristics for large databases; Hence, the
overall system disruption is minimized, and onl
y for the
following configuration changes:


User defined Historic Views (database query pre
-
processing)


Event Journal characteristics


Historical event “regions” (e.g. Storm events, Flood
events, etc)


Alarm Severities (priorities)


Alarm Acceptance character
istics


Driver characteristics


E
-
mail connection


Printer connection


Exclusive control characteristics


Database location


System logging


Web server characteristics


9.2.2

The computer and software shall be capable of running other Microsoft
Windows compatible packaged software programs, such as, word
processing, spreadsheets, database, while constantly monitoring the
PMCS

field networks.
The PMCS system shall provide acces
s for 3
rd

party applications to the entire configuration database, real
-
time and
historical process data, alarm, and event history. Applications shall be
able to interface using SQL Queries (ODBC), OPC (Object Linking and
Embedding for Process Control), a
nd through an OLE Automation
interface. The OLE automation interface shall provide the capability to
use a 3
rd

party application, such as Microsoft Excel with VBA (Visual
Basic for Applications), to configure or modify system databases. This
will allow u
sers to optionally use VBA, C#, C++, or another application
to configure and maintain the system. For example, an Excel spreadsheet
that holds the configuration data for each substation could be used to add
other Substations. Data could include, number o
f breakers, feeder names,
pump names, network addresses of SIUs and IEDs, etc. The information
in the spreadsheet would then be used by an Excel Macro using VBA to
configure the PCMS systems using existing breaker and sub
-
station
templates. Any modificat
ions to the system shall be logged and shall be
subject to the permissions of the security system.
The software shall be
user
-
intuitive with menu
-
driven graphic screens with the following
features:

a.

The one
-
line for substations shall not be overcrowded wit
h too
many device parameters, but shall utilize standard meters or
metering parameter
s

with pop
-
up metering displays for more
detailed information. These meters shall provide all information
for all types of field devices, but retain the same “look and feel”
from device to device. For example, the phase currents shall
always be in the top

left hand corner of the window, while the
power factor and frequency shall be on the right side of the
window. A button to remove the
p
op
-
up shall be provided, the
pop
-
up window shall be movable, and multiple pop
-
up display

SCADA Expert
Power RICH System
-
Enterprise
2013 R1 Release Notes

Page
19

of 6

windows can be used on the sam
e screen, allowing the user to
move between them for full comparison viewing. In addition,
there will be a real
-
time graphic trend parameter button on the
detail information pop
-
up windows.

b.

The system shall provide a predefined set of real
-
time trend pl
ots
for immediate user viewing of these parameters. For example, the
four phase currents are predefined as a pop
-
up real
-
time trend plot
with a single user stroke.

c.

All one
-
line screens shall display the current and device status at
all times

in clear unde
rstandable indication plus color,

with pop
-
up
windows for
more

detailed parameters as energy. All pop
-
up shall
have the device identification, device status, current time and date.
Any alarms shall be shown on all screens (in a header on each
screen) and

a direct “go to” the alarm shall be provided from the
alarm acknowledgement screen. The parameters of a device alarm
shall be available to the operator within two operator strokes.

d.

The status information on the one
-
line screens and alarms screens
shall i
ndicate the device

status:

OPEN, CLOSED, TRIPPED, and
COMMUNICATIONS status. The alarm screens show the reason
for the alarm, type of alarm, who acknowledged the alarm or if the
alarm has not been acknowledged. Addition information may be
added or delete
d from the alarm report pages by the user or
customized by system integrator.

9.2.3

Connectivity / Historian Highlights



Software shall include
PCMS
-
to
-
Enterprise connectivity including a in
-
built data historian for
PCMS

events (including alarms) and historical

(trend) data

including, but not limited to, reports, user operations, any
event
. The software connectivity and historian facilities include:



Historical entries at times of interest (e.g. crossing alarm
threshold, quality change)


Historical data storage c
omprises:

o

Exact time
-
stamp value stored and displayed at 1
00
Nanosecond
resolution (as reported by field RTUs)

o

Stored
Engineering Values and Units

o

Point alarm state at the time of historic record

o

Point quality at the time of historic record


Historic compre
ssion capability (configurable per point)



Can store all point changes



Restrict storage to Minimum interval



Restrict storage to Significant Change as percentage of
span



Restrict storage to Significant Change as Absolute value



Restrict storage to
Significant Change as Percentage of
current value


Full function viewer presents historic data graphically or in tabular
views


Create user defined mimics or trends using full function viewer:


SCADA Expert
Power RICH System
-
Enterprise
2013 R1 Release Notes

Page
20

of 6




Global mimics / trends




Restrict access using PRS EE Securit
y




Private Trend Stores per user (stored on server, backed
-
up
through redundancy, available wherever a user logs on)





Share trends with other users


Create Ad
-
hoc multi
-
pen trends using full function viewer


View Pre
-
defined multi
-
pen trends using Web v
iewer


View Ad
-
hoc single
-
pen trends using Web viewer


Event Journal comprises




Point

transaction information (point configurable)




Alarm

information (including operator accepts)




Auditable

events (e.g. operator log
-
on, modify history,
modify alarm limits)



insert user comment record


Selectable on
-
line retention period of Event Journal data


Form
-
based query filters and historic retrieval of Event Journal data
from full function viewer and W
eb viewer


Select on
-
line retention period of Historic and Event Journal data


Archive data to writeable media (e.g. DVD

or external hard drive
)


Mount and retrieve data from previous archives


PCMS

level secured access to historic data


Modify historic data ma
nually (e.g. following instrument calibration,
manual readings, etc)


requires privilege


Modify or Insert historic data programmatically (e.g. via OLE
Automation interface)

authentication secured


Annotate history (operator comments)


requires security
privilege


Historic databases are replicated in real
-
time between PRS EE Main,
Standby and Performance servers.


Where a Performance server is used as an Historian server, the
historic and event journal records can be kept online for longer
periods than the
Main / Standby servers.


Open system interfaces provided to all databases:




ODBC interface to
Real
-
time database,

Event
Journal

and
Historic database

o

OPC
-
AE interface
to
Alarm and

Event Journal

o

OPC
-
HDA interface to Historic database

o

OLE
-
DA and OPC
-
XML
-
DA
provider license for 3
rd

party
OPC clients


Pre
-
defined and User definable “Historic Views” providing pre
-
processed virtual database tables simplifying external data access and
reducing storage of raw and derived data


As detailed above, the
PMCS

software n
atively provides the user
interface for Historian data access. Historian data shall be accessed
through full function
PMCS

viewer (Display Client) or Web Client.
Configuration of the historian shall be part of the standard
PMCS

configuration.



SCADA Expert
Power RICH System
-
Enterprise
2013 R1 Release Notes

Page
21

of 6

9.2.4

Reports

The system Integrated
-
reporting engine shall use Crystal Reports
providing:


Automated server
-
side generation of reports based on event
triggers, repetitive schedules, ad
-
hoc user or programmatic
triggers, logic (IEC61131
-
3)


Parameter passing to generic rep
orts


e.g. user can run a standard
report for data months or years old


Export of report data to HTML (web), PDF, CSV, Excel, Word,
ODBC, Text, XML, etc.


Export generated report format to server, workstation disk, e
-
mail,
etc.


Crystal Reports Run
-
Time sha
ll be used as the system server’s report
generator and shall be bundled with each system server installation.

Users can generate, export and print pre
-
configured reports, including
passing parameters to reports, as a native system function. Crystal Report
s
does not have to be installed on the user’s workstation.

Workstations that create ad
-
hoc reports using Crystal Reports, or modify
system server reports require a licensed installation of Crystal Report
Professional Developer.

9.2.4.1

Data Export Tool



The PMCS shall have a Data Export Tool that exports Historical data.
The Data Export Tool shall use Configurable Historic Views to Excel or
Comma Separated files (CVS); an External Database like MS
-
SQL
Server, via ODBC
-
DSN, and a Data Table.




The Dat
a Tool allows the use of up to two (2) sorting fields and allows the
use of wildcards to select points in the database.





For example, Select data where:




Full name of field is
Like %KW% AND Like %Substation%




This would get data from all points
that had a name like KW and are in
any substation. You might want the Maximum Hourly KW for each
feeder in your system.




The Data Export Tool shall export the data using a Historical view that is
configurable by the user. The Historical view determines

what you want
to export. A few examples are Hourly Average for a day, Daily
Maximum for a month, or 5
-
minute averages for 30 days. This allows
PMCS to export data that is formatted the way the customer needs it.
Real world examples would be 1
-
hour KW a
verages over the month, or
24 hour KW Hour Usage per feeder, or Hourly KW Maximum per feeder.


SCADA Expert
Power RICH System
-
Enterprise
2013 R1 Release Notes

Page
22

of 6




Exports shall be easily schedule using a Schedule Object or can be
manually exported on an Ad Hoc basis.




Examples would be to export last months Hourly KW U
sage per feeder
for all feeders on the 1
st

of every month at 8:00 AM to an Excel File
named KW Usage %Month% %Year%.xls


There is no code required or the need to know Standard Query Language
(SQL) to export data.



9.2.5

Redundancy

(Optional at a later date

by end
-
user
)

The PCMS system shall natively support redundancy and shall not require
any coding or third party applications (Mirrored). The PCMS servers
shall provide server level redundancy. All Real
-
time data, Historical data,
Alarm data, Event data,
and configuration databases shall be duplicated
automatically on Standby servers. The PCMS system redundancy shall
have the capability to provide
Quad

level server redundancy and
Five (5)

level
when Performance

Server
(s)

is added..
Performance Servers sh
all
also have the ability to be ‘read
-
only’

so that they offer higher level of
security when installed outside corporate firewall

(Demilitarized Zone)
.


The
server processes
shall be
in constant communication via TCP/IP
links. Each database to databas
e tra
nsaction between servers shall be

monitored with both Main and Standby nodes monitoring availability of
the ‘Partner’ nodes. This checking
shall detect the

loss of
the
partner
server process
,

as well as potential communication path loss. In addition
to fa
ilure detection through failure of database transaction
communications, the Partner node server processes
shall
utilize low level
ICMP communications for faster detection of loss of a partner node. To
retain database
integrity during a changeover, the

dat
abase
shall
be locked
during the period a Standby is transitioning to Main, but
the typical
duration of a

failover
should only take
less than a couple seconds.


PCMS D
isplay
C
lients
shall be
configured with active connections to
Main and Standby servers
.

A failover of any system to a standby node
shall result in the D
isplay
C
lient transparently switching its connection to
the active server.

All mimics, alarms, trends, lists and/or reports on a
user’s display
shall be

updated from the new server connection

following
re
-
establishment by the display client.


The

transition by the client
shall be

transparent to the user.


PCMS
Web clients do not
need to
provide this functionality
, but shall be
manually
re
-
connect
ed

to the standby
server
.


9.2.6

Performance


SCADA Expert
Power RICH System
-
Enterprise
2013 R1 Release Notes

Page
23

of 6

The
System historian performance shall be optimized for time
-
series data.
It shall present a standard relational ODBC/SQL open interface, with
excellent performance compared with generic databases, such as Oracle,
SQL
-
server, etc.

A system configuration datab
ase, on
a
32
-
bit Windows® desktop
platforms with
4

GB memory, will
typically
handle
100,000 configuration
database objects

and larger systems

(500,000)

can utilize 64
-
bit windows
.
History can be enabled on any number of points within the database. The
Sy
stem historic databases shall be sized in the order of billions of records
for projects utilizing large server
-
class installations with Storage Area
Networks (SANs).

Enhance system performance using “Performance Server”
or “Proxy
Server”
architecture. A p
erformance server has mirror
-
image copies of
the operational system server databases including the configuration, real
-
time, historic and event journal databases. Performance server databases
are kept up to date, in real
-
time, from the Main server. Histor
ic, or other
access to the Performance Server does not impact the operational (e.g.
Main / Standby) servers.

The system shall be a

distributed architecture that shall be optimized for
data access across wide area networks (WAN). The system shall combine
a

number of advanced techniques including data compression; caching
and exception reported data, to provide high performance across medium
to slow links. This permit Display Clients to each connect to multiple
remote systems. Data shall be presented to th
e Display Client as a single
system, combining alarms, permitting trends with curves from multiple
systems, combined system data on the same mimic, etc.

Configuration and maintenance of distributed systems shall be centralized
through common client interf
aces, in the same way.

9.2.7

Disaster Recovery

The system shall natively support Main / Standby configurations as
described above. Triple standby shall also be available for the system.
Each system server node database is a mirror image of the system Main
serve
r with respect of Configuration Data, real
-
time
PMCS

data and
historic data. It is typical to locate Main and Standby system server nodes
at physically separated locations, e.g. Main Control Center + Disaster
Recovery Center. The system designs shall be b
ased around this
architecture.

As described above, system historian supports the capability to archive
data from the system event journal and historic database on to external
media.

Typical system installations include removable disk media (e.g. DVD,
USB d
rive) and backup media (e.g. Large Hard Drive, USB portable Hard
Drive, and Tape Backup). The removable disk media is typically used for
historic and event journal archive. The backup media is typically used for
disaster recovery storage. The system conf
iguration, real time, historic
and event journal databases shall be copied to backup media, online,
simplifying disaster recovery procedures.


SCADA Expert
Power RICH System
-
Enterprise
2013 R1 Release Notes

Page
24

of 6

The system vendor shall provide disaster recovery procedures as part of
system installation. The system software
shall contain all product
features. For disaster recovery scenarios requiring complete system
rebuild, system software shall be readily installed from CD
-
ROM that
utilizes standard Windows® operating system facilities. The system
databases shall be readily

restored from backup media. No other special
installation procedures are required.

9.2.8

Data via SMS and E
-
mail

Delivery of data (including alarm information) via SMS (also referred to
as Text Messaging) shall be a standard part of system paging
functionality.

E
-
mail for alarm data is closely related to paging, being
another “Alarm Redirection” feature. The system shall natively support
connection to an e
-
mail server for delivery of alarm data. E
-
mail content
is user configurable, including information from w
ithin the system
database. E
-
mail may simply contain text. It may also include a Web
hyperlink to take the user directly to a Web Browser alarm view mimic.
Using Microsoft embedded HTML technology; the e
-
mail can also
contain a live (updating) mimic pic
ture without requiring the user to start
a web browser to display the mimic.

SMS Command Processor
-

The existing pager driver
shall

be extended to
support incoming SMS messages so that users can send commands to the
PMCS

server to acknowledge alarms, run
reports, request status
information, run machines
,

and much more.

Some common examples are listed below:


Acknowledging alarms


Changing alarm setpoints


Requesting a status report


Triggering a report to be ema
i
led to a Blackberry


This facility permits
validated users to interact with the PMCS system,
without needing to setup and connect using a Display or Web Client.
Simpl
e

commands can be issued using a mobile phone from anywhere
and anytime.

Report data can also be sent via SMS and e
-
mail. Using the

ad
-
hoc free
format text paging, described above, the system logic can form up
messages and send to nominated pagers. E
-
mail of report data shall be
tightly integrated with the system reporting mechanism via Seagate
Crystal Reports. This allows a report,

including graphical information, to
be generated and exported to a user via e
-
mail. For example, e
-
mail a
work order.

9.2.9

System
Security


SCADA Expert
Power RICH System
-
Enterprise
2013 R1 Release Notes

Page
25

of 6

The
PMCS

system must provide state
-
of
-
the
-
art security technology at all
levels of operation

to create a safe and secure

PMCS

infrastructure. The
PMCS

system security must prevent system compromise from both
internal and external sources. The security functionality shall prevent
external attempts at system infiltration while simultaneously allowing
controlled access to nume
rous legitimate users. Security shall be
configured at the object level and be based on user
-
access profiles and
object permissions. Security shall apply to all clients in the system.

The
PMCS

shall lock out non
-
authorized system access while controlling
p
assword
-
based access for legitimate users. Engineers, for example, can
have full development and control access while process operators have
limited access based on their responsibilities. Security shall be configured
at an object level during development,

where permissions are applied to
discrete system points. Users or user groups shall be assigned password
-
protection levels of access for specific features including, configuration,
operation, alarms, and database navigation. Security levels shall be
confi
gured on an individual basis or grouped together to share common
configuration parameters, thereby reducing setup time. The system shall
use password encryption, aging, dictionary and inactivity logout.
Additionally, all database objects shall be assigned
permissions based
upon pre
-
configured users and user
-
groups. Permissions, which include
read and write capabilities, alarm and history control, configuration,
security and system administration, shall be automatically carried over
when an object is copied
or included in a template instance, thus further
reducing overall system setup time. The system shall have the ability to
apply security configuration across the database. Permissions shall be
able to be allocated at the parent level where they are inheri
ted by lower
level objects.

The
PMCS

system shall provide an audit
-
trail by providing an event
journal containing a user field entry for every record. This shall provide a
comprehensive index of time stamped actions, controls, alarms and events
including c
hanges to security settings. This will allow administrators the
ability to closely monitor activity relating to specific data points or
changes that have occurred to security privileges. Specific events shall be
able to be extracted from the database using

an integrated SQL filter tool.
The SQL Filter tool shall be used to easily create customized reports or to
view the results in the clients using only a mouse
-
click function.


The
PMCS

system shall apply security across all interfaces including
Display Cl
ients, Web Clients, OLE Automation interface, ODBC and
third party OPC connections. For links using internet networks, Secure
Sockets Layers (SSL), Private Keys, and Certificates shall be used to
ensure such security.

9.2.10

Data Acquisition

The
PMCS

system shall

use an industry standard protocol, such as DNP3,
which provides time
-
stamped, quality verification for all data, supports
Report
-
by
-
Exception class polling (
RBE polls

the SIU [System

SCADA Expert
Power RICH System
-
Enterprise
2013 R1 Release Notes

Page
26

of 6

Information Unit] that only reports the changes or events in each class
since the last poll), and Unsolicited Response data from SIUs (SIU sends
a data to the master station without being polled by the master). The
protocol shall have the capability to recover from data collisions caused
by unsolicited communications by SIUs.

The protocol shall backfill the
historian on a reconnection of communications after a communications
loss.


The
PMCS

system shall provide

a flexible scanning engine where
individual
SIU

scanning configurations are made through ‘fill
-
in
-
the
-
blanks” forms.

Each
SIU

object
shall
support an individually adjustable
scanning rate for integrity poll, as well as individual scanning rates for
Class 1, Class 2 and Class 3 event polls (RBE polls). Integrity and event
poll scanning rates for each
SIU

shall also be
time
-
aligned with adjustable
offset.


E.
G
.

SIU
1 polls every 60 seconds, 10 seconds after the top of the
minute,
SIU
2 polls every 60 seconds, 15 seconds after the top of the
minute, etc.


SIU scanning shall support

specific event object groups

with binary
,
analog and counter event group scans being individually selectable for
each
SIU
. Scan rates for these event group polls
shall be

selectable from
1 of 8 scan rates common to all
SIU
s on
a channel
.

Scanning
shall be
supported for point static data groups.

Within each
SIU
, points can be
selected for
a concurrent scan
. The rate of which are selectable from 1 of
the 8 scan rates on the channel.

All scan rates described above
shall be
standard configuration fields for the
SIU

or channel objects in the
PMCS

da
tabase. All
shall be

adjustable in the range milliseconds to weeks.
Scan
rates for m
ultiple
SIU
s
hall be able,

for convenience, summarized and
managed through the user’s creation of a mimic display, or system list.

The
PMCS

system shall support both direct connection to SIUs via Serial
or Local Area Network, or remote connection via radio or PSTN or GSM
MODEMs. The
PMCS

system shall provide all of the functionality to
dial and manage MODEM dialing.

System Integration with S
IU (RTU)

The
PMCS

system software shall be tightly integrated to the SIU
hardware used in the system. It shall have the ability to interface to the
SIU in a comprehensive and efficient manner. While the
PMCS

system is
running, the
PMCS

software shall be a
ble to remotely communicate,
control, and configure the hardware. This shall allow an operator to
create and download hardware configurations from within
PMCS

software. The
PMCS

software shall provide configuration export and
archival from within the sys
tem as well. This functionality allows
operators to configure a SIU and allow them to reuse that configuration by
downloading the configuration across the network to other SIUs. This
allows engineers and technicians to remotely work on the entire system

SCADA Expert
Power RICH System
-
Enterprise
2013 R1 Release Notes

Page
27

of 6

wi
thout

being forced to constantly work in the field at widely dispersed
sites. To facilitate a totally integrated system and to lower the total cost of
configuration, maintenance, and commissioning of the
PMCS

system, it
shall specifically provide as a mini
mum the ability to do the following:




Configure the SIUs while the system is running


Automatically distribute configuration changes across the entire
system


Upload and download SIU configuration files


Version control of software within SIUs


SIU clock sync
hronization with the servers


Remote diagnostics


Remote restart


9.2.11

Open Standards

The
PMCS

Software shall be based on industry
-
standard open interfaces
,

protocols
,

and
efficiently interface with third
-
party software and hardware
to provide seamless data exchange over a wide variety of communication
links. Flexibility shall be built into the software
making it

easily scale
from a single computer to a large installation of

dedicated servers and
dispersed clients. The software shall be client/server architecture with
separate server and client components. The software shall have built
-
in
system redundancy and data
-
backfilling features
to
assure the highest
degree of data rel
iability. Redundancy shall be accomplished without
custom code development.


9.2.12

Scalability

The systems shall be scalable meeting current requirements. It shall be
easily scaled to meet future demands. The
PMCS

system shall be capable
of running as a single PC, hosting the server and client, and be easily
expandable to a multi
-
plant wide area network with redundant mirrored,
clustered servers and hundreds of clients.

The
PMCS

system shall support the following

9.2.12.1

U
p to 5
0,000

(32
-
bit)/
500
,000 (64
-
bit)

real
-
time data
points
per server

-

Multiple ser
vers and cluster may be
designed

9.2.12.2

Built
-
in tools for expansion of databases, servers, clients,
and users

9.2.12.3

Open architecture standards and communication protocols
including O
PC, ODBC, HTTP, XML, SQL, DNP3
,
IEC870

and Modbus

9.2.12.4

Multiple communication links including serial,
LAN/WAN, radio and PSTN and GSM MODEMs.

9.2.12.5

Component
-
object architecture that allows for the
development of reusable application objects. Any object in

SCADA Expert
Power RICH System
-
Enterprise
2013 R1 Release Notes

Page
28

of 6

the syst
em can be converted to a template that can be used
for any number of instances in the system. If the template
is changed, all instances of that template shall be
updated
automatically

without the need to shutdown or recompile
the system.

9.2.12.6

Object oriented

database that supports renaming of object
components without losing any references.

9.2.12.7

Full system security configured to the object level and
based on user
-
access levels and object permissions.

9.2.12.8

Full function display clients for display of mimics (graphic
pages), trends, reports, control, alarms and events.

9.2.12.9

Full function display clients that support system
configuration that includes object databases, graphics, and
all other aspects of system configuration.

9.2.12.10

A browser based client that requires no configur
ation. The
Web based client shall have full functionality for data
display and control. It shall not be able to perform system
configuration. The web client shall be implemented using
Microsoft Internet Explorer or equal. The system shall
have a built
-
in Web server component that does not require
Microsoft IIS web server.

9.2.12.11

Support remote management of servers whether the system
consists of a single Server or a group of many "clustered"
Servers that are distributed over a wide area network.

9.2.12.12

OPTION
AL:
WebV
iew

capacity shall be available.


WebView
©


WebView is a client that was developed specifically for applications that
require a large number of users to access real
-
time and historical data.
Users view the current values of data in a tabular format (not
graphical)
and Historical Trend data in a chart format from any web browser.
Adding the WebView web

server option to a

Power
RICH
System
©
-
Enterprise Edition

allows any number of users to have access if they
have Read privileges in the system.



If addi
tional devices are added to the

Power
RICH
System
©
-
Enterprise
Edition

database, they are automatically updated and displayed in
WebView. Simple configuration fields determine what data is viewable
and how the data is presented. The format is easily chang
ed by a system
administrator.



All analog values are presented with Point Name, formatted value, and
units. Digital Points display the Current State Description (Closed,
Tripped, etc). Any point that has History turned on will have a Trend
Icon that
allows access to historic trend data via a charting tool. Users
can select the trend time and scaling.



When the users go to the Website, they are presented with a Log On
screen (See below). Then the users are presented with webpage that lists
the Devic
es / Sites they have security to Read. Devices shown in a Tree

SCADA Expert
Power RICH System
-
Enterprise
2013 R1 Release Notes

Page
29

of 6

view and when the user clicks on a device, the database is queried for that
device’s current values. The values can be refreshed by clicking the
Refresh Button in the Browser.



Trend data is

accessed by simply clicking on the trend icon next to the
values. A larger trend icon allows the user to look at a trend chart with all
of the values in the group (See Trends below). The user can look at Raw
Historic data (all samples in the Historian)
or they can look at Historical
Views, such as 1 hour averages or 24 hours Maximum values.



WebView uses Microsoft IIS web

server that supports SSL and
encryption on the web

server.
WebView does not require Web
Server License.





SCADA Expert
Power RICH System
-
Enterprise
2013 R1 Release Notes

Page
30

of 6

Log in screen


Device
page





SCADA Expert
Power RICH System
-
Enterprise
2013 R1 Release Notes

Page
31

of 6

Trends



9.2.13

Client Components


The
PMCS

system shall have two client types to meet the needs of system
users: a Display Client and a Web Client.


The Display Client shall be a fully functional client that includes a
development and an operational en
vironment. It shall allow engineers
and operators to develop and operate the
PMCS

system simultaneously
using login and security settings to determine the functionality available
to each user. It shall provide an intuitive integrated development
environm
ent
with

an operator
-
interface that shall,

at a mi
nimum,

include

the following
:



Dynamic animated displays using vector graphics


An intelligent alarm banner


Navigation tools


Operator tool bars


Easy to use queries for event lists like SQL


Live and historic

trend displays


Straight forward drawing tools


Comprehensive symbol libraries


Zoom
-
able vector graphics


Replication tools


Integrated report generation tool.


9.2.14

Display Client


The Display Client
shall be a separate installation from the server
component and
can be installed on the server or remote computers. The

SCADA Expert
Power RICH System
-
Enterprise
2013 R1 Release Notes

Page
32

of 6

remote installations shall be fully functional, just as if it was installed
directly on the server. The Display Client shall remain fully functionality
with network communications speeds as low as 6
4K baud.


The Display
Client shall be able to
connect to 64 servers simultaneously
.

9.2.15

Web Client

The Web Client shall be Browser based, thin client, providing fully
operational functionality and process control over a secure Internet
connection with a
Microsoft Internet Explorer
.
The licensing for the Web
Client shall use concurrent licensing, so that the clients are licensed by the
number of potential users online at any one time, not licensed by the
number of computers. Licensing shall be administere
d from the server
not the client. Development shall not be supported with the browser or
Web Client.

Multi
-
site Web

Client

to support cross database hyperlinks meaning that
users in
PMCS

system with multiple databases can navigate between the
sites using
standard hyperlinks configured in
Display Client
.

9.2.16

Diagnostics shall be internal to provide information on device and system
malfunctions, such as device not communicating, printer failure, out of
disk space, code errors, and similar type events.

9.2.17

The
PMCS

shall be capable of interfacing to PLC units and other system
via Ethernet, serial, DDE, OLE, OPC, and other protocols.

9.2.18

The software shall allow the user to set up to 255 defined, desired,
individual, computer alarms levels for all monitored parameters.
This
shall provide for user
-
defined levels, such as low warnings, medium level
warning, and special alarms for their attention. These alarms shall be
independent of the protection device alarms.

9.3

Drawing Graphic Capability

9.3.1

The software shall include the ca
pacity to create customer object oriented
graphics
for such things as system one
-
line drawings, flow diagrams o
f
system, equipment front or custom

graphic represen
tation desired by the
user and
make action buttons

for system commands. The software

shall
al
low for the insertion of customer
-
selected variable tags providing real
-
time
and historical
information from the remote devices. The graphic
package shall allow
unlimited

screen
drill
-
down

to lower
-
level detailed
screens. The graphic
s

package shall have,

as a minimum, the following
specified features:

a.

Animation or indication (changing of shape, color orientation, or
configuration) of any object or line on the screen based on a
change of incoming monitored data and/or a software
-
performed
calculation shall

be provided. For example, the changing of
single
-
line breaker color based on OPEN, CLOSED, TEST,
DISCONNECTED, TRIPPED via fault, or monitored values of
circuit breaker or motor starter or switch.


SCADA Expert
Power RICH System
-
Enterprise
2013 R1 Release Notes

Page
33

of 6

b.

Ability to perform mathematical operations and logic func
tion on
the incoming monitored data or calculated data points. These and
many other type

of user
-
defined functions can

be performed using
built
-
in
IEC
-
61131 function block or statement language a
nd
provide for new user
-
defined functions, provide string
ma
nipulation, and perform “if
-
then
-
else, For
-
Do, While
-
Do,
Conditional Executions.”

c.

Display in a real
-
time mode a graphic representation of either
monitored or calculated data. This shall include line charts and
bar graphics with animation.

d.

Librar
y
objects
that are able to be modified
for customer graphics
screens. The ability of the graphic package to use templates for
display screens and objects on the display screens, so that when
modifications to a template are made, all associated screens are
updated.

One change in a template updates all
instances of that
template.

e.

Custom developed screens to match customer one
-
line drawings,
customer floor plan, security and fire equipment, process control
equipment, building equipment, and actual power transmission
a
nd/or distribution equipment front
faceplates

shall be provided as
part of the
system.

THE BUYER will be able to select colors,
numbering scheme, and general arrangements of the screens
through preliminary design reviews (electronic or in person).
The
sy
stem shall p
rovide a master overview screen with
hyperlink

buttons, listing all subscreens by contract designation. Moving to
the subscreens can be selected by a mouse click operation with
proper
security assigned for the user.

f.

Automatic routing to approp
riate one
-
line shall be provided on an
alarm condition and graphical identification of the device causing
the fault or alarm.

9.4

System Component Detailed Specifications

9.4.1

Host (IO Server) Device Requirements

a.

Furnish and install a personal computer meeting the
requirements
previously outlined. Provide as a minimum,
PMCS

software
package, Microsoft Server

2003 or later

or Workstation), latest
version with all current service packs.

b.

Furnish and install a color inkjet printer interfaced to a
USB or
Ethernet

port
on the IO Server
(s)
, and a UPS system that will
provide a minimum of
30

minutes uptime without AC power for
all system components connected to the IO Server
(s)
.

9.4.2

Display and/or
Web

Clients (Optional)

a.

Furnish and install a personal computer meeting the requirements
previously outlined including the network interface card and
software files necessary for enterprise network operations.
Provide as a minimum,
PMCS

software package as 32
-
bit software

SCADA Expert
Power RICH System
-
Enterprise
2013 R1 Release Notes

Page
34

of 6

packag
e for data exchange, and Microsoft
XP Professional
(workstation)

or higher Windows Operating System
, latest version
with all current service packs.


OPTIONAL.

b.

Furnish and install a color inkjet printer interfaced to a parallel
port on the IO Server
(s)
, and

a UPS system that will provide a
minimum of
30

minutes uptime without AC power for all system
components connected to the IO Server. OPTIONAL

9.4.A 2013 R1 Additional Features

Power RICH System
-
Enterprise Edition now part of StruxureWare Software
Applications and Suites

StruxureWare is the brand name identifying
Schneider Electric’s

various software
applications and suites to drive business performance while conserving enterprise
resources. StruxureWare software suite is organized within a framewor
k of three levels:
Control level, Operations and Enterprise. StruxureWare software applications are available
as ‘A La Carte’ application or part of End Market Suites (Industry, Building...).

As part of the SCADA software suite of StruxureWare pertaining t
o the ’Control’ level,
Power RICH System
-
Enterprise Edition will now be referred to as Power RICH System
-
Enterprise Edition, the SCADA software
dedicated for telemetry and remote SCADA
applications.

Now part of StruxureWare software, Power RICH System
-
Ente
rprise Edition will include
the
StruxureWare software brand signature which includes the name, icons and splash
screens
in the product and marketing assets.

Server Improvements

Improved Historian Scalability

1. Improved start
-
up performance of the
historian:

a.

Historic data


up to 97% reduction in start
-
up times from CS 2010 R3.

b.

Event journal


up to 94% reduction in start
-
up times from CS 2010 R3.

2. Reduced the memory required by the historian when storing data online for long
periods, through a ne
w granule index:

a. Historic data


up to 90% reduction in memory usage from CS 2010 R3.

3. Improved performance of loaded granule cache.

Together these improvements considerably increase the scalability of the historian allowing
much more historic data to

be kept online for a much longer period of time.


SCADA Expert
Power RICH System
-
Enterprise
2013 R1 Release Notes

Page
35

of 6

These improvements have been driven by a large system which has a capacity for 250,000
points each storing 25 years’ worth of historic data (on permanent standby servers). This
equates to 326 million granul
es containing 219 billion records using 7.8TB of disk space.

Integrated Server Backup

A new database Backup object has been added to Power RICH System
-
Enterprise Edition.
This
enables the user to perform the Backup of the database automatically (e.g. usin
g a
Schedule) or manually using a method on the object.


SCADA Expert
Power RICH System
-
Enterprise
2013 R1 Release Notes

Page
36

of 6

The new ‘Integrated Server Database Backup’ task:



Suspends all database flushing on initiation



Confirms database flushing has stopped before proceeding with the backup



Replicates the
database files to the backup location



Re
-
enables database flushing

Additionally, the backup task also logs an event on initiation and completion. The completion
event includes statistics on the number of files copied and the total size of data copied.

Whil
st the backup is in progress, the database will continue to operate; processing values,
storing updates in memory and synchronizing updates to the standby. When the backup is
complete all updates are flushed to disk with the standard database flush algorit
hms.

The backup task copies the following files:



Database: Metadata, Structure, Configuration and Data



Historic Data



Event Journal Data



Configuration Change Data

Backup of historically stored records includes a configurable time range to allow the amount
o
f historic backed up to be tuned to control both the backup size and execution to be kept
within sensible limits on systems with large quantities of historic data.

Driver Developments

Dynacard Data Export Tool

The Dynacard Data Export Tool enables the user

to export Dynacard data from Power
RICH System
-
Enterprise Edition
. This data can then be imported into other systems such as
XSPOC.
This would allow those systems to perform additional analysis on the data.

SQL tables have been added to allow Dynacard data to be queried via ODBC, allowing
external tools to directly read and process the Dynacard data stored within Power RICH
System
-
Enterprise Edition

Schneider Electric Rod Pump Controller driver

The Schneider
Electric Rod Pump Controller is similar to the Lufkin SAMS controller and is
used for monitoring rod pump wells. The Schneider Electric Rod Pump Controller uses
Modbus as its core protocol and has been developed as an extension to the Advanced
Modbus drive
r in Power RICH System
-
Enterprise Edition.

The Power RICH System
-
Enterprise Edition driver will target the Schneider Electric
RPC v2.0
controller.


SCADA Expert
Power RICH System
-
Enterprise
2013 R1 Release Notes

Page
37

of 6

Support for SCADAPack E IEC61131
-
3 Target 5

Support for IEC61131
-
3 Target 5 has been added to the SCADAPack E RTU. The Target 5
file format is different to that of the previously supported Target 3 format.

Power RICH System
-
Enterprise Edition currently sup
ports downloading configuration to
SCADAPack E
RTUs including the compiled Target 3 files. The files are attached to the
SCADAPack E outstation object in Power RICH System
-
Enterprise Edition via the
‘Configuration Setup’ dialog. This
dialog also enables th
e user to view the description and
version information of the compiled file.

The existing support for Target 3 files in Power RICH System
-
Enterprise Edition has been
extended to
include Target 5 files. Additionally a new configuration field has been added
to
the
SCADAPack E outstation object to allow the user to select which version of IEC61131
-
3
Target is running in the outstation. The setting of this field is downloaded to the outstation
that supports the newer Target version to configure which version th
ey should use and
control the type of files which can be added through the ‘Configuration Setup’ dialog.

User Interface

Trending Improvements

The following improvements have been introduced to the trend subsystem in Power RICH
System
-
Enterprise Edition
:



Improved trend default settings



Y
-
Axis in trends have been made unambiguous



Improved display aesthetics to enhance user experience

Trend Default Settings for Traces

The existing Tools > Options dialog has been extended to allow a full set of defaults to be

specified for each trace type (Current, Raw Historic and Processed Historic). To simplify
entering this configuration, a new property sheet incorporating a separate page for each
trace type has been designed.

Y
-
Axis Relationship to the Trace

Under some co
nditions, it is not easy to determine which Y
-
Axis relates to which trace
within
a trend. This improvement to trends ensures that when a trace is selected on a trend, all
attributes relating to the trace is clearly visible.

When the user clicks on any trace in the Key Area of the trend, all the other traces on the
trend are faded out including attributes for other traces like markers, annotations, Y
-
Axes

SCADA Expert
Power RICH System
-
Enterprise
2013 R1 Release Notes

Page
38

of 6

and alarm limits. Only those attributes relating to the selected trace w
ill be clearly visible on
the trend.



SCADA Expert
Power RICH System
-
Enterprise
2013 R1 Release Notes

Page
39

of 6

Improved Display Aesthetics

Trends are highly configurable and most visual attributes can have a specific color defined
by
the user in addition to the automatic trace color selection provided by Power RICH Power
RICH System
-
Enterprise Edition
. Whilst the user is responsible for choos
ing most of these
colors, and by
definition, is also responsible for any color conflicts, it is still possible for Power
RICH System
-
Enterprise Edition

to add new traces using colors which are almost
impossible to discern
against the trend background.

Henc
e, the automatic trace color selection behaviour has been extended to limit the chance of a
color conflict by ensuring that existing trace colors, along with the trend background color are
all taken into consideration when selecting the color for a newly a
dded trace.

Improved Mimic Drawing Performance

The drawing performance for mimics has been improved by caching GDI+ brushes and
pens.

The re
-
drawing times on mimics containing lines and polylines has been markedly improved
(>
75%) by the changes made (results obtained by comparing re
-
drawing times for mimics on
v72 and v73).

New and Improved Symbol Library

The Power RICH System
-
Enterprise Edition symbol library has been updated to include 51
new
symbols for the TRSS range of pr
oducts, including Accutech instruments, SCADAPack
controllers and Trio radios.

Power RICH System
-
Enterprise Edition Mobile

Power RICH System
-
Enterprise Edition Mobile is an Android TM based mobile client and
server system for Power RICH System
-
Enterprise E
dition
. It brings mobility to SCADA
operations, allowing technical staff and
managers alike to obtain real time information on the
performance of the system, even while
working in remote locations.

Communications between the Power RICH System
-
Enterprise Ed
ition Mobile Server and the
Android TM phones uses
SSL to ensure appropriate encryption is used on all transmitted
data. As the system has
been designed from the ground up as a mobile platform, display
and data retrieval is
achieved in seconds, even for co
mplicated trends or large event journal
queries.

Users are notified of new alarm conditions relevant to their area of responsibility, and can
action those alarms using the built in alarm and event lists. The database browser provides
detailed status information related to any database object to allow more in depth problem


SCADA Expert
Power RICH System
-
Enterprise
2013 R1 Release Notes

Page
40

of 6

diagnosis. Trends provide users with the ability to review historic data to make the right

operational decisions for the future and user favorites allow users to sto
re the most
commonly
used views on their phone for easy retrieval.

Users can get access to tabular data providing easy analysis and comparison. Overall
system Key Performance Indicators for management, production summaries, system water
flows, reservoir le
vels etc can all be easily added and made available to users as custom
queries.

Example Projects

Wastewater Starter Application Project

A new application example is included within the Example Projects to provide a foundation
for development of a real
-
worl
d Wastewater Lift Station. This example leverages the close
integration of the SCADAPack E RTU objects and includes sample IEC 61131 logic for the
SCADAPack E RTU. The project also includes interfaces to other Schneider Electric

Equipment; such as, an Alti
var 61/71 Drive, a PowerLogic PM1000 Energy Meter, and
Phaseo Power Supply modules.

In addition a new Design Guide has been included in the TRSS Resource Center under
Power
RICH System
-
Enterprise Edition Release Version 2013 R1. This will provide practical
guidelines based on best
practices for the successful design of larger Power RICH System
-
Enterprise Edition deployments,
focusing on server and client performance and

efficient design
of the database and mimics.
Strategies discussed in this document are demonstrated within
the above application
example.

SPECIFICATION for PMCS



41



9.5

Product Summary

See 2013 R1 Add
ed features above.


System Historian



PMCS Product Summary:

An open and resilient architecture for
gathering, analyzing and reporting on
operational and commercial data, with
powerful configuration tools, high
performance
and cost
-
effective licensing



HISTORIAN PLATFORM


Data Sources

Data can be acquired and stored

simultaneously from:

-

Any OPC data source (e.g. Intellution /
Wonderware / Iconics / Citect
PMCS

/ OPC
drivers to PLCs)

-

Directly from PLCs and RTUs via built
-
in
drivers (e.g. DNP3, Modbus, Fieldbuses)

-

Enterprise databases via ODBC (e.g. Oracle,
SQLserver)

Point Name Sizes

Up to 255 characters in OPC tag format

Database size

License controlled

Failover

Failover for
data sources and for the database
server

Multiprocessor support

Yes

Backfill to eliminate data loss

Automatic, if supported by data source

Redundancy

Built
-
in dual network support, built
-
in
main/standby and triple
-
redundant server
support, performance
server support



CONFIGURATION


Drag
-
and
-
drop

configuration

Yes

“Fill in the form”

configuration of specific

properties

Yes


with interactive hover
-
help and advice on
configuration consistency

Express Wizards for

communications

Yes


Templates
provide a powerful way to
structure and manage duplicate configuration
using object oriented techniques

Long name support for

attributes and folders

Yes

User definable folder

structures and tree

hierarchy

Yes

Alias support for plain

Yes

SPECIFICATION for PMCS



42


System Historian

text names of plant

floor data tags

User definable field definitions

Yes

Automation Interface for
uploading configuration quickly

Yes



VISUALIZATION

TOOLS


Live plant mimic displays

Yes

Historic Trend displays

Yes

Trend displays with on
-
line
pan/zoom navigation

Yes

Trend displays with derived
traces

Yes

Trend displays with time
-
offsets
(e.g. for forecasting and
comparison)

Yes

Trend displays with X
-
Y Plots

Yes

Trend displays with Customized
Aggregates

Yes


Full aggregate support including quality
(% good
etc.) and statistical measures

Data Lists

Yes


both pre
-
built and customized lists on full
display client and web clients

Gantt charts

Yes


via Crystal Reports

Pareto charts

Yes


via Crystal Reports

Copy
-
and
-
paste

exporting

Yes

Crystal

reports interface

Yes


layout and generated report files are fully
managed by the server

Excel spreadsheet

interface

Yes


via ODBC or third party OPC Add
-
ons

Web browser interface

Yes


automatically generated with integrated
live mimic displays

Configurable alarm parameters

Yes

Live alarm list

Yes

Redirection of alarms via email
and SMS

Yes



DATA STORAGE


Event log

Yes

Historic point data

Yes

Integer

Yes

Long

Yes

Float/real

Yes

Double

Yes

String

Yes

All real
-
time and historic
PMCS

data stored in engineering units


Yes

SPECIFICATION for PMCS



43


System Historian

OPC quality status and

sub
-
status

Yes

Entry, logging and identification
of new or modified data

Yes

Automatic managed archive to
offline media

Yes

Aggregates available via ODBC
Interface (enables point and click
reports of historic data, and all
data is stored in raw form for full
data analysis)

Yes



HISTORIAN

PARAMETERS


Store @
PMCS

poll rate

Yes

Historic compression

Yes


by significant value change, %, range and
with minimum interval

Historic
enable/disable

Yes

Individual trend default time
bases

Yes, per point

Historic storage on exception

Yes, important changes stored (e.g. crossing an
alarm threshold)

Time series database

Yes


stores exact timestamp, scaled value with
engineering units,
alarm status, point quality
and reason for storage with every piece of
historic data

Adjustable retention rates

Yes, different thresholds can apply to different
servers

Adjustable archive rates

Yes, can be controlled through database (e.g.
scheduled or a
d
-
hoc archives)



SECURITY


Security model

Security model with additional attributes such
as hand
-
entry/modification, alarm management
and view permissions etc

Import/Export of configuration
with security permissions

Yes
-

point and click

Password
encryption for

internet security

Yes

Multiple areas and levels

for each user

Yes

Permissions can be

defined to the point level

Yes

Permissions differentiate:

-

Folder and attribute


visibility

-

Attribute display

-

Attribute write
-
back

-

Attribute
parameter


changes

Yes

SPECIFICATION for PMCS



44


System Historian

-

Security administration

Permissions apply

to configuration

environment as well as

client environment

Yes



DATA MIGRATION


Upload to relational

databases

Yes

Client export facilities

Yes

Copy to clipboard

facilities

Yes

API

interface

Yes


OLE Automation (COM), access via Visual
Basic etc.

OPC Client interfaces

Yes
-

Data access, Historic Data and
Alarm/Event

Built
-
in XML/SOAP queries

Yes

Built
-
in .NET interface

Yes



CUSTOMIZATION


Crystal Reports full

customizable
and user

definable reporting

facilities (report development
requires Crystal Reports
software)

Yes

Customization of web displays

Yes

Logical operation features

Yes
-

IEC 61131
-
3 compliant




SUPPORT


Phone/email

support teams

Yes

Training packages

Yes

Knowledgebase articles

Yes

Product Website

Yes

Application support

(optional)

Yes

Engineering support

(optional)

Yes






SPECIFICATION for PMCS



45

9.6

Minimum System Devices

9.6

As a minimum,
but not limited to,
system shall be capable of
communicating with the following
devices or devices included in
assembled equipment or substation:

a.

ABB DPU
-
2000R or PCD2000 with Modbus (RTU)
/DNP

over RS
-
485 por
t

or
Ethernet
.

b.

ABB TPU
-
2000R with Modbus (RTU)
/DNP

over RS
-
485
port and newer RET650 in DNP.

c.

ABB MSOC with Modbus (ASCII) RS
-
485

port

and new
615 units.

d.

ABB GPU
-
2000R with Modbus (RTU) protocol over RS
-
485 port.

e.

ABB LVCPU1000/MPSC
-
2000 with Modbus (RTU) RS
-
485 port.

f.

GE Multilin devices (SR750/760, F60, PQM, 269+/469,
489,
UR Series,
etc) with Modbus (RTU)
/DNP

RS
-
485 port

or Ethernet
.

g.

GE MicroVesaTrip through gateway using Modbus (RTU)
RS
-
485 port

or Ethernet
.

h.

Electro Industries series of devices with Modbus (RTU)
RS
-
485 port

or Ethernet
.

i.

Power Measurements Limited
(Sq D)

series of devices with
Modbus (RTU)
/DNP

RS
-
485

or E
thernet
.

j.

Basler with Modbus (ASCII) RS
-
485 port

or Ethernet
.

k.

Cutler
-
Hammer IQ Data Plus, IQ Analyzer, IQ 1000II
, and
other C
-
H Devices using the C
-
H Netlink

Modbus protocol
conversion products & RS
-
485 port
or

Ethernet.

l.

Square D 2200 series with Modbus (RT
U) RS
-
485 port

and
new PM devices.
.

m.

SATEC line of meters
with Modbus (RTU/DNP
via RS
-
485 or Ethernet.

n.

SEL all units via SEL2032 or directly via 232 or 485
ports with Modbus (RTU) or DNP 3.0 and o
v
er
Ethernet

and the new 3050 units. All SEL with Modbus
or
DNP are handled.
.

o.

Other vendors not named, but with Modbus

or DNP 3.0

RS
-
485 ports

or Ethernet
.

p.

All of ICMI devices

with DNP.

SPECIFICATION for PMCS



46

q.

QEI Capacitor Bank controller,
QCE11G14T eCap II
Standard, line post current senor input, AT929 neutral
current sensor input, G me
ter base mounting, temperature
sensor


9.7

Minimum Display Parameters from Devices

9.7

The
PMCS

software shall be capable of displaying the following
information from equipment:

a.

Individual phase and ground currents.

b.

Phase
-
to
-
phase and phase
-
to
-
neutral voltage
s.

c.

Vars, power factor, frequency.

d.

Watts, watt demand, watt
-
hours, and Var
-
hours.

e.

Amp demand.

f.

Alarm on circuit timing out to trip, cause of alarm, and
magnitude of current causing the trip.

g.

Alarm on circuit breaker tripping, cause of trip, and
magnitude

of the current causing the trip.

h.

Circuit breaker
statuses that

includ
e

open, close, tripped,
truck position (connected, test, or disconnected).

i.

Time
-
stamped trip including cause of trip, magnitude of
trip with time/date stamp from the device.




SPECIFICATION for PMCS



47

9.8

PMCS

Equi
pment supplied by Seller

9.8.1

Bidder shall furnish all data and information by filling in all
blanks:


Equipment




Manufacturer

Model/Type


Host/IO Server
(s) (Redundancy)

____________

___________

Display/
Web

Client



____________

___________

Monitor for IO Ser
ver

(s)


____________

___________

Monitor for Display/
Web Client

____________

___________

Inkjet Printer




____________

___________

Keyboard




____________

___________

Pointing device



____________

___________

UPS for IO Server
(s)



____________

_______
____

UPS for Display/
Web Client


____________

___________

Communication Converters

(RS
-
232/RS
-
485/Fiber Optics)

____________

___________

Network Interface Card


____________

___________

IO Server
(s)

Operating System

____________

___________

Display/
Web
Client

OS


____________

___________

PMCS

software



____________

___________

IO Server
(s)

Hard Drive
s


____________

___________

Display/
Web

Hard Drive


____________

___________

Video Card
s




____________

___________

Memory Size & Type



____________

_____
______

Computer Processor



____________

___________

Ancillary software products


____________

___________