Create Specification Rules
A specification header displays descriptive information. Most of the information, such as general material, can be assigned by Smart Materials table details (identical to commodity code tables). The specification rule enables any table type defined on Tables to be used for this purpose.
Specification Rule
Users can create New Specification rules using the SRD > Spec > Spec Editor > Specification Rules screen in Smart Reference Data Plus by following these steps:
-
Click Add to add new Spec Rule.
-
In the Specification Rule properties window, enter spec rule name and other required details.
-
Click Save to save the Specification Rule.
Specification Rule Tables
-
Double-click Spec Rule to view the Specification Rule Tables window.
-
Click in the Specification Rule Tables grid. Here user can define the Table names which are required to define the specification details. Users can select the level (Spec Header or Spec Item) at which these details should be shown for a specification.
-
Click Save to save the Specification Rule Tables to a Spec rule.
Only the tables assigned to a specification header level can be used later for detailed descriptions of the specification at the specification header level. Users can assign table details to each specification, based upon the table’s service, rating class, temperature limit, corrosion allowance, material type, design code, stress relief, and examination.
Specification Rule Attributes
Users can define custom attributes to a spec rule so that they can define custom properties for a spec either at the spec item level or the spec header level. To define these custom attributes, follow the steps given below:
-
Double-click Spec Rule to view the Specification Rule Attributes window.
-
Click in the Specification Rule Attributes grid. Here users can define the custom attributes as per requirement either at Spec Header level or Spec Item level for a specification.
-
Click Save to save the Specification Rule Attributes to a Spec rule.
Create Specification Types
The specification type is used to categorize and organize the specifications. The specification types can be used for any kind of organization; for example, based on company departments, plant types, main specification material, media, or other information.
Examples are: Specifications used for the Bio Pharma Industry, Specifications used for the Power Industry, and so on.
Each specification type is assigned to a specification rule. At least one rule must exist before a specification type can be created.
Users can create New Specification rules using the SRD > Spec > Spec Editor > Specification Types/Spec Header/Short Codes/Spec Item screen in Smart Reference Data Plus by following these steps:
-
Click Add to add a new Spec Type.
-
In the Specification Type properties window, type the Spec Type name, Spec Rule, and other required details.
-
Click Save to save the Specification Type.
Specification Management
In the spec cover page, the Specification Code field is a free format code field. This field is filled by most companies with meaningful codes such as the nominal pressure, the main material group, and a sequential number.
In the first block, the Spec Header Description, Spec Type Description, and Variable Attributes fields are available. The first two fields allow the insertion or viewing of the appropriate descriptions. The third field, Variable Attributes, allows the insertion or viewing of variable attributes that were previously defined for this specification rule on the Specification rules screen.
The second block of the Spec editor cover page maintains the following:
Specification Header Geometrics:
-
Special geometric tables are assigned to the specification. Filter tables are used to define the wall thickness information for the specification. Branch tables and other tables are used for additional documentation issues.
-
The nominal reducer filter geometric can be defined in SRD > Component Manager > Geometric Management > Nominal Reducers. The short code RED% will take care of the eccentric reducer and the concentric reducer. It may be required to have a separate geometric for reducers and swages. The short code to be used with swages is SWG%, which will be for both eccentric and concentric swages.
-
The branch tables can be defined in SRD > Component Manager > Geometric Management > Branches. If the specification needs to have a separate branch table for the 45-degree branch and 90-degree branch, the short codes 45% and 90% can be used with separate branch tables, which are unique for each degree.
-
The nominal sizes can be defined in SRD > Component Manager > Geometric Management > Nominal Sizes/Nominal Size Details. Other geometrics as applicable for a specific piping specification can also be created.
The geometrics are linked to a specific specification code. The spec header geometrics can be linked to specific short codes or all the short codes by using the wildcard character "%". The free wildcard "%" entry should not be used for branch tables (unless it is 45% or 90%). -
Also, other dependent data required for the interface to design systems is added. Care should be taken not to select the "filter" option on the screen.
Specification Details
The Specification Details section allows detailed information for all pre-selected tables to be assigned based on a specification rule.
Temperature-Pressure Table
The Temperature Pressure tab allows the definition of limits for pressure/temperature pairs.
Create/Add Specification Items
Users can add specification items to a spec by following these steps:
-
Click the Components tab in spec Editor window.
-
Click in the Specification Items grid to type all the required details like short code, group, part, option code, commodity code, MULTISIZEOPTION, size ranges, spec., item geometric filter, and specification item notes to add a spec item to the specification.
-
Click Save to save the Specification item to the spec.
In the MULTISIZEOPTION column, users can enter a string to represent an optional selection for multi-sized fittings when the first size and the second size are inadequate. In SDB, MULTISIZEOPTION values are added in the 3SD0J02-C and 1SD0J01-C Specifications.
Create/Add Filter Geometrics for Idents
The aim of a piping specification is to define a list of idents that are uniquely defined over the nominal diameter sizes and the schedule/thickness, based on specification items.
The filter table represents the applicable schedule for all sizes. A typical best practice is to create filter table codes in accordance with the specification code to make maintenance easier. Depending upon the situation, the filter geometrics at the specification header level or the specification item level are deployed.
It is very important that all specification items to be filtered by the specification header geometric filter table. Have the Geometric 1 field on the specification item level EMPTY. This rule defines an exception filter table for any specification item by simply assigning a different filter table to the specification item record.
The option in the spec items grid displays the idents that are present for the selected Spec item.
Missing idents can be seen on this window with the use of option.
Special Instructions for Jacketed Specifications
Jacketed Specifications are created as two individual Specifications. The parts related to core piping are included in the core spec, and parts related to the jacket and jumpers are included in the jacket spec.
SDB includes two jacketed specifications 1SD0J01 and 3SD0J02 created as 1SD0J01-C, 1SD0J01-J, 3SD0J01-C, and 3SD0J01-J, for core and jacket specifications respectively. The SDB naming convention is a "-C" suffix for a core spec and "-J" for a jacket spec.
The core spec includes the parts used in the core piping, and the jacketed components are jacketed valves and insert flanges.
The jacketed components require the multi-size option to be specified on the Spec Items grid under the Spec Editor.
Spec header geometrics tables, service limits, and specification details are normally different for core and jacket Specifications in a human spec. They should be created as per human spec in the respective Specifications.