Title: Plant Information Systems Architecture for Integration into Control Rooms IAEA Technical Meeting on
1Plant Information Systems Architecture for
Integration into Control Rooms IAEA Technical
Meeting on Integration of Analog and Digital IC
Systems in the Main Control Room (MCR) (Oct. 29
Nov. 2)
- Mike Benjamin
- Computers and Control Design Department
2OPG Plant Information (PI) System Evolution
- Monitoring requirements exist beyond those
provided by the current Digital Control Computers
(DCCs). - As with the DCCs, there is a need to deal with
the Human Machine Interface (HMI) obsolescence. - There are also enhanced display requirements.
- Our intention is not to expand the existing
display functionality in the DCCs, but to augment
the display functionality using other tools. - Over the years various techniques have been
employed to expand and enhance process monitoring
and display capabilities. - Focus of presentation is the evolution of OPGs
use of the PI tool, and our future plans for its
use.
3OPG PI System Evolution contd.
- Initial impetus for installation of PI was to
support Performance Engineering (PE). - DCC Gateways and a PI Process Historian were
installed at each site to provide tools to
perform surveillance and process troubleshooting.
- 1996 Darlington
- 1999 Pickering B
- 2001 Pickering A
- PI (Plant Information) System
- commercial tool with wide utility use
- interfaced to real-time plant computers
4Typical Architecture for PE Support
5PI Surveillance Tools
- System and Process Monitoring
- Automated system health monitoring
- Email notification of process alarm thresholds
and reports - ART - Alarm Retrieval Tool
- Integration of process annunciation and data
trending
6Darlington Production History
- Unit 2 in service
- Unit 1 in-service
- Unit 3 in-service
- Unit 4 in-service
- 60 NOP Trip Setpoint
- The gap (N-12 event) between the Unit 2 and U1
in-service dates was caused by fuel bundle
cracking from a natural frequency resonance
between the pump impeller and the PHT system - LOBES event 2003-08-14 (loss of power grid)
1990/02/21
2007/04/17
17.16 years
7System Health Monitoring
8ART- PI - Passport Integration
Alarms
Trends
Alarm Response Manual
Alarm Statistics
9Migration Towards Operational Support
- Recent migration towards real-time Engineering
support for Control Room surveillance - PIMS - Interactive tool used by Plant Operations
to calculate and prepare shift leak detection
reports used by Shift Advisor Technical (SAT). - Heat Balance, Thermal Efficiency calculation
support.
10PIMS - PHT Inventory Monitoring
11PIMS Leak Detection (May 2007)
Leak Rate
Error Bars
12ANO Support in MCR
- A recent study assessed the use of the Plant
Information System for control room tasks. - In this study, the typical categorization
question was reversed. - The question became Given a Historian system
qualified to a nuclear related Category III
software level, what control room tasks could
make use of the data?. - A key conclusion of the study is that a Category
III system could be used to perform panel checks,
provided that the data is periodically checked
against other qualified sources. - A project has now been initiated to install a
Category III Historian system in the MCR.
13System/Architectural Objectives
- Provide a qualified (Category III) Data
Historian, operating on a protected, isolated
Process LAN. - Architecture to minimize the number of special,
stand-alone interface computers that are
required. - Feed data from Nuclear Safety Related Systems
such as the DCCs, Safety System Monitoring
Computer, and Data Extraction Systems, and from
engineered systems of concern in terms of
production, environment or cyber security i.e.,
monitoring systems such as Meteorological Tower,
Algae, Lake Current, and Generator Temperature. - Make this data available in the MCR using a
qualified Human Machine Interface, to augment,
rather than replace, existing displays. - Transfer the data across a firewall to a
historian on the Business LAN for permanent
storage, and use by Performance Engineering. - Establish the appropriate level of engineering
controls and security, that will allow the
systems to be effectively configured, controlled
and maintained, at a reasonable cost, and time
frame.
14Conceptual Architecture
15Site Emergency Centre
- Process LAN can be extended some distance from
the MCR
16Some Design Issues for MCR System
- Availability of data less important than
correctness of data. - Need to ensure that any loss of data is promptly
detected and flagged. - Which systems to place on the Process LAN?
- Resolve perceived risks of combining data from
Nuclear Safety and Non-safety (but systematically
engineered), systems. - Historian availability requirements, and the
design alternatives that result from this
decision. - Should Historian design be Unitized?
- Length of history required to be stored (likely 1
month). - Can data be lost if the Historian fails.
- Is redundancy/backup required?
- Hardware procurement QA level requirements.
- Finding available real estate in the MCR.
- Each display will require Human Factors review to
ensure suitability for Operator use.
17Project Outline
- Darlington has been selected as the pilot site.
- Project funding approved in 2007 with a detailed
project plan to be completed in first half of
2008. - Project scope is to develop and implement the
architecture and provide operator support for
panel checks, as well as creating a number of
process displays. - Scope also includes replacement of the existing
Gateway computers to deal with obsolescence.