5 replies to this topic

[Halflight]

Hi,

 

When I fill a process data-sheet of on-off valves, the required data is a little bit different from the project by project.

But sometimes, I can't understand why every category on the data-sheet is needed.

 

Necessary data for the design of on-off valve I think is below :

 

Max Shut-off Pressure

Design Pressure

Design Temperature

Piping Material Spec

Connected Line Size (valve size shall be same as line size)

Valve Type

Additional Process Data (Toxic, Acid, Containing Solid, etc.)

 

On the contrary, unnecessary data for the design of on-off valve I think is below :

 

Density

Specific Heat Ratid (Cp/Cv)

Viscosity

Operating Pressure

Operating Temperature

Flow Rate

Compressibility Factor, Z

Molecular Weight

etc.

 

I think fluid properties are not required to design on-off valves, but if they are needed, tell me some codes or standards like ISA 75.01.

I want to know how that property applies.

 

Thank you.

[Pilesar]

Valve data sheets, rotating equipment data sheets, heat exchanger data sheets are often designed to try to cover the most common specs. You may not need to fill every blank on a form. Use your engineering judgment and communicate what the valve designer needs. If the designer has more info than needed, there is little harm.

[Bobby Strain]

You should be extracting process data from your process simulator if you have one. Do you have instrument engineers?

 

Bobby

[gegio1960]

halflight, I agree with you.

you just missed one (very important) item: the failure position.

that was the standard practice adopted by the major companies I've worked for.

moreover, depending on the various disciplines responsibilities, other data you listed should be omitted on the process specification (typically the ones under piping department responsibility).

[Halflight]

You should be extracting process data from your process simulator if you have one. Do you have instrument engineers?

 

Bobby

 

Extracting process data is not much difficult job, but it waste time and make delay the project. I was just curious for is there an any code or standard that I can acceptable.

 

Halflight

Edited by Halflight, 08 February 2023 - 11:24 AM.

[Halflight]

halflight, I agree with you.

you just missed one (very important) item: the failure position.

that was the standard practice adopted by the major companies I've worked for.

moreover, depending on the various disciplines responsibilities, other data you listed should be omitted on the process specification (typically the ones under piping department responsibility).

 

Thanks for advice, I just forgot that while posting this.

By the way, our company doesn't have clear R&R, so responsibility changes from project by project to client wanted.

 

Halflight