Table of Contents |
---|
Shipments view
Shipment view
Once a user selects a single shipment in the Shipments view, they are presented with a Single Shipment view.
...
The right side of the view is split into two views. The top view has 3 different tabs for 3 different views that display shipment information and the bottom view displays a map of the route. To see the whole top view, scroll down to the bottom.
Info tab
The first tab in the top view is the Info tab that shows shipment information and the operations that the user can perform on the shipment. The available operations are as shown on the image below.
...
While in the Info tab, it is possible to edit the Shipment Description. To do this, press the Pencil icon next to the Shipment Description in the top left corner of the Info screen.
...
Chart tab
The Chart tab shows the shipment measurements for a logger on a time series chart. Click here to read about the Chart tab in more details.
...
Data tab
The Data tab shows the shipment measurements for the selected logger(s) in a tabular format. Go here to read about the Data tab in more details.
...
The Properties tab shows the list of properties and their value(s) that have been added to the shipment.
...
Shipment actions
...
The user can perform different operations on the shipment depending on the state that it is in. If the shipment has not yet started, the user can manually override the start method of the shipment by pressing the Ship button. Then the user will be presented with a Ship shipment view where the shipping time is specified or the shipment is shipped now.
If the shipment has started, the user can manually override the delivery method of the shipment by pressing the Deliver button, after which the user will be presented with the Deliver view where the delivery time is specified or the shipment is delivered now.
When a shipment has been delivered, it is automatically closed once it has been processed if there are no medium or high excursions in the shipment. A shipment can be manually closed by pressing the Close Now button for as long as the quality of the shipment is not unknown. If the quality is unknown, then the shipment needs to be manually inspected.
The user can change the Shipment quality, Inspection status, and add Inspection comments in the shipment for as long as the shipment has not been closed. The user is presented with the Inspect Shipment view by pressing the Inspection button. The Shipment Inspection view is for quality assurance (QA) personnel to assess shipments in which loggers registered medium or high excursions as good or bad during transit. A customer using the Electronic signature option is required to add the password to complete the inspection. After clicking the Save button in the Inspect Shipment view, the customer is directed to the Electronic Signature Required view. In the Electronic Signature Required view, the user is required to give a reason for approving the shipment (Reason for Operation) as well as include the Username and Password, and press the Sign & Perform Action button. The user can review the raw command parameters and checksum of the action by clicking Show Raw Command Parameters and Checksum. For customers not using the Electronic signature option, the inspection can be saved without approval.
If enabled, Inspection Properties will be accessible in the Inspect Shipment modal. See below an example of an account with two inspection properties; Excursion Classification (enumerable) and Root cause (free text). Details on how to create and manage Inspection properties is accessible here.
...
The user can delete shipments that have not started and cancel shipments that are shipping, delivered, or closed. The user deletes a shipment by pressing the Delete button and confirms it by pressing the Confirm button. Deleting shipments that have not started is useful if mistakes were made when creating the shipment. Shipments are cancelled by pressing the Cancel button and the cancellation confirmed by pressing the Confirm button. Cancelled shipments are hidden, but can be found under the Search tab.
Rearming loggers
If you're a user with admin permission, you can reset boundary alarms. If a boundary has been triggered for a sensor, it can be reset in the Excursion Boundaries table in the single shipment view.
...
A boundary triggered by one or more loggers is indicated by a red exclamation icon. As a result, the boundary is no longer armed, meaning that the logger will no longer send alerts for this boundary. The icons for boundaries, both armed and unarmed, are a green check mark and a red x as shown in the image below.
...
Triggered and Armed statuses for boundaries assumes the "worst case" scenario from all loggers in the shipment.
For each boundary the following applies:
The boundary status is triggered if one logger in the shipment has triggered a boundary breach.
If one logger in the shipment is unarmed the boundary will also show as unarmed.
By clicking the + icon under the Details column, the information for individual loggers appear. They include information whether a particular logger is armed or not, and how many times each logger has triggered this particular boundary.
...
To rearm a logger or multiple loggers select the Rearm button.
...
Once the rearm button has been selected, it is possible to select the loggers that should be rearmed.
Simply tick the checkboxes next to the loggers you want to rearm, and select when the rearming should take effect in the drop-down menu, and press Apply (see image below).
A message will be sent to the loggers and the Armed status updated accordingly.
...
If the boundary for a logger is to be rearmed at a later time, a Clock icon will be shown indicating that the boundary will be rearmed at the set time (see image below).
...
When rearming boundaries, the logger can only receive the command to rearm a boundary when it wakes up. A wake-up only occurs on a preset interval, when a button is pressed on the logger, or if the logger detects an excursion. The earliest any further alerts can be issued by a rearmed logger is at its next wake-up, regardless of the delay selected. For example, if you select to rearm a logger immediately but the logger is not scheduled to wake up for 40 minutes, the earliest you can receive an alert is in 40 minutes time.
Note that when rearming a logger, the accumulative time limit will not be reset. This means that if the logger is still experiencing an excursion, an alert will immediately be issued when the logger wakes up and receives the command to rearm the boundary. Do resolve the issue causing an excursion before rearming the boundaries on a logger. Additionally, if the excursion has been resolved, but the logger detects conditions that breach the boundary, it will immediately issue an alert rather than waiting for the set time.
Request Report
When a shipment is closed a user can request a report in the Single Shipment view by clicking the Request Report button. Reports can be requested from shipments that are Shipping, Delivered and Closed. Pressing Request Report opens a modal where the user inserts an E-mail address and can choose to get extra data with the report by setting some Report config.
...
The Report config has default settings set by the customers administrator but can be overwritten by the user by changing the configurations in the modal.
...
The available configurations for the report are the following:
Timezone
Include in Report
Custom properties
Comments
Inspection comments
Attachments
PDF raw data
Excel raw data
...
Shipment Filter tabs
In the upper left corner of the shipments view, shipments can be filtered by the following 4 tabs:
Active
Inspection
Preparation
Closed
Search
Active
In the Active tab shipments that are currently shipping or are recently delivered can be seen.
...
When shipments start shipping they appear under Currently Shipping. When the shipments are delivered, they move from Currently shipping to Recently delivered.
They stay there until they are processed by the cloud, when they have been processed they are either closed automatically and moved to the closed tab, or moved to the inspection tab since. This depends on a customer setting where Shipments at or above a selected severity level will need to be manually inspected by a user. Shipments below the selected severity level will be automatically inspected and closed by the system.
Inspection
In the Inspection tab, shipments that have shipment quality set to undecided can be seen.
...
Shipments end up with quality set to undecided due to Medium and High excursions in the shipments. The shipments are split into 3 lists depending on whether they Need Inspection, are Being Inspected, or have already been Inspected (Not Closed).
Preparation
...
The Draft shipments remains as drafts until they are made Ready in the Shipment view. and the ready shipment will stay there until they ship with one of the start methods or by pressing the ship button in the shipment view.
Closed
In the Closed tab, shipments that have been closed can be seen.
...
Search
In the Search tab, the user can search for shipments that have certain parameters. Shipment searches are filtered by Time (Time Created, Time Shipped, Time Delivered and Time Closed) and the search period (From and To). It's possible to search for shipments by Status (Draft, Ready, Shipping, Delivered, Closed and Cancelled), Reference/name, Origin and Destination, Logger ID, Controlant Shipment ID, and Excursion Severity (No Excursion, Low, Medium, and High). The fields that are in bold are required. The search results are displayed below the fields after pressing the Search button.
...
...
Here below is the shipment status bar that appears in the single shipment view explained.
...
Shipment event types
In a single shipment view, under the Info tab, all events that occur from the time when a shipment is created and until it is delivered are displayed below the Event Log. Below is a list explaining possible events:
Excursion
Any excursions that may occur during the shipment, i.e. temperature going over the upper boundaries or under the lower boundaries. Upper and lower boundaries can be specified for the shipment.Start Button Pushed
The Start button was pressed during the shipment.
Stop button Pushed
The Stop button was pressed during the shipment.
Logger Enters Shipment Mode
The logger has entered shipping mode, i.e. the logger is being used in a shipment.
Logger Enters Standby Mode
Logger has entered standby mode, i.e. the logger is not in use.
Logger At Origin
Logger is at a shipment origin location.
Logger At Destination
Logger is at shipment delivery location.
Logger En Route
Logger in a shipment is on a shipping route.
Shipment Created
Shipment was created at this time.
Shipment Shipped
Shipment was started at this time.
Shipment Delivered
Shipment was delivered at this time.
Shipment Closed
Shipment has been closed after delivery.
Shipment Cancelled
Shipment was cancelled, either before the shipment was shipped or after a shipment was closed.Lights Off
Lights were turned off in the shipment. An event that happens when a logger in a shipment is placed in dark space, for example, inside a sealed box after being exposed to bright lights.Lights On
Lights were turned on in the shipment. An event that happens when a logger in a shipment is affected by light, for example, when a logger is inside a sealed box and the box is exposed to bright lights.
...
Logger filter in Event Log
It is possible to filter the Event Log by selecting logger(s) in the filtered Logger list.
...
The user selects loggers by clicking on the downward-facing black arrow (to the right of the Logger list).
Select one or more loggers.
N/A are shipment events that are not tied to a specific logger, for example, Shipment Closed.
If no selection is made all events are displayed.
...
Light Events
By default the Light events are hidden in the SCM UI. They can be displayed by checking the checkbox Light events in the Single Shipment view to the right of the Event Log title.
...
If Light events are displayed, they also appear in the chart under the Chart tab.
...
Info |
---|
Can’t find what you’re looking for?Visit our new Support Center! |