Case Studies.

Add Case Study

Our Case Study database tracks 18,926 case studies in the global enterprise technology ecosystem.
Filters allow you to explore case studies quickly and efficiently.

Download Excel
Filters
  • (1)
    • (1)
  • (1)
    • (1)
  • (1)
    • (1)
  • (1)
  • (1)
  • (1)
  • (1)
Selected Filters
1 case study
Sort by:
MachineMetrics helped Carolina Precision saved over $1.5M on machine monitoring - MachineMetrics Industrial IoT Case Study
MachineMetrics helped Carolina Precision saved over $1.5M on machine monitoring
Gary Bruner, the president of Carolina Precision Manufacturing, a contract manufacturer that specializes in small-diameter, close-tolerance CNC Swiss turned parts, had a problem. Over breakfast that morning, Gary had logged onto the MachineMetrics monitoring system on his laptop at home to check the status of his machines assigned to a lights-out operation, but saw immediately that two of his machines were not in production. “What’s wrong with machines 35 and 36?” he thought to himself. Upon arrival to the shop, Gary learned from his operator on duty that this type of hold up was nothing out of the ordinary, and was in fact a product of inefficient startup procedures that had simply never been analyzed or augmented previously. In an industry with razor thin margins, Gary understood that the keys to growth and success were in efficiency and quality. He understood the importance of keeping tabs on production stats, job status, uptime, and setup. However, there was no way to know how well machines were doing in real time. What was causing this additional downtime? Furthermore, CPM’s current methods of measurement and data collection were not only time consuming, but had quickly becoming outdated. Historically, CPM had an employee dedicated to the collection of utilization data. This employee would walk around to each of the machines, collect scrap tickets post-production, talk to operators, and record yesterday’s data into their current ERP system; not to mention that this manual data collection was prone to errors, and would take upwards of 2 hours per day. Without the ability to visualize their results, the recorded data was not very actionable.
Download PDF

Contact us

Let's talk!
* Required
* Required
* Required
* Invalid email address
By submitting this form, you agree that IoT ONE may contact you with insights and marketing messaging.
No thanks, I don't want to receive any marketing emails from IoT ONE.
Submit

Thank you for your message!
We will contact you soon.