Can someone please help me figure out why my MTTR behaves as it is in this model? I would expect all BFFRs to run for 60 minutes then go down for 10 minutes. However, I see a random behavior here. I think it is related to how I change the states in the process flow chart that I'm overriding some states by mistake.
Thank you for contributing to our community! We couldn't identify a maintained license or subscription linked to your account.
You may need to update your profile information to identify yourself as a license owner or their associate. Check out our article for how to ensure you receive timely support. If you update your profile comment back to let us know - we'll adjust the priority of your posts accordingly.
Hi @Mohamed Eldakroury, was Felix Möhlmann's answer helpful? If so, please click the "Accept" button at the bottom of their answer. Or if you still have questions, add a comment and we'll continue the conversation.
If we haven't heard back from you within 3 business days we'll auto-accept an answer, but you can always comment back to reopen your question.
1) Use different down 'IDs' in the MTBF/MTTR and the Time Table, so the program can correctly keep track of what state the object should be reset to when it resumes.
2) Stopping the object does not interrupt the Process Flow of items that are already in the object. You need to implement logic that stops the tokens while the object is down.
17 People are following this question.
© 1993- FlexSim Software Products, Inc. All Rights Reserved.
FlexSim is a fully 3D simulation software environment. FlexSim can be used to simulate any process in any industry.
FlexSim®, FlexSim Healthcare™, Problem Solved.®, the FlexSim logo, the FlexSim X-mark, and the FlexSim Healthcare logo with stylized Caduceus mark are trademarks of FlexSim Software Products, Inc. All rights reserved.
