Results with and without inspectors shifts overlapping:
Without Overlap
With Overlap
With schedule overlapping the only change that is noticible is the server utilization which goes down.
In order to get the number of boards that are rejected because of 3 or more failures of inspection I have simply used ModelEntity.TimesProcessed == 3 for the routing logic of connector between Inspector server and BadParts sink and got the following results:
3 or more failure count
Following are the fine-pitch placement machine proportions:
3 or more failure count
To create the Pharmacy model I have used two model entities and two servers and a source and a sink, below is a picture of the model and the connection between the servers and the entities:
Pharmacy Model
Then I have created tables, rate tables and scheduls, following are the screen shots:
Table & Sequence Table
Rate Tables
Work Schedule
To Run the model I was not sure how to handle the two arrival rate tables, so I chose the customer arrival rate table and run the model for 14 hours (8:00am to 10:00pm) and used 500 replication and got the following results:
Results
SMORE