Integrated Nuclear Security Network (INSN) Centralized Data Acquisition and Analysis System for Radiation Portal Monitors (RPM)

Integrated Nuclear Security Network (INSN)

Centralized Data Acquisition and Analysis System

for Radiation Portal Monitors (RPM)

Course Outline

I. IntroductionA. Purpose of Integrated Nuclear Security NetworkB. DefinitionsC. Basic ArchitectureD. User Profiles and Responsibilities

II. Getting StartedA. InstallationB. ConfigurationC. Data Acquisition

III. AnalysisA. ViewsB. Scenarios

IV. Standard Operating ProceduresA. Minimum RecommendationsB. Data Backup

V. ConclusionsA. ExercisesB. Questions and Answers

I. A. Purpose of INSN

What it is• System for networking sites to a central location(s)

– System = network, hardware, software• Designed for specific purposes

– Obtaining Daily Files automatically– Analyzing data for status of health and trend monitoring– Tool for communication with site operators, maintenance and trouble-

shooting– Secondary function to obtain User Files (alarm reports, RID files,

others) for Headquarters and/or alarm support organizations

What it is not• Real-time remote surveillance/alarm relay tool• Replacement for Front Line Officers, Central Alarm Station• Does not provide all answers automatically

– Human interaction is required– Tool facilitates information sharing among key stakeholders

What it is• System for networking sites to a central location(s)

– System = network, hardware, software• Designed for specific purposes

– Obtaining Daily Files automatically– Analyzing data for status of health and trend monitoring– Tool for communication with site operators, maintenance and trouble-

shooting– Secondary function to obtain User Files (alarm reports, RID files,

others) for Headquarters and/or alarm support organizations

What it is not• Real-time remote surveillance/alarm relay tool• Replacement for FLOs/FLO training• Does not provide all answers automatically

– Human interaction is required– Tool facilitates information sharing among key stakeholders

I. A. Purpose (Cont’d)

I. B. Definitions

INSN – Integrated Nuclear Security NetworkSystem (hardware, software, communications infrastructure) for collecting data from RPMs for monitoring Status of Health and enabling expert assistanceNDAC – National Data Analysis CenterLocation of the main workstation where data from CASs is acquired and analyzedASC - Alarm Support Center Location where experts for alarm resolution assistance resides, often (though not necessarily) a separate workstation at a location separate from the NDACCAS – Central Alarm StationWorkstation and/or server at border crossing points obtaining all data (associated with radiation detection systems), and enabling Front Line Officer resolution of alarmsDaily Files – Text file of raw RPM data recorded by the Central Alarm StationFiles are generated on a daily basisFiles contain information regarding occupancies, alarms, and other conditions Status of Health – Ability of the system to perform as designedStatus may be healthy or unhealthy (includes equipment, network connection, operations)Healthy Site – System performs as designed with no failures in equipment, network, or operationsUnhealthy Site – System does not perform as designed, experiencing failures in equipment, network, and/or operations

I. C. Basic Architecture

I. D. INSN User Profiles & Responsibilities

Role Analyst System Administrator

CAS Operator

Skills Profile • Understanding of RPM detection and response operations• Understanding of site operations• Analytical skills (esp. quantitative)• MS Office experience (esp. Excel)

• Analytical skills (esp. quantitative)• MySQL server and database configuration experience• Networking knowledge and experience• IT systems maintenance• Working knowledge of English

• Understanding of RPM detection and response operations• Ability to save RID files and alarm protocols

Expectations • Check NDAC software daily for connection status, download of Daily Files• Run periodic analysis of files through automated screens and manual examination as needed.• Develop performance trend profiles• Request additional information from CAS according to SOPs• Reporting and notification to supervisors/maintenance technicians according to SOPs

• Maintain configuration of INSN• Add users and sites as needed• Perform data archiving and backup according to SOPs• Maintain network and database status of health• Respond to analyst request for technical support for software/network

