This model object simplifies entry of scheduled arrivals for build to order products. Build to order products have codes that define product characteristics. The codes could affect what is assembled and how much production time is needed at each station (or even how much time is required by each person at each station).
You define the codes in a table, with the corresponding production requirement for each code. The production schedule contains all the codes required to build an order. Before running the simulation, the codes pick up the production requirements for each product.
For example, an east coast window manufacturer has 30 codes that define options on a window. Options define the size, materials, number of panes, type of glass, type of sash, etc. Changes to any of these codes could change the production time at one or all the stations. In addition, assembly requirements are added as a result of the codes. The number of combinations of options is in the millions. Each day, a new production schedule has unique window requirements defined by the codes.
A west coast truck manufacturer has 26 codes that define production requirements of the chassis. The codes describe the number of axles, drive type, suspension, load capacity, number of air tanks, etc. Changes to any of these codes change the production time for each person at a multi-person assembly station. Assembly quantities and types also change as a result of code changes. There are thousands of possible combinations of codes. As with the window production, the production schedule is defined by a base part with a series of codes defining the production options for that chassis.
Where to Find the Model Object
The following model object can be found in the model objects directory:
- Arrivals \ Scheduled Arrivals with Table Input
- Arrivals \ Scheduled with codes
- Ease of Use: Easy
- Ease of Modification: Moderate
How Does It Work
There are three main components to the Scheduled Arrival with Table Input:
Before using this Excel file for the first time, or after changing your model name, make sure that a manual export of data is done via ProcessModel. From your model, click Tools \ Export Data, click ‘Yes’ to all prompts until the data export file opens, close the data file and then use this Excel file.
You enter or import the production schedule with codes that describe the product characteristics.
The tables define the production time required for of the product codes. The production schedule queries the table to and adds the time to attributes used for each assembly station.
Tables defining time for each code
The production time information is imported into the model. Each product will have different values in the attributes specifying time at each station.
Once the model and tables are setup, testing a new schedule takes seconds to perform.
How to Use the Model Object
- Develop the Model with Attributes to Define Time and Assembly: The model uses attributes to define the production time at each station. A different attribute is used for each station time (or person at the station).Attributes define the sub-assembly attaches at stations. A unique attribute is needed for each subassembly.
The Attribute a_Assy1 of the base entity is set to one (the requester of the Attach) then 1 subassembly is requested. If the a_Assy1 of the base entity is set to zero, then no attachment is requested.
If several exclusive subassembly options are attached at the same assembly station, use several attach routes as shown below. The attribute a_Assy1a could be set to one, while a_Assy1b is set to zero or vice versa.
The options for the values of each attribute might include:
If several non-exclusive subassemblies are attached at the same assembly station, use several Attach routes as shown below.The options might include:
- Create a Scheduled Arrival in the Model: In the model, the arrival mus