• All quantities can be entered and stored with up to 5 decimal places. When displayed, quantities are rounded to 2 decimal places.

• Key performance indicators which are displayed as a percentage, such as OEE, are rounded to 1 decimal place.

• Rounding takes place at the display-level only. All calculations are performed using the actual stored values.

• The rate of production represented by each count that the rollover counter receives is compared to the maximum machine rate for the pacemaker to determine if the count represents valid data. The maximum machine rate can be specified or DPM calculates the value as 3 times the ideal cycle time for the material that is being produced.

• The reset value that is configured for each rollover counter is now treated as the expected value at which the counter rolls over, rather than as a hard-coded rollover value. This allows calculations to address situations where the count received by the rollover counter exceeds the configured reset value. The reset value can now include decimal points.

• In High Availability (HA) environments, the Distributed checkbox for the PTCAutomationEventProcessingTimerSubscription on the PTC.OperationKPI.AutomationEventsModelLogic_TS Thing Shape is enabled by default. This improves performance by distributing the processing of automated data across the HA clusters.

• For more information, see "Distributed Subscriptions" in Thing Subscriptions and ThingWorx High Availability in the ThingWorx Platform Help Center.

• The Log checkbox is now selected by default on the following remote properties: PTCAvailabilityEventFaultCode, PTCJobOrderID, PTCMaterialMasterID, PTCProductionCount, and PTCTargetQuantity. As a result, all data for these properties is automatically added to the value stream.

• When the value stream is queried for unprocessed data, only those entries for the queried time frame with GOOD quality are returned. In previous releases, this behavior was handled using subscriptions on the remote properties. For more information, see "Batch Processing of Automation Events" in Additional Automation Information (Operation KPI Building Block).

• When new scrap properties are created, their Log checkbox must be manually selected so that their associated data is automatically added to the value stream. For more information, see "Logging Scrap Counts" in Logging Scrap Counts.

• A new property, purgeChunkDurationInMinutes, has been introduced on the PTC.OperationKPI.AutomationPurgeScheduler entity which divides the time range of the data to be purged into chunks of the specified number of minutes. This results in multiple smaller calls to purge the data instead of a single larger call, which in turn reduces the amount of time the value stream table might be subject to a table lock due to the MSSQL server lock escalation policy.

• The start time for the time range of data to be purged is now determined by the timestamp of the oldest value stream entry for any of the remote properties, rather than subtracting the value of the dataAgeInHours property from the end time of the time range. This ensures that no old entries are left in the value stream.

• For more information, see "Scheduled Data Purge" in Additional Automation Information (Operation KPI Building Block).

• Production blocks that are more than 24 hours old can now be viewed in the Production Accounting pane. By default, you can view production blocks for shifts and dates from the past 13 days, including the current date.

• Use the Date field and navigation arrows to navigate to past shifts and dates to view past production blocks.

• The Actual OEE field shows the value calculated for the time frame that is currently shown.

• For more information, see "Production Accounting Pane" in Production Dashboard.

• The colors used for each loss event category in the Loss Event Entry and Event Log panes have been updated to avoid overlap with the colors used for the OEE status display of production blocks in the Production Accounting pane.

• You can now perform all time loss accounting actions for a closed production block from a single screen. Loss events can now also be edited from Time Loss Accounting.

• For more information, see Time Loss Accounting for a Closed Production Block.

• When editing individual automated events, the Work Unit Causing Event and Loss Reason can now be changed.

• Disabled reason codes are no longer displayed in the Select Loss Reason pane of the Edit Loss Event window. If a loss event has a disabled reason code selected as its Loss Reason, this is displayed in the Loss Reason field. When a new enabled loss reason is selected, the disabled loss reason no longer displays under the Loss Reason field.

• For more information, see Editing Loss Events and Editing Loss Events in Time Loss Accounting.

• The Job Order Summary pane is no longer displayed when viewing the expanded Event Log. This provides more room for displaying events.

