1. PROJECT TRAINING REPORT
ON
plant data history viewer
BY
anju gopalkrishnan
siontani datta
joyita saha
shatarupa chowdhury
(2014-2015)
PROJECT GUIDE:
Mr. nilesh gohel
(Head, Industrial Tomography
And Instrumentation Section)
Project Training report on Plant Data History Viewer
PLANT DATA HISTORY VIEWER Page 1
3. ACKNOWLEDGEMENT
We express our sincere thanks to Dr. Kallol Roy, Head, Research Reactor Maintenance Division,
B.A.R.C., for allowing us to undergo one month training at B.A.R.C.
We take this opportunity to express our profound gratitude and deep regards to our guide Mr. Nilesh
Gohel, for his exemplary guidance, monitoring, cordial support and constant encouragement
throughout the course of this project. It was a great opportunity and privilege to work under his able
guidance, without whom it would not have been possible to complete our training. His sound
knowledge and expertise always helped us. We are grateful for the cooperation during the period of
our assignment. The blessing, help and guidance given by him, time to time shall carry us a long
way ahead.
Lastly, we thank almighty, our parents and friends for their constant encouragement without which
this assignment would not be possible.
ABSTRACT
PLANT DATA HISTORY VIEWER Page 3
4. This report documents the work done during the project training at B.A.R.C., Mumbai under the
supervision of Mr. Nilesh Gohel.
The report presents following tasks completed during summer internship at B.A.R.C.:
1. Training was provided on Object Oriented Programming Principles & Applications, Design
Patterns, etc. This served purpose for creation of an application based on Object Oriented
Programming.
2. Task assigned to us was to create an Application based on .NET framework using
Object Oriented Programming in C#. This system is developed using Visual studio 2010 (WPF).
Database requirements are handled by MS Access.
This system is used to capture the signals generated by reactor per second. These signals have
various parameters such as Temperature , Pressure , Pump speed ,Pump Horsepower, Radiation
content, Density, Mass, Volume etc.
These parameters can be monitored continuously and can be queried as per the users requirements.
Normal range of the parameters are set & alarm is generated when they go out of range.
PLANT DATA HISTORY VIEWER Page 4
5. CONTENT
1. INTRODUCTION
1.1. ORGANISATION PROFILE
1.2. PROJECT OVERVIEW
2. LITERATURE SURVEY
2.1. RADIATION
2.2. DETECTORS
3. TOMOGRAPHY
3.1. WHAT IS TOMOGRAPHY?
3.2. WHAT IS DONE IN TOMOGRAPHY?
3.3. APPLICATIONS OF TOMOGRAPHY
3.4. TOMOGRAPHY WORK AT B.A.R.C.
4. SYSTEM OVERVIEW
4.1. INTRODUCTION
4.2. SYSTEM DESCRIPTION AND PERFORMANCE
4.3. HARDWARE
4.3.1. BLOCK DIAGRAM
PLANT DATA HISTORY VIEWER Page 5
6. 4.3.2. SERIAL COMMUNICATION
4.3.3. OVERVIEW OF ALL COMPONENTS
4.4. SOFTWARE
4.4.1. FLOWCHART
4.4.2. GRAPHICAL USER INTERFACE
4.4.3. PROGRAM DESCRIPTION
4.4.4. SOME IMPORTANT FUNCTIONS USED
5. CONCLUSION
6. BIBLIOGRAPHY
PLANT DATA HISTORY VIEWER Page 6
7. 1.INTRODUCTION
1.1 ORGANIZATION PROFILE
BHABHA ATOMIC RESEARCH CENTRE (B.A.R.C.) is a premier research institute of India
established in 1964 in a remote area of Mumbai known as Trombay. B.A.R.C. is situated in between
the hills on one side and the Arabian Sea on the other. Its beautiful campus and excellent ambience
always inspires the people here to carry out their research and development with zeal. B.A.R.C has
always been doing research in cutting edge technologies and it has taken a prominent place in Non-
Destructive Testing (NDT) technology worldwide.
B.A.R.C consists of various divisions who are devoted to carry out Research and Development in
various fields of Science and Technology. The main aim of Isotope Application Division is to
develop appropriate technology for the application of Nuclear Radiation in basic and applied
sciences, medicine, industry, agriculture, defense, population control and many more.
1.2 SCOPE & METHODOLOGY
It is very essential that the reactor parameters stay in the range for it to function correctly. for this
reason the reactor performance has to be continuously monitored and a normal range is set. If the
PLANT DATA HISTORY VIEWER Page 7
8. values of the parameters go beyond this range then an alarm is generated accordingly thus informing
the user to take appropriate actions.
Main concepts used are Object Oriented Programming & its Applications in C# and the .NET
Framework.
The goal of C# is to provide a simple, safe, modern, object oriented, internet centric, high
performance language for .NET development.
Object-oriented programming (OOP) is the core ingredient of the .NET framework. The
fundamental idea behind OOP is to combine into a single unit both data and the methods that
operate on that data; such units are called an object. All OOP languages provide mechanisms that
help you implement the object-oriented model. The important mechanisms are encapsulation,
inheritance, polymorphism.
The .NET platform is in essence a new development framework that provides a fresh application
programming interface (API) to the services of Windows OS.
2. LITERATURE SURVEY
2.1 .NET Framework
PLANT DATA HISTORY VIEWER Page 8
9. Fig. 2.1 .NET Framework
The .NET framewrk consists primariliy of a gigantic library of code that can be used from client
languages (such as c#) using object oriented programming techniques. It sits on top of the operating
system which can be any flavour of Windows, and consists of a number of components, currently
including-
• four official languages C#, VB.NET, managed C++ and JScript.NET.
• The CLR (COmmon Language Runtime) an object oriented platform for windows and web
development that all this languages share.
• A number of related class libraries collectively known as the FCL (Fremwork Class library).
2.2 Object Oriented Programming in C#:
C# is a general-purpose, type-safe, object-oriented programming language. It is an evolution of the
PLANT DATA HISTORY VIEWER Page 9
10. C and the C++ languages and has been created by Microsoft specifically to work with the .NET
platform. C# includes all the support for structured, component based, object oriented programming
that one expects derived from C++ and Java.
C# is a rich implementation of the object-orientation paradigm, which includes OOP techniques
some of which are listed below.
Encapsulation:
Encapsulation binds together code and the data it manipulates and keeps them both safe from
outside interference and misuse. Encapsulation is a protective container that prevents code and data
from being accessed by other code defined outside the container.
Inheritance:
Inheritance is the process by which one object acquires the properties of another object. A type
derives from a base type, taking all the base type members fields and functions. Inheritance is most
useful when you need to add functionality to an existing type. For example all .NET classes inherit
from the System. Object class, so a class can include new functionality as well as use the existing
object's class functions and properties as well.
Polymorphism:
Polymorphism is a feature that allows one interface to be used for a general class of action. This
concept is often expressed as "one interface, multiple actions". The specific action is determined by
the exact nature of circumstances.
Classes and interfaces:
In a traditional object-oriented paradigm, the only kind of type is a class. In C#, there are several
other kinds of types, one of which is an interface. An interface is like a class, except that it only
describes members. The implementation for those members comes from types that implement the
interface. Interfaces are particularly useful in scenarios where multiple inheritance is required.
Events:
The GUI such as Microsoft windows require that the program respond to events. An event can be a
button push, menu selection, completion of a file transfer and so forth. Objects may raise events as
part of their processing. Event handler is a special type of function that is called when the event
occurs.
PLANT DATA HISTORY VIEWER Page 10
11. 2.3 Visual Studio 2010:
Microsoft Visual Studio is an integrated development environment (IDE) from Microsoft. It is
used to develop computer programs for Microsoft Windows super family of operating systems, as
well as web sites, web applications and web services. Visual Studio uses Microsoft software
development platforms such as Windows API, Windows Forms, Windows Presentation
Foundation, Windows Store and Microsoft Silverlight.
Visual Studio includes a code editor supporting IntelliSense as well as code refactoring. The
integrated debugger works both as a source-level debugger and a machine-level debugger. Other
built-in tools include a forms designer for building GUI applications, web designer, class designer,
and database schema designer.
Visual Studio supports different programming languages and allows the code editor and debugger to
support (to varying degrees) nearly any programming language, provided a language-specific
service exists.
2.4 Windows Presentation Foundation:
Windows Presentation Foundation (or WPF) is a graphical subsystem for rendering user
interfaces in Windows-based applications by Microsoft. WPF, previously known as "Avalon", was
initially released as part of.NET Framework 3.0. WPF attempts to provide a consistent
programming model for building applications and separates the user interface from business
logic.WPF employs XAML, an XML-based language, to define and link various interface elements.
As the name says all, WPF is actually a new framework introduced with .NET framework 3.0 which
actually puts forward a new set of classes and assemblies which allow us to write programs more
efficiently and flexibly. It uses Direct3D rendering which employs graphics cards to render the
output on the screen. Thus the drawing in the form will be smooth and also there is a chance to
utilize the hardware capabilities installed in your machine. In case of traditional GDI forms
application, it is not possible to use advanced graphics capabilities and hence Windows Forms
application is inefficient in comparison to WPF. WPF controls are actually drawn over the screen,
and hence you can customize controls totally and modify their behavior when required.
PLANT DATA HISTORY VIEWER Page 11
12. 3. SYSTEM OVERVIEW
This system is made for monitoring the reactor state by analyzing its parameters & signals
generated. Tool used for running the application is Visual studio. The front end is based on
Windows presentation foundation & XAML. C# has been used for Object Oriented Programming.
The back end consists of MS Access database.
PLANT DATA HISTORY VIEWER Page 12
13. 3.1 Class Diagram:
Fig. 3.1 Class Diagram
The classes of the above class diagram are described below:
1. Signal Configuration class:
This class is used to store information about various parameters of the reactor like Signal
Name, Signal ID, Signal Range, Signal Low Set Point, Signal high set point ,Signal unit, etc.
PLANT DATA HISTORY VIEWER Page 13
14. 2. Periodic Data class:
This class holds the attributes of periodic data to be generated. The record is stored in an
array which is further passed to Periodic data generator class. Some of the attributes are
Time stamp, Temperature , Pressure, Pump speed, etc.
3. Periodic Data Generator class:
This class generates data periodically i.e. every 1 second. The data generated is stored in
database & can also be displayed in Data Grid. History data or Online data can be generated
as per requirements.
4. Alarm Data:
This class holds the attributes of alarm data to be generated. The record is stored in an array
which is further passed to Alarm data generator class. Some of the attributes are Time stamp,
Parameter Name, Parameter value, Alarm status , etc.
5. Alarm generator class:
This class analyzes the periodic data generated by the above class & based on set point
values of respective signals, generates High alarm or Low alarm if present. Otherwise the
signal is tagged to be normal.
6. Toolkit class:
This class initializes various signal parameters and creates a List of signal configuration
class. It also instantiates the timer to invoke Periodic data generator class. It further invokes
alarm generator , thus playing the centralized role in this system.
3.2 Activity Diagram:
The activity diagram for the implemented system is as below:
PLANT DATA HISTORY VIEWER Page 14
16. 4. APPLICATION GUI
The GUI is separated using two tab controls - Periodic Data & Alarm Data. On running the
application, active tab is Periodic data & automatic Periodic data is generated per second and stored
in its respective table (periodic data table) in database. The data generated can be displayed on
datagrid on clicking "Get Online data" button.
There are two dateTime pickers which are used for giving the "From" and "To" dates and time. Also
there are various checkboxes for the checking on the different parameters as per the users
requirements. The result is obtained by clicking on the "Search" button and displayed on the data
grid .
"Get History Data" button outputs all the periodic data which has been archived. "Clear" Button is
used to clear the contents of datagrid.
On selecting "Alarm Data" tab, each record in periodic data table are analyzed and corresponding
alarms are given. Each parameter has specific normal range. Set point low and Set point high are set
& if parameter values go beyond the normal range, Low & High Alarms are generated accordingly.
The Alarm record consists of : Time Stamp, Parameter value, Parameter name & Alarm Status. This
record is stored in its respective table (alarm data table) in database.
The screenshots for the application are as follows-
PLANT DATA HISTORY VIEWER Page 16
17. Fig 4.1 History Data
Fig 4.2 On clicking Get online data
PLANT DATA HISTORY VIEWER Page 17
18. Fig 4.3 Search based on User requirements
Fig 4.4 Search when "All" is selected
PLANT DATA HISTORY VIEWER Page 18
19. Fig. 4.5 Alarm data is generated on clicking Alarm Data Tab
PLANT DATA HISTORY VIEWER Page 19
20. REFERENCES & BIBLIOGRAPHY
1. Troelsen, Andrew, Pro C# with .NET 3.0, Apress
2. Watson, Karli, Beginning Microsoft Visual C# (2008), Wrox
3. Albahari, Joseph; Albahari, Ben, C# 5.0 IN A NUTSHELL, O'Reilly
PLANT DATA HISTORY VIEWER Page 20