Caesar 2 tutorial pdf

Click on the first element you wish to rotate. Page: 7 Tutor m. Edit the form and use the Replace button to update the input file. Compare the pump operating loads with and without the structure. Would friction increase the significance of the structure? Page: 8 Tutor m. Task 3: No room for a loop; install an expansion joint instead.

Review the types of joint assemblies. A tied expansion joint on the riser and below the valve will be best suited to absorb the horizontal pipe growth over the pump. Use this value to select the number of convolutions. Then install the expansion joint and analyze its suitability. Check the pump operating loads. Why is it so high? The catalog shows a 20 convolution joint provides To save time in this examination, the expansion joint will be placed between the flange and pipe rather than between the nozzle and flange.

Torsional rotation Ry is 0. Run through the linear interaction formula for a quick check Actual Allowed Ratio Axial 0. Page: 10 Tutor m.

Length A of the Standards of EJMA Other convolution counts are available; watch out for fatigue rating of cycles ; consult the manufacturer. Page: 11 Tutor m. Task 4: What if the long weld neck flange is connected to a vessel? It will be re-connected by the nozzle specification next. The nozzle provides no axial flexibility but the longitudinal and circumferential bending flexibilities appear significant.

Page: 12 Tutor m. Results: Compare the updated pump loads. These loads are greatly improved but still exceed the limit of 2. Including this flexibility in the loop and expansion joint models will be left to the student.

Check other structural results and pipe stresses. Conclusion: The drop in load is significant but additional flexibility either the loop or expansion joint is required to satisfy the pump limitations. Assuming that added flexibility for the pump will drop the vessel loads, evaluate the current vessel loads. Stresses are calculated using a Division 1 — Design by Rule — approach while they are evaluated using the Division 2 — Design by Analysis — approach.

Since not all of the Division 2 criteria will be examined here, the Division 1 maximum allowable stress limits defined above will be used rather than the Division 2 design stress intensities.

This calculated using pressure stress equations. Pb is bending due to pressure. Additional checks would be required if fatigue failure is anticipated; in which case the peak stresses need be calculated and comparisons be made to the endurance limit.

Test this by running the analysis with and without pressure thrust. Page: 14 Tutor m. Task 5: What effect does friction have on the pump loads? Mz to Table 4 ratio is 2. The limit is 2. Make sure that these protocols are installed on the client computers. Install and run the Monitor Utility. The readme file is delivered in the top level product folder of the product media. Be sure you have the latest version of the SmartPlant License Manager software before beginning the installation.

Any existing license key will be invalidated after the upgrade to SmartPlant License Manager v You will also need to generate a new computer ID and request a new key. Hardware Configurations The SmartPlant License Manager licensing computer software should be installed on a stable, single node, hardware configuration such as a simple PC , with a static IP address, because license key installation and license seat usage authentication depends on the information gathered from the physical hardware.

Any automated changes that cause the hardware information not to match with the information used to generate the license key will result in a failure of the authentication process. This includes terminal application servers, networked and distributed storage management systems, and so forth. When these specialized systems occur in the user's network, the SmartPlant License Manager Server licensing computer should be installed on a separate dedicated hardware configuration system.

The SmartPlant License Manager licensing computer should be situated on the user's network where it can be accessed by all systems that are running application software that relies on the SmartPlant License Manager licensing computer for license management. If SmartPlant License Manager licensing computers are cloned after the license key has been installed, then the license management will fail on the cloned system.

Each SmartPlant License Manager licensing computer requires its own unique license key. In other words, you cannot use a newer version on a client computer to retrieve a license from an older version of SmartPlant License Manager on the licensing computer.

The license computer must have the same version or a newer version installed than the clients. You must log in as Administrator to install this software. If the media does not start automatically, double-click Setup. You can change this location and name of this file as it can grow to be a large file. If you stop and restart logging, you need to define the output location. This file can grow very large and users can redefine the location and name of this file.

