Smartplant pid installation

In addition to the interactive approach of updating drawings, you can schedule the entire update process, except for the resolution of missing symbols, which is a manual process as described above. Reporting capability provides a summary of the selected drawings and the out-of-date criteria detected during the analyze step. The double quotes are required around this path, with no space between the -f1 and the opening double quotes.

For example, if you type the following command string, the software places the resulting. Work through the standard software installation on your database platform.

When you click Display on the License Agreement dialog box while running setup in record mode, the following message appears. Click OK to acknowledge that you are accepting the license agreement for all users on whose computers you will install the product. Setup then returns you to the normal installation process by displaying the license agreement and enabling the Yes button on the License Agreement dialog box.

The double quotes are required, with no space between the -f1 and the opening double quotes. The double quotes are required, with no space between the -f2 and the opening double quotes. If -f2 is not defined, a log file is created in the same location as the. Check the. A successful silent installation produces a. The uninstall procedure should use the same command and procedures as for the installation, both for the record mode and for each workstation mode; however, you should specify a different name for the.

You can also define symbology for graphics, default formats for data, and key distances that affect the behavior of the application. Usually, a project manager sets these options at the beginning of a project. The project manager seldom modifies these options except on rare occasions when project requirements dictate a change.

These locations are set at the time of plant structure creation. Install SmartPlant Reference Data 1. Review your Current Settings, then click Next to install the reference data. After installation, share the folder that contains the reference data. All SmartPlant users must be granted read permission to this share. Write permission to the share is required to make changes to the symbols, rules, templates, and other reference data.

We recommend that you make a copy of the reference data and store it with your plant files. This common practice will help you with future service pack installations, data recovery, and so forth. When working in an integrated environment, thin client mode operation is used as the means of providing Workshare.

When you execute administration activities via Citrix client, the software actually performs these activities on the server side, while the client remains idle, and the connection to Citrix is lost, possibly resulting in corruption of data.

Examples of these types of administration activities are: upgrading the database to a new version or importing a large number of drawings. As a workaround, we recommend that you perform these kinds of activities either on your database server machine or on a client machine using a configuration other than Citrix.

This means that it is possible to segregate intellectual property between sites by transferring only the data that needs to be shared. When using Workshare, it is necessary to update reference data at remote locations and to move data between sites. Using Thin Client Mode All users share a common database, so that there is no need to update reference data at remote locations or to move data between sites.

Publish the SmartPlant Application You need to publish the application to allow you to view the data using a web page. The names of dialog boxes may vary from the ones described in this document according the version of Citrix Presentation Server that you are using. On the Specify What to Publish page, do the following: a. Click the Application option button the default.

On the Program Neighborhood Settings page, if desired, define a program neighborhood folder and add shortcuts for the clients, and then click Next. On the Specify Application Appearance page, specify the window size, color, and start-up settings according to your needs, and then click Next. On the Specify Servers page, add the Citrix server and then click Next.

On the Specify Users page, add the user accounts that are to be granted access to the published application and then click Finish. After publishing the application, do the following to create the. You can also use this folder for temporary files.

Modify the system path statement on the server to include the common folder path in the system path. Terminal Server Logon Sequence The following section describes the logon sequence of system procedures carried out automatically.

Ensure that you have edited the Rootdrv2. When a user logs on to Windows Server, a logon script Userlogon. Therefore, you can run any pre-logon command or script from this file. The Userlogon. The Rootdrv. To upgrade, you must perform the following steps: 1. If you are working on a SQL Server platform, you can skip this step.

Open and then close Options Manager without running any commands. While the plants that have not been upgraded will appear in the Tree view, none of the data below the plant will be available. Attempting to work in a non-upgraded plant results in a message stating that the plant must be upgraded first.

A plant with a mixture of upgraded and non-upgraded data may result in some data being permanently inaccessible. To help you identify non-compliant data, use the Database Constraint Report. Tasks for correcting constraint violations 1. Make a complete backup of the data you are upgrading.

