Zetav and Verif tools

  1. About
  2. Download
  3. Usage
  4. Configuration
  5. Input Format
  6. Contact
  7. Acknowledgement

About

Zetav

Zetav is a tool for verification of systems specified in RT-Logic language.

Verif

Verif is a tool for verification and computation trace analysis of systems described using the Modechart formalism. It can also generate a set of restricted RT-Logic formulae from a Modechart specification which can be used in Zetav.

Download

Zetav

Windows (32-bit)

Verif

Multi-platform (Java needed)
General Rail Road Crossing example

Usage

Zetav

With default configuration file write the system specification (SP) to the sp-formulas.in file and the checked property (security assertion, SA) to the sa-formulas.in file. Launch zetav-verifier.exe to begin the verification.

Verif

With the default configuration example files and outputs are load/stored to archive root directory. But using file-browser you are free to select any needed location. To begin launch run.bat (windows) or run.sh (linux / unix). Select Modechart designer and create Modechart model or load it from file.

Module 3 Process Piping Hydraulics Sizing And Pressure Rating Pdf _best_ Jun 2026

= Weld joint strength reduction factor (relevant at high temperatures)

: Systems must meet specific design codes (e.g., ASME B31.3 for process plants) which define requirements for materials, fabrication, and testing.

This diagram illustrates how the three core disciplines of process piping design are integrated in a real-world engineering workflow:

) for straight pipe under internal pressure is calculated using the ASME B31.3 formula: = Weld joint strength reduction factor (relevant at

In piping design, we convert pressure drops into (meters or feet of fluid column).

Calculate total ΔP (friction + minor + static).

Industrial plants rely on standard velocity and pressure drop limits to prevent issues like erosion, noise, water hammer, and high energy costs. Fluid Type Recommended Velocity Range (m/s) Target Pressure Drop (bar/100m) 0.5 – 1.2 0.05 – 0.15 Water (Pump Discharge) 1.5 – 2.5 0.4 – 1.0 Steam (Saturated) 0.1 – 0.5 Steam (Superheated) 0.2 – 0.8 Gas / Vapor (Low Pressure) 0.01 – 0.1 Gas / Vapor (High Pressure) 0.1 – 0.5 Sizing Criteria for Single-Phase Liquid Lines Industrial plants rely on standard velocity and pressure

You can find detailed technical guidance in these publicly available documents:

By integrating these three core elements, engineers can design piping systems that are not only safe and reliable but also optimized for economic performance, ensuring the smooth and efficient operation of process plants for years to come.

Once the hydraulic diameter is known, the pipe wall thickness must be determined to safely contain the internal design pressure. ASME B31.3 Codes for Process Piping ASME B31

is an empirical constant (typically between 100 and 125 for continuous service). 4. Pipe Pressure Rating and Wall Thickness Calculation

wall thickness tolerance. The calculated thickness must be divided by 0.8750.875 to ensure compliance with the absolute minimum limits. 5. Engineering Best Practices and Optimization

Input Format

Zetav

The Zetav verifier expects the input RRTL formulae to be in the following form:

<rrtlformula>    : <formula> [ CONNECTIVE <formula> ] ...

<formula>        : <predicate> | NOT <formula> | <quantifiedvars> <formula> | ( <formula> )

<predicate>      : <function> PRED_SYMB <function>

<function>       : <function> FUNC_SYMB <function> | @( ACTION_TYPE ACTION , term ) | CONSTANT

<quantifiedvars> : QUANTIFIER VARIABLE [ QUANTIFIER VARIABLE ] ...
Where predicate symbols (PRED_SYMB) could be inequality operators <, =<, =, >=, >, function symbols (FUNC_SYMB) could be basic + and - operators, action type (ACTION_TYPE) could be starting action (^), stop action ($), transition action (%) and external action (#). Quantifier symbols (QUANTIFIER) could be either an universal quantifier (forall, V) or an existential quantifier (exists, E). Connectives (CONNECTIVE) could be conjunction (and, &, /\), disjunction (or, |, \/), or implication (imply, ->). All variables (VARIABLE) must start with a lower case letter and all actions (ACTION) with an upper case letter. Constants (CONSTANT) could be positive or negative number. RRTL formulae in the input file must be separated using semicolon (;).

An example could look like this:
V t V u (
  ( @(% TrainApproach, t) + 45 =< @(% Crossing, u) /\
    @(% Crossing, u) < @(% TrainApproach, t) + 60
  )
  ->
  ( @($ Downgate, t) =< @(% Crossing, u) /\
    @(% Crossing, u) =< @($ Downgate, t) + 45
  )
)

Verif

Verif tool does not deal with direct input. Examples are load from files with extension MCH. Those files are in XML and describes model modes structure and transition between modes. There is no need to directly modify those files. But in some cases it is possible to make some small changes manualy or generate Modechart models in another tool.

Contact

If you have further questions, do not hesitate to contact authors ( Jan Fiedor and Marek Gach ).

Acknowledgement

This work is supported by the Czech Science Foundation (projects GD102/09/H042 and P103/10/0306), the Czech Ministry of Education (projects COST OC10009 and MSM 0021630528), the European Commission (project IC0901), and the Brno University of Technology (project FIT-S-10-1).