> For the complete documentation index, see [llms.txt](https://help.boomerang3.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.boomerang3.com/boomerang-3-user-manual/dashboard/missions.md).
# Missions
Registering data during a limited time.
Most objects have measuring points (MPs) that send readings continuously.
Sometimes you only monitor parameters for a limited time. Transport monitoring is a common example.
In Boomerang, this time-limited data is stored as a **mission**.
### Mission components
Missions use BTiny gateways and BTiny mission sensors (Mission Loggers).
To store mission data, create a **mission object** in the system. Assign **mission MPs** to the mission object.
Mission MPs can be:
* **Real mission MPs**: store readings received directly from BTiny mission sensors.
* **Virtual mission MPs**: store imported or moved mission readings.
### How mission measurements are registered
You can register mission measurements using:
1. **BTiny mission sensors.**
2. **Logger cards**.
#### **1. BTiny mission sensors**
BTiny mission sensors (Mission Loggers) are described in [ICU Scandinavia Transport Solution](https://icuscandinavia.se/transport-solution/).
* Sensors log temperature offline or online.
* The data is uploaded online, if the sensor is within range of a **Cloud Connector**.
* Readings are sent to the Boomerang 3 server and stored in **real mission MPs**.
* If needed, mission data can be moved from **real** to **virtual** mission MPs.
The BTiny temperature loggers are battery-operated.
They have an internal memory buffer for continuous logging during transport.
The logger communicates with the Boomerang cloud when it is within wireless range of a Cloud Connector.
BTiny temperature loggers can log temperatures from -196°C up to +120°C.
#### **2. Logger cards**.
Logger cards are described in [Logger cards documentation](https://help.boomerang3.com/logger-card-client-user-manual/).
* Logger cards register temperature offline.
* Readings are sent to the Boomerang 3 server using the Logger Card client application.
* Readings are stored in **virtual mission MPs**.
### Next steps
* Follow [BTiny Mission sensor usage](/boomerang-3-user-manual/dashboard/missions/btiny-mission-sensor-usage.md) to start and stop a transport mission.
* See [Mission handling](/boomerang-3-user-manual/dashboard/missions/mission-handling.md) for how mission objects and MPs are structured.
---
# 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://help.boomerang3.com/boomerang-3-user-manual/dashboard/missions.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.
