Control Hardware Planning Guide EPDCXX26

(1)

Honeywell Process Solutions

Experion

Control Hardware Planning

Guide

EP-DCXX26

R400

July 2010

Release 400

Honeywell

(2)

Notices and Trademarks

Copyright 2010 by Honeywell International Sárl.

Release 400 July 2010

While this information is presented in good faith and believed to be accurate, Honeywell disclaims the implied warranties of merchantability and fitness for a particular purpose and makes no express warranties except as may be stated in its written agreement with and for its customers. In no event is Honeywell liable to anyone for any indirect, special or consequential damages. The information and specifications in this document are subject to change without notice.

Honeywell, PlantScape, Experion PKS, and TotalPlant are registered trademarks of Honeywell International Inc.

Other brand or product names are trademarks of their respective owners.

Honeywell Process Solutions 1860 W. Rose Garden Lane Phoenix, AZ 85027 USA

(3)

About This Document

This document provides an overview of things you should consider when planning for

the installation of your Experion control hardware.

Release Information

Document Name Document ID Release Number

Publication Date

Control Hardware Planning Guide

- plng EP-DCXX26 400 July 2010

Document Category

(4)

Support and Other Contacts

United States and Canada

Contact:

Phone:

Fascimile: Mail:

Honeywell Solution Support Center 1-800-822-7673

Calls are answered by dispatcher between 6:00 am and 4:00 pm Mountain Standard Time. Emergency calls outside normal working hours are received by an answering service and returned within one hour. 1-973-455-5000

Honeywell TAC, MS L17 1860 W. Garden Lane Phoenix, AZ, 85027 USA

Europe, Middle East, and Africa (EMEA)

Contact: Phone: Fascimile: Mail: Honeywell TAC-EMEA +32-2-728-2345 +32-2-728-2696 TAC-BE02 Hermes Plaza Hermeslaan, 1H B-1831 Diegem, Belgium

Pacific

Contact: Phone: Fascimile: Mail: Email:

Honeywell Global TAC – Pacific 1300-364-822 (toll free within Australia) +61-8-9362-9559 (outside Australia) +61-8-9362-9564

Honeywell Limited Australia 5 Kitchener Way

Burswood 6100, Western Australia [email protected]

India

Honeywell Global TAC – India +91-20- 6603-9400

+91-20- 6603-9800

Honeywell Automation India Ltd 56 and 57, Hadapsar Industrial Estate Hadapsar, Pune –411 013, India [email protected]

(5)

Korea

Honeywell Global TAC – Korea +82-2-799-6317 +82-2-792-9015 Honeywell Co., Ltd 4F, Sangam IT Tower 1590, DMC Sangam-dong, Mapo-gu Seoul, 121-836, Korea [email protected]

People’s Republic of China

Contact:

Phone:

Mail:

Email:

Honeywell Global TAC – China +86- 21-2219-6888

800-820-0237 400-820-0386

Honeywell (China) Co., Ltd

33/F, Tower A, City Center, 100 Zunyi Rd. Shanghai 200051, People’s Republic of China [email protected]

Singapore

Honeywell Global TAC – South East Asia +65-6580-3500

+65-6580-3501 +65-6445-3033

Honeywell Private Limited Honeywell Building

17, Changi Business Park Central 1 Singapore 486073 [email protected]

Taiwan

Honeywell Global TAC – Taiwan +886-7-536-2567

+886-7-536-2039 Honeywell Taiwan Ltd.

17F-1, No. 260, Jhongshan 2nd Road. Cianjhen District

Kaohsiung, Taiwan, ROC

(6)

Japan

Honeywell Global TAC – Japan +81-3-6730-7160

+81-3-6730-7228 Honeywell Japan Inc.

New Pier Takeshiba, South Tower Building, 20th Floor, 1-16-1 Kaigan, Minato-ku, Tokyo 105-0022, Japan

[email protected]

Elsewhere

Call your nearest Honeywell office.

World Wide Web

Honeywell Solution Support Online: http://www.honeywell.com/ps

Training Classes

Honeywell Automation College: http://www.automationcollege.com

(7)

Symbol Definitions

The following table lists those symbols used in this document to denote certain conditions.

Symbol Definition

ATTENTION: Identifies information that requires special

consideration.

TIP: Identifies advice or hints for the user, often in terms of

performing a task.

REFERENCE -EXTERNAL: Identifies an additional source of

information outside of the bookset.

REFERENCE - INTERNAL: Identifies an additional source of

information within the bookset.

CAUTION

Indicates a situation which, if not avoided, may result in equipment or work (data) on the system being damaged or lost, or may result in the inability to properly operate the process.

CAUTION: Indicates a potentially hazardous situation which, if not

avoided, may result in minor or moderate injury. It may also be used to alert against unsafe practices.

CAUTION symbol on the equipment refers the user to the product

manual for additional information. The symbol appears next to required information in the manual.

WARNING: Indicates a potentially hazardous situation, which, if not

avoided, could result in serious injury or death.

WARNING symbol on the equipment refers the user to the product

manual for additional information. The symbol appears next to required information in the manual.

(8)

Symbol Definitions

Symbol Definition

WARNING, Risk of electrical shock: Potential shock hazard where

HAZARDOUS LIVE voltages greater than 30 Vrms, 42.4 Vpeak, or 60 VDC may be accessible.

ESD HAZARD: Danger of an electro-static discharge to which

equipment may be sensitive. Observe precautions for handling electrostatic sensitive devices.

Protective Earth (PE) terminal: Provided for connection of the

protective earth (green or green/yellow) supply system conductor.

Functional earth terminal: Used for non-safety purposes such as

noise immunity improvement. NOTE: This connection shall be bonded to Protective Earth at the source of supply in accordance with national local electrical code requirements.

Earth Ground: Functional earth connection. NOTE: This

connection shall be bonded to Protective Earth at the source of supply in accordance with national and local electrical code requirements.

Chassis Ground: Identifies a connection to the chassis or frame of

the equipment shall be bonded to Protective Earth at the source of supply in accordance with national and local electrical code requirements.

(9)

1. INTRODUCTION ...29

1.1 Overview ... 29

About this guide ...29

Online documentation reference ...29

2. INITIAL PLANNING AND DESIGN ACTIVITIES...31

2.1 Getting Started ... 31

Review Experion capabilities...31

General Prerequisites...31

2.2 Schedules and Responsibilities ... 32

Pre-installation schedule ...32

Customer responsibilities ...34

2.3 Shipping and Receiving ... 34

Shipping ...34 Environmental considerations ...34 Cost...35 Receiving ...35 Moving...35 Unpacking ...35 Warehousing ...36

3. CONTROL NETWORK CONSIDERATIONS ...37

3.1 Communications Network... 37

New or existing network ...37

3.2 Identifying topology diagram symbols ... 37

About the symbols...37

3.3 Experion cluster types... 44

Overview ...44

Experion Cluster Type 1...45

(10)

Contents

Level 3 router connected...54

Common FTE community ...54

3.5 Experion and OPC ...55

Level 2 OPC client or server connection...55

Level 3 OPC Client or Server Connection...56

3.6 ACE OPC Gateway ...57

OPC Gateway Client ...57

Experion Inter-Cluster Gateway ...58

3.7 Enterprise Model Topologies ...60

3.8 Experion Application Topologies ...63

Experion Application Server (EAS) ...63

Application Point Server (APS) ...63

Experion Desktop Server (EDS) ...65

Application Server (AS)...66

3.9 PHD Integration Topologies ...68

PHD Integration Benefits ...69

3.10 eServer Topologies...71

3.11 Terminal Services ...72

Terminal services capability ...72

4. SUPERVISORY NETWORKS...75

4.1 About Supervisory networks ...75

4.2 Fault Tolerant Ethernet (FTE) Support ...75

4.3 FTE Supervisory Network Topologies ...76

Basic C200 Controller Fault Tolerant Ethernet Bridge (FTEB) topology ...76

Multiple Experion cluster FTE bridge topology...79

Basic C300 Controller with Control Firewall FTE topology ...80

Multiple Experion cluster mixed C200 and C300 topology ...82

C300 interoperability with PLC topologies...84

C200 with FTE interoperable topologies ...86

4.4 C300 Peer Contro Data Interface (PCDI) Topologies...89

4.5 ControlNet Supervisory Network Topologies ...90

Small ControlNet topology ...90

Conjoined redundant C200 Controller topology ...90

Basic ControlNet topology...92

ControlNet Interoperable topology ...93

(11)

Contents

Basic Ethernet topology ...95

4.7 Distributed System Architecture (DSA) Topologies... 97

Integrated SCADA and Experion ControlNet Server Topology...97

Multiple Experion ControlNet Server DSA Topology ...98

5. INPUT/OUTPUT (I/O) NETWORK CONSIDERATIONS ...99

5.1 About I/O Networks... 99

5.2 Basic Series A Chassis I/O Topology ... 100

Configuration Rules (MAC) ...100

5.3 Basic Series A Rail I/O Topology... 103

5.4 Basic Series H Rail I/O Topology... 104

5.5 Process Manager I/O Topologies ... 104

PM I/O with C200 and I/O Link Interface Module (IOLIM) ...104

PM I/O with C300 Controller...106

5.6 Series C I/O Topologies... 110

Series C I/O with C300...110

5.7 FTE Bridge (FTEB) Topologies... 114

Series A Chassis I/O and FTEB with C300 ...114

5.8 HART I/O Topologies ... 116

HART Series A Chassis I/O ...116

HART PM I/O ...117

HART Series C I/O...119

5.9 DeviceNet I/O Topologies... 120

DeviceNet with C200...121

DeviceNet with C300...121

5.10 Allen-Bradley Drive Interface Topologies ... 125

A-B Drive with C200 ...125

5.11 Fieldbus Interface Topologies ... 127

Fieldbus H1 network with non-redundant Series A FIM topology ...127

Redundant Series A FIM topology...129

Series C FIM topology...132

Maximum redundant Series C FIM topology ...135

5.12 Simulation Topologies ... 136

ControlNet simulation topology...136

(12)

Contents

6.1 Fault Tolerant Ethernet ...141

6.2 Ethernet ...143

Benefits of Ethernet ...143

Ethernet as applied to Process Control...143

Ethernet Networking...144

Ethernet Switching and Routing...144

6.3 ControlNet ...145

Benefits of ControlNet...145

ControlNet Networking ...145

ControlNet Network Residency Reference...146

6.4 System Configuration Examples Using ControlNet ...147

Small-scale system example...147

Small scale system configuration rules ...148

Medium-scale system configuration example ...148

Large-scale system example ...149

General configuration rules ...152

7. C200 AND PM I/O HARDWARE CONFIGURATION...155

7.1 Planning Your Control and I/O Hardware ...155

C200 Controllers ...155

Application Control Environment (ACE) supervisory controller ...156

Third-Party controllers...157

ControlNet Interface (CNI) ...158

Fault Tolerant Ethernet Bridge ...158

I/O Input Modules...159

I/O Output Modules...159

I/O configuration...160

I/O redundancy ...160

7.2 Planning Your Chassis Configurations...162

Background...162

Power supplies...162

C200 Controller chassis configuration...162

Minimum requirements for redundant controller network ...166

Redundant controller small system examples...166

I/O chassis configuration...168

Chassis addressing...171

7.3 Planning Your I/O Modules and Remote Termination Panels...172

Chassis I/O module planning ...172

Remote Termination Panel planning...173

HART I/O Module planning ...173

Fieldbus Interface Module (FIM) planning...173

(13)

Contents

PROFIBUS Interface Module (PBIM) planning...174

Serial Interface Module (SIM) planning ...174

Pulse Input Module (PIM) planning ...177

7.4 Planning Your Process Manager I/O Card Files ... 178

Card file models ...178

Left 7-Slot IOP...179

Right 7-Slot IOP ...180

15-Slot IOP...181

7.5 Planning Your Input/Output Processor (IOP) Cards ... 182

IOP types ...182

IOP redundancy ...183

Redundant HLAI IOPs...183

Redundant AO IOPs ...185

IOP card models ...186

7.6 Planning for Low Level Multiplexer IOP ... 188

LLMux versions ...188

Typical LLMux configuration...188

LLMux Power Adapter location...190

LLMux IOP to Power Adapter cable ...190

LLMux FTA location ...190

Remote LLMux FTA cabinet restrictions ...191

Local FTA to Power Adapter cabling ...191

External Power Adapter to FTA cabling ...191

Remote CJR installation...192

Typical RHMUX configuration ...194

CE Compliance ...197

Non-CE Compliance...197

RHMUX Power Adapter location ...197

RHMUX IOP to Power Adapter cable...197

RHMUX FTA location...197

Remote RHMUX FTA cabinet restrictions ...198

Indoor environment FTA to Power Adapter cabling...199

Outdoor environment Power Adapter to FTA cabling ...199

7.7 Planning for I/O Link Extender (Fiber Optic Link) ... 201

I/O Link Extender types ...201

Remote card files ...201

Fiber optic cable length ...201

Standard type extender ...202

Standard type extender with single IOP example...202

Standard type extender with redundant IOPs example ...203

Long Distance type Extender ...205

Long Distance type extender with single IOP example...205

Multiple IOPs at remote site example...206

(14)

Contents

I/O Link Interface cables ...209

7.8 Planning for Field Termination Assemblies (FTAs)...210

FTA types ...210