• Operate RPMs and CAS software according to FLO training and SOPs •Respond to analyst requests for additional files and/or information• Request assistance from NDAC or ASC according to SOPs when needed for alarm resolution or maintenance support

Alarm Support Centre(ASC)

Working with ASC is similar to working with the NDAC client➲ Can display and analyze data received from NDAC ➲ User Files view and analysis received by NDAC➲ Generation and printing of general and events reports

II. Getting Started: A. Installation

➲ Before NDAC configuration it is necessary to have a list of all CAS with the following parameters:

Daily Files prefix assigned to the given CAS IP-address of CAS-server where INSN service is installed Access port number for INSN-service Phone number (in case if modem is required for connection

with CAS)

➲ Lists of all radiation monitors for each CAS with indication of: Daily Files prefix assigned to the given monitor Number of counting gamma and neutron channels with

indication of their location on pillars Daily Files format

Select “NDAC connection...”

NDAC connection setting

Enter IP-address and NDAC port number. Usually NDAC client and service are installed on one computer. In this case IP-address of the service is 127.0.0.1

II. Getting Started: B. Configuration

NDAC Configuration

Select “Database connection...”

Setting of NDAC database connection

Enter IP-address and NDAC database port number. Usually NDAC client and database are installed on one computer. In this case IP-address of the service is 127.0.0.1

Select “NDAC configuration...”

Filling the NDAC structure

Specify folders of Daily and User Files if you want to change default paths

Press the “Add group” button to create CAS group

NDAC Configuration

NDAC Configuration

Enter group name and prefix. Group prefix is a two letters country code. For example, MD.

Press the “Add CAS” button to add new CAS in the group

All CAS in the group have the same first prefixes (country prefix). Usually one group is enough.

Press the “Remove” button to delete a CAS group



NDAC Configuration


Mark the Box and enter CAS phone number if CAS uses modem connection

Press the “Add RPM” button to create new monitor for a given CAS

Enter name and CAS prefix and parameters of INSN connection

Press the “Remove” button to delete CAS


NDAC Configuration

Select Daily Files format for the given RPM

Enter number of gamma and neutron counting channels with indication of their location on pillars

Enter the RPM name and prefix

Press the “Remove” button to delete RPM

Press the “Apply” button to assign RPM parameters



NDAC Configuration

Select “User accounts...”

User’s account manager

There are two access levels in the program – Administrator and Operator

Press the “Add” button to add new user

NDAC Configuration


Enter login and access level

Enter user password

Press the “OK” button

System settings can be changed only by administrator, not by operator


NDAC Configuration


Use the “Edit” button if you want to change password or user’s access level

Use the “Lock” button if you want to temporally lock user’s access

Press the “OK” button to apply changes

Administrator only can edit user’s account list

Press the “Remove” button to delete user


➲ The NDAC software will connect to the CAS on startupConnection will be maintained as long as the network allowsThe NDAC software will look for new Daily Files on connectionOnly new Daily Files will be updated from the CASReceived data as stored in the database

➲ Each CAS is displayed as an icon with general informationName of the locationConnection statusDate of last successful download of Daily File Time of next Daily File update

II. Getting Started: C. Data Acquisition

CAS Connection States

ReadyThe last CAS connection was successful

ErrorThe last CAS connection was unsuccessful

BusyCAS data transfer in progress

UndefinedCurrent data on CAS connection state are out-of-date

II. Getting Started: C. Data Acquisition

Data Acquisition

Data acquisition from CAS

Right-click the mouse on the CAS icon in order to call a pop-up command menu

Check connection test of connection between NDAC and CAS

Synchronize Daily Filesrequest Daily Files update

Query User Files request User Files

Note: Daily Files are synchronized automatically, but can be synchronized manually

Data AcquisitionUser Files acquisition

Execute “Query User Files” command. If connection is established successfully and there are new User Files in the CAS, a list of files will appear

