Currently eFactoryPro 3.0 allows for concurrent down ticket to be entered.
Since concurrent down tickets are being put into EFP 3.0, PowerBI is combining the downtime creating incorrect metrics. If a ticket is in on a down machine, EFP 3.0 should not allow another ticket with a malfunction to be created as there is already a down ticket active in the system.
Operations has decided that they want to allow concurrent malfunctions. eFactoryPro 3.0 flattens the downtime calculations PER TASK in order to remove duplicated periods of downtime.. However, overlapping malfunctions are allowed and aggregated from different tasks. The Portal informs users of overlapping malfunctions via the Malfunction tab of the Task, in order to prevent possible data issues.
-
Floyd commented
Can you elaborate on "flatten" calculations?
-
tommy commented
Site 213 has a similar issue.....