Strict resource group

A strict resource group is a type of resource group. Strict resource groups are generally ment to be used during the following conditions:

• Large amount of vehicles are to be measured in exactly the same way.
• The same WCU platform, modules, and WCU software version is installed in all vehicles.
• No deviations in WCU or Module configurations.

This allows for easy management of measurements in large fleets of vehicles at a cost of freedom in micromanagement. The strict resource groups system is built to be robust, and minimize the risk of usage error causing the measurements not to start.

A blue lock icon is used around the portal to indicate that a resource or resource group is strict.

Note: It is currently only possible to run Signalreader and SoH tasks on a strict resource group. This is intended to be expanded to more task types in coming versions of WICE.

Strict resource groups come with a number of features and limitations. A summary is provided here, with more in depth documentation below:

• All vehicles will automatically receive the same measurement tasks.
• All WCUs must have the same platform- and sub-type.
• All WCUs and modules will automatically receive the same configurations.
• All cars must have a SDDB file connected.

Note: If you want to temporarily change an individual WCU for some reason, you can remove it from the resource group at any time to make it editable. Don’t worry, the WCU will keep all measure tasks and configurations it had in the group.

Note: WICE does not support physically moving WCUs from one car to another while in a strict resource group. If you wish to do this, please remove the resource from the group, stop all potential tasks (and wait for the WCU to report them “Stopped”), physically move the WCU, wait for the WCU to acknowledge the new car in the portal, and then add it to the resource group again.

Measure task

One of the main features of strict resource groups is the automatic application of measure tasks to resources added. Since all resources in the group are forced to use the same platform type and configurations, the system can assure the task can run given that the hardware is in order.

Platform type

Strict resource groups need all WCUs in it to be of the same platform- and subtype. When a strict resource group is created, you must select the platform- and subtype. Only WCUs matching these types can be added to this resource group.

It is currently not possible to change the platform type of a strict resource group. If an administrator makes the group non-strict, the platform type can be changed in the configuration, and the group can be made strict again.

WCU and Module configuration

Strict resource groups atomically inherit WCU configuration and all Module configurations from the resource group. Unlike normal resource groups, there is no option to deviate from the configurations of the strict resource group.

These are applied automatically when the resource is added to the resource group.

Task Status for Task on Strict Resource Group

The status on a task created for a strict resource group will reflect the status of that task on all of the members of the resource group. See the table below for how the status of the strict resource group’s task is determined:

Status	Explanation
Pending	No child task running, but at least one is pending
Running	All child tasks are running
Partially Running	At least one child task is running
Warning	No child task running, pending or error, but at least one is warning
Error	No child task running or pending, but at least one is error
Stop Pending	No child task running, pending, warning or error, but at least one is stop pending
Stopped	All child tasks stopped

Icons will display to indicate if a status pending or partially running also contains an error or warning status.