Generate a Database Constraint Exceptions Report. Clean up the database by removing orphan model items. Resolve constraint violations. For more information, see Constraint Utilities on page Generate a database constraint exceptions report again. Run the appropriate constraint utilities again if any exceptions still exist.

Continue running the database constraint report and the constraint utilities until no exceptions are reported. Make a complete backup of the now compliant data. The utility runs the report on the active plant that you are connected to at the time. After connecting to the database, click the Create Database Constraint Report button. This process may take several minutes, depending on the amount of data you have in your plant.

When complete, the utility automatically saves a copy of the report in the temp directory under your user profile and displays the file name plant name - ConstraintExceptions. Exit the Database Constraint Exception Report utility. Open the report using Microsoft Excel and save a copy of the report to another location other than the temp directory.

We recommend running this utility again until no discrepancies are reported. Microsoft Excel must be installed on any workstation from which you run the Database Constraint Exception Report utility. The first sheet in the report is the Report Progress Messages, which contains a list of the constraint checks made and the number of violations detected for each constraint check.

Each violation type appears on its own worksheet, with the name of the constraint violation displayed on the worksheet tab. Each worksheet also contains a list of drawings containing constraint exceptions, along with the name of the recommended constraint utility usually in cell B1 to use in resolving the violation.

However, unlike all the other constraint utilities that run on a drawing-by-drawing basis, the Clean Data utility runs on the entire plant data set. If Clean Data is used to resolve any particular constraint violation, a particular drawing will not be specified in the report for this constraint violation nor will a utility name be listed at the top of the worksheet.

Using Constraint Utilities Before running any of the constraint utilities recommended by the database constraint report, run the Clean Data utility inside a blank drawing, then run the Database Constraint Report. Running Clean Data first decreases the number of exceptions listed in the report and lessens the amount of further manual data cleanup required. The remaining constraint utilities must be run from within specific drawings.

Each plant may require a different set of utilities. Open each drawing listed in the database constraint report and run the recommended macros on the drawing. You need to run only the macros listed in the report for that particular drawing. In general, each utility attempts to repair the constrain violation. However, in some cases the violation could not be cleaned up by the utility and the item is band-aided in the drawing.

This situation is noted and logged in each utility's corresponding log file. For more information, see Constraint Utilities Log Files on page You must manually fix any band-aided items in a drawing by deleting the item and replacing it.

If the relationship cannot be repaired, you must delete it and replace it. If the graphical label is watching a graphic, the database is updated to match, thus repairing the LabelPersist. If the label cannot be repaired, the utility band-aids it. You should delete and replace these band-aided items. If the graphical symbol exists, the utility repairs the item by updating the database with its graphic OID value.

If the graphical connector is connected to a symbol, the utility repairs the connector by updating the database to match. If the connector cannot be repaired, the utility band-aids it. If the graphical OPC exists, fix it. You should delete these items. If the graphical relationship indicator exists, the utility repairs the item by updating the database with its graphic OID value. If the graphical relationship indicator does not exist, the utility deletes the relationship from the database.

The utility band-aids the graphical connector, which you should delete. You should delete band-aided items. If the graphic does not exist, the utility deletes the representation from the database. The graphic parent must be an equipment or equipment component for the relationship to be re-established. If the relationship cannot be re-established, the utility band-aids it. If the Nozzle graphic is in the drawing, the utility band-aids it. Constraint Utilities Log Files Each constraint utility generates a log file, which records each action taken to correct the constraint violation.

Log files are located at the path specified in your TEMP environment variable. Constraint Utility Log File cmdnotconnectedcomps. Share Paths to Site. Create a UNC network share to the folder containing the site INI file and be prepared to provide this path during the upgrade process.

