> For the complete documentation index, see [llms.txt](https://docs.voting.works/vxsuite-user-manual-v4/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.voting.works/vxsuite-user-manual-v4/system-maintenance/maintenance-overview.md). # Maintenance Overview Voting system maintenance is an ongoing process that is a part of every election. General maintenance procedures are described in [Setup Inspection](/vxsuite-user-manual-v4/logic-and-accuracy-pre-election-testing/setup-inspection.md) and supplies in the [Supply List](/vxsuite-user-manual-v4/miscellaneous/supply-list.md). The following maintenance manuals are provided for long-term system maintenance reference and are targeted at a system administrator whose role and training requirements are defined in [Smart Cards and User Roles](/vxsuite-user-manual-v4/vxadmin-system-setup/programming-cards.md). Maintenance tasks that need to be performed by a VotingWorks technician are specifically identified in each voting system component maintenance manual. Maintenance performed by users (system administrators) do not require any specific facility, furnishing, fixture, or utility and are able to be performed in election offices and storage facilities. Maintenance performed by VotingWorks may require transport to a VotingWorks facility. In addition to regular election maintenance tasks, they include additional long-term maintenance tasks, provide manufacturer documentation, and make recommendations for spare parts and service. The [Approved Parts List](/vxsuite-user-manual-v4/system-maintenance/approved-parts-list.md) is a more formal and complete extension of the [Supply List](/vxsuite-user-manual-v4/miscellaneous/supply-list.md). In the event any voting system component has a catastrophic failure for any reason, users should replace the device with a backup unit or contact VotingWorks for a replacement unit. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.voting.works/vxsuite-user-manual-v4/system-maintenance/maintenance-overview.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.