Code Monkey home page Code Monkey logo

salabim-grid-plant-3d's Introduction

GridPlant

In this project we study techniques for reducing the effort of factory layout planning (FLP) and optimal job shop scheduling (JSS). To achieve this goal, we develop an easy-to-use configurator and simulator for a particular class of factories. More precisely, we concentrate on flexible manufacturing systems, which can be adapted to a variety of products and processes. We assume that the material flow between the work stations of the factory is handled completely by gantry robots.

๐Ÿ–ผ๏ธ Screenshots

Here are some screenshots of our software tool:

  • 3D animation of the factory components including robots and machines
  • Performance evaluation of the factory layout in a given order scenario
  • Graph visualization of the underlying factory configuration data model

In the following, we explain the software outputs in more detail.

3D animation

Our software is based on Salabim, a Python framework for Discrete Event Simulation (DES). DES is a standard tool for factory layout planning and performance evaluation. Salabim comes with an integrated 3D animation engine, which supports both primitive shapes and Computer-Aided Design (CAD) models in OBJ Wavefront format.

Salabim screenshot

Performance evaluation

The goal of Discrete Event Simulation (DES) is to evaluate the performance of your factory layout plan early in the planning process. Performance evaluation typically concentrates on the utilization of resources such as workers, machines, and storage areas. Our software automatically tracks the most relevant performance characteristics.

Console output

The performance data can be printed to the console.

Console screenshot

PyPlot output

The performance data can be visualized using bar charts.

PyPlot screenshot

๐Ÿ–ผ๏ธ Graph visualization

Finally, we support basic graph visualizations for debugging your factory configuration models. The following graph visualization displays the product types and manufacturing operations of a configuration model. Product types represent everything from raw material to end products, while operations consume and product them.

NetworkX screenshot

Requirements

To use this project, you need to install the following software packages on your machine. Note that simulation experiments can be carried out without the optional software packages.

  • Python
  • Discrete event simulation support
    • Salabim
    • 3D animation support (optional)
      • PyOpenGL
      • PyOpenGL_accelerate
    • OBJ Wavefront file format support (optional)
      • PyWavefront
      • PyGlet
    • Video production support (optional)
      • opencv-python
      • numpy
  • Chart visualization support
    • Matplotlib
  • Graph visualization support (optional)
    • NetworkX

๐Ÿ‘จโ€๐Ÿ’ป Examples

When performing a simulation study, we suggest working in four phases:

  1. Basic configuration defines the products as well as the processes to product them.
  2. Scenario configuration defines the situations, in which the factory must operate.
  3. Layout configuration defines the number and arrangement of the factory resources.
  4. Performance evaluation simulates the performance of the layout in a given scenario.

In the following, we describe each phase in more detail.

Phase 1: Basic configuration

Step 1: Import the Factory Design Automation (FDA) library.

from fda import *

Step 2: Define your product, tool, and machine types.

# Step 2.1: Define your product types
# (everything from raw material to end product)
pt1 = ProductType("Raw material 1", ...)
pt2 = ProductType("End product 1", ...)

# Step 2.2: Define your tool types
# (all types of tools you are using in your production)
tt1 = ToolType(...)

# Step 2.3: Define your machine types
# (all types of machines you are using in your production)
mt1 = MachineType(...)

Step 3: Define your executable operations.

# Produce PT2 from PT1 on MT1 with TT1
o1 = Operation(..., mt1, tt1, pt1, pt2)

Phase 2: Scenario configuration

Step 4: Define your scenarios including orders for product types (see Basic Configuration)

# Step 4.1: Define your scenarios
s1 = Scenario(...)
# Step 4.2: Define your orders in the scenarios
o1 = Order(..., pt1, s1)

Phase 3: Layout configuration

Step 5: Define your factory layouts including corridors, and machines (i.e. instances of machine types).

# Step 5.1: Define your layout variants
l1 = Layout(...)
# Step 5.2: Define your corridors for the layout variants
c1 = Corridor(..., l1)
# Step 5.3: Define your machines for the corridors of the layout variants
m1 = Machine(..., mt1, c1, ...)

Phase 4: Performance evaluation

Step 6: Evaluate the performance of a layout variant in a given scenario.

# Simulate L1 on S1
simulate(l1, s1)

๐Ÿ“ˆ Models

Here are some models explaining our overall idea:

Class model

The class model describes the core entities, which are implemented in our factory design software. The entities include product types, which represent everything from raw material to end product. Then, the entities include tool and machine types as well as available manufacturing operations. On top you define layouts and scenarios.

Class model

Object model

The object model describes a sample use case. The use case is concerned with producing metal gears from raw metal disks. The use case includes milling and grinding as possible operations. Furthermore, the use case includes two different types machining centers, on which these operations can be executed as well as different order scenarios.

First object model

Object model 1

Second object model

Object model 2

salabim-grid-plant-3d's People

Contributors

ghackenberg avatar sammarcochiara avatar

Stargazers

 avatar

Watchers

 avatar

salabim-grid-plant-3d's Issues

Support operations with multiple inputs/output

Currently, all operations can only have exactly one input and exactly one output. In the future, it might be interesting to model cases were an operation has multiple inputs and/or multiple outputs (e.g. an assembly step).

Support stochastic operation times

Currently, the duration of robot movements, mounting and unmounting of tools, and processing materials is static. In the future, probability distributions should be introduced, to support variations in operation times.

Improve visualization of order KPIs

Currently, the visualization includes one chart per order. In the future, all orders should be aggregated into one chart. The visualization should be more compact to support scenarios with plenty of orders.

Store configuration models in data files

Currently, the models are stored in Python scripts. In the future, the models should be stored in data files instead. Then, a parser component should read the data files and create corresponding Python objects from it.

Introduce controller interface

Currently, the control decisions are embedded into the main robot, the arm robot, and the job classes. In the future, it should be possible to connect different control strategies to the simulation environment. Therefore, a flexible controller interface must be introduced, for which different implementations can be provided.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.