Event option


The Event option is a feature to specify an event condition such as the number of times of production performed on a resource and generate an event (i.e., automatically generate and assign an event order) for the resource when the event condition is satisfied.


For example, you can specify to assign 60 minutes of cleaning after production is performed 10 times on a resource.
You can describe "180 times of production" as a conditional expression. You can specify various other conditions such as those listed below.

  • When 500 units have been produced
  • When production time reaches 100 hours
  • When the number of days during which a resource is not used becomes 7 or more
  • When the num spec 1 value of a production item totals 100
  • When the spec 1 or spec 2 of a production item is changed When the spec 1 and spec 2 of a production item are changed
  • When spec 1 (color) of a production item is white
  • When an input item (raw material) is changed
  • Specifying allowed start time or allowed days of week in which event orders can start

Basic usage

Based on the result of scheduling, event orders will be generated and assigned according to event conditions.
Since events are processed during execution of the adjustment command, you will need to include the adjustment command in the scheduling parameter.
When assigning event orders, the sequence of operations resulted from scheduling will not be changed but operations will be moved to the future. When assigning event orders, the sequence of operations resulted from scheduling will not be changed but operations will be moved to the future.

You can specify the codes of event orders to generate using the property "Event order code expression" in the Code generation tab of the project settings.


Event properties

You can specify other settings such as event conditions from the Event tab of the scheduling parameter settings.


Specify a name of an event condition in the property [Event condition] in the Event tab of the scheduling parameter settings.
If you click on the "->" button shown to the left of the event condition name you specified, the properties window will be switched to display properties for the event condition.


General tab

Conditional expression

Specify here the condition by which to generate an event.

 (Example)  
 ME.EventObjectEval[1].Counter >1000 When the counter of the parameter of the event object becomes larger than 1000
 ME.LeftOperation.Order.Item != ME.CurrOperation.Order.Item When the item of the left operation and that of the current operation is different

Duration

Specify here the amount of time that will be consumed by the event. For the item used by exploding order, this property value will be ignored. The [Production] property set in master table is given priority used to calculated the assignment time.

 (Example)  
 1.5h+5h Event of 6.5 hours
 IF( ME.CurrentOperation.Order.Item == 'ItemA', 1.5h, 3h ) 1.5 hours when the item of the current operation is "ItemA", and 3 hours otherwise.

Resource

Specify here the resource on which the event will occur. Specify an existing resource code. You cannot specify the resource group.
When the item used by exploding order is not set, specified resource is assigned to the event order.
When the item used by exploding order is set, the resource related with the item in master table is assigned to the event order.


Item used by exploding order (Ver.9 restricted features)

The item defined in master table is specified, event order is exploded according to master table and assigned.

In other words, the use instruction, input instruction and output instruction related with the event order are assigned when exploding the event order. If there are several backup resources in master table, the resource with highest evaluated result is assigned to generate the event order.

Followed cases can be handled.

  1. Consider the operator sub resource and make an event plan.
  2. There are setup and tear down in event order.
  3. Load balance of event order.
  4. The resource evaluated for event condition and the resource assigned to event order can be different.
In other words, the resource in event condition may be different with the resource registered in the master table.The resource assigned to event order can be different with the resource in event condition.
  5. There are input instruction and output instruction before and after the event order is occurred.
If there are input instruction and output instruction for the specified item, the inventory qty can be displayed in inventory graph.
Take cleaning the container (event order) for example, there should be input instruction before cleaning the container, and output instruction after cleaning the container.

Additional, other common functions in master table and resource table, such as "Required resource quantity" in master table, "Allowed start time" in resource table and so on, can be used as the same way with the manufacturing order. But followed functions can not be used.

  1. Multiple processes
Set multiple processes in master table for event order. Only the last process is available.
  2. Split operation
Even you set splitting operation in operation, item, master, resource classes, the operations for event order cannot be split.

 

Event order property setting expression (Ver.9 restricted features)

This feature is used to add, modify or delete the property value of the event order.
This setting expression is used just before exploding orders.
You can set the quantity or comment of event order.


Event counter

Specify here the method of counting and so on to be used for the conditional expression.
Specify a name in the property [Event counter].
If you click on the "->" button shown to the left of the event counter name you specified, the properties window will be switched to display properties for the event counter.

 

Time periods tab

Allowed start time for operations of event order