FTA dimensions ...212

FTA Mounting Channels ...214

FTA mounting orientation...214

Typical cabinet layout...214

Cable routing...216

FTA terminal types...216

FTA compression-type terminal Connector...216

FTA fixed-screw terminal connector...219

FTA removable-screw terminal connector...220

FTA crimp-pin terminal connector ...221

FTA Marshalling Panel...221

IOP to FTA cable models...223

FTA models ...224

7.9 Planning Your C200 Control System Installation...236

Background...236

Enclosures ...236

Mounting panels...237

Chassis mounting and spacing ...237

Remote Termination Panels...237

Wiring and Cabling...238

ControlNet network taps...238

Small-scale system enclosure configuration example...238

Medium-scale system enclosure configuration example ...240

Large-scale system enclosure configuration example...243

Single IOP cabinet configuration...246

IOP in complexed cabinets with redundant Process Controllers ...247

IOP in Complexed and remote cabinets...248

8. SERIES C HARDWARE CONFIGURATION ...251

8.1 Planning Your Series C Control System ...251

Possible Series C system configurations ...251

Configuration rules (SCS) ...252

Series C cabinet layout examples ...252

Configuration rules (IOL)...257

8.2 Selecting Series C Cabinet Hardware ...260

Single-Access, 0.5 meter (20 inches)-deep cabinet parts ...260

Dual-Access, 0.8 meter (32 inches)-deep cabinet parts...261

8.3 Selecting Power Entry Accessories ...264

Standard Power Entry ...264

(15)

Contents

Optional Power Entry guidelines ...265

8.4 Selecting Fan Assembly Kits ... 266

8.5 Carrier Channel Assembly Parts ... 266

8.6 Carrier Channel Assembly Reference Dimensions ... 268

8.7 Selecting Series C Power System ... 269

Series C power system parts...269

Model CC-PWRB01 power system ...270

Model CC-PWRR01 Power System ...271

Model CC-PWRN01 power system ...271

24V Backup Assembly ...271

Model CC-PWN401 Power System...271

Model CC-PWR401 Power System...271

8.8 Power Distribution Subsystem... 272

Horizontal dc power bus bar (HDPB) ...272

8.9 C300 Controller Memory Backup ... 273

Memory backup assembly cabling guidelines ...273

Memory backup hold-up times ...274

Replacing RAM charger batteries (NiMH batteries)...274

8.10 Series C DC Power Connections and Indicators ... 277

8.11 Series C Power Sub-System LED Indications ... 280

8.12 Series C Power Sub-System Alarm Contacts and LED Activation Levels

282

Using DI channels to report system alarms...283

To connect the Power System alarm cable for RAM Charger Assembly 51199932-100....284

To connect the Power System alarm cable for RAM Charger Assembly 51199932-200....286

8.13 LLMUX FTAs Mounting Considerations... 288

Remote CJR installation considerations...290

8.14 Series C System Cabling ... 291

Cable color coding schemes ...291

I/O Link Cables...292

PM I/O Link cables ...298

I/O Link address jumpers ...299

Ethernet cables ...299

LLMUX FTA cables ...301

DO relay extension cables ...303

Fieldbus power conditioner cables ...304

8.15 Agency Approvals for Series C Cabinets ... 305

(16)

Contents

8.17 Series C Hardware Grounding Considerations ...307

Grounding basics ...307

Types of Grounding Systems...308

Energy limiter for dissimilar grounds ...310

Isolation ...310

Codes and references...311

Two AC power sourcing methods ...311

Series C cabinet safety ground connections ...311

Grounding guidelines for C300 Controllers with Series C I/O...315

Series C cabinet typical power and ground connections ...316

Grounding guidelines for C300 Controllers with Series C I/O and PM I/O ...317

Grounding considerations for C200/IOLIM to C300 upgrade ...321

Grounding considerations for HPM to C300 upgrade...322

Grounding considerations for C200/IOLIM to C300 upgrade in PM cabinets...323

9. CONTROLNET CONFIGURATION...325

9.1 Planning Overview ...325

Background...325

Types of ControlNet networks...325

ControlNet supervisory network ...326

I/O ControlNet network...327

High-level ControlNet network overview...327

Network components ...327

Quick planning guide ...327

9.2 Planning Your Link and Segment Configurations ...331

Background...331

Segment planning considerations ...332

Link planning considerations...333

9.3 Connecting Your Links and Segments ...335

Background...335

Coaxial Repeater options...336

Determining if you need repeaters ...336

Mounting dimensions ...338

Configuring your link with repeaters ...339

Repeaters in series ...339

Repeaters in parallel ...340

Repeaters in a combination of series and parallel...341

9.4 Planning Your Physical Media ...343

Trunk cable ...343

Determining what type of cable you need ...343

General Wiring Guidelines ...344

Wiring External to Enclosures ...344

Wiring Inside Enclosures...345

(17)

Contents

Determining trunk section lengths ...346

Example ...346

Maintaining Experion ControlNet Cabling...347

9.5 Planning for Your ControlNet Cable Connectors ... 349

Background ...349

Connector types ...349

Example of connector type applications ...350

Using redundant media (optional) ...351

9.6 Planning for Your ControlNet Taps... 354

Background ...354

Determining how many taps you need ...355

Tap kits ...356

Mounting dimensions ...357

Universal mounting bracket...360

Planning for drop-cable identification ...360

9.7 Planning Your ControlNet Nodes ... 362

Background ...362

Communications Integrity...362

9.8 Planning for ControlNet Terminators... 363

Background ...363

Determining how many terminators you need ...363

9.9 Planning Your ControlNet Addressing ... 364

Background ...364

Non-redundant controller addressing ...364

Redundant controller addressing...364

Supervisory ControlNet addressing...365

Network Example 1: Two Non-Redundant Controllers (each with remote I/O chassis) ...366

Network Example 2: Redundant Controllers with One I/O ControlNet...367

I/O ControlNet addressing...368

MAC address guidelines summary...369

Single or Multiple Network Strategy ...371

10. SITE SELECTION AND PLANNING ...373

10.1 Planning for General Considerations... 373

Location...373

Interim development location ...373

Facilities ...373

Insurance and zoning ...373

10.2 Planning for Environmental Considerations ... 374

Corrosion and dust ...374

(18)

Contents

Temperature and humidity ...374

Ventilation and filtration...374

Vibration...375

10.3 Planning for Installation in Hazardous (Classified) Locations ...376

North American Hazardous (Classified) Locations...376

Hazardous Location Level of Risk...377

Hazardous Group Classifications...377

Nonincendive FTAs...378

Electrical code approval ...379

Current limiting resistor value...379

Cable size and load parameters ...379

Galvanically Isolated FTAs...381

10.4 Planning for Power and Grounding ...381

