When Will You Need This?
When you need to create a method of controlling a intermittent/variable assembly system or to establish a procedure of importing arrivals from Excel for the variable assembly model object.
This model object is specifically designed to be used with the variable assembly model object.
Variable Assembly Model Object
The following model object will be used to create import variable assembly arrivals to import data into ProcessModel: Arrivals \ Import Variable Assembly Arrivals.
How to Use the Model Object
Order of building the intermittent assembly model:
1. Build the main assembly line, inserting the Variable Assembly model object for each subassembly to be joined.
2. Build the subassembly lines and arrivals.
3. Insert this model object.
1. Open Your Model
Open your model or create a new blank model.
2. Insert the Model Object into Your Model
Locate the appropriate location in your model where you would like to place the model object, move the view to the location and then insert the model object.
3. Connect to Your Model
Connect the black activity to production line.
4. Open the Excel File
Right click on the Scheduled Arrivals Variable Assembly Sheet Excel icon and click on the third option from the bottom to open the Scheduled Arrivals Variable Assembly vx-x Excel file, where x-x represents the version number of the Excel file.
Click Enable Content if prompted
5. Setup the Excel File
Once the Scheduled Arrivals Variable Assembly vx-x Excel file opens click the 1. Setup button. This will instruct the Excel file to ping ProcessModel and fetch the name of all entities that have a Scheduled route from the active model and create new tabs for each entity. In our case we only have one entity called Part.
If you have multiple entities with a Scheduled route and only want to update one or more of the entities schedule you can delete the tabs of other entities. Make sure that you keep the tab with the buttons, change the name of the tab to reflect the name of another entity if the current entity name on the tab with buttons is not what you want to update, make sure that you keep the naming format: Ent (Entity-Name).
6. Enter Raw Data
1. Copy your attribute names into the Excel file, from cell C7 onwards. Sample data is included.
2. Copy your raw data into the Excel file, from cell A7 onwards. Make sure that you add all the attributes needed in your model and provide relevant values for them. Sample data is included.
Have UK dates and time? Use the UK Dates Converter
The attribute names must match to what you have in ProcessModel
Add Time and Quantity attributes inserted into your model as a result of using the Variable Assembly model object.
Add the production schedule to the Excel spreadsheet. Use 1 row for each production order
7. Import Data from the Spreadsheet to Processmodel
Before clicking the 2. Update button you may select one of the following 3 options in order instruct ProcessModel what it needs to do.
1. Import Data: Selecting this option will import the data into ProcessModel after crunching the numbers and updating the exported Data file from ProcessModel. The Excel file will automatically export data from your model.
2. Simulate Model: Selecting this option will simulate the model after completing all the actions mentioned in Import Data. Simulation animation will be off.
3. Animation On: Selecting this option will simulate the model with animation on after completing all the actions mentioned in Import Data.
The model object is now integrated into your model, you should now be able to save and then simulate the model.
After clicking the 2. Update button wait for a few seconds until you receive a relevant prompt via Excel or are moved to ProcessModel for model simulation. Once you are back in ProcessModel, you can look at the following location to make sure that the import was successful:
1. Click on the arrival route and from the Properties Dialog click Define Schedule, open the Action Logic and review the import values.
Review the first line of data that was imported
The data imported into ProcessModel is reflecting the same values