What is the difference between pds and smartplant 3d

Differentiators Proprietary automation technology produces reliable and predictable results Comprehensive offering addressing both automated and manual components Flexible and scalable to meet varying client scenarios and schedules Automated verification and quality control. Deliverables The primary deliverable from this service is a Smart 3D backup containing the migrated catalogue, model, drawings and reports.

Work Process Specifications and catalogues The migration work process begins with the conversion of the source specifications and catalogues to the target environment. Model In parallel with the specification and catalogue conversion, the source model is processed into a neutral form used as the input to the migration automation software.

Within each discipline, a series of phases of activities are performed: Automation is applied to migrate the source data to the target this automation may in itself involve several steps, such as firstly migrating graphical elements, and then separately migrating additional attribute and property data Manual retouching is performed to improve the fidelity of the migrated model for example, the source system may not contain structural member connection relationship information, so this must be applied to the target manually Automated comparison and quality checking is utilised to review and correct any mismatches Drawings Once model migration has been completed, drawing generation for piping isometrics and drawing migration for orthographics can begin, if required by the client.

Technical Scope Specification and catalogue migration Piping Structural Electrical Multi-discipline physical model migration Equipment Piping including pipe supports Structural and civil Electrical including equipment and cable trays Instrumentation including in-line and offline Access, maintenance and other envelopes Drawing migration Piping isometric regeneration Orthographic volumes and drawing migration As-built drawing embedding Manual retouching Application of client modelling standards and procedures Conduit and duct banks Roads and paving Adjustments to label and dimension positions Additional annotation and dimensioning where required Quality assurance Automated comparison of source and target Manual review and checking of deliverables To-do list management.

Quality Assurance Due to the necessity to use manual retouching within some parts of the model migration process, and also to address fundamental differences between the source and target systems, TecSurge has developed a suite of quality assurance tools to ensure a high quality result. These tools perform a variety of comparisons between the source and target systems, verifying elements such as: Component end point locations and coordinates Property data Isometric bill of materials Our quality tools allow designers to quickly identify potential migration errors, and zoom into affected elements in order to make any necessary adjustments.

Getting Started In order to make a full and accurate estimate of the effort, TecSurge relies upon information provided in three different forms: Consultative discussion, regarding overall fidelity and scope requirements Detailed quantitative and scoping factors, captured in a questionnaire Access to the source specifications, model and drawing data In cases where access to the source data is not available, less accurate estimates can still be prepared based on the information supplied in the first two forms.

The following high level questions have a significant impact on the time and cost of the migration project: Is specification and catalogue conversion required? Why: specification and catalogue migration can be a significant effort in its own right, and can impact the critical path of the project. Should manual retouching be performed by TecSurge?

Why: manual retouching of the migrated module is by definition a manual effort, and therefore has a considerable impact on the number of resources and therefore cost. Are orthographic drawings to be included in the migration? Why: orthographic or arrangement drawings often require significant manual retouching to match the originals, and this impacts the number of resources required.

Are there specific schedule constraints e. Why: aggressive schedules can be met by TecSurge, however they may require additional resources and increase cost. Piping Material Class Information. Not removing it does not impact the load, although a message is printed in the log file. Worksheets unique to a specific source workbook are copied to the new output workbook. In the case of worksheets that are common to all the input workbooks, unique data records rows are included in the output.

In the case of worksheets that are common to all input workbooks, if data is duplicated, then the data from the first worksheet is taken. The utility ignores duplicate data from the subsequent common worksheets. Piping Reference Data Spreadsheet Merge Utility This utility merges translated catalog part data workbooks into one workbook. Input Excel Files location - Specifies the location of the workbooks that you want to merge. Output Excel file - Specifies the single Excel workbook that will contain all merged data.

Start - Starts the process. For example, you can convert values in inches to values in millimeters. This utility can also convert metric part catalog data to its imperial equivalent. The utility does not support the conversion of specification sheets. The utility can only convert one catalog workbook at a time. The utility processes all sheets in the catalog workbook and reports results in a log file. The utility does not convert metric files to imperial equivalents, unless you revise the delivered NPD Equivalence Rule workbook so that it has metric units as the primary units of measure and the equivalent imperial units of measure as the secondary units of measure.

