API RBI v8.03.

03 Release Notes (revision 1) Page

1

Date: 04 June 2009 S/W Version: 8.03.5792

What’s New in API-RBI version 8.03.03

API-RBI 8.03.3 is a bug-release build to resolve high impact issues that have been detected with the 8.03.02
build.

Compatibility Concerns
Migration scripts are included in the set-up file to upgrade existing API-RBI databases (MySQL, SQL Server, and
Oracle) for use with 8.03.03. Once a database has been upgraded is no longer compatible with previous
versions of the software.

- NOTE – Database migration may take a substantial amount of time. The initial upgrade process may
take up to 15 minutes depending on database size. Please allow up to 5 additional minutes after the
software is “ready” for back-ground processes to complete. This is only necessary after the initial
migration only.

System Configuration
The documented system configuration is based on the development test environment. Deviation from the
documented system configuration is not recommended (i.e., Windows Vista, virtual server (i.e., Citrix)), and
users assume responsibility for any issue (i.e., performance, reliability) that is caused by non-standard
configurations.

System Requirements
Hardware Software

Client Workstation 1 GB RAM Windows 2000/XP OS

1GHz or better Java 1.6.0 (minimum)

80 MB Drive Available

Application Server 1 GB RAM Windows Server 2003 (minimum)

2GHz or better Java 1.6.0 (minimum)

500 MB Drive Available .Net Framework 2.0 (minimum)

Database Server Per database requirements

Stand-Alone PC 1.5 GB RAM Windows 2000/XP OS

2 GHz of better Java 1.6.0 (minimum)

 API RBI v8.03.03 Release Notes (revision 1) Page
2

Date: 04 June 2009 S/W Version: 8.03.5792

1 GB Drive or better .Net Framework 2.0 (minimum)

Supported Databases
MySQL V5.0 or newer

SQL Server 2000 or newer

Oracle 8i or newer

Upgrading from Pre-8.03.02

If upgrading from v8.03.02, disregard this section.

Licenses
The license format for this product is changed with version 8.03.02. Therefore, all sites, regardless of when
existing licenses are due to expire, must download a new license to successfully operate v8.03.02 and above.
This version will start with existing licenses; however, the user will be unable to perform calculations.

Remote Node Copy

Users may encounter problems with Remote Node copy unless the following actions are taken:

When the database to be copied includes PRVs, the user should first open the destination database and create
and delete a dummy PRV. This will allow the software to create the necessary PRV tables prior to the copy
operation.

MySQL Users
MySQL users should edit the my.ini file:

After the [mysqld] server section], add the following lines:

max_allowed_packet=4M

query_cache_limit=4M

Oracle Users
Oracle users should set the open_cursors to 3000.

Bug Fixes
Bugs and user requested enhancements are tracked via the SCARAB website at:
http://dt.equityeng.com/scarab/issues/.

The following bugs are fixed with API-RBI 8.03.03:

 API RBI v8.03.03 Release Notes (revision 1) Page
3

Date: 04 June 2009 S/W Version: 8.03.5792

SCARAB ID Summary
AR308 VOLFRACT_L and VOLFRACT_V
AR309 Vapor and Liquid Density

The following bugs/enhancement requests remain open in SCARAB with API-RBI 8.03.03:

SCARAB ID Summary
AR89 Polythionic tab is disable when the equipment has austenitic stainless steel clad

AR122 Re-define "risk categories" to match change to iso-risk approach

AR138 Plant wide report capability

AR153 Add Set Pressure to top of Overpressure Demand Cast Tab for the PRD Module

AR156 overpressure_potential field

AR174 PSV RBI Protected Components report enhancement

The fixed equipment report Design and Operating Conditions needs to include Flow Order Number
AR176 (from Component tab)

AR183 External Damage (CUI) is using thinning measured thickness in calculation

Bundle Module ? When viewing the inspection history, without making changes, the software makes
AR195 you verify if you want to leave without saving.

AR206 Units for CBA Optimal Bundle Replacement frequency needs to change from $/day to $/year

