element14 Community
element14 Community
    Register Log In
  • Site
  • Search
  • Log In Register
  • Community Hub
    Community Hub
    • What's New on element14
    • Feedback and Support
    • Benefits of Membership
    • Personal Blogs
    • Members Area
    • Achievement Levels
  • Learn
    Learn
    • Ask an Expert
    • eBooks
    • element14 presents
    • Learning Center
    • Tech Spotlight
    • STEM Academy
    • Webinars, Training and Events
    • Learning Groups
  • Technologies
    Technologies
    • 3D Printing
    • FPGA
    • Industrial Automation
    • Internet of Things
    • Power & Energy
    • Sensors
    • Technology Groups
  • Challenges & Projects
    Challenges & Projects
    • Design Challenges
    • element14 presents Projects
    • Project14
    • Arduino Projects
    • Raspberry Pi Projects
    • Project Groups
  • Products
    Products
    • Arduino
    • Avnet & Tria Boards Community
    • Dev Tools
    • Manufacturers
    • Multicomp Pro
    • Product Groups
    • Raspberry Pi
    • RoadTests & Reviews
  • About Us
  • Store
    Store
    • Visit Your Store
    • Choose another store...
      • Europe
      •  Austria (German)
      •  Belgium (Dutch, French)
      •  Bulgaria (Bulgarian)
      •  Czech Republic (Czech)
      •  Denmark (Danish)
      •  Estonia (Estonian)
      •  Finland (Finnish)
      •  France (French)
      •  Germany (German)
      •  Hungary (Hungarian)
      •  Ireland
      •  Israel
      •  Italy (Italian)
      •  Latvia (Latvian)
      •  
      •  Lithuania (Lithuanian)
      •  Netherlands (Dutch)
      •  Norway (Norwegian)
      •  Poland (Polish)
      •  Portugal (Portuguese)
      •  Romania (Romanian)
      •  Russia (Russian)
      •  Slovakia (Slovak)
      •  Slovenia (Slovenian)
      •  Spain (Spanish)
      •  Sweden (Swedish)
      •  Switzerland(German, French)
      •  Turkey (Turkish)
      •  United Kingdom
      • Asia Pacific
      •  Australia
      •  China
      •  Hong Kong
      •  India
      •  Korea (Korean)
      •  Malaysia
      •  New Zealand
      •  Philippines
      •  Singapore
      •  Taiwan
      •  Thailand (Thai)
      • Americas
      •  Brazil (Portuguese)
      •  Canada
      •  Mexico (Spanish)
      •  United States
      Can't find the country/region you're looking for? Visit our export site or find a local distributor.
  • Translate
  • Profile
  • Settings
Internet of Things
  • Technologies
  • More
Internet of Things
Forum Where the IoT meets the Facility Engineer
  • Blog
  • Forum
  • Documents
  • Quiz
  • Events
  • Polls
  • Members
  • Mentions
  • Sub-Groups
  • Tags
  • More
  • Cancel
  • New
Join Internet of Things to participate - click to join for free!
Actions
  • Share
  • More
  • Cancel
Forum Thread Details
  • State Not Answered
  • Replies 7 replies
  • Subscribers 511 subscribers
  • Views 790 views
  • Users 0 members are here
Related

Where the IoT meets the Facility Engineer

kellyhensen
kellyhensen over 9 years ago

In the good old days (two facility engineers talking).

Engineer 1:  “The conveyor in the southeast corner is making that noise again.”

Engineer 2:  “The grinding noise or the squeak?”

Engineer 1:  “The grind.  I hit it with the wrench yesterday afternoon and it was fine the rest of the day, but it’s making the noise again this morning.”

Engineer 2: “Better order what you need to repack the bearings before is seizes up again.”

 

Enter the IoT. . .

Engineer installs sensors on 127 mission critical areas of the facility measuring rotations, temperature, noise levels and power consumption.

Engineer has to convince IT department to invest in a server to store all the data that the sensors are collecting – outside of the DMZ, so the consultants can access the data real-time.

Wireless gateways are installed throughout the facility to communicate with the sensors and send the data to the new server.

