> For the complete documentation index, see [llms.txt](https://docs.plummerindustries.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.plummerindustries.com/bumper-mounts/recommended-layouts/individual-bumpers/maintenance.md).
# Maintenance
We have created a list of recommended maintenance/inspections at varying points throughout your usage of the Bumper Mounts
## Per match Tasks
* [ ] Visual inspections for loose hardware
* [ ] Look for missing parts
## Per Event
* [ ] Visually inspect sockets for signs of wear
* [ ] Add small amount of oil into the mechanism
* [ ] Tighten all hardware
{% hint style="info" %}
We recommend this oil from DUPONT but any oil will work.
When dry it leaves a film in the black oxide that adds lubricity and rust prevention.
{% endhint %}
## Yearly
* [ ] If you are reusing them year to year we recommend re oiling the entire mount to prevent rust
* [ ] Inspect for wear in both sockets and on mounts themselves
* [ ] Over oil mechanism and Unlock/Lock repeat to flush contaminants and re oil whole mechanism
{% hint style="warning" %}
If excessive wear or damage noticed during inspection reach out to us. There should be very minimal wear year to year. We have seen some instances of teams using their mounts for 3 years or more.
{% endhint %}
---
# 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.plummerindustries.com/bumper-mounts/recommended-layouts/individual-bumpers/maintenance.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.