Additional Information - Intergraph Smart Reference Data Standard Database - Version 12.4 - Help - Hexagon

General Information

• SDB has provided weight per unit length values for pipe stock. Density values have been deleted from SDB because this value is not required by the Smart 3D software. This is to inform users to provide only weight per unit length values wherever applicable.

• As a part of the addition of the European Norms standard into SDB, we have added only generic data for EN 1092-2 flanges. This is because the face to face values for the flanges are not specified in the standard. There is no geometric data available for this standard.

• Updated the ASME 16.11 female generic data to provide typical Hub Thickness value. The ASME 16.11 standard does not provide the dimension value for Hub Thickness. The reason is that the hub thickness is based on the manufacturer and manufacturing process. It changes from one manufacturer to another. We have considered the socket depth value as typical hub thickness value. This has been updated in SDB. "PipingGenericDataFemale" to create the Hub cylinder on the port side while placing the symbol in S3D for female ends. Users can change this value as required.

• The body OD defined in the SDB is the same as piping OD. The data provided in ‘ten spec’ is sample data: it’s not standard data. Regarding socket diameter, this data is given by the standard ASME B16.11 or others. So, it will be the same in ten spec and SDB, but body OD is not provided anywhere in the standards or manufacturing catalogs. As per the Smart 3D design document, the body OD can be defined either in the part class or female/bolted end generic data. If it is not defined in both places, the piping OD from plain piping generic data will be retrieved by the symbol code to place the cylinder. The actual body OD of the piping parts is completely different than what is defined in ten spec or SDB. The body OD will always be greater than the socket OD. The data for the body OD is not given by any manufacturer. Customers may get it from their own manufacturers and replace it with SDB data, or else they can change the body OD in their DB to be like the ten-spec data.

• For all the ASME B 16.9 fittings, SDB has provided the end standard mapping 26 (ASME B 36.10). However, customers are requested to change the end standard mapping for ASME 16.9 fittings when they are creating stainless steel parts/Specifications to the end standard value 157 (ASME B 36.19). On the Attribute Mappings screen present under Integration > Smart 3D > Smart 3D Configuration, under the Component Mappings Tab, provide the mappings using the commodity code level or using the spec level.

• Currently, SDB uses PDB 15 for Weld Neck flange where FTF excludes RF dimension, and RF dimension is provided in piping generic data bolted. When it is PDB 20, the FTF dimension includes the RF dimension.

• The GUIDs delivered in SDB are based on the GUIDs available in the S3D OOTB catalog and Smart Support workbooks with respect to each part class in SDB templates.

• Zero (0) schedule values are deleted from SDB OOTB geometric tables referred to MSS SP-97. However, same values are not deleted from migrated database. Users need to delete these values as per their requirement.

• In SDB 2018, Dimensional data related to "CAP" commodity part has been updated with schedule values as per ASME B16.9. Users need to delete Non-Schedule values as per their requirement.

• In SDB, below listed duplicate interface attributes are deleted from OOTB SDB based on the metadata required for S3D. However, these values are not deleted from a migrated database. Users need to delete these values as per their requirement.

  Interface Name	Deleted Attribute	Valid Attribute
  IJDynamicPipePort1	NPDUnitType1	NpdUnitType1
  IJDynamicPipePort2	NPDUnitType2	NpdUnitType2
  IJUA2L	b	B
  IJUAHvacDimensions	FLANGEWIDTH	FlangeWidth
  IStructFlangedSectionDimensions	D	d

• Equal Tee Commodity Codes referring to EN Standards which were mapped to Sheet TEE are now mapped to TEEPDB194 under SDB_ METRIC_MAPPING.

• SDB has provided schedules for higher rating SW Flanges as per the industry standards.

• SDB has the ability to export imperial specs with metric unit and vice versa using new general configuration settings. The part data will always be exported in the native units in which it was added. Only the data exported in specification sheets will get converted into alternate units.

• SDB has provided the ability to export the PipeBranch sheet for specs which have more than one branch table mapped in spec header. As part of this, SDB sample piping specification "1CS1S0A" has been defined with Multiple Branch tables (45 and 90 deg.).

• Users need to place "OutsideDiameterForSymbolGraphics.xml" in their shared content ([shared content]/xml) folder to place components with NPD of 1.5 inch and below. This xml will provide pipe OD values for the components with female/male ends. This xml is available on Smart Support Piping and Instrumentation Zip file.