Specify here the time periods during which operations of the event order can start. Concatenate the start time and end time with a hyphen "-". You can specify multiple time periods separated with semicolons. The method of specifying the time periods is the same as specifying shift patterns in the calendar table.


Allowed days of week for operations of event order

Specify here the days of week during which operations of the event order can start. You can describe days of week as Sun, Mon, Tue, Wed, Thu, Fri, and Sat. Concatenate two days of week with a hyphen "-". You can specify multiple periods of days of week separated with semicolons. The method of specifying the time periods is the same as specifying shift patterns in the calendar table.

 

Settings tab

Assignment position

Specify here the position to which, to assign operations of the event order.

 After operationAssigns operations of the event order after the operation, during which the event condition was satisfied.
 After previous operationAssigns operations of the event order after the previous operation of the operation, during which the event condition was satisfied.
 Before operationAssigns operations of the event order immediately before the operation, during which the event condition was satisfied.

 

Comments

Specify here comments.


Color

Specify here the display color of bars of the event order. This color will be set in the property "Display color" of the event order when it occurs.


Scheduling parameter

Scheduling parameter in which the event is registered.

 

Event counter

 

General tab

Increment expression

Specify here how the value of the counter should increase for operations using an expression.

 (Example)  
 ME.CurrentOperation.OperationOutMainItemQty Adds production quantities of operations.
 ME.CurrentOperation.OperationProductionTime Adds production times of operations.

 

Counter start time

Specify here the time at which the counter initialization value (first time) will be active.

 (Example)  
 2005/12/31 Specifies that the initialization value will be applied on 2005/12/31.

 

Counter initialization value (first time)

Specify here the initialization value for the counter as of the time specified in the "Counter start time". When no value is specified for the counter start time, the specified value will be applied from the scheduling start time.


Counter initialization value (after event occurs)

The counter will be initialized when the conditional expression is satisfied. Specify here the value to which the counter should be initialized at that time. The default is set to 0. When an expression is specified for "Counter initialization value expression (after event occurs)", expression results will be used.


Counter initialization value (after event occurs)

The counter will be initialized when the conditional expression is satisfied. When an expression is set, the result of the expression is used as the value of "Counter initialization value (after event occurs)”. When nothing is set, the value specified for "Counter initialization value (after event occurs)” is used.

 (Example)  
 Value of the counter at an event occurrence subtracted by 100 ME.Counter-100

 

Examples

Below are the examples of how to specify event objects. A project Sample 1: Packing is used in the examples.

Example 1

Specify an event with the following conditions.

  1. Generate an event order on resource Mixer1.
  2. Generate the event order after the operation during which the production of 150 or more pieces is completed.
  3. 50 pieces has already been produced as of the scheduling basis time.
  4. Duration of the event order is 6 hours.
  5. Allowed start time for operations of the event order is between 17:00 to 23:00.

Settings

In the property "Event condition" in the Event tab of the scheduling parameter settings, specify "Mixer1 Maintenance" as a name of the event condition.


Set properties of event condition "Mixer1 Maintenance" as follows.

 Conditional expression ME.EventCounter[1].Counter >=150
 Resource Mixer1
 Event counter Production qty
 Color 1

 

Set a property of event counter "Production qty" as follows.

 Increment expression ME.CurrentOperation.OperationOutMainItemQty
 Counter start time 2003/6/5
 Counter initialization value (first time) 50

 

In the property "Event order code expression" in the Code generation tab of the project settings, specify an expression so that the code of the event will be displayed as the name of the event condition followed by a serial number.

ME.Event[1].Code+ '_'+Func_GenStrSerialNum(PROJECT.Project_EventOrderSerialNumber,4)

If you reschedule, the event order will be assigned as in the diagram below.

  • Since 50 pieces is already produced as of 2003/6/5, the total production quantity exceeds 150 from adding the initial value of 50 and the production quantities 30 and 90 of the first and second operations. Therefore, event order Mixer1 Maintenance_0000 is generated.
  • Also, another event order Mixer1 Maintenance_0001 is generated when the total production quantity exceeds 150 from adding the production quantities 25, 80, and 50 of the three operations after the first event order.

 

Specify the property "Allowed start time for operations of event order" of event condition Mixer1 Maintenance as 17:00-23:00.

 

If you reschedule, the event order will be moved to the left to satisfy the allowed start time.

 

