This section covers the instructions on creating and managing "missions" on the Missions page in Logmore Cloud.
Missions are an important feature for most organizations. A mission can be set for a specific shipment or other contexts, where multiple loggers are associated with a single task at the same time.
A mission starts when their designated shipment begins and ends when the shipment is received by the recipient.
What are Missions?
Missions are a way to manage the data collected by your loggers. You can set up a mission to gather information from specific situation, for example an order or a shipment. Missions can include information such as alerts, reports and custom notes to the end user.
- A shipment ID for easy identification
- Alert limits — you can see if any alerts were triggered during the mission right after scanning the associated QR data logger
- A customized Scan Page that appears on the smartphone after scanning the logger, see how to Configure Scan Pages
- Custom fields — data fields that you can customize. Custom fields can be added to individual missions or mission templates. See more What are Custom fields in Missions?
- Mission reports:
- Mean Kinetic Temperature (MKT is calculated for each temperature channel in the mission)
- Scan locations
- Basics: start and stop, designated loggers, ID linking
- Mission alerting system
- Mission scan page customization
- Multiple loggers per mission
- Mission reports
- Mission presets for quick starting of missions
- Mission custom fields
One logger, multiple missions
A Logmore QR data logger be used in multiple missions and thanks to its small size, it is easy to send back to the sender. Every shipment is labeled as a "mission" in Logmore Cloud.
In the image above, we use an imaginary pharma company based in Helsinki but operating all over Finland as an example. The company has purchased Logmore QR data loggers and uses them to monitor their shipments of pharmaceutical goods. Each shipment is made a unique mission.
Mission 1: In February the company sends a large shipment equipped with QR data loggers from its main warehouse in Helsinki to Tampere warehouse.
Mission 2: In May the some of the QR data loggers used in Mission 1 are used in a smaller shipment from the Tampere warehouse to Turku.
Missions 3 & 4: In June the same QR data loggers are included as a part of a major shipment from the Turku warehouse to the Tampere warehouse, from where they are shipped directly to local retailers. However, during Mission 3, one of the containers has broken and the temperature of some of the products has risen above 25°C, potentially spoiling the product and therefore triggering an alert. Because of the alert, the employees at the Tampere warehouse know not to distribute any of the potentially spoiled goods, only the ones that are confirmed to still be OK.
Missions 5-7: By September, some of the QR data loggers have returned to the Tampere warehouse and are used again in a returning shipment to Helsinki. They are used once again in a new mission from Helsinki back to Tampere (alert again!), and again in the distribution to local pharmacies.
Starting a new Mission
- Go to the Missions page, located on the left-side panel of your Logmore Cloud.
- Click +New Mission and choose to continue without a template. This allows you to create a mission from scratch.
If you have created a Mission template suitable for the shipment, choose to create a Mission from it.
Fill in Basic Settings
- Enter a name for the Mission to make it easy to identify (for example, shipment number + destination).
- Select the loggers you want to include in the Mission.
- Create Alert rules, see .Getting started with alerts
If you have your own shipment IDs, we recommend entering them either as the Mission name or in the Mission notes field.
Fill in Advanced Settings
- (Optional) Click on Advanced settings and configure Mission timeline (the default is "now").
- (Optional) Add Custom fields. For details see What are Custom fields in Missions?
Set up Scan page config
- Check the box Auto-end mission on first scan if you want this mission to end after the logger has been scanned for the first time since the mission had started.
- Check the box Alert status to enable Scan page status alerts.
- In Infotext, add a text that is displayed on the Scan page. You can set different messages for the Scan page with or without alerts.
Use this function if the logger is scanned only on the recipient's end and not during the shipment duration.
Make these status alerts public if you want anyone outside your team using Logmore to see them.
For example, provide instructions on what should be done and who should be contacted when the mission has alerts. You can add instructions on how to return the logger.
Set Mission ending preferences for the Scan page
- Check the box "End monitoring” button to allow for the mission ending from the Scan page. The person scanning will see this button on the screen.
- Check Show alert status after mission ended and set the period for which the alert status page will appear. The person scanning the logger can see the alert status page for a specific time after the mission has been ended.
- Allow comments if the person scanning the logger should add information about the shipment.
Make this option public if you want anyone outside your team to end the mission.
Make the commenting public to allow anyone to leave comments from the Scan page without logging in.
For a mission with several loggers, scanning one of the loggers or pressing the “End monitoring” button after scanning will end this mission for other loggers attached to it. Enable Show alert status after mission ended for the receiver to see the alert status when scanning other loggers after the mission has been ended.
- In Permissions, define teams who can edit the mission and those teams who can only view the data.
- Check the box Public read access if you want anyone outside your teams to see the data connected to the mission (name, collected measurements, and timeline).
- Click Create.
Missions are either "ongoing" or "ended". Ongoing Missions are the ones currently active, while ended Missions are already over.
Like loggers, whole missions can now be made public. The setting for mission publicity is available in the "advanced" section at the bottom of the mission edit page.
The same rules apply to public missions as public loggers: if someone has the direct URL of the mission's page, they can read the data available on that page.
When creating a new mission you can set the mission to be automatically public if all the loggers included are already public. If they aren't, you can set the mission public after creating it by accessing the "edit mission" settings from the mission's page.
When you use the quick mission creation option, the mission will automatically be public if all of its loggers are.
Missions should only be made public if it is beneficial to the use case in order to maximize security. Keep security a priority and keep your mission data private unless your company benefits from customers, employees or other stakeholders having free access to it!