The utility only converts dimensional parameters. It does not convert weights, densities, or any other unit-based properties in the workbooks.

Also, part schedule thicknesses and generic data are not converted. All data in the part classes must be in the same units.

For example, all parts must be in inches or in mm. Running the conversion twice ruins the data. The translator maps sizes regardless of the units or changes due to any prior conversion. If you have input data in more than one workbook, you can merge the data into one workbook using the Piping Reference Data Merge utility. The UoM Conversion utility must have the input data in one workbook. In the Piping Parts Excel file box, browse and select the Excel workbook with the piping part data to convert.

This file helps convert units from imperial inches to metric mm. If you want to convert units from metric mm to imperial inches , you must revise the delivered NPD Equivalence Rule workbook. Click Start Convert. UoM Conversion Utility This utility converts the units of measure in translated piping part reference data. Piping Parts Excel file - Specifies the workbook with the units that you want to convert.

Start Convert - Starts the process. In the Piping Catalog Excel file box, browse and select the piping catalog workbook. In the Log file box, browse to specify the log file for the conversion process.

Piping Catalog Excel file - Specifies the piping catalog Excel workbook. You must have sufficient Visual Basic programming skills to understand and modify the generated Visual Basic symbol code as needed. The translator creates a log file to inform you of any errors found while parsing the EDEN code. Typically items to look for in the log file include variables that may need to be declared as symbol inputs and functions for which translation is not yet available.

After you have translated and fine-tuned the Visual Basic code, you will need to compile the symbol and test it in the software. When testing, verify the accuracy of the graphics and the placement of the symbol ports.

For information on loading the symbol into the software, refer to Add a Symbol to Reference Data, page The created Visual Basic project should compile and generate the symbol correctly. However, in many cases the symbol will need some manual edits. The program takes command line arguments as inputs. The steps to translate an EDEN symbols are: 1. We recommend that you use the name of the symbol for the folder name.

We strongly recommend that you create a small batch file for this purpose so that the information can be easily edited and run again in case of errors.

Modify the generated Visual Basic symbol, if needed, and test whether the symbol places correctly. This should not be changed. These edits are due to some of the limitations of the translator due to the dissimilarities in the way a symbol is defined in EDEN and the way in which a symbol is defined in Visual Basic. Known issues are identified below. These variables will most probably be symbol inputs in Visual Basic. Whenever such variables are encountered, the translator automatically treats them as symbol Inputs.

AddInputDef 4, "Dimension 37 ", "Dimension 37 ", 4. Note, that in Visual Basic the symbol input can be called by some other name, say, "ImpellerDiameter", "PumpHeight", and so forth.

You will have to modify the name of the input to match the one that is defined in the excel data files. However, in Visual Basic there is a mechanism to draw the Cylinder along with the Nozzle that is, use the length property of the nozzle. It is not possible for the translator to determine which connect point in EDEN goes with which cylinder. Therefore, the translator simply translates the code as is.

Thus, it generates two overlapping cylinders in Visual Basic. This overlap is just a runtime overhead of drawing an extra cylinder for each nozzle. You may want to remove the code that draws the graphic for the cylinder if you are sure that the graphic for the nozzle will suffice to represent the symbol and thus the extra cylinder is redundant.

You will also have to remove the output declaration in the symbol initialize, if you choose to do this. However, in Visual Basic you are required to list all the outputs of a symbol in the initialization of the User Symbol Services object. If some graphics are drawn within an If-Then-Else condition, then the translator has no way of knowing which object should be drawn at runtime. The current implementation of the translator is such that it lists all the objects in the outputs.

You are required to modify the code depending upon which outputs will be used. Depending upon the condition, either a cylinder or a cone will be drawn, but not both. LoadIdentity oT4x4Temp. Transform oT4x4Current oOutputCol. Add oCylinderCapped2 oT4x4Current. Transform oT4x4Current. Add oConeCapped1 oT4x4Current. This causes a problem at runtime because one of the outputs will be "Nothing" at runtime. NumOutputs in the same initialize method appropriately.