Data is collected.

Data is modeled.

Predictive analysis algorithms are developed and tested.

 

And then, in the brave new IoT world. . .

A sensor monitoring noise attributes starts logging higher than usual levels.

An order is automatically placed for replacement parts.

The engineer receives a work order for preventative maintenance to repack the bearings.

 

The question is:  Is it all worth it?  And how to we prove that it is (or it isn’t)?

  • Sign in to reply
  • Cancel

Top Replies

  • gadget.iom
    gadget.iom over 9 years ago +1
    Part of me still prefers the wrench approach.
  • mcb1
    mcb1 over 9 years ago in reply to gadget.iom +1
    Part of me still prefers the wrench approach. All of me prefers that .... at least it was getting fixed.
  • gadget.iom
    gadget.iom over 9 years ago in reply to mcb1 +1
    All of me prefers that .... at least it was getting fixed. True 'dat! Now the difficulty is getting the engineers away from their computer.
Parents
  • mcb1
    0 mcb1 over 9 years ago

    I was having a discussion this morning along a similar line.

    The Improvement cycle process is 4 steps, with different labels depending on is running this flavour.

     

    Essentially

    1.     Identify a problem (noise)

    2.     Identify how bad the issue is, how frequent it occurs, what downtime, solutions available to resolve

    3.     Implement the solution.

    4.     Check to see if it has resolved the issue, and repeat if necessary

     

    Most people tend to go from 1 to 3 without exploring all the options available, or without understanding why there is a problem.

     

     

    kellyhensen

    I think you forgot to add the two levels of management involved.

    One for the IoT and the other to ensure that the PM's were generated and completed.

     

     

     

    Surprisingly we had an issue of bearings failing in the Anenometers.

    These are small bearings that were failing after a very short life in service (generally they last longer than the tech that last worked on them)

    Replacements didn't last much longer, and it was finally discovered that the oil used by the manufacturer had a shelf life of 1 year.

    If the bearing was sitting, the oil would seperate which lead to premature failure.

     

    We started only stocking bearings with 6 months from manufacture and checking before installation.

     

    Mark

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
Reply
  • mcb1
    0 mcb1 over 9 years ago

    I was having a discussion this morning along a similar line.

    The Improvement cycle process is 4 steps, with different labels depending on is running this flavour.

     

    Essentially

    1.     Identify a problem (noise)

    2.     Identify how bad the issue is, how frequent it occurs, what downtime, solutions available to resolve

    3.     Implement the solution.

    4.     Check to see if it has resolved the issue, and repeat if necessary

     

    Most people tend to go from 1 to 3 without exploring all the options available, or without understanding why there is a problem.

     

     

    kellyhensen

    I think you forgot to add the two levels of management involved.

    One for the IoT and the other to ensure that the PM's were generated and completed.

     

     

     

    Surprisingly we had an issue of bearings failing in the Anenometers.

    These are small bearings that were failing after a very short life in service (generally they last longer than the tech that last worked on them)

    Replacements didn't last much longer, and it was finally discovered that the oil used by the manufacturer had a shelf life of 1 year.

    If the bearing was sitting, the oil would seperate which lead to premature failure.

     

    We started only stocking bearings with 6 months from manufacture and checking before installation.

     

    Mark

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Verify Answer
    • Cancel
Children
No Data
element14 Community

element14 is the first online community specifically for engineers. Connect with your peers and get expert answers to your questions.

  • Members
  • Learn
  • Technologies
  • Challenges & Projects
  • Products
  • Store
  • About Us
  • Feedback & Support
  • FAQs
  • Terms of Use
  • Privacy Policy
  • Legal and Copyright Notices
  • Sitemap
  • Cookies

An Avnet Company © 2025 Premier Farnell Limited. All Rights Reserved.

Premier Farnell Ltd, registered in England and Wales (no 00876412), registered office: Farnell House, Forge Lane, Leeds LS12 2NE.

ICP 备案号 10220084.

Follow element14

  • X
  • Facebook
  • linkedin
  • YouTube