top of page
  • Andrew Lewis

Building The Asset Hierarchy For Your Monitron Pilot

An Asset Hierarchy is Key for Workflow Productivity...

For large operations, it is unlikely that its asset hierarchy will match the limited number of levels in a PdM plaform. So a naimg convention will have to be set up. And, its best to have this set up outlined before actual sensor installation on assets. The challenge is creating an naming methodology that fits within these reduced levels and is intuitive for matinenance technicans using the dashboard.


WHY IT MATTERS: Asset naming has a big impact on both the setup and operation of a PdM platform. For setup, assigning names can be difficult and a laborious process. For operations, a consistent naming convetnion requires intuitive design that will be descriptive for technicians but will fit within the rules of the platform itself. Design as naming system that will work at scale.


NOTE: Use the Monitron documentation as your primary reference [ref]. The following tips are meant to be supplemental.


The approach below of naming and installation approach is for Amazon Monitron, but applies to any PdM system.


STEP 1: Build an asset name hierarchy

  • The hierarchy is important becuase it is used to display sensor names in the Monitron dashboard.

  • Layout your hierarchy, not just for the pilot but also for deployment across sites, total operation. It should use common wording and be easy to interpret and navigate for mainentance technicians.

  • Given the rules of naming in the dashboard entry, it is unlikely the hierarchy for the Monitron dashboard will match your existing asset heirarchy.

  • Name heirarchy will match thes levels:

  • AWS Account > Project Name > Site Name > Asset Name > Position Name

  • AWS Account info does not show in the dashboard.

Quotas in Asset Hierarchy

  • Name Quotas:

  • Accounts – Assign an account per geography or region will allow more flexible use of the names below.

  • Projects – For smaller customers, all assets can be directly managed within a project. User can choose to bypass the site layer.

  • Sites – For larger customers, multiple sites can be created under a project and each project managed separately as a combination of sites.

  • Asset Layers – Sensors paired to different Positions on Asset Multiple sensors can be paired to multiple different positions of an asset or asset group. Creative use of names can greatly expand sensors per site. But it would be difficult to allocate names with subtle changes in wording. Best use of position names is for axis placement, multiple bearing locations and maybe an electric motor driving a pump (as shown in the photo above where a common asset with two positions: motor and gearbox).

  • Monitron is only supported in two regions [ref]:

  • Using the above name quotas, craft a hierarchy spreadsheet with column headers that correspond to the above layers (except Account). Add names to create the hierarchy. This will speed the building of the hierarchy and help names to be defined in a more intutive way. The spreadsheet will speed that process of sensor pairing described in Step 2 below.

Sample Asset Hierarchy in the Monitron Dashboard


STEP 2: Pair sensors to the cloud

  • Sensor pairing to the cloud is done with a smartphone that connects each sensor to the AWS cloud through a gateway that is connected to the internet [reference].

  • There are two ways to perform the sensor pairing:

  1. Monitron documentation suggests it be done at the asset location, the time of installation. This works great except for noise, safety and delays operating in a production environment.

  2. Our approach is more productive – do the pairing of all sensors in a conference room or at a workbench.

  3. Using the hierarcy spreadsheet, add a column that assigns a unique number to each sensor, eg, 1 to 50, and its asset name description.

  4. Unbox all Monitron sensors and using a black marker, write a unique number on the top case of each sensor, eg, 1 to 50.

  5. Then pair each sensor and assign it the name hierarchy matching it's number.

  6. Must have a gateway operating in proximity of the sensor.

  7. Confirm sensor name and operation in the Monitron dashboard.

STEP 3: Physically attach sensors to assets and positions

  • Check that gateway(s) are installed within 20-30 yards of sensors [ref].

  • It is not necessary for the same gateway used in pairing to be used for final connection.

  • At each asset, locate the sensor that matches number on hierarchy spreadsheet.

  • Install (Mount) sensors on assets that have matching numbers [ref].

  • Confirm sensor operation in dashboard [ref].


PRIOR POST: Asset Selection for Your Monitron Pilot

NEXT POST: TBD

 

GetIQ.ai is a blog about building AI solutions for augmenting decision making and empowering people that make them. It's authored by the engineers at DecisionIQ.


ABOUT DECISIONIQ: We are "boots on the ground" factory engineers expert at the adoption of AI and machine learning into operations. As consultants and system integrators we bring our experience in a mix of a well structured programs that enable our clients to produce winning results and maximum ROI. You will learn to use AI to build competitive advantage by increasing plant uptime, quality and yield. With 24 POCs, Pilots and 16 deployments we have achieved for our client’s ROIs as high as 60x and a cumulative $22 million in savings.


AN AWS PARTNER: We provide capability in design of AI solutions for industrial applications. We work with the AWS Industrial IoT services stack, cloud migrations and Amazon Monitron Pilots and deployments. For qualifying customers, many of these capabilities are eligible for AWS subsidized funding.


©Copyright 2023, DecisionIQ, Inc.



21 views0 comments
bottom of page