The symbol graphics code may also be modified for better readability, however the code will function even if it is not modified.

In some cases, where the statements in the If-Then-Else are more complex, then more modifications may be necessary. Example of this may be when two graphics are drawn in the "if" case and only one is drawn in the "else" case. Approximations to Zero Visual Basic symbols have difficulty in drawing cones with zero radii.

In these cases, the generated code will compile successfully, however, at runtime it may raise some problems from the math calculations. This is avoided by changing the value of zero to a value that is very close to zero. In the above code, a value of zero is replaced with a value of "0. Aspects Equipment Symbols in Equipment can have aspects, and each graphic that is drawn can belong to one or many aspects. In Visual Basic we handle aspects by having separate ".

The translator does not generate separate code for each aspect. Thus, the code generated will not contain any information on the aspects. All the code generated will belong only to the SimplePhysical aspect. You will have to cut, copy and paste portions of the code into different aspects as needed. The translator does not generate this "Def" file automatically.

You will have to generate this file either with the wizard or by copying this file from another symbol and editing it as needed. This is because several Draw Complex Surface, Draw Line, and Draw Arc calls result in a single surface being drawn and thus adding the output automatically is not supported at this time. This code has no meaning in Visual Basic and this should be removed from the Visual Basic symbol code.

This example will convert the symbol for a standard full port globe valve. This symbol is used in the example to determine which EDEN Symbol Processor is required for extraction and conversion. Start PDS. Select Reference Data Manager. Select Graphic Commodity Library Manager.

Flip the toggle to Sub-string, and then type GLO. Select Revise Data. Click Accept. The system displays the EDEN module. In this example, "V11" is the module that should be extracted and converted.

Choose the module to convert, in this case "GLO". In Appendix B of the guide, find the record for 6Q1C11, [2-way] globe valve inline. This defines that V11 is the symbol processor for the part. Piping commodity symbol V11 notes a Model Code of V This process assumes you have not customized the EDEN symbol. If you have customized the EDEN symbol and user-defined Symbol Processors have been created, you must use Option 1 above and then review the Symbol Processor EDEN to determine the actual code used to place the physical representation of the part.

Flip the toggle to Sub-string, and then type V Click Extract Data. Select the V11 Model Parametric Shape from the list. The software extracts the module to the indicated folder.

Create a new folder for the conversion files. Copy the extracted EDEN module file to the new folder. Change folders to the new folder you created. The conversion utility creates the following files: CGlobeValveNew. More importantly, the log file displays messages regarding variables that may need to be declared as symbol inputs.

The log file also contains the parsed tokens so that any error in the parsing of the EDEN code itself can be detected easily. The log file also lists any function for which translation is not yet available.

After the DLL is compiled, it will be registered on the local machine. After the symbol has been compiled it can be placed in the modeling environment and then it can be verified for accuracy, especially regarding the placement of the ports in the symbol.

After the symbol has been verified to work, it can be integrated and then used in a production environment. Open the VB project and review the converted code. After you completely verify the new symbol, you need to distribute the DLL to all the client computers.

Add a Symbol to Reference Data In this procedure, you add a new symbol to the reference data. Before following this procedure, it is assumed that you have used the Visual Basic Part Definition Wizard to create a VB project and a Microsoft Excel workbook for the symbol. You will use this folder later when you copy the new symbol to the other clients. Refer to the Installation Guide for more information on installing the Programming Resources.

Create the Visual Basic Project for a Symbol 1. Open the Visual Basic project for the symbol. Open the modules that the wizard created and add or modify code as necessary. For example, you may need to add code in the inputs section and the outputs section of the parent class module. This module has the same name as the project, prefixed with a C. DLL file. Tip In our example, save the. Save the project and exit Visual Basic. Open the Excel workbook that the wizard created and specify the individual parts in the Head section on the part class sheet.

Add custom properties as needed on the part class sheet. You can add these properties in the Definition section, the Head section, or both sections on the part class sheet. Tip When you ran the wizard, you defined custom properties definition, occurrence, or both. These properties appear on the Custom Interfaces sheet of the workbook. Type an A in the first cell of all the new rows on the part class sheet.

