Mechanical Engineering News For the Power, Petrochemical and Related Industries ‘The COADE Mechanical Engineering News Bulletin is published periodically from the COADE offices in Houston, Texas. The Bulletin is intended to provide information about software applications and development for Mechanical Engineers serving the power, petrochemical, and related industries. Additionally, the Bulletin will serve asthe official notification vehicle for software errors discov~ cred in those Mechanical Engineering programs offered by COADE. (Please note, this bulletin is published only two to three times per year.) Table Of Contents PC Hardware for the Engineering User (Part 20), What's New at COADE Pipelines & Terminals Conference Compuserve ACCESS CAESAR II Version 3.22 A Preview of the New Vessel Program. ‘Technology You Can Use ‘Common Network Questions & Answers. Impact of API-650 Addendum... Applying APIL6S3 : Did You Know that CAESAR II Could .. Seismic Analysis of Tall Vertical ProcessTowers . ‘Commonly Asked CAESAR II Questions. Program Specifications CAESAR II Specifications... ‘TANK Specifications... CodeCale Specifications .. Announcements FEVPipe Version 28 so. CATIA Partnership. COADE, Inc Volume 20 Pyrat) PC Hardware & Systems for the Engineering User (Part 20) ‘The Pentium Problem ‘The news broke over the Thanksgiving Holiday, a Maw (error) had been found in Intel's Pentium chip. The ‘November 24 edition of The New York Times indicated that Intel had known about the problem sinee June, and that the problem was corrected then. However, by mid-December, no supplier that we know of had corrected chips. On. December 13, IBM halted shipment of their Pentium machines. Inthe December Idedition of The Houston Post, aan Intel spokesman stated that “.. the average chip goes through seven redesigns to correct esoteric flaws". In late December, Intel finally decided to become responsible and place the chips. However, as of mid-January, no new chips were available. Finally, in late January, PC Magazine and Dr. Dobbs Jounal diseussed the problem and its potential effects from neutral point of view. How do these events affect Pentium "users, and specifically, usersof COADE software products? CADCENTRE announes between PDMS and CA ARI ‘The interface, run from within PDMS directional For additional TRE. generates a complete, CAESAR II neutral file details, please contact CADCE! Cambridge, England. Firs. the pew hipmusthe understood Ielhas writtenathiny-one page documentttled"Statistcal Analysis of Floating Point Flaw in dhe Pentium Processor” This paper describes how the error occurred, the tests and analysis Intel has perfumed, characteristics ofthe error, and specifically which CPU instructions ae affected bythe error. The conclusion is that thee ate five binary bit patterns of advisor which can cause the erorin the dividerCOADE Mechanical Engineering News. April, 1995 hardware. Furthermore, the divider hardware is used for: {floating point division, floating point remainder, and loating point transcendental functions (sin, cos, tan). When the terror occurs, the result is inaccurate inthe fourth sign decimal digit. ‘This paper then goes on to describe the statistical analysis performed on the problem, by Intel, which led to the following Intel conclusion regarding engineering/scientific use of the Pentium. “Technical users running other applications requiring unusual precision and employing millions of divides per day should employ either an updated Pentium processor without the flaw or a software work TBM on the other hand, concluded that even with the statistical analysis, an average spreadsheet user could encounter the problem. around. (Note that this description of the errors more ominous than ‘most newspaper reports state, Most media coverage refers tothe problemas “only affectingrare, complex mathematical algorithms”, This isa great disservice to the general public « division is not a rare, complex operation!) ‘The article from The New York Times contained an example ‘equation which will reveal the error on the Pentium: A-(AIB)*B=0 ‘or the result is supposed to be zero! Using a value for A of 4,195,825.0 and a value for B of 3,145,727.0 produces a resultof 256 ona Pentium. Similarly, values of 5,505,001.0 and 204,011 0 yield 192. Are these errors significant? Ifthe error occurs during a stress calculation, probably not. However, what if the error occurs during the first division of matrix decomposition? Then the error propagates throngh out the entire solution -- who knows what results will be produced! COADE Research Services, developer of FE/Pipe, has formally changed its name to Paulin Research Group. Anyone interested in finite element analysis of piping components.can contact Paulin Research Group Phone: 713-251-8084 Fax: 713-251-1830 BBS: 713-251-4092 ‘To reveal whether or not COADE’s Pentium machine had the flaw, a small FORTRAN program was written using the above test equation. When compiled with the Microsoft FORTRAN compiler, the Pentium produced a result of 256. ‘The same program running on 486 and 386 processors produced a result of 0. Next, the same program was ‘compiledusing the WATCOM FORTRAN compiler. Again the Pentium produced a result of 956. Surprisingly, the 486 and 386 machines also produced the incorrect result of 256. A study of the assembly language code produce by the ‘compiler revealed that the WATCOM compiler performs “constant folding”, i.e. it recognized the equation as a ‘constant, the compiler then performed the math, and stuffed the result in the program. This is a plus for WATCOM in. the “speed of execution” category. However, due to the Pentium error, this program will now generate the wrong. ‘answer on any machine it is run on! Did any of these statistical analysis consider this possibility? This discovery ‘means that not only do users need to be wary of Pentium produced results, but software developers now nced to question the quality of the software generated on Pentium machines! ‘Some readers may recall thatin the last issue of Mechanical Engineering News, we noted that our software had been tested succesfully on the Pentium. The tests consisted of rerunning our standard series of QA jobs. None of these Jjobs exhibited the divider unit flaw discussed here. What should Pentium users of COADE software products do? COADE has had its Pentium chip replaced by Intel. No additional Pentiums will be purchased by COADE unless they are assured tobe flaw-free, sono distributed programs “will be compiled on machines with a flawed Pentium CPU. Inaddition, the COADE system check program, SYSCHK, hhas been modified to detect the Pentium and test for the divider unit error. ‘This new version of SYSCHK can be down loaded from the “Mizeellancous" file area of our BBS, and CompuServe. Our recommendation to users is that they contact Intel and obtain corrected Pentium chips. With the new (corrected) Pentium chip, testing has yielded expected (correct) results on a variety of QA jobs. Additionally, the division error has been corrected. In late February, Intel announced plans to publicly document and disclose flaws in ite processors, through addenda to design handbooks.COADE Mechanical Engineering News April, 1995 Pipelines & Terminals Conference During the first week of February 95, COADE exhibited its ‘ANK program (along with othersofiware) atthe Pipelines, Terminals, & Storage Conference in Houston, Texas. This conference/show received over 10,000 attendees, reviewing the products of over 650 exhibitors COADE also exhibited at the Petro-Expo Conference in Houston in late Mareh, CompuServe Access COADE, Inc. hasarranged o be one of the vendors supported through CompuServe’s CADICAMICAE forum, Weintend to use this forum to more quickly and efficiently provide our users with program revisions and product news, CompuServe is a worldwide computer network providing members with online access to a wide varity UF services Users of COADE products, can benefit from a CompuServe ‘membership through the rapid acquisition of data files and Program revisions. Additionally, E-mail can be sent direetly 1 COADE, In most cases this can be done duu telephone call, unlike the long distance call to our Bulletin Board Service. Thereare other benefits of CompuServe membership, support forums fora wide variety of software and hardware vendors, forums for mail and news, travel service forums, and forums for hobbies and reference, Using the message areas ofthese forums you ean keep abreast of developments at IBM, Novell, Microsott, and Intel. To access the COADE section of CompuServe, issue the "GO CADDVEN” command at any “!” prompt. Select Section #1, forthe general CAD/CAMICAE vendors, From this area, you can leave mail, upload or download files. (These processes are casi utilize one of the CompuServe Information Managers, either DOSCIM or WINCIM,) Public messages may be posted by addressing them (from within the forum) to COADE, private messizes ‘may be sent to COADE at CompuServe adress 73073.362. if you ‘To join CompuServe, you should contact CompuServe directly fone month of unlimited ac connect charges, a free subscription to the monthly CompuServe Magazine, and a $15 credit for extended and premium services, With the introductory sembership, you receive ess 10 basic servives free of CAESAR II Version 3.22 Version 3.22 of CAESAR Is in “beta rest” and is nearing completion. This release includes many chai It Of user suggestions, and several important technical additions. Listed below are the most important changes and enhancements included in CAESAR HI Version 3.22. + The Harmonic solver has been updated to provide “damping”. Harmonie analysis can now include or exclude damping as the user deems necessary + Cemter of Gravity calculations have been added, with results displayed in the error checker + ABillof M als report has been added, + The following codes have been reviewed (and any necessary changes made) for compliance to the latest editions: B31.3, B31.4, B31.5, B31.8, NC, and ND. + The following additional piping codeshave been added: RCCM-D, + Yield eriterion stresses can be computed as either Von Mises or as 3D Maximum Shear Stress intensity *+ Hoop Stress can be computed based on Outer Diameter Inner Diameter, Mean Diamete or Lame’s equation: + Thespring hangerdesign spreadsheethasbeen modified {0 default to a 25% load variation, In addition, the ‘aciual hanger load variation now appears in the hanger ‘output reports. + A new command (WIND) has been added 10 the stuuctural steel preprocessor. This allows selective wind loading on an element by element bass,COADE Mechanic | Engineering News April, 1995, ‘= A new key-combination (AI-D) is available in the input processor to compute the distance between Ow0 nodes. + User specified absolute coordinates for up to 30 nodes are saved in the input file + The 191 60 nput ttle paye bray been expanded fi ‘+ Automatic node numbering abilities have been added tw the spreadsheets of the main piping input module + Expausion Joint data bases from IWK (Geumany) ate provided. ‘+ Expansion Joint data base from Senior Flexonics provided. A Preview of the New Vessel Program By DavidDihl ‘This article is an introduction to our new Pressure Vessel Design/Analysis program. ‘This article will be of special interest to vessel engineers and designers who have expenence with CUADE’s PROVESSEL program. By reviewing these notes, the PROVESSEL user will quickly earn about our New Vessel Program (NVP), and its advantages overrRoVESSEL. (This article will referto this program as NVP, since the name has not been decided at this time.) With the initial release of NVP, COADE will no longer 1ssue updates to PROVESSEL. CUADE will continue to support PaOVESSEL users. pRoVESSEL users who are currently on the “Support, Maintenance, and Update” plan will receive NVP as their PROVESSEL update. Users will Continue to receive NV updates throughout the period of their maintenance plan. PROVESSEL users who are not currently on the “Support, Maintenance, and Update” plan ‘may rejoin the program (to receive NVP) by paying the standard lapsed update fee for PROVESSEL. ‘Most pROVESSEL users would find no reason to switch to ‘a new package; the program is a reliable tool. However, COADE has recognized several characteristics of the package which have preventedit from growing nd receiving ‘a wider acceptance in the engineering community. Some of these limiting characteristics involved internal data structures, analysis assumptions, and input data organization, In order to resolve these issues, COADE decided to start ‘with a"clean sheet of paper”, and developacompletely new program, which will in the long run, produce a better product. The NVP package will combine many of the ‘comments and suggestions from our user community with new development tools and interface technology. Program Input ‘One of the most noticeable differences beween pROVESSEL and NVPis the input processor, NVP uses an event driven Graphical User Interface, a GUL While reoVESSEL ‘operates in text mode for data specification, NVP operates graphics mode. This allows te vessel geometry 00 be viewed simultaneously with the input specification. The vessel model is now displayed as i is created. This combination of input data and graphics presents more information othe user, and aidsin both model specification ‘and verification, Upon starting NVP, the user is placed immediately in the input of the current vessel job. Vertical vessels, horizontal vessels, nozzles, and flanges are no longer segregated in ‘multiple job files - they can all be specified whenever necessary. Through the use of pull down menus, the user ccan control the input specification, the analysis of the ‘vessel, and the utility functions of the package. The vessel description can be specified in two modes. The “Build Mode” allows users to graphically build the vessel by assembling components from a tool bar shown on the screen. In the “Define Mode”, the specific data for each ‘vessel component can be defined. As the details of each ‘component (nozzles, rings, lugs, etc.) are specified, the graphics display of the vessel is simultaneously updated as necessary.COADE Mechanical Engineering News April, 1995 Vessel Analysis ‘The heart of NVP is the analysis engine, the number cruncher. This module is a completely new program, developed to allow the package to address more complex. vessels and loading combinations, Users can now consider vertical vessels supported on legs, lugs, rings, or skirts at any clevation, The effects of these various suppart types are reflected in the deadweight, wind, earthquake, and buckling calculations. In the load specification category, NVP includes ‘considerations for the latest editions of ASCE #7, the Uniform Building Code (UBC), and the National Building Code (NBC) of Canada. Users also have a great deal of flexibility in defining exactly what loads are considered in ‘what load case. For example, itis now possible to check wind loads on an empty vessel, or an earthquake during a hydrotest, all ina single execution, with results ina single output report. ‘The analysis of the vessel details (flanges, rings, nozzles, tc.) willrely on the computation engines of another COADE, vessel program, CodeCale The initial specification of these items is used by NVP for weight contributions. The ‘actual analysie and compliance ofthese detailed components is carried out in the CodeCale engines. The CodeCale ‘output is automatically appended to the overall NVP vessel ‘output reports. During the actual vessel analysis, NVP places control in the hands of the user As with prnVESSEL. NVP allows the "user to specify how various design decisions should be made atthe inpot level Roth programs can he set to 1)no change. straight rerate mode, or 2) automatic adjustment, design mode. With NVP, there i a third option, allow user intervention, interactive mode. During the analysis, intermediate results are displayed to the user, who may eractively alter the analysis path. This intermediate display and possible interactive control takes many of the {questions out of the design path chosen by the program, and places the design hack in the hands of the user. Program Output "The NVP package utilizes the same robust output processor as does COADE’s CodeCale program, Reports are available for each step of the analysis (input echo. error checking, load specification), as well as the results of each load case. Users simply select a topic and its destination (screen, printer, or file) to obtain a concise report of the requested item. Availability ‘The NVP package is reaching the end af the development cycle for Version 1.0. The “beta test” release is expected in late April, with the official release of Version 10 anticipated in late June. COADE has always respected the opinions of the user ‘community to suggest and guide program development ‘This is especially true of a new product. We therefore ‘encourage all users of NVP ta contact COADE and discuss any problems, comments, or suggestions as necessary Common Network Questions & Answers By Richard Ay ‘This article discusses the common questions and associated answers pertaining to COADEsoftware running on Network installations. 1) What COADE products support the “network” ESL? As of summer 1994, all COADE products support the network ESL. Details of the specific ESLs supported are described in point #3 below, 2) Where is the software loaded? ‘The program executables can be loaded (installed) on either the local workstation or on the network file This is strictly a matter of user preference. However, by installing the software on the network file server, it ean be accessed from any workstation. ‘Additionally, user disk space is saved since only one copy resides on the server, not one copy on each ‘workstation,COADE Mechanical Engineering News April, 1995 Fromaperformance pointof view, the software will run slightly faster if installed on a local workstation. This {is because the transmission of the .EXE files over the network (to the workstation's memory) is avoided, 3) How is the External Software Lock (ESL) utilized in a network environment? Asof Summer 1994, COADE software products support three different ESLs. These devices and their operation are described below. a) A“local” (green) ESL from Software Security Inc. This is the device COADE has been using since 1990. This ESL must be attached to the parallel port of the workstation, regardless of where the software is loaded. b) A “local” (white) ESL from Aladdin Software Security Ine. This device i new for COADE software in 1994 and is an alternative to solve access problems (i.e. hardware compatibility problems) some users experience withthe (green) ESL from Software Security. As before, the local ESL must be attached to the parallel port ofthe workstation, regardless of where the software is loaded. ©) A “network” (red) ESL from Aladdin Software Security Inc. This device is new for COADE software in 1994 and is intended to provide access for multiple users/programs over the network. Only one such ESL is needed. In order for the “network” ESL to function properly, a small management program must be run wherever the ESL is attached (to either the file server or the workstation). Once this manager program is running, users across the network can access the software, regardless of whore the software is loaded. Instructions for installing the “network” BSL ean be found in the program documentation, 4) Can a “local” ESL be used as a “network” ESL? NO! Attaching a “local” ESL to the file server will not allow access tothe software. In all probability, it will crash the network. 5) Can the “network” ESL be used on a local machine (in cease the network crashes)? 9 n 9) 10) No, the “network” ESL will not allow access to the software unless the mazayement program is running on the network. ‘Can additional licenses be added tothe “network” ESL ‘once itis at a customes’s site, No, at the present time there is ny software which allows a remote update of the number of licenses allowed by a “network” ESL. Additional licenses can bbe acquired by exchanging the current ESL for one ‘with the new required seat Can the software be moved/copied fiom the file server to a workstation or notebook computer? ‘Yes, the software canbe moved freely between machines. ‘There are no machine specific restr requirements built into the software, ‘Can the “network” version be run ona “local” machine? ‘There is no “network” specific version. All software products search forall three [SLsinthe order presented in point #3 above. Can a network installation support both a “network” ESL and “local” ESLs. ‘Yes, the software searches forall three ESL types. This ESL search is independent of where the software actually resides. The scarch concludes when the fst ESLis found. Ifa“local” ESLis found, the search stops and no licenses are locked on the “network” ESL. Ifo “local” ESL is found, the “network” ESL is located and the availability of licenses checked. available, itis locked and access to the software is allowed. Ifno licenses are available, the uset receives ‘an error message and access to the software is denied. If a license is How should a site allocate “network” and “local” ESLs? COADE recommends that only 70 to 80 percent of Ue licenses be assigned to the “network” ESL. This will provide several “local” ESLs which can be attached workstations atthe site. This provides added flexibility in that these “local” ESLs can then be used for uff site access, ie. when traveling, ‘One draw back to the “network” ESL is that the network must be up and running, and you have to have access to the network in order to use the software.COADE Mechanical Engineering News April, 4 11) Can multiple ESLs be attached to the same parallel port? Yes, as long as they are for different programs. The software stops searching for the ESL as soon as one is recognized. This is nota problem for “local” ESLs, but could be a problem on anetwork. Youcan not have two ‘COADE network (red) ESL on the same network - the software will never find the second de 12) Whatnetworks and what operating systems re supported by the Network ESL? ‘The network ESL from Aladdin Software Security has been used with COADE software on Novell, Pathworks, and Banyon networks. Operating systems include DOS, Windows, and Windows/NT. 13) Doesasite with multiple COADE products need multiple network ESLs? ‘No- in fact, as point #11 stated, multiple ESLs with the ‘same ID code can not reside on the same network. The COADENetwork ESL hasbeen etup tosupport multiple products, each with a specified number of licenses. Only one “network” ESL per network is required (possible). Impact of API-650 Addendum 1 By Ricard ay In December 1994, API issued Addendum 1 to the ninth dition of the API-G50 standard. While a number of pages ‘ode were revised by Addendum 1, there are only two ‘changes which affect design or analysis computations (and therefore users of COADE’s TANK program). ‘The first change of interest concerns the API materials listed in Table3-2, and their groups listed in Table 2-3. Addendum 1 has removed materials FE 42, FE 44, and FE 52 from these tables. In place of these materials, API has added IT 430 and FE 510, ‘The second item of imterest is a change in the scope of Appendix P, for nozzle flexibilities and limiting loads ‘Addendum I has added a phrase, limiting the applicability ‘of this appendix. “As paragraph P.1 now reads, the use of Appendix Pis recommended only fr tanks in excess of 120, feet (36.6 meters) in diameter How will these Addendum 1 changes affect TANK? The ‘material database willbe revised toreflect the new materials, and remove the old FE materials. This new data base willl bbe available for download from the COADE BBS as well as, ‘CompuServe. In addition, an “International” version of this data base will also be included. This “International” version will include several materials commonly used outside of the U.S. The revised API material data base will be designated A650_94.MAT, and the “International” data base will be designated A6S0_94.MAT. Both material databases wll becontained inthe download file U120_C.ZIP. To utilize either of these new material data base files, place the ZIP file in the TANK program directory. Extract the data base files using PKUNZIP. Then, use the TANK ‘configuration option to select the desired data base from the necessary data directories. ‘The new scope limitation of Appendix P will appear as a waming message in the next version of TANK. This ‘modification to the software will simply wam the user if nozzles are specified on atank with a diameter less than 120 feet (36.6 meters). This will not prevent the program from, running or applying the rules and equations of Appendix P. Applying API-653 By Vincent Carve The following article has heen submitted for publication hy Vincent Carucci, Vice President of Carmagen Engineering, Inc, 7 Waverly Place, Madison, NI 07940. API-653 and Tank Shell Thickness Assessment The primary focus of this article is to discuss API-093 requirements for the shell thickness of atmospheric storage tanks. It will begin by first briefly summarizing the background and scope of API-653 to establish a foundation ‘for what will follow. It will then generally describe tank inspection requirements and then focus on the shell. The article assumes that the readers are generally familiar with both API-650 and API-653, Background One catastrophic britle fracture of a storage tank that ‘occurred in 1988 spilled approximately 750,000 gallons of diesel fuel into adjacent storm sewers that then emptied into nearby river. The owner of the tank spent several million dollars in cleanup costs and fines because of this one Incident. This failure, along with two other spills that occurred within about a year ofthis one, focused a great deal of attention on the condition of existing storage tanks and the potential consequences of a failure. One result of this attention was the publication of API-653 in January 1991 ‘API-653 addresses the condition of existing, aboveground, atmospheric pressure storage tanks that were originally 7COADE Mechanical Engineering Nows April, 1995, ‘designed using API-650 orits predecessor, API-I2C. API- {653 presents requirements that are intended to prevent tank failure due to brittle fracture. However, API-653 requirements go beyond those that are neceseary to prevent a brittle fracture. API-653 requires that existing tanks be periodically inspected to ensure that they are structurally sound, within the required allowable stresses, and will not Teak before the next opportunity for inspection. Ensuring that a tank will not leak before the next inspection is more than just ensuring that it will nt fail catastrophically. Even 1 small leak is unacceptable. Inspection and Engineering Evaluation ‘An API-653 inspection program addresses four main components of the tank: the roof, shell, bottom. and foundation. These are the tank components that directly affect the structural integrity and liquid storage capability of the tank. API-653 does not specify the exact inspection procedures that must be followed nor the quantity of data that must be collected. It only specifies what must be inspected and the acceptance criteria. API-653 goes beyond ‘merely requiring thatthe main tank components be inspected, It requires that an engineering evaluation be made of the inspection data to ensure that the structural condition of the tank meets specified acceptance criteria. This engineering evaluation must go beyond confirming that the tank is structurally sound at the time of inspection: it must confirm that the tank will remain structurally sound during the ‘entire next period of operation, For example, assume that portions of the tank shell have thinned due to corrosion. You must assume that the corrosion will continue as the tank remains in operation. An ‘API-653 evaluation of the shell thickness requires confirmation that the shel! will not thin to an unacceptable level before itis inspected again. Therefore, evaluation of the shell thickness inspection data must confirm that each Portion of the shell has sufficient corrosion allowance remaining for the entire next period of operation, Shell Inspection ‘The tank shell must be visually examined for obvious flaws (eg. weld defects) and other forms of deterioration (e.g., plate distortion or corrosion). The most common form of deterioration that must be addressed is corrosion, and shell wall thickness measurements must be made to evaluate the remaining thickness of the shell. While corrosion may be uniform over large areas of the shell, the shell is normally not uniformly corroded in its entirety. Large areas of the shell may not have corroded at all, whereas other areas may have experienced significant corrosion. For example: ‘+ The portion of the shell that corresponds to the normal ‘operating liquid level! may corrode more than the rest of the shell due to the liquid/vapor interface. + Sludge and wax deposits may accumulate atthe tank bottom near the shell and cause more corrosion in the lower portion of the bottom course than elsewhere. A large amount of corrosion in this area, but on the outside, may also be caused by rainwater accumulation due to poor tank pit drainage. + One side of the tank may corrode more than the est due to the prevailing wind direction. ‘Therefore, evaluation of tank shell integrity must consider the required shell thicknesses (which vary with clevation on the shell) and the actual thicknesses measured. The actual measured thicknesses will vary by tank course, and may vary by position around the tank circumference, by elevation within the course, or even by specific location within a ‘given tank plate. Shell Integrity Evaluation AAPI-653 provides procedures for calculating the minimum. required shell course thicknesses and acecptance criteria for both uniformly corroded and pitted areas of the shell article focuses only on uniformly corroded arcas. ‘The minimum required shell plate thickness will normally becalculated using the following equation (Ref. Para. 2.3.3 ‘of API-653), as long as the tank ie no larger than 200 ft. in diameter: 6D(H - 1)G SE = Minimum acceptable thickness, in. Cannotbe less than 0.1 in. for any shell course. D = Nominal tank diameter. ft H_— = Height from the bottom of the most severely corroded area in each shell course to the maximum design liquid level. ft. G = The highest specific gravity of the tank contents, including water if the tank may be hydrotested in the futureCOADE Mechanical Enginecring News. April, 1995 S = Maximum allowable stress, psi. The smaller of O.80Y oF 0.426T for the bottom or second courses. or the smaller of 0.88Y or 0.472T for all other “Y" is the specified minimum yield strength of the plate or 30,000 psi if the plate material is unknown, “Tis the smaller ofthe specified minimum tensile strength of the plate or 80,000 psi, or $5,000 psi if the plate material is unknown. E = The original weld joint efficiency used in the tank design, Use E = 0.7 ifthe original B is unknown, E= 1.0ifa corroded area that is being evaluated is, far enough away from the welds, with the distance as defined by API-653. This. is obviously a very simple equation, but this can deceive you into thinking that a complete shell evaluation is simpler than it really is. We will now look at some things tobe eareful of, + As previously mentioned, this equation can only be used if the tank diameter is no greater than 200 ft. That is because this equation is based on the One-Foot shell thickness calculation method of API-650. For larger diameter tanks, the evaluation must be made using the variable design point method of API-650. This is a more complicated, iterative calculation procedure (but use of COADE's TANK program makes it simple). Note that the Variable Design Point Method may be used for smaller diameter tanks if desired. + The evaluation must be made for every shell course, ‘+ “HT is measured from the bottom of the most severely corroded area in each shell course, not necessarily from the bottom of the course. However, when inspection data are provided for evaluation, you often just get the ‘minimum thickness ora range of thicknesses measured in each course with no indication of the elevations within the course where the measurements were made. Therefore, without additional information, the evaluation must be made using the conservative assumption that the corrosion is at the bottom of the course in question. + “G" must consider both the specific gravity ofthe stored liquid and whether the tank will be hydrotested in the future. Hydrotesting is required if major repairs or alterations are needed. However to maxis permitted fill height ofthe stored liquid, calculating the ize the ‘minimum required thickness for both the stored liquid and water is acceptable. Then an acceptable fill height for each liquid can be back-calculated based on the measured thicknesses, aries with shell course and isthe same for both the stored liquid case and the hydrotest case. In these respects, it differs from API650. API-650 uses the same material allowable stress regardless ofthe course that is heing checked, and it uses a higher allowable stress forthe hydrotest case. The valuesof the allowable stresses also differ from those that are in API-650 for the same material specifications. Note also that API-653 permits a shell integrity evaluation even if the shell material specification is unknown, with the assumption that the shell material js low in strength (ie.. Y = 30,000 psi and T = 55.000 ‘This can bea large penalty ifthe shell was actually fabricated using higher strength steel Putting this in perspective. a tank may have been designed and constructed five years ago using A-516 Grade 70 plate for the shell (Y = 38.000 psi and 1 70,000 psi). However, if all the tank records are lost ‘and the materials cannot be confirmed. the tank cannot be filled to its original design fill height even if no corrosion at all has occurred (assuming that no excess thickness was provided in the original design). If ‘nothing else this emphasizes the importance of record- keeping. ““E" must be assumed to be 0.7 if the “E” used in the original design is unknown. Here again. this can be an ‘extreme penalty to pay ifthe actual joint efficiency was, ‘much higher than this. The reason for this low value is that even as late as 1970, tanks may have been designed with tislow weld jointefficiency (depending fon the shell weld detail and inspection specified). Note that “E” can be assumed to be equal to 1.0 (i.c..do not worry about the welds) if you are evaluating a corroded area that is far enough away from the welds. Unfortunately. the initial inspection data that you receive may not show how close the corroded area is to the welds. ‘Calculating the minimum required thickness for each shel couse (and in coroded regions) i really ameans to an end, The information that you really want isthe following:COADE Mechanical Engineering News April, 1995, + How much corrosion allowance do I have left at the relevant elevations in the shell? ‘+ How long can the tank stay in operation based on the available corrosion allowances? + What are the maximum permitted tank fill heights forboth the stored liquidand forany future hydrotest? Note that future corrosionallowance must be considered even for the hydrotest case when doing an API-653 evaluation, which differs from an API-650 design evaluation. APL650isadesign standard, which assumes. thatthe tank is hydrotested right after it has been built and the plates are al at their new thicknesses, and does not consider future hydrotests. API-653 addresses the actual condition of existing tanks (1e., considers deterioration). The API-653 evaluation must consider all loads that can be applied (i.e., must consider future hydrotests). Shell Evaluation Example We'll now put all these words to a practical test using the "TANK Program. Assume that a shell thickness inspection hhas just been done of the external floating roof, erude oil storage tank shown in Figure 1. This tank was built 10 years ‘ago, but all the design and fabrication records have been Jost. From the thickness measurements made, only one area ‘of corrosion was found in the bottom shell course, and this corrosion extends for a maximum vertical distance of 40 in, ‘The minimum thickness reported in this corroded urea was 1.125 in. No corrosion was noted elsewhere inthe shell, and ‘the original nominal course thicknesses are as shown in the figure ( based on the thickness measurements made), The ‘design fill height for the tank is 56 fl, and the specific gravity ofthe crude oil is 0.8. Itis your job to decide if the tank can remain in service at the desired design fill height. [ eee E abel pee seen eese e Figure 1 Example Problem Several things are going against you in this problem. 1. The shell material is unknown: therefore, you must use the API-653 default material yield andtensilestrengths. 2. Since there are no original records, you do not know for sure what shell weld inspection was done or the weld joint efficiency used in the design. Therefore, API-653 forces you to use E = 017. 3. The inspection data only gave the minimum thickness ‘measured and did not say exactly what elevation inthe botlom course the minimum thickness was at ‘Therefore, you must assume that the entire corroded area is at the bottom of the course and that itis all 1.125 in. thick. Figure 2 shows the initial input data used for this problem, and Figure 3 shows the portion ofthe output that is relevant for our purposes. Sceign nettod Cv, 8.2 8) o (ianiable. ona fae, scdorerste AD Ron obeertie (onsean: . ‘ibfea.in) —“ooaoe She gare Tare Stress (Se) Obie) “oonoe Fane Set Hetont Cad (eo eleon Bectan Ceuta tevel OH: te Set00 Riaula speettie traviey {6h ‘sino Bistance’ ur to Top Mod Girder te Senco ldsint trrteteney (asp A or 6539 CE i 008 ina vetecie. eee ini) ion Sha vrane ° coursed aetent 0100 curse $1 totenness tees PSHE DT BESS ain ‘avioe Course #2 Helene Sronco sures #2 Thteunese tase sures 6 CaeraetonAiswance (2A ‘oto feurse #3 Helens sonc0 fears # lah stene0 (cures 4 Gaeracton Aivance (A {20000 fsurse 4 Hetone eronea curse #§ Thtetrese e200 fears #3 CeranonAtfomce (0k Sent fauree #6 Toteeress ‘sot Curse #6 Gareaston Aitoance (CAT ‘2o000 cures #7 Meter evonoo fsurse #1 Thtetnese 7800 Es HY aration Aine CO sie tetrte #8 Setebnese curse #8 Garraston Aifoance G64} Figure 2 Input Data for Case 1 ‘Unknown Material - E = 0.7 10COADE Mechanical Engineering News. April, 1995 SHELL COURSE THICKNESS OATA Thickness Values for Three Cases na coURSE DESIGN Test user (deo FY Ga) a) Gan) 1.207 1.8258 1.1250 MA 2 Vow 1.3038 Vtes0 wk 3 ‘imo “37650 7500 MA 4 Tez096 = “r7e18 75000 A & 3000 “a7s88 37500 MA 7 ligne “a7se7 ‘37500 MA 8 ‘10000 ‘10000 37500 MA Retiring Thickness Remaining Corrosion Design Test Design Test Ging im) Gnd” cin) 1 Lz 1.260 956576: 01 2 Vous 13039 calasge-o1 3 Trai “pensie-or “12260 ‘eee 36201 @ [00000 00000 ‘37500 37500 SHELL COURSE ALLOWED FLUID HEIGHTS Fluid Weights for Three Cases coURSE DESIGN rest eautRED ey coe) a 1 me 56.000 2 48.000 5 40°00, 4 32.000, 5 24°00 ‘ 16.000, 7 ‘i000 a ‘éo009 Figure 4 Case 2 Output Unknown Material - E=1.0 This change in “E” has made a big difference; there is cally a corrosion allowance left even for dhe hydrowst case, You can now determine the required inspection interval based on these results aad see i this suits your inspection, maintenance, and operations planning needs. First calculate the corrosion rate, N, based on the maximum ‘couusion that ly vecutred, N= (Original Thickuess = 1m Measured ‘Thicknessy/Years of Operation = (1.375 - 1.125)/10 = 0.025 in./year, This corrosion rate is quite severe. ‘The minimum remaining corrosion allowance is 0.057 in. (Based on the bottom course). Therefore the main inspection interval is calculated as follows: Shell Inspection Interval CAN Shell Inspection Interval = 0.057/2 x 0.025 = 1.14 years ‘This says you have to inspect the shell again in just over a year in order to still operate the tank at its maximum fill height without repairing the corroded area. This is still not fn attractive conehision, At this point, it probably would be worthwhile to ask the inspectors to go out and take more thickness measurements in the corroded area to better define the extent of the corrosion and the actual elevation that it starts at. The evaluations that have been made thus far were based on the ‘minimum thickness that was measured; however, API-653 permits that the measured shell thicknesses be “averaged”, and that the evaluation be made considering both the average and minimum thicknestes in the corroded region (Ref. Paras. 2.3.2 and 2.3.3.1 of API-653). There is no advantage to finding out how close the corrosion is to the ‘welds in this case since we are already using E = 1.0. Let's now assume that the following additional inspection data have een obtained: + The worst portion ofthe corroded area really does start at the bottom of the course. + Five thickness measurements, equally spaced per API- ‘682 criteria, result inthe following measurements: 1.2, 1.25, 1.3, 1.2, 1.125. This yields an average thickness of 1.215 in. Using the previous results, there now is a (1.215 - 1.0681) 1.147 in. corrosion allowance remaining. Recalculating the required inspection interval yields the following result Shell Inspection Interval = 0.147/2 x 0.025 = 2.9 years ‘This is hetterthan before butnot great. Operating companies ‘want to maximize theirinspection intervals, usually targeting for at lenst 10 years or more. Note that the complete API- 653 evaluation ofthis case would also require checking that the minimum measured thickness (1.125 in. in this case) is at least 60% of the required thickness plus the needed corrosion allowance, but we can easily see that this second. criterion does not govern here, At this point, you might choose to repair the shell in order te achieve complete flexibility for future hydrotesting; however, it's worth pointing out one more thing before concluding this example. There may be situations where the site cannot take the time to make the repair now and reeds to get the tank back into service. It is possible to use the TANK program to calculate the fill height limitations assuming the needed corrosion allowance until the next inspection, 12COADE Mechanical Engineering News April, 1995 Inthis case assume that you wantto place the tank hack into service and inspect it again in five years. For this situation, you need a corrosion allowance of (5 x 2x 0.025) =0.25 in ‘This corrosion allowance is then used as input data and the fill-height limits can be calculated. ‘The results are shown in Figure 5. Note that when you run this case, you must eset the TANK program defaultioconsiderthecorroded hydrotest case foran API-653 evaluation (i. within the Computation Control section ofthe program configuration ment). APL-653 THICKNESS/CORROSION RESERVES Retiring Thickness Renaiving Corrosion Design Test Design Test Ge an cin an asus 73017 Sat 367 “nose ‘9@151€-01 1.0681 ‘a7? 55, [seam “28290 “te2es, 36054 jou Seas 31533 risa6e 27605, 14692 21298 SHELL COURSE ALLOWED FLUID HEIGHTS Hud Weights for Three Ceses course "peste Test requiReo ae we to 1 sans 50.692 56.000 2 46.058 48.000 5 aecess 40-000 4 2oisz7 s2!000 5 221396 24.000 é ain 16.000, 7 119 8.0000 a 1319 “00000 Fignre § Case 3 Output Unknown Material = CA 28 in, -B= 10 As yon can see from Figure, the tank ean remain in service forfive years (actually more) atthe design illheightof crude oil withont repaireaclong as hydrotest is nat aconsideration during this time period. Depending on the circumstances, ‘this may lead you ta canclade that itis nat necessary to make any repairs now. ‘The last thing that is worth noting is the impact that the “weak material” ascumption has on the evaluation. The ‘output summarized in Figure 6 is for the exact same case as in Figure 5 hut assumes that yen found data that indicates that the entire shell was fabricated from A-516 Grade 60 plate. Maybe the tank contractarstill had the original design information for the tank. 21-653 THICKNESS/CORROSION RESERVES Retiring Thickness Remaining Corrosion Gn) Ge ae) ae) 1 roses gray care zts9 2 66933 “e666 4556728834 3 ‘soe “63018 370g 2448s § Taunt “300g 3g T2asn 5 lor30 ‘aes “32770128337 6 ‘ise “azar Tent isees 5 90us3e-01 “11310 255225190 8 00000 “00000 37500137500 SHELL COURSE ALLOWED FLUTD HEIGHTS Fluta Weights for Three cases couRSE DESteN est acaurReo ea re (ta 1 68.762 55.210 56.000 2 g2leaz ——S0.15¢ © 48-000 5 iSi3s2 Sosa aca 4 39681 32000 5 solo 24000 & — ia:610 16:000 7 10-670 8.0000 & ance pata Figure 6 Case 4 Output A516 Gr. 60 Plate - CA = 0.2 Inlooking at Figure 6, you can clearly see the difference that the material specification makes. There is now only a ‘minimal fill height limitation even for the hydrotest care. ‘This article discussed several things to be considered when doing a shell thickness evaluation in accordance with API-653 and illustrated these using an example. Items that ‘were not discussed include evaluation of pitting, using the TANK program to check corroded areas at elev are above the bottom of a course, shell thickness evaluations for riveted tanks, using the Variable Design Point Method, and using detailed stress analysis toevaluate locally corroded regions. We are planning to write future articles to diseuse these and other topics. jone that 13COADE Mechanical Enginee! 1g Nows April, 1995, Did You Know that CAESAR II Could Many users contact COADE to offer suggestions and request program modifications. Recently several ‘modification requests have been made for abilities already incorporated into CAESAR II. This article will point out some of the more useful, non-technical capabilities of CAESAR II which may have gone unnoticed through the course of several updates. All ofthe topics discussed below have been available in CAESAR Il for several years. Interfacing: CAESAR Isupports geometric datainterfaces {o most of the popular CAD (Piping Isometric) packages currently available. A summary of these interfaces is shown in the table below. Vendor Package Notes ComputerVision ComputerVision Intergraph PDS — Intergraph Enhanced for Ver 322 PDMS CADCENTRE New for Ver 3.22 PRO.ISO, Rebis Formerly ADEV Cadpipe ‘Orange Computing Formerly ISS Autoplant Rebis Formerly EDA, Additionally, any CAD package (not in the list above) ‘capable of generating either of the CAFSAR Tl neutral files ccan transfer data into CAESAR II. All ofthe interfaces can be accessed by selecting “Uuilities” from the Main Menu. Then, from the Utilities Men, select “External Interfaces” Data Transfer: Some users have a need to transfer model input data, and sometimes output data, into other analysis or data base packages. The model data (piping input) is best formatted for transfer using the CAESAR IT neutral file ‘The format ofthis neutral file is completely documented in Chapter 13 of the User's Manual. This neutral file cantains the raw numeric data with section headers, There are no extraneous text titles or comments in this file. Reading this file provides the casiest and most complete way to transfer ‘model input data from CAESAR II to other packages. An important point to note about this neutral file is that it supports bi-directional data transfer. Therefore if another analysis, data base, or CAD package creates this file the piping model can be brought into CAESAR I for analysis. ‘The CAESAR II neutral file interface can be accessed by selecting “Utilities” from the Main Menu. Then. from the Utilities Menu, select “External Interfaces”. Then from the Extemal Interface menu, select “CAESAR II Neutral File”. ‘Output data (analysis results) can also be setup for transfer into other packages. The “Large Job Printing” utility can create either an ASCH text file ora direct access binary file of the results of specified reports for specified load cases. ‘The ASCII text file does have titles to skip over, but the data is self explanatory. ‘The binary data file ie documented in Chapter 12 of the User’s Manual ‘The CAESAR II Large Job Print Utility can be accessed by selecting “Utilities” from the Main Menu Then, from the Utilities Menu, select “Large Job Printing” Yes(No Prompts: Once a user becomes familiar with (CAESAR TI, the “Yes/No/Are You Sure” prompts become ‘a nuisance, Users have requested an option for turning these prompts (affectionately known as “Chicken Sereens”) off. This option is available in the configuration module of CAESAR TI. ‘The configuration module can be accessed by selecting “Configure/Setup” from the Main Menu. Then from the Configuration Menu, select “Miscellaneous”. The ‘configuration screen presented contains a series of toggles, including oneto disable the “Yes/No/ Are YouSure” prompts, Graphics Imports: Users have requested the ability to include CAESAR II graphics in reports and other documents. This can be easily accomplished by directing CAESAR II to generate a PCX file, instead of sending araphics hardcopies directly to the printer. Most current Word Processors have the ability to import PCX files, providing a method to include CAESAR II graphics in reports. PCX files can be requestedby selecting'“Configure/Setup” from the Main Menu. Then from the Configuration Menu, lect “Display and Printer”. Move to the ‘PlotHardCopy” directive and toggle ite value to PCX. Graphics Spooling: Requests have been made for the ability to save CAESAR II graphics in bit-map files, for later printing. This ability is similar to the PCX. generation discussedabove. CAESAR Iican beconfiguredto generate hit-map files, which can be spooled using the graphios spooler of the Utilities Menu. Once so configured, each plot session requests the name of a bitmap file for graphics storage (files can be appended if desired). These files can he created at the input or the output level, and can each contain multiple graphics images. 14COADE Mechanical Engineering News. April, 1995 Bit-Map files can be requested by selecting “Configure! Setup” from the Main Menu. Then from the Configuration Menu, select “Display and Printer". Move to the “PlotHardCopy” directive and toggle its value to C2_Fil Note, this is nota standard bit-map format, no other third party package will be able to read these files. Once bit-map files are available, they can be spooled to the printer by selecting “Utilities” from the Main Menu. From the Utilities menu, select “Hard Copy Spooling”. This utility program will then prompt for the names of up to 15, bit-map files for subsequent printing. Seismic Analysis of Tall Vertical Process Towers By Some Forthe refinement of petroleum products tall vertical process towers are used to break oil down into more elemental ‘components such as gasoline, propane, ethane, and a variety of others. When these towers are being designed, there are several points that must be considered. Some of these might be, What type of material should be used ? What diameter vessel is needed ? How tall must this vessel be ? ‘What does the service life ofthe vessel need to be ? Is the vessel going to be located near & hurricane oceanline ? Will the vessel be located in an area of high seismic activity ? Fortunately, most of this information is provided to the designer. Chemical engineers will normally specify the material of construction, and the basic size and the details of the interior construction (how much packing to use, how many trays etc.). However, itis up to the vessel designer to determine how thick the vessel should be. This thickness is ‘afunction of the design specifications, the applicableloadings such as intemal or external pressure, and the physical ‘geographic location of the vessel. Depending on the vessel's location, it will have tobe designed to operate and withstand stresses that occur during @ variety of situations. An ‘earthquake is one such situation, The wall ofthe vessel must bbe capable of withstanding the hoop stress incurred due to internal pressure. When an earthquake event occurs, the vessel incurs a longitudinal bending stress. This bending stress combines with other stresses, such as direct axial stress due to weight and longitudinal pressure stress. Each of these stresses must be computed and compared to an ASME code defined allowable stress. ‘Todetermine these stresses one cancompute them manually, which is time consuming, or use a suitable computer program. For the last several years COADE has been developing a new program which performs these types of combined stress calculations. In this article we will discuss seismic designs using this new program in conjunction with CAESAR II, and hopefully we can learn to avoid pitfalls in the seismic design of tall veical process towers. The vertical process tower we will look at is outlined as, follows 60 inch ID 1.5 inches thick (all elements) 135 feet tall '5 foot skirt section, supported only at base Low Carbon Stee! Material UBC-91 Earthquake Loading Criteria ‘When an earthquake event occurs, the ground experiences accelerations mainly in the horizontal directions, and to a lesser degree the vertical direction. When the ground accelerates, it pulls the base ofthe tower (skirt section) with it, and since tall towers are flexible structures, the upper sections have a tendency to stay at rest. However, all sections ofthe tower must eventually move. When the upper sections begin tomove, the base or skirt section ofthe vessel isnow moving in adifferent direction. This relative motion produces inertial forces and bending moments throughout the tower. Of course, these moments reach a maximum at the bottom, Knowing the shear force atthe center of mass ‘of each element and its distance (from the point of support), ‘we can determine the moments acting on the tower. Inorderto determine the forces acting on the vessel, weneed to determine the fundamental period at which it vibrates. ‘The first natural frequency, which is the inverse of the fundamental period, can be determined by more than one ‘method. The first method which some vessel programs use is the Rayleigh method (or its variant, Freese’s method). This method is the numerical integration of the equation Fe (2* pi* sqrt E W*y*2/ gE W*y))). Where g = 386 in/sec? W = Weight at element centroid y= Deflection at element centroid ‘There is a text book method for computing the first natural frequency of a uniform cross section cantilever beam. The basic equation is F (0.597 * Pi)*2* sqr(E*1* g/W*LM) 15COADE Mechanical Engineering News April, 1995 Where Pi = 3.14159 Case 1 - Stress Bending = F. = Modulus of Plasticity, psi 494983412841 57197000 = 13647 psi 1 = Moment of Inertia, inches4 We= weight per inch Case 2. Stress Rending = L = Length in inches 351704*12#31,5/137099 = 969.7 psi 2 = 3R6 inlcech? For our tower mode! the above equation for F yields a value (of 5.43808 radians/sec oF 0.8655 hertz. Thenatural frequency ‘used in the nonlinear soil interaction equation which is a factor that determines the forces on the vessel elements. ‘The CAESAR II program uses the Eigensolution method, and terative algoridum which can extract several frequencies of apiping system or steel structure. This sa very accurate ‘method and tends to give better results for poorly meshed models. Toexploitthe difference between thesetwomethods, ‘the same models were run on both programs. The results are listed in the table below. Note : All models have a 5 foot Skirt Element Run #1 =2 Elements, skirt and 1 135 foot Cylindrical Shell Vessel Program - 2,640 ha CAESAR IL = 0.61293 he Run #2 -6 Elements, skit and 5 27 foot Cylindrical Shell Elements Vessel Program - 0,85484 hz CAESAR I = 0.849 hz Run #3~ 11 Dlements, skirt and 10 13.5 foot Cylindrical Shell Elements Vessel Program — - 0.85264 hz CAESAR I = 0.860 hz Run #421 Elements, skirt and 20 6.75 foot Cylindrical Shell Elements Vessel Program - 0.85318 hz CAESAR I = 0.8624 he For the first 2 runs, the Vessel Program produced moments ‘of 494953 and 351704 Ft-bs at the base of the tower. The ‘computed moment of inertia ofthe base element where these ‘moments act is 137,099 in4, ‘The distance from the ecnter Of the vessel to the ODis 31.5 inches. The resulting bending satrezs for each case is as follows. Conclusions: ‘The Eigensolution Method computed frequencies were all close 10 the final accepted value of 0.8655 her, ‘The traditional vessel method of computing the natural frequency ‘approached this value only after the tower had been broken to change Pipe Parameters | p{Lisene_cose = RU sine +cose tes ane scose) toe r{1=SN0 +c050 °= RUT SINO +COSO Figure 9 - Rend split at angle @ In order to split the shown hend at the angle 0, three spreadsheets of data are required to completely define the two bend elements Spreadsheet 1. Code first elbow: Bend (Y/N) ¥ Radius = R AX = L1+Length coming into tangent AZ Spreadsheet 2. Code second elhow: Bend (YN) Y Radius = R AX =L2c08 AZ = L2sin8 Spreadsheet 3. Code next pipe: Bend(¥/N) N AX=0 ‘AZ = L3 + Length beyond tangent A second reason to split the bend isif the pipe is coming into the bend at an off angle. In this situation, the angle @ represents the angle from 90 degrees tothe tangent point of the bend and straight run of pipe. The dimensions of. and 1L3 are defined below the figure 18COADE Mechanical Engineering News April, 1995 Stort Bend Figure 10 - Straight pipe intersecting bend at angle © In this case, two spreadsheets are required to define the bend. Spreadsheet 1. Code straight run: Bend (Y/N) ¥ Radius = R AX = L2cos0 AZ= L2sind Spreadsheet 2. Code next pipe: Bend (Y/N) N AXx=0 ‘AZ = L3 + Length beyond tangent Q. Why ure there no forces and stresses computed on rigid elements? ‘A. This question typically arises in the form of, “When I luok at the force report, why do T not see any forces and. ‘moments on the rigid elements?” By default CAESAR II does not show the forces and ‘moments on rigid elements. There is, however, a flag that can be tured on in order to see these results. From within te input, choose [KJaux. From the auxiliary menu choose optionS-Special Execution Parameters. One of the special execution parameters is a May 10 print forces on rigid ‘elements, Once this is tumed on, these forces and moments, will appear inv Ue output reports. As forthe stresses, itistrue that no tresses will be computed onrigidclements. Because rigid elements are typically used as constructs, valves, equipment, etc., CAESAR II has no way of calculating the cross-sectional area, therefore the stresses cannot be computed. CAESAR II Specifications Listed below ate dose exrurs & omissions in the CAESAR TL ‘program that have been identified since the last newsletter. ‘These items ate listed in two chisses. Class 1 errors ate ‘problems or anomalies that might lead to the generation of erroneous results. Class 2 errors ate geueral prublewts tat ‘may result in confusion or an abort condition, but do not cause erroneous results. Class 1 1) Element Geneiator, Au cur has beeu discovered i the element generator when setting up horizontal “large rotation” rod restraints, when the user specified negative direction cosine. The direction was always considered as positive. This citor was corrected in Patch C. 2) Dynamic Sess Computation Module: An error was discovered in the stess computation niodules such Uhat the “stress type” indicator for “time history” runs was runs to “assuie™ the SUSIOCC stress type. This error was corrected in Patch C, 3) Piping Emor Check Module, An ewer tas been discovered inthe presentation of the“minimumrequired wall thickness” value, The was applied improperly causing non-English values to be reported incorrectly. This eur is conected is Version 3.22. 4) Piping Error Check Module: An error has been discovered in the conversion of the API-G50 user dat to intemal program units. The input assumes the “length” conversion factor for the nozzle aud id heights, white the error checker assumes the “diamete conversion factor. This mis-up may produce enor if the units ile in use employs different conversion units for length and diameter, and the nvecte height 1 diameter ratio is less than 1.5. Note, all COADE supplied units files use consistent units, and therefore do not exhibit this problem. This error is corrected in Version 3.22. 19COADE Mechanical Engineering News April, 1995, Class 2 1) Stress Computation Modules (Static & Dynamic; RCC- MC assumed the came sess caleulation as NCIND at intersections (i. the stress depends on the moments of All elements framing into the intersection), which causes CAESAR Il report the allowable tress as 0.0. RCCAMC does not require this, sa the allowable stress calculations are now reported as per the code, as of Patch € 2) Stress Computation Modules (Static & Dynamic}: The ‘occasional stress factor (as pecifiedin the configuration file) was not implemented for NC. ND. or RCC-M C. which caused CAESAR II touse a value of 1.20 forthe OCC load cases, ie. Service Level B. This error was corrected in Patch C. 3) Piping Error Check Module: A tolerance errorhas been discovered in the verification of the bi-linear stiffness value K2, when using stiffness units other than Ibn “The errr prevented a successful passthrough the error checker, which prevented the analysis from taking place. ‘This error exists in Version 3.21 only. and then only if the job was generated with the Buried Pipe Module. 4) Applications Guide: Page 2-65 in the Applications Guide provides incorrect spreadsheet data for the example. The data on page 2-65 should be identical to that of page 2-64, except the TYPE should be 1. 5) Report Writer: A memory management error has been found in the “report writer” module, which produces the input listings. This error prevented the generati of all input listings for some large jobs. This error exists in Version 3.21 only, and a corrected module can be downloaded from the COADE BBS. ‘The necessary file is REPRT-EXE. 6) Miscellaneous Bend SIF Processor: error has been discovered in the application of the units conversion constants when running the Bend SIF processor. The conversions were applied after the data check. instead Of before. This caused error messages, and prevented the calculation. when non-consistent units systems were used. This error is corrected for Version 3.22. 7) Buried Pipe Modeler: A error has been discovered when generating from a spreadsheet with (wo intersections (SIFs) specified. Only the firstintersection was moved to the proper spreadsheet. The second intersection specification ended up on the wrong spreadsheet, producing a fatal error in the Piping Error Check module. ‘This error exists in all versions from 3.0 up to and. including 3.21. This error is corrected in Version 3.22, 8) Piping Error Check Module: A units conversion error has been discovered in the presentation of the API-650 results, for the “delta temperature” field. ‘The temperature offset was incorrectly applied, causing the temperature value to be reported incorrectly. This error is corrected in Version 3.22. TANK Specifications Listed below are those errors & omissions in the TANK program that have been identified since the lst newsletter ‘These items are listed in two classes. Class 1 errors are problems or anomalies that might lead to the generation of ‘erroneous results. Class 2 errors are general problems that may result in confusion or an abort condition, but do nat ‘cause erroneous results, Class 1 1) Minimum Metal Temperature Computations: An error has been discovered in the determination of the minimum metal temperature for the shell courses. Versions prior to 1.20a always used the material gronp designation acquired from the “General Data” spreadsheet, regardless of any changes made ta the individual courses on the “Shell Course Materials” spreadsheet. ‘This error exists in all versions up ta 1.208. This error ‘has been corrected in the “A” patch, distributed to all 2) Weightof Tamed Roofs: Anerrorhasheen discovered in the computation ofthe weight of domed roofs. This error exists only in Version 120. ‘This error was partially corrected in the “A” patch, distributed to all users. Patch “R” contains the corrected routine for computing the weight of domed roofs. 20COADE Mechanical Engineering News April, 1995 Class 2 1). Material Group_Verification: A string comparison ‘error has been discovered in the error checker which prevents users from modifying the material group ‘designations. This error always produced a fatal eror ‘message which prevented the job from running. ‘This error exists in all versions up to 1.20a. This error thas been corrected in the “A” patch, distributed to all 2) Anchor Bolt Area Calculation: An over-sight has been discovered in the computation ofthe actual anchor bolt stress which could result in aero divide”, aborting the program. This error only surfaces for small tanks with no overturning moment, This error is corrected in Patch “B”. 3) Appendix F Bookkeeping: An error was discovered in ‘an output record indicator, which caused the output processor to abort with error #157. This condition ‘occurs when the Appendix F calculations fail. ‘This errorexistsinonly Version 1.20, and wascorrected in Patch “B”. 4) Cone Roof Design: An error has been discovered in the conical roof design module when applied to small tanks. If there is only a single, center column (i.e. no girder rings), the program aborts in the middle of the design. ‘Thiserrorexistsinonly Version 1.20,and wascorrected, in Patch “C", CodeCale Specifications Listed below are those errors & omissions in the CodeCale program that have been identified since the last newsletter. ‘These items are listed in two classes. Clase 1 errors are problems or anomalies that might lead to the generation of erroneous results, Class 2 errors are general problems that ‘may result in confusion o an abort condition, but do not cause erroneous results Class 1 1) Shell Ring Selection: The reinforcing ring structural shapes were being selected incorrectly in the SHELL. program. The problem was corrected and the self exploding executable SHLFIX.EXE was placed on the BBS. This error exists in all 5.X Versions up to and including 5.304. 2) Staved Vessel "k" Parameter Calculation: In the calculation of the parameter "k” for stayed rectangular vessels (Figures A7, A7-B, AB, and A8-B), the ratio 2/11 was being incorrectly computed as 11/12. This. error has been corrected and is contained in the self= ‘exploding executable RCTFIX.EXE on the BBS. ‘This error exists in all 5.X Versions up toand including. 5.304. 3) P&P *y" Value Determination: In the PIPE&PAD ‘module, the“y” Value for stainless steel piping materials ‘was not correctly determined for temperatures over 1000 degrees F. The correction is located on the BBS in the filename PIPE&PAD ZIP. ‘This ernor exists in all §.X Versions up to and including 5.304. Class 2 » Gs yrection:_The floating head program would not let you analyze a full face geometry when the user answered "Y” to full face ‘gasket. This correction iscontained inthe self-exploding executable FLO.EXE on the BBS. ‘This error exists in all 5.X Versions up to and including 5.300. 2) WRC107 Emer Checker; The WRCIO7 program was ‘checking ratio’s of d/D on spherical shells as if they were cylindrical shells. The error checker would not allow the program to run, This has been corrected and placed on the BBS in the fle WRC1O7.EXE. ‘This error exists in all 5.X Versions up wound including 530A. 21COADE Mechanical Engineering News April, 1995 FE/Pipe Version 2.8 Released Paulin Research Group announced the latest release of HivPipe, Version 2.8 in February 1995. The major enhancements for this version are listed below. + Automated Animation (Displaced Shapes and Stresses) + Plate Processor + Auto Generated Saddles, Pipe Shoes, and Various ‘Support Structures such as lugs, legs, box Supports, etc. + “Include” Feature that “joins” together different finite element models. + New Out-of-Core Solver (Approximately 30% faster. More efficient memory use.) + 32 bit Model Graphics (Graphics response twice as fast.) + Quick Cale Feature for WRC 107, WRC 297, N318 and N392 for round and rectangular attachments on cylinders or spheres. + Auto Element Shape Corrections (Poorly shaped elements are corrected automatically) + Thermal Profiler for Unreinforced Fabricated Tee Model. For studying different temperature states in branch and header piping. + 8-Noded Solid Models with Bubble Functions. Usedin the automatic model generation of WELDOLETS, REINFORCED and UNREINFORCED FABRICATED, TEES. + Pseudosymmetric Multi-Nozzle/Plate Options forFaster Calculations + UserDefined Surface Loading for Wind and Extraneous Loads. + Reinforcing Pad Options for Hillside Nozzles and Bends with Stanchions + Stress Contours Pointer to let the user interact with the stress plots. + Improved Screen Processor. Supports Popup Windows, programmable Data Bases, and Extended Features, + Sliding Interface for Flanges to Compute Worst Case Hub Stress, + Mesh Overrides to Automatically Produce Crude or Fine Meshes for the Complete Geometry, or for Only Paris of the Geometry. * Auxiliary Data Panels in the Graphies Processor that Provide: Model Slicing Element Condition Verification Material Property and Load Labeling Fast Polygon Algorithm for Quicker Images Control of Stress Plot Appearance Setting of Maximum Stress Value Plotted, (Colored plotsno longer have to vary between blue and red.) 7. Light Shading From Any Angle + Additional local dieplacement field specifications for the analysis of tank floors as per API 653. Implementations include hottom and settlement types. + Inertial Loading Capability on Ream Piping Elements. + DOSFxtendercapable of allocating &4 MB of Memory. Work has already begun on Version 2.9, which will be capable of “including” CARSAR TI Models, as shown in the figure below. 22COADE Mechanical Engineering News April, 1995, COADE and DASSAULT SYSTEMS announce a CAA Development Partnership Agreement Boston, Massachusetts, 16 January, 1995 - COADE Inc. of Houston, Texas, U.S.A. and Dassault Systemes announced today that thoy are entering into a CAA development partnership within the framework of the CATIA Application Architecture (CAA) strategy. CATIA APPLICATION ARCHITECTURE provi industries with the software development tools, methods and standards required to create seamless integrated engineering applications based on CATIA openarchitecture. These industry specific software products complement the CATIA Solutions. Inthis partnership, COADE will imegrate pipe-stessanaly sis capabilities similar to those provided by their product CAESAR II, on top of the CAA CATIACADAM AEC Plant Solutions (CAPS) infrastructure, As an initial phase, COADE will embed its stress analysis solver with a CCAPS user interface. “The partnership with Dassault Systemes will help us 10 continue 10 meet our mission of providing the top technical ipe stress software in the most user-friendly environment, offering our users a seamless interface between design and analysis,” said Rex O. Evans, CEO of COADE Inc. “We hhave been approached several times in the past by other vendors who wished 1o team up withus similar partnership ‘but Dassault Systemes, with their CCAPS sofeware, were the {first to provide a foundation which we viewed to be on a par with our CAESAR II software" “This CAA partnership will provide a key industrial complement, which will make our solution for the Architecture/Engineering/Construction market a turnkey solution, This demonstrates the tangible production usage of the CATIA Open Architecture” said Bemard Charles, President Dassault Systemes R & D. “I am pleased to strengthen our cooperation with COADE for the benefit of our CCAPS customers, who have been able to appreciate COADE's knowledge in the pipe stress analysis domain for over a decade”. Dassault Systemes, created in 1981 of Dassault Aviation and currently employs 1,000 persons. assault Systemes is a worldwide leader in advanced CAD/ CAMICAE with CATIA and CADAM software used in the aeronautics, automotive and consumer goods sectors and by engincer-consiructors, plant owners and. oper shipbuilders The company's subsidiary, Dassault Systemes of America (Burbank, California isin charge of developing CADAM CADD software on mainframe and Professional CADAM fon workstations. "Thy development of the AEC Plant applications built on the CAA platform, Furthermore Dassault Systemes of America has esponsibility for marketing and sales support of CATIA 1d CADAM in the United 8 “ompany alse as a leaving role in the 23COADE Mechanical Engineering News April, 1995 The COADE BBS The COADE BBS (Bulletin Board Service) was implemented to better verve our user base. ‘The BBS allows users to acquire small program corrections, up-load data files, leave messages, andcheck the latest COADE news announcements, The inten! of the BBS és ta provide am additional avenue for overall customer suppor. Users should logon tothe BBS atleastoacea month to check the ktest news bulletin. Any software erors discoveredreported are posted here as soon as they are sonfirmest, Anytime a nev, important fle is available for down-loading, its existence is also posted in the news. By checking the BES.news, you can obtain the latest on the satus of COADE software products, “The BBS also provides aquick way to obtain pogramarrections. (Minor corrections the software are posted on our BBS and on CompuServe. Any time a major error is discovered, we re-ship the software wall users.) This i not to say that we won't ship the updated software when requested, iti just much more expedient for users who need the fix to down-load it ‘Acquiring files from the BBS is relatively painless, assuming you have a good phone connection anda fast (a east 9600 baud) modem. Coanceting to our BBS willbe 2 long distance or international plone call! If your modem is slower than 9604 haul try down-kaading the necessary file from CompuServe, this is usually only a local phone call and it will costa whole Tot less “The whole purpose of going oncline ist obtain information and ies, quickly and cheaply. Ifyou can't do both, don't go on-line. (Most communications packages estimate wansmission times. If your estimate isover20 minutes, don't doit call us and wewillsend the fileby mail occouries.) Recently auser, calling fom Australia down-loaded a 370k file at 2400 baud. ‘This transmission rook 71 minutes! This burden con the part of our users is not the intention of the BBS. If you can’t obtain a necessary ile quickly, o¢ you have problems, please call or fax us, COADE Engineering Software 12777 Jones Ra, Suits 480, Houston, Texas 77070 Tel: 713-890-4566 Fax: 713-890-3301 BBS: 713-890-7286 ‘CompuServe: 73073:362 24