Limitations - Intergraph Smart 3D - Administration

Intergraph Smart 3D Export PDS to Smart 3D

PPMProductFamily
3D Design and Visualization
PPMProduct
Intergraph Smart 3D
PPMCategory
Administration
Version_S3D
12.x(2018)

Limitations when Exporting from PDS

  • FrameWorks Plus does not write tapered member, arc members, or generic solid members (created using the Place Solid Element command, which creates a FrameWorks Plus solid element from a MicroStation solid element or from two MicroStation 2D elements) to the CIS/2 file.

  • You cannot export grids from FrameWorks Plus.

  • The PDS Model Data Exporter is not used to export Structure data from FrameWorks Plus. You must use the CIS/2 translator for FrameWorks Plus that is delivered with FrameWorks Plus, which is leased separately from Smart 3D.

  • You cannot export ladders, stairs, handrails, or platforms from PDS.

  • You must have FrameWorks Plus and PD_Shell installed on the computer where you install the translator.

  • The PDS Export Tools component is a separately licensed product. Before attempting to install the component, please contact for licensing information.

  • You can use the PDS Model Data Exporter with PDS version 8.0 or higher. If the PDS project is an earlier version, you need to upgrade the project before using the utility to export data.

  • There is no drawing conversion available.

Limitations when Importing PDS Data

  • You should import Electrical Equipment using File > Import > Equipment command.

  • You will need to reestablish piping connectivity as it is not maintained across XML files. If you want to maintain connectivity, export all model to a single XML file at one time.

  • DVCS data is not imported.

  • PDS plant monuments placed far away from the global origin will cause errors when you try to import.

  • Attached MicroStation graphics in PDS import as unintelligent, non-editable objects in Smart 3D. Similarly, equipment with attached MicroStation graphics import as non-editable objects.

  • Equipment that was rotated and mirrored in PDS may not import in the original orientation.

  • Piping commodity override and piping commodity synonym items may not import correctly.

  • Piping taps and trunnions may require remodeling.

  • Because Raceway specifications are sized based in PDS but are not sized based in Smart 3D, you may have to re-assign the specifications after import.

  • The software will not graphically import EDEN-based or Pelican Forge- based supports. You can import designed support locations only.

  • Imported structural members are standard Smart 3D members. However, there are no frame connections, assembly connections, or relationships defined for any of the members on import. In addition, there is no data management of the imported members (the CIS/2 model can be imported multiple times without recognition of a prior import resulting in members being placed on top of the previous import).

  • You must create a mapping file using the File > New Mapping File Command before you can use that mapping file when importing a structural model.

  • The mapping file created by the software is a template. The software does not write known-to-be-different section names to the mapping file. You are responsible for verifying, editing, updating, and maintaining the third-party application section names in the file.

  • Non-circular holes from FrameWorks Plus may not import correctly.

  • If you edited the global origin in FrameWorks Plus, objects does not import to the correct location and must be moved to the correct location in Smart 3D.

Limitations for the Pipe Branch Cleanup Utility

  • The utility does not remove duplicate records from the branch tables.

  • The Pipe Branch and Pipe Nominal Diameters sheets must exist in separate workbooks. One way to set this up is to open the piping specification workbook, and cut and paste the Pipe Nominal Diameters sheet into another workbook. The specification workbook has the branch sheet in it. After the process is over, copy the nominal diameters sheet back into the specification workbook.

  • Before running the Pipe Branch Cleanup utility, you must convert at least one PDS specification using the PDS translator. The conversion results in one specification workbook and one catalog workbook per spec.

  • The Workstation setup includes the PDSTranslator folder only if you have specified the Project Management option during installation.

  • The process overwrites the Excel Pipe Branch workbook.

  • The process does not mark any records in the workbook as changed.

