> 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

## Station Maintenance and Operations

### 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**](/station-maintenance-and-operations/station-maintenance.md) – routine inspection, cleaning, and system checks
* [**Troubleshooting**](/station-maintenance-and-operations/troubleshooting.md) – identifying and resolving system and data issues
* [**Sensor Lifecycle Planning**](/station-maintenance-and-operations/sensor-lifecycle-planning.md) – planning for replacement and long-term maintenance
* [**Asset Management**](/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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://3dpaws.comet.ucar.edu/station-maintenance-and-operations.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.