<?xml version="1.0" encoding="UTF-8"?>
<collection>
<dc:dc xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:invenio="http://invenio-software.org/elements/1.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/oai_dc/ http://www.openarchives.org/OAI/2.0/oai_dc.xsd"><dc:identifier>doi:10.1016/j.ress.2017.04.006</dc:identifier><dc:language>eng</dc:language><dc:creator>Berrade, M. D.</dc:creator><dc:creator>Scarf, P. A.</dc:creator><dc:creator>Cavalcante, C.A.V.</dc:creator><dc:title>A study of postponed replacement in a delay time model</dc:title><dc:identifier>ART-2017-101874</dc:identifier><dc:description>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.</dc:description><dc:date>2017</dc:date><dc:source>http://zaguan.unizar.es/record/69942</dc:source><dc:doi>10.1016/j.ress.2017.04.006</dc:doi><dc:identifier>http://zaguan.unizar.es/record/69942</dc:identifier><dc:identifier>oai:zaguan.unizar.es:69942</dc:identifier><dc:relation>info:eu-repo/grantAgreement/ES/MINECO/MTM2015-63978-P</dc:relation><dc:identifier.citation>RELIABILITY ENGINEERING &amp; SYSTEM SAFETY 168 (2017), 70-79</dc:identifier.citation><dc:rights>by-nc-nd</dc:rights><dc:rights>http://creativecommons.org/licenses/by-nc-nd/3.0/es/</dc:rights><dc:rights>info:eu-repo/semantics/openAccess</dc:rights></dc:dc>

</collection>