AR214 Bundle Moduel Weibull Plot - Add Component description

New consequence modeler does not adjust initial conditions of the release model for user defined %
AR220 liquid

AR221 Combine "operating conditions" with "volume and mass" screens.

Report Spreadsheets - Cannot "Browse" and save the export spreadsheet anywhere but to the C:
AR226 drive, also cannot rename the spreadsheet

AR234 Risk Mechanism report does not print out risk values at target date for any damage mechanism.

AR235 Inspection Plan Report - no Inspection Description and no Comments

 API RBI v8.03.03 Release Notes (revision 1) Page
4

Date: 04 June 2009 S/W Version: 8.03.5792

AR236 Filtering limited to = only for some fields

AR238 HCN Risk Target value versus termperature

AR239 ADD HCN SCC MODEL TO SOFTWARE

AR241 Reporter role allows import

AR243 Add fields to import export and filter

AR244 Component Setting - Cracking inspection date is a mandatory field

AR250 PRD "Protected Components" should not list heat exchanger bundles, i.e. comptype=HEXTUBE

AR251 Reports - Incorrect TB side design pressure

AR252 Reports - Incorrect measured thickness reported

AR253 Specialist Role inconsistency

AR254 Adding a coating increases DF for equipment susceptible to external SCC.

AR256 J-Tree Color Coding For Tanks on Start-Up Incorrect

AR257 Oracle Difference (upgrade) Scrip Invalid

AR262 When applying global settings, GUI should give message to let user know what is going on

AR268 Speed issues with version 8.03 Stand alone

AR269 Equipment type changing when linke to protected equipment for PRV

AR270 Equipment type changing when adding bundles

AR271 Import data not being recognized by software

following AR 271 issues. Data for internal thinning, external thinning would not export through
AR272 export template.

AR273 T-min calculation error in API 653 tank module

For torispherical heads, a bug occurs when the corroded thickness gets below .5% of the crown
AR275 radius the calculator crashes

AR277 GUI issues with management factor

 API RBI v8.03.03 Release Notes (revision 1) Page
5

Date: 04 June 2009 S/W Version: 8.03.5792

Tank Module - Volumes for component and roll-up to equipment volumes are not being caclualted
AR280 properly, also volume validation check has a bug in it

Liquid Fill Height in Tank Module needs to be moved from the component level to the equipment
AR281 level

AR283 Translator for 3.3.3 files does not appear to work

AR285 No credit for multiple inspections for thinning and external

AR286 Filtering not working for some attributes particularly inventory groups. All data available on tree.

AR290 Import / Export spreadsheet error 1

AR291 Import / Export spreadsheet error 2

AR292 event tree error

AR293 consequence event tree error

AR295 Corroison Cost multilier is mislabeled on Component screen

AR296 Level 2 consequence modeler keys off of the word steam in the fluid name.

AR299 Error in the calculation of total mass in the new consecuence model

AR301 Tank Module - Corrosion rate calculation error

AR304 Most Role Permissions limited to single Plant

AR305 0F error with Level 2 consequence modeler

AR307 PTA Cracking - Error in the calculation of the L/H grades of 300 series SS

API-RBI v7 (xxx), v8 (xxx), 8.01 (8.01.0000, 8.01.0001, 8.01.0002), and 8.02

(8.02.0000, 8.02.0001, 8.02.0002) no Longer Supported
“No longer supported” means that users should not submit defect reports on anomalies found in unsupported
builds and that all defect resolutions will only be implemented in the current baseline. The Help Desk will
continue to assist users with these builds.
 API RBI v8.03.03 Release Notes (revision 1) Page
6

Date: 04 June 2009 S/W Version: 8.03.5792

API-RBI v9.0
Version 9.0, tentatively scheduled for release in fall of 2009, supersedes all previous releases of API-RBI and will
become the new API-RBI baseline. Version 9.0 utilizes a new architecture which leverages the Microsoft .NET
platform for extensibility and maintainability.