Click Next. On the Software License Agreement page, select your country from the list and click Display to view the license agreement. The license agreement is delivered as a PDF file. Carefully read the license agreement. Select either License Client or License Machine.

If you want to install the software in another location, click Change and select the new location. Click Install on the Ready to Install the Program page. A status bar displays the progress of the installation on the Status Setup page. Do not delete any files that are created during installation or as a result of using SmartPlant License Manager. Removal of any files causes the license system to fail and can require install, repair, or possibly removal and re-install of SmartPlant License Manager.

Add pdlice. You may need to remove pdlice. Otherwise, you may receive a Connection timed out error message when you start your application.

You may also see the same error in your scavenging log file. The System Administrator completes or gives guidance about most of these steps. Administrator rights are required to install and setup SmartPlant License Manager. If you need more information, follow the detailed procedures in the other sections. Please refer to the delivered SmartPlant License Manager Readme for all the latest product installation updates.

Designate a computer as the SmartPlant License Manager license computer. This computer must be on the network and have a name with no spaces and a static IP address. Request a license key from the Intergraph Order Desk or generate a license key using eLicense. Click License Machine and enter the license key you received. If the license key installs correctly, SmartPlant License Manager software automatically closes.

Next, install SmartPlant License Manager on each client computer. Enter the SmartPlant License Manager computer name. Exit SmartPlant License Manager. Install the software that requires licensing. Use that product's installation and configuration guides to install each product. Use the Test Seat Reservation and Test Seat Release commands to ensure that communication is working between the license computer and the client.

Successful messages show appropriate communication. Click Test Seat Reservation. Select the license computer name and Batch or Interactive mode. Start the software product that requires SmartPlant License Manager licensing. It is continually updated. Will providing the Machine ID make my computer less secure? The Machine ID allows the license manager to uniquely identify your computer from a collection of hardware and software identifiers without explicitly publishing your computer's TCPIP address.

You do not need a serial number to install SmartPlant License Manager. Can I divide the licenses for one LAN into several license computers for the purpose of managing project access, for example, or as coverage in the event that my license computer goes down? Yes, you can divide the licenses. What happens if I install the new license key prior to expiration of the old license key?

The new license will overwrite the existing key independent of the expiration date. Is my existing key still running if I regenerate the Machine ID? Yes, but you will not be able to reinstall the old key. You will need to request a new key for the new machine identifier. No, you can request licenses without upgrading the software. If you are upgrading software, you must request the upgrade before you request licenses. A license request does not include a software upgrade and a software upgrade does not include a license request.

The license machine is the computer where the license key is loaded; it can be a standard computer or a server. The license key tells the license machine how many licenses it can issue. Clients of a license machine are computers where SmartPlant License Manager is installed and pointing to the license machine. If a license is available, the license machine provides it. If all licenses are in use, the client is not granted a license.

Please check the starting number in your Machine ID or license key. See the table below. No, your configuration is entirely up to you. A persistent network connection is required if you want to connect to a license server that belongs to a different LAN.

Can I make an educated guess at my installation date? Intergraph provides a key within 48 hours of receipt of your request via mail or phone. Please ensure that the date you request is the actual date that you install the key, making sure that all necessary software is available and loaded before that date.

We request that you notify us as early as possible. What happens if my license machine goes down? You are unable to check out licenses from this machine until it is back in use. Processes that already have licenses checked out are not affected by the fact that the license computer is unavailable. It is possible in critical situations to request emergency licenses from Intergraph.

They are installed on the client computer rather than a licensing machine. Contact Intergraph Support at or your local Intergraph office for more information.

What happens if the license machine is rebooted in the middle of my design session? Licensing does not depend on maintaining a continuous communication link to the license computer. What happens if my local computer goes down after I've obtained a license? If the scavenger cannot contact the client computer during scavenging, the license is marked for a hour hold before it is released.

