<?xml version="1.0" encoding="UTF-8"?>
<collection xmlns="http://www.loc.gov/MARC21/slim">
    <record>
        <controlfield tag="001">69942</controlfield>
        <controlfield tag="005">20190709135509.0</controlfield>
        <datafield tag="024" ind1="7" ind2=" ">
            <subfield code="2">doi</subfield>
            <subfield code="a">10.1016/j.ress.2017.04.006</subfield>
        </datafield>
        <datafield tag="024" ind1="8" ind2=" ">
            <subfield code="2">sideral</subfield>
            <subfield code="a">101874</subfield>
        </datafield>
        <datafield tag="037" ind1=" " ind2=" ">
            <subfield code="a">ART-2017-101874</subfield>
        </datafield>
        <datafield tag="041" ind1=" " ind2=" ">
            <subfield code="a">eng</subfield>
        </datafield>
        <datafield tag="100" ind1=" " ind2=" ">
            <subfield code="0">(orcid)0000-0002-8035-5762</subfield>
            <subfield code="a">Berrade, M. D.</subfield>
            <subfield code="u">Universidad de Zaragoza</subfield>
        </datafield>
        <datafield tag="245" ind1=" " ind2=" ">
            <subfield code="a">A study of postponed replacement in a delay time model</subfield>
        </datafield>
        <datafield tag="260" ind1=" " ind2=" ">
            <subfield code="c">2017</subfield>
        </datafield>
        <datafield tag="506" ind1="0" ind2=" ">
            <subfield code="a">Access copy available to the general public</subfield>
            <subfield code="f">Unrestricted</subfield>
        </datafield>
        <datafield tag="520" ind1="3" ind2=" ">
            <subfield code="a">We develop a delay time model for a one component system with postponed replacement to analyze situations in which maintenance might not be executed immediately upon discovery of a defect in the system. Reasons for postponement are numerous: to avoid production disruption or unnecessary or ineffective replacement; to prepare for replacement; to extend component life; to wait for an opportunity. This paper explores conditions that make postponement cost-effective. We are interested in modelling the reality in which a maintainer either prioritizes functional continuity or is not confident of the inspection test indicating a defective state. In some cases more frequent inspection and a longer time limit for postponement are recommended to take advantage of maintenance opportunities, characterized by their low cost, arising after a positive inspection. However, when the cost of failure increases, a significant reduction in the time limit of postponement interval is observed. The examples reveal that both the time to defect arrival and delay time have a significant effect upon the cost-effectiveness of maintenance at the limit of postponement. Also, more simply, we find that opportunities must occur frequently enough and inspection should be a high quality procedure to risk postponement.</subfield>
        </datafield>
        <datafield tag="536" ind1=" " ind2=" ">
            <subfield code="9">info:eu-repo/grantAgreement/ES/MINECO/MTM2015-63978-P</subfield>
        </datafield>
        <datafield tag="540" ind1=" " ind2=" ">
            <subfield code="9">info:eu-repo/semantics/openAccess</subfield>
            <subfield code="a">by-nc-nd</subfield>
            <subfield code="u">http://creativecommons.org/licenses/by-nc-nd/3.0/es/</subfield>
        </datafield>
        <datafield tag="590" ind1=" " ind2=" ">
            <subfield code="a">4.139</subfield>
            <subfield code="b">2017</subfield>
        </datafield>
        <datafield tag="591" ind1=" " ind2=" ">
            <subfield code="a">OPERATIONS RESEARCH &amp; MANAGEMENT SCIENCE</subfield>
            <subfield code="b">6 / 83 = 0.072</subfield>
            <subfield code="c">2017</subfield>
            <subfield code="d">Q1</subfield>
            <subfield code="e">T1</subfield>
        </datafield>
        <datafield tag="591" ind1=" " ind2=" ">
            <subfield code="a">ENGINEERING, INDUSTRIAL</subfield>
            <subfield code="b">5 / 47 = 0.106</subfield>
            <subfield code="c">2017</subfield>
            <subfield code="d">Q1</subfield>
            <subfield code="e">T1</subfield>
        </datafield>
        <datafield tag="592" ind1=" " ind2=" ">
            <subfield code="a">1.665</subfield>
            <subfield code="b">2017</subfield>
        </datafield>
        <datafield tag="593" ind1=" " ind2=" ">
            <subfield code="a">Applied Mathematics</subfield>
            <subfield code="c">2017</subfield>
            <subfield code="d">Q1</subfield>
        </datafield>
        <datafield tag="593" ind1=" " ind2=" ">
            <subfield code="a">Safety, Risk, Reliability and Quality</subfield>
            <subfield code="c">2017</subfield>
            <subfield code="d">Q1</subfield>
        </datafield>
        <datafield tag="593" ind1=" " ind2=" ">
            <subfield code="a">Industrial and Manufacturing Engineering</subfield>
            <subfield code="c">2017</subfield>
            <subfield code="d">Q1</subfield>
        </datafield>
        <datafield tag="655" ind1=" " ind2="4">
            <subfield code="a">info:eu-repo/semantics/article</subfield>
            <subfield code="v">info:eu-repo/semantics/acceptedVersion</subfield>
        </datafield>
        <datafield tag="700" ind1=" " ind2=" ">
            <subfield code="a">Scarf, P. A.</subfield>
        </datafield>
        <datafield tag="700" ind1=" " ind2=" ">
            <subfield code="a">Cavalcante, C.A.V.</subfield>
        </datafield>
        <datafield tag="710" ind1="2" ind2=" ">
            <subfield code="1">2007</subfield>
            <subfield code="2">265</subfield>
            <subfield code="a">Universidad de Zaragoza</subfield>
            <subfield code="b">Dpto. Métodos Estadísticos</subfield>
            <subfield code="c">Área Estadís. Investig. Opera.</subfield>
        </datafield>
        <datafield tag="773" ind1=" " ind2=" ">
            <subfield code="g">168 (2017), 70-79</subfield>
            <subfield code="p">Reliab. eng. syst. saf.</subfield>
            <subfield code="t">RELIABILITY ENGINEERING &amp; SYSTEM SAFETY</subfield>
            <subfield code="x">0951-8320</subfield>
        </datafield>
        <datafield tag="856" ind1="4" ind2=" ">
            <subfield code="s">471438</subfield>
            <subfield code="u">http://zaguan.unizar.es/record/69942/files/texto_completo.pdf</subfield>
            <subfield code="y">Postprint</subfield>
        </datafield>
        <datafield tag="856" ind1="4" ind2=" ">
            <subfield code="s">69359</subfield>
            <subfield code="u">http://zaguan.unizar.es/record/69942/files/texto_completo.jpg?subformat=icon</subfield>
            <subfield code="x">icon</subfield>
            <subfield code="y">Postprint</subfield>
        </datafield>
        <datafield tag="909" ind1="C" ind2="O">
            <subfield code="o">oai:zaguan.unizar.es:69942</subfield>
            <subfield code="p">articulos</subfield>
            <subfield code="p">driver</subfield>
        </datafield>
        <datafield tag="951" ind1=" " ind2=" ">
            <subfield code="a">2019-07-09-11:50:38</subfield>
        </datafield>
        <datafield tag="980" ind1=" " ind2=" ">
            <subfield code="a">ARTICLE</subfield>
        </datafield>
    </record>

    
</collection>