Compliance ...381 Circuit capacities...382 Outlet capacities ...382 Multiple systems ...382 Convenience outlets ...382 Honeywell products...383

General grounding guidelines ...383

Grounding considerations for C200 with PM I/O ...384

About Lightning Grounds ...386

Lightning Ground Example (General Purpose Area)...387

10.5 Planning for Process Manager I/O Power Requirements ...388

Power system types and features ...388

Standard power system ...388

AC Only Power System...390

Typical AC power and ground connections for IOP...391

Power and I/O Link Interface cable for Controller and IOLIM...395

Power cables for IOPs ...395

Non-CE Compliant subsystems ...397

CE Compliant subsystems ...398

10.6 Planning for Bonding and Grounding ...399

Mounting and bonding chassis...399

Bonding and grounding chassis ...401

Control cabinet grounding ...402

Power supply grounding...404

DIN rail mounted component grounding...404

Grounding-electrode conductor...404

Cable shields on process wiring...404

10.7 Planning Your Cabling and Wiring...405

(19)

Contents

11.1 Introduction... 407

11.2 Planning for Static Electricity Minimization... 407

Ways to reduce electric static discharge ...407

11.3 Planning for Interference Minimization ... 408

General considerations ...408

Magnetic interference...408

Electromagnetic and radio frequency interference ...408

Removal and Insertion Under Power (RIUP)...408

11.4 Planning Raceway Layouts ... 409

General considerations ...409

Categorizing conductors...409

Routing conductors ...411

11.5 Planning for Power Distribution ... 413

Transformer connections...413

Monitoring the master control relay ...416

Sizing the transformer ...416

Transformer separation of power supplies and circuits ...417

Isolation transformers...418

Constant-voltage transformers ...418

Transformer ground connections ...419

11.6 Suppressing Power Surges... 419

Why do they occur?...419

Surge-suppressors ...419

Ferrite beads ...419

Typical suppression circuitry ...420

Examples ...420

11.7 Planning Enclosure Lighting... 422

Minimizing fluorescent lamp interference ...422

11.8 Avoiding Unintentional Momentary Turn-on of Outputs... 422

Minimizing the probability ...422

Minimizing the effect...423

Testing the minimization...423

12. CONTROL PROCESSING CONSIDERATIONS ...425

12.1 Control Processor Load Performance ... 425

Background ...425

Load performance calculation example...425

(20)

Contents

System configuration guidelines ...427

Link Units and I/O Link overruns ...428

Link Unit versus event collection...429

PV and Back Calculation Scanning...429

Link Unit versus output stores...430

Link Unit calculations ...430

IOLIM communication performance ...433

14. MONITORING NETWORK LOADING ...435

14.1 Viewing the ControlNet Loading ...435

15. APPLICATION LICENSING CONSIDERATIONS...437

15.1 Licensing Overview ...437

15.2 Viewing Licenses ...437

15.3 License Validation ...440

Licensing at Configuration time...440

Licensing at Load time ...440

Multiple Block Load scenario ...441

Attempting to launch an Engineering Tool when the license limit is reached ...441

Handling Application failures...441

Maintaining Licensing Information...441

15.4 Online License Change ...442

16. APPENDIX A...443

16.1 Corrosion Protection Planning...443

Conformal coating versus corrosion...443

G3 rating ...443

Gas concentrations ...444

Conformal coating symbol...444

Harsh Environment Enclosure ...445

Model and assembly numbering schemes for conformal coating...446

17. APPENDIX B...447

17.1 Fiber Optic Cable Routing...447

Routing methods...447

Cable A and B separation ...447

Direct burial hazards ...447

(21)

Contents

Vertical fiber migration consideration ...448

Cable jacket indoor building code restrictions ...448

Loose buffered cable usage ...448

Multiple-fiber cable requirements ...448

Indoor cable bend restrictions ...449

17.2 Cable Construction and Installation... 450

Fiber optic cable selection...450

62.5 micron cables ...450

Installation precautions...450

17.3 Cable Splices and Connections... 451

Cabling design considerations...451

Cable splice protection ...451

Cable breakout...451

Use of a breakout kit ...451

Cables with connectors preinstalled ...451

17.4 Signal Loss Budget ... 453

Calculation ...453

Types of splices ...454

Cable distance calculation...455

18. APPENDIX C...457

18.1 Model MU-CBSM01/MU-CBDM01 Cabinets (For PM I/O and Series A

Chassis Only) ... 457

Model MU-CBSM01 Single-access cabinet...457

Model MU-CBDM01 Dual-access cabinet ...458

Top and bottom cabinet entry...459

Independent cabinet entry...461

Cabinet complexing...461

NEMA 12...461

Cabinet cooling ...461

Mounting hardware for C200 Controller chassis...461

Cabinet internal structure ...462

18.2 Equipment Configurations ... 463

Cabinet equipment layout...463

Equipment dimension references ...466

7-Slot and 15-Slot card files installation ...468

18.3 FTA Mounting Channel Configurations ... 469

Vertical FTA Mounting Channel layout ...469

Normal Vertical FTA Mounting Channel orientation ...469

Inverted Vertical FTA Mounting Channel orientation ...470

(22)

Contents

18.4 IOP Cabinet Floor Planning ...473

Floor template ...473

19. APPENDIX D...475

19.1 Model MU-C8SFR1/MU- C8DFR1 Cabinets (For PM I/O and Series A

Chassis Only)...475

CE Compliant...475 Model MU-C8SFR1 Single-access cabinet ...475 Model MU-C8DFR1 Dual-access cabinet ...476 Top and bottom cabinet entry ...478 Independent cabinet entry...479 Cabinet complexing ...479 NEMA 12 ...479 Cabinet cooling ...479 Mounting hardware for C200 (Process) Controller chassis ...479 Cabinet internal structure...480

19.2 Equipment Configurations...481

Cabinet equipment layout ...481 Equipment dimension references...482 7-Slot and 15-Slot card files installation ...484

19.3 FTA Mounting Channel Configurations...486

Vertical FTA Mounting Channel layout...486 Normal Vertical FTA Mounting Channel orientation ...486 Inverted Vertical FTA Mounting Channel orientation...487 FTA Mounting Channel dimensions ...488 FTA installation hole locations ...488

19.4 IOP Cabinet Floor Planning ...489

Floor template ...489

20. APPENDIX E...491

20.1 Power Draw for IOP ...491

Power System considerations...491 Power calculation procedure...491 Component power usage ...492 Single Power System Calculation Example...498 Dual Power System Calculation Examples ...499

21. APPENDIX F ...501

21.1 Galvanically Isolated FTA Planning ...501

Galvanic Isolation Module ...501

(23)

Contents

Usage advantages ...501 CE Compliance ...502 Standby Manual devices and FTA connections...502 Operation limits ...503