The scavenger periodically advances this hour timer for each license. If the client is in contact sooner, the hold is voided and normal scavenging takes over. I am running out of licenses earlier than I believe I should be. How can I troubleshoot to understand what is happening? Have your users click Scavenge for Keys on the Scavenge Options dialog box or you can type pdlice -n in a Command Prompt window.

If you think that client nodes are improperly holding onto licenses, examine the results of the pdlice -M command. This shows you which client nodes have licenses checked out. If a client computer has no plant design-related activity and it is still holding licenses, rebooting that client and then scavenging from the license computer may free some licenses.

If possible, find out what was processing when the job stopped. Save the output of any scavenging process that returns a license. This information provides the reasons why the license was returned. What do I type to see the number of licenses?

How can I tell who is using a license? We installed a key for three licenses, but we can operate only two licenses at the same time. There can be several reasons. It is intended as a general road map for the program. This general doc- ument is the first source of information.

The Technical Reference Manual explains, in detail, the function of, input for, and output from each module of the program. These exam- ples illustrate methods of modeling individual piping components as well as complete piping systems. Here one can find tutorials on system modeling and analysis. In addition to these three manuals, a Quick Reference Guide is included with the soft- ware package. The Quick Reference Guide provides the user with commonly referenced information in a lightweight, easy-to-carry notebook.

While our documentation is intended to address the questions raised regarding piping analysis, sys- tem modeling, and results interpretation, not all the answers can be quickly found in these volumes. CAESAR II support is available by telephone, fax, the Internet, bulletin board service, and by mail; literally hundreds of support calls are answered every week.

COADE provides this service at no additional charge to the user. It is expected, however, that questions focus on the current version of the program. COADE conducts regular training classes in Houston and provides in-house and open attendance courses around the world. New versions are planned and targeted for a specific release date.

Some COADE users have expressed concern over tracking, archiving, and dis- tributing the various builds generated between major releases. In order to alleviate this problem for our users, all maintenance Builds for new releases contain all previous builds.

In other words, Build Y contains Build X. This increases the download size and time required to obtain the Build, but only one build is required at any given time.

How Are Builds Identified? Builds have a naming convention, as follows. The character U or F represents an unlim- ited or full-run version, L is an execution limited version, D is a dealer version. The fol- lowing examples illustrate this naming convention. Build Na m e Corre la tion CF. If the Build does not match your ESL, and you install it, the software will not function. You will receive error mes- sages that the ESL cannot be found, or you have an improper version. As new versions are released, additional input items become necessary and must be stored in the program data files.

In addition, file formats change, databases grow, and so on. A Build is intended for one specific version of the software. Using a Build on a differ- ent version without specific advice from COADE personnel is a sure way to cripple the software.

All entries in this news file are dated for ease of reference. Users should check one of these news files at least once a month to ensure they stay current with the software.

If users register with an E-mail address, they will be notified via E-mail of all new Builds. How Are Builds Obtained? The Builds are arranged in subdirectories by pro- gram. Each file contained in the directory includes a description defining what it contains, its size, and the date it was created. Decide which Build file you need and simply download it. What is Contained in a Specific Build? This is a plain ASCII text file that can be viewed with any text editor or simply printed to the system printer.

This text file con- tains a description of all corrections and enhancements made, which are contained in the current patch. When necessary, additional usage instructions may be found in this file. How Are Builds Installed? Builds distributed for Windows applications use a Windows installation procedure. The EXE is a self-extracting archive, which extracts to a number of sub-directories, each con- taining sufficient files to fit on a 1.

EXE program to actually install the Build. When a Build is ready to be released, the Main Menu module is revised to reflect the Build level. This allows the user to see, on the Main Program Menu, which Build is in use. To see which program modules have been modified, you can run a COADE utility program from within the program directory. A sample display from this utility is shown in the table below. By reviewing the following table, users can determine which modules have been patched and to what level.

