<?xml version="1.0" encoding="UTF-8"?>
<record
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://www.loc.gov/MARC21/slim http://www.loc.gov/standards/marcxml/schema/MARC21slim.xsd"
    xmlns="http://www.loc.gov/MARC21/slim">

  <leader>02126nab a2200241   4500</leader>
  <controlfield tag="005">20260520001113.0</controlfield>
  <controlfield tag="008">260224s2016    xxu                 ing  </controlfield>
  <datafield tag="041" ind1=" " ind2=" ">
    <subfield code="a">Ingl&#xE9;s</subfield>
  </datafield>
  <datafield tag="245" ind1="0" ind2="0">
    <subfield code="a">Assessing the Verification and Validation of Building Fire Evacuation Models</subfield>
  </datafield>
  <datafield tag="260" ind1=" " ind2=" ">
    <subfield code="a"></subfield>
    <subfield code="b"></subfield>
    <subfield code="c">ene. 2016</subfield>
  </datafield>
  <datafield tag="270" ind1=" " ind2=" ">
    <subfield code="a">25/07/2016 ; 25/07/2016</subfield>
  </datafield>
  <datafield tag="300" ind1=" " ind2=" ">
    <subfield code="a">22 p. ; 197-219</subfield>
  </datafield>
  <datafield tag="520" ind1=" " ind2=" ">
    <subfield code="a">Transcripci&#xF3;n del res&#xFA;men realizada por el autor: To date there is no International standard on the verification and validation (V&amp;V) of building fire evacuation models, i.e., model testers adopt inconsistent procedures or tests designed for other model uses. For instance, the tests presented within the MSC/Circ.1238 Guidelines for evacuation analysis for new and existing passenger ships provided by the International Maritime Organization are often employed for the V&amp;V of models outside their original context of use (building fires instead of maritime applications). This paper presents a list of verification tests for component testing and the analysis of emergent behaviours together with examples of experimental data-sets suitable for the analysis of different core components. The capabilities of building fire evacuation models are evaluated by studying their five main core components, namely (1) pre-evacuation time, (2) movement and navigation, (3) exit usage, (4) route availability and (5) flow constraints. This paper discusses the tests which are included in a freely available Technical Note developed at the National Institute of Standards and Technology. This work is intended to open a discussion on the main issues associated with the definition of a standard procedure for the V&amp;V of building fire evacuation models, including the definition of the acceptance criteria of a standard V&amp;V protocol.</subfield>
  </datafield>
  <datafield tag="581" ind1=" " ind2=" ">
    <subfield code="a">1</subfield>
  </datafield>
  <datafield tag="773" ind1="0" ind2=" ">
    <subfield code="t">Fire Technology</subfield>
    <subfield code="g">52</subfield>
  </datafield>
  <datafield tag="942" ind1=" " ind2=" ">
    <subfield code="c">ARTICULO</subfield>
  </datafield>
  <datafield tag="100" ind1="1" ind2=" ">
    <subfield code="a">Ronchi, Enrico</subfield>
    <subfield code="9">55471</subfield>
  </datafield>
  <datafield tag="100" ind1="1" ind2=" ">
    <subfield code="a">Nilsson, Daniel</subfield>
    <subfield code="9">55472</subfield>
  </datafield>
  <datafield tag="100" ind1="1" ind2=" ">
    <subfield code="a">Kuligowski, Erica D.</subfield>
    <subfield code="9">55473</subfield>
  </datafield>
  <datafield tag="100" ind1="1" ind2=" ">
    <subfield code="a">Peacock, Richard D.</subfield>
    <subfield code="9">32724</subfield>
  </datafield>
  <datafield tag="100" ind1="1" ind2=" ">
    <subfield code="a">Reneke, Paul A.</subfield>
    <subfield code="9">32726</subfield>
  </datafield>
  <datafield tag="999" ind1=" " ind2=" ">
    <subfield code="c">189654</subfield>
    <subfield code="d">189654</subfield>
  </datafield>
  <datafield tag="952" ind1=" " ind2=" ">
    <subfield code="0">0</subfield>
    <subfield code="1">0</subfield>
    <subfield code="4">0</subfield>
    <subfield code="7">0</subfield>
    <subfield code="9">257473</subfield>
    <subfield code="a">BAAB</subfield>
    <subfield code="b">BAAB</subfield>
    <subfield code="d">2026-03-06</subfield>
    <subfield code="j">200061894</subfield>
    <subfield code="l">0</subfield>
    <subfield code="p">200061894</subfield>
    <subfield code="r">2026-03-06 00:19:48</subfield>
    <subfield code="w">2026-03-06</subfield>
    <subfield code="y">ARTICULO</subfield>
  </datafield>
</record>
