Manual Data Entry and Automated Data Entry
By default, data is manually entered by operators into the Production Dashboard. DPM also allows data entry to be automated and entered directly into DPM from sensors on a machine or other integrated data sources. Depending on your system’s setup, data may be manually entered only, entered by automation only, or by a hybrid of both.
Automated events reflect the status of the connected pacemaker at any given time. These automated events can start and stop production on job orders, as well as be logged as loss events when the pacemaker is down. Production count and scrap count can also be entered by automated data entry. For more information, see Setting Up Data Automation.
The data on the Production Dashboard is updated as automated events are received, including events that start and stop production on job orders.
There are some key differences between manually entered events and events entered by automation:
|
Manually Entered Events
|
Automated Events
|
||
|---|---|---|---|
|
Loss events (other than scrap) that are manually entered have both a start time and a duration.
|
Automated events (other than scrap) have a start time, but do not end until the next automated event is received.
|
||
|
Manually entered loss events appear in the Event Log.
|
Any automated event that reflects a loss appears in the Event Log. These loss events that were entered by automated event entry are indicated with an asterisk ( * ) after their impact value (quantity or duration).
|
||
|
Automated loss events cannot be edited until they have ended, that is until after the next automated event is received.
Events that were split from an automated event are also considered to be automated events. They can also be edited and split, but can only be deleted from the Split Event Entry window for the original automated event from which they were split.
|
|||
|
During the current production block, Production count is manually entered from the Production Entry pane, while scrap count is manually entered by entering a loss event with the Scrap loss category from the Loss Event Entry pane. For production blocks closed within the past 24 hours, production count and scrap count can be added from the Time Loss Accounting window. For job orders that completed within the past week, scrap count can be added by entering historical scrap events. These counts are updated on the Production Dashboard where the Good and Scrap counts display.
|
When production count and scrap count are entered by automated data entry, these counts are automatically updated on the Production Dashboard where the Good and Scrap counts display.
|
||
|
For manually entered loss events, the Work Unit Causing Event can be the pacemaker for the work center, or it can be an upstream or downstream work unit.
If the pacemaker is selected as the Work Unit Causing Event, you can only select reasons from the loss category matching the selected Event Category. If a work unit other than the pacemaker is selected as the Work Unit Causing Event, you can select any loss reason that is valid for the selected work unit, from any loss category.
|
Automated events are logged against the pacemaker. This means that for an automated event, the Work Unit Causing Event is always the pacemaker, and the Event Category and Loss Category are always the same.
|
||
|
The actual cycle time for a completed job order is recalculated when the total production count for the job order is manually changed by:
• Adding or removing production count through the Time Loss Accounting window.
• Adding or editing scrap loss events from the Time Loss Accounting window.
|
The actual cycle time for a completed job order is not recalculated if there are automated events that are processed after the job order has been completed.
|
