The toolkit exposes a new Facility agent class that you are free to extend. This class is the main agent class that can be used to represent all different kinds of facilities.
A sample model has been provided in the Supply Chain Toolkit Overview that gives a specific usage example for reference.
\nThe Facility agent contains abstract functions in the super class that must be implemented in your extended class.
When you create a new Facility agent you will need to implement the following methods.
@Override\nprotected void processOutboundLoadingBay() {\n \n}\n\n@Override\nprotected void departTransport() {\n\n}\n\n@Override\nprotected void receiveInboundTransport(){\n \n}\n\n@Override\nprotected void processInboundLoadingBay(){\n\n}These methods provide the basic functionality required to handle the sending and receiving of TransportMessage messages carrying units / products between facility agents. They must be called from an Action and can be ignored if other mechanisms for departing transport are desired.
The receiveInboundTransport() method also has a function in the super class for receiving TransportMessage messages automatically.
@Override\nprotected void receiveInboundTransport(){\n super.receiveInboundTransport();\n}When calling departTransport(), you can add your custom logic for determining how you will depart trucks and by calling the receiveInboundTransport() function in the super class immediately afterwards in the run sequence, the TransportMessage messages will be placed in the LoadingBay.TransportQueue.
An example from the sample model use case can be found below:
\npublic static Action<FacilityTypeA> departOutboundTransport =\n Action.create(FacilityTypeA.class, FacilityTypeA::departTransport);As many LoadingBay classes as desired can be added to your Facility classes. They can be either initialized during the setup() phase, it could be done during an firstStep() run sequence, or new ones could be added during the simulation.
More on the LoadingBay class can be found in the Loading Bay docs.
A common challenge when simulating supply chains with massive throughput is the simulation time required for dealing with processing and filtering through millions, even 100s of millions of units travelling through facilities.
\nOne way to handle this and speed up these operations is by using ParallelStreams, ConcurrentList, and ConcurrentHashmap.
By using these structure it's possible to parallelize the operations across massive lists and maps while not running in to concurrent modification exceptions.
\nMore information can be found in the java.util.Concurrent & java.util.Collection libraries linked below: