SCM v2.22.0 Release Announcement
- Ragnar Gylfason (Deactivated)
The main change in the SCM v2.22.0 release is the first step towards 3rd party device support.
Additional minor changes include:
Improve how excursions from loggers are handled when a shipment is manually delivered to a time prior to an excursion event.
Minimum and maxium recorded temperatures displayed in the shipment detail view.
Improved user feedback when duplicating a shipment containing inactive loggers.
Provide the user with warning when requesting a shipment report if the shipment is missing data.
3rd party device support
Description: Controlant is taking the first step to support data from 3rd party devices. At first, the support will be limited to a specific provider and a specific device for a defined project.
The bulk of the changes will be outside the SCM solution but a couple of changes needed to be made for the SCM solution to ensure expected functionality.
New requirements:
SCMRS-551: SCM will not allow users to manually create new shipments with 3rd party devices.
SCMRS-552: SCM will not allow users to duplicate shipments with 3rd party devices through SCM UI.
SCMRS-553: SCM will not allow users to add 3rd party devices to existing draft shipments through SCM UI.
SCMRS-554: The system will consider it to be a missing data point if the time period between two measurements is more than the sampling rate plus 30 seconds.
Impact:
SCM will accept and be able to handle data from 3rd party devices. For most users there is no impact.
Min/Max shown in shipment view
This is the first (mini) step of bringing more data to the shipment view.
The minimum and maximum temperature values are one of the first data points that Quality Release look at when determining if a product can be released to market.
This information has been available in the pdf shipment reports that are generated at the end of the shipments, but is now available in the UI from the time logger starts reporting after the shipment is started.
New requirements:
SCMRS-555: User can see the minimum and maximum recorded temperature values across all loggers in the shipment detail view.
Impact: This information will be available to all users with access to the shipment. No change in how the system is used. This additional information can be leverage as needed by the users.
Excursion handling
We made minor updates with regards to how logger excursion events are displayed if a shipment is manually delivered to a time prior to the excursion taking place.
In the example, the logger was removed from the product, but the shipment wasn’t delivered. The temperature increased, resulting in an excursion. The shipment is later manually delivered at the time when the logger was detached from the product. This leaves the excursion, as shown in the image above, outside the monitoring period.
Previously, SCM was accounting for all excursions reported from loggers paired with the shipment and showing the excursions as triggered (see below image). This has been causing confusion for shipments similar to the example above.
The Excursion Boundaries table will now only show excursions that happened within the monitoring time resulting in the table being displayed as below.
User feedback if shipment is recreated with recalled/disabled loggers.
We are currently duplicating a lot of shipments and we are discovering ways we can improve that process and hopefully reduce the need to duplicate in the first place.
There was an urgent need to act quickly, as loggers that are not Active (disabled or recalled) are removed from the duplicated shipment. There are checks to ensure shipments are not created with inactive loggers and duplicating a shipment is indeed creating a new shipment.
However, it is not the simplest task for the user to detect this removal of loggers from the shipment and this has led to cases where a shipment arrives and a report is generated but missing a logger without an explanation.
To mitigate this we added two steps.
First, there is an error message in the pop-up modal.
Second, after the logger has been removed there will be an empty logger slot, indicating that there should have been a logger which is no longer there and preventing the user to immediately Ready the duplicated shipment without tending to the empty logger slot.
Warning when manually requesting report with missing data.
It was identified as a risk for a couple of customers that users might request a shipment report through the SCM UI wihtout realising the the shipment is missing data.
The shipment report does not yet reflect this status. To minimize risk and clarifying the status the following message was added to the request report modal.
Please get in touch with me with any questions or concerns at ragnar@controlant.com
Kind regards,
Ragnar Gylfason
Product Manager, SCM