Set Oracle Parameters If you are using an Oracle database, you must modify the following parameters in the initsid name. After completing the upgrade process, reset these parameters to their original values. You can use a higher number if necessary for other applications. SmartPlant uses open cursors to improve performance and scalability for database inserts, updates, and deletes.

Hash Parameters — Provide extra memory for the Oracle hash procedure by setting the following hash parameters to the values shown below. The upgrade process runs much faster if the hash table fits in RAM, rather than being written to and read from the disk.

Therefore, by providing extra memory for this procedure during the upgrade process, you can significantly reduce the time required.

However, you should make sure the setting was not previously changed to False. The new value should be as large as possible without interfering with the needs of the operating system. A value of default x 10 would not be unreasonable for a server with a gigabyte or more of memory. Memory Management Considerations Upgrading database information requires significant changes and, therefore, a significant amount of database server resources.

For that reason, Intergraph makes the following recommendations. You should limit the use of SmartPlant applications on the server, as well as access to the database by other plants. The more activity occurring on the database server during the upgrade process, the longer that process will take.

Version The following table is a compatibility matrix of the most recent software versions. Upgrading Plants Containing Projects Running the Upgrade Utility on a plant containing projects upgrades both the plant and its projects at the same time. Each of the upgrade tasks handles any necessary changes in both the plant databases and the project databases.

Upgrading Satellites in a Workshare Collaboration You do not have to collapse or shut down projects or satellites in Workshare collaborations before upgrading. Upgrading a satellite is a separate process. The host for a connected satellite must be upgraded before the satellite. Upgrading a Site When you open a site created in Version or Use the Upgrade Site command to perform the upgrade. Upgrade a Plant After you select the site containing the plants you want to upgrade, the SmartPlant Engineering Upgrade Utility displays a list of active plants that are available for upgrade.

Select the plant in the Tree view to see the available applications that can be upgraded for that plant. Right-click the active plant and select Upgrade Plant from the shortcut menu. The utility moves the plant from the Active plants node to the Upgrades in progress node and displays the list of upgrade tasks required to upgrade the selected plant.

Right-click in either view and select Finish Next Task to start the first upgrade task. If there is more than one task in the Upgrade Tasks view, click Finish All Tasks to complete the plant upgrade. After the plant is upgraded, the utility moves it back under the Active plants node and updates the plant status in the Upgrade Tasks view to Up-to-date. The formats and select lists will also be marked as out-of- date.

When the first task finishes, click Finish All Tasks to complete the application upgrade. After the application is upgraded, the utility moves the plant back under the Active plants node and updates the application status in the Upgrade Tasks view to Up-to-date.

Open Site Command File Menu Allows you to select another site containing other plants you want to upgrade. The status of each task appears in the Status column. The Upgrade Utility records how far it progresses during an upgrade task so that it can recover if system problems occur.

The status of each task appears in the Status column in the Upgrade Tasks view. Upgrade Plant Command Upgrade Menu Displays the upgrade tasks required for the plant upgrade process. On choosing this command, the utility moves the plant from the Active plants node to the Upgrades in progress node and displays the list of upgrade tasks required to upgrade the selected plant.

The formats and select lists will be marked as up-to-date. You should also use the Oracle analyzer scripts to optimize your databases. Backup Each Upgraded Plant After you have completed the upgrade process for each plant, you should do the following: 1.

Set the backup location for the plant in SmartPlant Engineering Manager and perform a full backup. Perform a complete database backup. Perform a file system backup to archive the drawings, reference data, and other files. These analyzer scripts collect statistics and store them internally in the database to determine potential execution paths so that the one with the lowest cost can be selected for use. After the upgrade, you should add these scripts to your nightly backup routine.

Preserve Software Customizations The Upgrade Utility does not make changes that might overwrite user customization of display names, property formats, calculation programs, validation programs, or layouts. A data dictionary change made during an upgrade can cause layouts that use PipingPoint properties to have an incorrect caption or column heading. None of the default layouts delivered during installation include PipingPoint properties. However, if you added these properties to one of the default layouts or created a new layout with PipingPoint properties, you can manually revise the captions for any layouts that use PipingPoint properties after you upgrade by doing the following: 1.