Save the changes to the workbook, and then exit Excel. The bulkload process is usually done on an administrator machine. Test the symbol in the software by opening a session and placing the part that uses the symbol. Choose whether to deploy the. Distributing Symbols Automatically You can have the software automatically distribute new and modified symbols to client computers by using CAB files.

Then, put the CAB file on the Symbols share on the server. When a user on a client computer goes to place the symbol, one of the following happens:. If the symbol is a new symbol, the software automatically pulls to the client computer the dll in the CAB file on the server, and then automatically registers the dll on the client computer.

If the symbol dll already exists on the client computer, the software compares the version number of the dll on the client computer with the version number of the CAB file on the server. If the dll in the CAB file is newer, the software automatically pulls to the client computer the newer dll in the CAB file, and then automatically registers the dll on the client computer.

Because of Microsoft operating system requirements, the user on the client computer must have Power User or Administrator access to the computer. If you do not allow users to have Power User or Administrator access to the client computer, then you must distribute symbols manually. For more information, see Distributing Symbols Manually, page Select the VB project for the symbol using Browse.

Click Package. On the Included Files page, clear all the checkboxes to the left of the file names to remove them from the package except for the dll of your symbol.

That is, the only file name that should have a check next to it is the name of your symbol dll. Put the CAB file on the server symbols share. Open the Excel workbook that contains the symbol part and go to the part sheet.

Create a new column on the sheet called Codebase. Type an M in the first cell of the row and re-bulkload the workbook. Distributing Symbols Manually If you choose not to use CAB files to distribute Visual Basic symbols, then you must distribute and register the symbols manually. Important If the symbol being distributed is an existing symbol that has been modified, the major version number in the Visual Basic project properties must be increased by 1.

Increasing the major version number by 1 forces the recomputation of existing symbol occurrences when the Synchronize Model With Catalog command in Project Management is run. If an existing symbol is modified and distributed, all the new symbol occurrences will use the new symbol unless the new occurrence uses an existing entry of symbol's cache. If an existing symbol is modified and distributed, and an existing occurrence is recomputed, it will use the new symbol if the recomputation results in creation of new entry in the symbol's cache.

Place the dll for the new or modified symbol on the server's symbols share. Register the new. Tip You can drag the file into the Run box rather than typing the entire path. Repeat steps 2 and 3 on each client machine.

You can use the delivered configuration files without editing if you have not customized any of the SmartPlant 3D "out-of-the-box" properties. However, if you have customized SmartPlant 3D properties, you must edit the workbooks to match your changes. The delivered sample workbooks are:. Ideally, all short codes should be kept common across specs. This is only to be used if some spec has a different short codes used on SmartPlant 3D side, different than the generic mapping the Generic-ItemCode-Map sheet provides.

For more information, see Electrical User Attribute Sheets, page Related Topics Electrical Translation Map, page You cannot cannot relocate or rename the columns in the ItemCode related worksheets. Do not change existing entries in this column. Add new entries to the bottom. Leave this column blank if you want to map the component ItemCode directly to a tag number in the next column.

You must leave the short code column blank if you define a tag number. Examples specifically placed items Y are: couplings, plugs, unions. Examples of implied items N are: conduits, elbows, and tees. Object Type - Enter the geometry object type code. Port to use as SP3D Location - Enter the port number which corresponds to the location of the component.

Enter 0 if it is the origin. This is only to be used if some conduit specification has a different ShortCodes used on SmartPlant 3D side, different than the generic mapping the Generic-ItemCode-Map sheet provides. Conduit Spec - Enter the conduit specification name for which you want to define an override.

This commodity name must already be in the Generic-ItemCode-Map sheet. You can find this information on the CustomInterfaces sheet of your catalog workbook in column B, InterfaceName. You can find this information on the CustomInterfaces sheet of your catalog workbook in column D, AttributeName.

If this sheet is missing or if an design equipment's part class attribute in the XML file does not have a mapped entry in this sheet, then the part class attribute specified in the XML file is used as the SmartPlant 3D part class for that designed equipment. An appropriate warning is given in the import log file that no mapping sheet or mapping entry was defined. Other sheets represent shapes, nozzles and custom shapes, parametrics, and attribute map information sheets.

