Database Software
for
Aviation and Industry


[ Home | Products & Services | Download Software | Purchase/Register Software | Customer Support | Feedback  ]


WinIST 2000
Performance Trending Software

On this page...


What is WinIST?

WinIST is a Pump and Valve Performance Trending computer software system developed to allow utility personnel to document and trend Inservice Testing (IST) activities of ASME Section XI. The program satisfies test data trending and documentation requirements of the NRC, and verifies the operational status of each pump or valve for power plant operation and safety. WinIST was designed specifically to relieve utility personnel of the necessity to manually maintain IST data as required by Subsections IWP and IWV of the ASME Boiler and Pressure Vessel Code, Section XI, "Rules for Inservice Testing of Nuclear Power Plant Components". The software effectively meets project requirements by providing computerized component testing accountability, test result data storage, component tracking and retrieval, report generation, plotted trends and updated ASME Code requirements.

WinIST is a fully interactive Windows application with easily accessible database functions for data entry, display, review, modifications, deletions, plotting and report generation. The program offers several predefined reports including the following:

  1. all pump and valve component system test requirements of ASME Section XI and component information,
  2. test data trends showing performance of all pump, valve and plant components over a specified period of time, and
  3. the current status of all components with unacceptable results.

Graphical pump reference curve plots, and IST trend plots that relate to associated trend reports can also be generated through the program.

WinIST is capable of recording and trending any number of user-defined parameters for each pump or valve component. Each trend parameter can be checked against four fixed or reference-based limits: "Upper Required Action", "Upper Alert", "Lower Alert" and "Lower Required Action". Following are some typical trend parameters which can easily be recorded and tracked by WinIST.

Pumps Valves
  • Flow rate
  • Differential pressure
  • Discharge pressure
  • Horizontal vibration amplitude
  • Vertical vibration amplitude
  • Horizontal vibration velocity
  • Vertical vibration velocity
  • Motor speed
  • Motor amperes
  • Inlet pressure (running, static)
  • Bearing temperature (upper,lower)
  • Full stroke exercise test to the open position
  • Full stroke exercise test to the closed position
  • Containment isolation valve leak test
  • Other leak tests
  • Partial stroke exercise test
  • Check valve exercise test to the open position
  • Check valve exercise test to the closed position
  • Other Pass/Fail exercise tests

How WinIST Organizes IST Data

Component Numbers
Each pump or valve being tracked by WinIST must be assigned a unique component number (pump number or valve number). This number is used throughout WinIST to identify the component, and serves as a relational link tying the various data files together.

Data Record Types
WinIST stores IST data in three types of data records: Component, Exam and Test History. The figure below illustrates the relationship between these records.

The figure below shows a typical pump component as it is displayed by WinIST. Pumps or valves must each have a single Component record. This record holds the assigned component number, and other descriptive information.

The grid on the left-hand side of the Trending page (see figure above) lists the Exam records assigned to the pump. Exam records are used to define the types of tests performed on a component, and to maintain the acceptance criteria and current status of these tests. A typical component will have several Exam records assigned (or linked) to it, one for each type of exam performed on that component. In this case, 8 Exam records have been assigned to the pump: 2 differential pressure (D PRSS and DP), a flow rate (FLOW), 4 vibration tests (INBD-H, INBD-V, OTBD-H and OT-BD-V), and a static pressure test (S PRSS). Clicking on an Exam in the grid displays details about that exam in the fields to the right of the grid. In the sample above, the differential pressure test (DP) has been selected. Detail fields are provided for the following:

To the right of the detail fields is a grid listing the Test History records which have been logged for this Exam. Test records are listed in reverse chronological order. As with the Exam grid, clicking on a test in the Test grid causes detailed information on that test to be displayed in the region at the bottom of the window. In the figure above, details about the DP (differential pressure) test performed on 6/6/1995 is displayed.

Test History records store the results of individual Inservice tests performed on plant components. Each time a particular type of Exam is performed on a component (and logged), a new Test History record is automatically created by WinIST and linked to the appropriate Exam record for that component. The Test History record stores the following:

Exam Codes

Exam Codes (e.g., "DP", "FLOW", etc. in the example above) are defined by the IST engineer to fit the particular characteristics and nomenclature of the plant. Exam Code definitions are stored in a separate data file along with default acceptance criteria settings. (The DP exam code definition shown has no default acceptance criteria settings.)

The default settings can streamline the initial setup of an IST database by automatically presetting the acceptance criteria fields in newly-created Exam records. Utilities are provided which automate the processes of assigning Exams to components and updating acceptance criteria settings in established Exam records. These utilities are initiated via the three buttons located at the bottom of the window.

How WinIST Processes Test Data

WinIST uses a procedure-based method for entry and logging of Inservice test information. Within the context of the software program, procedures are referred to as Surveillances. The Surveillances used for a particular plant or unit are defined and maintained by the IST engineer using WinIST's Surveillance Definition window, shown in the figure below.

A Surveillance consists of a unique identification number (Surveillance Number), a short one-line Name, an optional Revision number, a Description (memo field) and a set of Steps specifying the Components to be tested, and the Exams being performed on those components. Step are ordered by step number. The IST engineer can insert new steps or change the ordering of steps by manipulating step numbers.

Test Entry
Once defined, a Surveillance can be used to generate a Test Entry Sheet on the screen (see figure below) , allowing the IST engineer to quickly enter test results for processing by WinIST. The IST engineer records Inservice test results by modifying the columns in the form.

Test Results The measured test values are entered into the Test Results column, which accepts either numeric values or pass/fail for non-numeric exams.
Date This column is preset with the date entered by the IST engineer when the data sheet is created. However, the individual date associated with a step can be changed if necessary.
Ref (Reference) This column is used to indicate that the test value is from a reference or "baseline" test. When a "Y" is entered here, WinIST checks to see if "Baseline" referencing (see Exam Records) has been chosen for the component exam. If so, it establishes a new reference value equal to the entered test result. By definition, the status of a Reference test is always normal ("N").

Logging Test Results
Once completed and verified, Test Entry Sheets are "logged" into the WinIST database. The logging process does the following:

After logging is complete, WinIST generates a Log Status Report which indicates the tests being logged, the resulting component status settings, and the percentage change from the previously logged tests. The Log Status Report can be printed and/or displayed on the screen. The most recent Log Status Report is saved and can be viewed or printed as often as desired until the next logging session.

The figure below shows a typical Trend Plot produced by WinIST.

System Requirements

WinIST requires the following minimal system configuration in order to run efficiently. Stated requirements are for a stand alone installation. For network installations, the workstation must meet all of the stated requirements with the exception of the hard drive space which would be provided by the network server. Stated printer requirements can either be met by locally-attached or network accessible devices.

Support Services*

* Note: The support services described above are separately-contracted options, and are not included with the purchase of WinIST.

Download the Demo Version

The Demo version includes a sample IST database and, except for a 10 component limit, is fully functional. Download a copy and give it a try!


Information Request Form

Select the items that apply, and then let us know how to contact you.

Send product literature and pricing information
Have a salesperson contact me

Name (required)
Title
Company
Address
E-mail (required)
Phone

[ Home | Products & Services | Download Software | Purchase/Register Software | Customer Support | Feedback  ]

Send mail to support@polarisms.com with questions or comments about this web site.
Copyright © 2005 Polaris Microsystems, LLC
Last modified: October 5, 2005