
Sign up to save your podcasts
Or


In this episode, Paul Lachance, an industry veteran, takes us on a journey through the evolution of CMMS solutions. From the early days of Bigfoot to insights into the dynamics of startup culture and the critical importance of customer-centricity, to reflections on the ever-changing landscape of the #CMMS market. Discover the behind-the-scenes story of transformation and success in the world of maintenance management.
Thank you, Paul, for joining Greg to record this episode on CMMSradio! It was an honor to have you on to share your journey story, insights, and observations about the CMMS space as a whole.
Startup vs. Enterprise Dynamics:
Paul discusses the distinctions between startup and enterprise environments in the CMMS space, emphasizing the entrepreneurial spirit and challenges faced during the startup phase.
Smartware Group’s Journey:
The narrative follows the evolution from Bigfoot to Smartware Group, exploring the introduction of cloud technology and the strategic decision to extend CMMS applications beyond industrial settings.
Acquisition and Transformation:
Software Equity Group’s role in Smartware Group’s acquisition by Dude Solutions is highlighted, shedding light on the subsequent transformation of Bigfoot into Asset Essentials and its expansion into government and education sectors.
Customer-Centric Philosophy:
The importance of treating customers and employees well, coupled with robust support and services, is emphasized as a key factor in the success and sustainability of CMMS solutions.
Reflections on the CMMS Market and Future Trends:
Paul shares insights on the saturated CMMS market, the cyclical nature of the industry, and anticipates future trends, particularly in Industry 4.0 technologies, smart manufacturing, and the evolving landscape of CMMS solutions.
The post CR033: Talking CMMS with Industrial Manufacturing Strategist Technologist and Evangelist Paul Lachance appeared first on Accendo Reliability.
This episode is dedicated to ALL VETERANS of our United States Military.
When two Sea Dogs, like Bryan Bieschke of Align Machine Company and Howard Penrose of MotorDoc, LLC get rolling on these Maintenance Sea Stories you just sit back and enjoy. The maintenance mindsight insights from these heavy hitters in the maintenance and reliability are real, RAW, and practical. Pack a lunch and tune in for a no nonsense 85-minute ride along filled with unique perspectives, interesting and funny terms (Puddle Pirate) and a tribute to Veterans where we get to learn what Veteran’s Day means to these Salty Sailors (LOL) – Let us know what you think of the episode!!
Bryan Bieschke, CMRP – https://www.alignmachinecompany.com
Howard Penrose , CMRP, PhD – https://motordoc.com
https://cmmsradio.com
The post CR032: Maintenance Sea Stories with Bryan Bieschke and Howard Penrose appeared first on Accendo Reliability.
Today, we're diving deep into the world of electronics manufacturing from a unique vantage point that of the press.
My guest today is someone who has spent decades at the forefront of reporting on the electronics manufacturing industry. Mike Buetow, editor-in-chief of Circuits Assembly magazine, has covered everything from the latest technological advancements to the biggest challenges facing manufacturers today.
If there's a major trend shaping the industry, you can bet Mike has written about it, analyzed it, and spoken with the experts behind it. Mike is also the host of his own podcast, PCB chat, available at pcbchat.com. I am so proud to say Mike also syndicates this show at pcbchat.com.
In this episode, we'll explore the evolving landscape of electronics manufacturing, from supply chain disruptions and AI-driven automation to the future of ultra-high-density interconnects and the real impact of reshoring efforts.
We'll also get an inside look at what it takes to cover this ever-changing industry how stories are chosen, what topics are making waves, and what challenges lie ahead.
Printed Circuit Engineering Association (PCEA)
Home
Circuits Assembly Magazine:
The post RM 167: Meet the Press: A Conversation with Journalist and PCEA President, Mike Buetow appeared first on Accendo Reliability.
From Reliable Plant Conference 2023 – (Audio with Graphic) A great discussion with Dr. John Ross, CMRP of Maintenance Innovators, talking about the conference, the workshops, maintenance, CMMS and more.
The post CR031: Talking CMMS with Maintenance Innovators Dr John Ross from the Reliable Plant Conference appeared first on Accendo Reliability.
Unlocking Maintenance Success: From CMMS Mastery to Industry 4.0 Innovation! Join us for a dynamic radio conversation with Joe Anderson, COO of ReliabilityX, as we delve into the world of CMMS challenges, cultural change, and navigating the evolving landscapes of Industry 4.0 and 5.0. Discover the secrets to mastering CMMS, fostering a proactive maintenance culture, and embracing the power of learning from mistakes. Tune in and revolutionize your maintenance strategy today!
Selecting and utilizing Computerized Maintenance Management Systems (CMMS) present challenges due to varying industry needs, work types, and organizational sizes.
Connect with Joe Anderson: [email protected]
ReliabilityX: https://reliabilityx.com/
Tune in to Practical Reliability: https://podcasters.spotify.com/pod/sh…
Inquire: [email protected] or call 1–877-RLBLTYX
The post CR030: From CMMS Mastery to Industry 4.0 Innovation! Guest Expert: ReliabilityX COO Joe Anderson appeared first on Accendo Reliability.
We're developing requirements for our product, including setting reliability requirements. Or we're setting acceptance criteria for our test plans.
What confidence levels do we choose? We don't have to blindly set them – we can base it off the risks of failure, using our FMEA (failure mode effects analysis).
View the Episode Transcript
We should choose a confidence level for our requirements or their test plans. We can associate that confidence level with the level of risk associated with our product.
If we have an FMEA, we can find the place in the table where our requirement is a control or where it’s associated with a potential failure mode and cause. When we find it, then we have a lot of metrics we can use to help us decide on a level of confidence to test based on risk. And if we’ve done our FMEA earlier, then we would’ve had it populated with information from our cross-functional team in a time of cool heads, without the pressures of project management. It will be an objective input into what confidence level we should require for our test.
FMEA is a great tool for us to refer to, to help us choose a relevant confidence level by basing our decision on one or more metrics that the FMEA can provide.
Previous episodes that are related to this topic:
Episode 27: How many controls do we need to reduce risk?
Episode 31: 5 Aspects of Good Reliability Goals and Requirements
We are developing requirements for our product, including setting reliability requirements and its confidence levels or we're setting acceptance criteria for our test plans. What confidence levels do we choose? We don't have to blindly set them. We can base it off the risks of failure. I'll tell you how after this brief intro.
Hello and welcome to Quality during Design, the place to use quality thinking to create products others love for less. My name is Dianna. I'm a senior level quality professional and engineer with over 20 years of experience in manufacturing and design. Listen in and then join the conversation at qualityduringdesign.com.
Before testing anything, we need to choose what confidence level we want to have in the results. We need to do this because there's variation in everything in the way that we measure and test. The way that we manufacture introduces variation, including the raw materials that we, and the tools we're using to make it. Setting a confidence level accounts for the variability we're going to see in our test data. A confidence level is used in determining the sample size to test. If we want to make statements about how the design will perform in the field, then we need to test a sample size that statistically relevant, where we can use statistics to help us predict the performance in the field from a few tested in the lab.
Usually confidence levels are 90%, 95% or 99%. Why don't we take the most conservative approach and just pick a 99% confidence level where that may save us time and having to think about it, it wastes a lot of time and resources later. The higher, the confidence level, the more likely we'll need to test lots of samples. And that means making units for test, testing them all in the lab, and then having a more complex analysis.
Instead, one way we can choose a confidence level that we want for test is to correlate it with the risk of failure associated with it. Our product requirement is likely a control for a potential failure. What was the origin of our requirement? Why did we set it in the first place? What performance or characteristic of the final design is it controlling? If our product doesn't meet this requirement, what are the ways that it can fail? If we have an FMEA, we can find the place in the table where our requirement is a control or where it's associated with a potential failure mode and cause. When we find it, then we have a lot of metrics we can use to help us decide on a level of confidence to test based on risk. And if we've done our FMEA earlier, then we would've had it populated with information from our cross-functional team in a time of cool heads, without the pressures of project management. It will be an objective input into what confidence level we should require for our test.
What are the potential effects of this failure mode? In other words, what type of harm to the user, environment, or performance of the product is possible? Are there many effects listed or just one? If there are many effects, we may want a higher confidence level. What is the severity ranking of the effect? Is it high or is it low? The higher, the severity ranking, the more likely we should choose a higher confidence level. What other controls are in place besides our requirement? And what is the detection ranking? If this requirement is the only control, or if it's the strongest control, then we may want to choose a higher confidence level. We could also use this information to justify a lower confidence level. If we have a requirement that's associated with a failure that has one effect, that effect is not severe, and there are two other controls associated with that same cause, then maybe we'll choose a lower confidence level.
If this episode is helpful to you, I recommend two other previous Quality during Design episodes. Episode 27, How many Controls do we Need to Reduce Risk talks more about the controls that we use in an FMEA to control a risk. Episode 31, 5 Aspects of Good Reliability Goals and Requirements, talks about why we want a confidence level associated with our requirement.
Please go to my website at quality during design.com. You can visit me there and it also has a catalog of resources, including all the podcasts and their transcripts. Use the subscribe forms to join the weekly newsletter, where I share more insights and links in your podcast app. Make sure you subscribe or follow quality during design to get all the episodes and get notified when new ones are posted. This has been a production of Deeney Enterprises. Thanks for listening!
The post QDD 167: Redux: Choosing a Confidence Level for Test using FMEA appeared first on Accendo Reliability.