> For the complete documentation index, see [llms.txt](https://virtualfactory.gitbook.io/vlft/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://virtualfactory.gitbook.io/vlft/use-cases/manufacturing-system/hybrid-flow-shop-ontogui.md). # Modelling a Hybrid Flow Shop using OntoGui ## Case Description The flow shop is composed of 5 machines and 5 buffers which are connected accordingly The processing time of each machine varies according to the part(classes). ![process times](/files/-M4BtU5PSYf_04-leJii) Each of the machines has failure modes with different mean time to repair and mean time to failure. M1, M4, M5 have two failure modes and M2,M3 have only one failure mode. ![failure modes](/files/-M4BtU5RqO7YkLg-Xs-G) ## Formal model ![formal model](/files/-M4BtU5TQy_PAPsIzQ2v) ## Modelling of Hybrid Flow shop (Using OntoGui) ### Control panel ![control panel](/files/-M4BtU5VekY338PCmGfg) 1. A new ontology module Hybrid Flow-shop has been created. 2. System design tool is selected under the ontology tools. ### System Design System Design window is opened #### Part Types ![part a part types](/files/-M4BtU5Xnm6M_ts0GJvM) 1. A new part called Part-A of the class **Workpiece type** is created #### Process Plans ![part a process plan](/files/-M4BtU5ZITQz86zl7BPr) 1. A process plan **prodplan** is created for the **Part-A** #### Process Steps ![part a process step M1.1](/files/-M4BtU5aWwWi1Kyrin9b) ![part a settime M1.1](/files/-M4BtU5ciz7pLTvxyiM9) 1. M1.1 is the process step of the machine M1. The processing time of 1.1s is entered using the **set time** option and Manufacturing task is selected under the **set class** option. 2. M2.1 is the process step of the machine M2 with a processing time of 0.9s 3. M4.1 is the process step of the machine M4 with a processing time of 1.5s 4. M5.1 is the process step of the machine M5 with a processing time of 0.7s **Successors of process step** ![part a successor M1.1](/files/-M4BtU5eddrUxvjy-GIy) 1. M2.1 is selected as a successor of M1.1 using the **add** button under add successor. M3.1 is the successor of M2.1 and M4.1 is the successor of M3.1. #### Systems ![system create](/files/-M4BtU5gD4vN8XphC2jl) 1. A system called **Hybrid flowshop** of the class **Manufacturing system** is created. ![](/files/-M4BwlhFTARBiVgZ5n0Z) ![system add B1](/files/-M4BtU5iCY7L4ygNP9LV) 1. The machines M1,M2,M3 and M4 and buffers B1,B2,B3 and B4 are created under this system using the **Add new** option. **Managing connections of selected machine** ![](/files/-M4Bwt3ngkIguMOU_TXJ) 1. For M1, B1 is in upstream and B2,B3 are in downstream. For M2, B2 is in upstream and B4 is in downstream. For M3, B3 is in upstream and B4 is in downstream. For M4, B4 is in upstream and B5 is in downstream. For M5, B5 is in upstream and B1 is in downstream. **Manage properties of Buffer** ![system buffer capacity B1](/files/-M4BtU5kA7BvyVgdD3sF) 1. The buffer capacity of each buffer was entered in the box. **Manage failure modes of machine** ![system failure mode M1](/files/-M4BtU5mdT9QCBH92FtX) 1. The failure mode properties of each machine are entered. The failure type is "ODF". Time to fail is recorded in terms of hour and time to repair is in terms of minutes. The value is entered in properties value dialog box. 2. The procedure is repeated for all the other machines as well. M1 and M4 have two failure modes 3. The value can be modified later by using the **set** button #### Assignments of process step ![part a assignM M1.1](/files/-M4BtU5o0jV3RWmZAFef) 1. The machines are assigned to respective process step. M1 is assigned to M1.1, M2 is assigned to M2.1, M4 is assigned to M4.1 and M5 is assigned to M5.1. #### Part Types ![part b part type](/files/-M4BtU5qM8Eynb8NhBiq) 1. A new part called Part-B of the class **Workpiece type** is created #### Process Plans ![part b process plan](/files/-M4BtU5scF2LkWUZ11RY) 1. A process plan **prodplan.1** is created for the **Part-B** #### Process Steps ![part b process step](/files/-M4BtU5uW9vtqIJ-I9T7) 1. M1.2 is the process step of the machine M1. The processing time of 1.3s is entered using the **set time** option and Manufacturing task is selected under the **set class** option. 2. M3.2 is the process step of the machine M3 with a processing time of 2.1s 3. M4.2 is the process step of the machine M4 with a processing time of 1.2s 4. M5.2 is the process step of the machine M5 with a processing time of 0.8s **Successors of process step** 1. M3.2 is selected as a successor of M1.2 using the **add** button under add successor. M4.2 is the successor of M3.2 and M5.2 is the successor of M4.2. #### Assignments of process step 1. The machines are assigned to respective process step. M1 is assigned to M1.2, M3 is assigned to M3.2, M4 is assigned to M4.2 and M5 is assigned to M5.2. #### Part Types ![part c part type](/files/-M4BtU5wBlSdWXwDh898) 1. A new part called Part-C of the class **Workpiece type** is created #### Process Plans ![part c process plan](/files/-M4BtU5yKLpM-3kmA4Gg) 1. A process plan **prodplan.2** is created for the **Part-C** #### Process Steps ![part c process step](/files/-M4BtU6-ELQy05eyCOf-) 1. M1.3 is the process step of the machine M1. The processing time of 1s is entered using the **set time** option and Manufacturing task is selected under the **set class** option. 2. M2.3 is the process step of the machine M2 with a processing time of 1.1s 3. M4.3 is the process step of the machine M4 with a processing time of 0.7s 4. M5.3 is the process step of the machine M5 with a processing time of 0.5s **Successors of process step** 1. M2.3 is selected as a successor of M1.3 using the **add** button under add successor. M3.3 is the successor of M2.3 and M4.3 is the successor of M3.3. #### Assignments of process step 1. The machines are assigned to respective process step. M1 is assigned to M1.3, M2 is assigned to M2.3, M4 is assigned to M4.3 and M5 is assigned to M5.3. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://virtualfactory.gitbook.io/vlft/use-cases/manufacturing-system/hybrid-flow-shop-ontogui.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.