For more information, see Shapes and Nozzles Sheet, page To define a new part class item mapping, do the following. Fill in the details in the appropriate columns. Appendix A: Importer Workbooks To define a new custom shape mapping, do the following.

In this new sheet, define the attribute mapping for this custom shape's attributes. Please note that usually, the part class and part numbers for equipment components and catalog equipment will be different. You must keep this in mind when defining the mapping sheets. If this sheet is missing or if a design equipment part class attribute in XML does not have a mapping entry in this sheet, then the part class attribute specified in the XML file is used as SmartPlant 3D part class for that designed equipment.

A warning is written to the import log file about this to let you know that no mapping sheet or mapping entry was defined. Adjustment Rotation Matrix - If there is a coordinate system difference between the XML item and the SmartPlant 3D part, you can specify the adjustment rotation matrix to apply on the XML item's specified orientation so as to make it the equivalent SmartPlant 3D orientation after placement.

You can leave this field blank if there is no coordinate system difference. Verify that the data specified is correct. Any invalid data could cause unexpected results. For this E case, you can specify an Adjustment Rotation Matrix which when applied on the input orientation from the XML file would give the output orientation to use in SmartPlant 3D symbol.

Therefore, by specifying the Adjustment Rotation Matrix as [0,1,0] [0,0,-1] [-1,0,0] you can get the equivalent part orientation. Related Topics Equipment Translation Map, page You should use the Template-AttMap-Sheet as the template when creating these attribute mapping sheets.

Type - Enter the type. Copy this sheet to a new sheet for each item that you want to map. We recommend that you name the new sheet after the SmartPlant 3D part class and number. This name must be unique on this sheet. This attribute name must exist in the attribute interface that you defined in the previous column. This field is only necessary to make sure formula work on standard SmartPlant 3D internal values like 0.

You must ensure that all attributes involved in calculations are specified with the correct unit type. If you want the software to use an XML attribute value as it is in the calculation, you can leave this field blank.

Instance values of XML attributes used to evaluate formulae defined in next Column - Assume that for each equipment item instance, the values from the XML file are parsed according to its data type specified in previous column and entered into these fields.

Then the formulae are evaluated and the newly calculated attribute values are used in import. Define Formulae based on XML attribute values in previous Column to calculate the SP3D attribute value - If you do not use formulae in mapping, then leave this field blank. The formula will use the instance values in previous column and calculate the corresponding SmartPlant 3D attribute values.

The formulae can even refer to some other columns or sheets and need not be restricted to the XML instance variables in column F. We recommend that you name the new sheet after the SmartPlant 3D part number. This lookup reference is for parametric and catalog equipment. This field must be unique on this sheet. For more information about the columns in this workbook, refer to the Hangers and Supports Reference Data Guide.

You can find this information on the CustomInterfaces sheet of your piping catalog workbook in column B, InterfaceName. You can find this information on the CustomInterfaces sheet of your piping catalog workbook in column D, AttributeName.

For more information, see Piping User Attribute Sheets, page Examples specifically placed items Y are: valves, flange pairs takedowns , end flanges, caps, ends, spectacle blinds, blind flanges. Examples of implied items N are: pipes, elbows, tees, other branch components, reducers, flanges around valves. Related Topics Piping Translation Map, page This is only to be used if some piping specification has a different ShortCodes used on SmartPlant 3D side, different than the generic mapping the Generic-ItemCodeMap sheet provides.

Piping Material Class - Enter the piping specification material class name for which you want to define an override. Piping User Attribute Sheets The user attribute sheets the sheets with names that end with UA map user attributes defined in the XML file to user attributes in the software.

Appendix B: Automated Industry Commodity Code Creation The piping specification translation utility requires pre-defined commodity code formats. The properties must be included in the sequence in which they are defined in the.. You can re-build commodity codes as the piping specifications are being translated, or after the specs have been translated. Use this feature to switch from the default PDS commodity code format to the default SmartPlant commodity code format when translating piping specifications from PDS.