Example 2

Specify an event with the following conditions.

  1. Generate an event order for resource InspectionCenter1 before the operation during which the total production quantity reaches 100 or more pieces.
  2. Duration of the event order is 8 hours.

Settings

In the property "Event condition" in the Event tab of the scheduling parameter settings, specify "Inspection Maintenance" as a name of the event condition.

 

Set properties of event condition "Inspection Maintenance" as follows.

 Conditional expression ME.EventCounter[1].Counter >100
 Duration 8h
 Resource InspectionCenter1
 Event counter Param
 Assignment position Before operation

 

Set a property of event counter "Param" as follows.

 Increment expression ME.CurrentOperation.OperationOutMainItemQty

 

If you reschedule, event orders will be assigned before the operations during which the total production quantity exceeds 100.

 

Example 3

Two event objects are specified as in the following diagram. Both of the objects will generate event orders depending on the production quantity.
Event100 will generate an event order when the production quantity reaches 100 or more and Event200 will generate an event order when the production quantity reaches 200 or more.
The "Counter initialization value (after event occurs)" is set to 0 and "Counter initialization value expression (after event occurs)" is blank.

When you reschedule, event orders will be assigned as in the following diagram. (Event orders of Event100 is shown in orange and of Event200 in blue.)

 

Event conditions of Event100 and Event200 are specified as "100 or more" and "200 or more" respectively, meaning that the value of Event200 is just twice as much as that of Event100. However, Event100 will not always occur at the same time as Event200 occurs. That is because, depending on the production quantity of an operation, there may be a difference between the counter value and conditional value when the event condition is satisfied. Since the counter is initialized to zero, the difference will occur.
In the following diagram, the difference of 21 occurs for Event100 and 18 for Event200.

 

To generate event orders for Event100 at the same time as for Event200, you can use the property "Counter initialization value expression (after event occurs)" for Considerring the difference.
For the "Counter initialization value expression (after event occurs)" for Event100, specify

ME.Counter-100

For the "Counter initialization value expression (after event occurs)" for Event200, specify

ME.Counter-200


If you reschedule, event orders for Event100 will be generated at the same time as event orders for Event200 are generated.

 

Occurrence sequence when multiple events occur at the same time

When multiple events occur at the same time, event orders will be generated in the sequence in which the event objects are registered.

For example, as in the following diagram, when two event objects are registered in the scheduling parameter in the sequence of "Event1" and "Event2", event orders will be generated in that sequence. (The red order E0000 is generated from event object Event1 and the yellow order E0002 is generated from event object Event2.)

 

Opposite to the above example, the diagram below shows the case where event objects are registered in the sequence of "Event2" and "Event1". Event orders are assigned in the reverse sequence of the above example.

 

Event order and changeover

If there is a changeover between operation A and operation B, or the setting of “Zero setup time between same items” in the project settings is effective and the teardown time and the setup time are zero, inserting an event order here causes a new changeover between operation A and the event order, and the event order and operation B. To avoid this, set the “Keep assignment order of operations” property of the resources to which the event order is assigned to “Yes (Keep also the setup time)” so that the setup time before the event order was inserted is kept. “Yes (Keep also the setup time)” has been added since Ver. 15.0.

Setting the “Keep assignment order of operations” property to "Yes” results as follows.

  1. When calculating the changeover of a manufacturing order, the event order operation is ignored and the operation next to it is looked for.
  2. Changeovers in the event order no longer occur. Static setup occurs.
  3. Even if the checkbox of "Zero setup time between same items" in the project settings is selected, the static setup of the event order will not be deleted.
  4. By setting the “Keep assignment order of operations” property of the main resource of the operations of the event order to “Yes (Keep also the setup time)”, 1, 2 and 3 above are applied regardless of the setting of the “Keep assignment order of operations” property of the sub resources of the operation of the event order.

Restrictions

There are a number of restrictions on the event condition function.
For details, please see the event option reference that was included when installing Asprova.
For details, please see the event option reference that was included when installing Asprova.


There are some known issues with the event condition function.

Logic 9As a result of assigning event orders to a resource, there may be spare time for resources to which event orders are not assigned.

Logic 15When the assignable position of an event order is restricted by "Allowed start days of week for operations of event order" the assigned position may differ from the expected position.



HelpNo.:777600
© Since 2018 Asprova Corporation, All rights reserved.