• The new collapsible Filters pane allows you to filter the events in the expanded Event Log on multiple criteria.

• Full comment text for loss events in the Comments column. The new Alert column displays an alert icon when the reason selected for the loss event is not at the lowest level of the reason tree.

• The Work Unit Causing Event and Loss Category for each event now display in columns on the expanded event log.

• A Last Updated column has been added to show the updated date for edited loss events.

• The Time of Entry is now shown for scrap events entered through data automation, as well as for other automated events.

• For more information, see Expanded Event Log View and Filtering the Expanded Event Log.

• Editing manually-entered loss events after the first 24 hours.

• Deleting manually-entered loss events after the first 24 hours.

• Editing loss events added through data automation after 24 hours.

• When navigating from the waterfall chart to the Pareto charts, if the blue bar selected in the waterfall chart represents a single work unit with loss data, then the Pareto 1 chart contains the same information as the selected blue bar. In this case, the navigation skips the Pareto 1 chart and takes you directly to the Pareto 2 chart.

• For more information, see Navigating Between Charts.

• The Time Loss Analytics feature is now supported on customer-owned systems or cloud deployments as well as on PTC Cloud deployments.

• For more information see DPM Customer Deployments and Upgrading DPM Customer Deployments.

• You can now click the View Loss Insights button without selecting the blue bar for a loss category in the waterfall chart to view loss insights for all loss categories.

• For more information, see Viewing Loss Insights.

• You can now configure the area settings for the area directly from the Loss Insights page by using the Configure and Rerun button, as well as from the Area Settings page.

• For more information, see Loss Insights.

• The Materials List table for a work center has been moved to a separate Materials List tab. This allows more materials to be viewed at a time. The Material Settings tab has been renamed to Production Settings.

• For more information, see Production Settings Tab and Materials List Tab.

• The color displayed for OEE in Production Dashboard and Performance Analysis is determined by the values set on the Status Threshold tab for the Production OEE metric in the Metrics administration tool. This value can be set for individual work centers or set at a higher level of the equipment list and inherited by the work center.

• In previous releases, this configuration was performed from the Site Configuration tab in the Equipment List. This setting remains in the current release on the Site Configuration tab as read-only information to be available for comparison purposes on upgraded systems.

• For more information, see Status Threshold Tab and Site Configuration Tab.

• The ThingView Widget is now included with DPM and is available for use in custom extensions.

• For more information, see ThingView Widget.

• Precision (the maximum number of digits) and scale (the number of digits after the decimal point) for Number properties can now be specified in the database information for custom properties. For more information, see Adding Custom Properties to Data Model Entities and Adding Custom Entities to the Data Model.

• In ThingWorx Composer, the project for each building block has its Namespace value set to ptc.sca.<building_block_name>. For example, the Namespace on the PTC.Status project is ptc.sca.status, and the Namespace on the PTC.ModelManagementImpl project is ptc.sca.modelmanagementimpl.

• Only entities and characteristics (properties, services, configuration tables) with a public scope should be used in customizations. The scope is determined by the access modifier (if any) that is applied to the entity or characteristic. Starting with 9.5.0, new entities and characteristics that are added to the building blocks and require a non-public scope have the appropriate access modifiers applied. Any entities and characteristics which were present in the building blocks prior to 9.5.0, and which should have a non-public scope, have had the NON-PUBLIC designation added to their descriptions. These non-public entities and characteristics will have the appropriate access modifiers applied in a future release.

• When creating new customizations, ensure that none of the entities and characteristics you are using are marked as NON-PUBLIC.

• After upgrading to 9.5.0, review any existing customizations to discover if they use entities or characteristics that are marked as NON-PUBLIC. Update your customizations so that these entities or characteristics are not used, as they will become unavailable in a future release when the access modifiers are applied.

• For more information, see Understanding Namespaces, Access Modifiers, and Their Customization Impact.