> 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/asset-management.md). # Asset Management Guidance for tracking 3D-PAWS stations, components, maintenance history, and spare parts over the operational life of an observation network. ### Overview Operating a network of 3D-PAWS stations requires more than maintaining individual stations. Organizations also need a consistent way to track where stations are located, what equipment is installed, when components are replaced, and what spare parts are available. An asset management system helps maintain this operational history and supports maintenance planning, troubleshooting, and long-term network sustainability. Asset management systems do not need to be complex. Depending on the size of the network, records may be maintained using: * spreadsheets * shared folders * databases * dedicated asset management systems The most important requirement is **consistent record keeping using a unique station ID across all records**. *** #### Key Elements of an Asset Management System A practical 3D-PAWS asset management system should include: 1. a station registry 2. maintenance records 3. sensor and component records 4. spare-parts inventory 5. calibration and verification records 6. links to station documentation Together, these records provide the operational history of the observing network. *** #### Station Registry The station registry is the master list of stations in the network. At minimum, track: * station ID * station name * location * installation date * station status * data logger type * communications type * links to station documentation {% hint style="info" %} Use the same **station ID** across the station registry, metadata, maintenance records, component records, and data systems. Consistent identifiers make it much easier to connect information about a station over time. {% endhint %} Detailed information about site exposure, instrument heights, installation configuration, and other observational metadata should be maintained in the **Station Metadata** record. → [**Station Metadata**](/deploying-3d-paws/station-metadata.md) *** #### Station Status Tracking station status provides a quick overview of network condition and helps prioritize maintenance. Useful status categories may include: | Status | Meaning | | ------------------------ | -------------------------------------------------- | | **Active** | Station is operating normally | | **Offline** | Station is not currently transmitting or operating | | **Maintenance Required** | Station is operating but requires attention | | **Under Repair** | Maintenance or repair is in progress | | **Decommissioned** | Station is no longer in service | Organizations may adapt these categories to match their own operational procedures. *** #### Maintenance Records Maintain a history of station inspections, service visits, and repairs. Typical records include: * service date * technician or organization * issues observed * actions taken * components repaired or replaced * follow-up work required A maintenance history can help identify recurring problems and support troubleshooting and maintenance planning. → [**Station Maintenance**](/station-maintenance-and-operations/station-maintenance.md) *** #### Sensor and Component Tracking Sensors and other station components may be replaced several times during the life of a station. Track significant components such as: * temperature and humidity sensors * pressure sensors * wind sensors * rain gauges * optional environmental sensors * batteries * data loggers For each tracked component, useful information may include: * component type * manufacturer and model * serial number or other identifier, when available * station where installed * installation date * removal date * reason for removal * condition when removed * calibration or verification status, when applicable Recording installation and removal dates supports **Sensor Lifecycle Planning** and preserves the history of changes to the station. → [**Sensor Lifecycle Planning**](/station-maintenance-and-operations/sensor-lifecycle-planning.md) *** #### Spare-Parts Inventory Maintain an inventory of components available for maintenance and repair. Common spare parts may include: * sensors * cables and connectors * batteries * data loggers * communications hardware * mechanical assemblies * replacement 3D-printed components For each item, consider tracking: * component or part * quantity available * storage location * condition * compatibility or intended station type Maintaining appropriate spare parts can reduce station downtime when equipment needs to be repaired or replaced. {% hint style="info" %} Lifecycle planning can help determine which spare components should be kept available before they are needed in the field. {% endhint %} *** #### Calibration and Verification Records Some instruments require periodic calibration or verification. Examples include: * rain gauge calibration * distance sensor reference measurements * sensor verification checks Calibration or verification records should include: * instrument or component * date * method used * results * technician or organization * corrective action, if required Keep these records linked to the appropriate station and component. *** #### Station Documentation Each station should have associated documentation that can be located from the asset management system. This may include: * station metadata * installation records * site photographs * maintenance records * component replacement records * calibration and verification records Together, these records provide the operational history of the station. {% hint style="info" %} **Asset management and station metadata serve different purposes.** **Station metadata** describes the observing site, instrument exposure, and station configuration needed to interpret the observations. **Asset management** tracks the equipment, maintenance history, replacement history, and operational status of the station over time. {% endhint %} *** #### Managing a Network Over Time Review asset records regularly to identify: * stations requiring maintenance * components approaching planned replacement * recurring equipment failures * shortages of critical spare parts * calibration or verification needs * stations with incomplete records Keeping these records current makes it easier to plan maintenance visits, prepare replacement equipment, and manage the observation network over the long term. --- # 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/asset-management.md?ask=&goal= ``` `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.