In the list on the Engineering Data Editor toolbar, select the saved view that contains PipingPoint properties. On the Table Properties dialog box, click Advanced. Click the Layout tab. In the Display Property list, select the PipingPoint property. Confirm that the caption is appropriate for the property. If you need to modify the caption, make changes in the Caption box at the bottom of the Advanced Table Properties dialog box.

These changes can include deletions and additions to reference data, as well as modifications to existing data formats and locations. User Access Before you can upgrade the reference data and drawings for an upgraded plant, you must define user access for the plant in SmartPlant Engineering Manager. This log file is saved in the folder where the symbols are stored. Upgrade Reference Data 1. Select the site and plant for which you want to upgrade reference data.

A splash screen displays, then a message box informs you when the upgrade operation successfully completes. Click OK. When these changes are made, they apply to all drawings items after the time of change, but do not apply to existing drawing items. The Update Drawings functionality provided by the set of Out-of-Date Drawings commands in Drawing Manager allows you to manage which drawings are updated with the latest reference data changes by defining values that define out-of-date drawings criteria and by resolving any symbols that have been deleted, moved, or renamed.

You can also schedule these update operations and create reports. For more information about this functionality, see the Drawing Manager Help. Using the Update Drawings functionality is not required as part of the upgrade process, but it is strongly recommended. You must manually resolve the missing symbols using the Resolve Missing Symbols dialog box, which lists the symbols in question and allows you to define the new location of each symbol.

In addition to the interactive approach of updating drawings, you can schedule the entire update process, except for the resolution of missing symbols, which is a manual process as described above.

Reporting capability provides a summary of the selected drawings and the out-of-date criteria detected during the analyze step. This report format is non-configurable.

When you select this command, the selected drawings are analyzed based on the out-of-date criteria and the results display on the Update Drawings dialog box.

Update does not update any symbol whose definition has been changed into a break component. This situation occurs when you have a catalog item that has been placed in a drawing and then you change its definition to be a break component. Intergraph recommends that you backup your work or create a version of your work prior to using this command. Total drawings selected — Displays the number of drawings selected.

Report — Generates a Microsoft Excel report describing the details of out-of-date drawing s. Out-of-date drawings — Displays the number of drawings that are out-of-date based on the criteria selected using the Out-of-Date Drawing Criteria dialog box. Resolve — Displays the Resolve Missing Symbols dialog box. Use this button to resolve any missing symbols. Drawings with missing symbols — Displays the number of out-of-date drawings containing symbols that do not exist in the catalog.

For example, if the path is invalid, then all drawings in the project are in an out-of-date state but the software cannot update them. An error message displays and the report displays Drawings with a? Old Path - Displays the relative path of the missing symbol.

New Path - Displays possible options for defining correct locations for the missing symbol s. Drawings - Displays the list of drawings that contain the missing symbol s. Missing Symbols — Filename specified for at least one representation in the drawing does not have the corresponding symbol definition file available in the current catalog.

This criteria covers model items updated via Llama Outside the drawing. The OPC label is in a to-be-updated state as its mate has been moved. Recreate State — The drawing is in a Recreate state. These rights are defined by categories. Categories with radio button options indicate that the rights contained within are mutually exclusive, meaning you can choose only one right in that category to apply to the role.

In other categories, you can choose multiple rights, as denoted by check boxes. None — The user is not allowed to execute the application or utility for this plant structure. To download and run this utility, go to the URL for Intergraph Smart Support , then under Find the answer to your question type and follow the instructions. If the installation does not start automatically, double-click setup. On the Welcome page, click Full Installation. On the License Agreement page, select your country or region from the list to view the license agreement in your language and then select the I agree to the license agreement and conditions check box.