453-SWD-RMM-0103020 R01 S3 Bk2 SCC I&C 1

SCC and OCC
Set 3 Book 2 - Centralized Control System (SCC)

Integration and Configuration
453-SWD-RMM-0103020
453-SWD-RMM-0103020 Rev.01
MO-15.98.XX.XX/6XX-020 Rev.01
Revision Log
453-SWDRMM0103020
Metro No. &

Rev.
00
N/A
Rev. 01
MO15.98.XX.X
X/6XX-020
Rev. 01
File name: 453-SWD-RMM-0103020.doc
Date
Description of Changes
(yyyy-mm-dd)
Not used for the Sao Paulo project. In accordance with

MAN-10-202 rev 02 "Preparation and Supply of Technical
Documentation of Systems, Equipment and Installation",
the first issue shall be Rev. 01.
2014-02-21 First issue.
Confidential and proprietary

Page 2 of 2
Template ID-Number: 006735

Template Instruction ID-Number: 006736
So Paulo Expresso Tiradentes Monorail

Line 15 - Silver (Ipiranga/Cidade Tiradentes)
Set 3: SCC and OCC

Book 2: Centralized Control
System (SCC) Integration and
Configuration
Part 1
453-SWD-RMM-0103020
MO-15.98.XX.XX/6XX-020
Rev. 01
Rev. 01
This document and its contents are the property of BOMBARDIER Inc. or its subsidiaries. This document contains confidential proprietary information. The reproduction, distribution, utilization, or the
communication of this document or any part thereof without express authorization is strictly prohibited.
Offenders will be held liable for the payment of damages.
2014, Bombardier Transportation and its subsidiaries. All rights reserved.
List of Books
Set 3: SCC and OCC
Book 1 - SCC Operation
Book 2 - SCC Integration and Configuration
Book 3 - SCC Simulator
THIS PAGE LEFT BLANK INTENTIONALLY
MANUAL COMMENT FORM

Please use this Manual Comment Form to submit comments and suggested changes
to this manual. If your comments fit on this single sheet, you can fold this sheet into
thirds on the dotted lines, staple or tape it closed, and then mail it to the Technical
Publications and Training group.
Employer:
Site:
...........................................................
Book Title: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Section Number/Page: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Topic:
...........................................................
Text as Written:
...........................................................
...........................................................
...........................................................
...........................................................
...........................................................
...........................................................
(attach pages as needed)
Correct/Suggested Text:
...........................................................
...........................................................
...........................................................
...........................................................
...........................................................
...........................................................
Reason for suggested change:
...........................................................
...........................................................
...........................................................
...........................................................
...........................................................
Signature:
...........................................................
Today's Date: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Do you wish to be notified? Yes No
Your address:
...........................................................
...........................................................
Phone:
...........................................................
Place
Stamp
Here
Technical Publications and Training

Bombardier Transportation, Systems Division
P.O. Box 220, Station A
Kingston, Ontario Canada K7M 6R2
LIST OF EFFECTIVE PAGES

Insert latest revised pages, dispose of superseded pages in accordance with applicable orders.
Dates of issue for original and revised pages are:
Original . . . . . . . . . . .
Revision . . . . . . . . . .
Revision . . . . . . . . . .
Revision . . . . . . . . . .
Revision . . . . . . . . . .
01 . . . . . . . . . . .2014.02.21
02. . . . . . . . . . . .
03. . . . . . . . . . . .
04. . . . . . . . . . . .
05. . . . . . . . . . . .
Revision
Revision
Revision
Revision
. . . . . . . . . . . 06. . . . . . . . . . .
. . . . . . . . . . . 07. . . . . . . . . . .
. . . . . . . . . . . 08. . . . . . . . . . .
. . . . . . . . . . . 09. . . . . . . . . . .
The total number of pages in SCC & OCC Set 3, Book 2, Centralized Control System (SCC)
Integration and Configuration is 256 consisting of the following:
Page No.
Revision No.
Document Tracking Page . . . . . . . . . . . 01
Part 1
Title Page. . . . . . . . . . . . . . . . . . . . . . . . 01
List of Books . . . . . . . . . . . . . . . . . . . . . 01
Manual Comment Form . . . . . . . . . . . . 01
List of Effective Pages
A to B . . . . . . . . . . . . . . . . . . . . . . . . . . 01
Table of Contents
i to xiv . . . . . . . . . . . . . . . . . . . . . . . . . . 01
Page No.
Revision No.
Index
Index-1 to Index-2. . . . . . . . . . . . . . . . . 01
Part 2
Title Page . . . . . . . . . . . . . . . . . . . . . . . 01
Title Page . . . . . . . . . . . . . . . . . . . . . . . 01
Dell
Dell PowerEdge M1000e Enclosure
Owners Manual
Regulatory Model: BMX01, Rev A04
2013 - 09
(104 Pages) . . . . . . . . . . . . . . . . . . . . . . 01
Section 1 - General Information

1-1 to 1-4 . . . . . . . . . . . . . . . . . . . . . . . . 01
Section 2 - Description and Operation
2-1 to 2-88 . . . . . . . . . . . . . . . . . . . . . . . 01
Section 3 - Troubleshooting
3-1 to 3-2 . . . . . . . . . . . . . . . . . . . . . . . . 01
Section 4 - Corrective Maintenance
4-1 to 4-10 . . . . . . . . . . . . . . . . . . . . . . . 01
Section 5 - References
5-1 to 5-2 . . . . . . . . . . . . . . . . . . . . . . . . 01
Section 6 - Preventive Maintenance
6-1 to 6-2 . . . . . . . . . . . . . . . . . . . . . . . . 01
Section 7 - Parts Listing
7-1 to 7-14 . . . . . . . . . . . . . . . . . . . . . . . 01
453-SWD-RMM-0103020
MO-15.98.XX.XX/6XX-020
Rev. 01
Rev. 01
Rev. 01
Rev. 01
453-SWD-RMM-0103020
MO-15.98.XX.XX/6XX-020
SO PAULO EXPRESSO TIRADENTES MONORAIL

LINE 15 - SILVER (IPIRANGA/CIDADE TIRADENTES)
SCC & OCC SET 3, BOOK 2 - CENTRALIZED CONTROL SYSTEM (SCC) INTEGRATION AND
CONFIGURATION
TABLE OF CONTENTS
SECT/PARA
1
TITLE
GENERAL INFORMATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
1.1
1.2
1.3
2
INTRODUCTION. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
EQUIPMENT IDENTIFICATION AND LOCATION . . . . . . . . . . . . 1-1
SPECIFICATIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
DESCRIPTION AND OPERATION . . . . . . . . . . . . . . . . . . . . . . . . 2-1
2.1
2.1.1
2.1.2
2.1.3
2.1.3.1
2.1.3.2
2.1.3.3
2.1.3.4
2.1.3.5
2.1.3.6
2.1.3.7
2.1.4
2.1.5
2.1.6
2.1.6.1
2.1.6.2
2.1.6.3
2.1.6.4
2.1.7
2.2
2.3
2.4
2.4.1
2.4.2
2.4.3
2.5
2.5.1
2.5.1.1
2.5.1.2
2.5.1.3
2.5.2
2.5.3
2.6
SYSTEM OVERVIEW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5
System Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7
SCC Safety . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7
Non-Vital Consideration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7
Operation Prevention and Protection . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7
Redundant Architecture. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8
Command Confirmation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8
User Privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8
Network Security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9
Input Verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9
Programmable Logic Controllers (PLCs) . . . . . . . . . . . . . . . . . . . . . . . 2-9
Performance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9
Reliability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10
Redundant Server Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10
Redundant Network Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11
Redundant Protocol Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11
Minimal Workstation Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11
Maintainability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11
ARCHITECTURE OVERVIEW . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11
SCC SUBSYSTEM CORE COMPONENTS ARCHITECTURE . . . 2-11
SCC CORE SUPPORT COMPONENTS ARCHITECTURE . . . . . . 2-13
Unified Data Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-13
Alarm Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-13
Alarm Logger and Trend Logger . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-13
SCC DATA COLLECTION ARCHITECTURE . . . . . . . . . . . . . . . . 2-13
Modbus Over TCP/IP and Poller Control Devices . . . . . . . . . . . . . . . 2-13
Source 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-13
Source 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-13
Source 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-14
SNMP Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-14
OPC Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-14
SCC GUI VISUALIZATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-14
453-SWD-RMM-0103020
MO-15.98.XX.XX/6XX-020
Rev. 01
Rev. 01
2.7
2.7.1
2.7.2
2.7.3
2.7.4
2.7.5
2.7.6
2.7.7
2.7.8
2.7.9
2.7.9.1
2.7.9.2
2.7.9.3
2.7.9.4
2.7.10
2.7.11
2.7.11.1
2.7.11.2
2.7.11.3
2.7.12
2.8
2.8.1
2.8.2
2.8.3
2.9
2.9.1
2.9.2
2.9.3
2.10
2.10.1
2.10.2
2.10.2.1
2.10.2.2
2.10.2.3
2.10.3
2.10.3.1
2.10.3.2
2.10.3.3
2.10.3.4
2.10.3.5
2.10.3.6
2.10.3.7
2.10.3.8
2.10.3.9
2.10.4
2.10.4.1
2.10.4.2
2.10.4.3
Rev. 01
Rev. 01
SCC PROCESSOR MODULES . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Power Calc Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Passenger Information Interface Module . . . . . . . . . . . . . . . . . . . . . .
Public Address (PA) Interface Module . . . . . . . . . . . . . . . . . . . . . . . .
NetCheck . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SME CCTV Alarms Interface Software Module . . . . . . . . . . . . . . . .
Alarm Suspension . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Disabled Passengers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Sounder Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Scheduler Module and List of Objectives (LOBJ) . . . . . . . . . . . . . . .
CommandLineOPC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
WriteFile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ModbusMsg. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TCPMsg. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SCC Housed Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SCE/SEA/SFP Simulator (SIMEA) . . . . . . . . . . . . . . . . . . . . . . . . . .
VCR Controls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SimData Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Manual Mode Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
DDAS Interface (Reporting and Playback Support) . . . . . . . . . . . . . .
SCC SUBSYSTEM CORE COMPONENTS LOGIC
DESCRIPTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SCC SUBSYSTEM CORE SUPPORT COMPONENTS LOGIC
DESCRIPTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SCC SUBSYSTEM DATA COLLECTION LOGIC DESCRIPTION
Modbus Poller Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
General Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
OPC Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Modbus Server Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Comments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Config.Txt for the Modbus Poller . . . . . . . . . . . . . . . . . . . . . . . . . . . .
OPC.SERVER opc_server_name . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Modbus.Communication.Register modbus_register . . . . . . . . . . . . . .
Modbus.Primary.IP modbus_server_IP_address . . . . . . . . . . . . . . . .
Modbus.Primary.Port modbus_server_port . . . . . . . . . . . . . . . . . . . .
Modbus.Backup.IP modbus_server_IP_address . . . . . . . . . . . . . . . . .
Modbus.Backup.Port modbus_server_port . . . . . . . . . . . . . . . . . . . . .
Modbus.Slave.ID slave_ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Modbus.PollRate ms_delay_between_polls . . . . . . . . . . . . . . . . . . . .
Modbus.FastPollRate ms_delay_between_polls . . . . . . . . . . . . . . . . .
Poll.Txt for the Modbus Poller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
R: (Read) Parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Address: Parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Range: Parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ii
2-14
2-15
2-15
2-15
2-15
2-15
2-16
2-16
2-16
2-17
2-17
2-18
2-18
2-18
2-18
2-19
2-19
2-19
2-20
2-20
2-21
2-21
2-22
2-22
2-22
2-22
2-22
2-22
2-23
2-23
2-23
2-23
2-23
2-24
2-24
2-24
2-24
2-24
2-24
2-25
2-25
2-25
2-25
2-25
2-25
2-25
2-25
2-26
453-SWD-RMM-0103020
MO-15.98.XX.XX/6XX-020
2.10.5
2.10.5.1
2.10.5.2
2.10.5.3
2.10.5.4
2.10.5.5
2.10.5.6
2.10.5.7
2.10.5.8
2.10.5.9
2.10.5.10
2.10.6
2.10.6.1
2.10.6.2
2.10.6.3
2.10.6.4
2.10.7
2.10.8
2.10.9
2.10.9.1
2.10.9.2
2.10.9.3
2.10.9.4
2.10.9.5
2.10.9.6
2.10.10
2.10.11
2.10.12
2.10.13
2.10.13.1
2.10.13.2
2.10.13.3
2.10.14
2.10.14.1
2.10.14.2
2.10.14.3
2.11
2.11.1
2.11.2
2.11.3
2.12
2.12.1
2.12.1.1
2.12.1.2
2.12.1.3
2.12.1.4
2.12.1.5
2.12.1.6
2.12.2
2.12.2.1
Map.Txt for the Modbus Poller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Addr Parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tag Parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Type Parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
BitOffset Parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
BitLength Parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
RawMin and RawMax Parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . .
FinalMin and FinalMax Parameter . . . . . . . . . . . . . . . . . . . . . . . . . . .
Decimals Parameter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
RegType Parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Command Tag Formatting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Modbus Poller Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Polling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Requesting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Build . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Reconnect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Modbus Poller Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Conditional Modbus Poller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Conditional Modbus Poller Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . .
Poll.Txt for Conditional Modbus Poller . . . . . . . . . . . . . . . . . . . . . . .
C: Parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Bit: Parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Value: Parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Addr: Parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
I: Parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Conditional Polling Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Conditional Modbus Poller Processing . . . . . . . . . . . . . . . . . . . . . . . .
Conditional Modbus Poller Outputs . . . . . . . . . . . . . . . . . . . . . . . . . .
SNMP Manager and Unified Data Manager (Raw Data Bridge) . . . .
Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Gen Broker and Unified Data Manager (Raw Data Bridge) . . . . . . . .
Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SCC VISUALIZATION LOGIC DESCRIPTION . . . . . . . . . . . . . . .
Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SCC SUBSYSTEM PROCESSORS LOGIC DESCRIPTION. . . . . .
Power Calc Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Config.Txt: Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Map.Txt: Map Input Coding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Map.Txt: Link Input Coding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PI Interface, SDK, and Server Module . . . . . . . . . . . . . . . . . . . . . . . .
453-SWD-RMM-0103020
MO-15.98.XX.XX/6XX-020
iii
2-26
2-26
2-26
2-27
2-27
2-27
2-27
2-27
2-28
2-28
2-28
2-28
2-28
2-29
2-30
2-30
2-30
2-30
2-31
2-31
2-31
2-32
2-32
2-32
2-32
2-32
2-32
2-33
2-33
2-33
2-33
2-34
2-34
2-34
2-34
2-34
2-34
2-35
2-35
2-35
2-35
2-36
2-36
2-36
2-37
2-38
2-39
2-39
2-42
2-42
Rev. 01
Rev. 01
2.12.2.2
2.12.2.3
2.12.2.4
2.12.2.5
2.12.2.6
2.12.2.7
2.12.2.8
2.12.2.9
2.12.2.10
2.12.2.11
2.12.3
2.12.3.1
2.12.3.2
2.12.3.3
2.12.3.4
2.12.3.5
2.12.3.6
2.12.3.7
2.12.4
2.12.4.1
2.12.4.2
2.12.4.3
2.12.4.4
2.12.5
2.12.5.1
2.12.5.2
2.12.5.3
2.12.5.4
2.12.6
2.12.6.1
2.12.6.2
2.12.6.3
2.12.6.4
2.12.7
2.12.7.1
2.12.7.2
2.12.7.3
2.12.7.4
2.12.8
2.12.8.1
2.12.8.2
2.12.8.3
2.12.8.4
2.12.9
2.12.9.1
2.12.9.2
2.12.9.3
2.12.9.4
2.13
2.13.1
Rev. 01
Rev. 01
PI_Commands.txt: Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
OPC Server: Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Message Files: Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Client Side: Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Server Side Content: Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Place Holder Lookup: Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Content Request: Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PA Interface (PA Interface, SDK, and the PA Server) . . . . . . . . . . . .
Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
OPC Server: Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Message Files: Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PA Interface: Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Net Check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
CCTV Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Alarm Suspension . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Diagnostic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Disabled Passengers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Diagnostic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Sounder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Scheduler (List of Objectives). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SCC HOST APPLICATIONS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Radio Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
iv
2-44
2-44
2-44
2-48
2-48
2-49
2-50
2-51
2-52
2-53
2-53
2-55
2-55
2-55
2-56
2-59
2-61
2-61
2-61
2-62
2-62
2-63
2-63
2-63
2-63
2-65
2-66
2-66
2-66
2-68
2-68
2-69
2-69
2-70
2-70
2-70
2-71
2-71
2-71
2-71
2-72
2-73
2-73
2-73
2-74
2-78
2-80
2-80
2-82
2-82
453-SWD-RMM-0103020
MO-15.98.XX.XX/6XX-020
2.13.1.1
2.13.1.2
2.13.1.3
2.13.2
2.13.2.1
2.13.2.2
2.13.2.3
2.14
2.14.1
2.14.1.1
2.14.1.2
2.14.1.3
2.14.2
2.14.2.1
2.14.2.2
2.14.2.3
2.14.3
2.14.3.1
2.14.3.2
2.14.3.3
2.14.4
2.14.4.1
2.14.4.2
2.14.4.3
2.14.5
2.14.5.1
2.14.5.2
2.14.5.3
3
2-82
2-82
2-82
2-82
2-82
2-83
2-83
2-83
2-83
2-83
2-83
2-84
2-84
2-84
2-84
2-85
2-85
2-85
2-85
2-86
2-86
2-86
2-86
2-86
2-86
2-86
2-87
2-87
TROUBLESHOOTING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
3.1
3.2
SAFETY PRECAUTIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

SYSTEM TROUBLESHOOTING . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
CORRECTIVE MAINTENANCE . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
4.1
4.2
4.3
4.4
4.4.1
4.5
4.5.1
4.6
4.6.1
4.7
4.7.1
4.8
4.8.1
5
Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
VORS Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SCHEDULER SUPPORT APPLICATIONS . . . . . . . . . . . . . . . . . . .
Command Line OPC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
WriteFile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ModbusMsg. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TCPMsg. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SendMail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SAFETY PRECAUTIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TORQUE VALUES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SPECIAL TOOLS AND TEST EQUIPMENT. . . . . . . . . . . . . . . . . . .
HALF BLADE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Removal and Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
FULL BLADE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
AC POWER SUPPLY. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
FAN MODULE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
I/O MODULE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-1
4-1
4-1
4-1
4-1
4-3
4-3
4-5
4-5
4-5
4-5
4-8
4-8
REFERENCES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1
453-SWD-RMM-0103020
MO-15.98.XX.XX/6XX-020
Rev. 01
Rev. 01
5.1
6
DOCUMENTATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1
PREVENTIVE MAINTENANCE . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1
6.1
6.2
7
SAFETY PRECAUTIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1

PREVENTIVE MAINTENANCE SCHEDULE . . . . . . . . . . . . . . . . . 6-1
PARTS LISTING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1
7.1
7.2
Rev. 01
Rev. 01
PARTS LISTING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1

PARTS CATALOGUE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1
vi
453-SWD-RMM-0103020
MO-15.98.XX.XX/6XX-020
LIST OF FIGURES
FIGURE
TITLE
1-1
SCC Operator Equipment Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
2-1
2-2
2-3
2-4
2-5
2-6
2-7
2-8
SCC Subsystem Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2

SCC Data Flow and Processing (2 Sheets). . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3
SCC Server Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6
SCC Server Software Architecture. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12
Power Calc Diagnostic GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-40
PI Diagnostic GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-54
CCTV Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-67
Scheduler . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-81
4-1
4-2
4-3
4-4
4-5
Half Blade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Full Blade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
AC Power Supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fan Module. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
I/O Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7-1
7-2
7-3
7-4
7-5
7-6
SCC Cabinet Assembly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2

SCC SCADA Workstation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-4
SCC SCADA Workstation SCCW1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-6
SCC SCADA Training and Development Workstations . . . . . . . . . . . . . . . . 7-8
Administration and Services System Workstation . . . . . . . . . . . . . . . . . . . . 7-10
SCC SCADA Workstation SCCW6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-12
4-2
4-4
4-6
4-7
4-9
LIST OF TABLES
TABLE
TITLE
1-1
1-2
1-3
Equipment Identification and Suppliers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

General Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
Equipment Specifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
2-1
List of Operators. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-76
3-1
3-2
3-3
3-4
3-5
Power Supply Module Troubleshooting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

Fan Module Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
Input/Output Module Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
Cabinet Assembly Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
Software Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
5-1
Reference Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1
6-1
6-2
SCC Hardware Equipment Preventive Maintenance Schedule . . . . . . . . . . . . 6-1

SCC Software Preventive Maintenance Schedule . . . . . . . . . . . . . . . . . . . . . . 6-1
453-SWD-RMM-0103020
MO-15.98.XX.XX/6XX-020
vii
Rev. 01
Rev. 01
LIST OF ACRONYMS AND ABBREVIATIONS

AMV
ATC
CCO
CCTV
CRU
DDAS
DTS
E&M
FEC
GUI
HAP
LCD
MMS
OCC
OCS
PDA
PIP
PLC
PSDS
RSH
SAL
SAM
SAO
SCA
SCAP
SCC
SCE
SCF
SCL
SCMVD
SCP
SCT
SEA
SFP
SIMEA
SME
SMM
STD
TMS
UGI
VoIP
VORS
Rev. 01
Rev. 01
Track Switch
Automatic Train Control
Control Centre Operator
Closed Circuit Television
Customer Replaceable Unit
Distributed Data Acquisition System
Data Transmission System
Electrical and Mechanical
Front End Communication
Graphical User Interface
Hostler Access Panel
Liquid Crystal Display
Multimedia Text
Operations Control Centre
On-board Communications System
Personal Digital Assistant
Passenger Intercom Panel
Programmable Logic Controller
Platform Screen Door System
Time Synchronization Network
Electric Supply System
Maintenance Support System
Operational Automatism System
Access Control System
Fare Collection & Passenger Control
Centralized Control System
Traction Power Control System, Building Power
Fixed Communications System (Telephone)
Local Control System
Mobile Voice, Video and Data Mobile System
Yard Control System
Train Control and Regulation System
Auxiliary Equipment Control System
Passenger Flow Control System
SCC Simulator
Electronic Monitoring System
Multimedia System (PA/PI)
Data Transmission System
Train Management System
User Guide Interface
Voice Over IP
VoIP Operational Radio System
viii
453-SWD-RMM-0103020
MO-15.98.XX.XX/6XX-020
GENERAL SAFETY PRECAUTIONS

A.
This publication utilizes three levels of precautionary notices, as follows:
WARNING:
INDICATES AN OPERATION, SEQUENCE, OR FUNCTION THAT, IF NOT

OBSERVED, MAY CAUSE SERIOUS INJURY OR DEATH TO PERSONNEL
AND/OR SERIOUS DAMAGE TO OR LOSS OF EQUIPMENT. STRICTLY
ADHERE TO ALL WARNINGS.
CAUTION:
Indicates an operation, sequence, or function that, if not observed, may

cause damage or malfunction of equipment.
NOTE:
Provides additional explanatory information that may not be readily apparent from
the text or illustrations.
Warnings and cautions are intended as guides to indicate serious areas of potential
hazard. Normal safety operating and maintenance procedures for working with air
conditioning equipment, low voltage power supply, and high pressure hydraulic
components must be observed at all times.
WARNING: ONLY AUTHORIZED PERSONNEL SHALL BE ALLOWED IN THE MAINTENANCE AREA, WHICH SHALL BE ISOLATED AND WELL IDENTIFIED WITH PROMINENTLY DISPLAYED WARNING SIGNS. SUCH
SIGNS MUST ONLY BE REMOVED BY THE PERSON WHO INITIALLY
PLACED THEM.
WARNING: DISCONNECT ALL SOURCES OF POWER FROM THE TRAIN BEFORE
JACKING. IF POWER SUPPLIES ARE NOT REMOVED FROM THE
TRAIN BEFORE PERFORMING THE JACKING PROCEDURE, A LETHAL
VOLTAGE MAY EXIST BETWEEN THE CARBODY AND GROUND.
WARNING: WHEN WORKING IN AN AREA ACCESSIBLE TO THE PUBLIC, THE
WORK AREA MUST BE ADEQUATELY PROTECTED IN ACCORDANCE
WITH THE OPERATING AUTHORITY'S RULES AND REGULATIONS.
WARNING: DANGEROUS VOLTAGES ARE PRESENT THROUGHOUT SOME
EQUIPMENT. EXERCISE EXTREME CARE WHEN WORKING IN CLOSE
PROXIMITY TO ELECTRICALLY POWERED EQUIPMENT.
WARNING: BEFORE REPLACING ELECTRICALLY POWERED
ENSURE THAT AC AND/OR DC POWER IS REMOVED.
EQUIPMENT,
WARNING: ALL WORK TO BE PERFORMED ON ANY PART OF THE SYSTEM

MUST BE CARRIED OUT IN ACCORDANCE WITH THE WORK AUTHORIZATION PROCEDURES.
WARNING: BEFORE INSPECTING, MAINTAINING, REPAIRING, OR REPLACING
ANY ELECTRICALLY POWERED EQUIPMENT ON THE GUIDEWAY,
ENSURE THAT THE POWER IS REMOVED USING A PROVEN VOLTMETER, LOCK OUT PROCEDURES HAVE BEEN FOLLOWED, AND THAT A
GROUNDING DEVICE IS INSTALLED FOLLOWING APPROVED ARC
FLASH PROCEDURES.
453-SWD-RMM-0103020
MO-15.98.XX.XX/6XX-020
ix
Rev. 01
Rev. 01
WARNING: SOME EQUIPMENT MAKES USE OF LARGE CAPACITORS. HAZARDOUS VOLTAGES ARE STILL PRESENT INSIDE CERTAIN ENCLOSURES
FOR A PERIOD OF AT LEAST 5 MINUTES AFTER THE REMOVAL OF
THE HIGH VOLTAGE. USE A PROVEN VOLTMETER TO VERIFY THAT
VOLTAGE IS NOT PRESENT.
WARNING: VERIFY THAT THE MANUAL DISC BRAKES ARE RESTORED TO NORMAL SERVICE BEFORE OPERATING THE TRAIN ON THE GUIDEWAY.
THE DISC BRAKES WILL NOT FUNCTION WHEN THEY ARE MANUALLY RELEASED.
WARNING: BEFORE DISCONNECTING HYDRAULIC LINES OR PERFORMING
MAINTENANCE ON HYDRAULIC COMPONENTS, ENSURE THAT
HYDRAULIC PRESSURE IS NOT PRESENT.
WARNING: BEFORE DISCONNECTING PNEUMATIC/NITROGEN LINES OR PERFORMING MAINTENANCE ON PNEUMATIC/NITROGEN COMPONENTS, ENSURE THAT PRESSURE IS NOT PRESENT. BE AWARE
THAT RELIEVING LINE PRESSURE DOES NOT NECESSARILY RELIEVE
THE PRESSURE DOWNSTREAM OF SOME CONTROL COMPONENTS.
WARNING: BEFORE DISCONNECTING COOLANT LINES OR PERFORMING MAINTENANCE ON COOLING SYSTEM COMPONENTS, ENSURE THAT
PRESSURE IS NOT PRESENT. BE AWARE THAT RELIEVING LINE
PRESSURE DOES NOT NECESSARILY RELIEVE THE PRESSURE
DOWNSTREAM OF SOME CONTROL COMPONENTS.
WARNING: THE LIQUID COOLING SYSTEM COMPONENTS AND COOLANT ARE
HOT. ALLOW SUFFICIENT TIME FOR THE EQUIPMENT AND COOLANT TO REACH A SAFE TEMPERATURE BEFORE PERFORMING ANY
MAINTENANCE TASKS.
WARNING: BE AWARE OF UNEXPECTED EQUIPMENT OPERATION. KEEP HANDS
CLEAR OF ROTATING, MOVING, OR ENERGIZED COMPONENTS.
WARNING: CONSULT THE MATERIAL SAFETY DATA SHEETS (MSDSs) BEFORE
WORKING WITH LUBRICANTS, CLEANING AGENTS, OR ANY OTHER
MATERIAL THAT COULD BE HARMFUL, AND STRICTLY ADHERE TO
THE GUIDELINES THEREIN.
WARNING: TO PREVENT SERIOUS INJURY, ALL PERSONNEL DIRECTLY OR INDIRECTLY INVOLVED WITH THE INSPECTION, MAINTENANCE,
REPAIR, AND OVERHAUL OF EQUIPMENT IN THE MAINTENANCE
FACILITY MUST OBSERVE THE FOLLOWING PRECAUTIONS:
Rev. 01
Rev. 01
(1)
Observe all rules and regulations provided by the Operating Authority. If there is
a conflict between the instructions in this manual and the Operating Authority
rules and regulations, the latter shall govern.
(2)
Disconnect power when handling equipment electrical connections or when

checking electrical continuity. Always ground a circuit before touching its components.
(3)
Take proper precautions when handling static sensitive equipment by using

static mats, wrist straps, and using proper grounding techniques.
(4)
Maintain a clean work environment free of grease, oil, and debris. Keep the
work area neat and tidy and ensure work areas are free of trip and fire hazards.
x
453-SWD-RMM-0103020
MO-15.98.XX.XX/6XX-020
(5)
Ensure area is well ventilated when working with materials that produce dangerous fumes. Wear protective gear when handling materials that are injurious
to the skin or eyes.
(6)
When handling heavy components, select a lifting apparatus of adequate type

and capacity for the weight and size involved.
(7)
Wear protective clothing and safety glasses when cleaning with compressed
air to protect against flying debris. Do not direct compressed air toward anyone,
as air can be forced through the skin causing death.
(8)
When attaching hardware is replaced, care must be taken to ensure that

replacement parts match the originals. Incorrectly attaching hardware can
result in personal injury or equipment damage.
(9)
All personnel in the vicinity of the train must be warned to the danger of unexpected equipment operation or train movement. Such warnings must be issued
in the form of prominently displayed temporary signs and placards as well as
verbal instructions. Warning signs must only be removed by the employee who
installed them.
(10)
Occupational health and safety regulations must be complied with when working with ladders. Use strapping when ladders exceed the legislative height minimum.
(11)
Some equipment may have sharp edges and/or corners. Use caution when handling equipment and components, when opening access covers and equipment
lockers, and when working near any equipment enclosures, fan blades, cooling/
heating fins and other such assemblies.
(12)
Some equipment can be very hot or very cold while in operation. To avoid serious burns, allow sufficient time for the equipment to reach a safe temperature
and measure the temperature of the equipment before performing any maintenance tasks.
(13)
Follow all WARNINGS, CAUTIONS, and NOTES found throughout these manuals. If you must use a work procedure or tool not covered in this manual, first
satisfy yourself that the safety of all workers and equipment is not jeopardized
by the method selected.
453-SWD-RMM-0103020
MO-15.98.XX.XX/6XX-020
xi
Rev. 01
Rev. 01
Rev. 01
Rev. 01
xii
453-SWD-RMM-0103020
MO-15.98.XX.XX/6XX-020
SAE Grade 2 Bolts
SAE Grade 5 Bolts
SAE Grade 7 Bolts
SAE Grade 8 Bolts
Size
Dry
lbin
Lub.
lbin
Dry
lbin
Lub.
lbin
Dry
lbin
Lub.
lbin
Dry
lbin
Lub.
lbin
4-40
11
12
4-48
12
13
10
6-32
10
16
12
20
15
23
17
6-40
12
18
13
22
17
25
19
8-32
19
14
30
22
36
27
41
31
8-36
20
15
31
23
38
29
43
32
10-24
27
21
43
32
52
39
60
45
10-32
31
23
49
36
60
45
68
51
1/4-20
66
49
96
75
120
96
144
108
1/4-28
76
56
120
86
144
106
168
120
lbft
lbft
lbft
lbft
lbft
lbft
lbft
lbft
5/16-18
11
17
13
21
16
25
18
5/16-24
12
19
14
24
18
25
20
3/8-16
20
15
30
23
40
30
45
35
3/8-24
23
17
35
25
45
30
50
35
7/16-14
30
24
50
35
60
45
70
55
7/16-20
35
25
55
40
70
50
80
60
1/2-13
50
35
75
55
95
70
110
80
1/2-20
55
40
90
65
100
80
120
90
9/16-12
70
55
110
80
135
100
150
110
9/16-18
80
60
120
90
150
110
170
130
5/8-11
100
75
150
110
190
140
220
170
5/8-18
110
85
170
130
210
160
240
180
3/4-10
175
130
260
200
320
240
380
280
3/4-16
195
145
300
220
360
280
420
320
7/8-9
165
125
430
320
520
400
600
460
7/8-14
185
140
470
350
580
440
660
500
1-8
250
190
640
480
800
600
900
680
1-12
270
200
700
530
860
660
1000
740
1 1/8-7
350
270
800
600
1120
840
1280
960
1 1/8-12
400
300
880
660
1260
940
1440
1080
1 1/4-7
500
380
1120
840
1580
1100
1820
1360
1 1/4-12
550
420
1240
920
1760
1320
2000
1500
1 3/8-6
660
490
1460
1100
2080
1560
2380
1780
1 3/8-12
740
560
1680
1260
2380
1780
2720
2040
1 1/2-6
870
650
1940
1460
2780
2080
3160
2360
1 1/2-12
980
730
2200
1640
3100
2320
3560
2660
NOTE:The values given in this table can be used only in the absence of torque specifications in the procedures included in this manual.
453-SWD-RMM-0103020
MO-15.98.XX.XX/6XX-020
xiii
Rev. 01
Rev. 01
COEFFICIENT OF FRICTION FOR DIFFERENT SURFACES AND LUBRICATING CONDITIONS

SURFACE CONDITIONS
DRY
LUBRICATED
Plain
0.14
0.125
Zinc-plated
Plain
0.125
0.10
Zinc-plated
Zinc-plated
0.125
0.10
SCREW
NUT
Plain
ISO Class 4.6

Thread
Size
0.10
0.125
0.14
ISO Class 4.8 & 5.6

0.10
0.125
0.14
ISO Class 5.8

0.10
0.125
ISO Class 8.8
0.14
0.10
ISO Class 10.9
ISO Class 12.9
0.125
0.14
0.10
0.125
0.14
0.10
0.125
0.14
Ncm
M 1.6
5.5
6.5
7.5
8.5
9.5
10
15
17
18
21
24
25
25
29
30
M 1.8
7.5
9.5
10
10
11.5
12.5
18.5
21
23
26
30
32
32
36
38
M2
10.5
12
13
13.5
15.5
16.5
17
19
21.5
31
35
38
44
50
53
52
60
64
M 2.2
16
18
19
20
22
24
25
28
31
45
51
55
63
71
77
76
86
93
M 2.5
21
25
27
28
32
34
36
39
43
63
73
78
89
102
109
107
123
131
M3
38
44
47
49
56
60
63
72
78
111
128
137
157
180
192
188
215
230
M 3.5
59
68
73
75
86
92
96
110
119
171
196
210
240
275
295
290
330
395
M4
88
102
108
112
128
137
144
166
177
255
290
310
360
410
440
430
495
525
M5
170
200
210
220
250
270
280
320
340
500
575
615
705
810
865
845
970
1040
Nm
M6
3.4
3.7
3.8
4.3
4.6
4.8
5.6
8.6
9.9
10.5
12
14
15
14.5
16.5
18
M7
5.7
6.2
7.1
7.6
9.3
9.7
14
16.5
17.5
20
23
25
24
27
29
M8
7.2
8.3
8.9
9.1
10.5
11
11.7
13.6
14.5
21
24
26
29
34
36
35
40
43
M 10
14.4
16.6
18
18
21
22
23.4
27
29
42
48
51
58
67
72
70
81
87
M 12
25
29
31
31
36
39
41
47
50
72
83
89
101
117
125
121
140
150
M 14
40
46
50
50
58
62
47
74
81
114
132
141
160
185
198
193
220
240
M 16
60
70
76
76
88
95
98
115
124
174
200
215
245
285
305
295
340
365
M 18
83
95
105
105
121
130
135
155
170
240
275
295
340
390
420
405
470
500
M 20
120
135
146
148
171
184
195
219
238
340
390
420
475
550
590
570
660
710
M 22
160
183
198
199
230
250
260
298
322
455
530
570
640
745
800
765
890
960
M 24
203
235
251
255
295
315
330
382
408
580
675
725
820
950
1020
980
1140
1220
M 27
300
348
376
375
435
470
488
566
610
855
995
1070
1210
1400
1510
1450
1680
1810
M 30
405
470
504
510
590
635
658
763
818
1160
1350
1450
1640
1900
2050
1970
2280
2450
M 33
552
645
685
690
800
865
898
1045
1110
1570
1830
1970
2210
2580
2770
2650
3090
3330
M 36
705
825
885
885
1030
1111
1145
1340
1435
2030
2360
2530
2850
3310
3560
3420
3980
4280
M 39
920
1075
1155
1150
1440
1440
1495
1750
1880
2620
3050
3290
3680
4290
4620
4420
5150
5550
NOTE: The values given in this table can be used only in the absence of torque specifications in the procedures included in this manual.
Rev. 01
Rev. 01
xiv
453-SWD-RMM-0103020
MO-15.98.XX.XX/6XX-020

CONFIGURATION
SECTION 1 - GENERAL INFORMATION
1.1
INTRODUCTION
The purpose of this manual is to provide the information required to operate, repair
and maintain the Centralized Control System (SCC) and its systems.
1.2
EQUIPMENT IDENTIFICATION AND LOCATION (Ref. Fig. 1-1 and Table 1-1)
The major assemblies that comprise the SCC are identified by name and general
location in Figure 1-1 and are listed in Table 1-1 to 1-3.
DESCRIPTION
SUPPLIER
SCC Server
Dell Blade Server M1000E
SCC Workstation Processor
Dell
SCC Workstation Monitor

SCC Monitor Sound Bar
Table 1-1. Equipment Identification and Suppliers
1.3
SPECIFICATIONS (Ref. Tables 1-2 and 1-3)

EQUIPMENT DESCRIPTION
SPECIFICATION
SCC Server
TBD
Network Distribution
standard gigabyte ethernet cable category 5

standard gigabyte ethernet optical cable
through Data Transmission System
(STD/DTS)
Table 1-2. General Specifications
SPECIFICATION
DELL BLADE SERVER

Location
air-conditioned room
clean air of airborne contaminant, such as
smoke, dust and ash.
free from radiant interference such as handheld transmitters/receivers, radar, and radio/
television broadcast transmitters
Operating Temperature
TBD
Storage Temperature
TBD
Operating Altitude
TBD
Table 1-3. Equipment Specifications

453-SWD-RMM-0103020
MO-15.98.XX.XX/6XX-020
1-1
Rev. 01
Rev. 01
453-SCC-02-001
Figure 1-1. SCC Operator Equipment Location

Rev. 01
Rev. 01
1-2
453-SWD-RMM-0103020
MO-15.98.XX.XX/6XX-020
SPECIFICATION
Maximum Rate of Temperature Change

During Operation
TBD
Relative Humidity During Operation
TBD
Relative Humidity During Storage
TBD
Heat Dissipation For Each System

(both enclosures)
TBD
Air Cleanliness
TBD
Processors
TBD
TBD
TBD
TBD
TBD
TBD
Memory
TBD
TBD
I/O Subsystem
TBD
Storage Subsystem
TBD
TBD
Scalable Storage Subsystem
TBD
TBD
Embedded I/O
TBD
TBD
TBD
TBD
TBD
Manageability
TBD
TBD
TBD
TBD
PCI Adapters
TBD
TBD
TBD
Serviceability
TBD
Operating System
TBD
Power and Packaging
TBD
TBD
TBD
SCC WORKSTATION EQUIPMENT - DELL COMPUTER

Processor
TBD
Operating System
TBD
Table 1-3. Equipment Specifications (Continued)

453-SWD-RMM-0103020
MO-15.98.XX.XX/6XX-020
1-3
Rev. 01
Rev. 01
SPECIFICATION
Productivity Software
TBD
Security Software
TBD
Video Card
TBD
Mouse and Keyboard
TBD
Speakers
TBD
SCC WORKSTATION EQUIPMENT - DELL LCD MONITOR

Diagonal Viewable Size
TBD
Aspect Ratio
TBD
Panel Type
TBD
Optimal Resolution
TBD
Contrast Ratio
TBD
Response Time
TBD
Viewing Angle
TBD
Colour Support
TBD
Display Type
TBD
Device Type
TBD
Dimensions with stand (D x W x H)
TBD
TBD
Dimensions without stand (D x W x H)
TBD
TBD
Preset Display Area (H X V)
TBD
SCC WORKSTATION EQUIPMENT - DELL MONITOR SOUND BAR

Product Type
TBD
Enclosure Colour
TBD
Speaker Type
TBD
Audio Amplifier
TBD
Connectivity Technology
TBD
Recommended Placing
TBD
Connector Type
TBD
Output
TBD
Headset
TBD
Table 1-3. Equipment Specifications (Continued)
Rev. 01
Rev. 01
1-4
453-SWD-RMM-0103020
MO-15.98.XX.XX/6XX-020

CONFIGURATION
SECTION 2 - DESCRIPTION AND OPERATION
2.1
SYSTEM OVERVIEW (Ref. Figs. 2-1 and 2-2)

The Centralized Control System (SCC) provides data from and control of the traction power substation equipment, guideway equipment, trains, and passenger station
equipment from a central control location. The Communication Network is Ethernet
based, and supports a variety of communication layers (for example Transmission
Control Protocol / Internet Protocol (TCP/IP), User Datagram Protocol (UDP), and
Remote Desktop Protocol (RDP)) and protocols such as Object Linking and Embedding (OLE) for Process Control (OPC), Simple Network Management Protocol
(SNMP), and Modbus as required by the various SCC equipment software modules.
The SCC subsystem is the operator's interface for remotely monitoring and controlling (where applicable) equipment not related to control of the trains. It consists of
equipment throughout the system such as workstations, servers, and Programmable
Logic Controllers (PLCs). The SCC communicates with and gathers information
from most equipment in the overall system. The collected information is transferred
back to the Control Centre and the Control Centre Operator is alerted if required.
The processing of SCC control requests by the corresponding subsystem is not
detailed in this manual, but can be found in the specific subsystem manual.
Figure 2-1 and Figure 2-2 illustrate the general configuration of the system.
SCC system consists of:
A.
one or more field data interface devices, usually PLCs, that interface with field
sensing devices and other hardware units.
B.
a communications system used to transfer data between field data interface

devices and control units and the computers in the SCC central host. System
communication is based on radio, cable, and satellite.
C.
a central host computer server or servers (sometimes referred to as the SCC

Centre, master station, or Master Terminal Unit (MTU)).
D.
a Human Machine Interface (HMI) software system used to provide the SCC
central host and operator terminal application, support the communications
system, and monitor and control remotely located field data interface devices.
The SCC provides centralized computer monitoring and/or control of the following
subsystems:
Auxiliary Equipment Control System (SEA)

Energy Control System (SCE)
Passenger Flow Control System (SFP)
Vehicle On-board Radio System (VORS)
Train Management System (TMS)
On-board Communication System (OCS)
SCE/SEA/SFP Simulator (SIMEA)
453-SWD-RMM-0103020
MO-15.98.XX.XX/6XX-020
2-1
Rev. 01
Rev. 01
Figure 2-1. SCC Subsystem Interfaces

Rev. 01
Rev. 01
2-2
453-SWD-RMM-0103020
MO-15.98.XX.XX/6XX-020
453-SCC-02-013
Modbus
Poller
Tool
870-5-104
Protocol
Driver
VORS
Server
SCC
Internal
Modules
Iconics
SNMP
Server
Other
OPC
Servers
UDR Register
(Bridge Register)
"Iconics simulator OPCDA2" OPC Server
UDM Register
(Alarm Processor)
Iconics
Graph WorX
Screens Including
Alarm Viewer
and
Trend Viewer
TrendWorX64
Logger
Alarm WorX64
Alarm Point
Alarm WorX
Logger
Microsoft Express
SQL Database
Simulator Application
(Play Back Tool)
Long Storage
DDAS
Figure 2-2. SCC Data Flow and Processing (Sheet 1 of 2)

453-SWD-RMM-0103020
MO-15.98.XX.XX/6XX-020
2-3
Rev. 01
Rev. 01
453-SCC-02-015
Legend
CANbus Interface
Component
Components controlled by Bombardier
CANbus Events
Logger
Components controlled by Metro

Components of Bombardier and Metro
shared responsibility
Train
Model and State
CANbus Events /
Alarm Log Files
Alarm Logger
Modbus client /
server
WCF Service
Data communication interfaces
Train Configuration,
Status and Alarms Data
Functionality implementation
components
SCT
TMS
Train
Configuration File
ISB
WCF Service
Data Storage Components
Data Pre-Processing, Filtering,

Compression Component
Serial Interface
WCF Service
Signaling
Configuration, Status
and Alarms Data
Train Configuration,
Train Status and Alarms Data
Signaling
Configuration Data
Serial Interface
Signaling
DDAS
SAS Event Data
SAS Alarm
Data
Interface TBD
SAM
SAS Alarm
Generator
WCF Service
Cache Update
Requests
SAS Event
Data
SIMEA Simulation
Files
SAS Event
Data
WCF Service
Delay,
K-Factor and
Train Service
Data
SAS Event
Data
SAS Formula &
Metric Calculator
SAS User
Interface
SIMEA
Train Alarms Data

/
SCC Train Commands
Infrastructure
Configuration
Data
DDAS Simulation
File Generator
SIMEA Simulation
File Generation
Requests
FTP Client
DDAS Simulation
Files
SAS
Train
Configuration
Data
Infrastructure Status
and Alarms Data
DDAS Event Data
DDAS-to-SAS
Events
Data Converter
SAS Events
Data Cache
Train, Infrastructure,
Signaling and Communication
Configuration Storage
Main Status and Alarms

Data Storage
SAS Event Data /

Delay, K-Factor
and Train Service Data
Maintenance
Data
Interface TBD
Data Generated by SAS
SAS-to-DDAS
Data Converter
WCF Service
WEB Client,
XML Parser
OPC Client
Infrastructure
Configuration
Data
Infrastructure Status and Alarms Data /

SIMEA Simulation Generation Requests
Processed Data
OPC Server
FTP Server
HTML Web
Server
Modbus client /
server
SIMEA
Simulation Player
Local
Data Cache
SCC Workstation
DDAS-to-SIMEA
Simulation File
Converter
USB Port
USB Port
DDAS Simulation Files

on an USB Flash Drive
OPC Client
Infrastructure
Configuration
Storage
Raw Data
Processor
Raw Data
OPC Server
SCC
Infrastructure
Equipment
Interfaces
SCC Commands
(including SIMEA Simulation
Generation Requests)
Figure 2-2. SCC Data Flow and Processing (Sheet 2 of 2)

Rev. 01
Rev. 01
2-4
453-SWD-RMM-0103020
MO-15.98.XX.XX/6XX-020
2.1.1
Diagnostic and Data Acquisition Server (DDAS)

Train Control and Regulation System (SCT)
Personal Digital Assistant (PDA) / Station Attendant
Track Switch (AMV)
Bogie Maintenance Work Station (BMWS)
Car Wash (MLT)
Automatic Fare Collection System (SCAP)
Multimedia System (SMM)
Platform Screen Door System (PSDS)
Access Control System (SCA)
Closed Circuit Television System (CCTV-SME)
Local Control System (SCL)
Power Supply System (SAL)
Automatic Assured Receptivity Unit (AARU)
Elevators and Escalators
Ventilation Pumps
Fixed Control System (SCF).
Architecture (Ref. Fig. 2-3)

The SCC network server uses WebHMI architecture to communicate with the operator workstations without specialized software. This is possible because the SCC
Workstation is a Windows-based computer, and accessing the SCC server is done
using an HTML (Web page) communication protocol. This permits easy replacement of all workstations, and the ability to work from any network connected location. The SCC SQL database system is managed by the ICONICS Genesis 64
software.
The Memory Based OPC [Object Linking and Embedding (OLE) Process Control]
server is located on a two-slice server, the Dell Bade Server (M1000E) in the Control Centre EER. OPC is a standard for connecting and communicating with industrial automation devices and is based on the specification from the OPC Foundation
(OPC.org).
The SCC Server has redundancy that is transparent to the devices interacting with it.
The subsystem interfaces to and from the SCC Server do not need special redundancy consideration because the server redundancy is transparent to the network
devices and processes. This redundancy includes the creation of a virtual IP address
that allows the SCC Server to be addressed using the same IP address regardless
which server slice is primary. Each of the two server slices are identically configured to provide real-time and hot-swapable redundancy of the configuration and
database services. Regardless of connection method, all SCC data from all sources
is managed in the Memory-Based OPC Server. All data collection to and from the
Memory Based OPC Server is done through clients that either read or write data to
it.
The OPC server is responsible for:
A.
managing the SCC configuration,
B.
storing historical data,
453-SWD-RMM-0103020
MO-15.98.XX.XX/6XX-020
2-5
Rev. 01
Rev. 01
Figure 2-3. SCC Server Redundancy

Rev. 01
Rev. 01
2-6
453-SWD-RMM-0103020
MO-15.98.XX.XX/6XX-020
C.
storing trend-logger data,
D.
storing alarm-logger data, and
E.
scheduling of the special purpose software and interfaces to all subsystems.
Some external communication protocols or third party reporting modules exchange

data between the Memory Base OPC Server and the end devices using proprietary
software tools called Software-Development-Kits (SDK), through Modbus, or using
SNMP compatible protocols. Subsystems such as the CCTV and PA require software interfaces that cannot be easily embedded into the Genesis 64 product suite.
The server uses external, vendor provided SDK interface applications for data
exchange between the SCC and the subsystems. All SCC workstation requests for
subsystem data are made to the SCC server. The SCC server then forwards these
requests to the appropriate subsystem servers by transmitting the value of predetermined OPC database tags. In other words, the SCC server monitors these tags for
any change, then connects to the subsystem process interface server to pass-on or
collect the workstations request. Each database tag stores one piece of information
that is monitored and/or controlled using the SCC Graphical User Interface (GUI)
displays. These graphic displays alert the Central Control Operator (CCO) to the
subsystem or location where an alarm or incident has occurred. Control points are
selectable on the GUI display with either a keyboard or mouse. Once a point has
been selected, the command to change state is entered using the keyboard or mouse
and transmitted to a subsystem interface to initiate the control action. For some subsystems, the SCC System is integrated with them through Programmable Logic
Controllers (PLCs) to initiate and control actions.
2.1.2
System Network
The System Network provides communication pathways for all of the subsystems of
the System. The different communication subsystems that use the network are based
on Ethernet and TCP/IP technology standards and interface with the network nodes
and switches using the standard protocols.
The network provides SCC access to some of the systems aboard the trains to communicate with monitored and controlled equipment and communication equipment
such as Public Address and Passenger Information.
To allow these different SCC subsystems to communicate with other subsystems in
an efficient manner, they have been divided into smaller sub-groups or domains
using Vehicle Local Area Networks (VLANs). All of the communication devices in
the system and interface with the network are grouped into one of the VLANs.
2.1.3
SCC Safety
2.1.3.1
Non-Vital Consideration
The SCC subsystem is considered a non-vital system. Even though the design
ensures with high probability the execution of commands or the reporting of status
and alarms, the system relies on transmission of this data which cannot be guaranteed. The possible failure within the transmission of this information makes the SCC
system non-vital. As such, any alarms and alarm conditions that have a safety
impact are monitored in a secondary, vital manner through the device or system.
2.1.3.2
Operation Prevention and Protection

When devices need to be prevented from operating, such as the power supply and
distribution equipment for maintenance, the prevention and protection is not done
through the SCC Subsystem. Prevention and Protection is provided by physical
453-SWD-RMM-0103020
MO-15.98.XX.XX/6XX-020
2-7
Rev. 01
Rev. 01
means directly on the device using lock-out and tag-out or rack-out / tag-out procedures. This removes all potential for safety compromises within the SCC Subsystem.
2.1.3.3
Redundant Architecture (Ref. Fig. 2-3)

Redundant architecture is utilized to minimize the chance of SCC subsystem failure.
The SCC Subsystem Server is a dual slice server, employing lock-step technology to
ensure continuous, uninterrupted operation.
The Data Transmission System (STD) is the backbone of the SCC Subsystem communication. It uses a redundant loop network to overcome single point failures to
maintain service.
The communication between devices uses TCP/IP protocol does not guarantee
transmission, but employs error detection and repeating features to increase the
probability of correct transmission.
2.1.3.4
Command Confirmation
The GUI control pop-ups contain a secondary confirmation step when command
inputs are initiated by the CCO. The operator must first select the desired control
action, then confirm the selection by pressing a confirmation button. This procedure
reduced the risk of any accidental commands being executed by the operator.
NOTES:
2.1.3.5
1.
This feature does not apply to commands issued through the Scheduler and
thus the operator should take care when scheduling any command operations.
2.
It is not practical to implement commands having the Command Confirmation feature for Scheduled commands. This is due to the potential large volume of confirmation pop-ups presented to the CCO as the Scheduler
automatically manages devices. For example, a schedule for the Air Conditioning system using an ambient temperature sensor. The Air Conditioner
starts and stops several times each day, and the operator would need to confirm each of these actions.
User Privileges
WARNING: THE SCC SYSTEM CAN BE OPERATED USING A SIMPLE OPC CLIENT
SUCH AS THE COMMAND LINE OPC SUPPORT APPLICATION WITHOUT USER PRIVILEGES ASSOCIATED WITH THE SCC GUI. THIS FEATURE, HOWEVER, PERMITS THE SCHEDULER TO INTERACT WITH
THE SYSTEM.
The SCC Subsystem controls access to certain SCC functions with user privileges.
The privileges are assigned directly to users or assigned to user groups. The privileges that a user has determines the GUI functionality the user is permitted to access.
A level of safety is achieved by not allowing users to access equipment for which
they have not been trained. For example, a user that was only trained on passenger
information calls can be prevented from operating the Power Supply and Distribution system equipment.
NOTE:
Rev. 01
Rev. 01
Access to the Scheduler for editing commands using the GUI is protected by the
privileges but do not prevent commands that are initiated through the Scheduler.
2-8
453-SWD-RMM-0103020
MO-15.98.XX.XX/6XX-020
2.1.3.6
Network Security
The Data Transmission System (STD) is a contained network that normally has no
access to the outside world. A temporary connection can be established to perform
updates, however.
The Wi-Fi system (Voice and Data Mobile Communications System (SCMVD)),
which extends the STD, uses WPA2 or better encryption to limit access to the STD
using mobile devices.
2.1.3.7
Input Verification
Incorrect Operator Input (intentionally or unintentionally) is the largest source of
input errors. Inputs from the operator therefore have the greatest degree of verification / error-checking. Functions that pass input to other interfaces, such as the PAplay-requests to the PA Interface, require less verification due to previous stage
proofing.
Whenever an input error occurs, the system continues using default values or the
request is dropped and an error is generated. If this is not possible, the state returns
to a state that supports re-processing. For example, if a PA request is made for content that does not exist, the PA Interface returns a warning through an OPC tag,
drops the request, and returns to its normal state to wait for the next request.
2.1.4
Programmable Logic Controllers (PLCs)

All subsystems that are connected directly to the network and are running a TCP/IP
stack require an IP address. The connections between all other subsystems connected to the SCC server are locally hard-wired through network-connected Programmable Logic Controllers.
Programmable Logic Controllers are located in the passenger stations, the traction
power substations, and in the Depot EER. They provide real-time control and monitoring of remotely-located points through a modular, expandable architecture. The
Modicon M340 automated platform processor manages the entire PLC station, comprised of discrete I/O modules, analogue I/O modules, and a communication module. These are distributed across one or more racks connected on a local bus. Each
rack must include a power supply module. The main rack supports the CPU.
2.1.5
Performance
The performance of the SCC is measured by its response time. There is no specific
way to measure response time in the SCC system. The time between initiating the
command and the corresponding status change should not be included in the performance metrics because the device can take an extended period of time to change
state and the status for the state change may change at the end of the state change.
For example, a track switch can take some time to move. If the status for the switch
changes after the move is complete, the performance metrics would incorrectly indicate that the operation took a long time.
The performance metrics used to evaluate the SCC should be:
A.
One-Way Trip Time for a Modbus PLC Status / Alarm
A status or alarm generated on a device hardwired to a PLC and the time before it is
displayed in the SCC Alarm Banner is recorded.
453-SWD-RMM-0103020
MO-15.98.XX.XX/6XX-020
2-9
Rev. 01
Rev. 01
B.
One-Way Trip Time for a Modbus Device Status / Alarm
A status or alarm generated on a Modbus device and the time before it is displayed
in the SCC Alarm Banner is recorded.
C.
One-Way Trip Time for an SNMP Device Status / Alarm
A status or alarm generated on an SNMP device and the time before it is displayed
in the SCC Alarm Banner is recorded.
D.
One-Way Trip Time for an OPC Device Status / Alarm
A status or alarm generated on an OPC device and the time before it is displayed in
the SCC Alarm Banner is recorded.
E.
Command Time for a Modbus PLC Status / Alarm
A command requested to operate a device hardwired to a PLC and the time for the
device to start the request is recorded.
F.
Command Time for a Modbus Device Status / Alarm
A command requested to operate a Modbus device and the time for the device to
start the request is recorded.
G.
Command Time for an OPC Device Status / Alarm
A command requested to operate an OPC device and the time for the device to start
the request is recorded.
H.
Other Performance Metrics
Other performance metrics include the time from the initiation of a communications
interface (such as PA) to the activation of the subsystem. However, such metrics are
not as critical as the above metrics because a slight delay in initiating PA is not as
critical as obtaining data in a timely manner.
2.1.6
Reliability
The reliability features of the design and architecture of the SCC system is discussed
in the following paragraphs.
2.1.6.1
Redundant Server Architecture

A redundant architecture is used to minimize the chance of a SCC failure affecting
operation of the system. The SCC Server is a dual slice server employing VM technology that ensures that operation continues if either slice of the server fails.
Multiple servers with the same virtual state image of the server are continuously
updated. If the primary server fails, the virtual state image is continued by another
virtual server.
The SCC Server has a network card that allows the network card in each server slice
to be grouped together into one virtual network card. This allows either server slice
to communicate on the virtual network card. The SCC Server redundancy is completely transparent to these devices and adds to the reliability because they do not
need additional complex code to support the redundancy functionality.
Rev. 01
Rev. 01
2-10
453-SWD-RMM-0103020
MO-15.98.XX.XX/6XX-020
2.1.6.2
Redundant Network Architecture

The Data Transmission System (STD) is the backbone of the SCC communication
network. The Data Transmission System is a redundant loop network with the ability to overcome single points of failure while maintaining service.
2.1.6.3
Redundant Protocol Architecture

Most of the communication between devices uses TCP/IP technology. TCP/IP does
not guarantee transmission, but has an error detection and retransmission features to
increase the probability of correct transmission.
2.1.6.4
Minimal Workstation Installation

The workstation uses the WebHMI technology to minimize the amount of software
that needs to be installed on the workstation. Minimal software is installed on the
workstation to allow a workstation to be replaced quickly. The GUI does not have
any hardware specific requirements besides the minimum requirements.
2.1.7
Maintainability
The SCC Server modules are designed to use common interfaces such as OPC,
SQL, and TCP/IP to allow the modules to interact without being specifically
dependent on each other.
In most cases, a module can be swapped out and replaced by a similar module as
long as that module uses the same interface. For example, the Poller module can be
replaced with an off-the-shelf Modbus poller module provided by others. Since both
of these modules perform Modbus to OPC conversion they can be swapped without
significant modification. Modules use configuration files to determine many of the
parameters of the module allowing them to be re-configured easily.
SCC Modules are monitored by a Watchdog process that tracks the important
actions of the modules. This Watchdog is purely a monitoring aid, but allows the
user to get a quick summary to see the latest actions of the various modules. This
helps identify and isolate faulty modules.
2.2
ARCHITECTURE OVERVIEW
The SCC software architecture is based on the Windows 7 Microsoft 64-bit Operating System (OS). Other software such as the Iconics Genesis 64, SQL Database,
vendor proprietary SDKs, and communication modules are layered onto the server.
NOTE:
2.3
This document does explain the processing of any SCC requests carried out by
other subsystem servers. For example, this document includes the architecture
and design of the SCC interface to PA but it does not include architecture and
design of how the PA server carries out the SCC request.
SCC SUBSYSTEM CORE COMPONENTS ARCHITECTURE (Ref. Fig. 2-4)

At the core of the SCC is a Memory Based OPC Server for runtime, SQL database,
and historical data. All real-time data, monitoring, or control eventually begins or
ends in the Memory Based OPC Server. This runtime OPC Server is referred to as a
Memory Base because it does not initiate any data collection. All data collection to
and from the Memory Based OPC Server is done through OPC clients connecting to
the Memory Based OPC Server for reading or writing data.
Data in the Memory Based OPC Server is logged through different processes.
Depending on the data type, it is logged to the SQL historical database and retrieved
as a trend, unlike the Memory Based OPC Server for current (latest) data value.
453-SWD-RMM-0103020
MO-15.98.XX.XX/6XX-020
2-11
Rev. 01
Rev. 01
453-SCC-02-012
Figure 2-4. SCC Server Software Architecture

Rev. 01
Rev. 01
2-12
453-SWD-RMM-0103020
MO-15.98.XX.XX/6XX-020
2.4
SCC CORE SUPPORT COMPONENTS ARCHITECTURE (Ref. Fig. 2-4)

The Unified Data Manager (Alarm Process), Alarm Server, Alarm Logger, and
Trend Logger are all support components of the SCC Subsystem Core.
2.4.1
Unified Data Manager

The Unified Data Manager (Alarm Process) does most of the data processing to
determine if signals are in alarm state or not. Most of the equipment data in the
Memory Based OPC Server is packed in 16 bit registers. The Unified Data Manager
(Alarm Process) extracts the individual signals where applicable. This is done to
evaluate the signals against predefined criteria to determine if the signal is in alarm
state or not. The results of this computation are passed on to the actual Alarm Server.
By utilizing the Unified Data Manager (Alarm Process), most of the alarm processing is delegated from the Alarm Server to provide higher performance.
2.4.2
Alarm Server
The Alarm Server adds standard Alarm Server functionality to the signals extracted
from the Memory Based OPC Server. This enables features such as storing the alarm
state, the acknowledged state, and summary functions such as the number of active
or unacknowledged alarms in a group of related signals. The Alarm Server displays
this information in the real-time Alarm Banner in the SCC GUI.
2.4.3
Alarm Logger and Trend Logger

The Alarm Logger and Trend Logger store data from the Alarm Server or the Memory Based OPC Server in the historical SQL database. The Trend Logger, on the
other hand, stores analogue data based on an interval or when it changes from the
last logged value by more than the dead band value.
2.5
SCC DATA COLLECTION ARCHITECTURE (Ref. Fig. 2-4)

The SCC supports four methods of data exchange: OPC, SNMP, Modbus, and Text
File Exchange. The first three methods (OPC, SNMP and Modbus) are illustrated in
the bottom left corner of Figure 2-4.
2.5.1
Modbus Over TCP/IP and Poller Control Devices

There are three different sources of Modbus over TCP/IP protocols and the SCC utilizes two different processes (Poller and Conditional Poller) to read these source
protocols.
2.5.1.1
Source 1
PLCs are hardwired to devices and communicate with the SCC using Modbus over
TCP/IP. The PLCs are Polled by the SCC Modbus Poller; the SCC communicates
with the Poller module and not the actual PLCs. The SCC Poller module is a
straightforward Modbus polling application with support for dual IP address devices
(for example, redundant devices). The Poller module performs any scaling or offset
needed to convert the raw analogue data into final values. The Poller module uses a
static configuration file to determine which registers are read and converts the PLC
data to its corresponding OPC tags on the Memory Based OPC Server.
2.5.1.2
Source 2
The SCC Poller communicates directly with the Modbus over TCP/IP devices actual
end device and not through an intermediate PLC.
453-SWD-RMM-0103020
MO-15.98.XX.XX/6XX-020
2-13
Rev. 01
Rev. 01
2.5.1.3
Source 3
The third type of devices support the Conditional Modbus Poller module, such as
used in the train TMS touchscreens. The Conditional Poller module is the same as
mentioned above but it also reads a set of Change Bit Registers indicating which
groups of data have changed since the last poll. This permits polling of a much
smaller set of data for only the blocks of data that have changed.
Similarly to the Poller module, the Conditional Poller module performs any scaling
or offset needed to convert the raw analogue data into final values. The Conditional
Poller module uses a dynamic configuration file controlled by the change bit registers to indicate which blocks of data to read.
2.5.2
SNMP Data
The baseline OPC uses an SNMP GET command (as opposed to SNMP TRAP command) to obtain SNMP data. Since the SNMP Manager does not provide functionality for scaling raw data, the results of the SNMP Manger are passed through the
Unified Data Manager (Raw Data Bridge) to the memory-based OPC Server.
2.5.3
OPC Data
The GenBroker module is used to facilitate OPC communication between servers on
different machines. This module takes care of the DCOM and other handshaking to
allow the two different servers to communicate using OPC. Since GenBroker only
enables communication, the data is passed through the Unified Data Manager (Raw
Data Bridge) in order to provide scaling and offset functionality before writing to
the Memory Based OPC Server. Currently the VORS server is an OPC device that
communicates with the SCC in this manner.
2.6
SCC GUI VISUALIZATION

The ICONICS Genesis 64 software suite provides the tools to develop the SCC
Server GUI and screen functionality. A Web Server on the SCC Server provides clients (such as the SCC workstations) with system access through ActiveX control for
display of the various SCC configured screens. This is done using the ICONICS
WebHMI interface and Internet Explorer (IE) as the web browser for ActiveX control. This arrangement requires a minimal installation of software so it can easily be
replaced if the hardware fails.
The visualization also includes a CCTV control that is embedded in an IFRAME,
which is not part of the ICONICS suite. IFRAME provides live CCTV visualization
on the workstations and is integrated with the rest of the GUI screens.
Refer to the SCC GUI Operations screens in Set 3 Book 1, SCC Operation (document number MO-15.98.XX.XX/6XX-005) for more information.
2.7
SCC PROCESSOR MODULES

Processor Software Modules provide an external interface between the SCC and
external devices such as the PA Interface, NetCheck, CCTV Alarms, and Read SIP.
The processor software modules provide internal processing such as PowerCalc, PI
Interface, and Sounder modules that are not provided by the ICONICS Genesis 64
system. These Processor Software Modules typically:
Rev. 01
Rev. 01
A.
read data from the memory-based OPC Server and other sources such as TCP/
IP or external files,
B.
processes the read data,

2-14
453-SWD-RMM-0103020
MO-15.98.XX.XX/6XX-020
C.
respond by sending requests to external subsystems, and
D.
processes the internal changes by writing to the memory-based OPC Server,

writing to a file, or sending a TCP/IP message.
NOTE:
2.7.1
For a logic description of the SCC Subsystem Processors, refer to Paragraph 2.12.
Power Calc Module

The Power Calc Module calculates the power status of the power distribution system. It uses the memory-based OPC server and alarm server data from the status of
all of the power supplying devices (De-energized, Energized, Unknown) and the
status of all of the power conducting devices (Open, Closed, Unknown) to determine the power status of each displayed power segment. The results are written back
to the OPC Server for display on the GUI and supplying power status to the ATC
system.
2.7.2
Passenger Information Interface Module

The Passenger Information (PI) Interface Module detects Operator requests by reading changes in the OPC Server tags. It copies the desired message contents from the
PI server message directory, to the shared PI content file in the contents directory. A
corresponding process on the PI system then reads this PI content file to update the
displays with the new content. The PI interface also passes any direct sign control
commands (embedded in the display contents) to the second stage PI interface (PI
Interface SDK) for processing.
2.7.3
Public Address (PA) Interface Module

The PA Interface Module actions the operator PA requests by reading the corresponding changing PA Memory Based OPC Server tags. The PA Interface extracts
playing, priority mode, and content information and then sets the corresponding
Memory Based OPC Server tags to these values. It then executes the PA Interface
SDK with the appropriate content file.
2.7.4
NetCheck
The NetCheck module verifies the status of network devices that do not already
have high-level alarm support. The module supports two types of checking: PING
and RUDE. PING is a computer network administration utility used to test the availability of a host on an Internet Protocol (IP) network and to measure the round-trip
time for messages sent from the originating host to a destination computer. The
PING selection in NetCheck does a standard network PING to determine if the
device is connected to the network. This typically works with most network connected devices, but only determines if the device is connected and if its network
functionality is partially working.
The RUDE selection in NetCheck attempts to make a TCP/IP connection to a server
running on a device and then disconnects it. RUDE stands for Real-time UDP Data
Emitter. This verification provides more accurate information than a PING about the
state of the server by differentiating between a running or not-running network connected device. Results are visible on the NetCheck GUI and are also posted to the
OPC tags. The module uses simple text configuration files to indicate which devices
to check, which type of check to perform, and what OPC tag to use for the reporting.
2.7.5
SME CCTV Alarms Interface Software Module

This module provides bi-directional communication for CCTV-related alarms. It
periodically checks the CCTV server directory for new alarm event updates. When
new updates are available, the module reads the alarm and source and then triggers
453-SWD-RMM-0103020
MO-15.98.XX.XX/6XX-020
2-15
Rev. 01
Rev. 01
the corresponding OPC tag. Most of the CCTV alarms are event type alarms with no
corresponding alarm reset. The CCTV module automatically resets these OPC tags
on subsequent poll passes. For CCTV dual-state alarms (Alarm / Reset or NonAlarm condition) this automatic reset feature does not reset the OPC tag, allowing it
to be reset by the CCTV server directory at the appropriate time. A simple text configuration file determines which events are monitored and their corresponding OPC
tag.
The CCTV module also monitors specified OPC tags relating to Passenger Intercom
and TVM Intrusion. When these OPC tags are set, the module triggers a corresponding CCTV server-directory-macro. These CCTV macros increase the DVR recording frame rate of specified cameras for five minutes, then automatically returns them
to their normal frame rate. A simple text configuration file is used to indicate which
OPC tags correspond with the selected CCTV server directory macros.
2.7.6
Alarm Suspension
This software module is used to suspend alarms for a predetermined or indefinite
time period. This module is typically used to avoid cascading of expected alarms
caused by a high level alarm or event. For example, when removing power from a
train or wayside power distribution system, a large number of nuisance alarms are
generated as devices lose communication with each other. For this reason, the Alarm
Suspension module can be used prior to power shutdown to prevent these expected
alarms from being triggered and overwhelming the Operator.
NOTE:
2.7.7
The Alarm Suspension feature is not used by the base line configuration, but can
be used along with List Of Objectives (LOBJ) functionality (Ref. Para. 2.7.9).
Disabled Passengers
The Disabled Passenger system provides the Control Operator information about all
of the disabled passengers on the transit system and sends automatic notifications to
the station attendants to provide assistance. The entry and exit locations and details
about the disabled passengers is entered in to the system manually by the station
attendants. Notifications regarding the destination is performed automatically, however. This software module consists of a Web interface for the entry of the disabled
passengers information. The station attendants use SCC GUI screens and a notification system managed through the SCC Scheduler (Ref. Para. 2.7.9).
The SCC supports a number of notification systems, some of which require communications equipment and infrastructure not covered in this manual. Supported notification systems include the following:
2.7.8
telephone call (requires SIP based telephone architecture)

radio call (requires radio server)
e-mail (requires SMTP server and mobile devices to provide notification from
idle when an e-mail is received)
PA broadcast
PI broadcast
web page notification (does not wake a mobile device from idle)
alarm notification (on the SCC Workstations).
Sounder Module
The Sounder module provides functionality for the Audible alarms, and sounds the
alarm using a continuous audio loop until the alarm has been acknowledged. Unlike
Rev. 01
Rev. 01
2-16
453-SWD-RMM-0103020
MO-15.98.XX.XX/6XX-020
the other modules running on the SCC Server, the Sounder module runs on the SCC
Workstations. The module executes on start up and links to the name of the selected
alarm audio file. The sounder module re-reads this audio file each time the Play
Request is made, but not during a loop to allow the alarm audible file to be changed
without needing to stop and restart the Sounder module.
Additional ICONICS Genesis 64 scripting, executed on the SCC Workstation, activates the Sounder module whenever an active, unacknowledged audible alarm is
received. Once all of the audible alarms have either been reset, acknowledged, or
muted, the ICONICS scripting executes the Stop Play function.
2.7.9
Scheduler Module and List of Objectives (LOBJ)

The Scheduler Module compares data points against a list of time-based and/or tagbased criteria and executes corresponding external applications called Support
Action (SA) programs. When the scheduler is started, a base list of criteria is loaded
from the text configuration file. The text configuration file entries can be edited
dynamically using an updated OPC Tag, or by placing a text file in the schedulers
update directory. Dynamic update to manipulate the content of the scheduler is supported by both OPC and non-OPC applications.
The List of Objectives (LOBJ) application is operated through the Scheduler Module. The Objectives are created using an SCC GUI screen and saved in a LOBJ file.
An SCC GUI Scheduler screen permits the adding of the LOBJ to the Scheduler,
assuming the operator has sufficient privileges. A copy of the selected LOBJ file is
then placed into the Scheduler update directory, causing the LOBJ items to be added
to the Scheduler.
The Scheduler module supports internal command editing of its own criteria list and
the running of any software application not requiring user input and is executed by
the SCC operating system. This, combined with command line external Support
Action (SA) Programs, allows the Scheduler to perform many useful actions. The
following paragraphs describe the support action programs that have been specifically written for the Scheduler.
NOTE:
2.7.9.1
The scheduler is not limited to these commonly used SA programs.
CommandLineOPC
This program allows setting, and limited reading, of OPC Tags from the command
line such as setting and toggling tags, increasing tag values, and decreasing tag values. Only OPC DA servers are supported. As a testing tool, this module can also list
the local OPC Servers.
An example of this module being used with the scheduler is the performance of
Command Timeouts. Using Command Timeouts, the Scheduler can write OPC Tag
changes into the memory-based OPC Server. When a command is executed, one of
two criteria are added to the scheduler as follows:
A.
An alarm is raised by writing an OPC Tag after the preset time has expired and
both criteria are removed from the scheduler.
B.
Both criteria are removed from the scheduler if the related status for the command changes. This means that if the command does not cause a change in the
device status within a preset amount of time the alarm activates and the criteria
is removed from the scheduler. If the status for the device changes within the
preset amount of time, the alarm criteria is removed before it can be triggered.
453-SWD-RMM-0103020
MO-15.98.XX.XX/6XX-020
2-17
Rev. 01
Rev. 01
2.7.9.2
WriteFile
This SA program provides for the creation and/or appending of text files from a
command line. It can be used to write configuration and/or data files in real time,
and to write update files for the scheduler itself.
For example, the WriteFile module can write train information parameters to files
for the PI Interface and add and remove passengers from the Disabled Passenger
Tracking process.
2.7.9.3
ModbusMsg
This software module provides for command line sending of simple Modbus messages over TCP/IP. It supports sending of a Modbus byte stream that include the
TCP/IP header, the register, and sent value. For example, this module can write OPC
Tag values to the SCC-ATS Gateway PLC for communicating power rail status from
the SCC to the ATS.
2.7.9.4
TCPMsg
The TCPMsg is used to send a simple text message over TCP/IP from the command
line to a listening server on a specified port. The connection is maintained until the
TCPMsg sender receives a response from the connection that the data sent has been
communicated. Once the response is received, the module disconnects and ends
execution. A sample use of this module, with or without the scheduler, is to send
CCTV commands to other workstations.
NOTE:
2.7.10
The TCPMsg is not used when workstations initiate the CCTV pop-up locally,
instead using other methods to communicate directly to the CCTV module. This
only works for a workstation communicating to its own CCTV module.
SCC Housed Modules

There are two SCC housed modules: VORS GUI and the Radio GUI. These GUI
modules run outside of the SCC ICONICS Genesis 64 screen application but provide additional integrated functionality to the screens.
The VORS GUI functions independently of SCC and provides the following:
A.
wayside to train communications,
B.
train to wayside call detection,
C.
initiation of live or pre-recorded public address messages,
D.
initiation of free text or pre-programmed passenger display messages,
E.
reporting of incoming calls to the OPC Server through the OPC data collector,
and
F.
it allows the desired GUI page to be selected using OPC Server Tags, which are
written back to the VORS Wayside server for processing.
NOTE:
The VORS GUI interface is only for operator-initiated public address and passenger display and not for the regular, on-board service messages not implemented
through the SCC.
The Radio GUI provides workstation access to radio functions such as soft radio and
merging radio channels.
Rev. 01
Rev. 01
2-18
453-SWD-RMM-0103020
MO-15.98.XX.XX/6XX-020
NOTE:
2.7.11
The Radio GUI module does not provide any interaction with the SCC except for
providing SNMP alarms, which are collected using the SNMP Manager data collector.
SCE/SEA/SFP Simulator (SIMEA)

The SCE/SEA/SFP Simulator (SIMEA) is identical to the runtime SCC except that
it has no connection to the end devices. The data is resident in the OPC Server rather
than coming from the end devices. The rest of the logic and interactions are the same
as the runtime SCC system, regardless of whether the data in the OPC Server is from
the real end devices or is being played back as a simulation.
Simulation refers to the playing back of data that was artificially created by an
instructor for the purpose of training. The data can also be recorded from the realtime system and then extracted from the DDAS as a text file (Data Playback). Simulation and Data Playback refer to the same information but are created differently.
For the purpose of Playback, three slide-out control panels are provided. They are
normally not visible on the screen but can be viewed by hovering the mouse at the
top, far left, or at the bottom of the screen, and they remain visible until the mouse
moves away from the controls. The three control panels are VCR Controls (top),
SimData (bottom), and Manual Mode (left).
2.7.11.1
VCR Controls
The VCR Controls provide multimedia device type buttons that allow the user to
control the flow of the playback. They include:
A.
Go To Start,
B.
Slow Down,
C.
Stop/Pause,
D.
Play/Resume,
E.
Speed Up, and
F.
Go To End.
Also displayed is the playback time (offset) and playback speed. The time shows the
elapsed time from the beginning of the playback data and always starts at zero and
increases as the playback progresses. The playback speed starts at normal speed (1x)
and can be decreased or increased with the corresponding SLOW DOWN or SPEED
UP buttons.
2.7.11.2
SimData Control
The SimData Control provides:
A.
a way to manually load playback files for playing back data from the real-time
system, extracted from the DDAS,
B.
a display for related data, and
C.
the simulation functionality based on the current VCR control settings.
The SimData Control periodically checks the Windows Registry for new requests
from the VCR Control, processes them, and then clears the corresponding Windows
Registry to support additional VCR Control requests. When an input file is loaded,
the entries are displayed in list form on the SimData Control. If the Play button on
the VCR controls has not been pressed, the operator can scroll through the loaded
453-SWD-RMM-0103020
MO-15.98.XX.XX/6XX-020
2-19
Rev. 01
Rev. 01
data entries. This is used to verify the correct file and confirm the timing of entries
before running the simulation. Once the playback is started, the data list is
LOCKED from scrolling and shows the current entry and both entries before and
after the current entry to be simulated. This allows the operator to easily see past
entries and future data entries.
The playback input file is a text ASCII file with line delimited entries (Date, Time,
Tag, Value).
A.
Date Time
The Date Time entries are separated by a space and indicate the time stamp of the
tag change. For Playback files, this is the time stamp indicating when the event happened. For Simulation files, the actual date and time is not important except as a
measure of time or relative time interval between events. These parameters are separated from the Tag parameter by a comma.
B.
Tag
The Tag entry indicates the OPC Server tag to be modified and is followed by a
comma.
C.
Value
The Value entry indicates the value that is be written to the OPC Server tag.
2.7.11.3
Manual Mode Control

Manual Mode Control is used for simulation rather than real-time data playback
extracted from the DDAS. Manual Mode Control provides a tree-like list of scenarios, responses, and/or individual signals. By double-clicking any of these selections,
the scenario is loaded into the SimData Control for playback. Selection of a scenario
replaces any SimData that is loaded into the SimData control and restarts the simulation process from the beginning.
During a training session, the instructor remotely monitors the students display. The
instructor uses a web browser to connect to the students workstation using a webbased VNC session from an off-the-shelf product called ThinVNC. The instructor
then selects a scenario from the Manual Mode Control list, causing the scenario to
be simulated on the students workstation. The instructor monitors the VNC session
to observe the student response. The instructor can then select more entries from the
Manual Mode Control to simulate the Runtime SCC response to the students
action. If the student chooses a predictable action to a scenario, the prepared
response can be selected from the Manual Mode Control list. If not, the instructor
must manually generate the response by entering the individual signal.
NOTE:
2.7.12
There is no automatic simulation of Runtime SCC devices as part of the Simulation system due to the number of devices that the SCC interfaces with.
DDAS Interface (Reporting and Playback Support)

The interface between the SCC and DDAS is through the OPC Server, the OPC
Alarm Sever, and through HTTP. No separate module is required for this DDAS
interface.
When the DDAS first connects to the SCC it makes a regular HTTP request to a predetermined URL, which returns the SCC configuration file. The configuration file
format is similar to the TMS Data Dictionary (refer to the TMS ICD for details). The
configuration file is a hierarchical list of all locations, subsystems, devices, and their
signals. It indicates the servers where the signals can be found, which signal proper-
Rev. 01
Rev. 01
2-20
453-SWD-RMM-0103020
MO-15.98.XX.XX/6XX-020
ties are stored, and identifies which SCC OPC tags are used internally and do not
need to be stored by the DDAS.
Once the DDAS extracts the SCC configuration file, it implements an OPC client
connection to each of the two OPC servers (Memory Based and Alarm Based). It
then issues an OPC subscription for all of the desired OPC tags (except for the tags
marked for internal use). This allows the DDAS to capture all of the relevant tag
changes for the purpose of data storage.
The DDAS interface can also be used to request a subset of historical data for playback on the SIMEA.
NOTE:
The request for the historical SCC data is made on the real-time SCC system, and
not the SIMEA system, to keep the SIMEA isolated from the real-time system
data. The DDAS monitors a designated OPC tag used for sending requests from
the SCC to the DDAS.
The format of this OPC tag is IP StartStamp EndStamp Filter.

A.
IP
The IP parameter indicates the IP address of the requesting workstation. This is the
IP address that the results will be transferred to using the File Transfer Protocol
(FTP).
B.
StartStamp, EndStamp
StartStamp and EndStamp represent the start and end date and time of the desired
historical data.
C.
Filter
Filter is the desired text pattern of the OPC tags to be included in the query results.
For example, the PSDx filter selects all of the tags that include PSDx in the tag
name and includes the results in the historical file. The resulting historical results
include the state of all filtered points at the beginning of the specified time interval.
To return the state of the point at StartStamp date and time, the DDAS must locate
the last state change before StartStamp. The remaining historical data includes all of
the state changes for the filtered points that occurred up to the EndStamp date and
time.
Once the resulting filter query is compiled, the DDAS sends a text ASCII file to the
SCC Workstation through the FTP server. The DDAS sends the resulting file using
the FTP PUT command to the requesting FTP Server indicated by the IP address
sent in the SCC OPC tag request.
2.8
SCC SUBSYSTEM CORE COMPONENTS LOGIC DESCRIPTION

The data gathered and manipulated by the data collecting software is written to the
OPC Server. The OPC Server holds the data and allows OPC clients to subscribe to
the OPC tags contained on the OPC server.
2.8.1
Inputs
The OPC Server does not perform data collection. The data collectors act as the
OPC Server clients and use the OPC protocol to write data to the OPC Server tags.
In terms of inputs, the OPC Server uses a standard OPC Sever interface that allows:
A.
clients to connect to the OPC Server and make subscription requests, and
B.
clients to connect to the OPC Server and make write requests.
453-SWD-RMM-0103020
MO-15.98.XX.XX/6XX-020
2-21
Rev. 01
Rev. 01
2.8.2
Processing
Subscription requests allow OPC Server clients to be notified when any of their subscribed OPC tags change value. If a write request changes the value of a tag, all clients subscribed to that tag are sent a notification regarding the value change.
A.
Storage
Volatile (memory only)
B.
Format:
Tags:
String - Byte Array, Unlimited
Values: Numeric - Floating Point, 8 Bytes, String - Byte Array, Unlimited
2.8.3
Outputs
The OPC Server provides outputs in the form of data change notifications to subscribed OPC Server clients.
2.9
SCC SUBSYSTEM CORE SUPPORT COMPONENTS LOGIC DESCRIPTION

The Core Support Component Modules (Alarm Server, Alarm Logger, and Trend
Logger) are proprietary ICONICS Genesis 64 software components.
2.9.1
Inputs
The three core support modules take OPC Server tags as inputs using a standard
OPC Server client. In addition, these modules read user configuration from SQL
database tables. Since these components are ICONICS Genesis 64 components, the
SQL database structure and tables are governed by the ICONICS Genesis 64 product suite.
2.9.2
Processing
For tag changes, the core support modules perform the following functions:
2.9.3
A.
The Alarm Server evaluates the tags against user configured alarm criteria,
reads from the core SQL database, and determines if the tags have changed
alarm state. It also keeps track of the acknowledge state of the alarms and similar information, including alarm counts for alarm groups.
B.
The Alarm Logger evaluates tag changes and writes the new tag values to the
SQL database as historical data.
C.
The Trend Logger evaluates tag changes based on user-specified deadband

amounts and reads from the core SQL database. If the changes exceed the
deadband amount, the value is written to the SQL database as historical data.
Outputs
The outputs of Alarm Server modules are Alarm Server OPC tags. In addition to
being used by the other two Logger modules, these Alarm Server tags can be used
by the ICONICS Genesis 64 visualization.
A.
Storage
Volatile (memory only)
B.
Format
Tags:
String - Byte Array, Unlimited
Values: State - Boolean, 1 Bit, and Count - Long, 4 Bytes
Rev. 01
Rev. 01
2-22
453-SWD-RMM-0103020
MO-15.98.XX.XX/6XX-020
The output of the Alarm Logger and Trend Logger modules is written into the core
SQL database.
C.
D.
2.10
Storage
Non-Volatile (SQL database stored on disk)
Format
To SQL: SQL tables and data (via SQL protocol)
SCC SUBSYSTEM DATA COLLECTION LOGIC DESCRIPTION

The following section discusses the logic for the data collectors. Note that multiple
instances of the same data collector can be used to get the same type of protocol data
from different devices. For example, one instance per train of the Conditional Modbus Poller runs to gather data from each train.
2.10.1
Modbus Poller Inputs

The same Modbus Poller data collector module is used to get data from Modbus
PLCs / RTUs and direct Modbus devices.
Each instance of the Modbus Poller data collector (referred to as the Poller) uses
three configuration files as input to the Poller, a connection to the Modbus server
device and a connection to the OPC Server. Typically one instance of the Modbus
Poller is required for each Modbus IP address (excluding backup IP addresses).
There are therefore three configuration files for each Modbus IP address device:
Config.txt, Map.txt, and Poll.txt. Each of these input configuration files are ASCII
text files.
NOTE:
The connections to the Modbus server device and the OPC Server are outlined in
the this section because they are established on start-up and are maintained
unless disconnected. As such they are not part of the processing phase except for
the need to re-establish communication if lost.
Processes that use the Modbus or OPC protocols manage bi-directional data as both
inputs and outputs. However, the inputs discussed here refer to the flow of user data
and not protocol data.
2.10.2
General Operation
2.10.2.1
OPC Server
The Poller uses the OPC Server as both an input and output. When the Poller is
started it subscribes to all the OPC tags listed in its Map.txt configuration file. This
subscription connects the Poller to the OPC Server tags to record all of the corresponding register changes. When the Poller writes to these OPC tags, the OPC
Server sends a data change notification to all of the subscribed clients.
Since the Poller is a subscribed client and it receives notice of the tag changes, it typically ignores the data because it is itself the source of the change. On other occasions, some OPC tags are used to make OPC command requests to the Modbus
server devices. The Poller writes the OPC tag value to the corresponding Modbus
address, which is monitored by the Modbus server device. When triggered, the
Modbus server device executes the corresponding action.
2.10.2.2
Modbus Server Device

The Poller uses the connection to the Modbus server device as both an input and output. In most cases the Poller reads registers from the Modbus server device and
453-SWD-RMM-0103020
MO-15.98.XX.XX/6XX-020
2-23
Rev. 01
Rev. 01
posts them to the corresponding OPC tags. However, in some cases the Poller gets
requests from OPC Server tags and uses the connection to write data to the Modbus
Server device. Although this does not do anything on its own, typically the device
monitors these mutually agreed upon registers and causes the desired corresponding
action to occur if these registers are tripped.
2.10.2.3
Comments
Comments can be inserted into the configuration text file. This is done by inserting
an apostrophe character () as the first character on a new line, then the comment.
The Poller ignores all of the text until the first carriage return (character 13).
2.10.3
Config.Txt for the Modbus Poller

The first configuration file is located in the same directory as the Poller and contains
Config in its name. The complete name of the file is passed to the Poller as a command line parameter. This allows multiple types of configuration files to exist in the
same directory and still allow the selection of the desired configuration file, such as
Poll.Txt, Config.Txt, and Map.Txt type files. For example, for each device, the filen a m i n g - c o n v e n t i o n u s e d b y t he Polle r is ( 127.0.0.1_502_Ma p.txt ) ,
(127.0.0.1_502_Config.txt), and (127.0.0.1_502_Poll.txt).
The configuration file consisting of key/value pairs are specific to the OPC and
Modbus communication protocol between the Modbus server device, the Poller, and
the OPC Server. The format of this configuration file consists of line separated
entries (Unique Key).
The Unique Key is a keyword (no spaces) under which the value is retrieved within
the module. This is followed by a single space and then the value of the unique key.
Lastly this is followed by a carriage return (character 13) which places any additional key/value pairs on the next line. The Poller uses the key/value pairs described
in the following paragraphs.
2.10.3.1
OPC.SERVER opc_server_name
This key/value pair indicates the name of the OPC Server. An example of the value
of the key is ICONICS.SimulatorOPCDA.2.
2.10.3.2
Modbus.Communication.Register modbus_register
This key/value pair indicates the register to which the Poller writes to indicate the IP
address it is currently using for communication. When the Poller establishes communication to the Modbus Server, it writes the last Octet of the IP address into this
register. This register can then be polled by the Poller to get the information back to
the OPC Server. It can also be used by the Modbus Server device to detect faulty
communication lines that the Modbus Server device cannot detect.
2.10.3.3
Modbus.Primary.IP modbus_server_IP_address
This key/value pair indicates the IP address of the Modbus server (PLC or Modbus
device) to be polled.
2.10.3.4
Modbus.Primary.Port modbus_server_port
This key/value pair indicates the port of the Modbus server (PLC or Modbus device)
to be polled. The typical Modbus port is 502 but it is configurable for devices needing a different port number.
Rev. 01
Rev. 01
2-24
453-SWD-RMM-0103020
MO-15.98.XX.XX/6XX-020
2.10.3.5
Modbus.Backup.IP modbus_server_IP_address
This key/value pair indicates the Backup IP address specified redundancy done
through a different IP address. For devices not supporting redundancy, the backup IP
address should be the same as the primary.
2.10.3.6
Modbus.Backup.Port modbus_server_port
This key/value pair indicates the Backup Server Port specified redundancy done
through a different port. For devices not supporting redundancy, the backup port
should be the same as the primary.
2.10.3.7
Modbus.Slave.ID slave_ID
This key/value pair identifies the slave ID to be used in the Modbus protocol. Typically this value is not used in TCP/IP communication since a single IP address
device only implements one Modbus Server, thus not requiring a Slave ID. This ID
is a remnant in Modbus protocol from when the Modbus protocol was used over a
serial connection to multiple Modbus servers. However, occasionally some devices
require this to be a specific value (typically 1 or 255). This key/value pair allows the
value to be set.
2.10.3.8
Modbus.PollRate ms_delay_between_polls
This key/value pair defines the regular polling interval. The regular poll rate, measured in milliseconds, is the time that the Poller waits after all of its queued requests
have been processed. Typically the regular poll rate is set to the desired poll rate.
2.10.3.9
Modbus.FastPollRate ms_delay_between_polls
This key/value pair defines the fast polling interval. The fast poll rate, measured in
milliseconds, is the time that the Poller waits between receiving a Modbus response
and any queued Modbus requests. Typically the fast poll rate is set to an interval that
is very small (for example 5 milliseconds).
2.10.4
Poll.Txt for the Modbus Poller

This second configuration file is also located in the same directory as the Poller and
is used to define the specific polling instructions for the specific Modbus server
device. The file name of this configuration file must be the same as the command
line parameter passed to the Poller except the keywords Map.txt is replaced with
Poll.txt. For example, if the Map file passed to the Poller is
127.0.0.1_502_Map.txt then the corresponding Poll file is be named
127.0.0.1_502_Poll.txt. This configuration file consists of line separated entries
indicating the register range or ranges to read. Comments are inserted into the file by
starting the line with an apostrophe character (). Anything after the character until
the next Carriage Return (character 13) is ignored. Otherwise the format for a line is
R Address Range.
2.10.4.1
R: (Read) Parameter
This is a fixed character indicating a read function. Although R is the only type of
function supported by the Poller, the function indicator is maintained to provide
maximum compatibility with the Conditional Modbus Poller data collector.
2.10.4.2
Address: Parameter
This represents the starting Modbus Address of the register or register-range to be
polled. It is important to note that this is not the starting Modbus Register Address.
453-SWD-RMM-0103020
MO-15.98.XX.XX/6XX-020
2-25
Rev. 01
Rev. 01
The difference being that the Modbus Register Address 40001 corresponds to the
Modbus Address of 0.
2.10.4.3
Range: Parameter
This represents a byte value indicating the number of registers to be read. This value
is limited by the Modbus protocol to 127 because the Modbus protocol expresses the
range using a single byte to indicate the number of bytes to read.
NOTE:
2.10.5
Devices can have their own lower limit on the maximum number of registers that
can be read in a single poll cycle.
Map.Txt for the Modbus Poller

The Map configuration file is located in the same directory as the Poller and must
have the file name of the command line parameter sent to the Poller. This configuration file is used to define the transfer of raw Modbus data into scaled (if applicable)
OPC Server tags. The file defines:
A.
a link between Modbus addresses and OPC Tag,
B.
how the raw data should be interpreted,
C.
offsets and lengths when extracting only a part of a Modbus register,
D.
scaling from raw data to final data, and
E.
the number of decimal points to use and determines if the data is part of a bigger 32 bit data type.
The Data File format consists of line separated parameter entries in the following
format: Addr Tag Type BitOffset:BitLength:RawMin:RawMax:FinalMin:FinalMax:Decimals:RegType.
NOTES:
2.10.5.1
1.
Addr, Tag, and Type are separated by a space but all other parameters after
the Type parameter related to the interpretation and scaling of the raw data
are separated by a colon character (:).
2.
For registers that contain multiple pieces of data, such as two or more analogue values, additional Data Files can be added to the stream. This is done
by placing a comma at the end of each Data File (after RegType) and add the
additional Data Files. This links multiple OPC tags to a single Modbus
Address. The second and subsequent entries start with the Tag parameter
and eliminates the Modbus Address (Addr) parameter. This can be repeated
as many times as necessary to map a single Modbus Address to many tags
but it all must be done on one line, without a Carriage Return (character 13,
Enter key).
Addr Parameter
The Addr is the Modbus Address associated with the indicated OPC Tag (Ref. Para.
2.10.5.2). When this address is polled, the results, after scaling, are written to the
corresponding OPC Tag. It is important to note that this is not the Modbus Register
Address. The Modbus Address of zero corresponds to the Modbus Register Address
40001.
2.10.5.2
Tag Parameter
The Tag is the OPC Server Tag location where the scaled Modbus data is written.
The Tag is written without its OPC Server prefix because this information is read
from the Config.txt configuration file (Ref. Para. 2.10.3).
Rev. 01
Rev. 01
2-26
453-SWD-RMM-0103020
MO-15.98.XX.XX/6XX-020
2.10.5.3
Type Parameter
The Type setting indicates the raw Modbus data value of Signed (S) or Unsigned
(U). This value is used by the Poller to properly interpret the raw data before applying scaling.
2.10.5.4
BitOffset Parameter
The BitOffset setting is used when the raw Modbus data represents multiple pieces
of analogue information. Individual status and alarm signals, such as two state
inputs, are not separated out at this level, but instead are transferred to the OPC
Server as a 16 bit register. Extraction of these registers into individual signals
(pieces of analogue information) is done by the Unified Data Manager (UDM) and
the Alarm Server. However, analogue values are typically used directly at the OPC
Server level and thus need to be extracted using BitOffset. For example, a register
with two analogue values, each stored in 8 bits of a 16 bit register, would have the
first analogue value extracted with a BitOffset set to zero for the start bit, and the
second with a BitOffset set to 8 for the start bit.
NOTE:
2.10.5.5
The BitOffset value is used in conjunction with BitLength to extract the exact bit
range. Typically zero is used for transferring 16 bit registers when the BitLength is
set to 16. This is used, for example, on status and alarm two state data.
BitLength Parameter
The BitLength setting is used when the raw Modbus data includes multiple pieces of
analogue information. The value indicates the number of bits to extract. For example, a register with two analogue values can use 6 bits for the first and 10 bits for the
second. The 16 bit register would have the first analogue value extracted using a
BitLength setting of 6 and the second with a BitLength setting of 10. BitLength is
used in conjunction with BitOffset (Ref. Para. 2.10.5.4) to extract the exact bit
range. A setting of 16 is used for transferring a full 16 bit register. This is used on
status and alarm two state data.
2.10.5.6
RawMin and RawMax Parameter

This setting represents the minimum and maximum values of the raw data. Typically
this is defined by the data range of 0 to 65 535 for a 16 bit unsigned register. However, other values can be used to simplify scaling if the full register range is used.
For example, a device can write only raw values from 0 to 60 000 which represent a
final temperature of -30.000 to +30.000. For this example, the scaling is easier to
write using 0 and 60 000 as the raw values instead of trying to figure out what 0 to
65535 would equate to under the same conditions. Values of 0 and 65535 are used
when transferring status and alarm two state data 16 bit registers. Refer to Paragraph
2.10.5.7.
2.10.5.7
FinalMin and FinalMax Parameter

This setting indicates the minimum and maximum amount of the final values stored
in the OPC Server Tag. A linear offset and scaling algorithm is applied to scale the
actual value from RawMin and RawMax to FinalMin and FinalMax.
NOTE:
RawMin and FinalMin may not represent the minimum input values, as well the
RawMax and FinalMax may not represent the maximum values. These are two
source and destination points to establish the linear offset and scaling. For example, if the RawMin is 0, RawMax is 100, FinalMin is 0 and the FinalMax is 200. A
raw input of 200 (which is beyond RawMax setting) still scales linearly to 400
(which is beyond FinalMax setting). This allows the values to be set to the normal
operational values but still support detection of out-of-range signals.
453-SWD-RMM-0103020
MO-15.98.XX.XX/6XX-020
2-27
Rev. 01
Rev. 01
2.10.5.8
Decimals Parameter
This variable is set to zero or a positive number. It indicates the number of digits
after the decimal point the Poller retains of the values sent to the OPC Server tag.
Values are rounded to the number of decimal places indicated.
NOTE:
2.10.5.9
The Decimals setting represents the number of decimal places that are written to
the OPC Server tag, but do not indicate the number of decimal places displayed on
the screen visualization. Ideally, the two should be synchronized with each other;
however the Poller cannot enforce this rule. Typically, a value of zero is used when
transferring status and alarm two state data using 16 bit registers.
RegType Parameter
The RegType setting (R, +, -) indicates if the 16 bit register holds isolated data or is
part of a larger 32 bit analogue value. The parameter character (R) indicates a Regular 16 bit register, which can include multiple values such as analogues or two-state
data (Ref. Para. 2.10.5.4 and 2.10.5.5). Other settings include a minus character (-)
or a plus character (+) for 32 bit analogue values (two 16 bit registers). The minus () character indicates the lower half of the 32 bit data register and the plus (+) character indicates the upper half of the 32 bit data. Data is written to the OPC Server tag
only after reading both the upper (+) and lower (-) halves of the 32 bit data. The plus
and minus type registers do not support nesting, so both the plus and minus parts of
the register need to be read (and thus written out) before another plus/minus register
can be formed.
NOTE:
2.10.5.10
The plus/minus register type is only used for 32 bit analogue values.
Command Tag Formatting

OPC Command tags are used to store requested commands needed to operate Modbus server devices. OPC command tags are OPC Server tags that are written to by
the ICONICS Genesis 64 visualization, the Scheduler, or any other OPC client.
OPC Command Tags are defined using two OPC Server Tags. Each part of the full
OPC Command Tag uses the same Modbus Address (Addr) in the Map configuration file. The first part holds the Status of the request while the second holds the
Request itself. This duality of tags is necessary to prevent the Poller overwriting a
new request during the inactive phase while reading the Command Request Status
Tag.
For example, the first OPC Command Tag entry in the Map configuration file is
linked to the OPC Command Status Tag. On the next line, the Modbus Address is
repeated and is linked to the OPC Command Request Tag. When the Poller reads the
second Modbus Address, the value is written only to the first entry, the OPC command status tag, preventing the overwrite of the request.
2.10.6
Modbus Poller Processing

The processing of the Poller is divided into two main independent processes (Polling and Requesting) with two common sub-processes (Build and Reconnect).
2.10.6.1
Polling
The Poller stores the contents of the Config.txt, Map.txt, and Poll.txt configuration
files in local collection. A periodic-timer, set to the regular poll rate, causes the
Poller to execute its Polling process. To avoid overlapping polls, the periodic-timer
is disabled until the poll cycle is completed.
The Poller Process runs through the following sequence as follows:
Rev. 01
Rev. 01
2-28
453-SWD-RMM-0103020
MO-15.98.XX.XX/6XX-020
2.10.6.2
(1)
Each poll instruction is read, one at a time.
(2)
Each poll instruction is sent to the Build subprocess (Ref. Para.

2.10.6.3).
(3)
The Poller waits until a response is returned from the Build subprocess.
(4)
The Poller separates the response into its vital components.
(5)
The Poller looks up the Modbus Address within the map collection to
set the OPC tag and scaling parameters.
(6)
The Poller interprets the raw Modbus data for signed or unsigned type
parameters.
(7)
The Poller extracts the raw Modbus data contents using the BitOffset
and BitLength parameters.
(8)
The Poller applies the scaling parameters to map the values to its final
value.
(9)
The Poller writes to the corresponding OPC tag when the register types
are set to Regular.
(10)
The Poller stores double values for later write processing when register
types are set to non-regular.
(11)
The Poller writes the second part of the 32 bit register to the corresponding OPC tag when the value is combined with the previously
stored component.
(12)
Checks for outstanding poll instructions, if found, it sets the periodic

timer to a fast poll and re-enables it. If not found, it sets the periodic
timer to a regular poll and re-enables it.
Requesting
When the Poller receives a data change notification from the OPC Server, it looks up
the corresponding Modbus Address in the Map collection and then looks up the
OPC tag based on the Modbus Address.
If this double look up result matches the initial data change notification tag, then the
Map does not have a double entry for the Modbus Address. Thus, the OPC tag
change is a status change that the Poller then ignores.
If, on the other hand, the double look up results in a different tag then the Map must
have a double entry, which indicates a command OPC tag.
NOTE:
The OPC command status tag is always listed first in the Map.txt file. If the OPC
command request tag changes, then the second look up results in the OPC command status tag, rather than the OPC command request tag.
If the data change notification tag is a command request tag, then the Poller:
A.
reads the tag value,
B.
looks up the Modbus Address in its Map collection, and then
C.
sends a request to the Build sub-process to:
generate a Modbus write command, and
453-SWD-RMM-0103020
MO-15.98.XX.XX/6XX-020
2-29
Rev. 01
Rev. 01
send the Modbus write command to write the value to the corresponding
Modbus Address.
NOTE:
2.10.6.3
Unlike the polling process, there is no scaling performed during the requesting
process.
Build
The Build subprocess function takes poll instructions and builds a corresponding
Modbus byte stream message. The message is then sent to the Modbus server device
using the established Modbus connection. This process is common to both read and
write operations and provides a single location for building Modbus messages.
2.10.6.4
Reconnect
The Reconnect subprocess detects the loss of a connection to the Modbus server
device. This is done by repeatedly alternating the connection settings between the
current settings and the alternate settings (Primary to Backup or Backup to Primary)
and then attempting to re-establish the connection. The Poller favours neither the
Primary nor the Backup connection; whichever setting makes the connection first is
the setting used until disconnected.
NOTE:
2.10.7
The Poller does not swap back to the Primary settings when the Primary connection has been repaired.
Modbus Poller Outputs

There are two main independent processes: Polling and Requesting, each with its
own set of outputs. These processes take inputs and outputs from both the bi-directional Modbus and OPC protocols.
NOTE:
A.
The process discussed below, refer to the flow of user data and not protocol data.
Polling Process
The output of the Polling process writes to the corresponding OPC Server tag or
tags. The value written to the OPC tag is an interpreted, offset, and scaled version of
the raw Modbus input. However, for bit-packed-status and alarm two-state-signals
that are visualization (screen) ready, no additional formatting, offsetting, or scaling
is required to display it correctly. For OPC tags holding bit-packed-status and alarm
two-state-signals that are not visualization ready, they are extracted by the Unified
Data Manager (UDM) Alarm Process and passed to the Alarm Server before they
can be displayed.
The Polling process also has a Poll-request-output to the Modbus server device. This
Modbus protocol message is sent over TCP/IP to the device. The response to these
requests are inputs to the Poller, and are processed by the Poller resulting in Polling
outputs.
B.
Requesting Process
The output of the Requesting process writes to the Modbus server device using
Modbus protocol messages over TCP/IP. There is no interpretation, offset, or scaling applied in this process.
2.10.8
Conditional Modbus Poller

The Conditional Modbus Poller is very much the same module as the Modbus Poller
but instead uses a Conditional polling map for Conditional Polling features. Since
Rev. 01
Rev. 01
2-30
453-SWD-RMM-0103020
MO-15.98.XX.XX/6XX-020
the processing for Conditional Polling is somewhat different than regular Polling,
this data collector module is identified separately.
Conditional Polling is only available for Modbus devices that support this feature,
such as the vehicle TMS. This feature allows a device to poll large data devices
without having to read all the device's data during each poll cycle. Conditional Polling sets aside some registers, called Change Bit Registers, which are set by the Modbus device depending on data changed. Each Change Bit represents a data set or
group. If any data within the group changes, the device sets the corresponding bit
thus informing the poller that the entire group must be read. The poller first reads
these Change Bit Registers and then executes additional polls for all the groups
whose Change Bits are set. The poller is responsible for clearing the Change Bit
Registers before processing additional polls. This ensures that any setting of Change
Bits occurring after reading Change Bits are not accidentally cleared by the poller.
This could happen because of delays between the reading of the Change Bit Registers and clearing them.
For example, 1000 registers of data can be divided into 20 groups of data which can
be represented by the first 20 bits in two Change Bit Registers. Each of the
20 groups would consist of 50 registers of data each. If data changed in only two of
these groups, then the poller would poll three groups, first the Change Bits and then
the two groups of changed data, rather than polling all 20 groups.
To optimize data flow, the group size must be chosen using the following considerations:
2.10.9
A group size that is too small is inefficient. When multiple points change state,
they each trip different groups leading to a high poll request.
A group size that is too big has an increased chance of having at least one point
that has changed, forcing the group to be read more frequently.
Conditional Modbus Poller Inputs

The Conditional Modbus Poller uses the same configuration file inputs as the NonConditional Modbus Poller (Config.txt, Map.txt, and Poll.txt). It also uses the connection to the Modbus Server device and the OPC Server. The format for these configuration files are identical to the Non-Conditional Poller except for the Poll.txt file
making use of the Conditional directives.
2.10.9.1
Poll.Txt for Conditional Modbus Poller

There are two conditional directives that permit the Conditional Polling function to
be implemented. The syntax for the first Poll directive replaces the previous R (read)
directive with C Addr Range.
This directive is identical to the Modbus Poller R (read) parameter (Ref. Para.
2.10.4.1) but also stores the results for the next conditional evaluation by the second
parameter. This storing of results increases the Poller efficiency.
The second directive performs the actual conditional processing. The syntax for this
directive is ? Bit Value Addr Range.
2.10.9.2
C: Parameter
Conditional Parameter in the Poll.txt file always refers to the current non-conditional (C directive) read cycle. The value of the C Directive Read is stored for use by
the second conditional parameter until another non-conditional read directive is
453-SWD-RMM-0103020
MO-15.98.XX.XX/6XX-020
2-31
Rev. 01
Rev. 01
issued (C Addr Range). Then the previous stored values are replaced by the newly
stored values.
2.10.9.3
Bit: Parameter
The Bit parameter indicates which bit of the stored non-conditional read is to be
evaluated. If the non-conditional read consisted of multiple registers then the bit values continues across the registers starting with the lowest significant bit of the first
register. Thus the 3rd bit in the 2nd register would be bit 11.
2.10.9.4
Value: Parameter
For the conditional directive to be true, the Value parameter must indicate if the corresponding bit is Set (1) or Cleared (0).
2.10.9.5
Addr: Parameter
The Addr parameter indicates what starting Modbus address to use if the conditional directive is true.
2.10.9.6
I: Parameter
If the conditional directive is true, the I parameter indicates the number of registers
to read. As such, a typical short example of a conditional poll might look like the following:
R01
W00
? 1 1 1000 10
? 2 1 1050 10
? 3 1 1100 10
The above example reads one Change Bit Register from Register 40001 (Modbus
Address 0). It then clears the Change Bit Register. Lastly it checks the first, second
and third bits to see if they are set. If so, the poller reads 10 registers from the corresponding register ranges (1000, 1050 or 1100).
2.10.10
Conditional Polling Device

To use Conditional Polling, the Modbus Server device must support this protocol
enhancement feature. The Change Bit Registers act like an input to the Poller. They
are set by the device to inform the poller which group of registers to poll.
NOTE:
2.10.11
The convention used to determine which Change Bits represent which group of
register-ranges must be pre-established to allow inputs to be used correctly
between the Modbus Server device and the poller.
Conditional Modbus Poller Processing

The processing for the Conditional Poller is identical to the (Non-Conditional)
Poller (Ref. Para. 2.10.6) except for the extra processing needed to handle Conditional Directives.
When a Non-Conditional read is performed, the values of the registers are stored as
a binary string. The string format is stored from the lowest significant bit of the first
register address to the highest significant bit of the last register address.
Storage:
Rev. 01
Rev. 01
Volatile (Memory Only)

2-32
453-SWD-RMM-0103020
MO-15.98.XX.XX/6XX-020
Format:
String Containing 0s and 1s Representing Change Bits, LSB to MSB
The Bit and Value is extracted when a Conditional Directive is processed in the Poll
instruction. The indicated bit is an offset of the stored binary string so as to determine the corresponding bit value of the last Non-Conditional read, such as the
Change Bit Registers. If the corresponding bit matches the indicated state, such as
the Set State, then the rest of the Conditional Directive is processed like a Non-Conditional read except that the read values are not stored as the new binary strings. For
example, when the poller is performing in regular polling mode, it is processed like
the R directive (Ref. Para. 2.10.4). As such, the same stored Change Bit Register
value can be used in the next Conditional Directives without having to re-read the
Change Bit Registers. If the corresponding bit does not match the indicated state,
then the Conditional Directive is ignored and processing continues to the next Poll
instruction.
2.10.12
Conditional Modbus Poller Outputs

The outputs of the Conditional Poller are the same as the (Non-Conditional) Poller
(Ref. Para. 2.10.7).
2.10.13
SNMP Manager and Unified Data Manager (Raw Data Bridge)

The Simple Network Management Protocol (SNMP) Manager is used to collect
SNMP data using the SNMP (Get) protocol. It is primarily used to capture hardware
diagnostic data, however other software applications also make use of this protocol.
The ICONICS Genesis 64 product suite supports both SNMP (Get) and SNMP
(Traps) protocols The uses of the SNMP (Get) protocol supplements visualization
features not available through SNMP (Traps).
Since the SNMP Manager is part of the Genesis 64 Product Suite, its general
description of process operation will be limited to explaining its inputs and outputs.
2.10.13.1
Inputs
Using the SNMP (Get) protocol, the SNMP Manager connects to external devices
by using previously configured SQL database information. The configuration of the
SQL database is done using the Genesis 64 product suite GUI or by importing an
XML file using the Genesis 64 GUI. The steps of pre-configuring SNMP information can be found in the Genesis 64 documentation.
As defined in the pre-configured data of the SQL database, the inputs to the Unified
Data Manager (UDM) (Raw Data Bridge) are OPC Server tags. A pre-configured
scaling expression defines the translation of the input tags (SNMP OPC Server
tags), and specifying scaling parameters, and output tags (Memory Based OPC
Server tags). For more details on how to configure UDM Registers and UDM
Expressions refer to the Genesis 64 documentation.
2.10.13.2
Processing
In simple terms the SNMP Manager connects to the end devices based on the provided SQL database configuration and makes these results available as an OPC
server. The details associated with the processing are part of the Genesis 64 product
suite, and are beyond the scope of this manual.
NOTE:
The SNMP OPC Server is not the same as the Memory Based OPC Server to which
all other data is pushed. To unify all data into the Memory Based OPC Server, the
Genesis 64 Unified Data Manager takes data from the SNMP OPC Server and
transfers it to the Memory Based OPC Server. During this transfer, referred to as a
453-SWD-RMM-0103020
MO-15.98.XX.XX/6XX-020
2-33
Rev. 01
Rev. 01
Data Bridge, the value is scaled (as required) by an amount indicated in the preconfigured SQL database, this scaling is not supported by the SNMP Manager.
The processing supports version 1 (V1) and version 2 (V2) of the SNMP (Get) protocol. Version 3 (V3) is not yet supported but is planned for version (10.8) of Genesis 64.
2.10.13.3
Outputs
The outputs of the SNMP Manager consists of tags on an SNMP OPC Server.
The outputs of the UDM (Raw Data Bridge) consists of tags on the Memory based
OPC Server.
2.10.14
Gen Broker and Unified Data Manager (Raw Data Bridge)

Gen Broker is a data collection module which provides the Genesis 64 visualization
with a transparent connection to other machine OPC servers, handles additional
communication settings, and allows the system to accept OPC tags from other OPC
servers. Typically the OPC protocol, when not used on the same device as the OPC
server, requires additional configuration settings (DCOM) to allow it to work
between different computers.
2.10.14.1
Inputs
Gen Broker uses pre-configured SQL database settings to make connections to other
OPC Servers. These other OPC Servers act as inputs to Gen Broker. Since Gen Broker is a Genesis 64 product suite module, the configuration of Gen Broker is beyond
the scope of this document. Refer to the Genesis 64 documentation for details.
2.10.14.2
Processing
The Gen Broker data collection module is not a data collection module by itself.
Gen Broker only facilitates a transparent connection to other OPC Servers, not
hosted on the same machine. As such, Gen Broker only makes data accessible to the
Genesis 64 product suite but does not actually transfer any data from these servers to
local storage; such as the Memory Based OPC Server. However, just like the SNMP
Manager data, the UDM (Raw Data Bridge) transfers the data from the source OPC
Server to the common Memory Based OPC Server. During this process, as with the
SNMP Manager data, the data can be optionally scaled based on pre-configured
scaling values in the SQL database. As with the SNMP Manager, the process of configuring UDM Registers and Expressions is beyond the scope of this document.
2.10.14.3
Outputs
The outputs of the Gen Broker module are transparent connections to non-local
OPC Servers.
The outputs of the UDM (Raw Data Bridge) consists of tags on the Memory based
OPC Server.
2.11
SCC VISUALIZATION LOGIC DESCRIPTION

The SCC Visualization Screens are configured using the ICONICS Genesis 64 product suite. This product suite provides visual aspects of the GUI through 3 main modules:
Rev. 01
Rev. 01
GraphWorx
AlarmWorx
TrendWorx
2-34
453-SWD-RMM-0103020
MO-15.98.XX.XX/6XX-020
Viewing of the configured screens can be done using the Genesis 64 Runtime or
using a Web Browser.
The Web Browser method is implemented to minimize the amount of software
needed on the client machines. As such, only the Web Browser method will be discussed below. For visualization using the Genesis 64 Runtime, consult the Genesis
64 documentation.
2.11.1
Inputs
The SCC Visualization uses pre-configured ICONICS Genesis 64 GDFX files
which hold information about the graphical elements to be viewed. These include
dynamic views based on data, including user input information and various support
scripts. The creation and contents of these files are beyond the scope of this document. Refer to the Genesis 64 documentation for more details.
In addition to these pre-configured input files, the SCC Visualization can receive
inputs from OPC Servers, such as the Memory Based OPC Server and the SQL
Database for historical data.
2.11.2
Processing
The SCC Visuals use Genesis 64 ActiveX control served by Microsoft's IIS Web
Server. The clients connect to the IIS Web Server using standard HTML protocol
and retrieve the screen views through a WEB page containing ActiveX control. The
ActiveX control translates the pre-configured GraphWorx, AlarmWorx and TrendWorx configuration files into their corresponding visual appearance and provides
user input back to the server.
Since the ActiveX Control is part of the Genesis 64 product suite, the details of the
processing is unknown.
NOTE:
2.11.3
Due to the use of ActiveX technology, currently only Internet Explorer can be used
to visualize the Genesis 64 screens. Similarly, because the ActiveX control makes
use of the full OS functionality, the ActiveX control does not operate with mobile
devices. The Genesis 64 does however provide a MobileHMI version of the
ActiveX control, which provides limited access to some of Genesis 64 functionality.
Outputs
The output of the SCC Visualization to the Operators is an HTML WEB page containing embedded ActiveX control. The output of the ActiveX control is a graphical
representation of the desired screen with user input feedback to the system.
2.12
SCC SUBSYSTEM PROCESSORS LOGIC DESCRIPTION

The following paragraphs detail the Logic of the SCC Subsystem Processors which
function outside of the SCC Visualization for improved process efficiency.
For example, the Power Calc module interfaces with a large number of OPC Server
input tags, whereas a number of corresponding process points would require configuration for implementation within the SCC Visualization. If the power grid is modified, the Power Calc module can easily be edited to add or remove tags whereas
implementing the solution within the SCC Visualization would require configuration changes to add or remove process points.
NOTE:
For a general description of all the SCC Subsystem Processors (Ref. Para. 2.7).
453-SWD-RMM-0103020
MO-15.98.XX.XX/6XX-020
2-35
Rev. 01
Rev. 01
2.12.1
Power Calc Module

The Power Calc Module is used to calculate the state of each power segment of the
Single Line Power Diagram screens. The Power Calc Module takes two pre-configured configuration files as input: Config.Txt and Map.Txt.
2.12.1.1
Config.Txt: Inputs
The Config.Txt file is an ASCII text file which uses the same structure as defined in
the Modbus Poller sub-section of the SCC Subsystem Processors (Ref. Para.
2.10.3). The key/value pairs used by the Power Calc Module are:
2.12.1.2
OPC.Server opc_server_name: Identifies the name of the Memory Based

OPC Server where opc_server_name is replaced with the name of the OPC
server such as ICONICS.SimulatorOPCDA.2.
OPC.Alarm.Server op_alarm_server_name: Identifies the name of the
Alarm OPC Server where opc_alarm_server_name is replaced with the name
of the OPC alarm server such as ICONICS.AlarmServer.2.
Map.Txt: Map Input Coding

The Map file is located in a Maps sub-directory. It can have any name but should
end in .txt indicating that the file is a text based configuration file.
NOTE:
The Map.txt file has nothing to do with the Modbus Poller Map.txt file format.
There are two parts to the Map configuration file: the map and links.
The map is a grid of rows and columns that represents the layout of the power system and must appear first before the links. Each row is represented by a line which
contains all the column entries for that row. Each column is represented by a 5 digit
code followed by a space. For example, the code shown below represents a small
system that has been fit into 5 rows, each with 9 columns. Each physical device
related to power is represented on the map, including additional virtual devices such
as segments and virtual feeders.
..... ..... ..... ..... ..... ..... ..... ..... .....
..... 11111 11111 11111 W0001 11111 11111 11111 .....
..... S0001 ..... ..... ..... ..... ..... S0002 .....
..... 11111 B0001 11111 F0001 11111 B0002 11111 .....
..... ..... ..... ..... ..... ..... ..... ..... .....
A.
11111
The 11111 syntax is used to connect neighbouring map cells. Map cells can only be
connected to cells above, below, right and/or left but never diagonally.
B.
..... , 00000, or XXXXX
The ..... , or 00000, or XXXXX syntaxes are used to isolate neighbouring map cells.
There is no difference between the three listed options but they can be used to make
the map a little more legible. For example, the dot ..... notation can be used for nonconductive parts of the map whereas the XXXXX notation can be used to highlight
intentionally disconnected, or isolated parts of the map.
Rev. 01
Rev. 01
2-36
453-SWD-RMM-0103020
MO-15.98.XX.XX/6XX-020
C.
Fnnnn
Devices that provide power into the system, regardless of what the device actually
is, are referred to as Feeders and are indicated on the map using the Fnnnn syntax.
The letter F is a constant and refers to a Feeder type device and nnnn is a unique
feeder identification number. Typically nnnn is sequentially increasing; such as
counting the number of feeder devices.
D.
Bnnnn, Wnnnn
Devices that allow or disallow power to flow, regardless of what the device actually
is, are referred to as Breakers or Switches and are indicated in the map using the
Bnnnn or Wnnnn syntaxes. The letter B or W is a constant and refers to a Breaker
or Switch type device and nnnn is a unique breaker or switch identification number.
There is no difference between Breakers and Switches except that they can be used
to make the map more legible.
E.
Snnnn
Segments are sections of the map that do not represent a physical device, but are
used to take power state readings. Segments are represented on the map using the
Snnnn syntax. The letter S is a constant and refers to a Segment and nnnn is a
unique segment identification number.
F.
Vnnnn
Virtual Feeders represent the concept of one way power flow. A Virtual Feeder,
unlike an actual Feeder device, takes the power state of a section and provides it to a
different section on the system. Since this is a one direction process, from the segment to the virtual feeder, it is used to implement one way power flow. The Virtual
Feeders are represented on the map using the Vnnnn syntax. The letter V is a constant and refers to a Virtual Feeder type device and nnnn is a unique virtual feeder
identification number.
G.
Example
The following small example shows a sample implementation of a Virtual Feeder.

..... ..... ..... ..... ..... ..... ..... ..... .....
..... F0001 11111 S0002 00000 V0001 11111 F0002 .....
..... ..... S0001 ..... ..... ..... S0003 ..... .....
..... ..... ..... ..... ..... ..... ..... ..... .....
This example, shown above, could be a circuit for a backup generator which only
powers critical equipment. In this example, the feeder device F0001 would be the
main feed device normally providing power to both S0001 and S0003 through the
S0002/V0001 virtual feeder and F0002 would be the backup generator which would
normally be off. When F0001 fails, the backup generator F0002 would be turned on
which would then provide power to S0003 (the critical devices) but not to S0001
(the non-critical devices) because of the S0002/V0001 isolation.
2.12.1.3
Map.Txt: Link Input Coding

The second part of the map file is used to link the codes, listed above, to corresponding OPC tags.
453-SWD-RMM-0103020
MO-15.98.XX.XX/6XX-020
2-37
Rev. 01
Rev. 01
NOTE:
2.12.1.4
The format for each code is different than listed above. The conductive (11111)
and non-conductive (....., 00000, or XXXXX) segments do not have corresponding
entries in this second part of the map.
Feeder_Code<Memory_Based_OPC_Tag: Is the format for Feeder type

devices. Where the Feeder_Code is the 5 digit Fnnnn code, used above, and
the Memory_Based_OPC_Tag is replaced with the OPC tag that provides the
power state of the feeder type device. The value of the corresponding tag is a
tri-state value 0 = De-energized, 1 = Energized, and 2+ = Unknown. Devices
that do not support tri-state can still be used since these devices generate 0 or 1
which corresponds to the de-energized/energized states. The < character is a
constant and is used as a reminder that these are inputs from the OPC server to
the map.
Breaker_Code<Alarm_Server_State_OPC_Tag,
A l a r m _ S e r v e r _ A l a r m _ O P C _ Ta g ,
Switch_Code<Alarm_Server_State_OPC_Tag,
and Alarm_Server_Alarm_OPC_Tag: Is the format for Breaker or Switch
type devices. Where Breaker_Code or Switch_Code is the 5 digit Bnnnn or
Wnnnn code, used above. The OPC tags indicate the state of the device 0 =
Open, 1 = Closed. The alarm state of the device is indicated by 0 = Normal, and
1 = Alarm. Unlike the Memory Based OPC Server tags used with Feeders,
these tags come from the Alarm OPC Server and thus can only provide two
states (hence the need for two tags). The < character is a constant and is used to
remind the user that these are inputs from the OPC server to the map.
Segment_Code>Memory_Based_OPC_Tag: Is the format used for Segments. Where Segment_Code is the 5 digit Snnnn code, used above. The
Memory_Based_OPC_Tag is replaced with the OPC tag for writing the map
tri-state power state. The value of the corresponding tag is the tri-state value 0
= De-energized, 1 = Energized, and 2+ = Unknown. The < character is a constant and is used as a reminder that these are inputs from the Map to the OPC
server.
Virtual_Feeder_Code<Memory_Based_OPC_Tag: Is the format for Virtual
Feeder type devices. The format is the same as used for real Feeder type
devices except for the 5 digit Vnnnn code. The input tag associated with a Virtual Feeder is the same as the output tag written by the corresponding Segment.
In the Virtual Feeder example provided earlier, the same tag would be associated with S0001 as with V0001.
Processing
The Power Calc Module first draws the initial state of the basic map according to the
top section of the map file (Ref. Para. 2.12.1.2). This initial map is drawn with all
feeders de-energized and all breakers and switches closed (conductive). This initial
state map is drawn to indicate conductive devices and sections in one colour and all
non-conductive areas in a different colour.
Although the Power Calc Map uses multiple colours to differentiate the different
device types, the power flow determination uses 3 basic colours: one for non-conductive sections, another colour for conductive none-energized sections and a third
colour for conductive energized sections.
After rendering the initial map, the Power Calc module waits for OPC change notifications from its input tags. When a power related device changes state, the power
Rev. 01
Rev. 01
2-38
453-SWD-RMM-0103020
MO-15.98.XX.XX/6XX-020
state is then propagated to other parts of the map. As a result, the Power Calc Module recalculates the power of the map using the following steps:
(1)
Each Breaker and Switch is set to either the conductive, non-conductive or unknown state colour on the initial map rendering.
(2)
Each energized-Feeder is rendered using the Windows FloodFill function with the energized colour. This causes the energized colour to flow
until it reaches either a non-conductive colour or an unknown state colour.
NOTE:
2.12.1.5
The above steps depict which segments will have power but cannot determine if
an unknown power state exists. As a result, the following additional steps are
performed:
(3)
Each unknown-state-Feeder is rendered using the Windows FloodFill

function with the unknown-state-colour. This causes the unknownstate- colour to flow, down stream, until it reaches either a non-conductive, an unknown, or an energized state colour. Devices that are in an
unknown state but have confirmed power applied will block FloodFill
propagation of the unknown colour towards the powered section and
permit it down stream. In other words, an energized colour section
stops unknown colour propagation since a section adjoined by energized power and unknown power is itself powered.
(4)
Each Breaker and Switch having an unknown state and is neighboured

by energized colour reacts like an unknown Feeder. It is rendered using
the Windows FloodFill function with the unknown state colour. This
simulates energized power entering a device that is perhaps defective
thus in an unknown state, unsure if power is conducting or not.
(5)
Lastly, the value of all Segments are written back to the corresponding
tags listed in the second part of the map file. For Virtual Feeders, this
write may cause the Virtual Feeder state to change. Therefore, to
update portions of the system supplied by the Virtual Feeder, the above
process is triggered again. Multiple passes may be needed to resolve
the entire map if the map has chained Virtual Feeders.
Outputs
The output of the Power Calc Module is written to the Memory Based OPC Server
each time a segment changes state. The Power Calc Module updates all segment
tags, but the OPC Server only process OPC tag changes.
These tags are then used by:
2.12.1.6
the Visualization for display on the screen, to provide the power state information to the operator,
the Scheduler module,
the Poller module, and
the ATC process.
Diagnostics (Ref. Fig. 2-5)

The Power Calc Module runs on the server as a stand alone application requiring no
user interaction. However, for troubleshooting purposes the module supports two
levels of diagnostics: GUI and Log.txt.
453-SWD-RMM-0103020
MO-15.98.XX.XX/6XX-020
2-39
Rev. 01
Rev. 01
453-SCC-02-016
Figure 2-5. Power Calc Diagnostic GUI

Rev. 01
Rev. 01
2-40
453-SWD-RMM-0103020
MO-15.98.XX.XX/6XX-020
NOTE:
A.
To start the PowerCalc Module in application mode, first ensure that the service
version of the PowerCalc Module has been stopped by examining the Windows
Services screen. Failure to do so can cause unpredictable results since two versions of the module will try to process the data. Once the service version of the
PowerCalc Module is stopped, the application version can be started by running
PowerCalc with the -dialogue command line parameter. To revert back to the service version, ensure that the application version has been stopped and then restart the PowerCalc service from the Windows Services screen.
GUI
To determine the state of the Power Calc Module, a Graphic User Interface (GUI)
can be viewed to monitor or diagnose the operating state.
The left hand side shows a graphical representation of the power map showing the
latest calculated power state (Ref. Fig. 2-5). When inputs to the Power Calc Module
change, the map is reset to its initial state map then the power is propagated as per
the processing section (Ref. Para. 2.12.1.4).
The top right hand side of the screen displays a zoomed-in view of the current
mouse location of the left hand side map. Similar to a tool tip, the zoom view is generated only when the mouse stops and hovers over a map section. The zoom functionality is especially useful on large maps.
The map legend describes each map cell, row, and column combination which
relates to a corresponding entry on the visual map, as follows:
Feeders - Orange border

Breakers and Switches - Blue border
Sensor Segments - Yellow border
Segments - Black borders
The centre of each cell depicts the power state, as follows
Green - de-energized
Red - energized
Grey - unknown power state
Below the legend is the Process OPC Tag Data Change Events check box. When
checked, it indicates that OPC tag changes will be processed.
NOTE:
This check box initializes in the unchecked position during the Power Calc Module
start-up, then is automatically set to checked state. This provides a necessary
delay to prevent the Power Calc Module from executing many times and producing nonsense results due to device states not being available. For this reason, during start-up, as the Power Calc Module subscribes to all its input OPC tags, the
Power Calc Modules starts with Tag Processing turned off. After a short delay, the
OPC tag processing is turned back ON so that the Power Calc Module can function
as intended.
Below this area is the name of the current map. This is used to diagnose if the correct
map is loaded.
At the bottom of the GUI are two LED indicators representing the connection status
of the Memory Based OPC Server and the Alarm Server. Beside each LED is the
Last OPC Error to occur, if any.
Red - cannot connect to the OPC Servers.
453-SWD-RMM-0103020
MO-15.98.XX.XX/6XX-020
2-41
Rev. 01
Rev. 01
NOTE:
Ensure that the OPC Servers are correctly identified in the Config.Txt file, (Ref.
Para. 2.12.1.1).
Green - successful connection to the OPC Servers has been made.
The bottom part of the GUI lists the last transactions processed by the Power Calc
Module.
B.
Log.Txt:
The Power Calc Module supplies processing logic data to the Log.Txt file. If a
Log.txt file is present in the same directory as the Power Calc Module, then processing logic data has been written to this file. To activate or deactivate logging, the file
can be created or removed while the Power Calc Module is running.
NOTE:
The amount of data can be increased by running the Power Calc Module in VERBOSE mode. This is done by starting the Power Calc Module with the command
line parameter VERBOSE. Unlike the activation and deactivation of the log file,
VERBOSE can only be activated or deactivated by stopping the Power Calc Module.
WARNING: LOGGING DATA CAN ADVERSLY AFFECT PERFORMANCE OF THE

POWER CALC MODULE IF THE LOG FILE IS ALLOWED TO GET LARGE.
THE POWER CALC MODULE DOES NOT PERFORM ANY LOG FILE
CLEANUP OR LIMITING. LEAVING LOGGING ON CAN EVENTUALLY
LEAD TO A HUGE LOG.TXT FILE OCCUPYING ALL THE AVAILABLE
DISK SPACE ON THE COMPUTER AND RESULTING IN A SYSTEM
CRASH.
2.12.2
PI Interface, SDK, and Server Module

The PI Interface consist of two modules: the first stage PI Interface and the second
stage PI Interface SDK. The PI Interface Module changes the message content on
the IIS Windows Web Server for the Passenger Information displays located
throughout the system, but does not allow the parameters of the sign to be changed
such as brightness. The technology is based on HTML Javascript and HTTP
Request enabled web pages that make content queries to a PHP enabled web server,
such as Microsoft's IIS Web Server.
The second stage module, PI Interface SDK, is used to communicate directly to the
sign for the purpose of display control and obtaining display diagnostics. It uses a
vendor LAN protocol to manipulate (read and/or write) the properties of the display
but does not change the message content.
2.12.2.1
Config.Txt: Inputs
The PI Interface Module takes a pre-configured ASCII configuration file Config.txt
as input. This file has the exact same format as the Config.txt file described in the
Modbus Poller section (Ref. Para. 2.10.3). The key/value pairs used by the PI Interface Module are as follows:
Rev. 01
Rev. 01
OPC.Server opc_server_name: Specifies the name of the Memory Based

OPC Server.
OPC.Confirmation.Tag opc_tag: Indicates the OPC tag used to send back all
processing confirmations and/or errors.
ICS.SERVER.PI.Dir.Messages path_dir: Indicates the non-network directory where the messages are stored. For example C:\inetpub\wwwroot\Modules\PI\Msg, not network reference \\ICS_Server1\Moduels\PI\Msg.
2-42
453-SWD-RMM-0103020
MO-15.98.XX.XX/6XX-020
ICS.SERVER.PI.Dir.Content path_dir: Indicates the non-network directory

where the clients find the content files.
ICS.SERVER.PI.Dir.Formats path_dir: Indicates the non-network directory where the variable formats are stored.
OPC.PI.Command.Tag.nn opc_tag: This is a key/value pair indicating all
the monitored OPC tags for the PI Interface Module requests. The value nn is a
two digit number representing the OPC command tag used. The numbering
starts at 01 and increases by 1 for each unique OPC tag. Multiple OPC tags can
be specified for multiple workstations. This enables simultaneous requests to
the PI Interface Module without overwriting each other's request.
OPC.PI.Mode.Tag.location
opc_tag,
OPC.PI.Content.Tag.location
opc_tag, OPC.PI.Holding.Tag.location opc_tag: These sets of key/value
pairs, one for each zone, determine which OPC tag holds the zone's priority
mode, includes a brief description of its contents, and the current message
hold time. In each set of tags, location is replaced with a PI zone using the Snnx syntax. Where nn is the two digit station number ranging from 0 to 17 and x
designates the zone, P for Platform or C for Concourse.
OPC.PI.Coms.Error.Tag.location opc_tag, OPC.PI.Faults.Erro.Tag.location opc_tag, PI.Heartbeat.Max.Drift nnn: These set of key/value pairs, one
for each zone, are use to determine the alarm tags used to provide the zone
health status back to the OPC Server. The first key/value pair indicates the tag
used to report update errors. If the last display update exceeds the time indicated in the PI.Heartbeat.Max.Drift key/value pair (in seconds) then the tag's
value is set. If the last update occurs within the PI/Heartbeat.Max.Drift timeout
then the corresponding tag is cleared. The second key/value pair is set the
value of the PI diagnostic result. A value of 0 indicates that the display is ON
and has no errors. A value other than 0 indicates the combined total of all set
alarm bits. Refer to the NEC display documentation for details on these error
codes. These bits are as follows:
Bit 1: Display Not On
Bit 2: NEC Error x70
Bit 11: NEC Error xA0
Bit 14: NEC Error xB0
Bit 15: NEC Error xC0
453-SWD-RMM-0103020
MO-15.98.XX.XX/6XX-020
2-43
Rev. 01
Rev. 01
2.12.2.2
PI_Commands.txt: Inputs
The PI Interface SDK module uses the PI_Command.txt ASCII file as an input. This
file is mapped between the embedded display control command directive names and
their corresponding byte streams. The format of this file is a line delimited list of
directives using the following syntax:
Directive: Space_Seperated_Hex_Bytes
The Directive parameter is a text name used to refer to the embedded control command. This is the text that is used in the content file (with the //# key characters) to
instruct the PI Interface SDK module to carry out the corresponding command on
the displays.
The Space_Seperated_Hex_Bytes parameter is a list of bytes, represented as a 2
digit hex number, and separated from each other by a space. These bytes are the
actual bytes that are sent, over a LAN connection, to the display. This byte list
should always end with character 13 (Carriage Return) which is represented using
the hex byte notation as 0D.
As sample entry in this file may look like:
Get Diagnostics: 01 30 2A 30 41 30 34 02 42 31 03 1D 0D
This file acts as a look up table so that embedded display commands can use more
text based instructions as opposed to obfuscated byte streams.
2.12.2.3
OPC Server: Inputs

Request inputs to the PI Interface Module, use specified OPC command tags that are
pre-configured in the Config.txt file (Ref. Para. 2.12.2.1). These tags, must comply
with a rigid entry format to prevent being rejected. The format of the tag syntax is:
!Mode Content Hold Locations
!: Is a constant, indicating an active request.

Mode: Is a number indicating the priority mode of the sent message. It determines what is done if there is a, currently holding, message playing at the
desired destination(s).
Content: Is the name of the PI message to be played.
NOTE:
A corresponding message needs to exist in the messages folder on the PI Server

(Ref. Para. 2.12.2.4).
Hold: Is the time in milliseconds a message is considered to be playing. This

value sets the duration preventing a lower priority messages from replace it.
Locations: Is a list of locations, each separated by a space. It uses the same
Snn-x syntax in the Config.Txt file, (Ref. Para. 2.12.2.1).
A sample request might look like: !9 Arrival 5000 S01-P S01-C.

2.12.2.4
Message Files: Inputs

All messages requested through the PI Interface Module are available through the
pre-defined message list. Free Text or User Defined messages are processed by the
GUI creating a temporary predefined message.
To display the appropriate PI text message, it is necessary to pre-define the entries in
the Messages and Content directory and list within the Config.txt file. The Message
directory contains a list of all possible pre-defined messages whereas the Content
Rev. 01
Rev. 01
2-44
453-SWD-RMM-0103020
MO-15.98.XX.XX/6XX-020
directory is a list of the actual content files to be played. Both the Messages and
Content files are ASCII text file sharing the same name but having a different extension, .msg, and .js. (Ref. Para. 2.12.2.5) for more details.
The .msg file contains the title of the pre-defined message which is then listed on the
operators list of messages. The .msg file is optional and is not needed to display a
message. The Temporary Free Text files, processed by the GUI in response to user
input, do not have .msg files and, as a result, do not show up in the operators list.
The syntax used within the .msg file is: // type_char lang1_content/
lang2_Content
//: is a constant.
type_char: Is a character that denotes the Rich or Simple type of message.
Rich messages contain HTML content including images and video. Rich
messages can only be created from the operator GUI. Rich messages use
a sun type character
Simple messages are more limited in what and how they can display, but
they can be created using the operator GUI. The Simple messages use a
dot type character. ()
lang1_content/lang2_content: This parameter contains the name that shows
up in the operator's GUI and is directly related to the file name. To determine
the correct file name, the process will strip-off the (/) character, if present
between the two languages, and any non-ASCII characters such as the Arabic
text. Lastly, all spaces are removed. The remaining text must match and determines the correct .js file to play.
NOTES:
1.
When using a single language, ensure the language contains ASCII characters, otherwise the resulting file name will be empty. For a single language
application, the slash (/) character can be removed.
2.
If a pre-define message does not have a .msg file, it will not be selectable
from the operator screen. However, it can still be requested via the OPC command tags or through the diagnostic GUI.
The .js file is essential for defining and displaying contents of the pre-define message file. It is an ASCII javascript text file which consists of specially prepared
functions for defining the displaying contents, it also shares the same name as .msg
file. In addition to the regular javascript functions, the following functions are provided for content definition:
AddContent(Name,XPos,YPos,Content,FontSize,FontColor,Blink,Sync)
Name: is a unique identification string used to identify the content. It is

use in any subsequent function to refer to the same content.
XPos and YPos: are numeric parameters which define the start position
of the content on the display (X and Y position). XPos and YPos are
expressed in terms of pixels. The position indicates the top left pixel of
the content, depending on its size, it will take up a portion of the screen
in the rectangle XPos, YPos, XPos+n, YPos+m where n and m is the
width and height of the content. The screen resolution of the PI displays
is 1920x1080.
453-SWD-RMM-0103020
MO-15.98.XX.XX/6XX-020
2-45
Rev. 01
Rev. 01
NOTE:
NOTE:
Content: defines the displayed content. A string parameter which

encapsulates plain text or HTML code. It can be as simple or as complex
as desired including the use of animated images and/or video.
It may be necessary to download additional plug-ins or codecs to support video.
FontSize: is a numeric parameter that determines the size of the true
text. This parameter has no effect if the content does not include text or
is displaying an image containing text.
FontColor: is a string parameter that determines the colour of the text.
This parameter has no effect if the content does not include text or is displaying an image containing text. The contents of this parameter can
either be a string containing one of the HTML predefined colours (such
as red, green, blue, etc.) or a hex RGB colour code (for example
#7A953C).
Blink: is a numeric parameter to blink the content text. A value of 0 indicates that blink is off while a value of 1 indicates that blink is on. Default
is 0 if omitted.
Sync: is a string parameter used for selecting between two languages
during 2 display cycles. The screen displays alternately the Primary then
the Secondary text.
Primary: is used to synchronize all the text deemed for the primary cycle of display. All text identified as primary will display
on the PI screen at the same time.
Secondary: is used to synchronize all the text deemed for the

secondary cycle of display. All text identified as secondary will
display on the PI screen at the same time.
Blank / Null: when the Sync parameter is omitted, both the secondary and primary cycles will display the secondary text and
primary text at the same time.
For displaying time the Sync parameter of Null ensures the time is displayed on
the PI screen during both cycles of the display, while text can alternate between
two selected languages by using the Primary or Secondary parameter.
SetScroll(Name,X,Y,MinX,MaxPosX,MaxX,MinPosX,MinY,MaxPosY,MaxY,MinPosY)
The SetScroll function activates directional scrolling. It permits the scroll direction
to be specified as well as the bounding positions for a repeated scroll.
Rev. 01
Rev. 01
Name: is a text string indicating the content container name. It is the

same name as used in the original AddContent function.
X and Y: are numeric parameters indicating the speed and direction of
the scroll. X and Y are measured in pixels.
X: Is Horizontal scrolling. A negative number moves the contents from right to left. A zero is for no movement, and a positive
number scrolls the contents from left to right.
Y: Controls vertical scrolling. A negative number moves the content up. A zero is for no movement, and a positive number scrolls
the contents down.
2-46
453-SWD-RMM-0103020
MO-15.98.XX.XX/6XX-020
NOTE:
NOTE:
NOTE:
NOTE:
MinX and MaxPosX: are numeric parameters used to constrain the

scrolling of text within a defined boundary condition. This function is
applied when right to left text scrolling is reset to the right hand position.
When the position of the text reaches or passes the MinX position, it is
reset back to the MaxPosX position.
The MinX or MaxPosX position might need to be set to a higher positive or a negative value for off-screen positioning. This is due to the displayed text having
width. The value would typically be equal the text width.
MaxX and MinPosX: are numeric parameters used to constrain the
applied when left to right text scrolling is reset to the left hand position.
When the position of the text reaches or passes the MaxX position, it is
reset to the MinPosX position.
The MaxX or MinPosX position might need to be set to a higher positive or a negative value for off-screen positioning. This is due to the displayed text having
width. The value would typically equal the text width.
MinY and MaxPosY: are numeric parameters used to constrain the
applied when up-text-scrolling is reset to the bottom position. When the
position of the text reaches or passes the MinY position, it is reset to the
bottom MaxPosY position.
The MinY or MaxPosY position might need to be set to a higher positive or a negative value for off-screen positioning. This is due to the displayed text having
height. The value would typically equal the text height.
MaxY and MinPosY: are numeric parameters used to constrain the
applied when down-text-scrolling is reset to the top position. When the
position of the text reaches or passes the MaxY position, it is reset to the
top MinPosY position.
The MaxY or MinPosY position might need to be set to a higher positive or a negative value for off-screen positioning. This is due to the displayed text having
height. The value would typically equal the text height.
AddAction(Name,X,Y,HoldInterval,FadeSpeed)
The AddAction function adds a pause or fade effect to the text contents.

X and Y: is the screen location, in pixels, where the AddAction effect is
triggered.
HoldInterval: is an effect that pauses scrolling content, for a set time,
when it reaches a trigger X Y coordinate.
FadeSpeed: is an effect that fades scrolling content, in a set time, when
it reaches a trigger X Y coordinate. Omitting this value or setting it to 0,
disabled this feature.
453-SWD-RMM-0103020
MO-15.98.XX.XX/6XX-020
2-47
Rev. 01
Rev. 01
NOTE:
When the FadeSpeed is enabled and a complete fade is desired, the HoldInterval
time must be set with sufficient time for the complete fade to occur.
SetDirectStat(Name,Stat,Setting)
The displayed contents is implemented by using HTML DIV containers. This function gives direct access to the content's DIV container allowing any of the normal
DIV style properties to be set directly.

Stat: is a string indicating the desired style property.
Setting: is a string indicating the desired style property.
For example, to set the background colour of a DIV content called Example to
yellow, the CSS command would be document.getElemebtById('Example').style.background-color='yellow';. This would translate into SetDirectStat('Example','background-color','yellow');.
//#directive
In addition to content commands seen above, the content files can also embed display control commands. These are implemented as comment lines.
2.12.2.5
// and #: are static characters indicating a direct embedded display command. The line is a comment line and is ignored by the content processor
on the display. However, when the PI Interface sees the directive, it
passes it on-to the PI Interface SDK module for processing.
Processing
The PI subsystem is based on Javascript and HTTPRequest enabled HTML. The PI
display screens act like web browsers that have Javascript and HTTPRequest enabled. They display dedicated web pages from the PI server, SCC Server, which contain Javascript and HTTPRequest code.
2.12.2.6
Client Side: Processing

The client side of the PI subsystem is a web browser application. The web browser
must support HTML, Javascript and native HTTPRequest. Most current browsers,
such as Firefox used on the PI displays, support these requirements.
The client loads a predetermined web page from the PI Server which also includes
several parameters. These parameters, are provided to the server within the Uniform
Resource Locator (URL) as query parameters. The parameters are, as per HTML
query strings, separated by a semicolon. These parameters are Location=Snn-z,
Zoom=nnn, Heartbeat=m:
Rev. 01
Rev. 01
Location: this parameter indicates on which client to display. The syntax uses
the letter S for station, a 2 digit number for the station number, a dash and
either a letter P or C for platform or concourse.
Zoom: this parameter is used to scale the output for smaller display screens.
Typically this Zoom parameter is set to 100 for station screens and something
less for GUI displays.
Heartbeat: this parameter is a text string parameter containing either HB for
Heart Beat or NHB for No Heart Beat. The HB parameter requires the client
display screen to send heart beat pulses back to the server. Typically this
2-48
453-SWD-RMM-0103020
MO-15.98.XX.XX/6XX-020
parameter is set to HB for station display screens and NHB for SCC Operator
GUI displays.
NOTE:
By setting this parameter to NHB for GUI displays, the GUI displays will not send
pulses to the server and thus only pulses from the read displays will be received
by the server.
Each location web page contains the same core code and implements the following
Update Process:
(1)
The Update Process is triggered periodically by a Javascript timer.
(2)
When triggered, the Update Process sends out an HTTPRequest to the

server. The request includes the last time stamp check as part of the
URLs query string.
(3)
The Update Process then separates the new time stamp from the server
results and stores it as the last time stamp check.
(4)
The Update Process then actions any remaining results from the server
as Javascript code using the Eval Function.
The above process, along with the corresponding Server Side Processing (Ref. Para.
2.12.2.7), implements a dynamic real-time content update process without having to
reload the entire page. This is critical, because reloading the page reset visual effects
such as scrolling whereas, updating the contents dynamically allows such visual
effects to continue uninterrupted.
In addition, a Secondary Update System is used to change the contents of placeholders (variables) with revised data. Place-holders are reserved keywords in content, similar to variables in programming, enabling small parts of the content to be
changed. The Content Update Process, explained above, changes between basic
content messages while this Secondary Update System changes place-holder content in the messages. For example, the contents of a countdown message might
include a countdown timer. By using a place-holder for the countdown timer, the
countdown time is updated through the Secondary Update System without needing
a separate message for each possible countdown time.
The following process is used to update the Client-Side place-holder data:
2.12.2.7
(1)
When the client first loads new content, via the above Update Process,
it locates all place-holders and places them in a hidden form on a separate web page running in the background.
(2)
This web page periodically submits its contents to the PI Server which
returns the latest values for each of the used place-holders.
(3)
The client then updates all place-holder data on each display screen. As
such, the client holds two copies of the displayed contents, the non-visible version containing all the place-holders, and the visible version
with all the place-holders containing the current values.
Server Side Content: Processing

The PI Server is a PHP enabled web server which provides HTML access to location
specific content. PHP is an open source server-side scripting language designed for
Web development to produce dynamic Web pages. While PHP originally stood for
Personal Home Page, it is now said to stand for PHP: Hypertext Preprocessor. The
453-SWD-RMM-0103020
MO-15.98.XX.XX/6XX-020
2-49
Rev. 01
Rev. 01
PI Server is part of the SCC Server utilizing the same IIS Web Server as the visualization.
When a client makes an HTML query for PI content, it does so with the location,
zoom and heartbeat parameters as part of the query string (Ref. Para. 2.12.2.6). As
such, the PI server lets the regular IIS Web Server handle the request, returning the
location specific web page. The returned web page is just a shell containing the
Javascript code for updating its contents dynamically using HTTPRequest.
When the PI Server gets an HTTPRequest from a client display screen, the corresponding PI Server page performs the following processing to service the client:
(1)
The client's location and time stamp are extracted from the HTTPRequest query string.
(2)
The time stamp of the content file for the indicated location is compared to the client's time stamp.
(3)
The time stamp of the indicated location's content file is returned to the
client.
(4)
If the indicated location's content has a newer time stamp than the clients time stamp, the client then requires a content update. To update,
the server copies the contents of the indicated location's content to the
client. This content may also contain place-holders which are then
updated using a different update method (Ref. Para. 2.12.2.8).
(5)
The time stamp of the last update request, for the specific display, is
written to a local file on the PI Server for the PI Interface SDK module.
These files, one per location, are used by the PI Interface SDK to determine if a display has stopped requesting updates in which case a corresponding Communications alarm is raised.
The update method described above, is used for significant content changes such as
changing between messages. A different update method is used for updating placeholder values. For place-holders, the client submits a Form to a different PI server
web page. This web page does the following:
2.12.2.8
(1)
Read each place-holder from the Form.
(2)
Scan each place-holder's current value.
(3)
The Forms old value is then replaced by the new value and returned as
part of a regular HTML query.
Place Holder Lookup: Processing

To look up place-holders, the PI sever employs the Scheduler module to provide
OPC connectivity support (Ref. Para. 2.12.9). For the PI system, the Scheduler
takes desired OPC tag changes (either Memory Based OPC Server tags or Alarm
Server OPC tags), and writes their values into corresponding text files in the PI
directory on the IIS Web Server. The place-holder can be inserted into any of the
content functions such as AddContent or SetDirectStat (Ref. Para. 2.12.2.4).
The PI directory is also used to store static-place-holders for changing themes, such
as the colours. Message colours can be easily changed by changing the static-placeholder value.
The PI Server performs two forms of place-holder lookups, a Single Lookup or a
Double Lookup.
Rev. 01
Rev. 01
2-50
453-SWD-RMM-0103020
MO-15.98.XX.XX/6XX-020
NOTE:
A Double Lookup is used when additional information is desired. It uses the information from a single-lookup to reference additional lookup data. For example, an
OPC tag indicating a station number can also be used to reference the station
name rather than using just the station number.
Single Lookup: the value of the place-holder is read from its corresponding
file and returned as the latest place-holder value. This type of lookup is ideal
for place-holders such as countdown and static-place-holders. The syntax for a
Single Lookup place-holder is: {{Place_Holder_Name:Direct}}
Place_Holder_Name: is the name of the place-holder and also the name

of the corresponds PI Server file containing the latest value of that placeholder.
Direct: is a keyword constant which indicates Single Lookup.

Double Lookup: the place-holder is first evaluated like a Single Lookup. The
returned value is referenced using the format portion of the place-holder. The
file name used for this second lookup is a concatenation of the format, an
underscore, and the value of the first lookup. The syntax for a Double Lookup
place-holder is: {{Place_Holder_Name:Format}}
Place_Holder_Name: is the name of the place-holder and also the name

of the corresponds PI Server file containing the latest value of that placeholder.
Format: is a prefix string on the place-holder that is concatenated with

the value of the Single Lookup to determine which Second Lookup file
to use.
For example, consider an OPC tag for station number, and assuming that the PI
Server tag is stored in files containing the name of the corresponding station and are
named StationName_1.txt, StationName_2.txt, StationName_3.txt and so forth. The
place-holder {{StationNum:StationName}} in the content is used to extract the station name using the Station Number. When the PI server processes the lookup, it
first reads the second part of the place-holder for the keyword constants Direct or
Format. It then does a Single Lookup on the place-holder named StationNum. If we
use 3 as our example, it then concatenates the Format, StationName, with the value
of the lookup (separated by an underscore), to determine the name of the file used
for the second lookup. For this example, it reads the value stored in
StationNum_3.txt and returns the contents (Station 3).
2.12.2.9
Content Request: Processing

The PI Interface supports changes to the screen content files for any location and initiates the update process to ensure that new content is displayed on the screens. The
PI Interface subscribes to a number of Memory Based OPC Server tags as defined in
the pre-configured input configuration files (Ref. Para. 2.12.2.1). The following
procedural steps describe the culminated process taken when one of the OPC command tags change, the PI Interface performs as follows:
(1)
The parameters of the request are extracted and analysed to determine

an active request. This includes confirming the exclamation (!) character at the beginning of the message and the correct number of parameters (Ref. Para. 2.12.2.3).
(2)
Instead of clearing the tag, the request is written back to the OPC command tag without the exclamation (!) character. This tag modification
ensures the request will be processed again, even if the exact same
453-SWD-RMM-0103020
MO-15.98.XX.XX/6XX-020
2-51
Rev. 01
Rev. 01
request is made again. By excluding the exclamation mark, the PI Interface then rejects this as a new command (Ref. Para. 2.12.2.3). This
process provides an added benefit of keeping a copy of the request in
the OPC tag. This aids in trouble shooting because the contents of the
request are still available.
(3)
The mode parameters in the request are extracted and compared to the
currently stored mode for each requested location (Ref. Para. 2.12.2.3).
If the location is not currently holding or the request mode is higher
than the currently holding mode then processing continues for that
location. If the mode is equal to or lower, the location is removed from
the location list and a warning is written to a pre-configured OPC tag.
The exception to this process is the Clear Message command which
executes if the requested priority mode is higher or equal to. In this
manner, an operator can always clears issued messages.
(4)
The OPC tags are written for each locations' mode, content, and holding which indicate the screens are displaying.
(5)
The message directory is scanned for files of the same name parameter
with -platform or -concourse appended. If these two files exist, this
means that the requested content is different for platform and concourse. The files are then copied into the content directory and renamed
to the location's Snn-z code (Ref. Para. 2.12.2.1). This causes the PI
update system to spot a content change and provide the new contents to
the client on the next client update poll.
(6)
If the -platform and -concourse versions of the content files do not

exist, the content parameter name is compared for a matching content
file. If it exists, the same content is used for both platform and concourse screens. The content file is copied to the contents directory and
renamed to the location's Snn-z code (Ref. Para. 2.12.2.1).
(7)
If no content files are found, the request is ignored and a warning is

sent via OPC tag indicating that the content was not found.
(8)
If required, a timer is started for the specified Hold duration (Ref. Para.
2.12.2.3). When the time expires, a check is made of each location
playing requested messages. If confirmed, the location's mode and
holding OPC tags are cleared, mode is set to 255 and holding is set to 0.
NOTE:
2.12.2.10
The content OPC tag is not cleared because the screen displays the content until
a new request has replaced it. Higher priority messages will supersede lower priority messages.
Outputs
The transfer of messages from the message directory to the contents directory are
the PI Interface outputs, the messages are renamed with the corresponding location
code.
The outputs of the PI Interface are the locations' mode, content, and holding tags
which the PI Interface sets and clears, indicating the location's state.
The PI Server outputs are location specific web pages containing core javascript
update code, HTTPRequest responses containing the javascript content update code,
and a web page with a Place Holder form, updated with the latest Place Holder values when submitted.
Rev. 01
Rev. 01
2-52
453-SWD-RMM-0103020
MO-15.98.XX.XX/6XX-020
2.12.2.11

The PI Interface operates on the SCC server as a stand alone module, not requiring
any direct user interaction. However, for troubleshooting and testing purpose, a PI
Interface Diagnostic GUI is provided with some functionality.
The top right LED indicates successful connections to the OPC Server. A red LED
indicates a connection has not been established. Check that the server name has been
correctly specified in the configuration file.
NOTE:
When a connection to the OPC Server is not established, OPC commands tags
won't work and the location's mode, content, and holding tags will not be
updated.
A green LED indicates a successful connection has been established.

The main body of the Diagnostic GUI displays the last few commands that were
requested through the OPC command tags, or through the Diagnostic Request
Engine. By default only the request information is shown. However, the PI Interface
can be started with a command line parameter indicating the verbose level (typically
1 to 5). In this case, more detailed information about the processing is output.
The Diagnostic Request Engine is the input text box at bottom of the Diagnostic
GUI. Through this text box, the user can enter requests as if they were provided
through OPC command tags without actually submitting the request through OPC
tags. This permits testing of the system without having to use an OPC client.
NOTE:
2.12.3
Requests entered in the Diagnostic Request Engine must have the exact same format as requests sent through OPC tags, including the starting exclamation mark
character.
PA Interface (PA Interface, SDK, and the PA Server)

The requesting cycle of Public Address is a 3 stage process.
First, the request is pushed to the PA Interface module which performs

processing. This processing is similar to the PI Interface for setting the corresponding location's OPC tags and preparing the content. However, the prepared content, instead of being usable by a web server, is passed to a second
stage.
The second stage interface is called the PA Interface Software Development
Kit (SDK) module. This SDK module converts the legible content file into
SDK instructions, understood by the PA server.
Lastly, these SDK instructions are pass to the third stage, the PA server for
processing.
By splitting up the PA request cycle in this manner, the PA messages can be configured in easy to read content files, since SDK instructions are cryptic. It also makes
problem solving with the PA Interface, easier to diagnose. For example, problems
with status OPC tag being set indicates issues with the first stage module. And, if
incorrect message are played the likely problem is again with the first stage. If the
PA content is incorrect or is absent, but other requests are working fine, the likely
problem is in the second stage. If all PAs are absent, the likely problem is with the
third stage.
453-SWD-RMM-0103020
MO-15.98.XX.XX/6XX-020
2-53
Rev. 01
Rev. 01
Figure 2-6. PI Diagnostic GUI

Rev. 01
Rev. 01
2-54
453-SWD-RMM-0103020
MO-15.98.XX.XX/6XX-020
2.12.3.1
Inputs
The PA Interface takes inputs for the pre-configure configuration files and the connection to the Memory Based OPC Server.
2.12.3.2
Config.Txt: Inputs
The format for the ASCII text file is the same as most of the other modules. It contains key/value pairs which are used by the PA Interface for configuration. The key/
value pairs used by the PA Interface are:
OPC.Server opc_server_name: This key/value pair specifies the name of the

Memory Based OPC Server.
OPC.Confirmation.Tag opc_tag: This key/value pair identifies the OPC tag
used to return all processing confirmations and errors.
OPC.PA.VIPET: This key/value pair indicates the VIPET, PA Server, used for
requests. The VIPETs are configured with a Global process which permits
sending requests for any locations, from any location.
SCC.SERVER.PA.Dir.Messages path_dir: This key/value pair indicates the
non-network-directory where the PA messages are stored. A local reference
such as C:\inetpub\wwwroot\Modules\PA\Msg should be used rather than a
network reference like \\SCC_Server1\Moduels\PA\Msg.
SCC.SERVER.PA.Dir.Content path_dir: Indicates the key/value pair for the
non-network-directory where the clients source the content files.
SCC.SERVER.PI.Dir.Formats path_dir: This key/value pair indicates the
non-network-directory where the variable formats are stored.
NOTE:
2.12.3.3
For storage efficiency, the tag refers to PI rather than PA. The same formats are
used by both PI and PA, thus PA uses the PI tag to locate this directory.
OPC.PA.Command.Tag.nn opc_tag: This is a set of key/value pairs for all

the OPC tags monitored by the PA Interface Module requests. The variable nn
is an two digit number starting at 01 and incrementing by 1 for each OPC command tag. Each entry should have a unique OPC tag. Multiple OPC tags can be
specified this way, permitting multiple workstations to make simultaneous
requests to the PA Interface Modules without overwriting each other's request.
OPC.PA.Mode.Tag.location
opc_tag,
OPC.PA.Content.Tag.location
opc_tag, OPC.PA.Playing.Tag.location opc_tag: These key/value pairs, one
for each zone, determine which OPC tag holds the zone's priority mode, contains a brief description of its contents, and contains the playing status for the
current message. In each set, the tag.location is indicated by a PA zone of the
following syntaxes:
stationN-platform, N is a single digit station
stationN-concourse, N is a single digit station
depot-maintenance
depot-office
depot-trackside
OPC Server: Inputs

Request inputs to the PA Interface Module are, made using the specified OPC command tags, and pre-configured in the Config.txt file (Ref. Para. 2.12.3.2). These
453-SWD-RMM-0103020
MO-15.98.XX.XX/6XX-020
2-55
Rev. 01
Rev. 01
Request tags must comply to a rigid entry format or they will be rejected. The syntax
for the tag, similar but not completely identical to the PI request format, is as follows: !Mode Chime Content Repetitions Locations
!: the exclamation character is a constant, indicating an active request.

Mode: is a number representing the sent priority mode of the message. The
Priority Mode determines what is done in the event another currently playing
message is encountered at any one of the desired destinations.
Chime: represents the chime number selected to sound, if the contents contains a chime trigger. Chime number 0 indicates no chime, and numbers 1 to 3
indicate chimes with the same number of annunciations.
NOTE:
Content: is the name of the PA message to be played.
NOTE:
A corresponding message must exist in the Message folder on the PA Server (Ref.
Para. 2.12.3.4).
Repetitions: indicates the number of times the desired message is played. This
value is not used when Live content is selected.
NOTE:
The contents dictates when the chime will be used, if the contents doesnt trigger
a chime, even when a chime number is identified, it will not be played. In other
words, the contents dictates if and when the chimes are played, before, and/or
after. Of note, it is possible for the contents to force a chime rather than using the
user-selected-chime.
The Repetitions value indicates the number of times that the contents should be
played. If the contents contains a repeated message then this Repetitions parameter will multiply the repetitions by the indicated amount.
Locations: is a space separated list of play locations, using the same syntax as
the location portion of the Config.Txt file (Ref. Para. 2.12.3.2).
A sample PA request might look like:

!9 2 Arrival 3 station1-platform station1-concourse
NOTE:
2.12.3.4
Unlike the PI contents, there is no option for automatic zone specific contents.
Thus, if different messages need to be played in different zones, such as on the
platform and concourse, they need to be triggered with separate requests.
Message Files: Inputs

All messages requested through the PA Interface Module are treated as pre-defined
messages, including Live PA announcements and Text-To-Speech (TTS) messages.
For a TTS message, the GUI generates a temporary pre-defined message containing
the desired content, sends the request and then deletes it.
To define the contents of a pre-defined audio message, create one or more entry in
the Messages directory, as specified in the reference Config.Txt file. The Message
directory is a list of all the possible pre-defined messages whereas the Content directory is a list of actual content files that are playing (Ref. Para. 2.12.4.1).
Both the .msg and the .txt file are ASCII text files sharing the same name but having
different file extensions.
The .msg file is optional, it is named based on the content. The file format for this
file is identical to the same named file used by the PI Interface (Ref. Para. 2.12.2.4).
As with the PI Interface, if a pre-define message does not have a .msg file, it will not
Rev. 01
Rev. 01
2-56
453-SWD-RMM-0103020
MO-15.98.XX.XX/6XX-020
be selectable from the operator GUI but can still be requested via the OPC command
tags or through the diagnostic GUI.
The .txt file is not optional, it defines the audio contents of the pre-define message
file. This file shares the name with the content keywords that are used to retrieve the
content file, and are set in the .msg file, if one exists. The content is a UTF-8
encoded file which supports multilingual applications, and complies with the following directives.
NOTE:
A.
The content file may have many directives. Pay close attention to the order of the
directives, such as A, D, F, I, K, T and X, because the content will be played back in
the same order. Directives which do not affect the content directly such as U and
Z may appear anywhere in the content file before the action commands.
A:audio_file
The A directive inserts the contents of the specified audio file .WAV or .MP3 into
the contents. The corresponding audio file must be uploaded to all VIPETs into the /
dva/msgs directory.
NOTE:
B.
The audio files only need to be uploaded to the VIPETs associated with destinations where the file will be used. For example, an audio file which will only be
played in the depot can be uploaded to the depot VIPET and does not need to be
uploaded to the station VIPETs.
C:chime_file
The C directive inserts the contents of the chime audio file .WAV or .MP3 into the
contents. The corresponding audio file must be uploaded to all the VIPETs /dva/
msgs/chimes directories where the chime will be used. This directive is used with a
{Chime} place holder to insert the specified chime into the request,
C:chime{Chime}.wav. The {Chime} place holder is replaced with the numeric
selection made by the user. If the user, for example, wanted Chime number 2, by
selecting 2 from the GUI would result in C:chime2.wav.
C.
D:milliseconds
The D directive inserts a delay or a period of silence into the contents. The parameter indicates the length of the delay in milliseconds.
D.
F:File_UTF8
The F directive inserts UTF8 Text-To-Speech contents form a specified file, containing UTF8 text, into the contents. Contents requiring UTF8 text is added with a T
directive, making the contents file easier to read since there are no external files to
reference. For example, the core of a message can be inserted using the T directive
and the F directive can be used to append the contents of a file written by other processes. In this example, the final contents can be adjusted to system conditions without having to create multiple content files.
E.
I:Microphone_ID
The I directive links the contents to the specified microphone for live audio. The
specified microphone name must be configured on the VIPET and the microphone
must be properly connected to the VIPET for this functionality to work.
F.
K:Zones
The K directive is used to stop a specific zones from playing audio. This directive is
used with the {StopZones} Place Holder and must be the first entry in the content
file for systems configured as non-queuing. Since the first stage performs priority
453-SWD-RMM-0103020
MO-15.98.XX.XX/6XX-020
2-57
Rev. 01
Rev. 01
mode evaluation (Ref. Para. 2.12.3.3) for playing content, it can be said, for this
example, that the Mode has determined that the new content has higher priority than
any message that may be playing. As such, the K directive stops the currently playing message before playing the new content.
NOTE:
G.
If the system is configured for queuing, then this directive must not appear in the
content otherwise the queue will be destroyed.
N:Setting
The N directive is reserved for future use for Noise Compensation using an Ambient
Noise Sensor connected to the VIPETs. The setting is a numeric value 0 for Noise
Compensation OFF and 1 for ON.
H.
T:Text_UTF8
The T directive inserts UTF8 Text-To-Speech into the contents. This option must be
used when trying to insert Text-To-Speech using portuguese characters.
NOTE:
I.
Ensure that the content file is saved as a UTF8 file format otherwise the content
of all UTF8 text will be destroyed.
U:Urgency
The U directive is used to set priority mode of the contents. Typically this is always
set to the {Mode} Place Holder so that the priority mode of the request is used.
NOTE:
There are actually two layers of priority mode evaluation. First, a priority mode
check by the PA Interface evaluates if the message can be played. This check is
always performed on the request priority mode and has nothing to do with this U
directive. The second layer of priority mode evaluation is done by the PA server. It
is recommended these two priority modes remain in sync by setting the U directive to the {Mode} Place Holder. This ensures that the same request priority mode
is passed to the U directive, and thus to the PA Server.
The U directive is used in cases where a third party application creates content files.
These files would not therefore use the first stage PA Interface, but use the second
stage PA Interface SDK module to play these files. As a result, the {Mode} Place
Holder is not used, and the U directive hard code determines priority mode.
J.
V:Voice
The V directive is a variable used to set the current voice or language, until another
V directive is issued. The V directive must precede any content that is to be
announced using that selected voice. Typically each voice is associated with a different language allowing multi-lingual messages to be broadcast without heavy
accents. However, this same directive can also be used to switch between voices of
the same language.
NOTE:
K.
It is important to properly match voices with the correct language content

because voices for other languages will, at best, speak the contents with a heavy
accent or, at worst, not speak at all because the characters will not be understood.
X:Text_ASCII
The X directive inserts ASCII Text-To-Speech into the contents, it is used when the
TTS contents uses plain English characters. In most cases, the T directive should be
used rather than the X, since it can add both standard and non-standard characters.
The X directive permits external programs to write ASCII content files even if they
do not support UTF8 where the T directive may be in-compatible.
Rev. 01
Rev. 01
2-58
453-SWD-RMM-0103020
MO-15.98.XX.XX/6XX-020
L.
Z:Zone
The Z directive adds a location to the list of locations where the content should play.
Each location must have a separate Z directive. This directive is commonly used
with the {Locations} place holder to pass the desired location from the request to the
contents processor. The {Locations} place holder is automatically expanded into
multiple Z directives if necessary. The syntax for using the {Locations} place holder
is: Z:{Locations}.
M.
Action Commands
The last line of the content file is reserved for the Action Command. Care should be
taken to ensure that there are no empty lines or comment lines after this line, otherwise repetitions will not work correctly. The action line must be one of the following:
Play - The Play action passes the directives to the pre-defined message handler, of the PA Server, for execution. The common exception to this is when the
directives include Live PA (such as the I directive).
Live - When the source includes Live PA (such as the I directive) the directives
need to be sent to the live message handler, on the PA Server, for execution as
a result this Live action command needs to be used. The Chime and Delay
directives are still compatible with the Live action.
Stop - The Stop action is used to stop currently playing audio in specified
zones without playing any new audio. Any content directives, if present, are
ignored. The same results can be achieved using the K directive and the Play
action command, if no other content directives are added.
Background Music - The Background Music action command toggles Background Music ON and OFF. When this feature is turned ON and there is no
currently playing messages, the PA Server will play the audio provided
through its audio ports is connected to a station level music player.
Health - The Health action command is used to obtain zone health status without playing any content. Any content directives, if present, are ignored.
Quit - The Quit action command quits the PA Interface SDK without processing the directives. Typically this is only used for troubleshooting the interface
of PA Interface SDK.
In addition to the reserved Place Holders {Chime}, {Mode}, {Locations} and

{StopZones} the PA content file can use user Place Holders. These Place Holders
follow the same rules as PI Single Lookup Place Holders except that the Place Holders are enclosed in single brace brackets and the :Direct format is dropped. These
user defined Place Holders can be used to create content with parameters that can
easily be changed. For example, the voice (V directive) can be expressed as a Place
Holder so that if, in the future, the voice is changed all contents can easily be
updated by updating the voice Place Holder instead of having to edit each content
file.
2.12.3.5
PA Interface: Processing
The PA Interface receives request either through OPC command tags or the GUI
interface (Ref. Para. 2.12.3.7), it performs the following functions:
The request is analysed to make sure it is a valid request, it includes checking

for the presence of the exclamation (!) mark.
453-SWD-RMM-0103020
MO-15.98.XX.XX/6XX-020
2-59
Rev. 01
Rev. 01
A.
The OPC Command tag is written back with the request but with the exclamation mark omitted. This allows a later identical request to be processed. As the
exclamation mark is omitted, the OPC tag is not processed by the PA Interface
as a secondary request.
The request parameters is extracted and the currently stored mode for each
requested location is compared to the request mode.
If the request mode is equal or lower, the requested location is removed

from the location list and a warning message is sent through the Confirmation OPC tag.
In the case of a STOP message, the location is removed only if the

request mode is lower (for example, if the request mode is equal or
higher, the STOP is processed at that location). This ensures that an operator that initiated a message always has priority to stop it.
All the requested locations mode, content and playing OPC tags are set.
The desired content file is added to a copy of the BaseContent.txt found in the
PA directory. During this process the reserved Place Holders as well as any
user Place Holders are replaced in the file. The BaseContent.txt file provides
the base code that passes the added content file to the PA Interface SDK module. The result is a Batch file which is executed to have the PA Interface SDK
module which actually carries out the PA request. The file should be given a
unique name (to prevent multiple requests from overwriting each other) ending
in the extension .Bat.
The executing of the Batch file through the BaseContent.txt file includes the
commands for re-connecting to the PA Interface and commands for clean up
after the PA Interface SDK module finishes playing the requested content. This
is done by sending a request using the OPC command tag starting with the tilde
character (~). This is followed by a (automatically generated) cryptic string
which indicates to the clean up processor as to which locations needs to be
cleaned up and which request expected them to be playing.
A part of the Batch file through the BaseContent.txt file also includes commands for writing the health status gathered by the PI Interface SDK module
and returned through the return exit code to corresponding OPC tags.
When the PA Interface gets an OPC command request that starts with the tilde
character, it extracts the content and locations from the command. It compares
the current mode and content for each listed location to the mode and content
specified in the request. If they match the corresponding mode content and
playing OPC tags are cleared (set to 255 for mode, set to Idle for content and
set to 0 for playing). If the mode or content does not match then the currently
playing message, at the corresponding location, must be playing a message that
was requested by a different request and had higher priority. In such a cases no
clean up is performed because such locations will be cleaned up by the more
recent request processor.
PA Interface SDK:
Once the PA Interface SDK module is triggered by the BAT file made by the PA
Interface, a number of command line parameters are passed from PA Interface,
through the Batch file, to the PA Interface SDK module. The syntax for the PA Interface SDK module is as follows:
Rev. 01
Rev. 01
2-60
453-SWD-RMM-0103020
MO-15.98.XX.XX/6XX-020
PA_Interface_SDK JCOP_Server Verbose PQueue LQueue

The JCOP server parameter specifies the sever on the VIPET for the making of PA
requests. The PA Interface passes the JCOP server specified in the input configuration file as parameter 1 to the Batch file and the Batch file passes this on to the first
parameter of the PA Interface SDK module.
The Verbose parameter indicates the verbose level of the output that is generated
while the PA request is being processed. The PA Interface passes this parameter,
always 0, to the Batch file as parameter 2 and the Batch file passes this on to the second parameter of the PA Interface SDK.
The PQueue and LQueue indicate if the PA Server is to queue messages that cannot
be processed immediately. PQueue refers to queuing for predefined messages while
LQueue refers to queuing for live messages. The PA Interface passes this setting,
always 0, to the Batch file as parameter 3 assuming that both PQueue and LQueue
will use the same setting. The Batch file passes this setting on to the PA Interface
SDK as parameters 3 and 4.
During the processing of PA Interface SDK requests, the module reads the diagnostics of the PA system and returns the values, after processing the request, as the exit
code. This is then used by the calling Batch file to post the health status back to the
GUI using pre-arranged OPC tags.
B.
PA Server:
The detailed processing of the PA Server is beyond the scope of this document. In
broad terms, the PA Interface SDK uses SDK instructions, sent to the PA Server's
(software) JCOP server, to request the specified PA functionality. The PA Server, in
turn, sends back, through the JCOP server, events indicating the status of system and
the status of the requested functions.
2.12.3.6
Outputs
The outputs of the PI Interface module is a text for the specified locations' mode,
content and playing OPC Tags (set and clear) as well as the execution of a created
Batch file containing instructions to launch PA Interface SDK along with the contents for PA Interface SDK to process.
The output of the PI Interface SDK is a set of instructions set to the VIPET JCOP
server requesting the desired PA functionality as well as the PA diagnostic result
passed back through the PI Interface SDKs exit code.
2.12.3.7
Diagnostics
The PA Interface provides the exact same diagnostics as the PI Interface (Ref. Para.
2.12.2.11) except that they relate to PA functionality instead of PI functionality.
2.12.4
Net Check
The Net Check module allows the verification of network devices using either a
PING or RUDE connection. The results are reported back through OPC tags to the
Memory Based OPC Server.
In addition to the below listed inputs and outputs, the Net Check module includes
PING and RUDE as inputs and Outputs. But these inputs and outputs are only used
during the processing phase.
453-SWD-RMM-0103020
MO-15.98.XX.XX/6XX-020
2-61
Rev. 01
Rev. 01
2.12.4.1
Inputs
The Net Check module takes two pre-configured configuration files as input.
A.
Config.Txt:
This is the same flat ASCII text file format as used for other modules. The key/value
pairs used by the Net Check module are:
Indicates the name of the OPC server to which results are posted.
B.
Net Check.Txt:
This file is a flat ASCII text file with one entry per line. There are three different
type of entries that can be made:
P ip_addr Name : OPC_Tag,
R ip_addr ip_port Msg Name : OPC_Tag, and
D
2.12.4.2
The P command executes a PING check a specified IP address (ip_addr) and

responds to a PING command. Name indicates a reference name to be use on
the GUI. OPC_Tag indicates the OPC tag to which the results are posted.
The R command connects to the specified IP address (ip_addr) on the specified
port (ip_port). If the connection is successful an optional message will be sent
specified by the Msg parameter. If no message is to be sent before disconnecting the Msg parameter should be 'None'. Once Msg is sent (or not set if 'None')
the connection is closed. OPC_Tag indicates the OPC tag to which the results
are posted.
The D command is to specify a single cycle Delay.
Processing
Once The Net Check module starts up, it reads all the checks it needs to perform
from the NetCheck.txt input file. It stores this in a list and on each pulse it processes
the next check in the list. Once it gets to the end of the list, it restarts from the beginning.
P commands are processed by executing a PING on the specified address. The
response is timed. The result (which could be a time out) is written to the corresponding OPC Tag and the result is extracted graphically on the two GUI pages.
R commands are processed by connecting to the specified address on the specified
port. The response is timed. The result (which could be a time out) is written to the
corresponding OPC Tag and the result is extracted graphically in the two GUI pages.
If the command contains a message, the message is sent before disconnecting, otherwise the disconnection is made right away.
D commands are processed by no action on that poll cycle. This causes a pause in
checking until the next poll cycle. Typically D commands is used to lower CPU
usage.
Most network connected device supports the PING check unless the network has
disabled PING functionality. However, not all network devices support RUDE
checks because RUDE checks are based on TCP/IP connections but some devices
Rev. 01
Rev. 01
2-62
453-SWD-RMM-0103020
MO-15.98.XX.XX/6XX-020
may not be TCP/IP based servers (for example, could be UDP devices, SIP devices).
Typically RUDE connection, however, provide more information about the state of
the device than PING. A PING connection indicates that a device is connected to the
network and has at least some network functionality working. However, PING does
not indicate if server components are active.
The Msg option in the RUDE check is provided so that when connecting to servers
where the user would typically type an exit command (instead of just disconnecting), the RUDE check can do the same.
2.12.4.3
Outputs
The outputs of the Net Check module is a text to the corresponding OPC Tags identifying if the device passed or failed the check. In addition, the results are presented
on the Net Check GUI as both a check box (passed/failed) and a sonar map representing the response time of the check.
2.12.4.4
Diagnostics
To start the NetCheck Module in application mode, first ensure that the service version of the Module is stopped (from the Windows Services screen). Failure to do so
can cause unpredictable results since two versions of the module will try to process
the same data. Once the service version of the Module is stopped, the application
version can be stated by running the Module with the -dialogue command line
parameter. To revert back to the service version, ensure that the application version
is closed and then re-start the Module service (from the Windows Services screen).
The application version of the Module provides a GUI where the results will be seen
graphically (check boxes and sonar response time) as opposed to just getting the
information back through OPC tags.
2.12.5
CCTV Alarms
The CCTV Alarms module provides alarm information about the SME (CCTV system) and provides a method for the SCC to increase the recording frame rate on specific cameras when non-CCTV alarms, related to a CCTV camera, are tripped.
2.12.5.1
Inputs
The CCTV module uses a number of pre-configured input configuration files as
well as tags on the Memory Based and Alarm OPC Server.
A.
Config.Txt:
The format for the Config.Txt file is a flat ASCII text file with key/value pairs (same
as other modules). The key/value pairs used by the CCTV module are:
OPC.ALARM.SERVER opc_server_name
The above value/pair defines the Memory Based and Alarm OPC Server to be used
with the CCTV module.
B.
Map.Txt:
The map file is the bi-directional mapping between the Genetec CCTV directory
and the CCTV Module. This map includes mappings from Genetec CCTV directory
alarms to OPC tag and mappings from OPC tags to Genetec CCTV directory macro
triggers.
453-SWD-RMM-0103020
MO-15.98.XX.XX/6XX-020
2-63
Rev. 01
Rev. 01
Each of these cases has a slightly different syntax, there are two different entry syntax that can be found in the map file. They are as follows:
A.
Opc_tag_name<-keyword,IP_addr,state, and
B.
Opc_tag_name->CCTV_directory_trigger_ID.
Opc_tag_name<-keyword,IP_addr,state
This syntax maps CCTV directory alarms to OPC tags in the Memory Based OPC
Server.
The opc_tag_name parameter indicates which tag in the Memory Based OPC Server
is set.
The <- is a constant indicating the direction of data flow from the alarm to the OPC
tag.
The keyword parameter is used to identify the type of alarm generated in the CCTV
directory.
The IP_addr parameter is used to identify on which device the indicated alarm has
occurred (typically the IP address of the camera).
The state parameter indicates the value written to the OPC tag. In most cases CCTV
alarm is event based alarms which have no reset condition. In such a case the visualization needs to reset the OPC tag (as soon as possible) to allow the same alarm to be
re-triggered if necessary. In such a case the visualization will only indicate that the
event has been triggered but not when it has concluded.
However, in some cases, such as transmission lost, the CCTV directory provides
both the set and reset state. In such a case an entry, in the map file, can be made for
both the set and reset condition, both mapped to the same OPC tag, with different
state values.
The CCTV Module, in this case, acts like a multiplexer. It takes the CCTV directory
alarm and based on the alarm text and the IP address that generates it, it trips the corresponding OPC tag.
Opc_tag_name->CCTV_directory_trigger_ID
This syntax is to map alarm server OPC tags to CCTV directory macro triggers. This
functionality is typically used to trigger pre-configured macros in the CCTV directory to increase recording rate. The CCTV module subscribes to the OPC alarm tags
which have CCTV cameras associated with them. When these alarm trips, the
CCTV module is notified about the state change and, if a corresponding mapping is
found in the map file, sets the corresponding CCTV directory trigger on the Genetec
CCTV directory. This in turn, if configured properly (which is beyond the scope of
this document), causes a macro to increase the frame recording speed for 5 minutes.
C.
OPC Server:
A subscription to the OPC Alarm Server is an input to this module in order to trigger
CCTV directory triggers when the corresponding alarm tag is changed on the OPC
Alarm Server.
Although the Memory Based OPC Server is an output of the CCTV Module in terms
of module data flow, the OPC protocol is bi-directional and thus this server is also an
input for the purpose of data lower level processing flow.
Rev. 01
Rev. 01
2-64
453-SWD-RMM-0103020
MO-15.98.XX.XX/6XX-020
2.12.5.2
Processing
There are two independent processing streams to the CCTV module: alarms from
the CCTV directory being posted to the Memory Based OPC Server and the
processing of OPC Alarm Server alarms into CCTV directory triggers.
A.
CCTV Alarms:
When the CCTV module first starts, the map is read into memory and stored for later
processing. When the CCTV directory generates some CCTV related alarms, the
following is done:
B.
(1)
The keywords in each stored entry is compared to the generated alarm

text (name).
(2)
The IP address for each stored entry (that passed step 1) is compared to
the IP address of the device that initiated the CCTV directory alarm.
For each entry whose IP address matches the IP address of the alarm
source processing continues with step 3, otherwise processing, for that
stored entry, ends.
(3)
The state for each stored entry (that passed step 2) is compared to the
state of the generated alarm. For each entry whose state matches the
generated state, processing continues with step 4, otherwise processing, for that stored entry, ends.
(4)
The OPC tag and state parameters, of the stored entry, is analysed out
and the state is written to the Memory Based OPC tag.
Non-CCTV Alarms:
When the CCTV module first starts, the contents of the map file are stored in memory for future processing. A subscription to the OPC Alarm Server is made for all
alarm tags listed in the map file.
When one of these Alarm Server OPC tags change, the following is done:
(1)
All stored entries are consulted to see which, if any, match the changed
OPC tag. Since the subscribed OPC tags are based on the map file, at
least one matching entry will be found.
(2)
For each matching entry, the CCTV_Trigger_ID is extracted and then

triggered using the Gentec SDK interface.
The activating of the corresponding trigger on the CCTV directory does not actually
perform any action on its own. However, if the CCTV directory is properly pre-configured so that the trigger runs a corresponding macro, the activation of the trigger
will be used to start increased frame rate recording (or any other CCTV directory
based operation). This pre-configuration, however, is beyond the scope of this document.
For safety reasons, the increased frame rate lasts 5 minutes and then automatically
decreases back to the lower recording frame rate. This is done intentionally so that
the operators do not accidentally leave the camera in high recording rate for
extended periods of time (which can impact length of video storage). The lowering
of the frame rate is done internally on the CCTV directory and do not involve the
CCTV Module.
453-SWD-RMM-0103020
MO-15.98.XX.XX/6XX-020
2-65
Rev. 01
Rev. 01
2.12.5.3
Outputs
The CCTV Module has two independent outputs, one for each type of processing.
NOTE:
A.
Note that while the OPC Alarm Sever is a module input in terms of module data
flow, it is also an output, in terms of lower level data processing, since the OPC
protocol is bi-directional.
CCTV Alarms:
For CCTV Alarms, the output is text to Memory Based OPC Server tags.
B.
Non-CCTV Alarms:
For non-CCTV alarms, the output is the activation of corresponding triggers in the
CCTV directory.
2.12.5.4

The CCTV module is designed to be run on the SCC Server in stand-alone service
mode. For diagnostic purposes the CCTV Module can be run in application mode
which provides a minimal GUI and used in the process of troubleshooting.
The top part of the GUI indicates connection status to the CCTV directory and
refresh pulses.
The LED on the top right hand side indicates the connection to the OPC servers. If
the LED is red, a connection to the OPC Server cannot be made. Check the config
file to ensure that the OPC Server has been correctly specified. If the LED is green
then a connection to the OPC Server is established.
The second area from the top is a grid that shows the data that the CCTV module has
received from the CCTV directory. This data is analysed and the results are passed
to the third area from the top.
The third area from the top is a list of detected transactions. Entries in this area are
analysed against the stored entries to determine if any action is needed.
The label between the third and last area on the GUI indicates the last OPC transaction.
The last area is a text box used for GUI tag simulation. By entering an OPC tag name
and pressing ENTER, an OPC tag change is simulated. This is used to test NonCCTV Alarm processing without having to change OPC tags.
To start the CCTV Module in application mode, first ensure that the service version
of the Module is stopped (from the Windows Services screen). Failure to do so can
cause unpredictable results since two versions of the module will try to process the
same data. Once the service version of the Module is stopped, the application version is stated by running the Module with the -dialogue command line parameter. To
revert back to the service version, ensure that the application version is closed and
then re-start the Module service (from the Windows Services screen).
2.12.6
Alarm Suspension
The Alarm Suspension module runs on the SCC Server waiting for requests made
by changing OPC tag on the Memory Based OPC Server. Requests are made to enable or disable alarms and allow the request to be carried out on either specific alarm
or a group of alarms. The module has options to confirm the action or each affected
point through an OPC tag on the Memory Based OPC Server (typically associated
Rev. 01
Rev. 01
2-66
453-SWD-RMM-0103020
MO-15.98.XX.XX/6XX-020
Figure 2-7. CCTV Module

453-SWD-RMM-0103020
MO-15.98.XX.XX/6XX-020
2-67
Rev. 01
Rev. 01
with the Confirmation Bar). Lastly there is an option for the disabled points to be reenabled after a specified time has expired.
2.12.6.1
Inputs
The Alarm Suspension module uses one pre-configured, flat, ASCII text file for its
configuration. This file is called Config.txt and resided in the same directory as the
Alarm Suspension module.
The format of this configuration file, as with other modules, consist of key/value
pairs. The specific keys required by the Alarm Suspension module are:
OPC.SERVER OPC_Server_Name,
OPC.ALARM.SERVER Alarm_Server_Name, and
OPC.REQUEST.TAG.n OPC_Tag.
The first value/pair indicates the name of the Memory Based OPC Server on which
requests to the Alarm Suspension module is made.
The second value/pair indicates the name of the OPC Alarm Server on which points
is disabled/enabled.
The third value/pair, where n is unique number, can be repeated as necessary and
indicates all the tags on the OPC Memory Based which is used for making requests
to the Alarm Suspension module. Multiple tags allows each SCC Workstation to use
a unique OPC tag so that simultaneous requests from multiple workstations will not
overwrite each other.
In addition to the above required OPC tags, at least one entry of the following value/
pair requires:
REGISTER.TAG Alarm_Server_Tag
Where Alarm_Server_Tag is the enable property of the desired OPC tag on the
OPC Alarm Server. This is the attribute that the Alarm Suspension module writes in
order to enable (1) or disable (0) then corresponding alarm.
This entry is repeated for each possible tag that is, potentially, disabled/enabled by
the Alarm Suspension module.
Lastly an optional key/value pair is specified to identify the Confirmation Bar OPC
Tag to which confirmations (action or item) are written in cases where confirmation
is requested. The syntax for this key/value pair is:
OPC.Confirmation.Tag OPC_tag
Where OPC_tag is an OPC tag on the Memory Based OPC Server and is typically
associated with the Confirmation Bar.
2.12.6.2
Processing
The initial start of the Alarm Suspension module analyses the information in the
configuration file and opens one client connection to the Memory Based OPC
Server subscribing to all the OPC Request tags.
When a request is made on any of these tags, it is analysed for proper format and
then processed.
The syntax for a request is:
Rev. 01
Rev. 01
2-68
453-SWD-RMM-0103020
MO-15.98.XX.XX/6XX-020
Pattern State Flags

The Pattern is a text string which is compared to each registered Alarm Server tag.
If the Alarm Sever tag name contains the Pattern, it is subscribed to using a second
OPC connection made to the OPC Alarm Server.
Once all registered Alarm Server tags are checked, the value of the State parameter is written to all of them. Typically State is 0 to disable the alarms and 1 to enable the alarms.
The Flags parameter is a required parameter which contains a space delimited list
of all features that are to be applied to the transaction. If no special features are
desired the Flags can be set to the string None.
Supported features are:
CONFIRM_ACTION,
CONFIRM_ITEM, and
AUTO_ENABLE n.
The CONFIRM_ACTION flag is used once all matching tags are ready to be written, a text string is sent to the Confirmation Bar OPC Tag indicating the executed
request. This confirmation only confirms the action but does not indicated which
alarm tags were affected by the action.
The CONFIRM_ITEM flag is used for each alarm tag that matches the pattern,
the module writes a text string to the Confirmation Bar OPC Tag indicating the
alarm tag that was affected.
The AUTO_ENABLEn flag is used to place the request into a list queue with a
time stamp n minutes from the current time and the state set to 1 (instead of the
typical 0 for disabled). Once the current time reaches the time stamp, the queued
request is processed thus causing the alarms to be re-enabled. This feature is used to
temporarily suspend alarms but automatically re-enabled then after a set time
period.
2.12.6.3
Outputs
The outputs of the Alarm Suspension module are text to the OPC Alarm Server (typically to the Enable property) for the purpose of the disabling and enabling the
Alarm Server tag.
2.12.6.4
Diagnostic
The Alarm Suspension module runs as a stand alone service on the SCC Server.
However for diagnostic purposes the module runs in application mode which provides a GUI interface for troubleshooting monitoring and request testing.
To start the Alarm Suspension Module in application mode, first ensure that the
service version of the Module is stopped (from the Windows Services screen).
NOTE:
Failure to do so can cause unpredictable results since two versions of the module
will try to process the same data.
Once the service version of the Module is stopped, the application version is started
by running the Module with the -dialogue command line parameter. To revert back
to the service version, ensure that the application version IS closed and then re-start
the Module service (from the Windows Services screen).
453-SWD-RMM-0103020
MO-15.98.XX.XX/6XX-020
2-69
Rev. 01
Rev. 01
2.12.7
Disabled Passengers
The disabled passenger module is a combination of a web entry system, SCC GUI
screens and a notification system based on the SCC Server Scheduler.
When a disabled passenger enters the system, the station attendant assists the passenger and then enters the relevant information into the disabled passenger system
using a web interface. This information includes:
The train and car identification that the disabled passenger is on,
The destination station of the disabled passenger, and
The type of disability.
This information is made available for the entire system on corresponding SCC GUI
screens. The CCO operator monitors the flow of disabled passengers through the
system.
Once the train, carrying the disabled passenger, gets close to the destination (typically departs the station before the destination) the SCC Server Scheduler triggers a
notification which tells the station attendant, at the destination station, the incoming
disabled passenger. The provided notification includes the train and car identification as well as the disability type.
After the station attendant at the destination station assists the disabled passenger
from disembarking, the attendant uses the web interface to indicate that the transaction is complete and the corresponding information is removed from the disabled
passenger system.
2.12.7.1
Inputs
The disabled passenger system do not use any configuration style files as input.
Instead the system uses a static preprogrammed web page on the SCC Server which
allows the station attendant to start and end disabled passenger transactions.
The SCC Server receives these user inputs through standard HTML POST requests.
2.12.7.2
Processing
On receiving input from a station attendant about a new disabled passenger, the SCC
Server analyses the input and adds a corresponding entry into the destination disabled passenger file.
The SCC GUI screens use these disabled passenger files to display the current disabled passengers in the system.
In addition, the SCC Server creates corresponding entries in the Scheduler to activate the desired notification system when the disabled passenger's train is one station away from the destination.
Once the Scheduler criteria is met, the Scheduler will activate the notification and
remove the criteria from the Scheduler. This causes the station attendant at the destination station to be notified regarding the disabled passenger. At this stage the notification will have been removed from the Scheduler (this is to ensure that the
notification does not trigger again on the next pass of the train) but the disabled passenger information will still be in the system.
On receiving input from a station attendant about a completed transaction, the SCC
Server analyses the input and removes the corresponding entry from the system.
Rev. 01
Rev. 01
2-70
453-SWD-RMM-0103020
MO-15.98.XX.XX/6XX-020
2.12.7.3
Outputs
Besides the web interface for the station attendant to start and complete disabled
passenger transactions, the output of the disabled passenger system is a notification
to the destination station attendant to indicate that a disabled passenger is arriving.
In addition, the output of the disabled passenger system is flat ASCII text files, one
per station, indicating all the disabled passengers scheduled to arrive at that destination. These files are typically used by the SCC GUI to indicated the flow of disabled
passengers through the system.
2.12.7.4
Diagnostic
The disabled passenger system uses existing components, such as the SCC Core
Web Server and the SCC Scheduler to perform its functionality.
There is no diagnostics for this system beyond that of the components that it uses.
2.12.8
Sounder
The Sounder module is a workstation level module which provides the backbone for
audible alarms. Although the module resides on the server it is executed by the
workstation through a network connection to the server. This allows the EXE to
remain in one location but still allows the workstations to perform the annunciation
as opposed to the server.
2.12.8.1
Inputs
The Sounder do not use any pre-configured input files. All of its parameters are
passed to it using the command line.
There are two different command line syntax for this module. If the Sounder is not
running and thus it is being started, the following syntax is used:
Sounder.exe alarm_wav_file
The alarm_wav_file parameter indicates the location and filename of the alarm
file to be used. The contents of this file are re-read each time annunciation is re-activated. The contents of the file can be altered and the Sounder will utilize the modified version on the start of the next annunciation.
NOTE:
Note that the annunciation already in progress will continue to use the unmodified version until annunciation stops and is restarted.
Once the Sounder is started, successive calls to Sounder provides Sounder with
instructions regarding annunciation. The syntax for this is:
Sounder.exe command
Where command is one of the following possibilities:
STOP,
PLAY,
NUM,
URL param,
FILE param,
SOURCE param,
EXIT, and
453-SWD-RMM-0103020
MO-15.98.XX.XX/6XX-020
2-71
Rev. 01
Rev. 01
END.
The STOP command stops the current looping audio alarm file from being played.
The Sounder remains active waiting for future commands.
The PLAY command starts the playing an endless loop of the currently selected
alarm file. The Sounder remains active waiting for future commands.
The NUM command is an alternative way to start and stop the audio instead of the
PLAY and STOP command. If the value of num is 0 then the STOP command is
executed. If the value of num is greater than 0 then the PLAY command is executed.
The Sounder remains active waiting for future commands.
The URL, FILE and SOURCE commands are aliases for each other and any one of
the can be used to perform the same functionality. These commands change the currently selected wave file. The additional param parameter is the location and
filename of the new alarm WAV file. The Sounder remains active waiting for future
commands.
The Exit and End command are aliases of each other and either can be used to perform the same functionality. These commands stop the current audio and exit the
Sounder program. The Sounder does not remains active and no additional commands can be requested. To use the Sounder again, the Sounder must be restarted
using the initial start syntax above. This command is typically used to shutdown
Sounder.
2.12.8.2
Processing
The initial start of the Sounder perform checks to see the previous instance of
Sounder is running on that computer.
A.
Initial Processing:
The Sounder application does the following processing:
Rev. 01
Rev. 01
The command line is analysed for the alarm wave file and stored for later.
The registry location that Sounder uses to communicate with other instances is
cleared.
This Sounder instance becomes the main instance that will perform all the
annunciation. A timer loop is set up which periodically checks the Sounder
registry that Sounder uses to communicate with other instances.
On each time loop, if the Sounder registry is not empty, then contents of the
registry is processed and then cleared.
If the registry command is a PLAY command (or numeric value greater than 0)
the Sounder generates a copy of a Windows Media Player control and loads it
with the currently selected alarm file. This is necessary because the Windows
Media Player control normally stores the content. If the URL is changed and
then changed back, the control will normally play the stored content. By loading a copy of the control, the control is always forced to re-read the alarm file
and thus, if the alarm file contents are modified, the control always play the latest version of the alarm file.
If the registry command is a STOP command (or numeric value 0) then the current Windows Media Player control is unloaded ensuring that the audio stops
and that the Sounder module does not keep creating more and more control
instances.
2-72
453-SWD-RMM-0103020
MO-15.98.XX.XX/6XX-020
If the registry command is URL, FILE or SOURCE the new alarm file is analysed and stored for the next PLAY based command.
If the registry command is END or EXIT the Sounder application is stopped.
This causes the audio to stop (since there is no application to play it) and it
means no addition commands are processed. The next call to Sounder is interpreted using the initial Sounder syntax.
NOTE:
B.
Care should be taken not to send a PLAY or STOP command after the END or EXIT
command otherwise Sounder will re-start using the PLAY or STOP command as
the alarm wave file (see start-up syntax above).
Subsequent Processing:
If the Sounder is already running then the subsequent call writes the command line
parameters into the registry location used by the Sounder for communication
between instances.
2.12.8.3
Outputs
The output of Sounder is either continuously looping audio or the absence of continuously looping audio (depending on the command that is used).
2.12.8.4
Diagnostics
The Sounder application is intended to run stand alone service on the SCC workstations from the executable file on the server.
The module is run in application mode in which a minimal diagnostic on GUI is provided.
To start the Sounder Module in application mode, first ensure that the service version of the Module is stopped (from the Windows Services screen).
NOTE:
Once the service version of the Module is stopped, the application version is specified by running the Module with the -dialogue command line parameter. To revert
back to the service version, ensure that the application version is closed and then restart the Module service (from the Windows Services screen).
In order to monitor commands sent from subsequent instances of Sounder to the initial Sounder instance, check the following Registry entry:
HKEY_CURRENT_USER\Software\VB and VBA Program Settings\SounderEx\RemoteCommand
This key should be empty because as soon as the initial Sounder instance processes
the command, it is cleared. If this key retains its value for more than a few seconds,
it indicates that the initial Sounder instance is having a problem processing it.
2.12.9
Scheduler (List of Objectives)

The Scheduler module is a key module which assists in a number of processing
tasks. For example, timeout alarms, train service message requests, ATS data
processing for PI, and List of Objectives (LOBJ) is implemented using the Scheduler.
The Scheduler allows the user to specify criteria conditions, which is either time
based or tag based, and execute other applications when the criterias are true.
453-SWD-RMM-0103020
MO-15.98.XX.XX/6XX-020
2-73
Rev. 01
Rev. 01
The Scheduler provides anti-rerun technology to prevent the Scheduler from executing the criteria command multiple times if the criteria remains true for an extended
period of time.
The Scheduler's list of criteria is loaded on start-up but the criteria is added and
removed dynamically when Scheduler is running. To allow a maximum compatibility the criteria list is updated using either OPC or a flat ASCII file placed in the
Scheduler's update directory.
Besides internal command for adding/removing criteria to/from the Scheduler's criteria list, the Scheduler cannot execute any commands (actions) on its own. The
Scheduler has the ability to execute other applications (any application executable
by the OS). This ability with the set of right support application makes the Scheduler
very powerful. For example, with the CommandLineOPC support application the
Scheduler can write OPC tags. With the WriteFile support application, the Scheduler can write files.
The Scheduler contains a number of criteria which monitors the countdown and
dwell stats for the closest train to each station. The first set of criteria uses the WriteFile support program to create PlaceHolder files containing the train data for the PI
module to use (Ref. Para. 2.12.2). The rest of the relevant criteria determine which
messages needs to be played and then uses the CommandLineOPC support application to write the corresponding request to the PI Command OPC tag. In this manner,
although the Scheduler cannot make PI requests directly, it writes to the corresponding OPC command tags which result in the same effect.
In the case of List of Objectives, there are two files created when the operator uses
the LOBJ GUI to create a new LOBJ.
The first file is uses the given LOBJ name with a .txt extension. This file is used
internally by the GUI screen to be able to load existing LOBJ files for editing. The
other file uses the given LOBJ name with a .obj extension. This file is actually a
Scheduler compatible update (.dat) file which can be thrown into the Scheduler
update directory to carry out the List of Objectives. These files should be added
using the Scheduler GUI screen, as it is possible for these List of Objectives to have
a {Choice} place holder which allows the operator to choose some entry as the List
of Objectives is being scheduled.
2.12.9.1
Inputs
The Schedule module uses a connection to both the Memory Based OPC Server as
well as the OPC Alarm Server. In addition it uses a number of configuration files.
Each is detailed below:
Schedule.Dat:
This configuration file is a flat ASCII text file with one entry per line. The file contains the default criteria that the Scheduler starts with. These criteria can then be
increased using either of the dynamic update methods.
There are two types of criteria that the Scheduler supports and each is treated
slightly different: Time Based Criteria and Tag Based Criteria.
A.
Time Based:
Time Based Criteria is evaluated every second and typically has a condition which
checks against the current Date/Time. The syntax for this type of criteria is:
T(identification):Criteria|Command
Rev. 01
Rev. 01
2-74
453-SWD-RMM-0103020
MO-15.98.XX.XX/6XX-020
Or
t(identification):Criteria|Command.
Time Base Criteria always starts with a 'T' or 't' character. The upper case 'T' is used
for the criteria which is permanent and will remain even after the criteria becomes
true. A lower case 't' is used where the criteria is temporary and is removed as soon
as it becomes true.
The identification parameter is optional. It allows a group of commands to be associated with an identification so that the entire group can easily be removed (if necessary).
The criteria parameter indicates the criteria that must become true in order to execute the command. For Time Based Criteria the criteria is typically in the format of:
{DateTime}[?]pattern
Or
{DateTime}[?]{Now+Offset}
The first criteria comp a r e s t h e c u r r e nt d a t e a n d t i m e i n t h e f o r m a t
Y????M??D??(ddd)h??m??s??_HOLIDAY.
(for example, Y2011M11D02(WED)h14m35s25_REGULAR).
The [?] is the operand for collecting the required information. Thus if the pattern
parameter appears anywhere in the current data and time then the command will be
executed.
The second syntax compares the current time and date to the keyword Now with a
possible offset. This is used to schedule events a number of seconds after they are
added to the Scheduler. This is used to implement Timeout timers. For example, a
command is sent to a device. A criteria can be added to the Scheduler, using the
Now keyword, to raise an alarm in 30 seconds. A second criteria can be added to
the Scheduler which removes these two items from the Scheduler if the corresponding status for the device changes state. In this manner, if the device changes state the
criteria are removed from the Scheduler and no alarm is raised. If the device does
not change state in the specified 30 seconds, the Scheduler will trip the Now+30 criteria and raise an alarm.
Although Time Based Criteria normally compares against the current date and time,
the criteria can use any of the regular criteria operands.
B.
Tag Based:
Tag Based Criteria is evaluated when any of its Tag changes state. This immediately
imposes one requirement for Tag Based Criteria: the criteria must make reference to
at least one tag. The syntax for this type of criteria is:
C(identification):Criteria|Command
Or
c(identification):Criteria|Command
Tag Base Criteria always starts with a 'C' or 'c' character (for tag 'change'). The upper
case 'C' is used when the criteria is permanent and will remain even after the criteria
becomes true. The lower case 'c' is used where the criteria is temporary and will be
removed as soon as it becomes true.
453-SWD-RMM-0103020
MO-15.98.XX.XX/6XX-020
2-75
Rev. 01
Rev. 01
The identification parameter is optional. It allows a group of commands to be associated with an identification so that the entire group can easily be removed (if necessary).
The criteria parameter indicates the criteria that must become true in order to execute the command.
Values in expression are written directly. Tags in expressions are surrounded by
brace brackets {opc_server_name#opc_tag}. Where the # character is a constant
character used to separate the server and tag portion of the OPC tag. Operators are
always surrounded by square brackets. For Valid operators (Ref. Table 2-1).
OPERATORS
FUNCTION
[+]
Adds the value before the operator to the value after the operator
[-]
Subtracts the value after the operator from the value before the
operator
[*] or [x]
Multiplies the value before the operator with the value after the
operator
[/]
Divides the value before the operator by the value after the operator
[%]
Returns the modulus of the division of the value before the operator
by the value after the operator
[&]
Returns the bitwise AND of the value before the operator and the
value after the operator
[&^]
Returns the bitwise AND of the value before the operator and the
value of the bit position specified by the value after the operator
[|]
Returns the bitwise OR of the value before the operator and the
value after the operator
[<<]
Returns the value of a bitwise right-to-left shift of the value before

the operator by the number of bits specified after the operator
[>>]
Returns the value of a bitwise left-to-right shift of the value before

the operator by the number of bits specified after the operator
(inserting 0s)
[!]
Returns T if F else F
[?]
Returns T if the parameter after the operator is contained in the

parameter before the operator.
[@]
Returns T if the parameter before the operator is found in the criteria

list (checking both the Time Based and Tag Base criteria)
[R]
Returns a number of characters specified by the value after the operator from the end (right side) of the parameter before the operator.
[L]
Returns a number of characters specified by the value after the operator from the start (left side) of the parameter before the operator.
[M]
Returns all characters from the parameter before the operator starting (middle position) from the character specified by the value after
the operator
[<]
Returns a numeric Boolean indicating if the value before the operator

is smaller than the value after the operator. Numeric comparison. For
Text comparison use [T<]
[<=]

is smaller or equal to the value after the operator. Numeric comparison. For Text comparison use [T<=]
Table 2-1. List of Operators

Rev. 01
Rev. 01
2-76
453-SWD-RMM-0103020
MO-15.98.XX.XX/6XX-020
OPERATORS
FUNCTION
[=]

is equal to the value after the operator. Numeric comparison. For
Text comparison use [T=]
[!=]

is not equal to the value after the operator. Numeric comparison. For
Text comparison use [T!=]
[>]

is greater than the value after the operator. Numeric comparison. For
Text comparison use [T>]
[>=]

is greater or equal to the value after the operator. Numeric comparison. For Text comparison use [T>=]
[Change]
Returns T. Typically used with Tag Base Criteria to execute the command each time the tag changes. Since Tag Based Criteria are only
evaluated when the tag changes using a criteria that is always true
will cause the criteria to always be true and thus the command will
execute each time the tag changes
[AND]
Logical AND. True (T) if the condition before and the condition after
are true.
[OR]
Logical OR. True (T) is the condition before or the condition after (or
both) are true.
Table 2-1. List of Operators

For example, criteria for checking countdown is:
{ICONICS.SimulatorOPCDA.2#ATS_Station1_Train1_Coundown}[<]30
To prevent Anti-rerun processing, such as when the criteria is based on [Change],
the criteria can be preceded by a $. This must appear as the first character of the criteria.
The command portion of the syntax, for both Time Based and Tag Based criteria, is
either an internal command preceded by the number character (#) or the location,
filename and parameters (if any) to an application which is executed by the OS. This
application does not require any direct user GUI input (although it can use input
files), since the Scheduler runs on the SCC Server which is not visible to the operators.
The following internal commands are supported:
ADD criteria_entry,
REMOVE identification,
DUMP,
RESET,
EXIT, and
DEBUG msg.
The ADD internal command allows the addition of a criteria entry to the criteria list.
The parameter use the exact same format as the Schedule.Dat file.
453-SWD-RMM-0103020
MO-15.98.XX.XX/6XX-020
2-77
Rev. 01
Rev. 01
The REMOVE internal command allows the removal of criteria entries from the criteria list. Any entry which contains the identification parameter anywhere in the
entry is removed. It Includes both Tag and Time Based criteria entries.
The DUMP internal command writes the current Time and Tag Base criteria to a txt
file in the same directory as the Scheduler. The name of the file is always Schedule.txt. This command allows other processes to query the criteria list that the
Scheduler is using.
The RESET internal command resets all anti re-run flags.
The EXIT internal command ends the execution of the Scheduler. Once closed, the
Scheduler cannot be restarted through the criteria, the update OPC tag or the update
directory since the Scheduler is not running. In such a case the Scheduler executable
must be re-executed to restart the Scheduler.
The DEBUG internal command is used to test criteria. Instead of executing some
remote application the Scheduler generates a popup which echoes any parameters
provided to it. This internal command is not used for service criteria since the
Scheduler is running on the SCC Server which operators do not have access to
accept the popup messages. If a criteria is not performing as desired, the command
can be replaced temporarily with the DEBUG internal command to help diagnose if
the problem is a criteria issue or a command issue.
Schedule.Holiday.Dat
This is a flat ASCII text file with one entry per line. The file is used to indicate
which days are considered as holiday.
The Scheduler uses this information to determine if the current day is suffixed with
_REGULAR or _HOLIDAY.
This allows criteria based on dates and/or time to be different depending on the day
is a regular day or a holiday. The format for the file is:
C.
Date Comment
The date is in YYYY.MM.DD format and is followed by a space and then a comment indicating which holiday the date refers to.
Only holidays are entered into this file. All dates not listed are assumed to be regular
days. Typically it is not necessary to list Saturdays and Sundays in this file since the
day of the week is provided as a three letter code in the data time format.
D.
OPC Servers:
The Scheduler identifies the OPC Server directly in its configuration file (Schedule.Dat). This allows the Scheduler to be used with any number of OPC Servers
including the Memory Based OPC Server and the OPC Alarm Server.
These servers are inputs to the Scheduler allowing the Scheduler to evaluate the Tag
Based criteria when any of the subscribed tags on these servers change.
2.12.9.2
Processing
There are three different independent processing streams:
Rev. 01
Rev. 01
Time Base Criteria,

Tag Based Criteria, and
Update. Each is discussed below:
2-78
453-SWD-RMM-0103020
MO-15.98.XX.XX/6XX-020
A.
Time Based Criteria:
The Scheduler sets up a timer that fires at a minimum rate of one per second.
When the timer trips, the Scheduler evaluates each Time Base Criteria to see if any
are true. For each criteria that is not true, the Scheduler resets the criteria's anti rerun flag thus allowing it to be re-run when the criteria changes to true again. For
each criteria that is true, the corresponding command is executed if the anti re-run
flag is not set. If the flag is set, then the criteria's command is already been executed
(on a previous pass) and thus the criteria first changes back to false before it can be
re-run.
If the criteria is true and the anti re-run flag is not set, the Scheduler sets it unless the
criteria starts with the dollar sign character ($) which indicates that anti re-run technology should not be use for that criteria.
If the command is an internal command, it is processed by the Scheduler by passing
it to the same function that handles updates through OPC Tags and/or files in the
update directory. In this manner any changes to these internal commands are applied
to all instances of the commands.
B.
Tag Based Criteria
The Scheduler subscribes to all the OPC server/tags in its Schedule.Dat file.
When any of these tags change, the corresponding OPC Server sends a notification
to the Scheduler and the Scheduler runs through all its Tag Based criteria looking for
any criteria that contains that particular tag. All criteria which contain that tag are
evaluated to see if the new values changes the criteria state.
If the criteria is false then the criterias anti-rerun flag is cleared allowing the criteria
to execute its command when it becomes true again.
If the criteria is true but the anti re-run flag is set, no action is take since the command has already been executed.
If the criteria is true and the anti re-run flag is not set, the corresponding command
is executed.
If the criteria is true and the anti re-run flag is not set, the Scheduler sets it unless the
criteria starts with a dollar sign character ($) which indicates that anti re-run technology should not be use for that criteria.
NOTE:
C.
When the criteria is added through the update method (see below) any new OPC
tags are not subscribed to. As a result all tags, potential or not, must be specified
in the Schedule.Dat file.
State Tracking
In order to be able to re-start the Scheduler in the last known state (if desired), the
Scheduler dumps its current state, each time the state changes, to a file called
Scheduler_Service.State.Dat. This file is used as the initial input file to Scheduler
to re-start the Scheduler in the last known state. Care must be taken when doing this
because the Scheduler could have pending instructions which may not longer be
desirable.
By making the Scheduler start up with this DAT file, the Scheduler is made to automatically use the last saved state as the re-start state for the Scheduler.
453-SWD-RMM-0103020
MO-15.98.XX.XX/6XX-020
2-79
Rev. 01
Rev. 01
D.
Remote Command Processing
The Scheduler's criteria list is changed dynamically by either sending update commands through an OPC tag or by placing an update file into the updates directory of
the Scheduler. All three update methods (internal command, update via OPC tag,
update via update file) are sent to the same processor function:
ADD command is processed by stripping off the 'ADD' and placing the rest into
either the Time Base or Tag based criteria list. Any OPC tags introduced in this manner are not re-subscribed, so the tags used in dynamic ADD commands must be tags
which were already subscribed in the initial Schedule.Dat file. If necessary dummy
entries need to be added into the Scheduler.Dat file for any tags that may be added as
part of dynamically added criteria.
REMOVE command is processed by searching each Time Based and Tag Base criteria for the presence of the supplied pattern. Each criterion that includes the pattern
is removed. Multiple criteria entries, which serve a common purpose, are added in
with the same identification. Later, by using the identification with the REMOVE
command, the entire group of criteria entries is removed.
DUMP command is processed by opening the Schedule.txt file in the Scheduler
directory and writing the contents of the Time Based and Tag Based criteria lists to
the file. Any previous contents are overwritten. The content of the txt file is a
comma delimited text file, one line per criteria entry, which contains a more readable version of the criteria file. This file is processed by other processes to determine
the Scheduler's current criteria.
RESET command is processed by clearing all the Time Based and Tag Based flags.
EXIT command is processed by closing the Scheduler.
DEBUG command is processed by displaying a popup containing the contents of
the command parameters.
2.12.9.3
Outputs
The output of the Scheduler is either internal commands typically used to modify
the criteria list or execution of external commands/applications. These external
commands/applications should not have any GUI user input since the Scheduler is
designed to run on the SCC Server without any operator supervision.
The OPC Server to which the Scheduler subscribes, its output is also the same OPC
server since the OPC protocol is bidirectional but this is only at the lower processing
level as opposed to the module data flow level.
2.12.9.4
Diagnostics
The Scheduler is intended to run on the SCC Server as a stand alone service module.
For diagnostic purposes, the module runs in application mode in which it provides a
GUI for some basic troubleshooting information regarding the state of the scheduler.
The bottom of the GUI has to LEDs which indicate the connection status to the two
OPC Servers (Memory Based and Alarm Server). When these LED are in red, a connection to the respective OPC Server cannot be established. When the LED is in
green, a connection to the respective OPC Server is successfully established.
The two list panels hold the Time Based (on left) and Tag Based (on right) criteria.
The processing of the Scheduler is traced by creating the existence of the Scheduler.Log file. When this file exists, the Scheduler writes out information about its
Rev. 01
Rev. 01
2-80
453-SWD-RMM-0103020
MO-15.98.XX.XX/6XX-020
453-SCC-02-005
Figure 2-8. Scheduler

453-SWD-RMM-0103020
MO-15.98.XX.XX/6XX-020
2-81
Rev. 01
Rev. 01
processing to this file. This file is created or deleted on the fly while Scheduler is
running.
To start the Scheduler Module in application mode, first ensure that the service version of the Module is stopped (from the Windows Services screen).
NOTE:
Once the service version of the Module is stopped, the application version is specified by running the Module with the -dialogue command line parameter. To revert
back to the service version, ensure that the application version is closed and then restart the Module service (from the Windows Services screen).
2.13
SCC HOST APPLICATIONS

The SCC workstations acts as a host for applications that are not a part of the SCC
but they run on the SCC Workstations to provide an integrated look and feel without
true integration into the SCC.
2.13.1
Radio Interface
The Radio interface provided by Wave Twist Pair Solutions, is a stand alone application running on a Java platform on the SCC Workstation which provides the operator with access to radio functionality. Although the SCC Workstation provides the
Java environment to run this application the application runs independently of the
SCC Visualization.
2.13.1.1
Inputs
The Radio Interface module takes the Wave Engine server as an input.
2.13.1.2
Processing
The Radio Interface performs the various GUI functions by interfacing to the Wave
Engine server using the Wave Java-based SDK.
2.13.1.3
Outputs
The output of the Radio interface is requests to the Wave Engine for processing
Radio related functionality.
2.13.2
VORS Interface
The VORS Interface module provides a GUI interface to train related calls, PA and
PI functionality. The VORS Interface is an application which resides on the SCC
Workstations allowing the GUI to be shown and hidden based on the SCC Workstation functionality but otherwise runs independent of the SCC Visualization. The
GUI is maintained as part of the on-board communication equipment and thus the
details are beyond the scope of this document.
2.13.2.1
Inputs
The VORS GUI takes inputs from the VORS Wayside Server and can establish
direct communication to devices on the vehicle for the purpose of implementing
audio communication.
Rev. 01
Rev. 01
2-82
453-SWD-RMM-0103020
MO-15.98.XX.XX/6XX-020
2.13.2.2
Processing
The VORS GUI processes instructs to show, hide and switch pages based on OPC
tags sent from SCC Server to the VORS Wayside Server. These tags are set directly
on the VORS Wayside Server through the SCC Gen Broker data collector.
2.13.2.3
Outputs
The VORS GUI provides a GUI interface for requesting and seeing the status of the
train communication equipment. The VORS Wayside Server provides status information, in the way of OPC tags, which the SCC Server can read to determine the status of train calling devices.
2.14
SCHEDULER SUPPORT APPLICATIONS

A number of small applications are developed for trouble shooting purpose and/or to
allow the Scheduler to perform various tasks. These applications are provided input
through the command line (with no user GUI), execute a task and then exit.
Although the Scheduler runs any application, the following is a list of applications
specifically designed for use with the Scheduler:
2.14.1
Command Line OPC

The CommandLineOPC application is used to set OPC tags. Although it also supports options for reading tags and listing OPC servers, only the write function is
used with the Scheduler.
2.14.1.1
Inputs
The ComandLineOPC application takes the following command line syntax:
W OPC_Server_Name OPC_Server_Tag Value
Or
w OPC_Server_Name OPC_Server_Tag Value
Where W is a constant letter indicating a write function. The case of the letter indicates if the CommandLineOPC application waits to get feedback from the OPC
Server regarding the write or if it exits as soon as it sends the OPC write request.
The OPC_Server_Name parameter indicates the name of the OPC Server on
which the desired OPC tags exists.
The OPC_Server_Tag parameter indicates the name of the OPC tag to which the
desired value will be written.
The Value parameter indicates the string or number to be written to the indicated
tag.
2.14.1.2
Processing
The CommandLineOPC application analyses the write instruction, connects to the
server and subscribes to the indicated tag.
Depending on the case of the W directive, processing ends immediately after the
OPC request has been made or after an OPC Server notification that the tag changed
to the desired value.
453-SWD-RMM-0103020
MO-15.98.XX.XX/6XX-020
2-83
Rev. 01
Rev. 01
A timeout timer is to close the application within 10 seconds. This is used so that
failures to connect to the OPC Server or failures to write to the tag do not cause
CommandLineOPC to continue running in the background.
2.14.1.3
Outputs
The output of the CommandLineOPC application is a text of the indicated value to
the OPC tag on the OPC server.
2.14.2
WriteFile
The WriteFile application is used by the Scheduler to create Place Holder files use
by the PA and PI Interface modules.
The WriteFile application supports Appending, Overwriting, Reading, Deleting and
Sorting.
2.14.2.1
Inputs
All parameters are provided to this application through command line parameters.
The syntax for this application is:
{A|W|R|D|S} FileName Entry
Where {A|W|R|D|S} represents a single letter command (A=Append, W=Write,
R=Read, D=Delete Entry, S=Sort).
The FileName parameter is used to determine to which file the WriteFile command should be applied. For the A and W commands, if the filename does not exists
then it is created. For the R and S command, the specified file should exits otherwise
the command cannot be carried out.
The Entry parameter is only applicable for the A, W and D commands and indicates the text to be written (A and W) or the pattern to be deleted (D). The Entry
parameter are surrounded by quotes (") if it contains spaces.
2.14.2.2
Processing
A.
Write Commands (A and W):
If the command is A, the indicated file is opened for appending.

If the command is W, the indicated file is opened for writing.
The content of the Entry parameter is then written to the file. Normally new line
characters cannot be written to the file, but when using the append command, the
appended entry is place on the successive line. This allows multiple lines entries to
be made into the desired file. The file is automatically closed after writing.
B.
Read Commands (R):
The read command opens the specified file for reading. The first line from the file is
read. The read command is limited to read only the first entry in the file.
If the result is text then it is displayed in a pop-up dialogue box. If the result is
numeric it is returned as the exit code of the function thus allowing it to be read in a
batch file using the %errorlevel% parameter.
C.
Delete Entry Commands (D):
The indicted file is opened for reading. A file with the same filename but appended
with .new is opened for writing. The contents of the indicated file is copied into
Rev. 01
Rev. 01
2-84
453-SWD-RMM-0103020
MO-15.98.XX.XX/6XX-020
the new file as long as the line does not contain the pattern indicted by the Entry
parameter. The indicated file is deleted and the new file is renamed to remove the
.new.
The result is that the indicated file has all its entries except for those that matched the
pattern.
D.
Sort Commands (S):
Each line in the indicated file is read and placed into a list box with the sorted property set to true. Thus as each entry is added the list sorts it and the result is a list with
all the entries sorted.
The results are then written back to the indicated file (overwriting original contents).
Since the list box has sorted the list, the new version of the file contains the sorted
list.
2.14.2.3
Outputs
The output of the WriteFile application is a file with the specified command applied
to it.
2.14.3
ModbusMsg
The ModbusMsg application is used to send a Modbus message to a Modbus Server.
This application does not collect the results of the Modbus exchange it is only practical for setting Modbus Server values (not reading them).
2.14.3.1
Inputs
The ModbusMsg has two different syntaxes that it can use:
ByteStream, and
RegisterWrite.
Both syntaxes start with the IP address of the Modbus Server and the port. The specified port for Modbus protocols specified is 502, the port still needs to be indicated
as the ModbusMsg can send its messages to other ports in case an alternate port is
being used.
In the Byte Stream version, the port followed by a hex stream indicates the bytes to
be sent. In this case the entire message including the TCP/IP Modbus header (trans
ID, protocol and length) is included.
In the RegisterWrite version the port is followed by the Register and the Value.
NOTE:
The Register value should be a Holding Register such as 40001 as opposed to the
corresponding Modbus address 0. The Modbus protocol specifies that Holding
Registers start with 40001 not 40000. The Modbus protocol address 0 refers to
Holding Register 40001.
The register should be followed by a space and then followed by the value to be
written to the register. The value should be between 0 and 65535.
2.14.3.2
Processing
The application makes a connection to the Modbus Server specified at the indicated
IP address on the specified port.
If a hex byte stream is provided as the command line parameter then it is converted
to a byte array and send out as-is.
453-SWD-RMM-0103020
MO-15.98.XX.XX/6XX-020
2-85
Rev. 01
Rev. 01
If a register and value is provided as the command line parameter then the corresponding byte array is constructed and sent out.
The send progress is monitored until the Modbus Server has received the message
(typically almost instantly) and then the connection is disconnected and the application ends.
2.14.3.3
Outputs
The application outputs is a request to the indicated Modbus Sever device on the
indicated port.
2.14.4
TCPMsg
TCPMsg is to connect to a TCP/IP server, send a message and disconnect. It can be
used by the Scheduler to control application and/or modules which provide remote
control via TCP/IP. The CCTV Visualization control, for example, provides remote
control access through TCP/IP messages.
2.14.4.1
Inputs
The inputs to the application are in the form of command line parameters. The syntax for this application is:
IP_Addr Port Message
The IP_Addr is the IP address of the TCP Server to which the message is sent.
The Port is the Port on which the TCP Server is listening.
The Message is the string to be sent to the TCP Server.
2.14.4.2
Processing
The application connects to the specified IP address on the specified port. It sends
the contents of the Message parameter to the server.
Once the monitored send progress indicated that the server has received the message, the connection to the server is closed and the application exits.
2.14.4.3
Outputs
The output of the application is a TCP/IP connection and message to the indicated
server on the indicated port.
2.14.5
SendMail
The SendMail application uses a third party SNTP server to send e-mail messages.
2.14.5.1
Inputs
The SendMail application uses a Config.txt file for input. This is a flat ASCII text
file which has the same format as use by the other modules. The key/value pairs
used by SendMail are:
SMTP.Server SMTP_Server_Name,
SMTP.Server.Authentication Setting,
SMTP.Server.User User,
SMTP.Server.Password User_Password,
Rev. 01
Rev. 01
2-86
453-SWD-RMM-0103020
MO-15.98.XX.XX/6XX-020
SMTP.Server.SSL Setting,
SMTP.Server.Charset Charset, and
SMTP.Server.Sender Sender_Email.
The first key/value pair indicates the SMTP server to be used.

The second key/value pair indicates if authentication is used (0=No, 1=Yes).
The next two key/value pairs is for defining the user and password on the
SMTP server.
WARNING: THE PASSWORD IS NOT ENCRYPTED. USE AN ACCOUNT SPECIFICALLY FOR THIS PURPOSE - NOT A PERSONAL ACCOUNT.
The next key/value pair indicates if SSL is used (0=No, 1=Yes).

The next key/value pair indicates the character set to be used where the Charset
parameter is a string containing of the of the supported character sets.
The last key/value pair indicates the e-mail address that the SendMail application should use as the reply address.
The command line parameters define the actual message to be sent. The syntax is:
Destination Subject Message
Where Destination is the email account to which the message should be sent, Subject is shown on the subject line and the last parameter is the message. Always surround the contents of Subject and Message with quotes (").
2.14.5.2
Processing
On execution the application reads the SMTP related parameters from the Config.Txt file. It uses those parameters to set up a connection to the SMTP server (and
authenticate it).
Parsing the command line parameters the application constructs the necessary
SMTP message and sends it to the server for processing. Once the message is sent,
the connection to the SMTP server is closed and the application ends.
NOTE:
2.14.5.3
The speed of actually processing the request and sending it to the destination
depends on the SMTP server. It can take seconds, minutes or longer. This is not a
fault of the SendMail application, it is a setting of the SMTP server.
Outputs
The output of the SendMail application is a request to the SMTP server to process
the provided e-mail message.
453-SWD-RMM-0103020
MO-15.98.XX.XX/6XX-020
2-87
Rev. 01
Rev. 01
Rev. 01
Rev. 01
2-88
453-SWD-RMM-0103020
MO-15.98.XX.XX/6XX-020

CONFIGURATION
SECTION 3 - TROUBLESHOOTING
3.1
SAFETY PRECAUTIONS
The front matter of this manual contains a list of general safety precautions. Before
attempting any troubleshooting tasks, read and understand these precautions. Failure to do so can result in damage to equipment. If in doubt regarding any of these
precautions, ask for an explanation from your immediate supervisor before proceeding with any troubleshooting task.
3.2
SYSTEM TROUBLESHOOTING (Ref. Tables 3-1 to 3-5)

Troubleshooting procedures are provided in the following table(s). Each table
describes the fault symptom, the probable cause of the malfunction, and the
recommended action to correct the fault.
The troubleshooting tables assist the operator and maintenance person in restoring
the SCC to its operational status.
SYMPTOM
Faulty Power Supply
PROBABLE CAUSE
1.
Improper power supply.
2.
TBD
Damaged Power Cable.
TBD
RECOMMENDED ACTION
1.
Check for proper power

cable connection from the
PDU.
2.
If necessary, Install new

power cable.
Install new power cable.

TBD
Table 3-1. Power Supply Module Troubleshooting
SYMPTOM
Faulty Fan run
PROBABLE CAUSE
1.
2.
TBD
Presence of debris or
dirt.
TBD
RECOMMENDED ACTION
1.
Check for the harness and

power supply to the fan
module.
2.

fan Module,
1.
clean the debris or dirt and

re-install the fan module
2.

fan Module,
TBD
Table 3-2. Fan Module Troubleshooting
453-SWD-RMM-0103020
MO-15.98.XX.XX/6XX-020
3-1
Rev. 01
Rev. 01
SYMPTOM
PROBABLE CAUSE
TBD
TBD
RECOMMENDED ACTION
TBD
Table 3-3. Input/Output Module Troubleshooting
SYMPTOM
PROBABLE CAUSE
Faulty Cabinet Light
1.
2.
TBD
Damaged cabinet light.
TBD
RECOMMENDED ACTION
1.
Check for proper power

cable connection from the
PDU.
2.

cabinet light.
Install new cabinet light.

TBD
Table 3-4. Cabinet Assembly Troubleshooting
SYMPTOM
TBD
PROBABLE CAUSE
TBD
RECOMMENDED ACTION
TBD
Table 3-5. Software Troubleshooting
Rev. 01
Rev. 01
3-2
453-SWD-RMM-0103020
MO-15.98.XX.XX/6XX-020

CONFIGURATION
SECTION 4 - CORRECTIVE MAINTENANCE
4.1
SAFETY PRECAUTIONS
attempting any maintenance or troubleshooting tasks, read and understand these
precautions. Failure to do so can result in serious injury to individuals or damage to
equipment. If in doubt regarding any of these precautions, ask for an explanation
from your immediate supervisor before proceeding with any maintenance task.
WARNING: WEAR THE WRIST GROUNDING STRAP BEFORE ATTEMPTING THE
REMOVAL AND INSTALLATION OF ANY OF THE SCC COMPONENTS.
FAILING TO DO SO CAN CAUSE INJURY TO PERSONNEL AND/OR
DAMAGE THE ELECTRICAL COMPONENTS.
WARNING: AN ENERGY HAZARD WILL EXIST IF THE SAFETY GROUND CABLE IS
OMITTED OR DISCONNECTED.
WARNING: THE SYSTEM CHASSIS MUST BE POSITIVELY GROUNDED TO THE
RACK CABINET FRAME. DO NOT ATTEMPT TO CONNECT POWER TO
THE SYSTEM UNTIL GROUNDING CABLES ARE CONNECTED.
CAUTION:
4.2
A qualified electrician must perform all connections to DC power

and safety grounds. The system must be safely grounded at the cabinet frame. All electrical wiring must comply with applicable local
or national codes and practices.
TORQUE VALUES
Specific torque values are provided within the individual procedures. Refer to the
front matter of this manual for standard torque values.
4.3
SPECIAL TOOLS AND TEST EQUIPMENT

Wrist Grounding Strap.
4.4
HALF BLADE
4.4.1
Removal and Installation (Ref. Fig. 4-1)

A.
Removal
(1)
Turn OFF the half blade (3).
(2)
Make sure that the blades power is off.
NOTE:
When a blade is powered off, its front-panel power indicator is off.
(3)
Press and hold the release button (2) on the blade handle (1).
(4)
Slide the blade out of the enclosure form the guide rail (4).
453-SWD-RMM-0103020
MO-15.98.XX.XX/6XX-020
4-1
Rev. 01
Rev. 01
1.
2.
3.
4.
5.
BLADE HANDLE
RELEASE BUTTON
HALF BLADE
GUIDE RAIL ON ENCLOSURE
GUIE RAIL ON BLADE
Figure 4-1. Half Blade

Rev. 01
Rev. 01
4-2
453-SWD-RMM-0103020
MO-15.98.XX.XX/6XX-020
CAUTION:
B.
IF THE SYSTEM IS OPERATED FOR EXTENDED PERIOD OF TIME

WITHOUT A BLADE BLANK INSTALLED, IT CAN CAUSE THE ENCLOSURE TO OVERHEAT.
(5)
Install the blade blank(s).
(6)
Install the covers over the I/O connector pins.
Installation
(1)
Remove the covers from the I/O connector pins.
(2)
Remove the blade blank(s).
(3)
Orient the blade so that the blade handle (1) is on the left side of the half
blade (3).
NOTES:
1.
To install a half blade (3) in bays 1 through 8, align the guide rail (4) on the
upper edge of the blade so that the rail fits between the plastic guides on
the enclosure.
2.
To install a half blade (3) in bays 9 through 16, align the edge of the blade
with the guide rail (4) on the floor of the Server enclosure.
(4)
Slide the half blade (3) into the enclosure until the blade handle (1)
engages and locks the blade in place.
(5)
Turn ON the half blade (3).
4.5
FULL BLADE
4.5.1

A.
Removal
(1)
Turn OFF the full blade (6).
(2)
Make Sure that the blade's power supply is OFF.
(3)
Press and hold the release button (2) on the blade handle (1).
(4)
Slide the blade out of the enclosure from the guide rail (4).
CAUTION:
B.
OPERATING THE SYSTEM FOR EXTENDED PERIODS OF TIME WITHOUT A BLADE BLANK INSTALLED CAN CAUSE THE ENCLOSURE TO
OVERHEAT.
(5)
Install the blade blank(s).
(6)
Install the covers on the I/O connector pins.
Installation
(1)
Remove the covers from the I/O connector pins.
(2)
Remove the blade blank(s).
(3)
Orient the blade so that the blade handle (1) is on the left side of the half
blade (3).
NOTE:
To install a full blade (6) in bays 1 through 8, align the guide rail (4) on the upper
edge of the blade so that the rail fits between the plastic guides on the enclosure.
(4)
453-SWD-RMM-0103020
MO-15.98.XX.XX/6XX-020
Slide the full blade (6) into the enclosure until the blade handle (1)
engages and locks the blade in place.
4-3
Rev. 01
Rev. 01
1.
2.
3.
4.
5.
BLADE HANDLE
RELEASE BUTTON
FULL BLADE
GUIDE RAIL ON ENCLOSURE
GUIE RAIL ON BLADE
Figure 4-2. Full Blade

Rev. 01
Rev. 01
4-4
453-SWD-RMM-0103020
MO-15.98.XX.XX/6XX-020
(5)
Turn ON the full blade (6).
4.6
AC Power Supply
4.6.1

A.
Removal
NOTE:
(1)
Release the retention clip (4) and retention clip tether (2) from the
power cable (5) and disconnect the power cable (5) from the power
supply module (1).
(2)
Press down on the power supply module release button (6) on the handle (3).
(3)
Rotate the power supply module handle (3) down to eject the power
supply module (1).
(4)
Slide the power supply module (1) out of the enclosure.
(5)
Install the blank on the enclosure.
NOTE:
B.
The power supply modules are hot-swappable. Remove and replace only one
power supply module at a time in a system that is turned on.
Empty power supply bays must be blanked to maintain proper cooling in the enclosure.
Installation
(1)
Ensure that the power supply module handle (3) is fully open and the
power cable (5) is not connected to the electrical power supply.
(2)
Remove the blank from the enclosure.
(3)
Slide the power supply module (1) into the enclosure.
(4)
Rotate the power supply module handle (3) upward until it latches.
(5)
Plug a power cable (5) into the power supply module (1).
(6)
Secure the cable to the power supply with the retention clip (4) and fit
the retention clip tether (2) into the notch in the power supply handle
(3).
4.7
FAN MODULE
4.7.1

A.
Removal
WARNING: DO NOT OPERATE THE SYSTEM WITHOUT THE COOLING FANS.

CAUTION:
(1)
NOTE:
Care must be taken while handling the fan module to prevent damage to the connector.
Locate and Identify the failed system fan module (1).
Use the back-panel fan module indicators to identify the failed system.
(2)
Press the fan module release button (2).
(3)
Slide the fan module (1) out of the enclosure.
(4)
Install the blank on the enclosure.
453-SWD-RMM-0103020
MO-15.98.XX.XX/6XX-020
4-5
Rev. 01
Rev. 01
1.
2.
3.
4.
5.
6.
POWER SUPPLY
RETENTION CLIP TETHER
NOTCH IN POWER SUPPLY HANDLE
RETENTION CLIP
POWER CABLE
RELEASE BUTTON
Rev. 01
Rev. 01
4-6
453-SCC-02-008
1
3
Figure 4-3. AC Power Supply
453-SWD-RMM-0103020
MO-15.98.XX.XX/6XX-020
1.
2.
FAN MODULE
RELEASE BUTTON
Figure 4-4. Fan Module

453-SWD-RMM-0103020
MO-15.98.XX.XX/6XX-020
4-7
Rev. 01
Rev. 01
B.
Installation
(1)
Remove the blank from the enclosure.
(2)
Inspect the fan for debris before installing the fan in the enclosure.
(3)
Slide the fan module (1) into the enclosure until it is fully seated and
the release button (2) engages.
4.8
I/O MODULE
4.8.1

A.
Removal
CAUTION:
(1)
NOTE:
B.
Make sure that the cable enumerators are installed.

Cable enumerators assisted during the time of installation of the I/O modules.
(2)
Disconnect the cables attached to the I/O module (2).
(3)
Lift the latch (3) on the end of the module handle (4) and rotate the handle (4) away from the module (2).
(4)
Slide the I/O module (2) out of the enclosure.
(5)
Install the I/O connector cover (1).
Installation
(1)
Remove the I/O connector cover (1) from the back of the module (2).
(2)
Lift the handle release latch (3) and open the I/O module handle (4).
(3)
Slide the module (2) into the enclosure.
NOTE:
The I/O module must be installed in the appropriate I/O bay.
(4)
Close the handle (4) until it secures the module (2) in place and is fully
seated.
(5)
Connect all of the cables attached to the I/O module (2).
NOTE:
Rev. 01
Rev. 01
IF AN I/O MODULE IS REMOVED, IT MUST BE REPLACED WITH

ANOTHER I/O MODULE OR WITH A FILLER BLANK TO MAINTAIN
COOLING THROUGH THE SYSTEM ENCLOSURE.
A matching fabric mezzanine card must be installed in one or more blades to support the new I/O module. If necessary, install the mezzanine card(s).
4-8
453-SWD-RMM-0103020
MO-15.98.XX.XX/6XX-020
1.
2.
3.
4.
I/O CONNECTOR COVER

I/O MODULE
RELEASE LATCH
HANDLE
Figure 4-5. I/O Module

453-SWD-RMM-0103020
MO-15.98.XX.XX/6XX-020
4-9
Rev. 01
Rev. 01
Rev. 01
Rev. 01
4-10
453-SWD-RMM-0103020
MO-15.98.XX.XX/6XX-020

CONFIGURATION
SECTION 5 - REFERENCES
5.1
DOCUMENTATION (Ref. Table 5-1)

The documentation listed in the following table supports the text of this manual.
DOCUMENT SUPPLIER
Dell
DOCUMENT TITLE
Dell PowerEdge M1000e Enclosure Owners Manual
Table 5-1. Reference Documentation
453-SWD-RMM-0103020
MO-15.98.XX.XX/6XX-020
5-1
Rev. 01
Rev. 01
Rev. 01
Rev. 01
5-2
453-SWD-RMM-0103020
MO-15.98.XX.XX/6XX-020

CONFIGURATION
SECTION 6 - PREVENTIVE MAINTENANCE
6.1
SAFETY PRECAUTIONS
attempting any maintenance or troubleshooting tasks, read and understand these
precautions. Failure to do so can result in serious injury to individuals or damage to
equipment. If in doubt regarding any of these precautions, ask for an explanation
from your immediate supervisor before proceeding with any maintenance task.
6.2
PREVENTIVE MAINTENANCE SCHEDULE (Ref. Table 6-1 and 6-2)

Preventive Maintenance (PM) of the SCC Integration and Configuration comprises
periodic inspection, and cleaning of the hardware equipment. It also includes
updates of the software. The PM inspections for these components are listed in
Table 6-1, SCC Hardware Equipment Preventive Maintenance Schedule.
COMPONENT/EQUIPMENT
TASK
SCHEDULE
REFERENCE
Server
Visual Checks
TBD
TBD
Storage Devices
Visual Checks
TBD
TBD
Cabinet Filters
Change
TBD
TBD
Air-condition tweaks
Cleaning
TBD
TBD
Fire Fighting Equipment
Checks
TBD
TBD
Cabinet Lights
Checks
TBD
TBD
Cabinet Fans
Checks
TBD
TBD
VORS
TBD
TBD
TBD
CCTV
TBD
TBD
TBD
SCC CABINET ASSEMBLY
WORKSTATION
Table 6-1. SCC Hardware Equipment Preventive Maintenance Schedule
COMPONENT/EQUIPMENT
TASK
SCHEDULE
REFERENCE
Software Updates
TBD
TBD
TBD
Antivirus Updates
TBD
TBD
TBD
Security Checks
TBD
TBD
TBD
Firewall updates
TBD
TBD
TBD
SCC SOFTWARE
Table 6-2. SCC Software Preventive Maintenance Schedule
453-SWD-RMM-0103020
MO-15.98.XX.XX/6XX-020
6-1
Rev. 01
Rev. 01
Rev. 01
Rev. 01
6-2
453-SWD-RMM-0103020
MO-15.98.XX.XX/6XX-020

CONFIGURATION
SECTION 7 - PARTS LISTING
7.1
PARTS LISTING
This section contains the information necessary to order replacement parts as provided by the equipment suppliers.
The Figure and Index column contains the figure number of the related illustration
and the callout number for a specific item respectively.
The Part Number column identifies the suppliers part number for ordering a specific item, or a component, or an assembly.
The Units per Assembly column identifies the number of identical components or
assemblies within the major assembly.
7.2
PARTS CATALOGUE
453-SWD-RMM-0103020
MO-15.98.XX.XX/6XX-020
7-1
Rev. 01
Rev. 01
453-SCC-02-021
5
2
J19PA
J50PA
Catalyst 2960
10
11
12
13
14
15
16
17
18
19
20
21
22
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
3,12,13,14
23
24
47
48
Catalyst 2960
7
8
6
10,11
9
FRONT VIEW
REAR VIEW
Figure 7-1. SCC Cabinet Assembly

Rev. 01
Rev. 01
7-2
453-SWD-RMM-0103020
MO-15.98.XX.XX/6XX-020
SCC Intergration and Configuration

Figure &
Index No.
Part No.
Description
Units/ OEM Operator

Ref.
Assy. Code Stock
No.
7-1
453-DP1-0408-6002-1
SCC CABINET ASSEMBLY
Ref.
1
2
3
Cabinet
Shelf
Patch Panel, LAN
1
1
1
4
5
Switch, LAN
Re-Broadcaster, Mutlicast, VORS
2
1
6
7
Blade Server Assembly

Array, Data Storage
1
1
Console, Rack Mount
Utility Power Distribution Unit
10
Power Distribution Unit
11
Connector, Power Cord
12
Cable, LAN (1 m)
13
Cable, LAN (0.9 m)
17
14
Cable, LAN (2.1 m)
453-SWD-RMM-0103020
MO-15.98.XX.XX/6XX-020
7-3
Rev. 01
Rev. 01
Rev. 01
Rev. 01
FRONT VIEW
7-4
IEC60320
C14
REAR VIEW
AUDIO 3.5mm
DVI
POWER
ADAPTER
IEC60320
C14
IEC 60320
C13
DISPLAY
PORT
8P8C
USB-A
USB-B
CONSOLE
TO ASSOCIATED
SCT COMPUTER
SCCW2 TO SCTW4
SCCW3 TO SCTW1
SCCW4 TO SCTW2
SCCW5 TO SCTW3
DC9-12V
DVI
DVI
USB-A
USB-A
USB
CPU4
USB-B
USB
CPU4
DVI
USB-A
USB-A
USB-A
IEC 60320
C13
MONITOR 1
IEC60320
C14
KEYBOARD
DVI
IEC 60320
C13
MONITOR 2
MOUSE
IEC60320
C14
453-SCC-02-017
Figure 7-2. SCC SCADA Workstation
453-SWD-RMM-0103020
MO-15.98.XX.XX/6XX-020

Figure &
Index No.
Part No.
Description
7-2
453-DP1-0408-6006-1
SCC SCADA WORKSTATION
1
2
3
4
5
6
7
2312HM
IEC 60320-C13/C14
-
Monitor
Soundbar, Stero, Flat Panel
Adapter, DVI Port
Headset, USB
Power Cord
KVM Switch, USB
A/B Cable, USB 2.0 (5m)
453-SWD-RMM-0103020
MO-15.98.XX.XX/6XX-020
7-5
Units/ OEM Operator

Ref.
Assy. Code Stock
No.
Ref.
2
1
1
1
4
1
1
Rev. 01
Rev. 01
Rev. 01
Rev. 01
FRONT VIEW
USB-A
REAR VIEW
AUDIO 3.5mm
7-6
IEC 60320
C13
DISPLAY
PORT
DISPLAY
PORT
DISPLAY
PORT
DISPLAY
PORT
8P8C
USB-A
USB-A
DVI
DVI
DVI
DVI
DVI
DVI
DVI
DVI
IEC 60320
C14
USB-A
DVI
IEC 60320
C13
MONITOR 1
IEC 60320
C14
KEYBOARD
DVI
MOUSE
IEC 60320
C13
MONITOR 2
IEC 60320
C14
1
MONITOR 3
IEC 60320
C14
DVI
IEC 60320
C13
MONITOR 4
IEC 60320
C14
453-SCC-02-018
Figure 7-3. SCC SCADA Workstation SCCW1
453-SWD-RMM-0103020
MO-15.98.XX.XX/6XX-020

Figure &
Index No.
Part No.
Description
7-3
453-DP1-0408-6004-1

SCCW1
1
2
3
4
5
2312HM
IEC 60320-C13/C14
Monitor
Adapter, DVI Port
Headset, USB
Power Cord
453-SWD-RMM-0103020
MO-15.98.XX.XX/6XX-020
7-7
Units/ OEM Operator

Ref.
Assy. Code Stock
No.
Ref.
4
1
4
1
5
Rev. 01
Rev. 01
Rev. 01
Rev. 01
FRONT VIEW
USB-A
REAR VIEW
AUDIO 3.5mm
7-8
5
IEC 60320
C13
DISPLAY
PORT
DVI
8P8C
USB-A
USB-A
IEC 60320
C14
DVI
DVI
USB-A DVI
IEC 60320
C13
MONITOR 1
IEC 60320
C14
KEYBOARD
DVI
IEC 60320
C13
MONITOR 2
MOUSE
IEC 60320
C14
453-SCC-02-019
Figure 7-4. SCC SCADA Training and Development Workstations
453-SWD-RMM-0103020
MO-15.98.XX.XX/6XX-020

Figure &
Index No.
Part No.
Description
7-4
453-DP1-0408-6007-1
SCC SCADA TRAINING AND

DEVELOPMENT WORKSTATIONS
1
2
3
4
5
2312HM
IEC 60320-C13/C14
Monitor
Adapter, DVI Port
Headset, USB
Power Cord
453-SWD-RMM-0103020
MO-15.98.XX.XX/6XX-020
7-9
Units/ OEM Operator

Ref.
Assy. Code Stock
No.
Ref.
2
1
1
1
3
Rev. 01
Rev. 01
MOUSE
FRONT VIEW
REAR VIEW
IEC60320
C13
8P8C
USB-A
AUDIO 3.5mm
USB-A
DVI
IEC60320
C14
USB-A
DVI
MONITOR 1
IEC 60320
C13
IEC60320
C14
KEYBOARD
453-SCC-02-020
Figure 7-5. Administration and Services System Workstation

Rev. 01
Rev. 01
7-10
453-SWD-RMM-0103020
MO-15.98.XX.XX/6XX-020

Figure &
Index No.
Part No.
Description
7-5
453-DP1-0408-6008-1
ADMINSTRATION AND SERVICES

SYSTEM WORKSTATION
1
2
3
2312HM
IEC 60320-C13/C14
Monitor
Power Cord
453-SWD-RMM-0103020
MO-15.98.XX.XX/6XX-020
7-11
Units/ OEM Operator

Ref.
Assy. Code Stock
No.
Ref.
1
1
2
Rev. 01
Rev. 01
Rev. 01
Rev. 01
FRONT VIEW
7-12
IEC60320
C14
REAR VIEW
AUDIO 3.5mm
POWER
ADAPTER
IEC60320
C14
IEC60320
C13
DISPLAY
PORT
DVI
8P8C
USB-A
DC9-12V
CONSOLE
USB-B
TO ASSOCIATED SCT
COMPUTER CFMWS
TO ASSOCIATED SCT
COMPUTER SCTW5
DVI
DVI
USB-A
USB-A
USB-A
USB
CPU4
USB-B
USB
CPU3
USB-A
USB-A
USB
CPU1
IEC 60320
C13
USB-B
USB
CPU2
USB-A DVI
MONITOR 1
IEC60320
C14
KEYBOARD
DVI
IEC 60320
C13
MONITOR 2
MOUSE
IEC60320
C14
453-SCC-02-022
Figure 7-6. SCC SCADA Workstation SCCW6
453-SWD-RMM-0103020
MO-15.98.XX.XX/6XX-020

Figure &
Index No.
Part No.
Description
7-6
453-DP1-0408-6005-1

SCCW6
1
2
3
4
5
6
7
2312HM
IEC 60320-C13/C14
-
Monitor
Adapter, DVI Port
Headset, USB
Power Cord
KVM Switch, USB
A/B Cable, USB 2.0 (5 m)
453-SWD-RMM-0103020
MO-15.98.XX.XX/6XX-020
7-13
Units/ OEM Operator

Ref.
Assy. Code Stock
No.
Ref.
2
1
1
1
4
1
2
Rev. 01
Rev. 01
Rev. 01
Rev. 01
7-14
453-SWD-RMM-0103020
MO-15.98.XX.XX/6XX-020
Index
A
AC Power Supply, 4-5
Addr
Parameter, 2-32
Addr Parameter, 2-26
Alarm Logger, 2-13
Alarm Server, 2-13
Alarm Suspension, 2-16, 2-66
Adminstration And Services System
Workstation, 7-11
Architecture, 2-5
Architecture Overview, 2-11
B
Bit: Parameter, 2-32
BitOffset Parameter, 2-27
Build, 2-30
C
C: Parameter, 2-31
CCTV Alarms, 2-63
Command Confirmation, 2-8
Command Line OPC, 2-83
Command Tag Formatting, 2-28
Comments, 2-24
Conditional Modbus Poller, 2-30
Inputs, 2-31
Outputs, 2-33
Processing, 2-32
Conditional Polling Device, 2-32
Config.Txt
Inputs, 2-36
D
Decimals, 2-28
Disabled Passengers, 2-70
Documentation, 5-1
E
Equipment Identification and
Location, 1-1
I/O Module, 4-8

Input Verification, 2-9
Reliability, 2-10
Requesting, 2-29
Maintainability, 2-11
Map.Txt
Link Input Coding, 2-37
Map Input Coding, 2-36
Minimal Workstation Installation,
2-11
Modbus Over TCP/IP, 2-13
Modbus Poller Outputs, 2-30
Modbus Poller Processing, 2-28
Modbus Server Device, 2-23
ModbusMsg, 2-85
Safety Precautions, 3-1, 4-1, 6-1

SCC Cabinet Assembly, 7-3
SCC Core Support Components,
2-13
SCC Data Collection, 2-13
SCC GUI Visualization, 2-14
SCC Host Applications, 2-82
SCC Processor Modules, 2-14
SCC Safety, 2-7
SCC SCADA Training and
Development Workstations, 7-9
SCC SCADA Workstation, 7-5, 7-7
SCC SCADA Workstation SCCW6,
7-13
SCC Subsystem Core
Components, 2-11
SCC Subsystem Processors Logic,
2-35
SCC Visualization Logic, 2-34
Scheduler, 2-73
Scheduler Support Applications,
2-83
SDK, 2-42
Server Module, 2-42
SME CCTV Alarms Interface, 2-15
SNMP Data, 2-14
SNMP Manager, 2-33
Sounder, 2-71
Sounder Module, 2-16
Special Tools and Test
Equipment, 4-1
Specifications, 1-1
System Network, 2-7
System Overview, 2-1
System Troubleshooting, 3-1
N
Net Check, 2-61
NetCheck, 2-15
Network Security, 2-9
Non-Vital Consideration, 2-7
O
OPC Data, 2-14
OPC Server, 2-23
Operation Prevention and
Protection, 2-7
P
PA Interface, 2-53
Passenger Information Interface
Module, 2-15
Performance, 2-9
PI Interface, 2-42
Poll.Txt for Conditional Modbus
Poller, 2-31
Poller Control Devices, 2-13
Polling, 2-28
Power Calc Module, 2-15, 2-36
Preventive Maintenance
Schedule, 6-1
Programmable Logic Controllers,
2-9
Public Address Interface Module,
2-15
F
Fan Module, 4-5
FinalMax, 2-27
FinalMin, 2-27
Full Blade, 4-3
G
Gen Broker, 2-34
H
Half Blade, 4-1
I
I: Parameter, 2-32
453-SWD-RMM-0103020
MO-15.98.XX.XX/6XX-020
R
Radio Interface, 2-82
RawMax, 2-27
RawMin, 2-27
Reconnect, 2-30
Redundant Architecture, 2-8
Redundant Network
Architecture, 2-11
Redundant Protocol
Architecture, 2-11
Redundant Server Architecture,
2-10
RegType, 2-28
Index-1
T
Tag Parameter, 2-26
TCPMsg, 2-86
Torque Values, 4-1
Trend Logger, 2-13
Type Parameter, 2-27
U
Unified Data Manager, 2-13, 2-33,
2-34
User Privileges, 2-8
V
Value: Parameter, 2-32
VORS Interface, 2-82
W
WriteFile, 2-84
Rev. 01
Rev. 01
Rev. 01
Rev. 01
Index-2
453-SWD-RMM-0103020
MO-15.98.XX.XX/6XX-020

Set 3: SCC and OCC

Configuration
Part 2
453-SWD-RMM-0103020
MO-15.98.XX.XX/6XX-020
Rev. 01
Rev. 01

Set 3: SCC and OCC

Configuration
Owners Manual
453-SWD-RMM-0103020
MO-15.98.XX.XX/6XX-020
Rev. 01
Rev. 01

Owner's Manual
Regulatory Model: BMX01
Notes, Cautions, and Warnings

NOTE: A NOTE indicates important information that helps you make better use of your computer.
CAUTION: A CAUTION indicates either potential damage to hardware or loss of data and tells you how to avoid the
problem.
WARNING: A WARNING indicates a potential for property damage, personal injury, or death.
2013 Dell Inc. All Rights Reserved.

Trademarks used in this text: Dell, the Dell logo, Dell Boomi, Dell Precision , OptiPlex, Latitude, PowerEdge, PowerVault,
PowerConnect, OpenManage, EqualLogic, Compellent, KACE, FlexAddress, Force10, Venue and Vostro are trademarks
of Dell Inc. Intel, Pentium, Xeon, Core and Celeron are registered trademarks of Intel Corporation in the U.S. and other countries.
AMD is a registered trademark and AMD Opteron, AMD Phenom and AMD Sempron are trademarks of Advanced Micro
Devices, Inc. Microsoft, Windows, Windows Server, Internet Explorer, MS-DOS, Windows Vista and Active Directory are
either trademarks or registered trademarks of Microsoft Corporation in the United States and/or other countries. Red Hat and
Red Hat Enterprise Linux are registered trademarks of Red Hat, Inc. in the United States and/or other countries. Novell and SUSE
are registered trademarks of Novell Inc. in the United States and other countries. Oracle is a registered trademark of Oracle
Corporation and/or its affiliates. Citrix, Xen, XenServer and XenMotion are either registered trademarks or trademarks of Citrix
Systems, Inc. in the United States and/or other countries. VMware, vMotion, vCenter, vCenter SRM and vSphere are registered
trademarks or trademarks of VMware, Inc. in the United States or other countries. IBM is a registered trademark of International
Business Machines Corporation.
2013 - 09
Rev. A04
Contents
1 About Your System......................................................................................................................7
System Overview...................................................................................................................................................... 7
System Control-Panel Features................................................................................................................................ 9
LCD Module............................................................................................................................................................ 10
LCD Module Features.......................................................................................................................................11
Using The LCD Module Menus.........................................................................................................................12
Configuration Wizard.............................................................................................................................................. 12
Back-Panel Features.............................................................................................................................................. 13
Power Supply Indicators..................................................................................................................................14
Fan Module Indicators..................................................................................................................................... 16
Avocent iKVM Analog Switch Module (Optional)...................................................................................................17
Avocent Analog iKVM Switch Module Indicators........................................................................................... 17
Avocent Analog iKVM Switch Module Features..............................................................................................18
CMC Module........................................................................................................................................................... 19
CMC Module Features......................................................................................................................................19
CMC Fail-Safe Mode........................................................................................................................................ 20
Daisy-Chain CMC Network Connection........................................................................................................... 21
System Messages...................................................................................................................................................22
Other Information You May Need...........................................................................................................................22
2 Initial System Configuration.................................................................................................... 25

Before You Begin....................................................................................................................................................25
Initial Setup Sequence............................................................................................................................................25
Initial CMC Network Configuration.........................................................................................................................25
Configuring The CMC Using The LCD Configuration Wizard............................................................................26
Configuring The CMC Using A Management Station And CLI......................................................................... 26
Logging In To The CMC Using The Web-Based Interface......................................................................................27
Adding And Managing CMC Users.........................................................................................................................28
Configuring iDRAC Networking Using The Web-Based Interface......................................................................... 28
Setting The First Boot Device For Servers..............................................................................................................29
Configuring And Managing Power......................................................................................................................... 29
Installing Or Updating The CMC Firmware............................................................................................................. 29
Downloading The CMC Firmware.................................................................................................................... 30
Updating The CMC Firmware Using The Web-Based Interface...................................................................... 30
Updating The CMC Firmware Using RACADM.................................................................................................31
Configuring The Optional iKVM Switch Module..................................................................................................... 31
Updating The iKVM Firmware.......................................................................................................................... 31
Tiering The Avocent iKVM Switch From A Digital KVM Switch.......................................................................31
Tiering The Avocent iKVM Switch From An Analog KVM Switch....................................................................32

Configuring The Analog Switch........................................................................................................................32
Resynchronizing The Server List At The Remote Client Workstation.............................................................. 33
Viewing And Selecting Servers........................................................................................................................33
FlexAddress............................................................................................................................................................ 34
FlexAddress Plus.................................................................................................................................................... 34
3 Configuring The I/O Modules.................................................................................................. 35

Network Information...............................................................................................................................................35
I/O Connectivity.......................................................................................................................................................35
General I/O Module Configuration Guidelines................................................................................................. 35
Fabric A............................................................................................................................................................ 35
Fabric B............................................................................................................................................................ 36
Fabric C............................................................................................................................................................ 36
Port Auto-Disablement in Quad-Port Network Daughter Card (Dell PowerEdge M710HD Only)...........................36
Mezzanine Cards.................................................................................................................................................... 37
PowerEdge M610x Only................................................................................................................................... 37
Full-Height Blades............................................................................................................................................ 37
Half-Height Blades........................................................................................................................................... 37
I/O Module Port MappingFull-Height Blades..................................................................................................... 39
Standard LOM (Dual-Port) Mapping................................................................................................................ 39
Dual-Port Mezzanine Cards............................................................................................................................. 39
Quad-Port Mezzanine Cards............................................................................................................................ 43
I/O Module Port MappingHalf-Height Blades......................................................................................................45
Standard LOM (Dual-Port) and Network Daughter Card (Quad-Port) Mapping.............................................. 45
Dual-Port Mezzanine Cards............................................................................................................................. 45
Quad-Port Mezzanine Cards ........................................................................................................................... 46
I/O ModulesSwitches......................................................................................................................................... 47
Configuring A Switch Module Network Ethernet Port Using The Web-Based Interface................................47
Brocade M6505 16 Gbps FC SAN I/O Module.................................................................................................. 48
Cisco Nexus B22 Fabric Extender Module.......................................................................................................49
Dell PowerEdge M I/O Aggregator Switch...................................................................................................... 49
Dell Force10 MXL 10/40 GbE Switch.................................................................................................................50
Mellanox M4001F/M4001Q/M4001T Infiniband Switch I/O Module................................................................. 51
Dell PowerConnect KR 8024-k Switch..............................................................................................................52
Dell PowerConnect M8428-k 10 Gb Converged Network Switch.................................................................... 53
Mellanox M2401G DDR Infiniband Switch I/O Module.................................................................................... 54
Mellanox M3601Q QDR Infiniband Switch I/O Module.................................................................................... 55
Cisco Catalyst Ethernet Switch I/O Modules................................................................................................... 56
Dell PowerConnect M6348 1 Gb Ethernet Switch I/O Module......................................................................... 57
Dell PowerConnect M6220 Ethernet Switch I/O Module................................................................................. 58
Dell PowerConnect M8024 10 Gb Ethernet Switch I/O Module....................................................................... 59
Dell 8/4 Gbps FC SAN Module.......................................................................................................................... 60

Brocade M5424 FC8 I/O Module.......................................................................................................................61
I/O ModulesPass-Through .................................................................................................................................63
Dell 4 Gbps Fibre Channel Pass-Through Module........................................................................................... 63
Dell 10 GbE KR Pass-Through I/O Module........................................................................................................65
Dell 10 Gb Ethernet Pass-Through Module II...................................................................................................66
10/100/1000 Mb Ethernet Pass-Through I/O Module........................................................................................66
4 Installing Enclosure Components...........................................................................................69

Recommended Tools.............................................................................................................................................. 69
Removing And Installing A Blade........................................................................................................................... 69
Removing A Blade............................................................................................................................................ 69
Installing A Blade............................................................................................................................................. 71
Power Supply Modules...........................................................................................................................................71
Power Supply Blanks....................................................................................................................................... 71
AC Power Supply Modules...............................................................................................................................71
DC Power Supply Modules...............................................................................................................................74
Fan Modules........................................................................................................................................................... 80
Removing A Fan Module.................................................................................................................................. 80
Installing A Fan Module................................................................................................................................... 81
CMC Module........................................................................................................................................................... 81
Removing A CMC Module................................................................................................................................ 81
Installing A CMC Module................................................................................................................................. 82
iKVM Module.......................................................................................................................................................... 83
Removing An iKVM Module............................................................................................................................. 83
Installing An iKVM Module...............................................................................................................................84
I/O Modules............................................................................................................................................................ 84
Removing An I/O Module................................................................................................................................. 85
Installing An I/O Module...................................................................................................................................85
Enclosure Bezel...................................................................................................................................................... 86
Removing The Enclosure Bezel........................................................................................................................86
Installing The Enclosure Bezel.........................................................................................................................87
Enclosure Midplane................................................................................................................................................87
Removing The Front Module Cage Assembly And Midplane...........................................................................87
Installing The Midplane And Front Module Cage Assembly............................................................................89
Enclosure Control Panel Assembly.........................................................................................................................90
Removing The Control Panel............................................................................................................................ 90
Installing The Control Panel............................................................................................................................. 91
LCD Module............................................................................................................................................................ 91
Removing The LCD Module.............................................................................................................................. 91
Installing The LCD Module............................................................................................................................... 92
5 Troubleshooting The Enclosure..............................................................................................93

Safety FirstFor You and Your System..................................................................................................................93
Responding to a Systems Management Alert Message........................................................................................ 93
Troubleshooting A Damaged Enclosure................................................................................................................. 93
Troubleshooting Enclosure Components................................................................................................................93
Troubleshooting A Wet Enclosure................................................................................................................... 94
Troubleshooting Power Supply Modules.........................................................................................................94
Troubleshooting Fan Modules..........................................................................................................................95
Troubleshooting The iKVM Module................................................................................................................. 95
Troubleshooting I/O Modules...........................................................................................................................95
6 Technical Specifications......................................................................................................... 97
Enclosure Specifications........................................................................................................................................97
I/O Module Specifications...................................................................................................................................... 98
7 Getting Help..............................................................................................................................103
Contacting Dell..................................................................................................................................................... 103
About Your System
System Overview
Your system can include up to 16 half-height blades (server modules), eight full-height blades, eight sleeves with
quarter-height blades, or a mix of the three blade types. To function as a system, a blade or sleeve is inserted into an
enclosure (chassis) that supports power supplies, fan modules, a Chassis Management Controller (CMC) module, and at
least one I/O module for external network connectivity. The power supplies, fans, CMC, optional iKVM module, and I/O
modules are shared resources of the blades in the PowerEdge M1000e enclosure.
NOTE: To ensure proper operation and cooling, all bays in the enclosure must be populated at all times with either
a module or with a blank.
Figure 1. Blade Numbering Half-Height Blades
Figure 2. Blade Numbering Full Height Blades
Figure 3. Blade Numbering Quarter Height Blades
Figure 4. Blade Numbering Mixed Full-Height, Half-Height, and Quarter-Height Blades
System Control-Panel Features
Figure 5. Control-Panel Features
1. USB port (mouse only)

2. USB port (keyboard only)
3. video connector
4. system power button
5. system power indicator

Control Panel
Features
USB ports for
keyboard and mouse
Description
Icon
Description
USB port 1 connects to the mouse and USB port 2 connects to the
keyboard.
NOTE: The USB ports are functional if an optional iKVM module is
installed and front panel ports are enabled (default setting) in the
CMC interface.
NOTE: These ports do not support USB storage devices. Only
connect USB storage devices to the USB ports on the front panel
of the blade.
Video connector
Icon
Description
Functional if an optional iKVM module is installed and front panel

ports are enabled (default setting) in the CMC interface.
System power button Turns the system on and off. Press to turn on the system. Press and hold 10 seconds to turn off
the system.
NOTE: The system power button controls power to all of the blades and I/O modules in the
enclosure.
System power
indicator
Icon
Indicators
Off
System does not have power.
Green
System power is on.
LCD Module
The LCD module provides an initial configuration/deployment wizard, as well as easy access to infrastructure and blade
information, and error reporting.
10
Figure 6. LCD Display
1. LCD screen
2. scroll buttons (4)
3. selection ("check") button
LCD Module Features

The primary function of the LCD module is to provide real-time information on the health and status of the modules in the
enclosure.
LCD module features include:
A deployment setup wizard that allows you to configure the CMC modules network settings during initial system
set up.
Menus to configure the iDRAC in each blade.
Status information screens for each blade.
Status information screens for the modules installed in the back of the enclosure, including the I/O modules,
fans, CMC, iKVM, and power supplies.
A Network Summary screen listing the IP addresses of all components in the system.
Real time power consumption statistics, including high and low values, and average power consumption.
Ambient temperature values.
AC power information.
Critical failure alerts and warnings.
11
Using The LCD Module Menus

Key
Action
Left and right arrows
Move between screens.
Up or down arrow
Move to the previous or next option on a screen.
Center button
Select and save an item and move to the next screen.
Main Menu
The Main Menu options include links to the LCD Setup Menu, Server Menu, and Enclosure Menu.
LCD Setup Menu

You can change the default language and start-up screen for the LCD menu screens using this menu.
Server Menu
From the Server Menu dialog box, you can highlight each blade in the enclosure using the arrow keys, and view its
status.
A blade that is turned off or booting is designated by a gray rectangle. An active blade is indicated by a green
rectangle. If a blade has errors, this condition is indicated by an amber rectangle.
To select a blade, highlight it and press the center button. A dialog box displays the iDRAC IP address of the
blade and any errors present.
Enclosure Menu
The Enclosure Menu includes options for Module Status, Enclosure Status, and Network Summary.
In the Module Status dialog box, you can highlight each component in the enclosure and view its status.
A module that is turned off or booting is designated by a gray rectangle. An active module is indicated
by a green rectangle. If a module has errors, it is indicated by an amber rectangle.
If a module is selected, a dialog box displays the current status of the module and any errors present.
In the Enclosure Status dialog box, you can view the enclosure status, any error conditions, and power
consumption statistics.
The Network Summary screen lists the IP addresses for the CMC and iDRAC in each blade, and other
components in the enclosure.
Configuration Wizard
The CMC is preset for Dynamic Host Configuration Protocol (DHCP). To use a static IP address, you must toggle the CMC
setting from DHCP to a static address by either running the LCD configuration wizard, or by using a management station
and CLI commands. For more information, see the CMC documentation at support.dell.com/manuals.
To set up a network using the LCD configuration wizard:
1.
If you have not already done so, press the chassis power button to turn it on.
The LCD screen displays a series of initialization screens as it turns on. When it is ready, the Language Setup
screen is displayed.
2.
Select a language from the options in the dialog box.

The following message is displayed on the enclosure screen: Configure Enclosure?
3.
12
Press the center button to continue to the CMC Network Settings screen.
4.
5.
Configure the CMC network settings for your network environment:
Network speed
Duplex mode
Network mode (DHCP or static)
Static IP address, subnet mask, and gateway values (if static mode was selected)
DNS settings
If required, configure the iDRAC network settings. For more information about iDRAC, see the iDRAC Users Guide
at support.dell.com/manuals.
NOTE: The configuration wizard automatically configures each blades iDRAC internal network interface if you
do not choose to manually configure the iDRAC settings.
NOTE: You cannot set a static IP address for the iDRAC using the LCD configuration wizard. To set a static IP
address, use the CMC web-based interface or Remote Access Controller Administrator (RACADM).
6.
Review the settings on the Network Summary screen:
If the settings are correct, press the center button to close the configuration wizard and return to the Main
Menu.
If the settings are not correct, use the left arrow key to return to the screen for that setting and correct it.
After you complete the configuration wizard, the CMC is available on your network.
Back-Panel Features
Figure 7. Back-Panel Features
1. fan modules (9)

2. primary CMC module
3. I/O modules (6)
4. optional iKVM module

5. secondary CMC module
6. power supplies (6)
13
Figure 8. Back-Panel Module Bay Numbering
1. CMC 1 (primary CMC module)

2. A1 B1 C1 (left I/O modules)
3. iKVM (iKVM module)
4. C2 B2 A2 (right I/O modules)

5. CMC 2 (secondary CMC module)
Power Supply Indicators

NOTE: The AC power supplies must be connected to a Power Distribution Unit (PDU), not directly to an electrical
outlet. For DC power supplies, plug the other end of the power cables to a branch circuit-protective ground DC
power source of (4860) V DC.
14
A 2700 W power supply requires a 100 V to 240 V power source.
The 2700 W power supply provides 1350 W input power, if connected to a 110 V AC power source
(optional).
A 3000 W power supply can only be connected to a 200 V AC240 V AC power source.
Figure 9. Power Supply Indicators
1. DC power output indicator

2. power supply fault indicator
3. AC power indicator
The power supply indicators provide the following information:
Indicator
DC power output
indicator
Description
Icon
Description
Power supply fault

indicator
Icon
Description
AC power source
present indicator
Green indicates that the power supply is operational and providing

DC power to the system.
Amber indicates a problem with the power supply, which can result
from either a failed power supply or a failed fan within the power
supply.
Icon
Description
Green indicates that a valid AC source is connected to the power

supply and is operational.
15
Fan Module Indicators
Figure 10. Fan Module Indicators
1. fan power indicator

2. fan fault indicator
The indicators provide the following information:
Indicator
Fan power indicator
Fan fault indicator
16
Description
Solid Green
The fan is receiving DC power and working properly.
Off
The fan has failed.
Amber
The fan is in a fault condition.
Avocent iKVM Analog Switch Module (Optional)
Figure 11. Avocent iKVM Switch Module
1. status/identification indicator
2. power indicator
3. link indicator
CAUTION: Do not connect the ACI port to a
LAN device such as a network hub. Doing so
may result in equipment damage.
4. Analog Console Interface (ACI) port (for tiering

connection only)
5. activity indicator
6. USB connectors (2) for keyboard and mouse
7. video connector
Avocent Analog iKVM Switch Module Indicators

Module Indicator
Power indicator
Status/Identification
indicator
USB connectors
Description
Off
iKVM switch does not have power.
Green
iKVM switch has power.
Green flashing
Firmware upgrade in progress.
Blue blinking
iKVM module is being identified.
Amber flashing
System fault or error condition.
Allows a keyboard and mouse to be connected to the system.
17
Module Indicator
Description
Video connector
Allows a monitor to be connected to the system.
ACI port
Allows connection of one or more servers to a Dell console switch with an Analog Rack
Interface (ARI) port, such as an external digital or analog switch.
Link indicator
Activity indicator
Off
The ACI is not connected to the external switch.
Green
The ACI is connected to the external switch.
Off
Data is not being sent or received.
Amber blinking
Data is being sent or received.
Avocent Analog iKVM Switch Module Features
Local iKVM access can be remotely disabled on a per blade basis, using the blades iDRAC interface (access is
enabled by default).
NOTE: A console session (enabled by default) to a given blade is available for both iDRAC interface and
iKVM users. Users connected to a blade's console using iDRAC and the iKVM see the same video and are
able to type commands. If not required, sharing can be disabled using the iDRAC console interface.
One VGA connector. The iKVM supports a video display resolution range from 640 x 480 at 60 Hz up to 1280 x
1024 x 65,000 colors (non-interlaced) at 75 Hz.
Two USB ports for keyboard and mouse.

NOTE: The iKVM USB ports do not support storage devices.
RJ-45 Analog Console Interface (ACI) port for tiering with Dell and Avocent analog KVM and KVM over IP
switches with Analog Rack Interface (ARI) ports.
NOTE: Although the ACI port is an RJ-45 connector and uses Cat5 (or better) cabling, it is not an Ethernet
network interface port. It is only used for connection to external KVM switches with ARI ports, and does
not support native KVM over IP.
The iKVM can also be accessed from the front of the enclosure, providing front or rear panel KVM functionality,
but not at the same time. For enhanced security, front panel access can be disabled using the CMCs interface.
NOTE: Connecting a keyboard, video, and mouse to the enclosure front panel disables video output to the
iKVM back panel port. It does not interrupt iDRAC video and console redirection.
18
You can use the iKVM to access the CMC console directly, using RACADM or using the web-based interface.
For more information, see Using the iKVM Module in the CMC Users Guide at support.dell.com/manuals.
CMC Module
Figure 12. CMC Module Features
Ethernet connector Gb1
Ethernet connector STK ("stack") - used for daisychaining CMCs in separate enclosures
link indicator
activity indicator
DB-9 serial connector for local configuration
optional secondary CMC (CMC 2)
optional iKVM module
primary CMC (CMC 1)
blue status/identification indicator
10
power indicator
CMC Module Features

The CMC provides the following multiple systems management functions for your modular server:
Enclosure-level real-time automatic power and thermal management.
Monitors system power requirements and supports the optional Dynamic Power Supply Engagement
(DPSE) mode. The DPSE mode improves power efficiency by allowing the CMC to dynamically place
power supplies in standby mode, depending on the load and redundancy requirements.
Reports real-time power consumption, which includes logging high and low points with a time stamp.
Supports setting an optional enclosure Maximum Power Limit, which either alerts or takes actions, such
as throttling server modules and/or preventing the power up of new blades to keep the enclosure under
the defined maximum power limit.
Monitors and automatically controls cooling fans based on actual ambient and internal temperature
measurements.
19
Provides comprehensive enclosure inventory and status/error reporting.
CMC fail-safe mode. For more information, see CMC Fail-Safe Mode.
The CMC provides a mechanism for centralized configuration of the following:
The enclosures network and security settings
Power redundancy and power ceiling settings
I/O switches and iDRAC network settings
First boot device on the server blades
Checks I/O fabric consistency between the I/O modules and blades and disables components if
necessary to protect the system hardware
User access security
NOTE: It is recommended that you isolate chassis management from the data network. Dell cannot support
or guarantee uptime of a chassis that is improperly integrated into your environment. Due to the potential
of traffic on the data network, the management interfaces on the internal management network can be
saturated by traffic intended for servers. This results in CMC and iDRAC communication delays. These
delays may cause unpredictable chassis behavior, such as CMC displaying iDRAC as offline even when it
is up and running, which in turn causes other unwanted behavior. If physically isolating the management
network is impractical, the other option is to separate CMC and iDRAC traffic to a separate VLAN. The CMC
and individual iDRAC network interfaces can be configured to use a VLAN with the racadm setniccfg
command. For more information, see the Dell Chassis Management Controller Administrator Reference
Guide at support.dell.com/manuals.
CMC Fail-Safe Mode

Similar to the failover protection offered by the redundant CMC, the M1000e enclosure enables the fail-safe mode to
protect the blades and I/O modules from failures. The fail-safe mode is enabled when no CMC is in control of the
chassis. During the CMC failover period or during a single CMC management loss:
you cannot turn on newly installed blades
existing blades cannot be accessed remotely
chassis cooling fans run at 100% for thermal protection of the components
blade performance reduces to limit power consumption until management of the CMC is restored
The following are some of the conditions that can result in CMC management loss:
Condition
Description
CMC removal
Chassis management resumes after replacing CMC, or after failover to standby CMC.
CMC network cable

removal or network
connection loss
Chassis management resumes after the chassis fails over to the standby CMC. Network
failover is only enabled in redundant CMC mode.
CMC reset
Chassis management resumes after the CMC reboots or chassis fails over to the standby CMC.
CMC failover
command issued
Chassis management resumes after the chassis fails over to the standby CMC.
CMC firmware update Chassis management resumes after the CMC reboots or chassis fails over to the standby CMC.
It is recommended that you update the standby CMC first so that there is only one failover
event. For more information on updating the CMC firmware, see the CMC User's Guide at
support.dell.com/manuals.
20
Condition
Description
CMC error detection

and correction
Chassis management resumes after the CMC resets or chassis fails over to the standby CMC.
NOTE: You can configure the enclosure with a single CMC or with redundant CMCs. In redundant CMC
configurations, if the primary CMC loses communication with the enclosure or the management network, the
standby CMC takes over chassis management.
Daisy-Chain CMC Network Connection

Each CMC has two RJ-45 Ethernet ports, labeled GB (the uplink port) and STK (the stacking or cable consolidation port).
With basic cabling, you can connect the GB port to the management network and leave the STK port unused.
CAUTION: Connecting the STK port to the management network can have unpredictable results. Cabling GB and
STK to the same network (broadcast domain) can cause a broadcast storm.
If you have multiple chassis in a rack, you can reduce the number of connections to the management network by daisychaining up to four chassis together. If each of the four chassis contains a redundant CMC, by daisy-chaining you can
reduce the number of management network connections required from eight to two. If each chassis has only one CMC,
you can reduce the connections required from four to one.
When daisy-chaining chassis together, GB is the uplink port and STK is the stacking (cable consolidation) port. Connect
the GB ports to the management network or to the STK port of the CMC in a chassis that is closer to the network. You
must connect the STK port only to a GB port further from the chain or network.
Create separate chains for the CMCs in the active CMC slot and the second CMC slot.
NOTE: At least one CMC must be installed for the system to power up. If a second, optional CMC module is
installed, failover protection and hot-swap replacement is available. See the latest CMC User's Guide at
support.dell.com/manuals for complete instructions on how to set up and operate the CMC module.
The following figure illustrates the arrangement of cables for four daisy-chained chassis, each with active and standby
CMCs.
21
Figure 13. CMC Daisy-Chaining
1. management network
2. secondary CMC
3. primary CMC
System Messages
System messages related to the blades in the enclosure may appear on the monitor screen to notify you of a possible
problem with a blade. For a detailed listing of these error messages, including possible causes and solutions, see the
blade documentation.
Other Information You May Need

WARNING: See the safety and regulatory information that shipped with your system. Warranty information may be
included within this document or as a separate document.
22
The Getting Started Guide provides an overview of system features, setting up your system, and technical
specifications.
The blade Owner's Manual provides information about the blade features and describes how to troubleshoot the
blade and install or replace the blade's components.
The Dell CMC Users Guide provides information on installing, configuring, and using the CMC.
Dell systems management application documentation provides information about installing and using the
systems management software.
For the full name of an abbreviation or acronym used in this document, see the Glossary at support.dell.com/
manuals.
Any media that ships with your system that provides documentation and tools for configuring and managing your
system, including those pertaining to the operating system, system management software, system updates, and
system components that you purchased with your system.
NOTE: Always check for updates on support.dell.com/manuals and read the updates first because they
often supersede information in other documents.
23
24
Initial System Configuration
Before You Begin

CAUTION: The enclosure power supplies must be connected to a Type B or permanently-connected PDU and not
directly to an electrical outlet. The AC power supplies require a 100 V to 120 V or 200 V to 240 V power source. You
can select only one AC power input, as the system does not operate at both ranges simultaneously. For DC power
supplies, plug the other end of the power cables to a branch circuit-protective ground DC power source of (4860)
V DC.
If your network uses static addressing, you need the IP address, subnet mask, and gateway to configure the CMC and
other modules in the enclosure.
Initial Setup Sequence

NOTE: Follow the instructions on the enclosure chassis and remove the blades and power supplies before lifting
and installing the system. Reinstall the blades and power supplies after you install the chassis in the rack.
1.
Unpack the enclosure and install it in a rack.

For more information, see the Getting Started Guide and Rack Installation Guide at support.dell.com/manuals.
CAUTION: Do not turn on the blades (server modules) until you have configured the switch modules.
2.
Connect the power supply units to a PDU.
3.
If an optional iKVM module is installed, connect the keyboard, video, and mouse to the enclosure control panel or
to the iKVM module.
NOTE: Connecting a keyboard, video, and mouse to the enclosure control panel disables video output to the
iKVM back panel port.
4.
Press the power button on the enclosure control panel.
5.
Configure the CMC network settings.

The LCD configuration wizard allows you to quickly configure the CMC and iDRAC management interfaces and
manage the enclosure remotely. You can also use a management station and the RACADM CLI to configure the
CMC.
6.
Configure the I/O modules to allow proper network or storage management or paths.
7.
After the Ethernet and fibre channel switches are configured, you can turn on your server blades. This allows time
for the Ethernet switch to boot and allow PXI\UNDI traffic for all blade modules.
Initial CMC Network Configuration

The CMC is preset for DHCP. To use a static IP address, you must toggle the CMC setting from DHCP to a static address
by either running the LCD configuration wizard, or by using a management station and CLI commands.
25
If toggled to use a static address, the CMC IP address defaults to the standard IP address settings of 192.168.0.120,
255.255.255.0, and gateway of 192.168.0.1. You can change this address to an IP address of your choice.
Configuring The CMC Using The LCD Configuration Wizard

When you first boot your system, the screen on the LCD module directs you to configure the CMC network settings.
NOTE: The option to configure the enclosure using the LCD configuration wizard is only available until the CMC
default password is changed or when the LCD configuration wizard is complete. Thereafter, use the RACADM CLI
or the web-based GUI to change the CMC settings.
NOTE: The serial null modem cable for the CMC is an option. You can access the CLI using the 17th blade feature
on the embedded iKVM module. Blade number 17 is a direct local connection to the CMC.
1.
Choose a language from the options in the dialog box.
2.
Start the LCD configuration wizard.
3.
Configure the CMC network settings for your network environment.
Network speed
Duplex mode
Protocol (IPv4 and/or IPv6)
Network mode (DHCP or static)
Static IP address, subnet mask, and gateway values (if static mode was selected)
DNS setting, including a registered CMC name, (if DHCP mode was selected)
NOTE: The CMC external management network mode is set by default to DHCP. To use a static IP address,
you must change the setting using the LCD configuration wizard.
4.
If required, configure the iDRAC network setting for DHCP mode.

NOTE: You cannot set a static IP address for the iDRAC using the LCD configuration wizard. To set the static
IP address, use the web-based interface.
5.
Review the settings on the Network Summary screen:
If the settings are correct, press the center button to close the configuration wizard and return to the Main
Menu.
If the settings are not correct, use the left-arrow key to return to the screen for that setting and make the
appropriate changes.
The Network Summary screen lists the IP addresses for the CMC and the iDRAC network settings.
After you complete the LCD configuration wizard, you can access the CMC on the network using the web-based CMC
interface or text-based interfaces such as a serial console, Telnet, or SSH.
NOTE: If you want to use static addresses rather than DHCP to access the iDRACs, you must configure them using
the CMC web-based interface or CLI.
Configuring The CMC Using A Management Station And CLI

The LCD configuration wizard is the quickest way to initially configure the CMC network settings. However, you can also
use a management station and a local connection to access the CMC.
There are two ways to create a local connection to the CMC:
26
The CMC Console, using the optional iKVM. Press <Prnt Scrn> and select blade number 17.
Serial connection, using an optional null modem cable (115200 bps, 8 data bits, no parity, 1 stop bit, and no flow
control).
Once you have established a connection to the CMC, you can complete the initial CMC network configuration.
1.
Log in to the CMC.

The default user name is root and the default password is calvin.
2.
Type getniccfg and press <Enter> to view the current CMC network parameters.
3.
Configure the CMC network settings:
To set a static IP address, type

setniccfg -s <IP address><network mask><gateway>
and press <Enter>.
To configure the CMC to obtain an IP address using DHCP, type

setniccfg -d
and press <Enter>.
The new network settings are activated in a few seconds after configuring the network.
Logging In To The CMC Using The Web-Based Interface

1.
Open a supported web browser window.

For current information on supported web browsers, see the CMC Users Guide at support.dell.com/manuals.
2.
Log in to the CMC.
If the CMC is accessed using a specific IP address, type the following URL in the Address field, and then
press <Enter>.
https://<CMC IP address>
The default IP address for the CMC is 192.168.0.120. If the default HTTPS port number (port 443) has been
changed, type:
https://<CMC IP address>:<port number>
where <CMC IP address> is the IP address for the CMC and <port number> is the HTTPS port number.
If you access the CMC using a registered DNS name, type the CMCs name:
https://<CMC name>
By default, the CMC name on the DNS server is cmc-<service tag>
The CMC Login page is displayed.
NOTE: The default CMC user name is root, and the password is calvin. The root account is the default
administrative account that ships with the CMC. For added security, you must change the default password of
the root account during initial setup.
NOTE: The CMC does not support extended ASCII characters, such as , , , , or other characters used
primarily in non-English languages.
NOTE: You cannot log in to the web-based interface with different user names in multiple browser windows
on a single workstation.
You can log in as either a CMC user or as Directory Service user in Microsoft Active Directory or Lightweight
Directory Access Protocol Services (LDAP).
3.
In the Username field, type your user name:
27
CMC user name: <user name>
Active Directory user name: <domain>\<user name>
LDAP user name: <user name>
NOTE: This field is case sensitive.

4.
In the Password field, type your CMC user password or Active Directory user password.
NOTE: This field is case-sensitive.
Adding And Managing CMC Users

From the Users and User Configuration pages in the web-based interface, you can view information about CMC users,
add a new user, and change settings for an existing user.
NOTE: For added security, it is highly recommended that you change the default password of the root (User 1)
account. The root account is the default administrative account that ships with the CMC.
To change the default password for the root account, click User ID 1 to open the User Configuration page. Help for that
page is available through the Help link at the top right corner of the page.
NOTE: You must have User Configuration Administrator privileges to perform the following steps.
1.
Log in to the web-based interface.
2.
Select Chassis in the system tree.
3.
Click the Network/Security tab, and then click the Users sub-tab.
The Users page is displayed, listing each users user ID, login state, user name, and CMC privilege, including those
of the root user. User IDs available for configuration have no user information displayed.
4.
Click an available user ID number. The User Configuration page is displayed.

To refresh the contents of the Users page, click Refresh. To print the contents of the Users page, click Print.
5.
Select general settings for the users.

For details on user groups and privileges, see the CMC Users Guide at support.dell.com/manuals.
6.
Assign the user to a CMC user group.

You can customize the privileges settings for the user by using the check boxes. After you have selected a CMC
Group or made Custom user privilege selections, click Apply Changes to save the settings.
When you select a user privilege setting from the CMC Group drop-down menu, the enabled privileges (shown as
checked boxes in the list) are displayed according to the pre-defined settings for that group.
Configuring iDRAC Networking Using The Web-Based Interface

Follow this procedure to configure the iDRAC in the LCD configuration wizard.
NOTE: If you did not configure the iDRAC using the LCD configuration wizard, iDRAC is disabled until you configure
it using the web-based interface.
NOTE: You must have Chassis Configuration Administrator privileges to set up iDRAC network settings from the
CMC.
NOTE: The default CMC user name is root and the default password is calvin.
1.
2.
Click the plus (+) symbol next to Chassis in the left column, then click Servers.
28
3.
Click Setup Deploy.
4.
Select the protocol for the iDRAC setting (IPv4 and/or IPv6).
5.
Under Enable Lan, select the check box next to the server to enable LAN for iDRAC.
6.
Under Enable IPMI over LAN, select or clear the check box next to the server to enable or disable IPMI over LAN.
7.
Under DHCP Enabled, select or clear the check box next to the server to enable or disable DHCP for iDRAC.
8.
If DHCP is disabled, enter the static IP address, netmask, and default gateway for the iDRAC.
9.
Click Apply at the bottom of the page.
Setting The First Boot Device For Servers

The First Boot Device page allows you to specify the boot device for each blade. You can set the default boot device and
also set a one-time boot device. This allows you to boot using a special image to perform tasks such as running
diagnostics or reinstalling an operating system.
To set the first boot device for some or all servers in the chassis:
1.
Log in to the CMC web-based interface.
2.
Click Servers in the system tree and then click Setup Deploy First Boot Device. A list of servers is displayed, one
per row.
3.
Select the boot device you want to use for each server from the list box.
4.
If you want the server to boot from the selected device every time it boots, clear the Boot Once check box for the
server.
If you want the server to boot from the selected device only on the next boot cycle, select the Boot Once check box
for the server.
5.
Click Apply.
Configuring And Managing Power

You can use the web-based and RACADM interfaces to manage and configure power controls on the CMC, as outlined
in the following sections. For more information on the various power management options, see the CMC Users Guide at
The CMCs power management service optimizes power consumption for the entire chassis (the chassis, servers, I/O
modules, iKVM, CMC, and PSUs) and re-allocates power to different modules based on the demand.
NOTE: To perform power management actions, you must have Chassis Control Administrator privileges.
1.
2.
3.
Click the Power Management tab. The Power Budget Status page is displayed.
4.
Click the Configuration sub-tab. The Budget/Redundancy Configuration page is displayed.
5.
Configure the power budget and redundancy settings based on the components in the enclosure and your needs.
6.
Click Apply to save your changes.
Installing Or Updating The CMC Firmware

NOTE: It is normal for some or all of the fan units to spin at 100 percent during CMC or iDRAC firmware updates on
a server.
29
NOTE: In a redundant CMC configuration, care must be taken to update CMC firmware on both modules. Failure to
do so may cause unexpected behavior during a CMC failover or failback. Use the following procedure for
redundant CMC deployments.
1.
Locate the secondary or standby CMC by using the RACADM getsysinfo command, or by using the Chassis
Summary page in the web-based interface. Visually, the status indicator is solid blue on the primary or active CMC
module and off on the standby or secondary CMC.
2.
Update the firmware on the standby CMC first, using the web-based interface or RACADM.
3.
Verify that the secondary or standby CMCs firmware is at the requested level with the getsysinfo command or
using the web-based interface.
4.
After the standby CMC has rebooted, update the firmware on the active or primary CMC. Allow 10 minutes for the
standby CMC to boot.
5.
Verify that the active or primary CMC firmware is at the requested level using the getsysinfo command or using
the web-based interface.
6.
Once both CMCs are updated to the same firmware revision, use the cmcchangeover command to reset the
CMC in the left slot as primary.
Downloading The CMC Firmware

Before beginning the firmware update, download the latest firmware version from support.dell.com, and save it to your
local system. The following software components are included with your CMC firmware package:
Compiled CMC firmware code and data
Web-based interface, JPEG, and other user interface data files
Default configuration files
Use the Firmware Update page to update the CMC firmware to the latest revision. When you run the firmware update,
the update retains the current CMC settings.
NOTE: The firmware update, by default, retains the current CMC settings. During the update process, you have the
option to reset the CMC configuration settings back to the factory default settings.
Updating The CMC Firmware Using The Web-Based Interface

1.
2.
Click Chassis in the system tree.
3.
Click the Update tab. The Updatable Components page is displayed.
4.
On the Updatable Components page, click the CMC name. The Firmware Update page is displayed.
5.
In the Value field, type the path on your management station or shared network where the firmware image file
resides, or click Browse to navigate to the file location.
NOTE: The default CMC firmware image name is firmimg.cmc and this filename must not be changed. Ensure
that you keep different firmware revisions separated as the file name always remains the same.
6.
Click Update. A dialog box prompts to confirm the action.
7.
Click Yes to continue. The firmware transfer process begins and the status displays the message Firmware
Update in Progress. After the CMC update is complete, the CMC is reset and you must refresh the User
Interface page to log in again.
30
Updating The CMC Firmware Using RACADM

1.
Open a CMC command line console and log in.
2.
Type:
racadm fwupdate -g -u - a <TFTP server IP address> -d <filepath> -m <cmcactive|cmc-standby>
For complete instructions on how to configure and operate the CMC module, see the latest CMC User's Guide at
Configuring The Optional iKVM Switch Module

Updating The iKVM Firmware
NOTE: The iKVM resets and becomes temporarily unavailable after the firmware has been uploaded successfully.
1.
2.
3.
Click the Update tab. The Updatable Components page is displayed.
4.
Click the iKVM name. The Firmware Update page is displayed.
5.
In the Value field, type the path on your management station or shared network where the firmware image file
resides, or click Browse to navigate to the file location.
NOTE: The default iKVM firmware image name is ikvm.bin. However, the iKVM firmware image name can be
renamed. If you are unable to locate ikvm.bin, verify if another user has renamed the file.
6.
Click Update. A dialog box prompts you to confirm the action.
7.
Click Yes to continue.
When the update is complete, the iKVM resets.
Tiering The Avocent iKVM Switch From A Digital KVM Switch

The iKVM module may also be tiered from a digital KVM switch such as the Dell 2161DS-2 or 4161DS, or a supported
Avocent digital KVM switch. Many switches may be tiered without the need for a Server Interface Pod (SIP).
The cabling requirements for various external digital KVM switches are as follows:
Dell PowerConnect 2161DS, 4161DS, 2161DS-2, 2321DS (version 1.3.40.0 or later) or Avocent DSR x02x (except
1024), x03x (version 3.6 or later): Seamless tiering using ACI port and Cat 5 cable
Avocent DSR 800, x16x, x010, 1024: Avocent USB SIP (DSRIQ-USB) with Cat 5 cable
To tier the iKVM module from a Dell 2161DS, 180AS, or 2160AS console switch:
If the switch does not require a SIP to connect to the iKVM , connect a Cat 5 (or newer) cable to the RJ-45 ACI
port on the iKVM module. Connect the other end of this cable to the ARI port on the external switch.
If the switch requires a USB SIP, connect an Avocent USB SIP to the iKVM, then connect a Cat 5 (or newer)
cable to the SIP. Connect the other end of this cable to the ARI port on the external switch.
Once the KVM switch is connected, the server modules are displayed in OSCAR.
NOTE: You must also re-synchronize the server list from the Remote Console Switch software to view the list of
blades.
31
Tiering The Avocent iKVM Switch From An Analog KVM Switch

The Avocent iKVM switch can be tiered from analog KVM switches such as the Dell 2160AS and 180AS, as well as many
Avocent analog KVM switches. Many switches may be tiered without the need for a SIP.
The cabling requirements for specific external switches are as follows:
Dell PowerConnect 180AS, 2160AS (version 1.0.3.2 or later) or Avocent Autoview 2020, 2030 (version 1.6.0.4 or
later): Seamless tiering using ACI port and Cat 5 cable
Avocent Autoview 1400, 1500, 2000, 1415, 1515, 2015u: Avocent USB SIP (DSRIQ-USB) required with Cat 5 cable
Before connecting the iKVM switch to a supported analog switch, you must set the display in slot order, and set the
Screen Delay Time to 1 or more seconds:
1.
Press <Prnt Scrn> to launch the iKVM Switch OSCAR.
2.
Click Setup Menu. The Menu dialog box is displayed.
3.
Select Slot to display servers numerically by slot number.
4.
Set a screen delay time of at least 1 second.
5.
Click OK.
Setting the Screen Delay time to 1 second allows you to soft switch to a server without launching OSCAR.
NOTE: Soft switching allows you to switch servers using a hot key sequence. To soft switch to a server, press
<Prnt Scrn> and type the first few characters of its name or number. If you have a Delay Time set and you press
the key sequences before that time has elapsed, OSCAR does not display.
Configuring The Analog Switch

1.
Press <Prnt Scrn> to launch the iKVM Switch OSCAR.
2.
Click Setup Devices Device Modify.
3.
Select the 16-port option to match the number of blades in your system.
4.
Click OK to exit OSCAR.
5.
Press <Prnt Scrn> to verify that the settings have taken effect. The slot number of the blade to which the iKVM
switch is now attached must be expanded to display each of the slot locations of the blades in the system. For
instance, if the iKVM switch is attached to slot 1, it must be displayed as 01-01 to 01-16.
6.
Connect the Avocent iKVM switch to a supported analog switch:
If the switch does not require a SIP to connect to the iKVM, connect a Cat 5 (or newer) cable to the RJ-45 ACI port
on the iKVM module. Connect the other end of this cable to the ARI port on the external switch.
If the analog switch requires a USB SIP, connect an Avocent USB SIP to the iKVM, then connect a Cat 5 (or newer)
cable to the SIP. Connect the other end of this cable to the ARI port on the external switch.
7.
Connect both the analog switch and the system to an appropriate power source.
8.
Turn on the system.
9.
Turn on the external analog switch.

NOTE: If the external analog switch is powered up before the system, it may result in only one blade being
displayed in the analog switch OSCAR, instead of 16. If this behavior occurs, shut down and restart the switch so
that the entire complement of blades is recognized.
32
NOTE: In addition to the steps outlined above, some external analog switches may require you to perform
additional steps to ensure that the iKVM switch blades are displayed in the external analog switch OSCAR. For
more information, see the external analog switch documentation.
Resynchronizing The Server List At The Remote Client Workstation

Once the iKVM module is connected, the blades are displayed in OSCAR. You must re-synchronize the servers on any
remote workstation to ensure that the blades are available to any remote users connected to the console switch through
the Remote Console Switch software.
NOTE: This procedure only re-synchronizes one remote client workstation. With multiple client workstations, save
the re-synchronized local database and load it into the other client workstations to ensure consistency.
To re-synchronize the server listing:
1.
Click Resync in the Server category of the Management panel. The resync wizard launches.
2.
Click Next. A warning message is displayed indicating that the database will be updated to match the current
configuration of the console switch. Your current local database names will be overwritten with the switch names.
To include unpowered SIPs in the re-synchronization, select the Include Offline SIPs check box.
3.
Click Next. A Polling Remote Console Switch message box is displayed with a progress bar indicating that the
switch information is being retrieved.
4.
If no changes were detected in the appliance, a completion dialog box is displayed with this information. If server
changes were detected, then the Detected Changes dialog box is displayed.
5.
Click Next to update the database.

If a cascade switch was detected, the Enter Cascade Switch Information dialog box is displayed.
6.
Select the type of switch connected to the appliance from the drop-down list. If the type you are looking for is not
available, you can add it by clicking Add.
7.
Click Next. The completion dialog box is displayed.
8.
Click Finish to exit.
9.
Start up the analog switch and the system.
Viewing And Selecting Servers

Use the OSCAR Main dialog box to view, configure, and manage servers in the M1000e enclosure through the iKVM. You
can view the servers by name or by slot. The slot number is the chassis slot number the server occupies. The Slot
column indicates the slot number in which a server is installed.
NOTE: Server names and slot numbers are assigned by the CMC.
NOTE: If you have enabled access to the CMC though the iKVM, an additional option, Dell CMC Console, is
displayed.
To access the Main dialog box, press <PrintScreen> to launch the OSCAR interface. The Main dialog box is displayed.
or
If a password has been assigned, the Password dialog box is displayed. Type your password and click OK. The Main
dialog box is displayed.
33
FlexAddress
The FlexAddress feature allows server modules to replace the factory assigned World Wide Name and Media Access
Control (WWN/MAC) network IDs with WWN/MAC IDs provided by the chassis. FlexAddress is delivered on a Secure
Digital (SD) card that must be inserted into the CMC to provide the chassis-assigned WWN/MAC IDs.
Every server module is assigned unique WWN and MAC IDs as part of the manufacturing process. Before the
FlexAddress feature was introduced, if you had to replace one server module with another, the WWN/MAC IDs would
change and Ethernet network management tools and SAN resources would need to be reconfigured to be aware of the
new server module.
FlexAddress allows the CMC to assign WWN/MAC IDs to a particular slot and override the factory IDs. If the server
module is replaced, the slot-based WWN/MAC ID remains the same. This feature eliminates the need to reconfigure
Ethernet network management tools and SAN resources for a new server module.
Additionally, the override action only occurs when a server module is inserted in a FlexAddress enabled chassis; no
permanent changes are made to the server module. If a server module is moved to a chassis that does not support
FlexAddress, the factory assigned WWN/MAC IDs are used.
Prior to installing FlexAddress, you can determine the range of MAC addresses contained on a FlexAddress feature card
by inserting the SD card into an USB Memory Card Reader and viewing the file pwwn_mac.xml. This clear text XML file
on the SD card contains an XML tag mac_start, which is the first starting hex MAC address that will be used for this
unique MAC address range. The mac_count tag is the total number of MAC addresses that the SD card allocates. The
total MAC range allocated can be determined by:
<mac_start> + 0xCF (208 - 1) = mac_end
For example:
(starting_mac)00188BFFDCFA + 0xCF =
(ending_mac)00188BFFDDC9
NOTE: To prevent modifying any of the contents accidentally, you must lock the SD card prior to inserting in the
USB "Memory Card Reader". You must then unlock the SD card before inserting it into the CMC.
For more information on the FlexAddress feature, see the following resources:
The CMC Secure Digital (SD) Card Technical Specification document at support.dell.com/manuals
The Help link in the CMC web interface
The FlexAddress information in the CMC Users Guide at support.dell.com/manuals
FlexAddress Plus
FlexAddress Plus expands the number of MAC addresses to 3136 from the original FlexAddress pool of 208.
FlexAddress Plus is provided on the FlexAddress Plus Secure Digital (SD) card along with the FlexAddress feature.
NOTE: The SD card labeled FlexAddress only contains FlexAddress and the card labeled FlexAddress Plus contains
FlexAddress and FlexAddress Plus. The card must be inserted into the CMC to activate the feature.
34
Configuring The I/O Modules
Network Information
You can configure your I/O switch modules using:
CMC web-based interface.

NOTE: The default IP address for the CMC is 192.168.0.120.
CMC CLI using serial console redirection.
Direct access to the I/O module serial port (if supported).
I/O module default IP address (if supported).
I/O Connectivity
The enclosure supports three layers of I/O fabric, selectable between combinations of Ethernet, fibre-channel, and
Infiniband modules. You can install up to six hot-swappable I/O modules in the enclosure, including fibre channel
switches, fibre-channel pass-throughs, Infiniband switches, Ethernet switches, and Ethernet pass-through modules.
General I/O Module Configuration Guidelines
If an I/O module is installed in Fabric B or Fabric C, at least one blade must have a matching mezzanine card
installed to support data flow to that I/O module.
If a blade has an optional mezzanine card installed in a Fabric B or Fabric C card slot, at least one corresponding
I/O module must be installed to support data flow to that fabric.
Modules may be installed in Fabrics B and C independently (you do not need to install modules in Fabric B
before installing modules in the Fabric C slots).
Slots A1 and A2 only support Ethernet I/O modules. This fabric type is hardset to Ethernet for these slots and
cannot support fibre channel, Infiniband, or other fabric type modules.
Fabrics A, B, and C can support Ethernet fabric-type modules.
To enable switch configuration prior to blade imaging, I/O modules are allowed to power-up before a blade is
inserted in the enclosure.
Fabric A
Fabric A is a redundant Gb Ethernet fabric, supporting I/O module slots A1 and A2. The integrated Ethernet controllers in
each blade dictate Fabric A as an Ethernet-only fabric.
NOTE: Fabric A supports KR (10 Gbps standard).
NOTE: Modules designed specifically for Fabric B or Fabric C cannot be installed in slots A1 or A2, as indicated by
the color-coded labeling on the faceplate of each module.
35
Fabric B
Fabric B is a 1 to 40 Gb/sec redundant fabric, supporting I/O module slots B1 and B2. Fabric B currently supports 1 Gb or
10 Gb Ethernet, DDR/QDR Infiniband, and 4 Gbps or 8 Gbps fibre channel modules. Additional fabric types may be
supported in the future.
NOTE: Fabric B supports up to 16 Gbps fibre channel, Infiniband FDR (14 Gbps standard), and KR (10 Gbps
standard).
To communicate with an I/O module in the Fabric B slots, a blade must have a matching mezzanine card installed in a
Fabric B mezzanine card location.
Modules designed for Fabric A may also be installed in the Fabric B slots.
Fabric C
Fabric C is a 1 to 40 Gb/sec redundant fabric, supporting I/O module slots C1 and C2. Fabric C currently supports 1 Gb or
10 Gb Ethernet, DDR/QDR Infiniband, and 4 Gbps or 8 Gbps fibre channel modules. Additional fabric types may be
supported in the future.
NOTE: Fabric C supports up to 16 Gbps fibre channel, Infiniband FDR (14 Gbps standard), and KR (10 Gbps
standard).
To communicate with an I/O module in the Fabric C slots, a blade must have a matching mezzanine card installed in a
Fabric C mezzanine card location.
Modules designed for Fabric A may also be installed in the Fabric C slots.
Port Auto-Disablement in Quad-Port Network Daughter Card (Dell

PowerEdge M710HD Only)
Systems installed with quad-port Network Daughter Card support a Port Auto-Disablement feature. This feature disables
the third (NIC3) and fourth (NIC4) ports of a quad-port network daughter card during system boot, if the corresponding
I/O module installed in the chassis Fabric A slots does not support quad-port mapping. This behavior is limited to Fabric
A slots only and is automatically enabled or disabled depending on the type of I/O module installed.
NOTE: A quad-port network daughter card must be used with a 48-port switch module (32 internal ports) for all the
ports to be active.
NOTE: LOM firmware updates are applied only to the enabled ports on a quad-port network daughter card.
The following table provides an overview of the configurations that enable or disable the NIC3 and NIC4 ports of a quadport network daughter card.
Table 1. Port Auto-Disablement Decision Table
IOM Slot A1
IOM Slot A2
NIC3 and NIC4 (Enabled/

Disabled)
Port Auto-Disablement
Empty
Empty
Enabled
Inactive
Empty
Dual Port
Disabled
Active
Empty
Quad or Greater Port
Enabled
Inactive
Dual Port
Empty
Disabled
Active
36
IOM Slot A1
IOM Slot A2
NIC3 and NIC4 (Enabled/

Disabled)
Port Auto-Disablement
Dual Port
Dual Port
Disabled
Active
Dual Port
Enabled
Inactive
Empty
Enabled
Inactive
Dual Port
Enabled
Inactive
Enabled
Inactive
Mezzanine Cards
PowerEdge M610x Only
PowerEdge M610x supports two mezzanine cards. Mezzanine cards can be installed in both the slots on the midplane
interface card.
NOTE: PowerEdge M610x is a full-height blade but supports only two mezzanine cards in the expansion bay. The
two mezzanine slots on the M610x system board (MEZZ2_FAB_B and MEZZ1_FAB_C) are reserved for the
mezzanine interface card.
Full-Height Blades
Full-height blades support four mezzanine cards:
Slot Mezz1_Fabric_C and slot Mezz3_Fabric_C support Fabric C. They must match the fabric type of the I/O
modules installed in I/O module slots C1 and C2.
Slot Mezz2_Fabric_B and slot Mezz4_Fabric_B support Fabric B. They must match the fabric type of the I/O
modules installed in I/O module slots B1 and B2.
Half-Height Blades
Half-height blades support two mezzanine cards:
Mezzanine card slot C supports Fabric C. This card must match the fabric type of I/O modules installed in I/O
module slots C1 and C2.
Mezzanine card slot B supports Fabric B. This card must match the fabric type of I/O modules installed in I/O
module slots B1 and B2.
The following table shows various supported combinations of mezzanine cards and I/O modules.
Table 2. Supported I/O Module Configurations
Fabric A
Fabric B Mezzanine
Card
Fabric C Mezzanine
Card
I/O Bay A1, A2
I/O Bay B1, B2
I/O Bay C1, C2
Standard
None
Integrated LOM
None
Ethernet
None
switch module
or passthrough
module
Standard
Ethernet mezzanine
Integrated LOM card
None
Ethernet
Ethernet
None
switch module switch module
None
37
Fabric A
Fabric B Mezzanine
Card
Fabric C Mezzanine
Card
I/O Bay A1, A2
I/O Bay B1, B2
or passthrough
module
or passthrough
module
I/O Bay C1, C2
Standard
None
Integrated LOM
Infiniband mezzanine
card
Ethernet
None
switch module
or passthrough
module
Infiniband
switch module
Standard
Ethernet mezzanine
Integrated LOM card
Ethernet mezzanine
card
Ethernet
switch module
or passthrough
module
Ethernet
switch module
or passthrough
module
Ethernet switch
module or
pass-through
module
Standard
Fibre channel
Integrated LOM mezzanine card
card
Ethernet
switch module
or passthrough
module
Fibre channel
switch or
pass-through
module
Infiniband
switch module
Standard
None
Integrated LOM
Fibre channel
mezzanine card
Ethernet
None
switch module
or passthrough
module
Standard
Fibre channel
Fibre channel
mezzanine card
Ethernet
switch module
or passthrough
module
Ethernet
Fibre channel
switch module switch or passor passthrough module
through
module
Standard
Ethernet mezzanine
Integrated LOM card
Fibre channel
mezzanine card
Ethernet
switch module
or passthrough
module
Ethernet
Fibre channel
switch module switch or passor passthrough module
through
module
Standard
Integrated LOM card
card
Ethernet
Infiniband
Infiniband
switch module switch module switch module
or passthrough
module
Standard
Integrated LOM card
Ethernet mezzanine
card
Ethernet
Infiniband
switch module switch module
or passthrough
module
38
Fibre channel
switch or passthrough module
Ethernet switch
module or
pass-through
module
Fabric A
Fabric B Mezzanine
Card
Standard
Fibre channel
Fabric C Mezzanine
Card
I/O Bay A1, A2
I/O Bay B1, B2
I/O Bay C1, C2
Ethernet mezzanine
card
Ethernet
switch module
or passthrough
module
Fibre channel
switch or
pass-through
module
Ethernet switch
module or
pass-through
module
I/O Module Port MappingFull-Height Blades

NOTE: The I/O port mappings in the following sections are applicable only to the I/O Pass-Through Modules.
Standard LOM (Dual-Port) Mapping

Each LOM has two port connections. For a full-height blade in bay n:
Integrated LOM1, connection 1 connects to I/O module A1, port n.
Integrated LOM1, connection 2 connects to I/O module A2, port n.
Integrated LOM2, connection 1 connects to I/O module A1, port n+8.
Integrated LOM2, connection 2 connects to I/O module A2, port n+8.
For example, in a full-height blade in slot 5:
Integrated LOM1 connection 1 connects to I/O module A1, port 5.

NOTE: Even though PowerEdge M610x is a full-height blade system, only one network controller (LOM1) is
available.
For PowerEdge M610x blade in bay n, the integrated NIC connects to I/O module A1, port n and I/O module A2, port n.
Dual-Port Mezzanine Cards

Each mezzanine card has two port connections. For a full-height blade in bay n:
Mezzanine card 1, connection 1 connects to I/O module C1, port n. Mezzanine card 1, connection 2 connects to
I/O module C2, port n.
Mezzanine card 2, connection 1 connects to I/O module B1, port n. Mezzanine card 2, connection 2 connects to
I/O module B2 port n.
Mezzanine card 3, connection 1 connects to I/O module C1, port n+8. Mezzanine card 3, connection 2 connects
to I/O module C2 port n+8.
Mezzanine card 4, connection 1 connects to I/O module B1, port n+8. Mezzanine card 4, connection 2 connects
to I/O module B2 port n+8.
For example, in a full-height blade:
Mezzanine card 3 connection 1 connects to I/O module C1, port 13.
Mezzanine card 3 connection 2 connects to I/O module C2 port 13.
The following table shows the port number assignments for the eight possible full height blade locations.
39
NOTE: Even though PowerEdge M610x is a full blade system, only two mezzanine card slots (MEZZ1_FAB_C1 and
MEZZ2_FAB_B1) in the expansion bay are available for use. The other two slots on the system board
(MEZZ1_FAB_C and MEZZ2_FAB_B) are occupied by the mezzanine interface card which provides connectivity
between the PCIe expansion-card riser and the system board.
For PowerEdge M610x, in bay n:
Mezzanine card B (in the expansion bay) connects to I/O module B1, port n+8 and I/O module B2, port n+8.
Mezzanine card C (in the expansion bay) connects to I/O module C1, port n+8 and I/O module C2, port n+8.
Table 3. Example of I/O Module Port Assignments - PowerEdge M610x in Slot 2
Blade 2
I/O Module
A1
B1
Mezzanine Card C
Mezzanine Card B
C1
C2
Port 10
Port 10
Port 10
Figure 14. Example of PowerEdge M610x Port Mapping Blade 2
40
B2
Port 10
A2
Table 4. I/O Module Port Assignments - Full-Height Blades (not applicable for PowerEdge M610x)
Blade 1
I/O Module
B1
Mezz1_Fab_C
Mezz2_Fab_B
C2
Port 1
Port 1
Port 1
Mezz3_Fab_C
Mezz4_Fab_B
C1
Port 1
Port 9
Port 9
I/O Module
B1
Mezz1_Fab_C
C1
C2
Port 2
Port 2
Port 2
Mezz3_Fab_C
Mezz4_Fab_B
Port 10
Port 10
I/O Module
Mezz1_Fab_C
C1
C2
Port 3
Port 3
Port 3
Mezz3_Fab_C
Port 11
Port 11
I/O Module
Mezz1_Fab_C
C1
C2
Port 4
Port 4
Port 4
Mezz3_Fab_C
Port 12
Port 12
Port 12
Port 12
I/O Module
B1
Mezz1_Fab_C
C1
C2
Port 5
Port 5
Port 5
Mezz3_Fab_C
Mezz4_Fab_B
B2
Port 4
Blade 5
Mezz2_Fab_B
Port 11
Port 11
B1
Mezz4_Fab_B
B2
Port 3
Blade 4
Mezz2_Fab_B
Port 10
Port 10
B1
Mezz4_Fab_B
B2
Port 2
Blade 3
Mezz2_Fab_B
Port 9
Port 9
Blade 2
Mezz2_Fab_B
B2
Port 5
Port 13
Port 13
B2
Port 13
Port 13
41
Blade 6
I/O Module
B1
Mezz1_Fab_C
Mezz2_Fab_B
C2
Port 6
Port 6
Port 6
Mezz3_Fab_C
Mezz4_Fab_B
C1
Port 6
Port 14
Port 14
I/O Module
B1
Mezz1_Fab_C
C1
C2
Port 7
Port 7
Port 7
Mezz3_Fab_C
Mezz4_Fab_B
Port 15
Port 15
Port 15
Port 15
I/O Module
B1
Mezz1_Fab_C
C1
C2
Port 8
Port 8
Port 8
Mezz3_Fab_C
Mezz4_Fab_B
B2
Port 7
Blade 8
Mezz2_Fab_B
Port 14
Port 14
Blade 7
Mezz2_Fab_B
B2
Port 8
Port 16
Port 16
B2
Port 16
Port 16
The following figure shows the port connections for a full-height blade in bay 3 with four mezzanine cards.
42
Figure 15. Example of Full-Height Blade Port Mapping Blade 3 (not applicable for PowerEdge M610x)
Quad-Port Mezzanine Cards

The following table illustrates the I/O module port mapping for full-height blades with quad-port mezzanine cards.
NOTE: For a detailed mapping of each PowerEdge system, see Quadport Capable Hardware for the M1000e
Modular Chassis at support.dell.com/manuals.
Blade n and Blade (n + 8)
I/O Module
NOTE: n denotes a
B1
variable value from 1
to 8.
Mezz_FAB_B_Blade
n_Port1
Mezz_FAB_B_Blade
n_Port2
C1
C2
B2
Portn
Portn
43
Blade n and Blade (n + 8)
I/O Module
NOTE: n denotes a
B1
variable value from 1
to 8.
Mezz_FAB_B_Blade
n_Port3
C1
C2
Port(n+16)
Port(n+16)
Mezz_FAB_B_Blade
n_Port4
Portn
Mezz_FAB_C_Blade
n_Port1
Portn
Mezz_FAB_C_Blade
n_Port2
Port(n+16)
Mezz_FAB_C_Blade
n_Port3
Port(n+16)
Mezz_FAB_C_Blade
n_Port4
Mezz_FAB_B_Blade n
+8_Port1
Port(n+8)
Port(n+8)
Mezz_FAB_B_Blade n
+8_Port2
Mezz_FAB_B_Blade n
+8_Port3
Port(n+24)
Port(n+24)
Mezz_FAB_B_Blade n
+8_Port4
Mezz_FAB_C_Blade n
+8_Port1
Port(n+8)
Port(n+8)
Mezz_FAB_C_Blade n
+8_Port2
Mezz_FAB_C_Blade n
+8_Port3
Mezz_FAB_C_Blade n
+8_Port4
B2
Port (n+24)
Port(n+24)
NOTE: Even though PowerEdge M610x is a full blade system, only two mezzanine card slots (MEZZ1_Fab_C1 and
MEZZ2_FAB_B1) in the expansion bay are available for use. The other two slots on the system board
(MEZZ1_FAB_C and MEZZ2_FAB_B) are occupied by the mezzanine interface card which provides connectivity
between the PCIe expansion-card riser and the system board.
The following table illustrates the I/O module port mapping for PowerEdge M610x in bay n.
44
Table 6. Example of I/O Module Port Assignments - PowerEdge M610x Blade 1
Blade 1
I/O Module
A1
B1
C1
C2
Mezzanine Card C (port 1

and port 2)
Port 9
Port 9
Mezzanine Card C (port 3

and port 4)
Port 25
Port 25
B2
Mezzanine Card B (port

1 and port 2)
Port 9
Port 9
Mezzanine Card B (port

1 and port 2)
Port 25
Port 25
A2
I/O Module Port MappingHalf-Height Blades

Standard LOM (Dual-Port) and Network Daughter Card (Quad-Port) Mapping
Each standard LOM has two port connections. For a half-height blade in bay n:
Integrated LOM, connection 1 connects to I/O module A1, port n. Integrated LOM, connection 2 connects to I/O module
A2, port n.
Half-height blades with network daughter card (M710HD) hosts two network controllers (LOM1 and LOM2), each with
two port connections. For a half-height blade in bay n:
LOM1, connection 1 connects to I/O module A1, port n. LOM1, connection 2 connects to I/O module A2, port n.
LOM2, connection 1 connects to I/O module A1, port n+16. LOM2, connection 2 connects to I/O module A2, port n
+16.
NOTE: If the I/O modules A1 and A2 are not quad-port capable, then the LOM2 ports (NIC3 and NIC4) gets disabled
during system boot.
For example, in a half-height blade, in slot 5:
Dual-Port Mezzanine Cards

For a half-height blade in bay n:
The integrated NIC connects to I/O module A1, port n and I/O module A2, port n.
Mezzanine card B connects to I/O module B1, port n and I/O module B2, port n.
Mezzanine card C connects to I/O module C1, port n and I/O module C2, port n.
For example, in a blade in slot 12, the integrated NIC connects to I/O module A1, port 12 and I/O module A2, port 12.
45
Table 7. Example of I/O Module Port Assignments - Half-Height Blade 1
Blade 1
I/O Module
A1
Integrated NIC
B1
C1
C2
B2
Port 1
Port 1
Mezzanine Card C
Mezzanine Card B
A2
Port 1
Port 1
Port 1
Port 1
The following figure shows the port connections for a half-height blade in bay 1 with two mezzanine cards.
Figure 16. Example of Half-Height Blade Port Mapping
Quad-Port Mezzanine Cards

The following table illustrates the I/O module port mapping for a half-height blade with the quad-port mezzanine card. In
the following table, n denotes a variable value from 1 to 16.
46
NOTE: For a detailed mapping of each PowerEdge system, see Quadport Capable Hardware For the M1000e
Modular Chassis at support.dell.com/manuals.
Blade n
I/O Module
A1
Integrated LOM1
B1
C1
C2
B2
Port n
Port n
Integrated LOM2
Mezz_FAB_B_Blade
n_Port1
Port n
Port n
Mezz_FAB_B_Blade
n_Port2
Mezz_FAB_B_Blade
n_Port3
A2
Port (n+16)
Port (n+16)
Mezz_FAB_B_Blade
n_Port4
Mezz_FAB_C_Blade
n_Port1
Port n
Port n
Mezz_FAB_C_Blade
n_Port2
Mezz_FAB_C_Blade
n_Port3
Port (n+16)
Mezz_FAB_C_Blade
n_Port4
Port (n+16)
I/O ModulesSwitches
Configuring A Switch Module Network Ethernet Port Using The Web-Based Interface
You can use the CMC web-based interface to configure an I/O modules Ethernet port.
NOTE: Use this procedure to configure the switchs out-of-band Ethernet port. The switchs in-band management
IP address is configured through the switchs external ports. These two IP addresses must be different, and on
different networks.
NOTE: To change settings on the I/O module configuration page, you must have Fabric Administrator privileges for
the particular Fabric in which the module is installed
NOTE: The network IP address set on the I/O module by the CMC is not saved to a configuration file. To save the IP
address configuration permanently, use the connect switch-n RACADM command, or use a direct interface
to the I/O module GUI.
NOTE: Do not attempt to configure I/O module network settings for Ethernet pass-through or Infiniband switches.
1.
2.
Select I/O Modules in the Chassis menu in the system tree.
47
3.
Select the Setup tab. The Configuring I/O Modules Network Settings page is displayed.
4.
Configure the switch for integration into your network.
Select DHCP Mode Enabled if your network uses a DHCP server to assign IP addresses.
If your network uses static IP addressing, enter an IP address, subnet mask and gateway.
5.
Click Apply.
6.
Click the Deploy sub-tab.
After all I/O modules have been configured and connected, the enclosures blades can be inserted and booted with full
network communication.
Brocade M6505 16 Gbps FC SAN I/O Module

The Brocade M6505 16 Gbps FC I/O module includes eight external fibre channel ports, 16 internal ports, and one serial
port with an RJ-45 connector. The external fibre channel ports operate at 4 Gbps, 8 Gbps, or 16 Gbps. Internal ports
support speeds of 8 Gbps and 16 Gbps.
NOTE: This module can be upgraded to 24 ports using a Ports on Demand (POD) license.
This fibre channel switch module supports hot-pluggable Small Form Factor Pluggable plus (SFP+) optical transceivers.
NOTE: To ensure proper functionality, use only SFPs provided with this module.
Figure 17. Brocade M6505 16 Gbps FC SAN I/O Module
1.
2.
3.
4.
48
fibre channel ports (8)

port LED indicators
server management status/indicator LED
power status LED
5. SAN I/O module status indicator

6. serial port (RJ-45 connector)
Cisco Nexus B22 Fabric Extender Module

The Cisco Nexus B22 Fabric Extender module acts as a remote line card for a parent Cisco Nexus switch. This module is
an extension of the parent Cisco Nexus switch fabric. The Fabric Extenders and the parent Cisco Nexus switch together
form a distributed modular system. The Cisco Nexus B22 Fabric Extender connects to the server modules using 10 Gb
Ethernet and consists of eight 10 Gb Ethernet fabric uplinks to the parent Cisco Nexus switch. The Cisco Nexus B22
Fabric Extender module consists of the following:
Sixteen 10 Gb (internal) Ethernet ports

Eight 10 Gb Ethernet SFP + ports
Two single color LEDs per port for external uplink ports
Figure 18. Cisco Nexus B22 Fabric Extender Module
1.
2.
3.
4.
external network ports (8)

port LED indicator
status indicator
identification indicator
Dell PowerEdge M I/O Aggregator Switch

The PowerEdge I/O Aggregator is a layer 2 switch blade with two fixed 40 GbE ports on the base module and provides
support for two optional plug-in modules. The Aggregator runs the Dell Force10 Operating System (FTOS) and
autoconfigures as an unmanaged switch with bridging and multiplexing features.
This module provides:
49
Thirty-two 1/10-Gigabit Ethernet internal ports-each port can operate in either 1 GbE or 10 GbE mode.
An internal Ethernet interface for switch management.
Two fixed 40 GbE ports on the base module. These ports operate in 4 x 10 GbE mode with breakout cables and
support up to eight 10 GbE uplink ports. The 40 GbE ports can be configured as stacking links.
FlexIO plug-in modules in two expansion slots:
Four-port 10 GbE module using SFP+ optics or direct-attach cables (1 m, 3 m, or 5 m DAC)
Four-port 10GBASE-T module using RJ-45 connector (copper) cables
Two-port 40 GbE QSFP+ module for 10 GbE SFP+ connections using 4 x 10 GbE breakout cables.
For additional information about the PowerEdge M I/O Aggregator switch module, see the documentation that shipped
with the module.
Figure 19. Dell PowerEdge M I/O Aggregator Switch
1.
2.
3.
4.
expansion slot 1
expansion slot 0
USB storage port
activity and link LEDs
5. USB console port

6. 40 GbE QSFP+ ports
Dell Force10 MXL 10/40 GbE Switch

The Force10 MXL 10/40 GbE switch module has two fixed 40 GbE ports on the base module and provides support for two
optional plug-in modules. This module provides:
50
Thirty two 1 GbE or 10 GbE internal ports each port can operate in either 1 GbE or 10 GbE mode.
Two native 40 GbE fixed ports on the base module for uplink connections. These ports can be used with 4 x 10G
breakout cables to operate as 10 GbE uplink ports. The native 40 GbE ports can be configured as stacking ports.
10 GbE or 40 GbE external connectivity by using the following plug-in modules in the two expansion slots:
Four-port 10 GbE module using SFP+ optics (SR, LR, or LRM) or direct-attach cables (1 m, 3 m, 5 m DAC)
Four-port 10GBASE-T module using RJ-45 connector (copper) cables
Two-port 40 GbE QSFP+ module for 10 GbE SFP+ connections
For additional information about the Force10 MXL 10/40 GbE switch module, see the documentation that shipped with the
module.
Figure 20. Dell Force10 MXL 10/40 GbE Switch I/O Module
1.
2.
3.
4.
expansion slots (8)

LED status indicators
USB storage port
USB console port
6. power indicator
7. 40 GbE QSFP+ ports (2)
Mellanox M4001F/M4001Q/M4001T Infiniband Switch I/O Module

The Mellanox M4001F/M4001Q/M4001T Infiniband switch delivers 56 Gb/s at FDR speed and 40 Gb/s at QDR and FDR10
speed (full bisectional bandwidth per port). This switch module includes 16 Quad Small Form-factor Pluggable (QSFP)
51
ports on the front panel and 16 internal Infiniband ports. This Infiniband switch module is hot-swappable and may be
installed in Fabrics B or C.
Figure 21. Mellanox M4001F/M4001Q/M4001T Infiniband Switch Module
1. Infiniband QSFP ports (16)

2. LED status/module status indicators
3. serial port (RJ-45 connector)
4. module status indicator

5. power indicator
Dell PowerConnect KR 8024-k Switch

The PowerConnect KR M8024-k switch provides 16 internal 10 GbE ports, four external 10 GbE SFP+ ports, and one 10
GbE expansion slot for 10 GbE external uplinks. The expansion slot on the front panel can support the following modules:
10 Gb Ethernet module with four optical SFP+ connectors
10 Gb Ethernet module with three copper CX4 uplinks
10 Gb Ethernet module with two copper 10GBASE-T uplinks
This switch may be installed in either Fabric B or Fabric C.
52
Figure 22. Dell PowerConnect KR 8024-k Switch
1. SFP+ ports (4)

2. console management connector
4. power indicator
5. expansion slot
Dell PowerConnect M8428-k 10 Gb Converged Network Switch

The Dell PowerConnect M8428-k 10 Gb Converged Network switch module supports FCoE protocols and allows fibre
channel traffic to travel over 10 Gbps Enhanced Ethernet (DCB) networks. This module consists of:
Four 8 Gbps external autosensing fibre channel ports.
Eight 10 Gb Enhanced Ethernet (DCB) optical SFP+ port connectors.
Sixteen internal 10 Gb Enhanced Ethernet (DCB/FCoE) ports that link to the blades in the enclosure.
One serial port with an RJ-45 connector.
This fibre channel switch may be installed in any of the three Fabrics.
For additional information about the Dell PowerConnect M8428-k 10 Gb Converged Network switch module, see the
documentation at support.dell.com/manuals.
53
Figure 23. Dell PowerConnect M8428-k 10 Gb Converged Network Switch
1.
2.
3.
4.
LED status indicators (12)

serial port (RJ-45 connector)
module status indicator
diagnostic status indicator
5. power indicator
6. 8 Gb fibre channel ports (ports 2527 and port 0)
7. 10 GbE ports (ports 1724)
Mellanox M2401G DDR Infiniband Switch I/O Module

The Mellanox M2401G DDR Infiniband switch I/O module includes 24 4x DDR Infiniband ports. Eight ports are external
uplink ports, while 16 internal ports provide connectivity to the blades in the enclosure.
54
Figure 24. Mellanox M2401G DDR Infiniband Switch Module
1. Infiniband ports (8)

2. port link status indicators (8)
3. port activity indicators (8)
4. module diagnostic power indicator

Mellanox M3601Q QDR Infiniband Switch I/O Module

The Mellanox M3601Q QDR Infiniband switch I/O module includes 32 4x QDR Infiniband ports. Of these, 16 ports are
external uplink ports, while 16 internal ports provide connectivity to the blades in the enclosure. This module occupies
two I/O module slots. By default, the M3610Q module plugs into I/O module slot C1, but occupies both slots B1 and C1. It
can also be plugged into I/O module slot B1 (occupying slots A1 and B1) or slot B2 (occupying slots B2 and C2).
55
Figure 25. Mellanox M3601Q QDR Infiniband Switch I/O Module
1. Infiniband ports (16)

2. port link status indicators (16)
3. port activity indicators (16)
4. module diagnostic power indicator

Cisco Catalyst Ethernet Switch I/O Modules

Your system supports three Cisco Catalyst Blade Switch (CBS) versions:
The Cisco 3130G-S switch includes four 10/100/1000 Mb Ethernet uplink ports and two Stackwise Plus ports.
The Cisco CBS 3130X-S switch includes four 10/100/1000 Mb Ethernet uplink ports, two 10 Gb uplink ports, and
two Stackwise Plus ports.
The Cisco CBS 3032 switch includes four 10/100/1000 Mb Ethernet uplink ports.
The two option bays support the following module options:
Cisco X2 10 Gb transceiver modules (CBS 3130X-S only)
Cisco TwinGig converter modules
All three switches include an RJ-45 console connector for switch management. Sixteen internal Gb Ethernet connectors
link to the blades in the enclosure. For additional information about the Cisco CBS Ethernet switch modules, see the
documentation that shipped with the module.
56
Figure 26. Cisco Catalyst Ethernet Switch Module Features
1. Stackwise Plus connectors (not enabled in CBS

3032)
2. 10/100/1000 Mb Ethernet connectors (4)
3. option bays (2)
4. Cisco status indicators
5. mode button
6. console port for switch management

7. power indicator
Dell PowerConnect M6348 1 Gb Ethernet Switch I/O Module

PowerConnect M6348 is a hot-swappable 48-port 1 Gb Ethernet switch. While 16 ports are external uplink ports, the
remaining 32 internal ports provide connectivity to the blades within the enclosure with a maximum bandwidth of 1 Gbps
each. The PowerConnect M6348 switch also supports:
Two integrated 10 Gb Ethernet SFP+ connectors
Two integrated CX4 connectors for stacking or 10 Gb uplinks
One console management connector
It is recommended that you use the PowerConnect M6348 switch with quad-port mezzanine cards for maximum
functionality. The quad-port mezzanine cards and the PowerConnect M6348 Ethernet switch enable an increased
bandwidth (two 1 Gbps lanes), higher port density, and server module consolidation.
57
Figure 27. PowerConnect M6348 1 Gb Ethernet Switch I/O Module Features
1.
2.
3.
4.
standard 10/100/1000 Mb Ethernet connectors (16)

SFP+ connectors (2)
CX4 stacking connectors (2)
console management connector
5. power indicator
Dell PowerConnect M6220 Ethernet Switch I/O Module

The PowerConnect M6220 Ethernet switch module includes four external 10/100/1000 Mbps Ethernet connectors and
one USB type A form factor serial connector. Two option bays support the following modules:
A resilient stacking module with 2 x 24 Gb stacking ports
A 10 Gb Ethernet module with two 10 Gb optical XFP uplinks
A 10 Gb Ethernet module with two copper CX4 uplinks
A 10 Gb Ethernet module with two copper 10GBASE-T uplinks
A 10 Gb Ethernet module with two SFP+ (optical or direct-attach copper) uplinks
Installing two optional modules provides additional stacking and redundancy support. Sixteen internal Gb Ethernet
connectors link to the blades in the enclosure.
For additional information about the PowerConnect M6220 Ethernet switch module, see the documentation that shipped
with the module.
58
Figure 28. PowerConnect M6220 Ethernet Switch I/O Module
1. optional modules (2) (dual 10 Gb Ethernet uplink

module shown)
2. standard 10/100/1000 Mb Ethernet connectors (4)
3. serial connector (USB type-A form factor)
4. power indicator
Dell PowerConnect M8024 10 Gb Ethernet Switch I/O Module

The PowerConnect M8024 switch module incorporates two optional bays that support the following modules:
A 10 Gb Ethernet module with four optical SFP+ connectors
A 10 Gb Ethernet module with three copper CX4 uplinks
A 10 Gb Ethernet module with two copper 10GBASE-T uplinks
The modules can be used in any combination and are sold separately.
You can initially configure the switch using either of two methods:
Connect an external management system to the switch using an optional USB type-A form factor serial cable,
and configure the switch using a terminal application.
Use the iKVM CMC console (17th blade) and the connect switch-n CMC CLI command. For more information,
see the CMC Users Guide at support.dell.com/manuals.
Once an IP address is assigned to the management VLAN or interface and the switch is connected to a management
network, both Telnet and http are available through the network.
59
Figure 29. PowerConnect M8024 10 Gb Ethernet Switch I/O Module
1. optional module with four SFP+ ports

2. optional module with three CX4 ports
3. serial connector for optional USB type-A formfactor cable
4. power indicator
Dell 8/4 Gbps FC SAN Module

The Dell 8/4 Gbps FC SAN module includes 24 total autosensing fibre channel ports (12 ports are enabled in the standard
configuration and 12 additional ports may be enabled as an optional upgrade) and one serial port with an RJ-45
connector. The internal fibre channel ports operate at 8 Gb/s or 4 Gb/s. The external fibre channel ports operate at 8
Gb/s, 4 Gb/s, or 2 Gb/s.
NOTE: CMC firmware version 1.3 is required to support FC8 mezzanine cards and I/O modules.
NOTE: This fibre channel switch module includes Short Wave SFP optical transceivers. To ensure proper
functionality, use only SFPs provided with this module.
NOTE: This module requires a Fibre Channel fabric for support, as it functions in the Access Gateway (NPIV) mode
and cannot be directly connected to a storage array.
60
Figure 30. Dell 8/4 Gbps FC SAN Module
1.
2.
3.
4.

fibre channel port status indicators (8)
fibre channel port speed indicators (8)

6. power indicator
Brocade M5424 FC8 I/O Module

The Brocade M5424 FC8 I/O module includes eight external autosensing fibre channel ports (four ports are enabled in
the standard configuration and four additional ports may be enabled as an optional upgrade), 16 internal ports, and one
serial port with an RJ-45 connector. The external fibre channel ports operate at 8 Gb/sec, 4 Gb/sec, or 2 Gb/sec.
NOTE: CMC firmware version 1.3 is required to support FC8 mezzanine cards and I/O modules.
NOTE: This fibre channel switch module includes Short Wave SFP optical transceivers. To ensure proper
functionality, use only SFPs provided with this module.
61
Figure 31. Brocade M5424 FC8 I/O Module
1.
2.
3.
4.

fibre channel port status indicators (8)
fibre channel port speed indicators (8)

6. power indicator
The following are the I/O module indicators:

Fibre channel
port status
indicator
62
Indicator
Status
Off
No signal carrier
Amber on
Signal present but not online
Green on
Online, but no activity
Green blinking
slowly
Online, but segmented
Green blinking
quickly
Internal loopback
Green flickering
I/O activity on port
Amber blinking
slowly
Port disabled
Fibre channel
port speed
indicator
Module status
indicator
Module power
indicator
Status/
identification
indicator
Indicator
Status
Amber blinking
rapidly
Error or fault with port
Indicator
Status
Off
2 Gb link established
Green on
Amber on
Indicator
Status
Off
Module is off or enclosure power is off
Green on
All ports are ready for use
Amber on
Module is booting, being reset, or ports are offline
Green/amber
blinking
Diagnostic message is in error log, or environmental range is

exceeded
Indicator
Status
Off
Power to the module is off
Green
Module has power
Indicator
Status
Blue on
Normal health
Blue off
Boot in progress
Blue blinking
Identifying module
Amber blinking
Fault condition in module
I/O ModulesPass-Through
Dell 4 Gbps Fibre Channel Pass-Through Module
The 4 Gbps fibre channel pass-through module provides a bypass connection between a fibre channel mezzanine card
in the blade and optical transceivers for direct connection into a fibre channel switch or a storage array. The 16 passthrough ports on this module can negotiate speeds of 1 Gbps, 2 Gbps, or 4 Gbps. The 4 Gbps fibre channel pass-through
module is hot-swappable, and may be installed in Fabric B or Fabric C.
NOTE: To ensure proper functionality, use only the Short Wave SFP transceivers provided with this module.
63
Figure 32. 4 Gbps Fibre Channel Pass-Through Module
1.
2.
3.
4.
SFP fibre channel connectors (16)

fibre channel green/amber indicators (two per port)
power indicator
status/identification indicator
The following are the fibre channel pass-through indicators:

Power Indicator
Off: Power to the module is off

Green: Module has power
Status/
Identification
Indicator
Blue off: Secondary module in a stack

Blue on: Primary module in a stack, if applicable
Amber flashing: Fault condition in module
Fibre Channel
Port Indicators
With Emulex
Mezzanine Card
Installed
Green off, amber off: Mezzanine board failure before POST

Green off, amber on or green off, amber blinking: Mezzanine board failure during POST
Green off, amber flashing irregularly: POST in progress
Green on, amber off or green on, amber on: Mezzanine board failure during operation
Green on, one fast amber blink: 1 Gb link established
Green on, two fast amber blinks: 2 Gb link established
Green on, three fast amber blinks: 4 Gb link established
64
Slow green blinking, amber off: No link established

Slow green blinking, slow amber blinking: Offline for firmware download
Fibre Channel
Port LEDs with
Qlogic Mezzanine
Card Installed
Green off, amber off: Power off

Green off, amber on: Online, 1 Gb or 2 Gb link
Green on, amber off: Online, 4 Gb link
Green off, amber flashing: I/O activity, 1 Gb or 2 Gb
Green flashing, amber off: I/O activity, 4 Gb
Green flashing and amber flashing at same time: Loss of synchronization
Green flashing and amber flashing at different intervals: Firmware error
Off/amber flashing (twice per second): Connection has lost synchronization
Dell 10 GbE KR Pass-Through I/O Module

The 10 GbE KR pass-through module supports 10 Gb connections and provides a direct connection between the optional
internal Ethernet KR mezzanine card or KR network daughter card in the blade and an external Ethernet device. This
module has 16 external SFP+ ports on the front panel and sixteen 10 GbE KR internal ports through the backplane. This
module enables you to use optical SFP+ (short reach or long reach) and direct-attached copper (DCA) SFP+ modules.
The Ethernet pass-through module is hot-swappable and may be installed in Fabric A, B, or C. The pass-through module
does not support 1G mezzanine or network daughter cards in blades.
Figure 33. Dell 10 GbE KR Pass-Through I/O Module
65
1.
2.
3.
4.
SFP+ ports (16)

green/amber indicators (two per port)
power indicator
Dell 10 Gb Ethernet Pass-Through Module II

The Dell 10 Gb Ethernet pass-through module II supports 10 Gb connections and provides a direct connection between
the optional internal Ethernet mezzanine card in the blade and an external Ethernet device. The Ethernet pass-through
modules are hot-swappable and may be installed in Fabric B or Fabric C.
The 10 Gb Ethernet pass-through module II enables you to use optical SFP+ (short reach or long reach) and directattached copper (DCA) SFP+ modules. The Ethernet pass-through module does not support 1G mezzanine or network
daughter cards in blades.
Figure 34. 10 Gb Ethernet Pass-Through Module II
1.
2.
3.
4.
SFP+ ports (16)

green/amber indicators (two per port)
power indicator
10/100/1000 Mb Ethernet Pass-Through I/O Module

The Ethernet pass-through module supports 10/100/1000 Mb connections and provides a direct connection between the
optional internal Ethernet mezzanine card in the blade and an external Ethernet device. The Ethernet pass-through
modules are hot-swappable and may be installed in any of the three Fabrics.
66
NOTE: To ensure proper functionality, use only the SFP transceivers provided with this module.
Figure 35. 10/100/1000 Mb Ethernet Pass-Through I/O Module
1. activity indicators (16)

2. link indicators (16)
3. RJ-45 Ethernet connectors (16)
4. power indicator
NOTE: Connectors on the Ethernet pass-through module correspond directly to the blade number. For example,
blade 5 is connected to port 5 on the Ethernet pass-through module. Integrated network adapter 1 maps to I/O slot
A1. Integrated network adapter 2 maps to I/O slot A2.
67
68
Installing Enclosure Components
NOTE: To ensure proper operation and cooling, all bays in the enclosure must be populated at all times with either
a module or with a blank.
Recommended Tools
You may need the following items to perform the procedures in this section:
#1 and #2 Phillips screwdrivers
T8, T10, T15, and T20 Torx drivers
Wrist grounding strap
Removing And Installing A Blade

CAUTION: Many repairs may only be done by a certified service technician. You should only perform
troubleshooting and simple repairs as authorized in your product documentation, or as directed by the online or
telephone service and support team. Damage due to servicing that is not authorized by Dell is not covered by your
warranty. Read and follow the safety instructions that came with the product.
NOTE: These procedures are applicable only for full-height and half-height blades. For information on removing
and installing quarter-height blades from a sleeve, see the blade's Owner's Manual at support.dell.com/manuals.
Removing A Blade
1.
Power down the blade using the operating system commands or the CMC, and ensure that the blade's power is off.
When a blade is powered off, its front-panel power indicator is off.
CAUTION: Before removing full-height blades 3 or 4 or half-height blades 11 or 12, rotate the LCD panel to the
storage position to prevent accidental damage to the LCD screen.
2.
Press the release button on the blade handle.
3.
Pull out the blade handle to unlock the blade from the enclosure.
CAUTION: If you are permanently removing the blade, install a blade blank(s). Operating the system for
extended periods of time without a blade blank installed can cause the enclosure to overheat.
NOTE: A full-height blade requires two blade blanks.
4.
Slide the blade out of the enclosure.

CAUTION: To protect the I/O connector pins, install the I/O connector covers any time a blade is removed from
the enclosure.
NOTE: A full-height blade requires four connector covers and a half-height blade requires two connector
covers.
5.
Install the I/O connector cover over the I/O connector.
69
Figure 36. Removing and Installing a Half-Height Blade
1. blade handle
2. release button
3. blade
4. guide rail on enclosure

5. guide rail on blade (or blade blank)
Figure 37. Removing and Installing a Full-Height Blade
1. blade handle
70
2. release button
3. blade
4. guide rail on enclosure
5. guide rail on blade (or blade blank)
Installing A Blade
1.
If you are installing a new blade, remove the plastic cover from the I/O connector(s) and save for future use.
2.
Orient the blade so that the blade handle is on the left side of the blade.
CAUTION: If you are installing a full-height blade in bays 3 or 4 or a half-height blade in bays 11 or 12, rotate
the LCD module to the horizontal storage position to prevent accidental damage to the LCD screen.
3.
To install a full-height blade or a half-height blade in bays 1 through 8, align the guide rail on the upper edge of the
blade so that the rail fits between the plastic guides on the enclosure.
4.
To install a half-height blade in one of the eight lower bays (bays 9 through 16), align the edge of the blade with the
guide rail on the floor of the M1000e enclosure.
5.
Slide the blade into the enclosure until the handle engages and locks the blade in place.
Power Supply Modules

The Dell PowerEdge M1000e enclosure supports up to six hot-swappable power supply modules, accessible from the
enclosure back panel.
NOTE: The power supply modules have internal fans that provide thermal cooling to these modules. A power
supply module must be replaced if an internal fan failure occurs.
The CMC module controls power management for the system. You can program the CMC to configure the power budget,
redundancy, and dynamic power of the entire enclosure (chassis, servers, I/O modules, iKVM, CMC, and power
supplies). The power management service optimizes power consumption and re-allocates power to different modules
based on real-time demand. For more information, see the CMC User's Guide at support.dell.com/manuals.
NOTE: The wattage of a power supply module is listed on its regulatory label.
Power Supply Blanks

If the M1000e enclosure is operated with only three power supplies, power supply blanks must be installed in the three
unoccupied power supply bays (4 through 6) to maintain proper cooling airflow in the enclosure.
AC Power Supply Modules

NOTE: A 2700 W power supply module requires 110 V to 240 V input from an AC power source. If a power supply
module is plugged into a 110 V electrical outlet, the power supply operates at 1350 W, if you select the Allow 110
VAC Operation check box in the CMC Power Configuration screen.
NOTE: A 3000 W power supply module requires 200 V to 240 V input from an AC power source.
NOTE: PDU inlet cords for this system may be too thick to fit in the wire guides installed in the rack vertical rails. If
this is the case, remove the wire guides by removing the attachment screw securing each guide. Route the PDU
inlet cords along the vertical rails, securing them with tie wraps or strips.
71
Removing An AC Power Supply

NOTE: The power supply modules are hot-swappable. Remove and replace only one power supply module at a time
in a system that is turned on.
1.
Release the retention clip on the power cable and disconnect the power cable from the power supply module.
2.
Press down on the power supply module release button on the handle.
3.
Rotate the power supply module handle down to eject the power supply module.
4.
Slide the power supply module out of the enclosure.
Figure 38. Power Cable Retention Clip
72
1. power supply
2. retention clip tether
3. notch in power supply handle
4. retention clip
5. power cable
Figure 39. Removing and Installing a Power Supply Module
1. power supply
2. handle
3. release button
Installing An AC Power Supply

1.
Ensure that the power supply module handle is fully open and the power cable is not plugged into the electrical
outlet.
2.
Slide the power supply module into the enclosure.
3.
Rotate the power supply module handle upward until it latches.
4.
Plug a power cable into the power supply module.
5.
Secure the cable to the power supply with the retention clip by fitting the retention clip over the cable, and fitting
the retention clip tether into the notch in the power supply handle.
73
DC Power Supply Modules

A 2700 W DC power supply module requires (4860) V DC input from a DC power source.
Wiring Instructions For A DC Power Supply

This document describes the requirements and wiring instructions for a 48 V DC power wire and safety ground wire for
systems equipped with a 48 V DC supply.
WARNING: For equipment using (4860) V DC power supplies, a qualified electrician must perform all connections
to DC power and to safety grounds. Do not attempt connecting to DC power or installing grounds yourself. All
electrical wiring must comply with applicable local or national codes and practices. Damage due to servicing that
is not authorized by Dell is not covered by your warranty. Read and follow all safety instructions that came with the
product.
WARNING: An energy hazard will exist if the safety ground cable is omitted or disconnected.
WARNING: The system chassis must be positively grounded to the rack cabinet frame. Do not attempt to connect
power to the system until grounding cables are connected.
CAUTION: A qualified electrician must perform all connections to DC power and safety grounds. The system must
be safety grounded at the cabinet frame. All electrical wiring must comply with applicable local or national codes
and practices.
CAUTION: This equipment is designed to permit the connection of the earthed conductor of the DC supply circuit to
the earthing conductor on the equipment. See the installation instructions. If this connection is made, all of the
following conditions must be met.
This equipment must be connected directly to the DC supply system earthing electrode conductor or to a
bonding jumper from an earthing terminal bar or bus to which the DC supply system earthing electrode
conductor is connected.
This equipment must be located in the same immediate area (such as, adjacent cabinets) as any other
equipment that has a connection between the earthed conductor of the same DC supply circuit and the earthing
conductor, and also the point of earthing of the DC system. The DC system must not be earthed elsewhere.
The DC supply source must be located within the same premises as this equipment.
The earthed circuit conductor between the DC power source and the earthing electrode conductor must not be
connected to switching or disconnecting devices.
Precaution Statements
This product is intended for restricted access locations (dedicated equipment rooms, equipment closet, or the like) in
accordance with the National Electrical Code, American National Standards Institute (ANSI)/National Fire Protection
Association (NFPA) 70.
CAUTION: Wire the unit with copper only. Unless otherwise specified, use only 4 American Wire Gauge (AWG)
wire rated minimum 90 C (194 F) for source and return. Protect the (4860) V DC (1 wire) with a branch circuit
overcurrent protection rated 100 A for DC with a high interrupt current rating.
Connect the equipment to a 48 V DC supply source that is electrically isolated from the AC source (reliably grounded 48
V DC SELV source). Ensure that the 48 V DC source is secured to earth (ground).
NOTE: A readily accessible disconnect device that is suitably approved and rated must be incorporated in the field
wiring.
74
CAUTION: When stranded wiring is required, use approved wiring termination, such as closed-loop or spade-type
with upturned lugs. These terminations are the appropriate size for the wires and must be double crimped, one on
the conductor and one on the insulation.
CAUTION: When installing the unit, the ground connection must always be made first and disconnected last to
prevent an energy hazard.
CAUTION: Never defeat the ground conductor or operate the equipment in the absence of a suitably installed
ground conductor. Contact the appropriate electrical inspection authority or an electrician if you are uncertain that
suitable grounding is available.
Input Requirements
Supply voltage: (4860) V DC
Current consumption: 75 A (maximum)
Kit Contents
Molex # 394260002 at PSU end
Molex # 39422-0012 mating DC power connector
Required Tools
Hand-crimping tool (Tyco Electronics 1490749-1, Upper Die 1490414-2, Lower Die 1-1490413-6).
Wire-stripper pliers capable of removing insulation from size 4 AWG solid or stranded, insulated copper wire.
NOTE: Use alpha wire part number 3080 or equivalent (65/30 stranding).
Required Wires
One UL 4 AWG, 2 m maximum (stranded) black wire [(4860) V DC]
One UL 4 AWG, 2 m maximum (stranded) red wire (V DC return)
One UL 4 AWG, 2 m maximum (stranded) green/yellow/green with a yellow stripe wire (safety ground)
Assembling And Connecting The Safety Ground Wire

product.
1.
Strip the insulation from the end of the green/yellow wire (safety ground wire), exposing approximately 4.5 mm
(0.175 inch) of copper wire.
2.
Using a hand-crimping tool (Tyco Electronics 1490749-1, Upper Die 1490414-2, and Lower Die 1-1490413-6), crimp
the ring-tongue terminal (Amp/Tyco PN 33115-1) to the green/yellow wire.
3.
Connect the safety ground wire to the grounding post on the back of the system using a #5/16 nut equipped with a
locking washer.
The nut must be torqued to 16 in lbs (1.8 N-m) to ensure proper ground wire retention.
75
Figure 40. Assembling and Connecting the Safety Ground Wire
1.
2.
3.
4.
grounding post
safety ground wire terminal
locking washer
#5/16 nut
Assembling The DC Input Power Wires And DC Power Connector

product.
1.
76
Strip the insulation from the ends of the DC power wires, exposing approximately 13 mm (0.5 inch) of copper wire.
WARNING: Reversing polarity when connecting DC power wires can permanently damage the power supply
or the system.
2.
Insert the copper ends into the mating connectors and tighten the captive screws at the top of the mating
connector using a #2 Phillips screwdriver. The captive screws must be torqued to 16 in lbs (1.8 N-m) to ensure
proper cable retention.
WARNING: To protect the power supply from electrostatic discharge, the captive screws must be covered
with the rubber cap before inserting the mating connector into the power supply.
3.
Rotate the rubber cap to fix it over the captive screws.
4.
Insert the DC power connector into the power supply.
5.
Tighten the screws on the wings of the DC power connector.
Figure 41. Assembling the DC Input Power Wires
1.
2.
3.
4.
DC power socket
rubber cap
captive screws (2)
DC power connector
5. wire 48 V
6. wire RTN
7. wings (2)
77
Removing A DC Power Supply

product.
CAUTION: The system requires six power supplies for normal operation. On power-redundant systems, remove and
replace only one power supply at a time in a system that is powered on.
NOTE: The power supply modules have internal fans that provide thermal cooling to these modules. A power
supply module must be replaced if an internal fan failure occurs.
NOTE: You may have to unlatch and lift the optional cable management arm if it interferes with power supply
removal. For information about the cable management arm, see the systems rack documentation.
1.
Disconnect the power wires from the power source and the connector from the power supply you intend to
remove.
2.
Disconnect the safety ground wire.
3.
Press the release latch on the power supply and slide the power supply away from the chassis.
78
Figure 42. Removing and Installing a DC Power Supply
1.
2.
3.
4.
connector
DC power supply
release latch
power supply handle
Installing A DC Power Supply

product.
1.
Verify that both the power supplies are the same type and have the same maximum output power.
NOTE: The maximum output power (shown in Watts) is listed on the power supply label.
2.
If applicable, remove the power supply blank.
79
3.
Slide the new power supply into the chassis until the power supply is fully seated and the release latch snaps into
place.
NOTE: If you unlatched the cable management arm, re-latch it. For information about the cable management
arm, see the systems rack documentation.
4.
Connect the safety ground wire. See Assembling And Connecting The Safety Ground Wire.
5.
Install the DC power connector in the power supply. See Assembling The DC Input Power Wires And DC Power
Connector.
6.
Connect the power wires to a DC power source.

NOTE: When installing, hot-swapping, or hot-adding a new power supply, allow several seconds for the
system to recognize the power supply and determine its status. The power-supply status indicator turns green
to signify that the power supply is functioning properly.
Fan Modules
The enclosure contains nine hot-swappable fan modules. All nine fan modules must be installed at all times to ensure
proper cooling.
Removing A Fan Module

WARNING: Do not operate the system without the cooling fans.
CAUTION: Exercise care while handling the fan module to prevent damage to the connector on the fan module.
1.
Identify the failed system fan module using the back-panel fan module indicators.
2.
Press the fan-module release button.
3.
Slide the fan module out of the enclosure.
80
Figure 43. Removing and Installing A Fan Module
1. fan module
2. release button
Installing A Fan Module

CAUTION: Exercise care while handling the fan module to prevent damage to the connector on the fan module.
1.
Inspect the fan for debris before installing the fan in the enclosure.
2.
Slide the fan module into the enclosure until it is fully seated and the release button engages.
CMC Module
Removing A CMC Module
1.
Disconnect the cables attached to the CMC module.
2.
Push the release latch on the handle and rotate the handle away from the module front panel.
3.
Slide the CMC module out of the enclosure.
81
4.
Install the I/O connector cover.
Figure 44. Removing and Installing a CMC Module or iKVM Module (CMC Module Shown)
1. I/O connector cover

2. release latch
3. release lever
Installing A CMC Module

1.
Remove the I/O connector cover.
2.
Open the CMC module handle.
3.
Slide the module into the enclosure until the handle contacts the enclosure.
4.
To fully seat the module, close the handle until the release latch snaps into place.
5.
Reconnect the cables that were attached to the module.
CMC Module SD Card
The SD card slot on the CMC module supports an optional WWN/MAC feature that allows slot-based WWN/MACs for
the blades, simplifying blade installation and replacement.
NOTE: For a redundant CMC module system, install the SD card on the passive module. The blue status indicator on
the passive module is off.
1.
Remove the CMC module from the M1000e enclosure.

NOTE: Verify the write protection latch is in the "unlock" position.
2.
82
Locate the SD card slot on the bottom of the CMC module and insert the contact-pin end of the card into the slot
with the label on the card facing upwards.
3.
Reinstall the CMC module and reattach any cables that were disconnected.
On a single CMC system, the SD card activates automatically. For redundant CMC module systems, initiate a
changeover to make the passive module active using the following steps:
a. Navigate to the Chassis page.
b. Click the Power Management tab.
c. Click the Control sub tab.
d. Select the Reset CMC (warm boot) button.
e. Click Apply.
The CMC automatically fails over to the redundant module, and that module now becomes active and displays a
solid blue status LED. The SD card activates automatically.
For information on configuration and usage of the FlexAddress feature, see the CMC Users Guide at
Figure 45. Installing an SD Card in the CMC Module
1. SD card connector
2. SD card
iKVM Module
Removing An iKVM Module
1.
Disconnect the cables attached to the iKVM module.
2.
Press in the release latch on the handle and rotate the handle away from the module front panel.
3.
Slide the module out of the enclosure.
83
4.
Figure 46. Removing and Installing a CMC Module or iKVM Module (CMC Module Shown)
1. I/O connector cover

2. release latch
3. release lever
Installing An iKVM Module

1.
Remove the I/O connector cover.
2.
Open the iKVM module handle.
3.
Slide the module into the enclosure until the handle contacts the enclosure.
4.
To fully seat the module, close the handle until the release latch snaps into place.
5.
If applicable, connect the keyboard, monitor, and mouse to the module.
I/O Modules
CAUTION: If you remove an I/O module, you must either replace it with another I/O module or with a filler blank to
maintain cooling airflow through the system enclosure.
84
Removing An I/O Module

1.
If you have not already installed the cable enumerators to make removal and replacement of the I/O modules easier
and faster, install them now.
For more information, see the Rack Installation Guide at support.dell.com/manuals.
2.
Disconnect the cables attached to the I/O module.
3.
Lift the latch on the end of the modules handle and rotate the handle away from the module.
4.
Slide the I/O module out of the enclosure.
5.
Figure 47. Removing and Installing an I/O Module
1.
2.
3.
4.
I/O connector cover

I/O module
release latch
handle
Installing An I/O Module

85
NOTE: The I/O module must be installed in the appropriate I/O bay.
1.
Unpack the I/O module and prepare it for installation.

For instructions, see the documentation that accompanied the I/O module.
2.
Remove the I/O connector cover from the back of the module.
3.
Lift the handle release latch and open the I/O module handle.
4.
Slide the module into the enclosure.
5.
Close the handle until it snaps securely into place and the module is fully seated.
6.
Connect all cables that must be attached to the I/O module.

See the documentation provided with the I/O module for information about its cable connections. For more
information on using the cable enumerators to organize and manage the cables, see the Rack Installation Guide at
7.
A matching fabric mezzanine card must be installed in one or more blades to support the new I/O module. If
necessary, install the mezzanine card(s).
Enclosure Bezel
Removing The Enclosure Bezel
1.
Press the power switch on the enclosure to turn off the system.
2.
Rotate the LCD module so that the underside of the module faces upward.
3.
Remove the cable cover and disconnect the ribbon cable from the LCD module.
4.
Remove the Torx T8 and Torx T20 screws that secure the bezel to the enclosure.
86
Figure 48. Removing and Installing the Bezel
1.
2.
3.
4.
bezel
enclosure
Torx T20 screws (6)
Torx T8 screws (2)
Installing The Enclosure Bezel

1.
Attach the bezel to the enclosure using the Torx T8 and Torx T20 screws.
2.
Connect the ribbon cable to the LCD module, and reinstall the cover plate.
Enclosure Midplane
Removing The Front Module Cage Assembly And Midplane
87
NOTE: A Torx T20 driver is required for this procedure.

1.
Press the enclosure power switch to turn off the system.

CAUTION: To avoid damaging the modules, you must remove all the modules installed in the enclosure before
removing the front module cage assembly and midplane.
NOTE: If you remove the chassis from the rack, you must remove all modules before moving the chassis. Do
not use the LCD display as a handle when moving the chassis.
2.
Remove the following:

a)
b)
c)
d)
e)
f)
3.
All the blades

Power supply modules
Fan modules
CMC module(s)
iKVM module
I/O modules
Remove the four Torx T20 screws securing the front module cage assembly to the enclosure.
NOTE: The empty cage assembly weighs 21 kg (47 lb). Obtain assistance when removing the cage assembly
from the enclosure.
4.
Slide the cage out from the enclosure.
5.
Disconnect the control-panel cable from the midplane by pressing the small latch at each end of the connector.
6.
Remove the four Torx T15 screws securing the midplane to the back of the front cage assembly, and remove the
midplane.
Figure 49. Removing and Installing the Front Module Cage Assembly
1. front module cage assembly
88
2. enclosure
3. Torx T20 screws (4)
Figure 50. Removing and Installing the Midplane
1. front module cage assembly

2. midplane
Installing The Midplane And Front Module Cage Assembly

1.
Attach the midplane to the front module cage assembly and secure it with the four Torx T15 screws.
2.
Connect the control-panel cable to the midplane.
3.
Carefully slide the front module cage assembly into the enclosure.
4.
Install the four Torx T20 screws to secure the front module cage assembly to the enclosure.
5.
Install the following:

a)
b)
c)
d)
e)
I/O modules
iKVM module
CMC module(s)
Fan modules
89
f)
All the blades
Enclosure Control Panel Assembly

Removing The Control Panel
1.
Press the system power switch to turn off the system.
2.
Remove the blades.
3.
Remove the bezel.
4.
Remove the two screws securing the control panel to the enclosure.
5.
Press the catch at each end of the control-panel cable connector, and remove the control-panel cable from the
underside of the control panel.
6.
Use the pull-tab to disconnect the LCD panel cable from the underside of the control panel.
Figure 51. Removing and Installing the Control Panel
1.
2.
3.
4.
90
control panel
control-panel cable
screws (2)
LCD panel cable
Installing The Control Panel

1.
Connect the LCD panel cable to the new control panel.
2.
Connect the control panel cable to the underside of the new control panel.
3.
Reinstall the control panel using the two screws.
4.
Reinstall the bezel.
5.
Install the blades.
LCD Module
Removing The LCD Module
1.
Rotate the LCD module so that the underside of the module faces upward.
2.
Remove the cable cover.
3.
Disconnect the ribbon cable.
4.
Remove the two Torx T8 screws securing the LCD module to the hinges.
91
Figure 52. Removing and Installing the LCD Module
1. cable cover
2. LCD module
3. ribbon cable
4. hinges (2)
Installing The LCD Module

1.
Attach the new LCD module to the hinges using the two Torx T8 screws.
2.
Connect the ribbon cable to the module, and reinstall the cable cover.
92
Troubleshooting The Enclosure
NOTE: For troubleshooting information on the blades in your enclosure, see the blade documentation at
Safety FirstFor You and Your System

Responding to a Systems Management Alert Message

The CMC management applications monitor critical system voltages and temperatures, and the cooling fans in the
system. For information about the CMC alert messages, see the CMC User's Guide at support.dell.com/manuals.
Troubleshooting A Damaged Enclosure

1.
Ensure that the following components are properly installed and connected:
CMC module
iKVM module
I/O modules
Fan modules
Blades
Sleeves (with quarter-height blades)
2.
Ensure that all cables are properly connected.
3.
Ensure that all components are properly installed and free from damage.
4.
Run the online diagnostics.

If the tests fail, see Getting Help.
Troubleshooting Enclosure Components

The following procedures describe how to troubleshoot the following components:
Fan modules
CMC module
Network switch module
93
Troubleshooting A Wet Enclosure

1.
Turn off the system.
2.
Disconnect the power supplies from the PDU.

CAUTION: Wait until all of the indicators on the power supplies turn off before proceeding.
3.
Remove all of the blades/sleeves.
4.
Remove the following components from the enclosure:

a)
b)
c)
d)
e)
5.

Fan modules
CMC module(s)
iKVM module
I/O modules
Let the system dry thoroughly for at least 24 hours.

NOTE: Air dry and do not use towels.
6.
Install the following components in the enclosure:

a)
b)
c)
d)
e)
I/O modules
iKVM module
CMC module(s)
Fan modules
7.
Install the blades/sleeves.
8.
Reconnect the power supply modules to their PDU and start up the system.
If the system does not start up properly, see Getting Help.
9.
Run the Server Administrator diagnostics to confirm that the system is working properly.
If the tests fail, see Getting Help.
Troubleshooting Power Supply Modules

NOTE: The power-supply modules are hot swappable. Remove and replace only one power-supply module at a
time in a system that is turned on. Leave a failed power-supply module installed in the enclosure until you are
ready to replace it. Operating the system with a power-supply module removed for extended periods of time can
cause the system to overheat.
NOTE: A 2700 W power supply module requires 110 V to 240 V input from an AC power source. If a power supply
module is plugged into a 110 V electrical outlet, the power supply operates at 1350 W, if you select the Allow 110
VAC Operation check box in the CMC Power Configuration screen.
1.
Locate the faulty power supply module and check the indicators. The power supply's AC indicator is green if AC
power is available. The power supply's fault indicator is amber if the power supply is faulty. If no indicators are lit,
ensure that 208 V AC power is available from the PDU and that the power cable is properly connected to the power
supply module.
2.
Install a new power supply.
94
NOTE: After installing a new power supply, allow several seconds for the system to recognize the power
supply and determine whether it is working properly. The power supply DC power indicator turns green if the
power supply is functioning properly.
3.
If none of the power supplies show a fault LED and the blades do not power on, check the LCD display or CMC for
status messages.
4.
If the problem is not resolved, see Getting Help.
Troubleshooting Fan Modules

NOTE: The fan modules are hot swappable. Remove and replace only one fan module at a time in a system that is
turned on. Operating the system without all six fan modules for extended periods of time can cause the system to
overheat.
1.
Locate the faulty fan. Each fan module has indicators that identify a faulty fan.
2.
Remove the fan module.
3.
Examine the blades for debris. If debris is present, carefully remove it.
4.
Reseat the faulty fan.
5.
If none of the fans show a fault LED and the blades do not power on, check the LCD display or CMC for status
messages.
6.
If the problem is not resolved, install a new fan.
7.
If the new fan does not operate, see Getting Help.
Troubleshooting The iKVM Module

When using iDRAC video\console redirection, and you cannot see video through the iKVM when you switch to a blade
running Linux, a typical cause is that a monitor or KVM appliance with a lower resolution has recently been added.
For example, a blade running X Windows under Linux is inserted and powered on. A user connects to the blade in OS
GUI mode using the iDRAC and a video resolution is detected and hard-set for that session. A monitor or KVM appliance
is attached to the front or rear iKVM interface on the M1000e enclosure. The monitor or the KVM appliance is configured
with a resolution LOWER than the currently configured resolution in the X-Window session on the Linux blade. When
you select the Linux blade using the front or rear port on the iKVM, the iDRAC circuit adopts the lower resolution of the
external connected devices. The video on the lower resolution monitor or the KVM appliance is not displayed until X
Windows is restarted (iDRAC video should still be viewable.)
1.
From the iDRAC session, exit and re-enter GUI mode. The lower resolution is communicated and utilized.
2.
Set all monitors or KVM appliances connected to the M1000e enclosure to the same resolution or higher as
configured on the Linux blades in GUI mode.
3.
From the lower resolution monitor (no video displayed) press <CTRL><ALT><F3> to change to the non-GUI login
screen.
4.
Restart X Windows to detect and utilize the lower resolution.
Troubleshooting I/O Modules

NOTE: To eliminate the possibility of a hardware problem with the module or its attaching devices, first ensure that
the module is properly initialized and configured.
1.
Check that you have installed the module in an I/O slot that matches its fabric type.
2.
Check that the pass-through module or switch ports are cabled correctly. A given mezzanine card in a full-height
blade connects to two I/O ports on the two associated I/O modules.
95
3.
Using the "17th blade" feature of the CMC, use the Connect Switch-X command to verify that the switch is fully
booted, and verify the switchs firmware revision and IP address.
4.
Verify that the switch module has a valid IP address for the subnet. Verify using the ICMP ping command.
5.
Check the network connector indicators on the network switch module:
6.
If the link indicator displays an error condition, check all cable connections.
Try another connector on the external switch or hub.
If the activity indicator does not light, replace the network switch module.
Using the switch management interface, verify the switch port properties. If the switch is configured correctly,
back up the switch configuration and replace the switch. See the switch module documentation for details.
7.
If the blade requires a mezzanine card for a particular network switch module, ensure that the appropriate
mezzanine card is installed. If so, reseat the mezzanine card. If the network link indicator on the blade is green,
then the blade has a valid link to the appropriate network switch module.
8.
Ensure that the appropriate operating system drivers are installed and that the protocol settings are configured to
ensure proper communication.
96
Technical Specifications
Enclosure Specifications
Power Supply Module
AC/DC power supply (per power supply module) (2700
W)
Wattage
2700 W
Connector
IEC C20
Heat dissipation
1205 BTU/hr (maximum)
Maximum inrush current
Under typical line conditions and over the entire system

ambient operating range, the inrush current may reach 55 A
per power supply for 10 ms or less.
AC/DC power supply (per power supply module) (3000

W)
Wattage
3000 W
Connector
IEC 320
Heat dissipation
NOTE: Heat dissipation is calculated using the

power supply wattage rating.
Under typical line conditions and over the entire system

ambient operating range, the inrush current may reach 55 A
per power supply for 10 ms or less.
System voltage requirements
16 A, 200 V AC to 240 V AC, 50 Hz/60 Hz (3000 W power

supply)
NOTE: This system is also designed to be connected 16 A, 100 V AC to 240 V AC, 50 Hz/60 Hz (2700 W power
to IT power systems with a phase to phase voltage supply)
not exceeding 230 V.
DC/DC power supply (per power supply)
Wattage
2700 W
Connector
Molex # 394260002 at PSU end, mating connector Molex #

39422-0012
Heat dissipation
97
Power Supply Module

Under typical input voltage conditions and over the entire

system ambient operating range, the inrush current may
reach 120 A per power supply for 10 ms or less.
System voltage requirements
75 A, 48 V DC to 60 V DC
Optional Avocent iKVM Module

Externally accessible connectors
USB
Two 4-pin, USB 2.0-compliant connectors for keyboard and

mouse support
ACI port
RJ-45
Video
15-pin VGA
Chassis Management Controller Module

Remote management
Two dedicated 10/100/1000 Mb RJ-45 (for integrated

Ethernet remote access controller). Gb port connects to the
external management network. STK port allows CMCs in
adjacent enclosures to be daisy chained.
Serial
9-pin, DTE, 16550-compatible
Video
15-pin VGA
Battery
CR 2032 3.0-V Lithium ion coin cell
Enclosure Control Panel

USB
Two 4-pin, USB 2.0-compliant connectors for keyboard and

mouse support
Video
15-pin VGA
LCD panel features
Four cursor control keys, one select key, LCD screen
I/O Module Specifications

Cisco Nexus B22 Fabric Extender Module
98
Sixteen 10 Gb (internal) Ethernet ports and Eight 10 Gigabit

Ethernet SFP+ ports that support 10Gbase-SR, 10Gbase-LR,
and 10Gbase-ER fabric connections.
Brocade M6505 16 Gbps FC SAN I/O Module

Eight physical FC8 ports that support 4/8/16 Gbps fibre

channel connections
Serial Port
RJ-45
Dell PowerEdge M I/O Aggregator Switch Module

Serial
4-pin, USB 2.0 type A connector. Must use provided USB

type A to DB9 adapter to connect to terminal.
Optional Modules
Two fixed 40 GbE ports that operate in 4x10 GbE mode.
Dell Force10 MXL 10/40 GbE Switch Module

Serial

Optional Modules
Two optional bays. Each bay supports an Uplink module

with four 40 GbE optical SFP+ connectors, or 10GBASE-T
module using RJ-45 connectors.
PowerConnect M8024 10 Gb Ethernet Switch Module

Serial

Optional Modules
Two optional bays. Each bay supports an Uplink module

with four 10 Gb optical SFP+ connectors, or three 10 Gb CX4
uplinks. A stacking module is not available.
PowerConnect M6220 Ethernet Switch Module

10/100/1000 Mbps Ethernet
Four autonegotiating RJ-45 ports
Serial

Optional Modules
Two option bays. Each bay supports a module with two 24

Gb stacking ports, two 10 Gb CX4 copper uplinks, or two 10
Gb optical XFPs.
99
Brocade FC8 Fibre Channel Switch Module

Eight physical FC8 ports (four enabled by default,

upgradeable to eight) that support 2/4/8 Gbps fibre channel
connections
Serial Port
RJ-45
Brocade FC4 Fibre Channel Switch Module

Fibre channel
Eight physical FC4 ports (four enabled by default,

upgradeable to eight) that support 1/2/4 Gbps FC
connections
Serial Port
RJ-45
Mellanox M4001F/M4001Q Infiniband Switch I/O Module

Infiniband ports
Sixteen QSFP connectors
Mellanox Infiniband Switch Module

Infiniband ports
Eight Infiniband uplink ports
Gb Ethernet Pass-Through Module

Ethernet
Sixteen RJ-45 ports. Pass-through ports support 10/100/1000

Mbps connections.
Fibre Channel Pass-Through Module

Fibre channel transceiver
Sixteen external SFP ports that support 1/2/4 Gbps FC

connections
Environmental
NOTE: For additional information about environmental measurements for specific system configurations, see
dell.com/environmental_datasheets.
Standard Operating Temperature
Expanded Operating Temperature
100
Continuous operation: 10 C to 35 C at 10% to 80%

relative humidity (RH), with 26 C max dew point. De-rate
maximum allowable dry bulb temperature at 1 C per 300
m above 900 m (1 F per 550 ft).
Environmental
NOTE: When operating in the expanded temperature
range, system performance may be impacted.
NOTE: When operating in the expanded temperature
range, ambient temperature warnings may be
reported on the LCD and in the System Event Log.
< 10% of annual operating hours
5 C to 40 C at 5% to 85% RH with 26 C dew point.

NOTE: Outside the standard operating temperature
(10 C to 35 C), the system can operate down to 5 C
or up to 40 C for a maximum of 10% of its annual
operating hours.
For temperatures between 35 C and 40 C, de-rate
maximum allowable dry bulb temperature by 1 C per 175
< 1% of annual operating hours
5 C to 45 C at 5% to 90% RH with 26 C dew point.

NOTE: Outside the standard operating temperature
(10 C to 35 C), the system can operate down to 5
C or up to 45 C for a maximum of 1% of its annual
operating hours.
For temperatures between 40 C and 45 C, de-rate
maximum allowable dry bulb temperature by 1 C per 125
Expanded Operating Temperature Restrictions
Install blades that fulfill the requirements for

expanded operating temperature range.
NOTE: For more information on the bladespecific restrictions for the expanded
operating temperature range, see the
technical specifications in the blade's
Owner's Manual at dell.com/support/
manuals.
2700 W power supplies are supported as per the
power supply rated capacity.
3000 W power supplies are supported with a
capacity of 2800 W per power supply.
Install fans of the following ratings:
12 V, 5.0 A
12 V, 6.30 A
Only the following I/O modules are supported:
Brocade M5424 FC8 I/O module

Dell M8428-k 10 Gb converged network
switch
Cisco 1 GE 3130X-s switch
Mellanox M3601Q DDR/QDR switch
Dell PowerConnect M8024-k switch
Dell PowerConnect M6220 Ethernet
switch I/O module
101
Environmental
Storage Temperature
102
Dell PowerConnect M8024 10 Gb

Ethernet switch I/O module
40 C to 65 C (40 F to 149 F) with a maximum

temperature gradation of 20 C per hour.
Getting Help
Contacting Dell
NOTE: If you do not have an active Internet connection, you can find contact information on your purchase invoice,
packing slip, bill, or Dell product catalog.
Dell provides several online and telephone-based support and service options. Availability varies by country and
product, and some services may not be available in your area. To contact Dell for sales, technical support, or customer
service issues:
1.
Visit dell.com/support
2.
Select your support category.
3.
Verify your country or region in the Choose a Country/Region drop-down menu at the top of page.
4.
Select the appropriate service or support link based on your need.
103

453-SWD-RMM-0103020 R01 S3 Bk2 SCC I&C 1

Uploaded by

Copyright:

Available Formats

453-SWD-RMM-0103020 R01 S3 Bk2 SCC I&C 1

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

453-SWD-RMM-0103020 R01 S3 Bk2 SCC I&C 1

Uploaded by

Copyright:

Available Formats

SCC and OCC

Set 3 Book 2 - Centralized Control System (SCC)

Metro No. &

File name: 453-SWD-RMM-0103020.doc

Not used for the Sao Paulo project. In accordance with

Confidential and proprietary

Template ID-Number: 006735

So Paulo Expresso Tiradentes Monorail

Set 3: SCC and OCC

THIS PAGE LEFT BLANK INTENTIONALLY

MANUAL COMMENT FORM

Technical Publications and Training

LIST OF EFFECTIVE PAGES

Section 1 - General Information

THIS PAGE LEFT BLANK INTENTIONALLY

SO PAULO EXPRESSO TIRADENTES MONORAIL

SYSTEM OVERVIEW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

SCC PROCESSOR MODULES . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Map.Txt for the Modbus Poller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

SAFETY PRECAUTIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

SAFETY PRECAUTIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1

PARTS LISTING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1

SCC Operator Equipment Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2

SCC Subsystem Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2

SCC Cabinet Assembly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2

Equipment Identification and Suppliers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

List of Operators. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-76

Power Supply Module Troubleshooting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

Reference Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1

SCC Hardware Equipment Preventive Maintenance Schedule . . . . . . . . . . . . 6-1

LIST OF ACRONYMS AND ABBREVIATIONS

GENERAL SAFETY PRECAUTIONS

This publication utilizes three levels of precautionary notices, as follows:

INDICATES AN OPERATION, SEQUENCE, OR FUNCTION THAT, IF NOT

Indicates an operation, sequence, or function that, if not observed, may

WARNING: ALL WORK TO BE PERFORMED ON ANY PART OF THE SYSTEM

Disconnect power when handling equipment electrical connections or when

Take proper precautions when handling static sensitive equipment by using

When handling heavy components, select a lifting apparatus of adequate type

When attaching hardware is replaced, care must be taken to ensure that

THIS PAGE LEFT BLANK INTENTIONALLY

SAE Grade 2 Bolts

SAE Grade 5 Bolts

SAE Grade 7 Bolts

SAE Grade 8 Bolts

COEFFICIENT OF FRICTION FOR DIFFERENT SURFACES AND LUBRICATING CONDITIONS

ISO Class 4.6

ISO Class 4.8 & 5.6

ISO Class 5.8

ISO Class 8.8

ISO Class 10.9

ISO Class 12.9

SO PAULO EXPRESSO TIRADENTES MONORAIL

Dell Blade Server M1000E

SCC Workstation Processor

SCC Workstation Monitor

Table 1-1. Equipment Identification and Suppliers

SPECIFICATIONS (Ref. Tables 1-2 and 1-3)

standard gigabyte ethernet cable category 5

Table 1-2. General Specifications