The following describes the format of the industry commodity based on the following types of commodity codes. Appendix B: Automated Industry Commodity Code Creation Miscellaneous Fittings This category includes flanged fittings, welded fittings, socket fittings, socket welded fittings, threaded fittings, tubing fittings, underground fittings, fire and safety components, and all other miscellaneous fittings.

Otherwise, the Surface Preparation property is used. Otherwise, the Flange Face Surface Finish property is used.

Otherwise, the Geometric Industry Standard property is used. Gaskets Gaskets are determined on the basis of existence in the gasket part data.

Otherwise, the Gasket Industry Standard property is used. Note that the nut height will not be explicitly included in the commodity code format for nuts. It is assumed that the nut type, the nominal bolt diameter, and the industry standard.

Note that some stock piping specialties, for example, valves, will have the industry commodity code based on a different, more appropriate, format. Some stock piping specialties, for example, valves, have the industry commodity code based on a different, more appropriate, format.

Index analysis models mapping files, 56 area list, 28 associating PDS files, 17 PDS projects, 13, 18, 20 automated commodity code creation, CAB files, 95 CableTraySpec, 98 CIMsteel, 35 member criteria, 37 cleaning pipe branch data, 74, 75, 76 piping commodity filter data, 72, 73, 74 commodity codes, 70, 71 automated creation during translation, ComponentMap, ConduitSpec, 99 configuration files PDS exporter, 22 converting PDS data, 57, 58, 60, 61, 63, 66, 70, 71, 81, 82 PDS symbols to SP3D, 83, 84, 86 PDS symbols to SP3D examples, 90 units of measure, 78, 79, 80 creating mapping files, 56 design equipment part class map sheet, discipline, 28 distributing symbols automatically, 95 manually, 96 EDEN symbols, 83, 84, 86, 90 command line structure, 84 translator outputs, 86 VB modifications, 86 workflow, 84 workflow examples, 90 editing PDS-translated data, 63 electrical lighting fixtures sheet, ElectricalTranslationMap.

Open navigation menu. Close suggestions Search Search. User Settings. Skip carousel. Carousel Previous. Carousel Next. What is Scribd? Pds Guide. Uploaded by vangarubalaji Did you find this document useful? Is this content inappropriate? Report this Document. Flag for inappropriate content.

Download now. Related titles. Carousel Previous Carousel Next. Jump to Page. Search inside document. Intergraph Corporation Huntsville, Alabama Warranties and Liabilities All warranties given by Intergraph Corporation about equipment or software are set forth in your purchase contract, and nothing stated in, or implied by, this document or its contents shall be considered or deemed a modification or amendment of such warranties. Table of Contents Table of Contents Preface The documentation set is divided into four categories: Administrative guides contain information about installing, configuring, customizing, and troubleshooting SmartPlant 3D.

Version PMC files Any file s with a. Note MicroStation SmartSolids are not rendered when they are in a reference file. This file defines: the user configurable equipment attributes on equipment.

To specify an attribute, you can define using: hard coded text such as "Required". Tip If the setup determines that PDS is not installed, an error message appears. The PDS Model Data Exporter is available for the following disciplines: Piping - In the Piping discipline, because you can have piping networks connected across models, a single XML file is specified for a set of model files being exported. Already a member? Close this window and log in.

Join Us Close. Are you an Engineering professional? Join Eng-Tips Forums! Join Us! By joining you are opting in to receive e-mail. Promoting, selling, recruiting, coursework and thesis posting is forbidden. Students Click Here. Related Projects. I am in contact with both the parties and both say we cannot give you any demo version to try my hands on because you cannot get any good idea of software with out the training!!!! Now the idea of getting training of both the software and then making decision seems rather awkward.

The other way is to buy the software blindly and be stuck with it for ever, good or bad. I have seen PDMS and it seems not so user friendly like most of the software which migrated to Windows environment rather late no Undo most of the part and etc…. SmartPlant superlative description at Intergraph site seems very enticing and it seems to be user friendly and powerful. But I have not seen any one working on it so cannot be sure what it is like in reality.

Any feed back from the users of the two would be highly helpful.