> For the complete documentation index, see [llms.txt](https://knowledgebase.flaik.com/flaik-knowledge-base/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledgebase.flaik.com/flaik-knowledge-base/for-hardware-specialists/getting-started/hardware-best-practice-operations.md).

# Hardware Best Practice- Operations

We recommend the following best practices for utilizing the flaik tags and/or scanners in the most efficient capacity possible for your resort operation-

* Nominate Specific users to interact with flaik hardware on a regular basis to maintain consistency, especially on peak days.
* Don't pre-assign tags to individuals, as this creates complexity on the morning of, opening the users up to making mistakes and creating bad Tag to student associations. (ie. more work for someone after classes are formed)
* Ensure your instructors check the status of their Tag, as well as any used by their students during the scan process. If a tag LED has not started pulsing green after being undocked, it is not communicating and the data for that tag will not compile or be complete for the day of use.
* Create a designated area near where tags are stored, to isolate hardware with identified issues.  If a Tag is found to not be functioning as it should, instead of returning it to the operational fleet, it can be isolated for investigation when time allows.  We recommend labeling issue tags, isolating with other non-functional hardware components, and reporting issues to flaik staff for review and troubleshooting.
* On exceptionally cold days(<10°), wait as long as possible before staging electronics outside, as extreme cold can cause electronics to perform sluggishly, especially scanners.  We recommend additional cold/wet weather steps in [this Knowledge Base article](https://flaik.freshdesk.com/a/solutions/articles/44002013563?lang=en).
* Any accessories have been provided intentionally to address a specific issue or to improve the user experience. Use provided accessories. (ie. scanner cover allows hand warmer to be inserted over the battery, preserving functionality on extremely cold days)


---

# 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://knowledgebase.flaik.com/flaik-knowledge-base/for-hardware-specialists/getting-started/hardware-best-practice-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.