<?xml version="1.0" encoding="UTF-8"?>
<collection xmlns="http://www.loc.gov/MARC21/slim">
 <record>
  <leader>     caa a22        4500</leader>
  <controlfield tag="001">445359773</controlfield>
  <controlfield tag="003">CHVBK</controlfield>
  <controlfield tag="005">20180317142911.0</controlfield>
  <controlfield tag="007">cr unu---uuuuu</controlfield>
  <controlfield tag="008">170323e20111201xx      s     000 0 eng  </controlfield>
  <datafield tag="024" ind1="7" ind2="0">
   <subfield code="a">10.1007/s10100-010-0151-x</subfield>
   <subfield code="2">doi</subfield>
  </datafield>
  <datafield tag="035" ind1=" " ind2=" ">
   <subfield code="a">(NATIONALLICENCE)springer-10.1007/s10100-010-0151-x</subfield>
  </datafield>
  <datafield tag="100" ind1="1" ind2=" ">
   <subfield code="a">Monhor</subfield>
   <subfield code="D">Davaadorjin</subfield>
   <subfield code="u">Faculty of Geoinformatics, University of West Hungary, Pirosalma u.1-3, Szekesfehervar, Hungary</subfield>
   <subfield code="4">aut</subfield>
  </datafield>
  <datafield tag="245" ind1="1" ind2="2">
   <subfield code="a">A new probabilistic approach to the path criticality in stochastic PERT</subfield>
   <subfield code="h">[Elektronische Daten]</subfield>
   <subfield code="c">[Davaadorjin Monhor]</subfield>
  </datafield>
  <datafield tag="520" ind1="3" ind2=" ">
   <subfield code="a">The notion of critical path is a key issue in the temporal analysis of project scheduling in deterministic setting. The very essence of the CPM consists in identifying the critical path, i.e., the longest path in a project network, because this path conveys information on how long it should take to complete the project to the project manager. The problem how can a stochastic counterpart of the deterministic critical path be defined is an important question in stochastic PERT. However, in the literature of stochastic PERT this question has so far almost been ignored, and the research into the random nature of a project duration has mainly been concentrated on the completion time in stochastic PERT in which any concrete special path is not specified. In the present paper we attempt to take first steps to fill this gap. We first developed a probabilistic background theory for univariate and bivariate marginal distributions of path durations of stochastic PERT whose joint path durations are modelled by multivariate normal distribution. Then, a new probabilistic approach to the comparison of path durations is introduced, and based on this comparison we define the concept of probabilistically critical path as a stochastic counterpart of the deterministic critical path. Also, an illustrative simple example of PCP and numerical results on the established probability bounds are presented.</subfield>
  </datafield>
  <datafield tag="540" ind1=" " ind2=" ">
   <subfield code="a">Springer-Verlag, 2010</subfield>
  </datafield>
  <datafield tag="690" ind1=" " ind2="7">
   <subfield code="a">Bounding bivariate normal probabilities</subfield>
   <subfield code="2">nationallicence</subfield>
  </datafield>
  <datafield tag="690" ind1=" " ind2="7">
   <subfield code="a">Critical path</subfield>
   <subfield code="2">nationallicence</subfield>
  </datafield>
  <datafield tag="690" ind1=" " ind2="7">
   <subfield code="a">Completion time in stochastic PERT</subfield>
   <subfield code="2">nationallicence</subfield>
  </datafield>
  <datafield tag="690" ind1=" " ind2="7">
   <subfield code="a">Probabilistically critical path</subfield>
   <subfield code="2">nationallicence</subfield>
  </datafield>
  <datafield tag="690" ind1=" " ind2="7">
   <subfield code="a">Stochastic PERT</subfield>
   <subfield code="2">nationallicence</subfield>
  </datafield>
  <datafield tag="773" ind1="0" ind2=" ">
   <subfield code="t">Central European Journal of Operations Research</subfield>
   <subfield code="d">Springer-Verlag</subfield>
   <subfield code="g">19/4(2011-12-01), 615-633</subfield>
   <subfield code="x">1435-246X</subfield>
   <subfield code="q">19:4&lt;615</subfield>
   <subfield code="1">2011</subfield>
   <subfield code="2">19</subfield>
   <subfield code="o">10100</subfield>
  </datafield>
  <datafield tag="856" ind1="4" ind2="0">
   <subfield code="u">https://doi.org/10.1007/s10100-010-0151-x</subfield>
   <subfield code="q">text/html</subfield>
   <subfield code="z">Onlinezugriff via DOI</subfield>
  </datafield>
  <datafield tag="908" ind1=" " ind2=" ">
   <subfield code="D">1</subfield>
   <subfield code="a">research-article</subfield>
   <subfield code="2">jats</subfield>
  </datafield>
  <datafield tag="950" ind1=" " ind2=" ">
   <subfield code="B">NATIONALLICENCE</subfield>
   <subfield code="P">856</subfield>
   <subfield code="E">40</subfield>
   <subfield code="u">https://doi.org/10.1007/s10100-010-0151-x</subfield>
   <subfield code="q">text/html</subfield>
   <subfield code="z">Onlinezugriff via DOI</subfield>
  </datafield>
  <datafield tag="950" ind1=" " ind2=" ">
   <subfield code="B">NATIONALLICENCE</subfield>
   <subfield code="P">100</subfield>
   <subfield code="E">1-</subfield>
   <subfield code="a">Monhor</subfield>
   <subfield code="D">Davaadorjin</subfield>
   <subfield code="u">Faculty of Geoinformatics, University of West Hungary, Pirosalma u.1-3, Szekesfehervar, Hungary</subfield>
   <subfield code="4">aut</subfield>
  </datafield>
  <datafield tag="950" ind1=" " ind2=" ">
   <subfield code="B">NATIONALLICENCE</subfield>
   <subfield code="P">773</subfield>
   <subfield code="E">0-</subfield>
   <subfield code="t">Central European Journal of Operations Research</subfield>
   <subfield code="d">Springer-Verlag</subfield>
   <subfield code="g">19/4(2011-12-01), 615-633</subfield>
   <subfield code="x">1435-246X</subfield>
   <subfield code="q">19:4&lt;615</subfield>
   <subfield code="1">2011</subfield>
   <subfield code="2">19</subfield>
   <subfield code="o">10100</subfield>
  </datafield>
  <datafield tag="900" ind1=" " ind2="7">
   <subfield code="a">Metadata rights reserved</subfield>
   <subfield code="b">Springer special CC-BY-NC licence</subfield>
   <subfield code="2">nationallicence</subfield>
  </datafield>
  <datafield tag="898" ind1=" " ind2=" ">
   <subfield code="a">BK010053</subfield>
   <subfield code="b">XK010053</subfield>
   <subfield code="c">XK010000</subfield>
  </datafield>
  <datafield tag="949" ind1=" " ind2=" ">
   <subfield code="B">NATIONALLICENCE</subfield>
   <subfield code="F">NATIONALLICENCE</subfield>
   <subfield code="b">NL-springer</subfield>
  </datafield>
 </record>
</collection>
