IO48x48Icon

Input - Output Combinations, as defined on the Input - Output Tab of the Step Definition Form, define how the input of a Step Definition will change when it will move to the next step.

AKA: Input-Output Conversions are also known as Input Output Constraints or Input Output Combinations.

Different uses for Input-Output Conversions

Input Output Conversions can be used for different functions. There are basic ones, and special ones that can be specified using the Input-Output Type on the Form.

NOTE: The Part Definition of the Part Record only changes at the moment the step successfully is completed and the Part Record moves to next step as defined on the Flow Definitions.

Default

  • ANY -> ANY

If no 'Input - Output' combinations are defined in the Input - Output Tab then all Part Definitions can move through the Step Definition. This allowance is good for Flow Definitions such as an inventory receive Flow, which can receive many different types of Parts.

Simple Conversion Type - automatically applied when not selected, those are:

  • Constraint - Part A to Part A

If only a single 'Input - Output' is defined for a Step Definition than only the 'Input' can pass through this Step, all other Parts with different Part Definitions will not be permitted to enter this Step. This can make sure for example that only certain products can move through the Step and Flow.

IO-SimpleSample

  • Conversion - Part A to Part B

It is possible that, due to a manufacturing operation (step), the definition of a part changes. This is usefull if you want to see the difference of the input and the ouput part in the EZ-MES system (e.g. for the inventory count). To change this definition first an input Part Definition will be assigned, followed by a new/different output Part Definition that will be be connected to the Part Record

  • One to Many - Part A to Part B or Part C or Part D

One Input is selected, and different Outputs. Depending on the configuration of the flow those products are created. For example the Step converts the T-Shirt into either a Part B T-Shirt, Part C T-Shirt or Part D T-Shirtt, depending on what Graphic is printed on it.

  • Many to one - Part A, or Part B or Part C to Part D

This is the opposite as with the previous IO combination. The only difference is any of the Input Parts will all be converted to the single Output Part. This would make it a 'Many to One' type of conversion. You might have a few different 'Dirty Widgets' ( Dirty Widget A, Dirty Widget B, etc. ) that possibly go through a cleaning process and become a finsished 'Clean Widget'.

  • Combining Inputs - Outputs in a Flow Definition

When Step Definitions are combined in a Flow Definition the combination of all the 'Input - Output' constraints will determine which parts can move through the Flow.

  • Change number of parts - Part A quanty 1 to Part B quantity 20

In addition to a Part Conversion it's possible that the quantity changes due to the operation. This can be controlled by the Quantity field on the Input - Output combination (See example for more details: Splitting one part into many parts)

  • Change User Defines States

On the Part Definition its User Defined State can be defined and then the Input - Output Combination handles the defined state change from one state to the next.

Combine Conversion Type

  • Change number of parts - Part A quantity 10 to Part B quantity 1

Combine Inputs into a new Output, for example loading 10 finished products into a pallet.

When products are consumed, it should not be done with this Input - Output option, but by using the Material consumption.

 IO-CombineSample

Force Conversion Type

The Force Conversion Type takes an Input Part and Forces it to a Child Part of the Output Part.

IO-ForceSample

Useful Links