Professional Documents
Culture Documents
Dokumen - Tips Phast Risk Release Notes
Dokumen - Tips Phast Risk Release Notes
DNV SOFTWARE
Palace House, 3 Cathedral Street, London SE19DE, UK
http://www.dnv.com/software
Workflow for transferring data from Phast Risk v6.7 into Extended
Reporting
In order to use the Extended Reporting Extension with v6.7 it is necessary to transfer risk data from
Phast Risk to Extended Reporting. The program uses a database and generates database files. There is
no need to get involved in the detail of how the database works unless larger more complex studies are
required.
Default Mode
Phast Risk v6.7 is designed by default to make transfer of data between Phast Risk and Extended
Reporting happen without any further intervention or specialist knowledge from the user.
Default mode is used for small to medium sized studies where long term storage of the data is not
required and where the generation of Risk data takes a relatively small amount of time.
The workflow is simple:
• Select Run Rows and calculate Consequence and Risk.
• When Risk results have been created the sigma button will become activated
• Click on the sigma button and Extended Risk Reporting will open using the current risk
results
Phast Risk v6.7 Release Notes 5
• If after examining the risk results in Extended Reporting you wish to edit the input data in the
study and re-run the Consequence and Risk calculations you can click the sigma button again
to generate the new risk results database. When you click the sigma button Phast Risk will
offer you the option to Overwrite previous data, Save as or Cancel the database creation. If
you overwrite the results database, previous results are lost. If you choose to Save as you can
rename the new risk database file and therefore store both the old and new results for analysis.
If you leave extended reporting open, then return to Phast Risk, make further edits and then click the
sigma button you are effectively trying to open a second instance of the Extended Reporting tool.
Because the first instance of Extended Reporting is reading from the original data file then Phast Risk
will not allow you to overwrite the original data file whilst it is in use.
Advanced Mode
Working in advanced mode may be necessary to support working with larger, more complex studies
which are time consuming to run. There are methods for selectively running calculations of only some
aspects of the study. This reduces storage needs and calculation times and methods for automatically
saving the data at the end of lengthy calculation runs. This way, the program can be left to perform
calculations and data saving unattended.
Phast Risk v6.7 Release Notes 6
• Set the file name for the data using the File field (as shown above), or by browsing to the
desired location using the ‘…’ button.
• Check ‘Write Extended Risk Results after Risk Calculations’
• Click OK on the Risk Preferences dialog and choose Run Models to begin the calculation and
data writing process
If you want to Launch Extended Reporting so that it is ready for use at the end of the calculation and
data writing run, then check ‘Launch Extended Risk Reporting’
Please note it is not possible to save a data file to a compressed drive, or networked drive or to a drive
where the current user of the machine does not have the necessary read/write permissions.
Please be aware that if you intend to save variations and versions that it is necessary to reset the file
name for each MDF file that you wish to Save. The file name can be defined via
Options ► Preferences ► Risk ► Extended Risk Reporting (tab)
It is not possible to double click on an MDF file to open it. It must be opened using the File menu of
Extended Reporting. The datafile is transferrable if the installed version of SQL Server on the original
PC is the same as the installed version on the destination PC. The default version of SQL Server
installed with Phast Risk v6.7 is SQL Sever Express 2008 R1
The maximum size of the datafile is finite and determined by the particular version of SQL Server
which is installed with Phast Risk. If the size of your study’s database exceeds the limit set on it then
the data writing will fail for the current run row and there will be incomplete data, accompanied by a
warning.
It is near impossible to reliably predict how large a data file will become ahead of performing the
calculations. However, we have produced a set of example studies which will give approximate sizes
of data files when using various configurations of run rows, models, weathers, etc.
These should help in the planning of a study which might exceed the data limit.
Whilst it is always preferable to deal with the problems of large amounts of data through design there
may be some instances where you find it necessary to produce extremely large studies which exceed
or nearly exceed the 4GB storage constraints imposed by the SQL Server Express R1 version.
There are a number of steps which can be taken to maximise storage capacity and to create smaller
subsets of the risk data, details of each option follow.
• Upgrading SQL Server Version: It is possible to increase the storage capacity of the data files
by upgrading the SQL Server version
• Selecting a subset of Run Rows
• Using preferences to limit results produced: It is possible to set preferences so that only
particular aspects of the risk calculations generate results. For example. It is possible to switch
off all societal risk results and only produce results for individual risk.
• Using preferences to limit which precompiled tables are produced: Similarly, by default, a
number of precompiled views are created by the data writing process. By switching these off
space may be saved at the expense of speed of access in Extended Reporting.
In this way you can use the Extended Reporting to examine the details of the risk results in stages
rather than having to write the entire study results to a single, large database. This will keep the
database size down.
Sometimes it is necessary to write results from every run row to the database: for instance to obtain
combined contours for the whole study or an overall FN curve. For very large studies, if all the risk
results are written to the database at one time then this operation may exceed the allowed database size
so a reduced set of risk results must be obtained by running the risk again to obtain only these results.
This is explained in the next section.
Phast Risk v6.7 Release Notes 9
For example, if you have a study which you know will exceed the data file size if all risk results were
generated then it would still be possible to get an overview of risk across the entire study by changing
the ‘Calculation scheme’ to ‘Contours & F/N Curve only’. This effectively tells the calculation run
to not generate data for ‘Risk Ranking Points’, ‘Risk Ranking Results’ and ‘Building Category
Results’.
Another example would be, if you wanted to generate an overview of ‘Risk Ranking Points’ for an
entire, large study then you could switch off results generation for all but ‘Risk Ranking Points’.
The technique of limiting the results produced and saved by models can be combined with other
techniques for limiting the size of the data files for very large studies.
Pre-compiled results preparation can also be turned off if you are not interested in a particular type of
results in order to reduce the data file size.
There are two types of precompiled data tables: Summary tables and Details.
Summary tables
• Risk Dashboard
• RIByN (Risk Integral By Number of statistical fatalities), Bar Chart and Pie Chart
• Category PLL/FAR (Potential Loss of Life/Fatal Accident Rate)
• Individual Risk
Details tables
• FN Totals and Raw FN Chart
• FN Details
• Individual Risk Details
• Explosion Details
Phast Risk v6.7 Release Notes 11
The summary tables occupy a relatively small amount of storage space within the data file. However,
the detail tables can potentially occupy a large amount of space and will provide a significant space
saving if they are not required and can be switched off.
Turning off the generation of either summary tables or details tables does not preclude you from
seeing those results in Extended Reporting: the results views are simply not pre-prepared for faster
viewing. However, in the case of a large study, turning of their creation will impact significantly on
the speed at which various data views in Extended Reporting can be loaded and navigated.
It is not possible to predict the size of a study’s risk results as it depends on whether consequences
impact populations and risk ranking points, etc. However, here are a set of input parameters for a
range of studies which offer guidelines about approximate sizes of risk result data files.
Study Size in GigaBytes 1.219 1.007 2.376 5.093 9.926 8.204 9.926
Study Inputs
Number of Run Rows 4 7 130 15 40 90 45
Avg Events per Run Row 194 437 24 170 78 192 266
Avg Weathers per Run Row 4 6 2 2 4 2 2
Avg Weather Directions per Run Row 32 96 32 40 64 40 40
Avg BuildingTypes per Run Row 17 17 2 6 5 6 6
Avg Buildings per Run Row 18 2 2 58 2 56 56
Avg PopulationCategories per Run Row 10 10 14 10 10 10 10
Avg Areas per Run Row 3 1 1 4 1 4 4
Avg Obstructed Regions per Run Row 13 86 1 24 2 20 20
Avg Risk Ranking Points per Run Row 10 260 0 9 8 9 9
These new additional results are available for the ‘Vessel/Pipe Source’, ‘User-defined Source’ and the
‘Warehouse Fire Model’ scenarios. These enhancements are further detailed below for the specific
case of the ‘warehouse’ scenario.
The sections below describe these modifications and enhancements in further detail.
Phast Risk v6.7 Release Notes 14
In Phast Risk v6.7 the model has been enhanced to reset the fire duration time to the actual duration it
takes for all materials to be burnt and the model will now run successfully.
15:47:39 ----- Calculating Model Doors Open- 900 m2/1800 s for Weather
Deelen, dag:Deelen - D 9.0m/s...
15:47:39 ---Info: WHFIRE 2001: Specified fire duration is larger than time
1031.11 s at which all warehouse materials are burned. So fire duration is
reset to the time 1031.11 s at which all warehouse materials are burned
Phast Risk v6.7 Release Notes 15
The message displayed will only be seen if ‘display information messages’ and ‘display warning
messages’ are selected in the Miscellaneous tab from the Options>Preferences>General Preferences
menu.
Phast Risk v6.7 Release Notes 16
In v6.7 additional toxic graphs are produced, so all the following combinations are now available:
• NO2,SO2,HCl separate probits/lethality versus distance
• NO2/SO2/HCl mixture dose/lethality versus distance
• NO2/SO2/HCl mixture footprint contours for probit/dose/lethality
• NO2,SO2,HCl separate footprint contours for probit/dose/lethality
An example can be seen in the Outdoor Toxic Lethality Footprint below where version v6.54 displays
the NO2 & HCl lethality footprint.
Phast Risk v6.7 Release Notes 17
The v6.7 plot displays the Warehouse Reference mixture footprint in addition to the NO2 & HCl
lethality
Please note that in the above screen shot the formatting of the plots has been adjusted from the default
(right-click on legend and choose Properties) to help distinguish between overlapping lines.
Phast Risk v6.7 Release Notes 18
The Dispersion stop criterion in the Dispersion Parameter group set in the Other tab (seen below) is
defaulted to ‘Risk based’.
The above default option should always be chosen for risk calculations, i.e. to determine the individual
and societal risk. However, with this option chosen the toxicity calculations will not proceed beyond
the minimum probability of death (default 1% in Phast Risk) and therefore all ERPG concentration
values may not be reached.
To ensure that all equivalent ERPG concentration values are reached, the user should change the
above option from ‘Risk based’ to ‘Mixed Basis’ (in addition to selection of ERPG averaging time in
‘Location’ tab of the Warehouse Fire model.
Please note that regardless of the option chosen dispersion calculations will always stop when the
cloud reaches the Maximum distance for dispersion set in the System Parameters (defaulted at 50
km), even if the other criteria have not all been met.
Phast Risk v6.7 Release Notes 20
PGS15 logic for allowing ADR Class 3 liquids has now been fully implemented. This logic is as
follows:
The screen below shows that for Fire-fighting system 2.1b, the ‘not stored’ & ‘Stored in other
packaging’ are now the only available options, as expected from the details above.
Phast Risk v6.7 Release Notes 23
In previous versions of Phast Risk user defined reactions rates are only available to PGS-15 Fire-
fighting systems. Once the PGS-15 option is unticked the option of user defined reaction rates is no
longer available as can be seen in the Phast Risk v6.54 image below.
In Phast Risk v6.7, users now have availability of the user-defined reaction rate when PGS-15 Fire-
fighting systems are not selected.
Phast Risk v6.7 Release Notes 24
Users need to select either ‘Stored in Other Packaging’ or ‘Stored in Synthetic Packaging’ in order for
the Reaction rate calculation field to be enabled. Then, the user defined calculation can be selected
and the desired value may be entered, as can be seen below.
Phast Risk v6.7 Release Notes 25
The following enhancements have been implemented in Phast Risk v6.7 to the in-building release
model:
• In v6.7, the release duration is set so all liquid will eventually evaporate from the building
for both instantaneous and continuous releases. This corrects an inconsistency previously
present where liquid would not always evaporate for instantaneous releases.
• For continuous releases the release duration from a building can never be less than one air
change.
• The release duration can never be more than the maximum release duration as set in the
parameters (currently 1800 seconds).
For indoor releases, the vapor fraction multiplication factor remains in use (current default value of 3)
and the material remaining is presumed to be trapped as liquid in the building. This multiplication
factor determines the fraction of vapor that can be released from the building and can be modified in
the Discharge parameters group.
In addition to dispersion calculations, the in-building model also carries out explosion calculations,
(which are not included in the risk calculations). Previous to v6.7, the venting parameter of the indoor
confined explosion model was a constant. The venting parameter is now a variable based on the
laminar burning velocity. Please note this correlation is only applicable for low-strength enclosures
which cannot withhold an overpressure higher than 0.1 bar (National Fire Protection Association -
NFPA 68) for laminar burning velocity not higher than 0.6m/s. Currently, there is no implementation
for high-strength enclosures; this is listed as a potential enhancement for a future version.
For further information on the in-building release model theory, please refer to the technical
documentation which is available with the Phast Risk installation
Phast Risk v6.7 Release Notes 26
10000
Predicted SMD [microns]
1000 Cardiff_Cyclo-Hexane
Cardiff_Water
Cardiff_Gasoline
Cardiff_Butane
Cardiff_Propane
INERIS_Butane
100 VKI - R134-A
STEP - Propane
HSL - Propane
INERIS - Butane
Ecole de Mines - Water
+30%-deviation
-30%-deviation
10
10 100 1000 10000
Measured SMD [microns]
A modified CCPS droplet correlation has been developed and implemented in Phast Risk v6.7 as the
default choice for non-instantaneous releases. This modified CCPS correlation chooses the
mechanical break-up droplet size for sub-cooled releases and the flashing droplet size for superheated
releases, instead of choosing the minimum size as in the original CCPS correlation. Better predictions
compared to experiments are obtained with the modified CCPS droplet correlation, as shown in the
figure below.
Phast Risk v6.7 Release Notes 29
10000
Predicted SMD [microns]
1000 Cardiff_Cyclo-Hexane
Cardiff_Water
Cardiff_Gasoline
Cardiff_Butane
Cardiff_Propane
INERIS_Butane
100 VKI - R134-A
STEP - Propane
HSL - Propane
INERIS - Butane
Ecole de Mines - Water
+30%-deviation
-30%-deviation
10
10 100 1000 10000
Measured SMD [microns]
Please note the modified CCPS droplet correlation is intended to be used in conjunction with the
Unified Dispersion Model (UDM) Version 2, which is the new default UDM model in Phast Risk
v6.7. Additionally, it was also shown that the modified CCPS droplet correlation resulted in the most
accurate UDM predictions of rainout.
For further details, see the document ‘Dropsize_theory_validation.pdf’ included as part of the Phast
Risk technical documentation.
13:45:47 +++Warning: UDMA 1106: Solid CO2 modelling enabled, but droplet
modelling not handled. Dispersion modelling will use equilibrium no rainout
The inclusion of CO2 as a Hazardous Substance in the Seveso Directive has been described in a HSE
paper available from the HSE's web site (http://www.hse.gov.uk/seveso/co2-hazardous-substance.pdf).
This paper states that the Phast CO2 model currently has the “greatest potential” to accurately model
the release of CO2.
For further information on the modelling, see also the files Thrm_theory.pdf and Xprp_Theory.pdf
included as part of the technical documentation on the release DVD.
Phast Risk v6.7 Release Notes 30
Component A B N
Nitrogen (N2) -65.7 1 5.2
Carbon Dioxide (CO2) -90.778 1.01 8
The above values for nitrogen correspond to the probit function recommended in the “Reference
Manual BEVI Risk Assessments” (formerly Purple Book) for inert gases such as nitrogen.
The above values for carbon dioxide are derived from values recommended by the HSE for SLOT (1%
probability of death), SLOD (50% probability of death) and N. The HSE SLOT DTL and SLOD DTL
values for carbon dioxide are 1.5 x 1040 and 1.5 x 1041 respectively (units ppm for concentration c and
minutes for time t), where the dangerous toxic load DTL is defined by
DTL = N
∫ c dt
Please note that the above values are not used by default, since both nitrogen and carbon dioxide are
flagged as inert materials. The materials’ Flammable/Toxic physical property setting needs to be set
to Toxic to enable toxicity calculations (and associated risk).
Previously, if using dangerous toxic load values greater than 3.4 x 1038 you receive an error during
toxic effect calculations. The SLOT DTL and SLOD DTL values for Carbon Dioxide are 1.5 x 1040
and 1.5 x 1041 respectively. The dangerous toxic load model currently uses single precision floating
point values which have a maximum definable positive value of 3.4 x 1038. Over time all of the DNV
Software models are being updated to use double precision floating point numerical values but at this
time the dangerous toxic load calculation is awaiting update. It is worth noting that this problem tends
to exist for materials which are not strictly classified as ‘toxic’ but are considered harmful at relatively
large concentrations and exposure times based on their asphyxiation potential. Please note that when
calculating toxic load using these toxic coefficients changes should be made to the model inputs as
follow:
1. Change the Toxic parameters > Toxic Tab > Probit Calculation Method to 'Use Probit'
2. For SLOT use 1% lethality, for SLOD 50%
Pools on Water
The table below lists the material properties used in Phast Risk for pools on water. These are all non-
DIPPR physical properties. The last two properties in the table concern ammonia only, and for this
case the properties are obtained from Raj and Reid as described in the PVAP theory manual. For the
remaining first four properties a thorough literature search has been done and new values have been
Phast Risk v6.7 Release Notes 31
implemented in Phast Risk v6.7. For further details on the actual values please refer to the
Property_Database_Property_List.pdf document provided with the software.
bund
If the release location is indeed at the centre of the bund, the formulation in previous versions of Phast
Risk may have given too conservative results; particularly for the cases of a large bund, rainout
locations at or near the bund wall and formation of a large pool filling the entire bund.
Phast Risk v6.7 provides a modified less conservative method, which applies the assumption that the
release point is at the centre of the bund both for the rainout criterion and the subsequent pool fire
calculations.
vapour-plume centre-line
(always unaffected by bund)
bund
Bund radius
• If rainout occurs outside the bund, this enhancement will have no effect.
• If the droplets hit the bund wall, rainout is assumed to occur inside the bund and the resulting
pool is assumed to have spread back, in the upwind direction
• If rainout occurs within the bund, without hitting the wall, it is assumed that the pool will
spread without bund effects until the downwind radius of the pool reaches the downwind
radius of the bund and then spread back upwind, ultimately with the pool constrained by the
bund centered at the release point.
Phast Risk v6.7 Release Notes 32
The previous versions of Phast Risk assumed the pool centre to be equal to the rainout location. This
simplistic latter assumption has been maintained in Phast Risk v6.7 for the purpose of the pool
evaporation calculations and the pool vapour added back to the UDM cloud.
However the early and late pool fires will apply the new, more correct location of the pool fire, with
the downwind edge of the pool fires moved to the downwind bund wall (but reduction of radiation due
to shielding by the bund wall is not considered).
The first change is that the parameter is now set as an indoor fraction instead of an outdoor fraction in
order to make the input consistent with the data in the population database; hence it is renamed to
‘Fraction of population indoors (Societal Risk)’, and the default values have been changed to 0.9
Phast Risk v6.7 Release Notes 34
Each population now has an indoor fraction attribute, shown below. This parameter is used as the
default setting for each population defined in the population set and the value will be surrounded by a
green border. This value can be set individually for each population as needed.
Phast Risk v6.7 Release Notes 35
In Phast Risk v6.7, the 3D/ME Purple Book method requires an ‘Unconfined Explosion Strength’ and
this can be used together with an efficiency factor in such a way to represent a cloud where a fixed
proportion of the cloud is ignited within assumed but unspecified obstructed regions in all delayed
ignition locations.
The Unobstructed explosion strength and Explosion Efficiency parameters are located in the General
Risk Parameters, ME and BST tab. Please note that the ‘Unconfined Explosion Strength’ can be set to
any value between 0 and 10 and therefore possibly represents unconfined or confined explosion source
strengths, depending on your preferred input value. The default value is 2.
Comparison of the Wiekema and 3D Cloud ME/Purple Book explosion
methods
To obtain equivalent results to the former Wiekema method when using the new 3D ME/Purple Book
method the following settings would be used:
• The Multi Energy curve used is 10 (Unobstructed strength parameter value 10)
• 12.5% of the flammable mass is considered to be in obstructed regions (12.5% Unobstructed
explosion efficiency)
• Heavy explosion damage corresponds to an overpressure of 0.3 bar (Indoor and outdoor
fatality = 1)
• Lighter explosion damage corresponds to an overpressure of 0.1 bar (Indoor fatality only
0.025)
Phast Risk v6.7 Release Notes 36
100
0.3
1
0.1
0.1
0.01
0.001
0.1 1 10 100
Scaled distance r'
ellipses so the new method removes one of the approximations in the risk calculations. There are some
further significant differences;
When applying the free-field logic (only normally used in SAFETI-NL) this means that the
risk model knows how far the cloud travels along the centreline. In the 2D method it knows
only how far the ellipses go downwind at the flammable effect height (1m in SAFETI-NL, 0m
in Phast Risk). So the free-field decision algorithm can use the cloud centreline distance to
determine whether the cloud crosses the plant boundary at any height.
If the explosion fails to generate overpressures because the energy available is below the
minimum parameter value then in the 2D method there are limited mechanisms to ensure that
the flash fire zone still does generate risk. In reality if there is ignition then the flash fire
hazard (possibly with pool fire too) will be present even if no overpressures are generated.
However the 2D modeling has limitations as listed in the following table;
This will then bring up the wizard where you can select the type of CAD connection to be used and the
file to be used.
Once the file is selected the wizard will create the CSD file and will include all layers available. As
you can see below the location of the CSD file is displayed
Phast Risk v6.7 Release Notes 40
Once the Finish button is pressed, the tree will show the new connection created.
Phast Risk v6.7 Release Notes 41
Minor enhancements
Specification of breach location larger than the total pipe length will produce a fatal error, resulting
in a red bordered Vessel/Pipe Source and no consequence results in v6.7 whereas the previous
behavior was to automatically relocate the break location to the end of the pipe. This change applies to
both long pipeline models: the vapor phase long pipeline scenarios and 2-phase long pipeline
scenarios.
In calculation of ambient temperature, now dry air specific heat instead of wet air is used in the
code in line with UDM theory (Appendix A.3 in UDM theory manual). Particularly in cases which
experience large elevation changes this may have some effect. This has less effect if UDM version 2
(default) is in use for dispersion calculations
The default value for the parameter for maximum step size for instantaneous releases has been
reduced from 1000s to 100s. This will affect results for instantaneous releases for step sizes larger
than 100 seconds. This will also result in more smooth results in the far-field.
Modified pool fire maximum burn rate mixing rule - incorrect mixing rule is applied in case a
mixture contains both components with defined maximum burn rate and undefined maximum burn
rate. In Phast Risk v6.7 a mixture’s maximum burn rate is now set to undefined when any of the
components are undefined. An ‘undefined’ mixing rate as input to the pool fire model POLF, means
that POLF will calculate the burn rate itself.
Corrected density calculations for jet fires. The saturated vapour density at atmospheric pressure is
required for two-phase jet fire calculation. For some materials, particularly mixtures, liquid density
could previously be erroneously returned as vapour density by the property calculation if the saturation
temperature at atmospheric pressure is very low and this would subsequently lead to under-predictions
of jet fire radiation. This is prevented now by using ideal gas density if no valid vapour density is
found by the property calculation for a 2-phase discharge. If this occurs, the JFSH warning 1050 is
given. Thus if this warning is given in Phast Risk v6.7, increased risk may occur for the jet fire
compared to v6.6.
Warehouse fires, with warehouse material including Br and F. The modelled combustion product
released to the atmosphere consist of HCl, HBr and HF. Prior to v6.7, HBr and HF were classed
together with HCl to conserve mass in line with previous CPR-15 regulations. To obtain more accurate
toxicity calculations it is however more appropriate to conserve number of moles instead of mass.
Thus in Phast Risk v6.7, HBr and HF are classed together with HCl such as to conserve moles in line
in more recent PGS-15 regulations. In case Br and/or F are present in the stored warehouse material,
this will affect the mass fraction of HCl per unit mass of active warehouse material, the mass fraction
of HCl in the modelled released combustion product (HCl, NO2, SO2 mixture), and the mass release
rate of HCl/NO2/SO2 mixture.
Phast Risk v6.7 Release Notes 43
SI10384: When a file created in versions previous to This can be remedied by saving the PSU file in
v6.7 is opened and the map is viewed there may be a v6.7, closing the file and then reopening the file.
GIS error on the message log and the map may be
invisible
SI10311: When exporting a report, the save as dialog The workaround is to click the save button and
does not show a field to enter a name in Vista then rename the saved file to the desired name
SI10150: When using external connections, the data If you get this message in the log window,
complete check does not spot if an External Connection please check the locations for the external
has moved from its original location. This means that connections and modify accordingly
you can have an External Connection with Feature
Classes showing as complete in the node tree, but not
displaying in the GIS views. On opening a map or risk
contour plot you get the following message in the log
window:
"GIS Error: Unable to connect to the database. Please
verify that your warehouse-connection parameters are
correct and try again."
When inserting a building type, the geometry is
The workaround is to fill in the building type
mandatory but there is no warning if you do not enter
geometry. Values of 10, 10, 10 may be suitable
the data and the program does not run the risk
if there are no known values.
calculations. An error similar to the one below will
appear:
*** Error: Cannot execute run row 'Flammables
Night ME' because Building Type 'Building
Set\Building Type' has incomplete data
Phast Risk v6.7 Release Notes 44
SI10536: Import of certain AutoCAD files results in The example.dwg import was created using the
undesirable display of vectors zig zagging the object. new CAD import wizard (see page 37). This
method imports all layers. To workaround the
An example of such a drawing is:
problem, use the manual CAD import method
and exclude the problematic layer when defining
feature classes. Alternatively, remove the layer
in AutoCAD.
Phast Risk v6.7 Release Notes 45
Or
J415 Discharge from vessels and short pipes (leak, line rupture, relief valve scenarios) DISC warning
1005 converted to DISC error 32. The error is now provided in case entropy is not conserved for
property calculations associated with choked orifice flow. This appears to be mostly caused by
picking up incorrect vapour density instead of liquid density and vice versa. This is now an error
because previous results were shown to be physically incorrect by a large margin. To model cases
which show this error it will be necessary to adjust inputs and/or use the user-defined source model.
Dispersion
2110 UDM instantaneous dispersion taking excessively large downwind steps Very large steps taken
by instantaneous dispersion model results in discontinuities in the toxic and concentration results.
This has been resolved in reducing the default maximum step size for instantaneous dispersion
calculations from 1000 seconds to 100 seconds.
10365 Droplet trajectories for pressurised instantaneous releases These were incorrectly calculated,
resulting in rainout too far downwind. This would result in clouds leaving the pool behind too soon.
Risk
9964 Zero length route segments It was possible to enter a route geometry with successive identical
points. This resulted in a route model error and the associated model group being left out of the risk
calculations. The error message could be missed in the log window by the user. So, the identical
points are now eliminated and the model can process them.
10285 Delayed Ignition Probability for K2, K3 and K4 liquids should be zero. Previously, the delayed
ignition probability for K2, K3 and K4 liquids was set to 1-Immediate ignition probability and not
zero as prescribed by the Purple Book. Thus did lead to erroneous inclusion of delayed explosions
and delayed flash fires and too high risk. This is fixed in v6.7, i.e. in v6.7 the delayed ignition
probability is set equal to 0 for K2,K3,K4 liquids. This therefore results in a risk reduction.
10408 Toxic risk can be too high This could occur when subsequent toxic clouds have the property such
that the clouds have a high width/length ratio (>1) and decreasing length between clouds. Resolution
of this incident can only reduce risk results.
10239, Vertical refrigerated releases missing the jet fire effects This could result in not including the jet
10283 fire for the risk calculations. In v6.7 the jet fire will be vertical and will be included in the risk
calculations. Thus this change may increase the risk but normally the jet fire effects from such a
release are not significant.
GUI
8812 Problems connecting to some GIS database formats
Previously there were problems connecting to GML, WCS and WMS sources.
10225 Flammable Mass in earlier fireball report is not the mass actually used in the model
For v6.7, in the Fireball report there are now two fields: Potential Fireball Mass (total mass in vessel),
and Actual Flammable Mass (mass used for fire-ball calculations, three times vapour fraction (if <
100%).
10290 The flammable lethality zone on the Map tab in graphs is incorrectly calculated.
Changing the lethality on the jetfire reporting levels grid had no effect on the jetfire lethality Effect
zone on the map.
10379 The Pool fire report included the radiative fraction for general fires even if not used
Now the correct radiative fraction is reported (as output by the pool fire calculations) for all types of
fires (general, luminous, smoky fires). This only affects the pool fire report and does not otherwise
affect the results.
10440 Save as with results not working properly with psc format with memory saving on
The supplementary results files we not being written the results folder as required by the minimise
memory option.
10469 Warehouse fire scenario remains blue while copying to other study
Because the parameters may vary between studies then the results must be regenerated in the new
study and not copied from the existing run of the model.
10513 Save as overwrites existing file on Vista and Windows 7 with file extensions on
It was easy to think you were saving to a new file and instead the existing file was being overwritten
so your original data was lost. The problem only occurred on Windows Vista and version 7 when the
user had activated the display of file extensions (non-default).
Phast Risk v6.7 Release Notes 49
Technical Reference
The Technical Reference subfolder contains *.PDF documents which give details of several aspects
of the modelling. These details include verification and validation of the models.
Phast Risk v6.7 Release Notes 50
System Requirements
Operating Windows XP SP3, Windows Server 2003, Windows Server 2008,
system
Microsoft Vista, Windows7
Internet IE 5.0x. This does not have to be set as your default browser, but you
Browser must have at least this version installed in order to run the program.
Display 800x600 resolution
Screen color 65536 (16-bit) and higher
depth
CPU 32 or 64 bit multi-core CPU from Intel or ADM like Intel Core2 Duo
Media DVD-ROM drive or internet connection
Pointing device MS Mouse or compatible
Disk Space The installation requires 285 MB of disk space
Spreadsheet The program is capable of using Excel spreadsheets for input/output of
data
.
CPU Speed Recommended
Memory
(minimum)
Phast Risk 2.8+GHz 3GB (2GB)
Phast Risk (large study) 3.2+GHz 6GB (4GB)
These values are based on the user experiencing acceptable performance. Depending on your needs
you may consider to select a more powerful machine.
The indicated required disk space is very dependent on the existing system. Our values are based on a
clean operating system with no additional software.
Temporary folders
The program uses hard disk space to write temporary, or “scratch” files which are subsequently
deleted once the run has completed or in some cases when the program has been closed down. By
default the program uses the subfolder C:\DNVUser\Temp to write temporary files during the
calculation of results, and also to write temporary files that are used during the reporting of results.
For large Study Folders, these temporary files can require a lot of hard disk space. Phast Risk will
crash if there is insufficient hard disk space for it to create the temporary files, so you should save your
Phast Risk v6.7 Release Notes 51
Study Folder before running calculations or viewing results, and avoid running Phast Risk if the free
space on your hard disk is low
Phast Risk uses a third party product called “Seagate Crystal Reports” to produce text reports. Crystal
Reports always uses the temporary folder set up by your operating system for its own scratch file
space, and by default this is generally the C:\Temp folder.
Memory Management
Phast Risk can use a lot of memory (RAM) when running very large studies/study folders, and also
when viewing large combinations of text reports and graphs. You should follow these simple rules to
avoid problems with memory:
• Close all out-of-date Reports and Graphs if you are no longer using them. You can always
reopen the Report or Graph for the Model if you need to view it again; if the name of the
Model is displayed in blue in the Study Tree, then that Model has results that are available for
viewing.
• Use the option in the Results tab of the General Preferences to save results to files instead of
storing them in memory. Reports and Graphs will take longer to generate if you choose this
option, but it will reduce the memory requirements considerably.
• For very large studies (for example those containing more than 100 models and 3 associated
weathers) ensure before you run that you have sufficient hard disk space for temporary file
storage and also for runtime memory requirements.
Runtime memory is memory which will be used by Phast Risk for storing results as it performs its
calculations; it is a combination of fixed RAM plus “virtual” (hard disk substitute) memory. You can
adjust the total available memory size using the System option in the Control Panel. Consult your IT
professional before altering any of these settings.
During calculations for a very large study, you may see an "out of memory" message (or similar)
appear on the screen. If this occurs it is important you stop the calculations immediately and save your
work. If you do not stop the calculations, Phast Risk may crash, and you will lose any changes you
made to your Study Folder since the last time you saved your work.
The process of generating Graphs can sometimes require a large amount of memory (especially
graphics memory). Models which involve the rainout and evaporation of a flammable material can
produce a particularly large number of data points that need to be plotted, with large demands on the
Graphing function. If you use the “data culling” option (on the Graphs tab section of the Preferences
dialog, which is under the Options menu), then the Graphing function will ignore unnecessary data
points (i.e. data points which do not describe significant changes in the behavior), and will therefore
save memory and time. See the online Help for more details of data culling.
It has not been explicitly mentioned that the application is single-thread software and increasing cores
or CPUs will not improve calculation. However, multi-cores would benefit the overall user experience
as the OS, Outlook, SQL Server or other applications can use the other system capacities. In this case,
the bottleneck may be the RAM or disk read/write speed (local or remote).