When Will You Need This?
In a scenario where you would like to import real-life data into ProcessModel, along with attribute values that can define the flow, time taken at each step and which resource is needed at what step.
The following Model Object will be used to import healthcare arrivals and other data into ProcessModel; Arrivals \ Import Scheduled Arrivals.
Ease of Use: Easy
Ease of Modification: Moderate
How to Use the Model Object
1. Open Your Model
Open your model.
Make sure that your model has at-least one scheduled arrivals.
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.
4. Open the Excel File
Right click on the Scheduled ArrivalsInput Sheet Excel icon and click on the third option from the bottom to open the Scheduled ArrivalsInput 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 ArrivalsInput 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 from ProcessModel into the Excel file, from cell C6 onwards. Overwrite the sample data 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. Overwrite the sample data included.
Have UK dates and time? Use the UK Dates Converter
The attribute names must match to what you have in ProcessModel
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 Import Scheduled Arrivals model is now integrated into your model, you should now be able to save and then simulate the model.
Attributes, Variables, Scenario Parameters and Scenarios usage
1. a_PartNumber: An example attribute for Scheduled Arrivals Import.
2. a_GrateTypeRequired: An example attribute for Scheduled Arrivals Import.
3. a_QtyInTote: An example attribute for Scheduled Arrivals Import.
4. a_QtyPerGrate: An example attribute for Scheduled Arrivals Import.
5. a_LoadTimePerPart: An example attribute for Scheduled Arrivals Import.
6. a_GrateBatchSize: An example attribute for Scheduled Arrivals Import.
7. a_RemBatchQty: An example attribute for Scheduled Arrivals Import.
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.