Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »


The main change in the SCM v2.22.0 release is the first step towards 3rd party device support.

Additional minor changes include:

  • Improvement how excursions from loggers are handled in situation where a shipment is manually delivered to a time prior to an excursion event.


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.

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 dedvices 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 the impact on users is non existing as this will only be accepted in limited capacity.


Excursion handling

We made minor updates with regards to have logger excursion events are displayed if a shipment is manually delivered to a time prior to the excursion taking place.

In the example above 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. This has been causing confusion for shipments similar to in the example above.

Moving forward, the Excursion Boundaries table will only show excursions that happened within the monitoring time resulting in the table to be displayed as below.


Please get in touch with me with any questions or concerns at ragnar@controlant.com

Kind regards,

Ragnar Gylfason
Product Manager, SCM

  • No labels