Mark files which you want to transfer

Press the “Transfer” button to start files transfer from CAS to NDAC

• User Files are manually created by the CAS user (RID files, alarm protocols, images, etc.• User Files must be manually requested by the NDAC• Files must be put in the INSN “User Files” folder by the CAS operator

Data analysis

User Files acquisitionWhen files are transferred from CAS they can be exported to the local computer using CAS details, User Files List view.

File download status

➲ The NDAC software will connect to the CAS on startupConnection will be maintained as long as the network allowsThe NDAC software will look for new Daily Files on connectionOnly new Daily Files will be updated from the CASReceived data as stored in the database

➲ Each CAS is displayed as an icon with general informationName of the locationConnection statusDate of last successful download of Daily File Time of next Daily File update

III. Analysis: A. Views

Select item with the same name in the Analysis menu of the

main window

Data Analysis

CAS details view

Right-click the mouse on the CAS icon to call a pop-up command menu

Select CAS details... item

… or

Data analysis

CAS details view• To see general overview and access for information, open the CAS details view

• The CAS current state view shows general information for each monitor connected to the CAS. The the Occupancy count, Alarms count, and name of the last transferred Daily File are displayed.

Pressing this icon generates a report which can be printed or saved in a PDF file

A pop-up list for selecting of the information type

This button brings up a window with detailed information about a given monitor

Data analysis

CAS details view

Select “Daily Files” list to view the list of Daily files received from the given CAS

A protocol is generated by pressing this icon

Marked files are saved in a user-specified folder by pressing the “Export to disk” button

Use this button for a window with detailed info of the RPM

Data analysis

RPM Statistics What can this view tell you? Trends of different events

Number of occupancies

Tampers

Power faults Excesses of expected

background limitsGamma alarms Neutron alarms

Gamma/Neutron alarms

At a GlanceWhat could this mean?

• Gamma/Neutron Alarm, Tamper Alarm.• Which do you want to follow up on?

Site ProfilingWhat could this mean?

• Relatively high number of alarms as percent of occupancies. • Does this site see a lot of NORM cargo? • Is this the typical volume of traffic for this site?• Does this site get a lot of tamper alarms? Any pattern to when they occur?

Data analysisSite Profiling (Continued)

Detailed information on a given monitor

Select the event type to view

Specify filter of events on date

Then press the “Apply” button

Data analysisCAS Data View

Detailed information on the monitor: Alarms

Channel count

Select the event

Press the “Show Alarm” button

left pillar right pillar

upper gamma

lower gamma

neutronUse mouse for zoom


Detailed information on the monitor: Alarms

Press the icon to generate a protocol – alarms list

Press the icon to generate a protocol on the specified alarm


Detailed information on the monitor: Occupancies

Channel count

Select the event

Press the “Show Occup.” button

left pillar right pillar

upper gamma

lower gamma

neutron


Detailed information on the monitor: Occupancies

Press the icon to generate a protocol for the given measurement


Detailed information on the monitor: Faults

Select type of the event

Press the “Show” button


Detailed information on the monitor: Background

Note: When specifying date interval, consider that background data sampling for the long interval requires some time

Data analysisGeneral Report

Select appropriate item in the “Analysis” menu

Enter date interval and press the “Generate” button

• Request spectra and alarm protocols to assess individual events and build site profiles

Data analysisUser Files Can Help

Marked files will be saved in a user-specified folder on pressing the “Export to disk” button

• Too many alarms. What could be the cause?

Data analysisIII. Analysis. B. Scenarios

Comparing detector profiles for clues

• Could be voltage spikes on one detector.

• Could be NORM in routine commerce

• Could be threshold reset too low

• Could be operational problems (background suppression, cross-talk)

• Too many alarms. What could be the cause?



• Could be NORM in routine commerce

• Could be threshold reset too low

• Could be operational problems (background suppression, cross-talk)

• Non-uniform alarm profile. What could be the cause?



• Could be distribution of the source in cargo

• Could be voltage spike

• Need to follow up on alarm resolution, compare with other alarms on that RPM to determine.

• Non-uniform alarm profile. What could be the cause?



• Could be distribution of the source in cargo

• Could be voltage spike

• Need to follow up on alarm resolution, compare with other alarms on that RPM to determine.

• Gaps in data. What could be the cause?


• Could be scheduled power outages.

• Could be routine loss of power due to infrastructure inadequacy.

• Could be one person turning off RPMs during her/his shift.

Gaps in data. What could be the cause?


• Could be: scheduled power outages.

• Routine loss of power due to infrastructure inadequacy.

• One person turning off RPMs during her/his shift.

• Routine maintenance

You may have advance warning of this pattern from the overview screen

Tamper alarms.


Possible causes:• Maintenance

activities• Intentional

tampering.• Loose

connection with the magnetic sensor.

• Look at timing of the activities to help determine.

• Obtain a copy of maintenance schedules and orders to verify.

IV. Standard Operating Procedures. A. Minimum Recommendations

➲ Check the Main View twice a day (beginning and end of shift)➲ Look for patterns in connectivity, confirm Daily File download➲ Run analysis of each CAS and its RPM for 1 week, 2 week, and

monthly intervals on a routine basis and develop operational profiles for each site and RPM.

➲ Follow up with CAS operators to investigate anomalies.➲ Determine who should receive reports on status of health of RPMs,

issues with operations, and observed anomalies in alarms, etc.➲ Determine communication hierarchy between NDAC and sites,

NDAC and ASC to ensure no duplication of efforts➲ Maintain a list of CAS operators, their schedules, and phone

numbers.➲ Ensure CAS operators know how to save User Files, and develop

request procedures (e.g., by phone, email).➲ Obtain copies of planned maintenance schedules.

Data backup and Archiving is recommended

Daily and User Files from the CAS are stored in the directories specified during system configuration. Default paths are:%ALLUSERSAPPDATA%\YaNDACServer\daily_files and

%ALLUSERSAPPDATA%\YaNDACServer\user_files, correspondingly.

It is recommended that these directories be copied to external storage (external HDD, USB flash, or other storage media) at least once per week.

IV. Standard Operating Procedures. B. Data backup

V. Conclusion: A. Exercises

• Exercises are intended for practice. There are no wrong answers, just opportunities for discovery.

A hypothetical Member State ABC has the following:

– 1 NDAC– 1 ASC– 7 CAS– 2-4 RPM per CAS

CASs are located at:– Airports– Dry ports– Seaports– Land borders

No. of CAS

Nature of Location

Location Abbreviation

Type of RPM installed

Abbreviation of installed RPM

Traffic volume at the location

02 Airport A1, A2 Pedestrian L001, L002, L003, L004

High

02 Dryport D1, D2 Vehicle L001, L002, L003, L004

Medium to High

02 Land border L1, L2 Vehicle + Pedestrian

L001, L002, L003, L004

Medium to High

01 Seaport S1 Vehicle + Pedestrian

L001, L002, L003, L004

Low to Medium

– CAS 7 is new and needs to be added. What do you do?– Which CAS data are you interested in monitoring and why?– How will you know that the connection between you and a

CAS has failed? What shall you do then?– Why it is important to know about missing data files?– How will you request the user files from CAS L2 for a

specific alarm at L002?– You want to share analysis of a Daily File or a User File of a

certain RPM with the ASC. What do you do?– Data received from a certain CAS deviates significantly from

its average value. What could be the reason? What do you do?

Exercise Tasks

V. Conclusion. B. Questions & Answers

Any questions?

Documents

Integrated Nuclear Security Network (INSN) Centralized Data Acquisition and Analysis System for Radiation Portal Monitors (RPM)