Jump to content

popejo11

Members
  • Posts

    7
  • Joined

  • Last visited

About popejo11

Converted

  • LOCATION
    China

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

popejo11's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. Haha, well, I figured out the problem at about the same time you made your post. It turns out that one of my group members moved the last server in the process before the sink from being the very last server to the first server. When he did that, he didn't change the entity routing logic in the transfer nodes of either server, so the entities ended up doing one big loop. Once we corrected the routing logic, everything seems to be flowing smoothly. Anyway, thanks for your response gocken.
  2. HI all, I keep running into an error every time I run my model and I'm not sure what it means. The dialog box says: --------------- Entity: PartType.88 A Runtime error was detected at time 288.17 Hours at the following process step: Object: Model Process: Srv8_AfterProcessing Token: Token.1 Step: [Release] ReleaseTool Property: NumberOfObjects Error releasing resources of type Specific 'Tool1' owned by object 'PartType.88'. Unable to release '1' resource object(s) of the specified type because the number of individual resources owned and satisfying release conditions is only '0'. --------------------- My model is set up so that it creates entities (PartType 0 through 4) so that it will make one PartType 0, then one PartType 1, ... , then one PartType 4, and start back over at PartType 0. (Based on the SimBit "Sequential Processing By Batch Specified in Table"). As each entity enters the model after being assigned a specific type, it seizes capacity in a resource specific to that PartType. The resource remains seized until the last server before the sink (Srv8), where the resource is released. The seize/release operations are accomplished using Add-On Process Triggers. Not sure if it's relevant, but the entities must ride on one of 4 transporter between all servers. Can anyone help me solve this error? If I understand it correctly, somewhere along the way more resource capacity is being released than seized and I'm not sure why.
  3. Yep, I was shocked at how simple that was to accomplish when I finally figured it out! Thanks Dave.
  4. I think I figured this out. Switching from workstations to servers allowed me to use secondary resource seizing and releasing across a process. So the first server would seize the resource, the resource remains seized through the process, and then the last server releases the resource.
  5. Hi all, I'm a new user to Simio and am having to give myself a crash course in the software, so please bear with me. I posted this in the material handling forum but have realized that this is probably a better question for the SI Objects forum. My project is a manufacturing facility that involves product being created, processed, and finished in tooling, which is transported between process steps by transporter vehicles. My team is attempting to determine the need for additional tooling and transporters in this facility, and so material handling and resources are the main focus area of the project. Can entities seize resources across multiple workstations? IE, an entity (product) would seize a resource (tooling) out of the Source, and continue seizing that same resource as it travels through several workstations, and then release the resource as the entity enters the Sink? In our facility, the product is supported in tooling as it undergoes multiple operations at different workstations, and we need a way to model the tooling utilization. The transporters can come and go freely while the part/product & tooling combination are in process at each workstation. Is it possible to model this in Simio? Or reasoning behind using the objects the way we are is so that we can track utilization of the tooling and transporters to determine at what production rate they cross the 100% utilization rate threshold. Thanks in advance.
×
×
  • Create New...