The Computer in BWR Operations - Present and Future

The current General Electric Boiling Water Reactor process computer is a conventionally architectured, medium sized, monolithic system based upon the GE-PAC* 4010. The system performs scan, log, and alarm functions, as well as some rather complicated nuclear steam supply and turbine generator perfor...

Full description

Saved in:
Bibliographic Details
Published in:IEEE transactions on nuclear science 1973-01, Vol.20 (1), p.740-744
Main Authors: Sweet, William B., Conklin, David R.
Format: Article
Language:English
Subjects:
Application software
Computer architecture
Control systems
Distributed computing
Distributed control
Hardware
High performance computing
Inductors
Nuclear power generation
Turbines
Citations: Items that cite this one
Online Access:Get full text
Tags: Add Tag
No Tags, Be the first to tag this record!
Description
Summary:The current General Electric Boiling Water Reactor process computer is a conventionally architectured, medium sized, monolithic system based upon the GE-PAC* 4010. The system performs scan, log, and alarm functions, as well as some rather complicated nuclear steam supply and turbine generator performance calculations. However, over the years, the G.E. system designers in San Jose have become aware of both the limitations of the monolithic architecture as applied to the rapidly growing nuclear applications as well as the recent tremendous advances in computer hardware technology. What has emerged is the concept of a distributed computer control system primarily designed for the G.E. BWR, but also ideally suited for other applications. Built around a high speed common data base memory, the distributed system yields a giant improvement in terms of overall computer system modularity, software simplicity, versatility, price/performance ratio, availability, and functional capability. The G.E. design is built around two major changes in philosophy in terms of applying process computers to an application: (1) Force the computer architecture to fit the man and the application, and (2) Increase the hardware content and complexity whenever it is consistent with reducing the software complexity and cost.
ISSN:0018-9499
1558-1578
DOI:10.1109/TNS.1973.4326991