21.2 GI FTA Power ... 503

FTA power requirements...503 Power Distribution Assembly...504 Eight 2-pin power connectors ...504 Model MU-KGPRxx cables...504 Same size as A-size FTA ...505 Cabling to Power Distribution Assemblies ...505 Power Distribution Cable length restrictions ...505 Cabling to FTAs ...505 FTA Cable length restrictions ...505 Typical cabinet configuration...506 Marshalling Panel mounting ...507 Additional Power System...507 Avoid using a non-IOP power source ...507 Use surplus power for the FTAs...507 Vertical FTA Mounting Channel cabling assignment ...507 Field wiring restrictions...507 Field wiring routing ...508

21.3 High Level Analog Input (HLAI) FTAs ... 508

Model MU-GAIH12/MU-GAIH82 FTAs...508 Model MU-GAIH13/MU-GAIH83 FTAs...509 Model MU-GAIH14/MU-GAIH84 FTAs...511 Model MU-GAIH22/MU-GAIH92 FTAs...513

21.4 12Vdc Digital Input FTAs ... 516

Model MU-GDID12/MU-GDID82 FTAs...516 Model MU-GDID13/MU-GDID83 FTAs...518

21.5 Analog Output FTAs... 520

Model MU-GAOX02/72 and MU-GAOX12/82 FTAs ...520 Model MC-GHAO11 and MC-GHAO21 FTAs ...521

21.6 12Vdc Digital Output FTAs ... 523

Model MU-GDOD12/MU-GDOD82 FTAs ...523 Model MU-GDOL12/MU-GDO82 FTAs ...524

21.7 Combiner Panel ... 527

Model MU-GLFD02 ...527

21.8 Marshalling Panel ... 528

Model MU-GMAR52...528 Bus bar...528 Mounting ...528

(24)

Contents

22. APPENDIX G ...531

22.1 Honeywell Services ...531

Honeywell support...531 TotalPlant services...531 Experion training ...532

23. APPENDIX H...533

23.1 Configuration Rules for Fieldbus Interface Module (FIM) Topology ..533

The following table lists rules to consider when including Series A FIMs in your control hardware configuration...533

23.2 FIM Performance Limits ...541

23.3 FIM Display-related Performance Limits ...543

Assumptions: ...543

23.4 Series C FIM TCP Connections ...544

23.5 Redundant FIM - Performance Requirements ...544

Initial Synchronization Time ...544 Failure detection time...545 Display connections (ControlNet or FTE)...545 Control connections (ControlNet or FTE)...546 Fieldbus client-server connections...546 Fieldbus publication fail-over time...546 Fieldbus subscription fail-over time...547 Fieldbus alert fail-over time ...547 Impact of FIM cache on fail-over time ...548

(25)

Contents

Tables

Table 1 Allowable combinations of redundant and non-redundant Series A FIMs per

C200 ... 132

Table 2 Redundant controller chassis slot configuration rules... 163

Table 3 I/O chassis configuration ... 170

Table 4 Callout descriptions for Figure 37... 313

Table 5 Quick planning guide ... 327

Table 6 Available repeaters... 336

Table 7 Maximum number of repeaters per link... 339

Table 8 Determining the type of cable you need... 343

Table 9 Connector types and their application ... 349

Table 10 Cabling/routing procedures ... 405

Table 11 Categorizing conductors for noise immunity ... 409

Table 12 Routing conductors for noise immunity ... 412

Table 13 Control Processor load performance calculation example... 425

Table 14 Allowable Redundant and Non-Redundant FIM Combinations per C200

(26)

Contents

Figures

Figure 1 Experion Cluster Type 1 ...46

Figure 2 Experion Cluster Type 2 ...47

Figure 3 Experion Cluster Type 3 ...48

Figure 4 Experion Cluster Type 4 ...50

Figure 5 Experion Cluster Type 5 ...52

Figure 6 Router Connected Topology...54

Figure 7 Common FTE Community Connected Topology...54

Figure 8 Level 2 OPC Server Topology...55

Figure 9 Level 3 OPC Server Topology...56

Figure 10 Resident OPC Gateway Client ...57

Figure 11 Non-resident OPC Gateway Client...57

Figure 12 Simple Experion Inter-Cluster Gateway ...58

Figure 13 Complex Experion Inter-Cluster Gateway and OPC Gateway...59

Figure 14 Example Experion System with Multiple Servers and One EMDB Topology.61

Figure 15 Example Mulitple Experion Systems with Optional DSA Connections and

multiple EMDBs Topology ...62

Figure 16 EAS topology ...63

Figure 17 Sample APS Topology...64

Figure 18 Sample EDS Topology ...66

Figure 19 Sample AS Topology ...67

Figure 20 Basic PHD Integration Topology ...68

Figure 21 Multi-Cluster PHD Integration Topology...69

Figure 22 Sample eServer Topology ...71

Figure 23 Terminal Server Topology ...72

Figure 24 Basic C200 FTE Topology...76

Figure 25 Multiple Experion Cluster C200 FTE Topology ...79

Figure 26 Basic C300 FTE Topology...81

Figure 27 Multiple Experion Cluster with Mixed C300 and C200 FTE Topology ...83

Figure 28 Sample C300 and PLC Interoperable Topology...85

Figure 29 Possible C200 with FTE and ControlNet for Third-Party ControlNet Devices

Topology ...87

Figure 30 Possible C200 using FTE with ControlNet for Rockwell Ethernet Third-Party

Devices Topology ...88

Figure 31 C300 PCDI Topologies...89

Figure 32 Small ControlNet Topology...90

Figure 33 Conjoined Redundant C200 ControlNet Topology...91

Figure 34 Basic ControlNet Topology...92

Figure 35 Experion Server Integrated with PLCs Topology ...94

Figure 36 Small Supervisory CIP Ethernet Topology ...95

(27)

Contents

Figure 38 Integrated SCADA topology ... 97

Figure 39 Multiple ControlNet server DSA topology ... 98

Figure 40 Basic Series A Chassis I/O Topology ... 100

Figure 41 Basic Series A Rail I/O Topology ... 104

Figure 42 Basic PM I/O with C200 and IOLIM Topology ... 105

Figure 43 Basic C300 with Series A Chassis I/O Topology ... 114

Figure 44 Series A Spectrum HART I/O Topology... 116

Figure 45 HART PM I/O Topology... 117

Figure 46 HART Series C I/O Topology ... 119

Figure 47 C200 DeviceNet I/O Topology ... 121

Figure 48 Non-Redundant Series A FIM topology ... 127

Figure 49 Redundant Series A FIM topology ... 130

Figure 50 Basic Series C FIM topology... 133

Figure 51 Maximum C300, Series C FIM and Control Firewall topology ... 135

Figure 52 Typical ControlNet Simulation Topology... 136

