Initial DPM Administration Activities
After your data has been imported and before making DPM available to users, an administrator must complete the following activities in Administration:
1. Ensure that your materials are present as expected. You can create new materials as needed. For more information, see Materials.
2. Ensure that reason trees are assigned to your equipment and materials as expected. You can create new reason trees and update assignments as needed. For more information, see Reason Trees.
3. Ensure that calendars are assigned to your equipment as expected. You can create new calendars, including creating new shifts and shift schedules, update the shifts and shift schedules for your existing calendars, and update the equipment assignments as needed. For more information, see Shifts and Calendars.
4. Ensure that the production block duration and OEE thresholds are set appropriately for each site in your equipment list. For more information, see Site Configuration Tab.
5. Ensure that materials are added to the work centers that produce them, and that the material settings are appropriate for each work center. For more information, see Material Settings Tab.
6. If you are setting up data automation, ensure that the machine codes for each pacemaker work unit are mapped to the appropriate reason codes. For more information, see Machine Code Settings Tab.
7. Set the target values and status thresholds for the metrics used in Scorecard, as required. For more information, see Target Definition Tab and Status Threshold Tab.
8. Optionally create job orders. For more information, see Job Orders.
The following activities can be completed after DPM has been in use over time:
1. Optionally set up pipeline schedules for each of your areas. The pipeline schedules push data that is analyzed for the View Loss Insights action in Performance Analysis. This setup step can be performed at a later time, after DPM has been in use and production data has been gathered. At least one month of data (or more than 500 production blocks) are needed for repeating patterns and scenarios to be identified. For more information, see Time Loss Analytics.
2. Create demand windows for your sites and configure demand as needed for bottleneck analysis. For more information, see Configuring Bottleneck Analysis.
 |
If multiple enterprises were imported during data import, ensure that the name of the correct enterprise is configured. Only one enterprise can be configured, and only data for the configured enterprise is available in Production Dashboard and throughout DPM.
To configure the enterprise, complete the following steps in ThingWorx Composer:
1. Navigate to the PTC.MfgModelImpl.Manager Thing and click Edit. 2. Under Configuration, scroll to the NetworkConfiguration configuration table and click  in the table row.3. In the edit window, enter the Thing name of the network entity for the enterprise in the network field. This is the Thing name that was specified for the enterprise when the data was imported. Do not change the value of the id field. 4. Click Set to close the edit window. 5. Click Save to save the configuration changes. |