Release 10.10.0.3
This release of the OEE App is addressing UI fixes and improvements as well as fixes of the OEE calculation.
Improvements
| Component | Description | Issue |
|---|---|---|
| UI | Until now, all profiles needed a 10 min (600s) default calculation interval. If this interval was not configured for the calculation profile, it was automatically added by the OEE application. With this change, it is now possible to define a default calculation interval for each profile, which will be used on the machine park overview. Calculation profiles created before this change will be migrated to use the 10 min interval as their default interval. With this change it is now also possible to reduce the number of MEAs created for the calculcation profiles. For slow producing machines, it might, for example, not be required to create a measurement every 10 mins. |
COE-443 |
| UI | The rule validation has been significantly improved for the Matching dialogs in the profile editor. The new validation now evaluates the type of calculation step to derive the type of the output of the whole formula. This type is compared with the expected output and errors are reported inline in the rule editor. | COE-441 COE-508 |
| UI | It is now possible to assign machines to multiple organizational units (such as Lines, Areas, or Sites). The dialog for assigning (adding) machines to an organizational entity now lists all unassigned machines before listing the machines already assigned to any other entity. Parent organizational entities of all assigned machines are presented in the entry selection. | COE-547 |
| UI | The drag-and-drop option in the Organization Admin section has been enabled by default, but is now limited to reordering entities within its parent entity. The switch to enable the drag-and-drop option in the list header has been removed. | COE-609 |
| UI | In the machine dashboard, showing alarms in the OEE data chart can now be optionally disabled. To control the visibility of alarms in the chart, a new switch was added at the bottom of the Legend of the chart. Additionally, the number of alarms loaded in the machine dashboard was optimized to improve performance. | COE-338 COE-499 COE-510 |
| UI | When choosing the calculation method in the Matching dialog of the profile editor, the entire tile can now be clicked to select a calculation method. | COE-340 |
| UI | After creating a new calculation profile and loading a configuration from an existing profile, it is now possible to remove and assign a different machine to the calculation profile. When assigning a new machine to a calculation profile the mappings in the matching configurations are validated. If the subscriptions of the old and new machine match, calculation rules in the Matching dialog will be migrated to the new machine. No manual changes are required. If the subscriptions do not match, an alert will be presented and the Matching tab as well as the profile itself will show as incomplete and require manual updating. | COE-349 |
| UI | For configuration of matching rules for calculation profiles, it is now possible to refer back to the length of the calculation interval. This is required for some availability and performance calculations (for example, when calculating the actual production amount based on a flow rate). The Interval Length can now be selected from the drop-down menu in the dialog. |
COE-541 |
| UI | The OEE App was updated to Angular 11 and Cumulocity WebSDK 1011.0.15 | COE-477 |
| Microservice | Upgraded Apama to 10.7.2.5. | COE-556 |
Fixes
| Component | Description | Issue |
|---|---|---|
| Microservice | When using calculation categories, for all categories the formula of the first category was used, leading to incorrect calculation results. The calculation of categories has now been fixed. | COE-584 |
| Microservice | When using line profiles, the subscriptions for MEAs were not created correctly and OEE calculation was not performed. This issue is now resolved, subscriptions are created for the calculation profiles to fix the OEE calculation of line profiles. | COE-532 |
| Microservice | Formulas defining machine status and quality status conditions were not properly deleted. This led to problems when switching off machine status and quality status calculation. A similar problem occurred when enabling categories on a profile using machine and quality status calculations. This issue has been fixed, the formulas are now deleted correctly. | COE-543 |
| Microservice | Using Measurement count in calculation rules was fixed to now start the calculation correctly. | COE-544 |
| UI | The Andon board was fixed to include the default interval in the dropdown to switch between resolutions. This issue is related to COE-443. | COE-385 |
| UI | The data chart on the machine dashboard was fixed to use the correct UTC start date depending on the actual time zone. The wrong start date led to data gaps in the chart at the beginning of the selected timeframe. Also the data chart now includes the last measurement before the selected timeframe to ensure measurements are displayed for the entire selected timeframe without any gaps at the beginning of the selected timeframe. | COE-489 COE-524 |
| Microservice | New Rest API endpoints have been added to allow the deletion of shift plans for a location and production plans for a device. See documentation at https://cumulocity.com/api/oee/. | COE-527 |
| Microservice | Using calculation categories it is possible to define multiple formulas for the same input (for example, for availability loss to track different loss reasons). The results of the different formulas are aggregated to a total value. The calculation for categories has been fixed to not only store the total value, but also store and show the individual values used to calculate the total value. | COE-539 |
| Microservice | Calculation for availability and quality losses was fixed when using status events to treat the conditions as amount and not as loss definitions. | COE-540 |
| UI | When adding machines to an organizational unit, it is now only possible to add machines with complete calculation profiles. Machines with incomplete calculation profiles are filtered from the list of available options. | COE-589 |
| UI | The machine dashboard now loads all measurements using type=OEEMeasurements at once to optimize performance and reduce number of data loading request. |
COE-554 |
| UI | When editing a Matching rule of a calculation profile, the title now contains the selected type of rule. | COE-578 |
| UI | Missing translations have been added to the dialogs used to add entities to organization units. | COE-586 |
| UI | In the machine park overview, the detailed description for each organization unit is now displayed directly under the name of the unit, changing the order with the last update date. | COE-588 |
| UI | Fixed header misalignments in the Admin section profiles list. | COE-605 |
| UI | When the quality status events are used to calculate the quality component of OEE, events are created in Cumulocity IoT to indicate if the quality is OK. The events are now correctly created on the calculation profile, instead of the machine, as this has lead to confusion for machines with multiple profiles and potentially different quality criteria. | COE-480 |
| UI | The formatting of dates has been fixed and unified. The dates are now correctly presented using the selected user locale. | COE-509 |
Release 10.10.0.2
This release of the OEE App addresses all microservices to resolve log4j security vulnerabilities CVE-2021-44228 and CVE-2021-45046.
Fixes
| Component | Description | Issue |
|---|---|---|
| Microservice | Mitigate log4j exploit by upgrading Apama to 10.7.2.4. | COE-503 |
Release 10.10.0.1
This release of the OEE App fixes important calculation issues and brings a set of UI improvements and enhancements for icons, dashboards, charts and the profile editor.
Important
All OEE values and parameters calculated per calculation interval are now stored as fragments in one single measurement instead of 20 measurements. With this change, the number of measurements created by calculation interval is significantly reduced.
Fixes
| Component | Description | Issue |
|---|---|---|
| UI | Enabled custom tenant UI branding. The OEE App now automatically uses the tenant's branding configuration to enable customization of colors, fonts, logos, and so on. For more information on Cumulocity IoT branding configuration, see Enterprise tenant > Customizing your platform > Branding in the User guide. | COE-350 |
| UI | When creating a new OEE calculation profile, a list of existing calculation profiles is presented to optionally choose to copy an existing configuration into the new calculation profile. An issue has been fixed causing the list of existing calculation profiles to not show in some situations. | COE-321 |
| UI | The OEE App is sending OEERestartInformation alarms when the calculation is started or stopped. An issue has been fixed sending OEERestartInformation alarms also when creating or saving a calculation profile. | COE-352 |
| UI | In Safari browsers, the gauge charts in the OEE status of machine dashboards and Andon boards have been fixed to render correctly. | COE-363 |
| UI | Gauge charts in the OEE status of machine dashboards and Andon boards have been fixed to render correctly for values greater than 100. | COE-376 |
| UI | The OEE targets in the overview show trend arrows next to the OEE value indicating if the OEE trend is going up or down. An issue has been fixed breaking the correct calculation of the trend, so even if a trend arrow is presented it might not have represented the calculated trend. Also a new trend array (right) has been introduced to indicate trends without a change. | COE-416 |
| Microservice | The Availability for an interval is now always calculated with the first measurement, event or alarm (MEA) after the interval ended and does not require explicit status change events, such as machine up or down events. Depending on the status changes received for machines, it was possible to not see any OEE being calculated at the end of each calculation interval or even for multiple intervals. | COE-335 |
| Microservice | Store only 1 measurement with type="OEEMeasurements" including all calculated OEE values and parameters as separate fragments for each calculation interval. This reduces the number of measurements created per calculation interval from 20 to just 1. OEE measurement queries should be updated to use type="OEEMeasurements" instead of quering for types or valueFragmentType. The OEE application itself supports both variants of measurements and will continue to work as expected.
|
COE-387 |
| Microservice | The accuracy and rounding of Quality calculation has been fixed. Even for an expected Quality of 100.0, the calculated Quality value might have slightly deviated. In the past, the calculated Quality value might have slightly deviated from the expected value causing a Quality value in excess of 100.0. and an OEECalculationAlarm. | COE-351 |
| Microservice | Improved and optimized logging of HttpErrors logged by the GeneralErrorHandler in logs of the apama-oeeapp microservice. | COE-420 |
| Microservice | Improved and fixed the REST API documentation for the oee-bundle microservice. Documentation is now available as OpenAPI at https://cumulocity.com/api/oee/10.10.0/ | COE-195 |
| Microservice | Fixed REST API error handling and error messages. Error responses might have contained unnecessary information or could have used different formats. | COE-268 |
| Microservice | Fixed and improved the performance and scalability of microservices. The main fixes are related to the oee-bundle microservice. | COE-358 |