Figure 53 Typical FTE Simulation Topology ... 137

Figure 54 Top View of Carrier Channel Assembly with IOTA and resident Series C

form-factor module installed ... 267

Figure 55 View A - CCA Overall Mounting Dimensions ... 269

Figure 56 View B - CCA Cross Section Detail... 269

Figure 57 Typical dc power and battery backup connections in Series C cabinet with

RAM Charger 51199932-100 ... 278

Figure 58 Typical dc power and battery backup connections in Series C cabinet with

RAM Charger 51199932-200 ... 279

Figure 59 Alarm cable connection to the power supply and 24V DI IOTA... 285

Figure 60 Alarm cable connection to the power supply and 24V DI IOTA... 287

Figure 61 LLMUX FTA used with Series C LLMUX IOTA... 289

Figure 62 Remote CJR sensor connected to LLMUX2 FTA MC-TAMT14 ... 290

Figure 63 Typical AC power source through mains panel with safety ground bus and AC

safety (mains) ground rod. ... 309

Figure 64 Typical AC power source through mains panel with safety ground bus, AC

safety (mains) ground, supplementary ground, master reference ground, and

lightning ground rods... 309

Figure 65 Typical safety ground connections in Series C cabinet ... 312

Figure 66 Typical power and ground connections to AC terminal block in Series C

cabinet ... 314

Figure 67 Quad dual access Series C cabinet complex example with C300, Series C

Power Supply, and Series C I/O... 315

Figure 68 Typical power and ground connections for Series C cabinet... 316

Figure 69 Quad dual access cabinet complex example with C300, Series C power

supply, Series C I/O, PM power supply, and PM I/O in Series C and PM cabinets,

respectively... 317

(28)

Contents

Figures

Figure 70 Typical power and ground connections for PM I/O cabinet that is non-EC

compliant...319

Figure 71 Typical PM cabinet safety ground connections. ...320

Figure 72 Quad dual access cabinet complex example with C300 and Series C power

supply in Series C cabinets replacing C200/IOLIM in PM cabinets with PM power

supply and PM I/O ...321

Figure 73 Quad dual access cabinet complex example with C300 and Series C power

supply in Series C cabinets replacing HPM in PM cabinets with PM power supply

and PM I/O...322

Figure 74 Quad dual access cabinet complex example with C300 replacing C200/IOLIM

(29)

1. Introduction

1.1 Overview

About this guide

This guide is intended to provide information to assist you in planning and designing the

installation of your Experion control hardware. Control hardware is an umbrella term

used to refer to the Honeywell control and input/output components that can be supplied

with an Experion system.

This guide complements the Sever and Client Planning Guide that provides planning and

design topics for Experion servers and clients.

Online documentation reference

Knowledge Builder is the online documentation library for the Experion system. It is

provided on a compact disc and can be installed on a suitable personal computer. If you

are using a printed copy of the Control Hardware Planning Guide, we recommend that

you install Knowledge Builder to take advantage of its online search and reference

capabilities.

(30)

1. Introduction

(31)

2. Initial Planning and Design Activities

2.1 Getting

Started

Review Experion capabilities

Read the Overview section in Knowledge Builder so that you understand the basic

concepts and terminology, and appreciate the capabilities of Experion.

Complement the information in this document with the data in the Server and Client

Planning Guide to cover all aspects of an Experion installation.

REFERENCE - INTERNAL

Please refer to the Server and Client Planning Guide for planning and design topics for Experion servers and clients as well as information about adding third-party controllers.

General Prerequisites

Before designing a system, collect as much information as possible about the plant and

its processes. This helps to define the specific control requirements for your plant. The

following mix of skills and plant data are general prerequisites for the planning process.

Skill or Data Purpose

Understanding of Basic Monitoring and Control Concepts

 Need a basic knowledge of the concepts of process monitoring and control to adequately plan your control system installation.

 Need a Process Narrative to provide a literal description of the plant processes

Piping and Instrumentation Diagrams (P&IDs)

 Shows the equipment used in the plant and how it is connected, in schematic format.

 Can be used to break down large processes into constituent subprocesses.

Flow Diagrams  Describes the sequence of events in plant processes.

 Defines how the control system should be used to interact with the processes.

(32)

2. Initial Planning and Design Activities

2.2. Schedules and Responsibilities

Skill or Data Purpose

Engineering and System Specifications  Describe operational requirements; that is, what the system needs to do.

 Describe when and how your Experion system will be implemented.

 Describe details of the Experion system's hardware and software.

Other Resources  Wiring diagrams,

 Computer-aided drafting (CAD) schematics of the plant,

 Other plant layout diagrams, often showing electrical wiring configurations, the location of power cables, and other helpful information.

 Subject-matter-experts (typically engineers) in the process, control, instrumentation, etc., who can provide details that might be missing from schematics and diagrams.

 Process operators who can often tell you how the plant is run, and provide valuable insight into the design of custom displays.

2.2 Schedules and Responsibilities

Pre-installation schedule

After you have selected a suitable location for your system equipment, establish a

schedule incorporating all phases of site preparation and system installation work. Use

the following checklist to schedule and monitor the events that must occur prior to the

actual delivery and installation of your system.

Date Event

Plan Actual Determine whether building modification or construction is

required.

(33)

2.2. Schedules and Responsibilities

Date Event

Plan Actual Determine the requirements, if any, of additional electrical power,

power conditioning, or grounding; arrange for its installation. Determine the locations, pathways, and types of communications data-lines; arrange for their installation.

Implement ElectroStatic Discharge (ESD) and ElectroMagnetic Inteference (EMI) reduction measures.

Complete corrosion analyses for site location.

Determine whether air conditioning is required, then arrange for its installation.

Order cables.

Verify equipment delivery and installation schedule. Order power panels.

Order the required quantity and type of data-line communications equipment necessary for your system application.

Order furniture, storage equipment, and other similar equipment to support your needs.

Thirty days before delivery, complete the following tasks: Install and test primary power equipment.

Install lighting fixtures.

Complete the support facilities (such as media storage). Verify that all required construction, electrical and communications wiring, air conditioning, fire, and smoke-detection equipment installation have been completed.

Notify your Honeywell Account Manager of your facility's state of readiness, or of any

possible contingencies that might delay installation.

(34)

2.3. Shipping and Receiving

Customer responsibilities

In general, you are responsible for preparing your facility as outlined in this guide, so

that the Experion System can be properly installed. Your responsibilities as a customer

are as follows:



Install this equipment in accordance with the requirements of the National Electrical

Code (NEC), ANSI/NFPA 70, or the Canadian Electrical Code (CEC), C22.1.



To furnish and install (at your expense, and sole responsibility) all internal building

wiring (including power and signal cables) in accordance with the NEC or the CEC.



