Asset Configurations

Machine Internal Design (MID) defines and groups the criteria used to diagnose faults for related machines. The MID is created in the ALERT database and includes the baseline criteria, component details, and machine train layout.  

MID information can be gathered using the Rapid Plant Setup mobile application.

An MID can apply to one or multiple machines.  All machines of the same MID are evaluated using identical component definitions and baseline criteria, thus all machines of the MID should be of the same make and model and operate using the same process.

The MID Completion Score (0-100) is a percentage scale to achieving the criteria for accurate automated (and manual) diagnostics.  The score is based on the completeness of the diagnostic baseline and component fault details such as fundamental forcing frequencies, speed change ratios, and consistent repeatable test criteria. 

This field is set using automation.

Once a completion profile has been achieved and the analyst has validated the best possible accuracy of the automated diagnostic engine, the MID profile can be locked to prevent changes and will be annotated as a Certified MID.

Operational Significant (1-10) is an asset rating to prioritize the importance of an asset to a process or production. 

Op. Sig. is set in the ALERT database with a default value of 10. 10 is highest significance.

This value is applied for business level metrics such as compound risk index.

Asset Category Tier (1-6) defines the asset complexity for analysis. 6 is the most complex.

Tier field is set and managed by a Program Manager and is used to categorize the expected level of effort required for an analyst to accurately identify fault conditions of the machine.  This value is used for generally used for service program pricing.

Service Level Agreement defines the requirements for analysis of diagnostic the diagnostic data collected from a machine. 

This field is set and managed by a Program Manager and is used to establish the expectations for what data is automated through the Expert Automated Diagnostic System, what is required to be reviewed by an analyst and the expected turn-around time.

Factors include data source type, tier, and fault reoccurrence. 

Data acquisition source type is the normal source of data collection: Online, Portable, or Wireless

This field is set in the ALERT database and is used for various reports and metrics as well as indication for collection on the TRIO data collector in the field.

Minimum Compliance Periodicity (MCP) defines the minimum periodicity expected to capture data or data exceptions for an asset to meet the compliance expectation.

This field is set in the ALERT database and is used for the compliance metric and the expectation of what's due on the TRIO portable data collector in the field.

The field is used as an expectation of data requirements for online and wireless systems independent of the actual frequency of collection. Example, "weekly" is the recommended MCP for wireless assets, meaning data is expected to be captured and reported upon at least once per week to meet the expectation, though the system attempts to collect data once a day.  If MCP is set to "Daily", any day that data is not captured for a machine, such as normal outage, the asset is marked as non-compliant.  

Wireless devices can be triggered to collected data based on a machine's is-running condition.

When enabled, the trigger will begin at the designated collection time of day and will evaluate the Acceleration (A-rms) scalar data to determine if the is-running condition is met before collecting the full diagnostic data. If the threshold does not achieve the level for the trigger, the sensor will remain armed for the next set of scalar data (hourly) to re-evaluate the running condition.

If disabled, the sensor will not validate running condition and collect diagnostic data based on the Collection Time of Day setting.

This field is set via the PredictivePortal Online System Configurations.

Defines the expected time of day an asset should be normally running for assets with wireless data sources.  All wireless devices associated with an asset will be triggered to collect diagnostic data when the time of day is met and is-running is triggered if enabled.

This field is set via the PredictivePortal Online System Configurations.