IL Calculation Report
The purpose of this widget is to provide a visual display of complete and incomplete SIFs per a specific project and location. A link is provided in the widget that takes the user to the Incomplete SIFs report.
IL Rated Summary
The purpose of this widget is to display SIFs Related to a project within a location that have closed their respective gaps versus those that have not. A link is provided in the widget that takes the user to the IL Rated Summary report.
Project Journal
The purpose of this widget is to associate comments and files with categories. Users can log information that will be useful about the project history and upload supporting documents.
Cause Tracking
The purpose of this widget is to enable the user to track cause rates (assumed frequency vs actual frequency) within a location. Since causes are on AsBuilt equipment only, the project context when dealing with this widget should be limited to AsBuilt.
Demand Tracking
The purpose of this widget is to enable the user to track demand rates across protection layers within a location. Since demands are on AsBuilt equipment only, the project context when dealing with this widget should be limited to AsBuilt. A filter is provided to narrow the results to only SIFs’ or only IPL’s.
Demand Analyzer
The purpose of this widget is to display assemblies that are routinely tripping potentially resulting in problems. The Target, #/period column will show a calculated target based on the selected date range. Demand Count displays the total number of demands that occurred, or were ongoing during the selected date range and will be highlighted based on the following:
-
Grey if Count < Target
-
Orange/Yellow if Count = Target
-
Red if Count > Target
-
Dark Grey if IPL Target is not defined (Target will also have a '-' in it)
-
Moving Gradient indicates open ongoing event
The button ‘Configure Event Types’ enables users with system administration rights at the enterprise location to create and configure event types for use on both the Demand and Bypass Analyzer.
Spurious Trip Analyzer
The purpose of this widget is to display assemblies that are routinely experiencing spurious tripping. Data about the spurious trips is displayed by duration percent or count. Duration percent is the percentage of time the device was unavailable due to the spurious trip. This is calculated using the end date and period selected. The count displays the total number of times a spurious trip occurred during the selected time.
Bypass Analyzer
The purpose of this widget is display assemblies that are routinely in bypass potentially resulting in problems. Data about the bypass is displayed by duration percent or count. Duration percent is the percentage of time the device was unavailable during bypass. This is calculated using the end date and period selected. The count displays the total number of times the device was in bypass. The button ‘Configure Event Types’ enables users with system administration rights at the enterprise location to create and configure event types for use on both the Demand and Bypass Analyzer.
Failure Counts
This widget displays a summary of the failure date records that have been recorded and reviewed per location that a user has access to. Failures are divided into Safe Detected (SD), Safe Undetected (SU), Dangerous Detected (DD), and Dangerous Undetected (DU). The data is summarized based on the location tree, and the widget provides expansion similar to the location tree for enhanced visibility. Additionally, users have the choice to show failure records classified as "Systemetic" in the event that these failures are desired to be included in further analysis. Some key functionality to note about this widget:
-
The date range defaults to the past 30 days. To view a different period change the start and end dates.
-
Users can toggle 'Expand All' and 'Collapse All' by clicking on the "Location Tree" label.
-
For additional detail on individual records, and Excel export function it provided. This includes each failure record including component tag-names, date-time stamp and additional detail.
-
Remember that parent locations may have data recorded at their location, which may result in a parent have counts that are higher than the sum of the children locations.
-
For example in the image below the failure counts summarized at the MDS location include Failures from Isolated Cabin, Home Station in addition to failure recorded at the MDS location itself.
-