Category
|
Sheet Name
|
Validation
|
Specification Details
|
PipingMaterialsClassData
|
-
Attributes of PipingMateriaClassData can be mapped and imported in the code list mappings
screen.
-
Code list sheet if imported to SRD table and if the table is present in specification
rule for that particulr spec, the data is imported to specification details in spec
cover page. Otherwise the code list can be imported to template.
The specification rule must correspond to the specification to which the data is being
imported.
|
Specification Header Geometrics
|
ServiceLimits
|
-
PipingMaterialClassData sheet must be loaded along with all the above validations.
-
ServiceLimits sheet must be loaded.
-
PipeNominalDiameters must be loaded to obtain NPD values and units.
-
SpecName, Temperature, NominalPipingDiameterTo, and Pressure must be available in
ServiceLimits sheet
-
The attributes Temparature, NominalPipingDiameterTo, and Pressure from the service
limits sheet must be mapped to corresponding Smart Reference Data attributes in the
Import Geometrics screen.
-
The Service limit must be mapped to a Smart Reference Data rating geometric.
-
Smart Reference Data rating geometric must have only temperature, pressure, and NominalPipingDiameterTo
attributes and these attributes must be included as inputs.
-
The data width value for Smart Reference Data rating geometric attributes (temperature,
pressure, and NominalPipingDiameterTo) must be greater than or equal to the width
of the corresponding data in servicelimits sheet.
|
PipeNominalDiameters
|
|
Schedules
|
-
ShortCodeHierarchyRule must be loaded with shortcodes under "Pipes" ShortCodeHierarchyType.
-
PipingCommodityFilter with the above short codes and schedules must be loaded to the
staging area.
-
PipeNominalDiameters sheet must be loaded and the sheet must contain nominal diameters
for the selected specification.
-
ScheduleThickness Code list sheet must be loaded to validate schedule.
-
PipeStock sheet should be loaded to fetch schedules for ASME and other standards.
|
PipeBranch
|
-
PipeBranch sheet with data for the selected specification must be loaded to view validations.
-
PipingCommodityFilter sheet should be loaded to get the Industry Commodity Code (ICC)
for the short codes from PipeBranch.
-
All the ICCs should be available in Smart Reference Data (associated with CC) to get
group and part combination for the ShortCode.
-
You must assign default group and part to the Smart Reference Data short code of
"ReinforcingWeld". This is because, ICC will not be found in PCF for "ReinforcingWeld"
short code. Hence, group and part are fetched from the Parts To Short Codes grid.
|
Nominal Reducers in PCF
|
The Smart 3D Short Code mapping must be done at the project or product group level.
|
Specification Notes
|
Standard Notes Data
|
|
Specification Items
|
Spec items from PCF
|
-
All codelist sheets of codelist attributes loaded to staging area can be imported
to spec items or templates depending on the attribute mapping in import geometric
screen. Example: Selection basis that has codelist as its value of the PCF sheet.
-
ShortCodeHierarchy rule and PipeNominal diameters sheets must be loaded.
-
CommodityCode from PCF sheet must be available in Smart Reference Data as ICC/CCC
( Go to MapInterfaceCCs/CCCs form or CommodityMappings tab of Smart 3D Import screen).
-
Short code of PCF should be mapped to Project or Product Group Shortcode.
-
The mapped Smart Reference Data CommodityCode of CC from PCF must have Geometrics
associated with it.
-
The Smart 3D Commodity Code available in PipingCommodityFilter sheet with a short
code mapped to a SRD Commodity Code should either have same Smart 3D short code or
no Smart 3D short code mapped at part level.
-
The Smart 3D Commodity Code available in PipingCommodityFilter sheet with a short
code mapped to a SRD Commodity Code should either have same Smart 3D short code or
no Smart 3D short code mapped at spec item level.
-
While exporting the imported data, PipingCommodityFilter (PCF) sheet may have multiple
short codes with same commodity code. If there are multiple short codes mapped at
part level, then duplicates may get generated in the exported sheet. To avoid exporting
duplicate data, you can do one of the following:
-
If in a Project, delete the short codes assigned at part level.
-
If in a Product Group, you may not delete the short code. Therefore, map the short
codes at spec item level.
Ideally, if one commodity code with 2 different short codes is available in the spec,
then you should not map Smart 3D short codes for that commodity code at part level.
|
Specification item Notes
|
Spec Item Notes in PCF
|
-
Note Purpose and Standard Notes Data sheets must be loaded in the staging area.
-
The notes of PCF sheet must be mapped to the Smart Reference Data notes of SPEC note
type in staging area or the note should exist with the same name in Smart Reference
Data.
|
Specification Templates
|
AllowablePipingMaterialsClass
Permissible Taps
CorrosionAllowance
MinimumPipeLengthRulePerSpec
MinPipeLengthPurchasePerSpec
ThicknessDataRule
BendAngles
WeldClearance
OutsideSurfaceTreatment
InsideSurfaceTreatment
PortAlignmentPerSpec
PipeTakedownParts
Bolt Selection Filter
Nut Selection Filter
Washer Selection Filter
Gasket Selection Filter
|
-
PipingMaterialClassData sheet must be loaded along with all the related validations.
-
The specification rule sheet corresponding to the selected specification, must be
loaded to the staging area.
-
If the spec rule sheet contains any code list attributes:
-
If codelist attribute is present in the staging area, codelist sheet must be loaded.
-
Project default <ZI_SP3D_CT> must be set for SP3D code list template, in the project defaults screen.
-
If codelist attribute is present and project default is set as <ZI_SP3D_CT>, codelist sheet data must be available in the code list template.
-
If all the above conditions (a, b, and c) are met, spec rule sheet code list number
must be available in the code list sheet in the template.
-
The specification rule sheet corresponding to the selected specification, must be
loaded to the staging area.
|
Specification Item Geometrics
|
Spec Item Geometrics in PCF
|
-
PipeNominalDiameters sheet must be loaded with all the required attributes (specname,Npd,
NpdUnitType) in the datatable configuration.
-
Npd and NpdUnitType attributes in the PipeNominalDIameter sheet must have valid values.
Npd must have numeric value.
-
The following attributes in PCF must have valid numeric values:
-
The geometric that is mapped to Smart 3D component must have all the required attributes.
-
Worksheets shortcodehierarchyrule, schedulethickness, and pipestock must be loaded
into the staging area.
|