To install any power and signal cables according to the NEC, CEC, and other local

regulations and requirements.



Before shipment, to prepare the premises for installation; to provide installation to

include space, a stable power supply, connectors, cables, and fittings.



For equipment that Honeywell installs, to provide necessary labor for unpacking and

placement of equipment and packing for return.



To provide equipment that is not manufactured or supplied by Honeywell.

2.3 Shipping and Receiving

Shipping

Honeywell ships and insures the Experion System components.

Environmental considerations

Through-out the transit process, the environment must be monitored; correction must be

made if the following controller equipment ratings are exceeded:



Temperature Range: -55° to 85°C (-67° to 158°F)



Humidity Range: 5 to 95% RH non-condensing

CAUTION

(35)

Cost

The following issues should be taken into account in determining shipping costs:



The shipping distance and the weight of the equipment (responsibility of the

purchaser).



Listed equipment weights are adjusted up to 25 percent higher to allow for the

weight of: cables, operating supplies, shipping materials, spare parts, and test

equipment.



Mileage figures used in determining cost can be obtained from the Household Goods

Carriers Bureau Mileage Guide, or from an automobile road atlas.

Receiving

Depending on the tariffs in effect, the carrier may be responsible for placing and delivery

of the system equipment at your facility according to the tariffs in effect.

Moving

Guidelines for moving equipment into your facility (particularly for large systems) are

described below:



Check the maximum equipment dimensions against possible obstacles; these may

include such things as narrow hallways, restricted doorways, and small elevators.



Check for availability and readiness of any necessary devices for moving equipment

to or within your facility. In most cases, the system and its equipment will be

accommodated by the usual equipment-moving devices.



Delays can be avoided by giving the delivery carrier advance notice of any special

requirements. If notified in advance, Honeywell can alert the carrier on your behalf.

Unpacking

When unpacking the equipment, check the shipment against the invoice; immediately

notify your Honeywell Account Manager of any discrepancies.

If a Product Registration Label (containing the Model Number and Serial Number of the

component) is affixed to the shipping carton when received, remove and return it to

Honeywell at the noted address to ensure follow-up service and support.

(36)

Warehousing

In some instances, it may be necessary to temporarily store the system components

before installation. In this event, keep the factory wrapping intact to minimize humidity.

If it is necessary to unseal the equipment for customs or receiving, add more desiccant;

then reseal the package.

Ensure that the selected storage area does not subject the equipment to environmental

extremes beyond those listed in the previous section.

(37)

3. Control Network Considerations

3.1 Communications

Network

New or existing network

The first thing to consider when designing a control system network is whether the

system will be incorporated into an existing network, or a new network will be

implemented.



If planning a new network, you need to consider issues such as the network

architecture to use.



If planning to use an existing network, you will have to determine how to integrate

the networks as seamlessly as possible. If the existing network has a system

administrator, they should help with the integration.



If a complex network is being planned, it might be advisable to consult professional

network designers. Honeywell can design and implement your network, if desired.

3.2 Identifying topology diagram symbols

About the symbols

The symbols listed in the following table are used to simplify the node and component

references to reduce the size and enhance the readability of the topology diagrams

included in this document.

If Symbol is . . . Then, it represents

Native Experion Computer-Based Components

Experion Server

Redundant Experion Server

(38)

3. Control Network Considerations

3.2. Identifying topology diagram symbols

Experion Console Station

Experion Console Extension

Experion with TPS Computer-Based Components

Experion Server (TPS) used with TPS Systems and connected to the TPN (LCN) Network

Redundant Experion Server (TPS) used with TPS Systems and connected to the TPN (LCN) Network

Application Control Environment (TPS) used with TPS Systems and connected to the TPN (LCN) Network

Experion Console Station (TPS) used with TPS Systems and connected to the TPN (LCN) Network

Experion Level 3/Level 4 Application Components

Experion Application Server

PHD Server

(39)

Experion Desktop Server

Application Point Server

Application Server

Experion Desktop Workstation

Miscellaneous Computer-Based Components

Windows 2003 Domain Server

Windows 2000 Domain Server

Third-Party OPC Server

Third-Party OPC Client

Windows Terminal Server

(40)

Experion Series A Embedded Control Components C200 Controller

Redundant C200 Controller

Series A Chassis I/O

Series A Rail I/O

Series H Rail I/O

I/O Link Interface Module

Redundant I/O Link Interface Module

Legacy I/O Module

Redundant Legacy I/O Module

(41)

Redundant Series A FIM (Chassis)

Fault Tolerant Ethernet Bridge Module

Redundant Fault Tolerant Ethernet Module

Experion Series C Embedded Control Components C300 Controller

Redundant C300 Controller

Series C I/O

Redundant Series C I/O

(42)

Redundant Series C FIM (FIM4)

Control Firewall (9-Port)

Miscellaneous Embedded Control Components

Fail Safe Controller (FSC)

Safety Manager

Miscellaneous Network Components

Cisco Switch

Cisco Fault Tolerant Ethernet (FTE) Switches

Cisco Router

Network Firewall

(43)

Legacy TPS Components

xProcess Manager

Process Manager I/O

Network Interface Module

Universal Station

(44)

3.3. Experion cluster types

3.3 Experion cluster types

Overview

The following Table provides a summary of the various general Experion Server/Cluster

Network configurations possible with Experion R310 and later. The sections that follow

provide more information and diagrams to explain each configuration type.

Not all network combinations are shown, but the examples, along with the associated

Configuration Rules, provide you with the necessary guidelines to understand how

Experion systems may be configured.

In the Table, the term Process means an Experion system with C200, C300, and /or ACE

Controllers, and so on. Any Process system may also include SCADA devices and so on.

SCADA only systems do not include C200, C300, or ACE Controllers.

Cluster Type Application (Process/ SCADA) Level 1/Level 2 Network Choices Level 3 Network Choices See Note ControlNet Process CIP Ethernet Non-Redundant Ethernet 1 1: L3 Ethernet

SCADA Misc Non-Redundant

Ethernet 2 ControlNet Process CIP Ethernet Dual Ethernet 1 2: L3 Dual Ethernet

SCADA Misc Dual Ethernet 2

Process ControlNet FTE 3

3: L3 FTE

SCADA Misc FTE 2

Ethernet

4: L2 FTE Process FTE

FTE 2, 4 Ethernet 5: TPS TPS, Process and SCADA LCN/UCN and/or FTE FTE 2, 5

(45)

Cluster Type Application (Process/ SCADA) Level 1/Level 2 Network Choices Level 3 Network Choices See Note Notes:

1. Level 2 CIP Ethernet means non-redundant Ethernet using Ethernet Module TC-CEN021.

2. The Misc equals SCADA Network(s) that may consist of Serial Devices (RS232 or RS485),

