> For the complete documentation index, see [llms.txt](https://3dpaws.comet.ucar.edu/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://3dpaws.comet.ucar.edu/station-maintenance-and-operations.md).

# Station Maintenance and Operations

Guidance for maintaining 3D-PAWS stations, troubleshooting issues, planning component replacement, and managing station assets over time.

### Overview

After deployment, 3D-PAWS stations require ongoing monitoring, maintenance, and documentation to ensure reliable operation and high-quality data.

This section covers the activities needed to keep a station functioning over time.

***

### Operational Responsibilities

Station operation includes:

* performing routine maintenance and inspections
* monitoring data quality and system performance
* troubleshooting issues as they arise
* planning for component replacement over time
* documenting maintenance activities and site conditions

***

### Pages in This Section

Use the following pages to manage station operations:

* [**Station Maintenance**](https://3dpaws.comet.ucar.edu/station-maintenance-and-operations/station-maintenance.md) – routine inspection, cleaning, and system checks
* [**Troubleshooting**](https://3dpaws.comet.ucar.edu/station-maintenance-and-operations/troubleshooting.md) – identifying and resolving system and data issues
* [**Sensor Lifecycle Planning**](https://3dpaws.comet.ucar.edu/station-maintenance-and-operations/sensor-lifecycle-planning.md) – planning for replacement and long-term maintenance
* [**Asset Management**](https://3dpaws.comet.ucar.edu/station-maintenance-and-operations/asset-management.md) – tracking equipment and station components


---

# 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://3dpaws.comet.ucar.edu/station-maintenance-and-operations.md?ask=<question>&goal=<user_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.