• As part of moving generic data from templates to geometric table, separate tables are created for storing imperial and metric based data. As the outputs for the Piping Generic Data Bolted are more than 15, two geometric tables have been created for each unit system.

• Updated the commodity codes that refer to retired valve body PDBs with best practice valve body PDBs.

  • Updated the geometric data for new attributes that are mandatory for the best practice valve body PDBs.

  • Created the part data for the best practice valve operators for the corresponding retired valve operators in the template data.

  • Updated the comment "Eventually to be retired" for the retired part classes in the Help Text string. The data for retired valve operators still exists in the template.

  • Updated the item mapping, transfer types, and sheet configurations for the new best practice part class sheets.

  • Updated the item mapping for the piping commodity material control data sheet, so that the valve body refers to the best practice valve operator parts.

  • Updated the valve operator part number and valve operator type to refer to the best practice valve operator.

  • Updated the comment "Eventually to be retired" for the 292 retired part class sheets in the Help Text string, which refer to the retired symbols; however, no commodity group and parts are mapped to any of the retired part classes.

• All the duplicate and ‘Manual’ assigned geometric relations in SDB are deleted and assigned the commodity codes with appropriate geometric tables by updating commodity geometric rules.

• All the Symbol DLL’s in SDB are updated with the latest versions of DLL’s that are available on smart support.

• All the codelists in SDB are updated to be in line with the smart support select list workbooks which is the master source for S3D codelists.

• Materials data in SDB is updated with reference to the latest design standards (ASME B31.1 for Power Piping & ASME B31.3 for Process Piping).

• All the mandatory attributes in S3D configurations in SDB Integration are marked as mandatory in line with S3D Monikers. This will provide a check for the users that they aren’t missing any of the mandatory column values that are mandatory in S3D.

• A sample commodity code is created for Nipple part (BJ) under Pipe (P) group and the same is added in the Sample Power piping specification (1CS1S0A).

• SDB Commodity Attribute "P_Alias" table details "ZZZ" is consistently updated with Description "-"in all the Groups and P_Alias_trim was updated to have the description as ",-". Now, P_Alias_Trim will be visible in Commodity Descriptions, whereas P_Alias shall not be used in any of the Commodity Codes and thus the same are disused. Also, as the table details "ZZZ" has no value with reference to description, same has been deleted from all the applicable Commodity Codes.

COG Data

SDB has added COG data. Below are the guidelines followed for calculating the COG data:

• COG data added in SDB was computed based on the Smart 3D symbol PDBs as we have not found COG data in any of the manufacturing catalogs or standards.

• In SDB, we have added COG data for US commodity codes, for all PIP Specifications, GB, and EN standards data. We will add COG data for other components in future releases.

• SDB computed the COG data with respect to the Smart 3D symbol origin.

• SDB considered the components as a solid body (that is, we have not considered the schedules).

• SDB added COG data for all six attributes defined in Smart 3D, that is, DRYCOGX, DRYCOGY, DRYCOGZ, WATERCOGX, WATERCOGY, and WATERCOGZ. SDB considered DRYCOGX and WATERCOGX to be the same.

• In addition to the above, six more attributes have been added: DRYCOGX1, DRYCOGY1, DRYCOGZ1, WATERCOGX1, WATERCOGY1, and WATERCOGZ1. Customers can use these attributes to add their own COG data. When a customer adds data to these six attributes, their data overrides the SDB delivered data.

• For the following part class sheets, SDB has considered COG as the symbol origin: BackupRingPDB3186, ClampPDB2385, Coupling, CouplingPDB2107, CouplingPDB420, RedCouplingPDB2107, Reinforcing Weld, and Valve Spacer, Full Circle Reinforcement, Eccentric Reducer, EccReducerPDB4141, Eccentric Swage, valves, and operators.

• This COG data is applicable to only Smart 3D because the calculations are based on the Smart 3D symbol PDBs.

Weight Data

• SDB has added weight data for US standards and US manufacturing parts in SDB based on the available manufacturing catalogs.

  Because SDB has not found weight data for all the parts, weight data is added for only a few sizes based on the manufacturing catalogs.

• SDB has not included the manufacturer name in the weight tables.

• Some of the weight tables are commented as uncertified data because the source information is not known.

• SDB will include the missing weight data in future releases.

Sample Thickness Data Rule

SDB has added the sample thickness data for the calculated wall thickness PIP Specifications on Templates under the ThicknessDataRule sheet as a starting point for customers. Customers need to modify this data based on their project requirements.

