• Loss events now include the ability to designate the Event Category which is the loss category for the event on the pacemaker, as well as the Loss Category and Loss Reason for the event on the Work Unit Causing Event, when the work unit that caused the event is not the pacemaker. For example, there could be 10 minutes of unplanned downtime on the pacemaker that resulted from a scrap event on an upstream work unit. For more information, see Editing Loss Events.

• The pacemaker for the work center now appears at the top of the Add Loss Event, Edit Loss Event, Time Loss Accounting, Historical Scrap Event, and Split Automated Event windows.

• The Production (materials) block now displays the Good, Scrap, and Expected counts on the Add Loss Event, Edit Loss Event, Time Loss Accounting, Historical Scrap Event, and Split Automated Event windows.

• When using manual data entry, the good count and scrap count are now user-entered values, and the total production count is calculated by adding the good count and scrap count together. Previously, the total production count and scrap count were user-entered values, and the good count was calculated by subtracting the scrap count from the total production count.

• When a scrap loss event is added in the Production Dashboard, the good count is not changed unless the Reallocate From Good checkbox is selected. When the checkbox is selected, the amount entered for the scrap event is also removed from the good count. Previously, when entering a scrap loss event in Production Dashboard, the scrap count for the event was automatically subtracted from the good count for the production block, unless the Add to Production Count checkbox was selected. When the Add to Production Count checkbox was selected, the scrap count for the event was added to both the scrap count and the total production count, leaving the good count unchanged.

• The fields on the bottom right of the Time Loss Accounting window, which show the status of the time loss accounting, have been updated: Production Block Length, Effective Production Time, Total Logged Losses, and Time Loss Unaccounted For.

• For more information, see Production Dashboard.

• The data displayed in the waterfall and Pareto charts includes events for all work units in a work center. Previously, only data for the current pacemaker in a work center was included.

• Use the Show Average Week toggle in Performance Analysis to see what data on waterfall and Pareto charts looks like when normalized for an average 168-hour week. For more information, see Showing Data for an Average Week.

• The blue bars in the waterfall chart display the loss categories that are set as the Event Category on loss events entered in the Production Dashboard.

• The blue bars in the top-level Pareto chart (Pareto 1) show the loss categories for events which have the Event Category that was selected in the waterfall chart. The blue bars in subsequent Pareto charts show the loss category and the loss reasons. For events where the Work Unit Causing Event is the pacemaker, the loss category is the same as the event category. For events where the Work Unit Causing Event is not the pacemaker, the loss category can be different from the event category.

• For more information, see Performance Analysis.

• Actions against a work center now collect and show data from all work units on the work center. Previously, actions against a work center showed data only from the designated pacemaker work unit for the work center.

• Both the Time Loss Trend chart on an individual action and the Total Loss Hours chart on the main Action Tracker page show data from loss events which match the loss category and loss event for the individual action or the applied Loss Category filter, respectively. The event category for those loss events is not considered for these charts.

• When an action is against a work center, each dot on the Time Loss Trend chart represents the sum of all events on that day, with the selected loss reason, which were caused by any work unit in the work center. When an action is against a work unit, each dot in the chart represents the sum of all events on that day, with the selected loss reason, which were caused by the selected work unit.

• The Baseline OEE and Current OEE values that are shown on an action are calculated for the work center. When the action is against a work unit, these values are calculated for the work center to which the work unit belongs.

• For more information, see Action Tracker.

• The production and scrap rollover counters for automated equipment reset to 0 when the rollover value is reached. Previously, the counters also reset when the job order changed on the pacemaker work unit Thing.

• When the reallocateFromGoodCount checkbox is selected (TRUE) for a scrap property, the scrap count received for the property is reallocated from the good count which has already been recorded.

• For more information, see Setting Up Data Automation.

• In Administration, there is now a section for reviewing the historical best demonstrated speed information.

• The Ideal Cycle Time for a material can be manually edited or you can select a value to use from the Historical Cycle Time list. This list displays the actual cycle times for job orders completed for that material on the work center in the past six months that are faster than the current ideal cycle time.

• The Best Demonstrated Speed for the material is the fastest actual cycle time that appears in the Historical Cycle Time list. If there is an actual cycle time in the list that you do not want to be considered for the Best Demonstrated Speed, it can be hidden from the list.

• For more information, see Material Settings Tab and Selecting the Ideal Cycle Time from the Historical Cycle Times List.

