4.4.1 – Steps in Creating a Model Object
1. Copy the Activities, Routings and Resources needed to replicate the desired behavior.
2. Paste the copied elements into a new model.
3. Add ProcessModel elements needed so this new model will operate independently.
4. Using the text tool, document the purpose and how to use this MO. Make notes that will help the user understand the MO operation.
5. Change the color of all non-essential model elements light gray.
For changing the color of text, routings and activities see Chapter 2, Section , Formatting Lines.
6. Change the name of the layer on which the model resides to Model and add a new layer titled Notes. To make these changes, right mouse-click on the layer tab in the lower left corner of the layout and open the layer manager.
Use the layer manager to rename current layers and add new layers.
7. Move all non-essential elements to the Notes layer. Only model elements that will be copied from the model object will remain on the Model layer. To move items on the ProcessModel layout to another layer, select the elements desired (shift-click to select multiple items) then right-mouse-click on one of the layer tabs and select Move to Layer. Select the Notes layer and press OK.
8. Create data file to supply information to the model object data base. This is a text file (can be created using Notepad) with a predefined format. The format follows:
@#Indus#@Manufacturing, Service, Healthcare, Logistics, Other,#@
@#Categ#@Arrivals, Batching, Conveyors, Costing, Flow Control, Inspection, Miscellaneous, Priorities, Routings, Setup, Shifts, Time, Utilization, Visual Indicators,#@
Save this text file with the same name as your model, except with an extension of “.txt”. A typical text file might look like the one shown below:
@#Indus#@Manufacturing, Military, Service, Other,#@
@#Desc#@If you have a need to route ENTITIES by percentage that changes based on the ENTITY name.#@
In the Industry section, type the industry for which this MO applies. Enter one or more industries separated by commas and the last entry ending with a comma. In the example above, this model will show up in 3 industries and in the other category.
In the Category section, type the category for which this Mo applies. This section will generally have one category, but may have more.
In the Keywords section, type all the keywords that might be used to find a model object separated by commas.
In the Description section, type the sentence or paragraph that defines the purpose of this model object.
In the Video section, enter the full URL describing the path to an online video.
Notice the general pattern. “@#” starts a section followed by a name of the section (Indus, Categ, Keyw, Desc, video). The name of the section is followed by “#@”, the information of the section and then another “#@”
9. Create a picture of the model object Layout. This file will be used to generate the preview for the model object. Save the .JPG with the same name as the model but in the JPG format. A picture size of 600 X 450 is recommended for a preview picture.
10. Link the .TXT file from step 8 and the .JPG from step 9 to the model. In the Notes tab of the model add a shape from the palette (it won’t make any difference if it is an entity, activity or resource and the name is not important). Change the Object Type to “Link”.
Link the two files by right-mouse-clicking on the link object and selecting Link Document.
11. Change the Paste Rule for variables, attributes and scenario parameters to allow them to integrate properly. Each of the three elements above need to know how to behave if there is already an element with the same name in the target model.
Set the Paste Rule to Duplicate if this element name can be used in many places. For example: the name a_Dir1 might be used every time action logic is used to determine which routing to take. The same attribute would be reused at every decision and thus could be used many times without creating a new attribute.
Set the Past Rule to Clone if the name being pasted must be unique for the logic being pasted. For example: the counter v_Count1 might be used to tell the logic how many times an entity had been through a particular set of logic. This means when a model object containing v_Count1 is copied into a model which already has the same variable name, the arriving variable needs to be renamed and all of the logic in the arriving model object needs to be rewritten using the new variable name.
12. Click on the Model Tab to make the Model layer active.
13. Save the model in the ProcessModel Model Objects directory.