<?xml version="1.0" encoding="UTF-8"?><?xml-stylesheet type="text/xsl" href="static/style.xsl"?><OAI-PMH xmlns="http://www.openarchives.org/OAI/2.0/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/ http://www.openarchives.org/OAI/2.0/OAI-PMH.xsd"><responseDate>2026-09-18T23:15:16Z</responseDate><request verb="GetRecord" identifier="oai:mountainscholar.org:10217/235336" metadataPrefix="dim">https://api.mountainscholar.org/server/oai/request</request><GetRecord><record><header><identifier>oai:mountainscholar.org:10217/235336</identifier><datestamp>2025-12-30T03:26:35Z</datestamp><setSpec>com_10217_100532</setSpec><setSpec>com_10217_100000</setSpec><setSpec>com_10217_199888</setSpec><setSpec>com_10217_100303</setSpec><setSpec>col_10217_182111</setSpec><setSpec>col_10217_199889</setSpec></header><metadata><dim:dim xmlns:dim="http://www.dspace.org/xmlns/dspace/dim" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:doc="http://www.lyncode.com/xoai" xsi:schemaLocation="http://www.dspace.org/xmlns/dspace/dim http://www.dspace.org/schema/dim.xsd">
   <dim:field mdschema="dc" element="contributor" qualifier="author" authority="7d92b727-615e-4f07-81b5-f2318a869bf8" confidence="-1">Pirani, Badruddin, author</dim:field>
   <dim:field mdschema="dc" element="contributor" qualifier="author" authority="4e7a8ed6-fa09-4d1f-8fbd-6078c6936ca3" confidence="-1">Cale, James, advisor</dim:field>
   <dim:field mdschema="dc" element="contributor" qualifier="author" authority="79769aa9-668c-48f2-9b0a-3b542dae002a" confidence="-1">Simske, Steven, committee member</dim:field>
   <dim:field mdschema="dc" element="contributor" qualifier="author" authority="dd187236-d8ac-46de-aabb-4c2da545c5b8" confidence="-1">Miller, Erika, committee member</dim:field>
   <dim:field mdschema="dc" element="contributor" qualifier="author" authority="da2c8ff2-4596-41ff-a2f2-20c1f6a30089" confidence="-1">Keller, Josh, committee member</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="accessioned">2022-05-30T10:22:53Z</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="available">2022-05-30T10:22:53Z</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="issued">2022</dim:field>
   <dim:field mdschema="dc" element="identifier">Pirani_colostate_0053A_17154.pdf</dim:field>
   <dim:field mdschema="dc" element="identifier" qualifier="uri">https://hdl.handle.net/10217/235336</dim:field>
   <dim:field mdschema="dc" element="identifier" qualifier="uri">https://doi.org/10.25675/3.02439</dim:field>
   <dim:field mdschema="dc" element="description" qualifier="abstract">Battery systems are used as critical power sources in a wide variety of advanced platforms (e.g., ships, submersibles, aircraft). These platforms undergo unique and extreme mission profiles that necessitate high reliability and maintainability. Battery system failures and non-optimal maintenance strategies have a significant impact on total fleet lifecycle costs and operational capability.  Previous research has applied various approaches to improve battery system reliability and maintainability. Machine learning methodologies have applied data-driven and physics-based approaches to model battery decay and predict battery state-of-health, estimation of battery state-of-charge, and prediction of future performance. Queuing theory has been used to optimize battery charging resources ensure service and minimize cost. However, these approaches do not focus on pre-acceptance reliability improvements or platform operational requirements. This research introduces a two-faceted approach for enhancing the overall maintainability of platforms with battery systems as critical components. The first facet is the implementation of an advanced inspection and classification methodology for automating the acceptance/rejection decision for batteries prior to entering service. The purpose of this "pre-screening" step is to increase the reliability of batteries in service prior to deployment. The second facet of the proposed approach is the optimization of several critical maintenance plan design attributes for battery systems. Together, the approach seeks to simultaneously enhance both aspects of maintainability (inherent reliability and cost-effectiveness) for battery systems, with the goal of decreasing total lifecycle cost and increasing operational availability.</dim:field>
   <dim:field mdschema="dc" element="format" qualifier="medium">born digital</dim:field>
   <dim:field mdschema="dc" element="format" qualifier="medium">doctoral dissertations</dim:field>
   <dim:field mdschema="dc" element="language">English</dim:field>
   <dim:field mdschema="dc" element="language" qualifier="iso">eng</dim:field>
   <dim:field mdschema="dc" element="publisher">Colorado State University. Libraries</dim:field>
   <dim:field mdschema="dc" element="relation" qualifier="ispartof">2020-</dim:field>
   <dim:field mdschema="dc" element="rights">Copyright and other restrictions may apply. User is responsible for compliance with all applicable laws. For information about copyright law, please see https://libguides.colostate.edu/copyright.</dim:field>
   <dim:field mdschema="dc" element="title">A combined classification and queuing system optimization approach for enhanced battery system maintainability</dim:field>
   <dim:field mdschema="dc" element="type">Text</dim:field>
   <dim:field mdschema="thesis" element="degree" qualifier="name">Doctor of Philosophy (Ph.D.)</dim:field>
   <dim:field mdschema="thesis" element="degree" qualifier="level">Doctoral</dim:field>
   <dim:field mdschema="thesis" element="degree" qualifier="discipline">Systems Engineering</dim:field>
   <dim:field mdschema="thesis" element="degree" qualifier="grantor">Colorado State University</dim:field>
   <dim:field mdschema="dcterms" element="rights" qualifier="dpla">This Item is protected by copyright and/or related rights (https://rightsstatements.org/vocab/InC/1.0/). You are free to use this Item in any way that is permitted by the copyright and related rights legislation that applies to your use. For other uses you need to obtain permission from the rights-holder(s).</dim:field>
   <dim:field mdschema="others" element="access-status">open.access</dim:field>
</dim:dim>
</metadata></record></GetRecord></OAI-PMH>