• The pacemaker for a work center can now be changed from the Material Settings tab for the work center in Administration > Equipment List. Previously the pacemaker was changed using a service in ThingWorx Composer.

• For more information, including the impacts throughout DPM when a pacemaker is changed, see Changing a Pacemaker.

• Materials can now be created and edited from the Material Configuration page under Administration. For more information, see Creating a Material and Editing a Material.

• Materials can be disabled and enabled. For more information, including the impacts of disabling a material, see Enabling and Disabling Materials.

• Reason trees can now be created and edited from the Reason Trees page under Administration. For more information, see Creating a Reason Tree and Editing a Reason Tree.

• Within a reason tree, reason codes can be created and edited. For more information, see Creating a Reason Code and Editing a Reason Code.

• Both reason trees and individual reason codes within a reason tree can be disabled and enabled. For more information, including the impacts of disabling a reason tree or reason code, see Enabling and Disabling Reason Trees and Enabling and Disabling Reason Codes.

• Calendars can now be created and edited from the Calendars tab of the Shifts & Calendars page under Administration. Within a calendar, individual calendar days can be added and removed from the end of the calendar. Shift schedules can be assigned to calendar days. For more information, see Calendars.

• Shift schedules can now be created and edited from the Shift Schedules tab of the Shifts & Calendars page under Administration. Within a shift schedule, shifts can be created and edited. For more information, see Shift Schedules.

• For information on how and when shift instances are created to be used in production, see Understanding Shift Instances.

• The Good Quantity column in the job orders list displays the good count of material produced for the job order. Previously, this column was named Quantity Completed and showed the total quantity completed for the job order, both good and scrap count. This column update appears on both the main Job Orders page and the Job Orders tab for areas and work centers.

• For more information, see Job Orders and Job Orders Tab.

• Starting with release 1.1, the supported minimum screen resolution for DPM is 1280x1024.

• The mashups topics for the Production Dashboard, Performance Analysis, and the Action Tracker building blocks have been updated to reflect user interface changes made in DPM 1.1. For more information, see Mashups in Production Dashboard, Mashups in Performance Analysis, and Mashups in Action Tracker.

• Default values can now be specified on Data Shape fields in the DPM data model. For more information, see Adding Custom Properties to Data Model Entities and Adding Custom Entities to the Data Model.

• Administration Building Block—

◦ A new HistoricalLookbackConfiguration configuration table has been added. For more information, see Configurations (Administration Building Block).

• Database Connection Building Block—

◦ When DPM is deployed, the comprehensive logging of historical data is disabled. This limits the logging of historical data to only those actions that are required by other functionality. You can configure the set of limited actions that are logged when comprehensive logging is disabled. For more information, see Configuring What Historical Data is Logged.

◦ The list of logical operators that can be used in a filters key has been updated. The filters key also supports isCaseSensitive. For more information, see Using JSON Filters in Query Services.

• Job Order Building Block—

◦ New fields have been added to the PTC.JobOrder.JobOrderExecutionResponse Data Shape: actualCycleTime and enabled. For more information, see Database Schema (Job Order Building Block).

• Material Master Building Block—

◦ A new enable field has been added to the PTC.MaterialMaster.MaterialMaster Data Shape. For more information, see Database Schema (Material Master Building Block).

• Operation KPI Building Block—

◦ New properties have been documented: jobOrderLookBackRange and minEventAgeInDays on the PTC.OperationKPIImpl.DatabaseUtility_TT Thing Template, and PTCLastAutomationProcessedValues on the PTC.OperationKPI.AutomationEventsModelLogic_TS Thing Shape. For more information, see Key Properties (Operation KPI Building Block).

◦ New eventCategoryUid and eventTypeUidfields have been added to the PTC.OperationKPI.ProductionEvent, PTC.OperationKPI.AvailabilityEvent, and PTC.OperationKPI.LossEvent Data Shapes.

◦ For more information, see Database Schema (Operation KPI Building Block).

• Reason Code Building Block—

◦ A new Invalid reason type and reason category have been added. For more information, see Default Reason Types, Reason Categories, and Reason Trees.

◦ A new enable field has been added to the PTC.ReasonCode.ReasonTreeNode Data Shape. For more information, see Database Schema (Reason Code Building Block).

• For more information on updates to the database schema, see Database Schema Changes in this topic.