Reliability Growth
About Data Mapped to the Baseline Analysis <Source Type> Window
When you create a Reliability Growth Analysis from a query or dataset, the Reliability Growth Builder will prompt you to map values from columns in the query or dataset to certain values in the Reliability Growth Analysis. The values that you select to map on the Select Data Fields and Provide Information For Downtime screens in the Reliability Growth Builder will then appear in the associated columns in the Baseline Analysis <Source Type> window. The <Source Type> is Query or Dataset on which your analysis is based.
This family is enabled for site filtering, which means that records in this family can be assigned to a specific site, and will then only be accessible to users who are assigned to the same site and have the appropriate license and family privileges. For more information, refer to the Site Filtering section of the documentation.
Details
The following table displays which columns are mapped from fields in the Reliability Growth Builder to columns in the <Measurement> Data window:
| Reliability Growth Builder Screen | Reliability Growth Builder Field | Baseline Analysis <Source Type> Window Column |
|---|---|---|
| Provide Information for Downtime | Downtime Field | Downtime |
| Select Data Fields | Asset ID | Asset ID |
| Select Data Fields | Date | Failure Date |
| Select Data Fields | Cumulative Operating Time | COT(units) |
| Select Data Fields | <Measurement> | <Measurement> |
| Select Data Fields | Installation Date | Installation Date |
About Interpreting Extrapolation Results
After you select an extrapolation method (by date or by amount of time), for each segment in the analysis, a dotted green line extends from the last failure date for that segment to the specified date in the future. The future date is calculated based on the date or time units you provided in the Select Extrapolation window. At the end of the dotted green line, a number appears, representing the estimated number of failures that would have occurred at that point in time.
A solid green line also intersects the end date for each segment, and the cumulative operating time at the end of that segment appears on the solid green line.
AMSAA Detailed Results (Non-Event)
The AMSAA Reliability Growth Model section displays the results of the Reliability Growth Analysis calculations. If the Reliability Growth Analysis has been split into multiple segments, a separate set of results will be displayed for each segment.
The AMSAA Reliability Growth Model section for an analysis based upon non-event data will look mostly the same as the AMSAA Reliability Growth Model section for an event-based analysis. Instead of showing the Initial Mean time Between <Measurement> and Final Mean time Between <Measurement>, however, the following items will be displayed:
- Initial <Measurement> Rate: Contains the <Measurement> rate, calculated from when the first datapoint is recorded for the segment.
- Final <Measurement> Rate: Contains the <Measurement> rate at the end of the segment.
Additionally, for an analysis that is based on data that includes cumulative operating time and does not include dates, references to dates will be displayed as the units you chose for your analysis (e.g., At 62 Months, the Cost Rate is 83.7040 Per Month).
AMSAA Detailed Results (Event-Based)
The AMSAA Reliability Growth Model section displays the results of the Reliability Growth Analysis calculations. If the Reliability Growth Analysis has been split into multiple segments, a separate set of results will be displayed for each segment. The labels on the AMSAA Reliability Growth Model section will look different depending on whether or not the analysis contains event-based data. If the data is event-based, certain labels will also look different depending on whether or not the data contains dates.
The AMSAA Reliability Growth Model section displays the following information:
- Initial Mean time Between <Measurement>: Contains the mean time between <Measurement> that was calculated at the beginning of the analysis, or the beginning of the segment.
- Final Mean Time Between <Measurement>: Contains the mean time between <Measurement> that was calculated at the end of the analysis, or end of the segment.
Additionally, for analyses based on event-based data that do not include dates, references to dates will be displayed as the units you chose for your analysis (e.g., At 303,156.00 Miles, the MTBF is 20,757.81 Miles).
<Measurement> Rate Trend
The <Measurement> Rate Trend graph displays the <Measurement> rate of a piece of equipment or location changes over time. This graph is the inverse of the Measurement Time between <Measurement> Trend graph. The datapoints represent observed <Measurement> dates included in the analysis. You can use the <Measurement> Rate Trend graph to view changes in the rate that <measurements> are occurring. You can also view the number of <measurements> occurring per day, rather than the number of days between <measurements>.
The following image displays a Failures Rate Trend graph:
Graph Features
While viewing the graph, you can:
-
Hover on any datapoint to view the coordinates and the details of a datapoint. You can view the number of cumulative <measurements> on the specified date, date of the observation, and <measurement> rate at the specified time.
Note: This feature may not be available on all devices. On tablets and smaller devices, you can tap on the datapoint to view the details of an observed datapoint. -
Select an observed datapoint to display the Point Tooltip window and view the data.
On the Point Tooltip window, you can:
- View number of cumulative <measurements> on the specified date, date of the observation, and <measurement> rate at the specified time.
-
Select Split to Split the analysis into segments.
Note: If you have already split the data, Split will be replaced with Merge. You can select Merge to merge the segments again. - Select the Go to Editor to access the Reliability Growth Data window, where you can modify the data.
- Customize the appearance of the graph by using standard graph features.
- Estimate how many <measurements> will have occurred at some date in the future.
MTB <Measurement> Trend
The Mean Time between <Measurement> Trend graph displays how the mean time between <Measurement> changes over time. The mean time between <Measurement> is calculated from the distribution of the <Measurement> over time. The datapoints represent observed failure dates included in the analysis. The Mean Time between <Measurement> Trend graph displays:
- How mean time between <Measurement> has decreased or increased over time.
- Whether the strategy changes have improved mean time between <Measurement> or not.
The following image displays a Mean Time Between Failures Trend graph:
Graph Features
While viewing the graph, you can:
-
Hover on any datapoint to access the coordinates and the details of a datapoint. You can access the number of cumulative <measurements> on the specified date, date of the observation, and mean time between <measurements> at the specified time.
Note: This feature may not be available on all the devices. On tablets and smaller devices, you can select on the datapoint to view the details of an observed datapoint. -
Select an observed datapoint to display the Point Tooltip window and access the data.
On the Point Tooltip window, you can:
- Access the number of cumulative <measurements> on the specified date, date of the observation, and mean time between <measurements> at the specified time.
-
Select the Split to Split the analysis into segments.
Note: If you have already split the data, the Split will be replaced with Merge. You can select Merge to merge the segments again. - Select the Go to Editor to display the Reliability Growth Data window, where you can modify the data.
- Customize the appearance of the graph by using standard graph features.
- Estimate how many <measurements> will have occurred (and what the MTB<measurement> would be) at some date in the future.
Cumulative <Measurement> Plot
The Cumulative <Measurement> Plot is a log-log graph with data overlay. The graph uses logarithmic scales on both the horizontal and vertical axes. The graph represents the cumulative <Measurement> as a function of the cumulative time (Cumulative Failures vs. Cumulative Operating Time), which is the total amount of time the Asset has been in operation since the start of the analysis.
The following image displays the Cumulative Failures Plot:
Graph Features
While viewing the graph, you can:
-
Hover on any datapoint to view the coordinates and the details of a datapoint.
Note: This feature may not be available on all the devices based on the screen resolution. On tablets and smaller devices, you can select the datapoint to view the details of an observed datapoint.- For an observed datapoint, you can access the name of the asset, date of the observation, cumulative time in the analysis at the specified time, and number of cumulative <measurements> till the specified date.
-
For a datapoint on the estimated data line, you can access the name of the segment, cumulative time at the selected point on the line, number of cumulative <measurements> at the selected point on the line, value of beta and lambda, and determine whether the analysis passed the GOF test or not.
You can also determine whether the analysis passed the GOF test by the color of the plot line. If the graph line is blue, it passed the GOF test. If the plot line is orange, it failed the GOF test.
-
Select an observed datapoint to open Point Tooltip window and view the data.
On the Point Tooltip window, you can:
- Access the name of the asset, date of the observation, cumulative time in the analysis at the specified time, and number of cumulative <measurements> till the specified date.
-
Select Split to Split the analysis into segments.
Note: If you have already split the data, Split will be replaced with Merge. You can select Merge to merge the segments again. - Select Go to Editor to access the Reliability Growth Data window, where you can modify the datapoint details.
- Customize the appearance of the graph by using standard graph features.
- Estimate how many failures will have occurred at some date in the future.
Examples for Reliability Growth
The following examples explain how a Reliability Growth Analysis can be used as an evaluation tool in different scenarios.
Example 1: Analysis Using Failure Event Dates
The following example demonstrates a scenario where you would create a Reliability Growth Analysis with event-based data that is measured using failure dates.
If you track events (e.g., safety events or failures) by specific date, then you can create a Reliability Growth Analysis using event-based data that is measured using failure dates.
Centrifugal Pump 1051700 was installed at the Springfield plant on July 20, 1998. Since its installation, the pump has failed several times, and each time the pump fails it is repaired immediately without any significant downtime. You have collected data noting which days the pump failed. You want to use the following data to perform a Reliability Growth Analysis to determine the mean time between pump failures.
| Failure Dates | Number of Failures |
|---|---|
|
12/14/1998 |
1 |
|
2/7/1999 |
1 |
|
6/26/1999 |
1 |
|
8/1/1999 |
1 |
|
9/5/1999 |
1 |
|
1/1/2001 |
1 |
|
1/2/2001 |
1 |
|
2/7/2002 |
1 |
|
7/11/2002 |
1 |
|
12/10/2002 |
1 |
|
5/12/2003 |
1 |
|
7/2/2003 |
1 |
|
11/28/2005 |
1 |
|
1/30/2006 |
1 |
In this case, you would use event-based data derived from failure dates to predict:
- The date when the pump will fail next.
- How many times the pump will fail by a certain date.
- If the number of failures increased or decreased as a result of a strategy change (e.g., a new preventative maintenance schedule), which was implemented after the failure on September 5, 1999.
Example 2: Analysis Using Cumulative Operating Time
The following example demonstrates a scenario where you would create a Reliability Growth Analysis with event-based data that is measured using cumulative operating time.
Sometimes the specific days on which a piece of equipment or location fails may not be available, or the piece of equipment or location may not operate for the same amount of time every day. In these cases, it would be more valuable to predict future failures using cumulative operating time (COT), or the amount of time the piece of equipment or location has been in operation.
Haul Truck 1 was purchased for a shipping firm as a used vehicle with 11,028 miles. The truck now runs varied routes depending on the number of shipments to which it is assigned. Because the truck does not always travel the same number of miles each day, you collect the data representing the mileage points at which the truck broke down. You want to use the following data to perform a Reliability Growth Analysis to determine the mean operating time (i.e., number of miles) between failures.
| Cumulative Operating Time (Miles) | Number of Failures |
|---|---|
|
27,393 |
1 |
|
41,675 |
1 |
|
60,400 |
1 |
|
66,128 |
1 |
|
72,132 |
1 |
|
77,314 |
1 |
|
113,888 |
1 |
|
146,671 |
1 |
|
205,424 |
1 |
|
224,624 |
1 |
|
243,841 |
1 |
|
260,828 |
1 |
|
279,951 |
1 |
|
303,156 |
1 |
In this case, you would use event-based data derived from cumulative operating time to predict:
- The mileage point at which the next failure will occur.
- How many failures will occur by a certain mileage point (e.g., five failures will have occurred after 1,000 miles).
- If the number of failures increased or decreased as a result of a strategy change (e.g., more routine oil changes), which was implemented after the failure at 77,314 miles.
Example 3: Analysis Using Grouped and Non-Event Data
In Examples 1 and 2, each datapoint represents a single measurement or failure. In some datasets, each datapoint may represent more than one measurement, or an amount of data. Throughout this documentation, this type of data is referred to as grouped data. To perform Reliability Growth Analyses on grouped data, when you create a dataset, you must use datapoints that represent multiple measurements or an amount of data. Datasets containing grouped data can be based on either failure dates or cumulative operating time.
For example, if you want to analyze a pump for which you record data every six months and every time you record data you record multiple failures (one datapoint represents multiple failures), you would create a Reliability Growth Analysis based on event-based, grouped data that is derived from cumulative operating time.
In Examples 1 and 2, each datapoint was also based on an event. Examples of event-based failures include equipment or location failures, safety incidents, or equipment or location repairs. Sometimes, you may want to perform a Reliability Growth Analysis on a variable that does not measure a specific event (e.g., an amount). For the correct labels to appear throughout the analysis, these datasets should be entered as non-event data. Datasets containing non-event data can be based on either failure dates or cumulative operating time.
Using a Reliability Growth Analysis to measure cost is the most common example of evaluating grouped data and non-event data.
The following example demonstrates a scenario where you would create a Reliability Growth Analysis with grouped data that is not event-based that is measured using cumulative operating time.
You want to measure the cost of equipment failures at the Springfield plant in order to determine how you should plan a budget for that plant in the future. Individual pieces of equipment fail at different rates, so you measure the total cost of replacement parts and mechanic labor for the entire plant every few months. You want to use the following data to perform a Reliability Growth Analysis to view the cost trends at this plant.
| Cumulative Operating Time (Months) | Cost |
|---|---|
| 6.5 | 1,120 |
| 13 | 996 |
| 17 | 1,052 |
| 23 | 1,085 |
| 37 | 1,075 |
| 49.5 | 1,096 |
| 62 | 1,001 |
In this case, you would use non-event, grouped data that is derived from cumulative operating time to predict:
- The repair costs that the plant will incur by some point in the future.
- If the repair costs have increased or decreased as a result of a strategy change (e.g., changing the mechanic who replaces parts), which was implemented after 23 months.
System Code Tables Used by Reliability Analytics
The following table lists the System Code Tables that are used by Reliability Analytics.
|
Table ID |
Table Description |
Function |
|---|---|---|
| MI_ACTION_TYPE | Action Type | Populates a list of options for the Action Type field in System Reliability records. |
| MI_CONDITION_MONITORING_TYPE | Condition Monitoring Type | Populates a list of options for the Condition Monitoring Type field in System Reliability records. |
| MI_RATE_UNITS | Rate Units | Populates a list of Rate Unit options for multiple System Reliability records. |
| MI_TIMEANAL_TYPE | Time Analysis Type | Populates a list of options for the Time Analysis Type field in System Reliability Analysis Definition records. |
| MI_TIME_UNITS | Time Units | Populates a list of Time Unit options for multiple System Reliability records. |
Reliability Analytics URLs
There is one URL route associated with Reliability Analytics: reliability. The following table describes the various paths that build on the route, and the elements that you can specify for each.
| Element | Description | Accepted Value(s) | Notes |
|---|---|---|---|
|
reliability/dashboard/<EntityKey>: Displays the Reliability Analytics overview page. | |||
| <EntityKey> | Specifies Asset context for the RA Overview page. |
Any numeric Entity Key that corresponds to an existing Asset. | Entering 0 for an Entity Key displays a generic RA overview. |
| reliability/automation/<EntityKey>/summary: Displays Automation rules. | |||
| <EntityKey> | Specifies which Reliability Automation Rules you want to view. | The Entity Key of the desired automation rule. | This parameter is required and it refers to the analysis. Without the Entity Key, then the URL will not be supported. |
| reliability/probability/<EntityKey>/<WorkspaceName>: Displays Probability Distribution Analyses. | |||
| <EntityKey> | Specifies which Probability Distribution you want to view. | The Entity Key of the desired analysis. | This parameter is required and it refers to the analysis. Without the Entity Key, then the URL will not be supported. |
| <WorkspaceName> | Specifies the type of Probability Distribution Analysis information you want to view. | cdfplot | Displays the CDF Plot workspace. |
| pdfplot | Displays the PDF Plot workspace. | ||
| probabilityplot | Displays the Probability Plot workspace. | ||
| summary | Displays the Analysis Summary workspace. | ||
| reliability/production/<EntityKey>/<WorkspaceName>: Displays Production Analyses. | |||
| <EntityKey> | Specifies which Production Analysis you want to view. | The Entity Key of the desired analysis. | This parameter is required and it refers to the analysis. Without the Entity Key, then the URL will not be supported. |
| <WorkspaceName> | Specifies the type of Production Analysis information you want to view. | overview | Displays the Analysis Summary workspace. |
| production-plot | Displays the Production Data workspace. | ||
| reliability/distribution/<EntityKey>/<WorkspaceName>: Displays Reliability Distribution Analyses. | |||
| <EntityKey> | Specifies which Reliability Distribution Analysis you want to view. | The Entity Key of the desired analysis. | This parameter is required and it refers to the analysis. Without the Entity Key, then the URL will not be supported. |
| <WorkspaceName> | Specifies the type of Reliability Distribution Analysis information that you want to view. | cdfplot | Displays the CDF Plot workspace. |
| failureprobability | Displays the Failure Probability workspace. | ||
| failurerateplot | Displays the Failure Rate Plot workspace. | ||
| pdfplot | Displays the PDF Plot workspace. | ||
| pmoptimization | Displays the PM Optimization workspace. | ||
| probabilityplot | Displays the Probability Plot workspace. | ||
| summary | Displays the Analysis Summary workspace. | ||
| reliability/growth/<EntityKey>/<WorkspaceName>: Displays Reliability Growth Analyses. | |||
| <EntityKey> | Specifies which Reliability Growth Analysis you want to view. | The Entity Key of the desired analysis. | This parameter is required and refers to the analysis. Without the Entity Key, the URL will not be supported. |
| <WorkspaceName> | Specifies the type of Reliability Growth Analysis information that you want to view. | failurerateplot | Displays the Failure Rate Plot workspace. |
| failuresplot | Displays the Cumulative Failures Plot workspace. | ||
| mtbfplot | Displays the MTBF Plot workspace. | ||
| summary | Displays the Analysis Summary workspace. | ||
|
reliability/spares/<EntityKey>/<WorkspaceName>: Displays Spares Analyses. reliability/spares/<EntityKey>/spareoverview/<SpareEntityKey>: Displays a Spare. reliability/spares/<EntityKey>/spareapploverview/<SpareEntityKey>/<SpareApplicationEntityKey>: Displays Spare Application. | |||
| <EntityKey> | Specifies which Spares Analysis you want to view. | The Entity Key of the desired analysis. | This parameter is required and refers to the analysis. Without the Entity Key, the URL will not be supported. |
| <WorkspaceName> | Specifies the type of Spares Analysis information you want to view. | overview | Displays the Analysis Summary workspace. |
| <SpareEntityKey> | Specifies which Spare you want to view. | The Entity Key of the desired Spare. |
This parameter is required and refers to the Spare. Without the Spare Entity Key, the URL will not be supported. Displays the Spare workspace. |
| <SpareApplicationEntityKey> | Specifies which Spare Application you want to view. | The Entity Key of the desired Spare Application. |
This parameter is required and refers to the Spare Application. Without the Spare Application Entity Key, the URL will not be supported. Displays the Applications section. |
|
reliability/system/<EntityKey>/<WorkspaceName>: Displays System Reliability Analyses. reliability/system/<EntityKey>/scenario/<ScenarioEntityKey>: Displays System Reliability Scenarios. | |||
| <EntityKey> | Specifies which System Reliability Analysis you want to view. | The Entity Key of the desired analysis. | This parameter is required and refers to the analysis. Without the Entity Key, the URL will not be supported. |
| simulation | Displays the Simulation Results workspace. | ||
| summary | Displays the Analysis Summary workspace. | ||
| <ScenarioEntityKey> | Specifies which System Reliability Scenario you want to view. | The Entity Key of the desired Scenario. | Displays the Scenario workspace. |
| Example URL | Destination |
|---|---|
|
reliability/dashboard/0 | Reliability Analytics Overview page. |
| reliability/automation/3228505/summary | Automation page with the Entity Key 3228505. |
| reliability/probability/3228505/summary | Probability Distribution page, displaying the Analysis Summary workspace with the Entity Key 3228505. |
| reliability/production/4924257/overview | Production Analysis page, displaying the Analysis Summary workspace with the Entity Key 4924257. |
| reliability/distribution/2842417/summary | Reliability Distribution page, displaying the Analysis Summary workspace with the Entity Key 2842417. |
| reliability/growth/2842411/summary | Reliability Growth page, displaying the Analysis Summaryworkspace with the Entity Key 2842411. |
| reliability/spares/2841956/overview | Spares Analysis page, displaying the Summary workspace with the Entity Key 2841956. |
| reliability/spares/2841956/spareoverview/2841957 | Spare Analysis Summary workspace with the Entity Key 2841956 and the Spare Entity Key 2841957. |
|
reliability/spares/2841956/spareapploverview/2841957/2841959 | Spare Critical Applications workspace with the Entity Key 2841956, the Spare Entity Key 2841957 and the Spare Application Key 2841959. |
|
reliability/system/3352307/summary | System Reliability page, displaying the Summary workspace with the Entity Key 3352307. |
|
reliability/system/3352307/scenario/3352304 | System Reliability Analysis page, displaying the Diagram workspace with the Entity Key 3352307 and the Scenario Entity Key 3352304. |
Reliability Growth Analysis Data Model
The following diagram shows how the families used in Reliability Growth Analysis are related to one another.
As you develop a Reliability Growth Analysis, you will create records in these families and link them together, either manually or automatically via the options in the GE Digital APM Framework. Throughout this documentation, we use the term Reliability Growth Analysis to mean the combination of the Reliability Growth record and all the records that are linked to it.
About Site Filtering in Reliability Growth Analysis
In Reliability Growth Analysis, the site is assigned based on the user's selection in the Site control.
Data for the analysis can be generated by a query that contains records from multiple sites. Analyses that are created for a single site and that are based on a query containing multi-site data will contain multi-site data. A single-site user with access to the analysis can open the analysis and view all of the multi-site data in an analysis.
A user that has been assigned, at a minimum, to all of the sites that are associated with the records queried by the analysis will have full access to modify the analysis. If this user reloads the analysis, the query will return data based on the sites that were assigned at the time the analysis was created.
A user that has not been assigned to all of the sites that are associated with the records queried by the analysis will be able to view the analysis, but will not be able to reload or edit the data.
Consider an organization that has three sites, Site X, Site Y, and Site Z. The following Reliability Growth Analysis records exist:
- Reliability Growth Analysis A: Assigned to Site X
- Reliability Growth Analysis B: Assigned to Site Y
- Reliability Growth Analysis C: Assigned to Site Z
- Reliability Growth Analysis D: No site assigned (global record)
Scenario 1: User assigned to only Site X
This user will see Reliability Growth Analyses A and D.
Scenario 2: User assigned to both Site X and Site Y
This user will see Reliability Growth Analyses A, B, and D.
Scenario 3: Super User
This user will see Reliability Growth Analyses A, B, C, and D.
Reliability Recommendation Records
Recommendation records in Reliability Analytics store details of a recommendation and the progress associated with getting the recommendation approved and implemented. The following table provides an alphabetical list and description of the fields that exist for the Reliability Recommendation family. The information in the table reflects the baseline state and behavior of these fields. This list is not comprehensive.
This family is enabled for site filtering, which means that records in this family can be assigned to a specific site, and will then only be accessible to users who are assigned to the same site and have the appropriate license and family privileges. For more information, refer to the Site Filtering section of the documentation.
| Field | Data Type | Description | Behavior and Usage |
|---|---|---|---|
| Alert Assignee When Due? |
Logical |
An option that lets you send an alert to the person responsible for implementing the recommendation. |
If this field is selected, the GE Digital APM system will send an alert to the person in the Assigned to Name field on the date defined in the Target Completion Date field. This field is labeled Alert Responsible Party When Due? and is available on the Alert tab on the datasheet. |
|
Analysis ID |
Character |
The ID of the analysis associated with the recommendation. |
This field is populated automatically with the Record ID of the analysis to which the Reliability Recommendation record will be linked when it is saved. |
|
Asset ID |
Character |
The ID for the Equipment associated with the recommendation. |
You can define this field by selecting <insert ellipsis icon> and searching for the required Equipment. You can then selecting the Equipment, then select OK to link it to the Recommendation. This field is labeled Equipment ID and is available on the General Information tab on the datasheet. |
|
Assigned to Name |
Character |
The name of the person responsible for ensuring the recommendation is implemented. |
This field contains a list of all Security Users in the database, presented in the following format: <last name>, <first name>, <user ID> This field is optional. You can select a user from the list. This field is available on the General Information tab on the datasheet. |
|
Author Name |
Character |
The name of the person proposing the recommendation. |
You can select a team member from a list of current human resources. This field is available on the General Information tab on the datasheet. |
|
Business Impact |
Character |
The impact to the manufacturing process during the recommendation implementation. |
You can choose this value from a list of the following options:
This field is available on the General Information tab on the datasheet. |
|
Completed |
Logical |
Indicates that the recommendation is complete. |
You can set this value to True to indicate that this recommendation is complete. |
|
Completion Comments |
Text |
Details about the completed recommendation. |
This field is required if the value in the Status field is Rejected, Cancelled,or Superseded. This field is labeled Close-Out Comments and is available on the General Information tab on the datasheet. |
|
Creation Date |
Date |
The date the recommendation was created. |
This field is disabled and populated automatically with the date on which the RA Recommendation was created. This field is available on the General Information tab on the datasheet. |
|
Date Reviewed |
Date |
The date the recommendation status was changed to Reviewed. |
This field is populated automatically with the current date when the Status field is updated to Reviewed. |
|
Days before Due Date to be Notified |
Number |
The numbers of days prior to the target date that the email message should be sent. |
This field is enabled only when the Alert Responsible Part When Due? field is set to True, in which case this field is required. This field is labeled Days before Due Date to be Alerted and is available on the Alert tab on the datasheet. |
|
Equipment Technical Number |
Character |
The technical number of the piece of equipment for which the recommendation is being made. |
When you select a value in the Equipment ID field, this field is populated automatically with the value in the Equipment Technical Number field of the associated Equipment. This field is labeled Technical Number and is available on the General Information tab on the datasheet. |
|
Final Action Taken |
Text |
The actions taken to implement the recommendation. |
You can define this field manually by typing a description of final actions in this field. |
|
Final Approver Name |
Character |
The name of the person responsible for approving the recommendation and the associated cost. |
This field contains a list of all Security Users in the database, presented in the following format: <last name>, <first name>, <user ID> You can select a user from the list. Note: An email alert will be sent only if the user specified in the Final Approver Name field has logged in to GE Digital APM system.
This field is available on the General Information tab on the datasheet. |
|
Frequency of Alert After Due Date |
Character |
The frequency after the target date that the alert will be resent. |
This field is enabled only when the value in the Alert Responsible Part When Due? field is True, in which case this field is required, and you can choose a value from the list of following values:
This field is available on the Alert tab on the datasheet. |
|
Functional Location ID |
Character |
The ID of the Functional Location that is either linked to the Equipment that appears in the Equipment ID field or linked separately to the RA Recommendation. |
This value is populated automatically if a Functional Location exists and is linked to the Equipment that appears in the Equipment ID field. You can also select <insert ellipsis icon> to search for the desired Functional Location, select it. When you select OK, the Functional Location is linked to the RA Recommendation. This field is available on the General Information tab on the datasheet. |
|
Implemented Date |
Date |
The date the recommendation was implemented. |
This field is populated automatically when the RA Recommendation is implemented. When this occurs, the field becomes disabled. This field is available on the General Information tab on the datasheet. |
|
Implementation Alert Text |
Text |
Text the user can add that will be sent in the body of the alert to the assignee to remind them the recommendation must be met by the target date. |
You can type the text you wish to appear in the Alert email. This field is available on the Alert tab on the datasheet. |
|
Mandatory Date |
Date |
The date by which the recommendation must be implemented. |
You can select a date using the Calendar tool. This field is available on the General Information tab on the datasheet. |
|
Recommendation Basis |
Character |
Background information about why the recommendation is being made. The reason the recommended action is needed. |
You can type any necessary background information in this field. This field is available on the General Information tab on the datasheet. |
|
Recommendation Closure Date |
Date |
The date the recommendation status is changed to Implemented, Rejected, or Superseded. |
This field is populated automatically with the current date when the value in the status field is changed to Implemented, Rejected, or Superseded. |
|
Recommendation Description |
Text |
A detailed description of the recommendation. |
You can type a description of the recommendation in this field. This field is available on the General Information tab on the datasheet. |
|
Recommendation Headline |
Character |
A brief summary of the recommendation. |
You can type a brief summary of the recommendation in this field. This field is available on the General Information tab on the datasheet. |
|
Recommendation ID |
Character |
The ID for the RA Recommendation. |
This field is populated automatically with a unique name (e.g., REC_888) when the recommendation is created. You can change this value if desired. This field is available on the General Information tab on the datasheet. |
|
Recommendation Priority |
Character |
A value that represents the priority or criticality level of the recommendation for implementation. |
You can chose from a list of the following values:
This field is available on the General Information tab on the datasheet. |
|
Reevaluate? |
Logical |
Indicates whether team members should evaluate the recommendation again. |
If this check box is selected, an alert will be sent to users specified in the Reevaluation Notification List field. This field is available on the Alert tab on the datasheet. |
|
Reevaluation Alert Body Text |
Text |
The message text in the body of the reevaluation alert, which will be sent to users in the reevaluation notification list. |
This field is enabled only when the Reevaluate? field check box is selected. Then the field is required. This field is available on the Alert tab on the datasheet. |
|
Reevaluation Notification List |
Character |
Individuals that will be sent to the reevaluation alert. |
This field is enabled only when the Reevaluate? field is set to True. Then the field is required. You can select from a list of names with Human Resources. This field is labeled Reevaluation Alert List and is available on the Alert tab on the datasheet. |
|
Reevaluation Date |
Date |
The date on which an alert is sent out to tell the alert recipient to re-evaluate the recommendation. |
This field is enabled only when the Reevaluate? field is set to True. Then the field is required. You can select a date using the Calendar tool. This field is available on the Alert tab on the datasheet. |
|
Required Equipment Status |
Character |
The operating status the piece of equipment must be under, in order for the recommendation to be implemented. |
You can choose from a list of the following values:
This field is available on the General Information tab on the datasheet. |
|
Reviewer Name |
Character |
The first and last name of the person who should review the information in the Recommendation before the recommended action is performed. |
This field contains a list of all Security Users in the database, presented in the following format: <last name>, <first name>, <user ID> You can select a user from a list of security users in the database. This field is available on the General Information tab on the datasheet. |
|
Status |
Character |
The status of the recommendation. |
You can choose from a list of the following values:
When the is created, the field is set to Created, but can be modified if needed. This field is required. You can send an alert only if the Status field is set to Approved or In Progress value. This field is available on the General Information tab on the datasheet. |
|
Status Changed By |
Character |
The ID of the user who last changed value in the Status field. |
This field is populated automatically when the Status field is updated. This value does not appear on the datasheet by Work default. |
|
Status Changed by Name |
Character |
The name of the person who last changed the Status field. |
This field is populated automatically when the Status field is updated. This value does not appear on the datasheet by default. |
|
Status Date |
Date |
The date the Status field was most recently changed. |
This field is populated automatically with the current date when the Status field is updated. This value does not appear on the datasheet by default. |
|
Target Completion Date |
Date |
The date the recommendation is intended to be implemented. |
You can select a date using the Calendar tool. This field is required. This field is available on the General Information tab on the datasheet. |
|
Work Order Number |
Character |
The ID of the work order arising from the work request. |
This field is populated automatically after a notification has been created in SAP. This value does not appear on the datasheet by default. |
|
Work Request Equipment |
Character |
The ID of the Equipment in SAP that is associated with the SAP Notification that was created. |
This field is populated automatically after a notification has been created in SAP. This field is available on the General Information tab on the datasheet. |
|
Work Request Functional Location |
Character |
The ID of the Functional Location in SAP that is associated with the SAP Notification that was created. |
This field is populated automatically after a notification has been created in SAP. This field is available on the General Information tab on the datasheet. |
|
Work Request Reference |
Character |
The ID of the SAP Notification. |
This field is populated automatically after a notification has been created in SAP. This field is available on the General Information tab on the datasheet. |
Measurement Data Records
<Measurement> Data record stores information about the Reliability Growth Analysis, which is a data format used to create a Reliability Growth Analysis. The following table provides an alphabetical list and description of the fields that exist for the Reliability Growth Analysis family, which appear when you manually enter data on the Reliability Growth Analysis window. The information in the table reflects the baseline state and behavior of these fields.
This family is enabled for site filtering, which means that records in this family can be assigned to a specific site, and will then only be accessible to users who are assigned to the same site and have the appropriate license and family privileges. For more information, refer to the Site Filtering section of the documentation.
Data for event-based analysis using failure dates
<Measurement Name>Tab
| Field Caption | Data Type | Description | Behavior and Usage |
|---|---|---|---|
| Asset ID | Character | The ID of the Asset that failed. | This value is mapped from a query or dataset or manually entered when you create the analysis. |
| Cumulative Time <units> | Number | The Cumulative Time to Failure, which is the total runtime for a population of Assets at the moment that a failure occurs in one of them. | Values in this field are calculated by the GE Digital APM system and are read-only. |
| Date | Date | The date on which the failure occurred. |
This value is mapped from a query or dataset or manually entered when you create the analysis and is required. If you delete a value in the Date field for an event-based analysis that is based on dates, when you select Finish, an error message will appear. |
| Downtime Units | Number | The amount of time that passed from the time the Asset failed until it was returned to service. | This information helps determine the total operating time of a piece of equipment or location. <Units> corresponds with the value selected in the Time Units list on the Provide Information for Downtime screen for the analysis. |
| Failures | Number | The number of failures represented by each datapoint. Cells in this column will contain the value 1 (one) by default, which indicates that the analysis data is not grouped, and one datapoint represents one failure. A value that is not equal to 1 (one) indicates that the analysis data is grouped, and each datapoint represents more than one failure or an amount of data. | This value can optionally be mapped from a query or dataset or manually entered when you create the analysis. |
| Ignore | Logical | A check box field that indicates whether or not the data on the selected row is ignored. | When selected, the data in the associated row will be excluded from the analysis. When cleared, data in the selected row will be included in the analysis. You can modify this value manually. |
| Remarks | Character | Comments about the failure. | You can enter a value in this field manually. |
| Segment | Logical | The segment to which the data belongs. | Values displayed in this field are read-only. |
| Time <units> | Number | The Time to Failure, which is the amount of time between the date the Asset was put into service until the date that it failed. If the data includes an installation date for the Asset , this value is calculated from the installation date. If the data does not include an installation date, this value is calculated from the first failure. <Units> corresponds to the value selected in the Operating Time Units list on the Time Unit field for the analysis. | This value is calculated automatically by the GE Digital APM system. If the value in this field is greater than the value in the GOF Statistic field, the Passed GOF field is set to True. |
Assets Tab
| Field Caption | Data Type | Description | Behavior and Usage |
|---|---|---|---|
| Asset ID | Character | The Record ID of the Asset that is being analyzed. | This value is mapped from a query or dataset or manually entered when you create the analysis. |
| Installation Date | Date | The date on which the Asset was installed. | This field appears only for analyses based on failure dates. This value is mapped from a query or dataset or manually entered when you create the analysis. |
| Last Replacement Date | Number | The last date or time at which the Asset failed. | Values in this column are calculated by the GE Digital APM system and are read-only. For data that contains cumulative operating time, this field is Last Replacement <Measurement>. |
Data for event-based analysis using cumulative operating time
<Measurement Name> Tab
| Field Caption | Data Type | Description | Behavior and Usage |
|---|---|---|---|
| Asset ID | Character | The ID of the Asset that failed. | This value is mapped from a query or dataset or manually entered when you create the analysis. |
| COT <units> | Number | The Cumulative Operating Time, which is the total amount of time that has passed since the Asset was placed into service. |
<Units> corresponds with the value selected in the Time Units list on the Select Data Fields screen for the analysis. This field is sorted in ascending order by default. This value is mapped from a query or dataset or manually entered when you create the analysis, and is required. Note: For analyses based on cumulative operating time, if the values in the Failure Date column are not in the same order as the values in the COT (units) column (e.g., if the Failure Date 1/1/2012 has a COT of 1000 and the Failure date 1/2/2012 has a COT of 990), when you select OK, a message will appear, stating that sorting cumulative operating time values from smallest to largest will result in failure dates that are not in order from earliest to latest. As a result, no dates will be shown in the analysis results; only cumulative operating time will be shown.
|
| Cumulative Time <units> | Number | The Cumulative Time to Failure, which is the total runtime for a population of Assets at the moment that a failure occurs in one of them. |
Values in this field are calculated by the GE Digital APM system and are read-only. Note: The Cumulative Time is the total runtime for a piece of equipment or location after the analysis has started. This may be different from the COT, which is the total runtime of the piece of equipment or location since it was created. In our example, the haul truck has a mileage of 11,028 before the analysis starts, and fails at a mileage of 27,393. The COT is the total mileage on the truck, 27,293. The Cumulative Time is the mileage the truck has run since the analysis started (27,393-11,028=16,365). If the piece of equipment or location is brand new (i.e., the truck has a mileage of 0), the Cumulative Time and the COT will be the same.
|
| Date | Date | The date on which the failure occurred. |
This value is mapped from a query or dataset or manually entered when you create the analysis and is required. If you delete a value in the Date field for an event-based analysis that is based on dates, when you select Finish, an error message will appear. This value is optional, but in order for dates to be displayed throughout the analysis, ALL failures must have a failure date. If one or more failure dates are missing, then no dates will be shown in the analysis; only cumulative operating time will be shown. For instance, in Example 2, the data does not include dates on which the haul truck broke down, so the analysis results will be able to predict the next failure in cumulative operating times only (e.g., the next failure will occur at 324,001 miles). |
| Failures | Number | The number of failures represented by each datapoint. Cells in this column will contain the value 1 (one) by default, which indicates that the analysis data is not grouped, and one datapoint represents one failure. A value that is not equal to 1 (one) indicates that the analysis data is grouped, and each datapoint represents more than one failure or an amount of data. | This value can optionally be mapped from a query or dataset or manually entered when you create the analysis. |
| Ignore | Logical | A check box field that indicates whether or not the data on the selected row is ignored | When selected, the data in the associated row will be excluded from the analysis. When cleared, data in the selected row will be included in the analysis. You can modify this value manually. |
| Remarks | Character | Comments about the failure. | You can enter a value in this field manually. |
| Segment | Logical | The segment to which the data belongs. | Values displayed in this field are read-only. |
Assets Tab
| Field Caption | Data Type | Description | Behavior and Usage |
|---|---|---|---|
| Asset ID | Character | The Record ID of the Asset that is being analyzed. | This value is mapped from a query or dataset or manually entered when you create the analysis. |
| Last Replacement | Number | The last date or time at which the Asset failed. | Values in this column are calculated by the GE Digital APM system and are read-only. For data that contains cumulative operating time, this field is Last Replacement <Measurement>. |
Data for grouped non-event based analysis
<Measurement Name> Tab
| Field Caption | Data Type | Description | Behavior and Usage |
|---|---|---|---|
| Cost | Number | The cost measured at each datapoint. For grouped data, values in this column represent the amount of data (e.g., cost) recorded between that datapoint and the previous datapoint. For non-grouped data, which is used in Examples 1 and 2, the values in this field are always 1 (one). For grouped data, the values can be greater than or less than 1 (one) but must be greater than 0 (zero). |
This value is mapped from a query or dataset or manually entered when you create the analysis. The name of this column depends on the measurement name you are using for your analysis. |
Assets Tab
| Field Caption | Data Type | Description | Behavior and Usage |
|---|---|---|---|
| Asset ID | Character | The Record ID of the Asset that is being analyzed. | This value is mapped from a query or dataset or manually entered when you create the analysis. |
| Installation Date | Date | The date on which the Asset was installed. | This field appears only for analyses based on failure dates. This value is mapped from a query or dataset or manually entered when you create the analysis. |
| Last Replacement | Number | The last date or time at which the Asset failed. | Values in this column are calculated by the GE Digital APM system and are read-only. For data that contains cumulative operating time, this field is Last Replacement <Measurement>. |
Growth Model Records
A Growth Model record stores information about the Reliability Growth model used to develop a Reliability Growth Analysis. The following table provides an alphabetical list and description of the fields that exist for the Growth Model family, which appear by default on the Growth Model datasheet. The information in the table reflects the baseline state and behavior of these fields.
This family is enabled for site filtering, which means that records in this family can be assigned to a specific site, and will then only be accessible to users who are assigned to the same site and have the appropriate license and family privileges. For more information, refer to the Site Filtering section of the documentation.
| Field Caption | Data Type | Description | Behavior and Usage |
|---|---|---|---|
| Analysis ID | Character | The name of the Reliability Growth Analysis. | This field is populated with the value in the Analysis ID field of the Reliability Growth record to which the Growth Model is linked. |
| Beta | Number | A value that represents the slope of the Cumulative Failures plot. | This feld is populated with the Beta value calculated by the GE Digital APM system. The Beta value indicates whether the MTBF is increasing, decreasing, or remaining constant. |
| GOF Critical Value | Number | The value used to determine whether the analysis passed the goodness of fit (GOF) test. | This value is calculated by the GE Digital APM system. If the value in this field is greater than the value in the GOF Statistic field, the Passed GOF field is set to True. |
| GOF Statistic | Number | A value that demonstrates the preciseness of fit. | This value is calculated by the GE Digital APM system. If the value in this field is less than the value in the GOF Critical Value field, the Passed GOF field is set to True. |
| Lambda | Number | The scale parameter that equals the Y-intercept of the Cumulative Failures Plot at time t =1. | This field is populated with the value calculated by the GE Digital APM system. |
| Model Start Date | Date | The date the model was started. | This field is populated with the start date of the segment. |
| Number of Failures | Number | The total number of failures in the dataset used to calculate the growth model. | This field is populated with the total number of failures in the Failure Data grid. |
| Offset | Number | The operating time offset for this model relative to the beginning of the analysis. | If there beginning operating time and the beginning observation time are the same, this field will be populated with 0. If there is a difference, this field will be populated with the difference between beginning operating time and beginning observation time. |
| Passed GOF | Logical | Indicates whether the model passed the Goodness-of-Fit test or not. | The analysis passes the GOF test when the value in the GOF Statistic field is less than the value in the GOF Critical Value field. |
| Sequence | Number | The chronological order of this model in the analysis. | This field is populated with the segment number that corresponds to the Growth Model record. If there is only one segment, this field is populated automatically with 1 (None). |
| Time Terminated | Logical | Indicates if the end date of the model is time-based. | If this field is set to True, then the end of the model is time-based. Otherwise, the end of the model is failure-based. |
| Total Observation Time | Number | The total amount of time that the equipment is in operation during the specified analysis period. | This field is populated automatically with the total operating time calculated from your dataset. This value appears in the Analysis Period section of the Reliability Growth page and is the t value in the AMSAA Reliability Growth Model. |
Reliability Growth Records
A Reliability Growth record stores information about an analysis that tracks changes in Mean Time Between Failure (MTBF) over a specified period of time to determine strategies or repairs necessary to increase the reliability of a product. The following table provides an alphabetical list and description of the fields that exist for the Reliability Growth family. The information in the table reflects the baseline state and behavior of these fields. This list is not comprehensive.
This family is enabled for site filtering, which means that records in this family can be assigned to a specific site, and will then only be accessible to users who are assigned to the same site and have the appropriate license and family privileges. For more information, refer to the Site Filtering section of the documentation.
| Field Caption | Data Type | Description | Behavior and Usage |
|---|---|---|---|
| Analysis End Date | Date | The date on which the Reliability Growth Analysis will end. |
This field is only used for analyses based on dates. This value is populated with the value in the End Date section of the Set Analysis Period window. This field does not exist by default on the Reliability Growth datasheet. |
| Analysis End Time | Number | The cumulative operating time at which the analysis will end. |
This field is only used for analyses based on cumulative operating time. This value is populated with the value in the End Time section of the Set Analysis Period window. This field does not exist by default on the Reliability Growth datasheet. |
| Analysis Name | Character | The name of the Growth Analysis. |
This field is populated with the value that you entered in the Analysis Name box when you save the Growth Analysis. This field does not exist by default on the Reliability Growth datasheet. |
| Analysis Start Date | Date | The date on which the Reliability Growth Analysis will begin. |
This field is only used for analyses based on dates. This value is populated automatically with the value in the Start Date section of the Set Analysis Period window. This field does not exist by default on the Reliability Growth datasheet. |
| Analysis Start Time | Time | The cumulative operating time at which the Reliability Growth Analysis will begin. |
This field is only used for analyses based on cumulative operating time. This value is populated automatically with the value in the Start Time section of the Set Analysis Period window. This field does not exist by default on the Reliability Growth datasheet. |
| Asset Installation Field | Character | The name of the field in the query or dataset that contains Asset installation data. |
This field is populated automatically with the value you select in the Installation Date list on the Select Data Fields screen in the Reliability Growth Builder when you create an analysis based on dates. This field does not exist by default on the Reliability Growth datasheet. |
| Date Based Extrapolation | Logical | Indicates if the user specified the extrapolation based on a date. |
If you extrapolate the analysis results based on failure dates, this value is set automatically to True. If you choose to extrapolate based on time or there is no extrapolation at all, this value is set to False. |
| Description | Character | A brief description of the analysis. |
This field is populated automatically with the value that you entered in the Analysis Description box when you save the Growth Analysis. This field does not exist by default on the Reliability Growth datasheet. |
| Downtime Units | Character | The units associated with downtime. |
This field is populated automatically with the value you select in the Time Units list on the Provide Information for Downtime screen when you create an analysis based on dates. You can select one of the following options:
This field does not exist by default on the Reliability Growth datasheet. |
| Extrapolated | Logical | Indicates if the analysis results will be extrapolated beyond the analysis end date. | If you choose to extrapolate the results, this value will be set to True. |
| Extrapolation Date | Date | Indicates the date and time you extrapolated the analysis. | If the Date Based Extrapolation field is set to True, this field is populated automatically with the date and time you extrapolated the analysis in the GE Digital APM Framework. |
| Extrapolation Time | Numeric | Indicates the total operating time that will be cumulated when the extrapolation point is reached. | If the Extrapolated field is set to True and the Date Based Extrapolation field is set to False, this field is populated with the cumulative operating time that corresponds with the extrapolation time you set in the Select Extrapolation window. |
| Failure Date Field | Character | The name of the field in the query or dataset that contains the dates on which the Asset failed. |
This field is populated with the value you select in the Date list on the Select Data Fields screen when you create an analysis based on dates. This field does not exist by default on the Reliability Growth datasheet. |
| Failure Number Field | Character | The name of the field in the query or dataset that contains the number of failures recorded at each measurement. |
This field is populated with the value you select in the <Measurement> list on the Select Data Fields screen when you create an analysis. This field does not exist by default on the Reliability Growth datasheet. |
| Failure Rate Plot | Binary | Contains an image of the <Measurement> Rate Trend plot. |
This field is used to display the <Measurement> Rate Trend graph in the Plots section in the Reliability Growth report. This field does not exist by default on the Reliability Growth datasheet. |
| Failures | Text | Contains the data that is displayed in the Reliability Growth Data window. |
This field is used to populate the Assets and <Measurement> Data sections in the Reliability Growth report. This field does not exist by default on the Reliability Growth datasheet. |
| Failures Plot | Binary | Contains an image of the Cumulative <Measurement> plot. |
This field is used to display the Cumulative <Measurement> plot in the Plots section in the Reliability Growth report. This field does not exist by default on the Reliability Growth datasheet. |
| Failure Time Field | Character | The name of the field in the query or dataset that contains the cumulative operating time at which the piece of equipment or location failed. |
This field is populated with the value you select in the Cumulative Operating Time list on the Select Data Fields screen when you create an analysis based on cumulative operating time. This field does not exist by default on the Reliability Growth datasheet. |
| Is Grouped Data | Logical | Indicates whether or not the data is grouped. |
If this value is True, the data is grouped data and contains more than one failure at each measurement. If this value is False, the data is not grouped and contains only one failure at each measurement. This value depends on the type of data that is mapped to the Failure Number field. This field does not exist by default on the Reliability Growth datasheet. |
| Is Non-Event Data | Logical | Indicates whether or not the data is event count. |
If this value is True, the data is not event count (e.g., cost). If this value is False, the data is event count (e.g., number of failures). This field is populated depending on the value you select in the Measurement Data Format section of the Select Data Format screen when you create the analysis. This field does not exist by default on the Reliability Growth datasheet. |
| Measurement Name | Character | The name of the data you are measuring throughout the analysis (e.g., cost, events). |
This field is populated automatically with the value you enter in the Measurement Name box on the Select Data Format screen when you create an analysis. After you create an analysis, you can change the value in the Measurement Name field via the Select Growth Data Format window. The measurement name is displayed throughout the analysis results. This field does not exist by default on the Reliability Growth datasheet. |
| MTBF Plot | Binary | Contains an image of the MTB<Measurement> Trend plot. |
This field is used to display the MTB<Measurement>Trend plot in the Plots section in the Reliability Growth report. This field does not exist by default on the Reliability Growth datasheet. |
Reliability Growth Folder
The Catalog folder \\Public\Meridium\Modules\Reliability Manager\Reliability Growth contains the following items.
|
Item Name |
Behavior and Usage |
|---|---|
| Queries Subfolder | |
| TileListOfReliabilityGrowth |
Returns the list of Reliability Growth Analyses in the Reliability Growth list on the RA Overview page. |