23.03.2017 Views

wilamowski-b-m-irwin-j-d-industrial-communication-systems-2011

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

29-4 Industrial Communication Systems<br />

are listed in the IEC 61226 recommendations. There are typically three classes of instrumentation and<br />

control functions for European pressurized reactor (EPR):<br />

• F1A functions, which are performed by the reactor protection system, RPS (automatic reactor<br />

trip, actuation of the engineered safeguard <strong>systems</strong> and their supporting <strong>systems</strong>), and by the<br />

priority and actuator control system, PACS. This is the strongest safety rule where the behavior<br />

must be deterministic.<br />

• F1B functions, which are performed mainly by the safety automation system (SAS) and by the<br />

safety information and control system (SICS). In this class, the behavior must be predictive.<br />

• F2 functions, which are performed by the process automation system (PAS); the process information<br />

and control system (PICS); and the reactor control, surveillance, and limitation system<br />

(RCSL). F2 functions can be either seismic classified (F2E functions) or non-seismic classified<br />

(F2N functions).<br />

The priority rules are defined as follows:<br />

• Higher class functions have priority over low-class functions; so, F1A has priority over F1B,<br />

which has priority over F2 functions. Higher class functions must not be disturbed by lower class<br />

functions.<br />

• The order of priority within each control system is defined as follows: system and component<br />

protection has priority over automated functions, which has priority over manual functions.<br />

Automatic functions can be switched off if the process conditions allow it.<br />

29.3 Power Plant Information Systems<br />

and Extra-Plant Communications<br />

Power plant information system plays an important role in operational performance. A well-designed<br />

power plant information system helps to achieve operational efficiency by providing secure access to the<br />

right information at the right time to the right person. It concerns in particular the integration of power<br />

plant information system with enterprise business information system. It represents a challenging task<br />

because these <strong>systems</strong> do not have a same lifecycle in terms of evolution and technology used.<br />

The need of accessing process data for doing business intelligence or e-monitoring from a remote<br />

expertise is the major motivation. Having standardized power plant information model and business<br />

meta-model helps to reduce complexity in the integration of power plant information system and business<br />

information system. IEC TC57-WG13 Common Information Model (CIM) provides a standard<br />

and basic description of power plant assets.<br />

29.3.1 Common Information Model<br />

The most important extra-power plant <strong>communication</strong> is the information exchange for real-time and<br />

non-real-time information, used in the planning, operation, and maintenance of power <strong>systems</strong>. IEC<br />

TC57 WG3 and WG13 have defined, respectively, telecontrol protocols and energy management system<br />

for real-time and non-real-time power control between the grid dispatching center and a power plant<br />

control room.<br />

The European Transmission System Operators (ETSO) organization also works closely with IEC<br />

TC57 to define the CIM, IEC-61970-301 as the reference model for electric energy trading and for the<br />

power system operation. The CIM provides, for example, a standard and basic description of power plant<br />

assets. Generation, load model, outage, SCADA, energy scheduling, and financial packages (Figure 29.4)<br />

are typically defined in the TC57-WG13.<br />

© <strong>2011</strong> by Taylor and Francis Group, LLC

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!