ControlNet Connections, and/or Ethernet Interfaces (for example, MODBUS TCP) or combinations of these. In addition, SCADA points and connections may coexist with C200s and TPS within specified capacity constraints.

3. Level 1/Level 2 CIP Ethernet from Servers to C200s is not supported when using Level 3 FTE based Clusters.

4. Level 3 is Router connected when using FTE for L2 Supervisory Network. L3 may then be separate FTE community or normal non-redundant Ethernet.

5. When FTE-based Controllers are used with a TPS Cluster, then FTE must also be used as an additional L2/L1 Network, and L3 then becomes router connected. Otherwise, the Ethernet/FTE connected to the TPS connected computer nodes is considered the L3 Network.

Experion Cluster Type 1

The following topology is a small Experion cluster network configuration. This

configuration can be specified to ship from the factory when a non-redundant cluster is

specified. This cluster is a small computer workgroup that uses local accounts and is not

commonly connected to any other Ethernet network. The Server may or may not be

connected to a ControlNet Supervisory Network depending on whether it is a C200

and/or SCADA application. Typically, redundant servers use a redundant network

solution; so redundant servers are not typical for this configuration type.

Characteristics



Single Ethernet



Redundant or Non-Redundant Server (shown)



Windows Server 2003 Operating System



Local Windows or Traditional Accounts

(46)

Figure 1 Experion Cluster Type 1

Configuration Rules (CT1)

Reference Description

CR_CT1.0 Experion users may use Windows group-based accounts, Windows accounts, or Traditional operator accounts. If using Windows accounts, using a Windows Domain controller and Domain based Windows accounts is strongly

recommended for account maintenance, especially as the number of nodes increases.

CR_CT1.1 Experion services use local Windows accounts.

CR_CT1.2 All Experion nodes are configured to be part of the same Workgroup or Domain, if used.

CR_CT1.3 Only Windows 2003 Server is supported as the operating system for the Experion server.

CR_CT1.4 Only Windows XP is supported as the operating system for the Experion Flex Station.

CR_CT1.5 Server may use a Dual CPU configuration.

Experion Cluster Type 2

The following topology is a small to medium Experion cluster network configuration.

This is the configuration shipped from the factory when a redundant cluster is specified

without FTE. This cluster is a small computer workgroup that uses traditional accounts

and is commonly not connected to any other network. If Windows accounts are to be

used for operators, in a redundant server topology, a Windows domain controller is

strongly recommended for account maintenance. The Server may or may not be

connected to a ControlNet Supervisory Network depending on whether it is a C200

and/or SCADA application. Typically, redundant network solutions support redundant

servers, so a non-redundant server is not typical for this configuration type.

(47)

Characteristics



Dual Ethernet



Redundant (shown) or Non-Redundant Server



Windows Server 2003 Operating System



Traditional or Windows Accounts



Workgroup or Domain

Figure 2 Experion Cluster Type 2

Configuration Rules (CT2)

CR_CT2.0 Experion users may use Windows group-based accounts, Windows accounts, or Traditional operator accounts. If using Windows accounts, using a Windows Domain controller and Domain based Windows accounts is strongly

recommended for account maintenance, especially as the number of nodes increases.

CR_CT2.2 All Experion nodes are configured to be part of the same Workgroup or Domain, if used.

CR_CT2.3 Only Windows 2003 Server is supported as the operating system for the Experion server.

CR_CT2.4 Only Windows XP is supported as the operating system for the Experion Flex Station.

(48)

Experion Cluster Type 3

The following topology is an example of a medium to large Experion cluster

configuration. You can connect from 1 to 60 Flex Stations to the Experion server. The

server may or may not be connected to a ControlNet Supervisory network (shown)

depending on whether it is a C200 and/or SCADA application. Typically, FTE solutions

are used with redundant servers, so a non-redundant server is not typical for this

configuration type.

Characteristics



FTE Level 3 Network



Redundant (shown) or Non-Redundant Server



Windows Server 2003 Operating System (for Experion server)



Traditional or Domain Windows Accounts



External Network

(49)

Configuration Rules (CT3)

CR_CT3.0 Experion users may use Windows group-based accounts, Domain Windows accounts or Traditional operator accounts.

CR_CT3.2 Experion operator based security has been qualified with Windows 2000 native mode and Windows 2003 domains - all modes.

CR_CT3.3 Experion nodes may be part of a Windows Domain

CR_CT3.4 In a Domain configuration, all nodes in the Experion cluster should be time synchronized with the Domain controller or dedicated NTP Server. CR_CT3.5 In a workgroup configuration, the time must be synchronized between

redundant servers and all console stations in the Experion cluster. They should also be synchronized with any other clusters connected through the Distributed Server Architecture (DSA).

CR_CT3.6 A Windows 2000 (W2K) Domain controller (shown) cannot be directly

connected through FTE. It must be configured as a single-connected node on either of the FTE segments or through a router in the Level 3 network. If using a backup Domain controller, we recommend that you single-connect it to the opposite FTE segment.

CR_CT3.7 A Windows 2003 (W2K3) Domain controller (not shown) is supported on FTE. The FTE Driver must be installed in the Domain server node.

CR_CT3.8 The Experion servers use Windows 2003 server operating system (OS). However, Experion MUST NOT be installed on a Domain controller. For example, neither the Experion server nor the ACE node can reside on the same server node as the Domain controller.

CR_CT3.9 FTE requires the use of qualified switches. Please refer to the FTE Technical Data and Specification document for the latest FTE configuration rules. CR_CT3.10 The ACE node runs on Windows 2003 server operating system and must be a

member of the Domain, if a Domain is configured.

CR_CT3.11 Only one System Event Server (SES) must be installed per FTE Community. If Experion servers are redundant, the SES is installed on both servers. The System Management runtime software should be installed on all nodes in the Experion cluster that are to be monitored by the System Event Server. The

(50)

cluster nodes being monitored by the System Event Server

CR_CT3.12 The System Management runtime software should be installed on all nodes that are to be monitored by the System Event Server. The time should be synchronized between the redundant servers and all Experion cluster nodes being monitored by the System Event Server

CR_CT3_13 The High Security Policy Workstation Package should be installed on the redundant servers.

Experion Cluster Type 4

The following topology is an example of a medium to large Experion cluster

configuration with Console Stations and FTE-based Controllers (not shown). You can

connect from 1 to 40 Stations to the Experion server, of which up to 11 of these Stations

can be configured as Console Stations within the Console Station configuration limits.

Typically, FTE solutions with FTE Bridge module and Console Stations are used with

redundant servers; so a non-redundant server is not typical for this type of configuration.

Characteristics



FTE Level 2 Network



Redundant Server



Windows 2003 Server Operating System (for Experion server)



Domain Windows Accounts



External Network Router