When a new version of the software is released, what should be done with the old, existing version? Addition- ally, any Builds obtained should also be archived with the original diskettes. This will allow full usage of this version at some later time, if it becomes necessary. To reinstall an older version of the software, the distribution diskettes from COADE should be installed first.

Then, the last Build should be installed. Each Build includes the modifications made in all prior Builds. COADE schedules and distributes these updates approxi- mately every nine months, depending on their scope and necessity. Updates, maintenance, and support are available on an annual basis after the first year.

Limited Run Provides 50 static or dynamic analyses of piping system models over an unlimited period of time, but does not include program updates. Updates are automatically delivered to all full run users who purchase updates, mainte- nance, and support, and all lease users.

Added an alpha-numeric node label option to the piping input module Expanded Static Load case options: 1 added load components H, CS, HP, and WW hanger loads, cold spring, hydro pressure, and weight filled with water, respectively , 2 added HYDRO stress type, 3 added option to set snubber and hanger status on a load case basis, 4 provided ability to scale friction factor on a load case basis. Updated the 3D input graphics, as well as partial implementation in the static output processor including the Element Viewer.

Updated the spring hanger design algorithm to provide the option to iterate the Operating for Hanger Travel load case to include the stiffness of the selected hanger. Added new configuration options for ambient temperature, default friction coefficient if non- zero, automatically gets applied to new translational restraints , liberal stress allowable, stress stiffening, and Bourdon settings, as well as how to handle B Added the ability to define the flexibility factor on bends.

Included piping and structural files now support long file names, may be located in any directory path, and the number of included structural files has been expanded from 10 to Added a new warning report to the static output. Added a dirty flag to the piping input preprocessor and the configuration modules. Attempt- ing to exit these processors without saving changes produces a warning message. Added the ability to detect the differences between material data in the input file and that in the material database including missing user materials.

This feature offers the user the opportu- nity to use the original data. Updated API to 4th Edition. Added the ability to save static load case data without running the job. As of Ver- sion 4. The design pressure is applied to the computation of HT and HD. These loads are now repre- sented by CS and H in the load case definitions.

This addi- tional load case better reflects the intent of section The installation program allows total or partial installations, diagnostic checks of the installation, multi-language support, and ease of updating. EXE program. Once the installation program is initialized, a menu of context-sensitive options is dis- played on the screen.

For users upgrading to a new version of CAESAR II, the installation program can be instructed to place the new files in the same directory where the current version resides. The new version files will overwrite the old version files where appropriate.

Installation The installation procedure presents the user with a series of dialog boxes that request information or selections from the user. The installation dialogs contain from two to three buttons at the bottom. It is best if nothing else is running while the installation program runs. Most unsuc- cessful installation attempts can be attributed to other software running at the same time as the installation. Note that the software can- not be installed without this serial number.

Once the proper serial number has been speci- fied, the installation program reports the acceptance of the serial number and the type of installation about to take place. This directory is the location to which the software will be installed.

The dialog presented allows the user to navigate to different drives, either local or network, and to select directories. If the desired directory does not exist, it may be typed in manually in the edit box provided at the top of the dialog. By default, the installa- tion program assumes a destination directory the same as an existing version of the soft- ware. In almost all cases, the top button, for a full installation, should be selected.

A full installation ensures the complete package is installed from the CD to the destination direc- tory, and any ancillary procedures are executed following the installation. Several of the dialogs work in this manner, to ensure all necessary information is obtained prior to the start of the actual file transfer. Once this dialog is complete, the Language dialog is presented. This dialog allows the user to select from various languages, which then dictate the exact language resource files that will be installed.

Typically, the folder name should be the same as the software name, for ease of use. The ESL is the security device used to protect the software license. Various types of ESLs are supported by the software, each requiring their own device driver.

This dialog enables the installation of the correct driver assuming the user makes the correct selection. Once the ESL type has been selected, the installation program presents the user with a dia- log summarizing all of the selections just made. This is the last dialog presented before the actual transfer of the files takes place.