Limitations for the Piping Commodity Filter Cleanup Utility

  • The Piping Nominal Diameters sheet and the Piping Commodity Filter (PCF) sheet must be in the workbook specified for processing.

  • The utility does not merge multi-size items, such as reducers and reducing tees, unless all the records in the first size and second size match.

  • The utility may change the formatting of some merged cells. If you require specific formatting, it may be necessary to apply the desired formats to modified cells after the cleanup is completed.

  • Before running the Piping Commodity Filter Cleanup utility, you must convert at least one PDS specification using the PDS translator. The conversion results in one specification workbook and one catalog workbook per spec. The specification workbook contains the piping commodity filter and piping nominal diameter information.

  • The process overwrites the Excel workbook.

  • The process does not mark any records in the workbook as changed.

Limitations for the Piping Reference Data Merge Utility

  • The utility does not support the merging of specification workbooks.

  • The utility can merge as many catalog (part) workbooks as required, and reports the results in a log file.

  • Before running the Piping Reference Data Merge utility, you must convert at least two PDS specifications using the PDS translator. The conversion results in one specification workbook and one catalog workbook per spec. The Piping Reference Data Merge utility merges catalog (part) workbooks.

  • The output workbook includes a Sheet1 worksheet. You can remove this sheet and save the workbook before bulk loading. 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 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.

Limitations when using the UoM Conversion Utility

  • Before running the UoM Conversion utility, you must convert at least one PDS specification using the PDS translator. The conversion results in one specification workbook and one catalog workbook per spec.

  • 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 thickness 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.

  • The Workstation setup includes the PDSTranslator folder only if you have specified the Project Management option during installation.

  • A default NPD Equivalence Rule workbook is delivered in the [Product Folder]\Core\Shared\UOMServices\xls folder. This file helps convert units from imperial (inches) to metric (mm).

  • You must remove the Read-only property on the NPD Equivalence Rule workbook before running the conversion process.

Limitations when Distributing Symbols

  • 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.

  • 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 re-computation 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 re-computation results in creation of new entry in the symbol’s cache.

Limitations when using the OD to NPD Utility

  • Before running the OD to NPD utility, you must convert at least one PDS specification using the PDS translator. The conversion results in one specification workbook and one catalog workbook per spec.

Limitation when using the PDS Translator

  • The PDS translation process requires the specification writer to make some manual edits to complete the conversion.

  • You may need to run the translation step a number of times.

  • If the PDS translator encounters two through-bolted fittings requiring a complete substitution of cap screws; and both through-bolted fittings have identical bolted ends in terms of end preparation, pressure rating, and end standard; and the two through-bolted fittings imply different cap screw commodity codes in PDS, only one cap screw record will be created in the Bolt Selection Filter. The PDS Translator will arbitrarily choose one of the two cap screw commodity codes, and the specification writer must manually add the second cap screw by use of the bolt option.

  • If the PDS translator encounters a through-bolted fitting requiring a complete substitution of cap screws; and the through-bolted fitting implies two different cap screw commodity codes in PDS based on two different size ranges, only one cap screw record will be created in the Bolt Selection Filter. The PDS Translator will arbitrarily choose one of the two cap screw commodity codes, and the specification writer must manually add the second cap screw by use of a different size range.

  • For the CL51 through CL56 rating items, the rating must be changed to a schedule/thickness value.

  • For reinforcing pads using a geometry standard of 6 (or other), the value can be removed from the PipingCommodityMatlControlData worksheet in column P. This record is not required for Smart 3D.

  • Items using any user-defined or customized geometry standards require that the values are added to the AllCodelists workbook.

  • The size-dependent commodity codes flag refers only to the PCD format, and not to the Project Administrator option in PDS. Set this option to YES only if you have ALL individual NPD values in the PCD (for example, when you have all NPD values for piping commodities from 2" to 6"). The software includes a worksheet for size-dependent codes from pdtable_212. You must enter sizedep.txt (or other file name) on the File Names worksheet in the appropriate option row. This file is a report of size-dependent commodity codes.

  • The translation process does not convert PDS codelists.

  • The process uses two Smart 3D codelists that relate to dimensional data. The delivered codelist file for Smart 3D is AllCodeLists.xls.