Jump to content
Simio Forum

Welcome to the Simio Forum

Welcome to the Simio Forum! Experience the full experience of the forum by becoming a Simio Insider! You must be an Insider to post on any forum!

Click_Here_button.png

New Software Release

Our latest release, Simio 11, is here!

Kaylinn

Members
  • Content Count

    6
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Kaylinn

Converted

  1. AHH! I understand now. I guess we've always cheated and done it with server/workstation reliability logic (because for the most part, our FPY is our reason for downtime, not our servers/workstations actually being broken). So do you know how I would I do what I'm looking to do? Is there a property I can add to the entity that would be called upon as a FPY at each station? To add an extra layer of difficulty, the failure rates won't be the same at every station. For example, Entity A at station 1 might have a FPY of 90%, Entity B at station 1 has 85%, Entity A at station 2 has 95%, and Entity B at station 2 has 50%, if that makes sense. Thank you for your help!!!
  2. @jzhou I'm confused why you're confused. I have several entity types (in the real world, they're hydraulic pumps and motors). They all go through the same stations on the assembly line, but they don't all fail at the same rate. For example, our motors have a FPY of 90% per say, but one model of pumps is closer to 55%, while another is 75%. We build to order, so I could run any part at any time. And each part has it's own failure rate and general repair time at each station. @CWatson I think I get what you're going for. But wouldn't that still tie a single failure rate to my station instead of a dynamic rate/time based on unit type? Thanks!
  3. Hello! I'm trying to model an assembly line that has several unit (entity) types run down it. I have a table set up determining processing times for each entity types and that works fine. I tried the same syntax for the Reliability Logic (for both uptime between failures or count between failures and the time to repair) but I keep getting errors saying there is a problem determining the row to use in my table. I've tried different tables and several failure types and I'm stuck. I also tried add-on processes to SetRow via the Token object, but that didn't help. I even tried copying and pasting the exact same syntax I have for the processing time into the reliability logic, and it still gets stuck. Can I not call on table references in my reliability logic? Thanks! Kaylinn
  4. Hello! I am modeling a wash station that takes 30 minutes for the first piece, and an additional 5 for each piece after that(so a batch of 3 would take 40 minutes, a batch of 6 would take 55 minutes, and so on) but I'm having some trouble putting this into a processing time. The added problem is that the number of entities changes. Currently I'm using a source that produces one "shipment" a day with "Entities per arrival" set as "random.triangular(3,13,19)" which is working fine for my quantity, but I don't know how to relate that into the processing time of the next workstation. Thanks!
  5. Thank you for your quick reply! Yes, I am using workstations. Could you tell me more about this resource reservation? That's a new one for me. And I just had another question. I am modeling a wash station that takes 30 minutes for the first piece, and an additional 5 for each piece after that(so a batch of 3 would take 40 minutes, a batch of 6 would take 55 minutes, and so on) but I'm having some trouble putting this into a processing time. The added problem is that the number of entities changes. Currently I'm using a source that produces one "shipment" a day with "Entities per arrival" set as "random.triangular(3,13,19)" which is working fine for my quantity, but I don't know how to relate that into the processing time of the next workstation.
  6. Hi folks! I'm trying to model a production line with one worker and several stations that he visits/uses. The process is in a specific order (ie, the entities move in a direct path) but the worker is free to float between stations as needed. The situation I'm facing now is that some stations require him during the beginning and ending, excluding processing time, and other use him the whole time. I have a station that he is called to be at, and he goes and completes the task, then exits the station leaving the entities, goes to finish another task, and then returns to the original station to pick up the entities he left before. How do I make him take those entities to their next location before leaving? I've tried setting the "task selection strategy" to "largest priority" and assigning higher priority to the entities at the original station, but it's not working. Any help would be very appreciated! Thanks PS, does anyone have any thoughts/preferences between using processes to seize the worker and delay during the task versus using the station's secondary resources to call him? They seem to be the same thing to me and I was just wondering if there are any tips/tricks/reasons to use one over the other? Double thanks!
×
×
  • Create New...