Discrete Event Simulation Process

Discrete Event Simulation is a great tool to use in the early stages of the automation life cycle. In general, discrete event simulation engineering activities can be grouped into 2 phases starting with process conception and ending in system startup support.

Process conception:

Do you know what equipment is needed to achieve the most optimized throughput in your manufacturing process?  Discrete Event Simulation is a powerful tool to analyze alternate scenarios to identify the resources and processes required to meet your production needs. If you need to analyze your production system, contact us to perform a process study. Some of the key results you can get from using Discrete Event Simulation for process conception are:

  • Resource requirements and allocation
  • Production volume estimates
  • Facilities planning
  • Identify bottlenecks,
  • Balance line production

Final System Design and Process Validation:

If you have decided to use robotic simulation to validate your process and are focusing on tooling/ fixture mechanical design and facilities layout development, contact us to show you how Discrete Event Simulation can interactively validate the full system process as it evolves.  Discrete Event Simulation can help identify cycle time issues and propose process changes to remedy them.  Some of the key results you can get from using Discrete Event Simulation during design process validation are:

  • System wide cycle time impact
  • Refine resource constraints
  • Identify buffer requirements like conveyors and transfer systems
  • Final production output

Modifications to existing systems

Often during installation, production systems that have changed or had not been simulated during the process and design phases exhibit unexpected behavior and do not meet requirements.  An in-depth analysis can be performed using Discrete Event Simulation to identify the root cause and propose solutions in a timely manner.

  • Identification of root causes of poor system performance
  • Run multiple scenarios and observe system impact
  • Avoid “domino effect” of changes for the worse
  • Cost savings due to virtual validation prior to change implementation