The minimum thickness and requirement thicknesses are assumed while preferred schedules are given from ASME standards B36.10/36.10M and 36.19/36.19M. For Piping specifications where the Calculated Wall Thickness exceeds the values as per ASME B36.10 are provided with de-rated pressure temperature Values for required size ranges. These Specifications are Included up to maximum Wall Thickness values available as per ASME B36.10.

For Stainless Steel (SS) Piping specifications with sizes specified as Calculated Wall Thickness, details are considered as per ASME B36.19.

If the Calculated Wall Thickness Value does not exist in ASME B36.19, necessary details shall be considered from ASME B36.10 and all applicable Pipe Commodity Codes with SS Material grade referred with this change in PIP specs are updated with appropriate Dimensional Details.

For 6CS1S01, 6CA1S01, 6CB1S01, 6CB1S02, 15CM1S01, 15CL1S01, 15CK1S01, 15SD0S01, 15SJ0S01 piping classes, pipe stock placement will fail at Max PT condition. This is because they require higher schedules/wall thickness that are not available in the standard itself. However, all the Components defined in SDB will be 100% placed at De-rated condition for these piping classes. The list of De-rated pressure temperature combinations is provided below.

For 9SK0S01, 9SK1S01, 5SK0S01, 15SK1S01 piping classes, pipe stock placement will fail at above 1000°F condition. This is because they require higher schedules/wall thickness that are not available in the standard itself. However, all the Components defined in SDB will be 100% placed at up to 1000°F condition for these piping classes.

Standard PDF Pipe Spec Report in SDB

The spec report menu Reports has been added to the Smart Reference Data-Standard Database menu. The report is included in the SDB build for existing customers. The SDB migration will update all Smart Reference Data menu related settings required for the new report for existing customers.

User must copy the "S50RSDB.rdf" file from the database server (<SDB Install Folder> \Reports) to the application server (<Smart Materials Install Folder \rep\) to extract these reports.

Also, users must specify a valid value for the report server name in the application server specific settings under A 60.04 DBA Settings, and it should be active as shown below.

Export SDB Data referring to DOTNET or COM symbols

The Smart 3D Interface is enabled users to produce SDB Specifications either with .Net or COM (VB6) Symbol ProgID based exports which can be loaded into Smart 3D.

Mapping between .Net and COM symbols needs to be provided in SRD > Geometric Management > Other Geometrics > S3D_SYMBOL_MAPS.

Selection of Symbol Basis option is defined in General Configurations enabling users to export SDB PIP Specifications either with Dot Net or COM Symbol ProgIDs.

Smart Reference Data currently does not have the ability to export DLL related to Valve Operators. This will be addressed independently in a future release.

New vs Old Olet Design Implementation in SDB

In SDB olets were defined the same way as other reducing fittings, that are based on both header and branch size with Header Schedule.

But as the olets are available based on the branch size and Branch Schedule, SDB has changed the way data is defined for these. As per the new design, Header schedule is deleted to define the olets in SDB.

Below is a comparison of the new versus old design of the olet implementation in SDB.

New Implementation of the Olet Design

All existing olets commodity codes with parts like EBL - Elbolet, SOC - Sockolet under the group "O" - Forged Fitting and Parts Like BPT – Buttweld Pipet, WEL Weldolet under group B – Buttweld Fittings with Beveled End (BE) branch connection are updated with new object parameter to exclude Header Schedule (SCH1)

Design change with new object parameter:

Design change at Commodity Code Level:

Design Change at Ident level:

All existing Olet Commodity Codes with Socket Welded End (SWE)/ Female Threaded End (FTE) branch connection are updated with object parameter to contain only Header Size (NPS1) and Branch Size (NPS2)

Design change at Commodity Code Level:

Design Change at Ident level:

On the Spec Items grid, Olets are specified based on the branch size and header size as per the new design.

Olet design implemented in SDB 2012 until SDB 2018 are obsolete with this new design.

Old Implementation of Olet Design in SDB

The old design for existing parts (EBL - Elbolet, SOC - Sockolet) were under the group (O - Forged Fittings) and Parts Like BPT – Buttweld Pipet, WEL - Weldolet under group B – Buttweld Fittings with BE branch connection.

Object parameter details for Parts with BE branch connection:

Commodity Codes with Object parameters:

Ident Details:

Design of object parameter details for Parts with SWE/FTE branch connection

Commodity Codes with Object parameters: