Release Notes > Digital Performance Management 1.2.0 Release Notes
Digital Performance Management 1.2.0 Release Notes
The following feature enhancements, known issues and limitations, and resolved support cases are part of the Digital Performance Management (DPM) 1.2.0 release. Also provided are: database schema changes, refactored services, and end-of-support information.
Feature Enhancements
The following enhancements have been made in the 1.2.0 release:
Deployment Enhancements
On a customer-owned system or cloud, DPM can be deployed using Solution Central or the Software Downloads page.
For more information on these scenarios, see Deploying DPM on a Customer-Owned System or Cloud.
Bottleneck Analysis
A new Bottleneck chart has been added to Performance Analysis, providing an easy way to identify your top production bottlenecks.
The bottleneck analysis tool automates the identification of operations that constrain a site’s ability to meet production demand within the planned schedule. By identifying the largest production bottlenecks in a site, DPM helps you to focus on the highest-value improvement opportunities and prioritize the operational improvement initiatives that will have the most impact on your manufacturing processes.
For more information, see Bottleneck and Configuring Bottleneck Analysis.
The new Scorecard tool provides a report of the performance of work centers across the enterprise based on standard predefined metrics. This tool lets you view and drill into any level of the equipment hierarchy from the entire enterprise down to the individual work center to view metrics information. For more information, see Scorecard.
Each of these predefined metric can be configured to specify status threshold and target values for your equipment. These values are used in the Scorecard to display operational and performance data for your work centers. For more information, see Metrics.
When configuring a metric, the Calculation tab helps in understanding the formula used to calculate each metric. For more information, see Calculation Tab.
Viewing Loss Insights with Time Loss Analytics
Time Loss Analytics derives insights and identifies scenarios related to higher amounts of time loss for an area. These insights can be accessed from DPM by using the View Loss Insights action in Performance Analysis. For more information, see Viewing Loss Insights.
The analytics settings are configured for each individual area, including which features to include when calculating insights, and the pipeline schedule for pushing data from DPM to the ThingWorx Analytics Server for analysis. For more information, see Time Loss Analytics.
For the initial release, this functionality is available for PTC Cloud hosted customers.
Post-release instructions have been added for customers with DPM on a customer-owned system or cloud to deploy the Time Loss Analytics functionality. For more information, see Deploying DPM on a Customer-Owned System or Cloud and Upgrading DPM on a Customer-Owned System or Cloud.
Production Dashboard Enhancements
The Production Dashboard user interface has been updated for improved display at the 1280x1024 minimum screen resolution. This update includes the main screen, the expanded event log, and the Add Loss Event, Edit Loss Event, Time Loss Accounting, Historical Scrap Event, and Split Automated Event windows.
For more information, see Production Dashboard.
Performance Analysis Enhancements
Information panes have been added to the bottom of waterfall and Pareto charts, providing additional details about the data that is displayed and selected in the chart. For more information see, Time Loss Waterfall Chart and Loss Reason Pareto Charts.
The View Event Log on waterfall, Pareto, and trend charts opens a read-only event log providing details about the events included in the selected blue bar. For more information, see Viewing the Event Log.
Improved navigation through the various Performance Analysis charts, using the Next Chart button and a navigation breadcrumb. For more information, see Navigating Between Charts.
Navigation Enhancements
The DPM navigation menu has been updated for ease of use.
For more information, see Navigating DPM.
Date and Time Format Enhancements
DPM now displays dates and times in international format.
For more information, see Date and Time Formats in DPM.
Multi-Site Support for Materials
Materials can now belong to one, many, or all sites within DPM, and material names must be unique across the enterprise. In previous releases, an individual material could belong to only one site, and material names had to be unique within each site. This meant that if a material was produced in more than one site, separate materials were needed in DPM for each site, potentially all with the same name.
Materials can now be assigned to multiple sites when the material is created or by later editing the material. For more information, see Materials.
Existing materials are migrated during upgrade to DPM 1.2, with the names of any duplicate materials updated to append their site name. This allows duplicate materials to be easily identified and consolidated by editing and disabling materials as needed. For more information, see the "Post-Upgrade Activities" section of the upgrade topic for your deployment scenario, under Upgrading DPM.
Database Enhancements
The database Thing now extends from the SQLThing Thing Template available in ThingWorx. This provides for better database usage, including use of the shared connection pool provided by the persistence provider.
For more information, see Implementation Model (Database Connection Building Block) in this help center and Storing Data with ThingWorx in the ThingWorx Help Center.
Localization of Database Values
Functionality has been added to support the localization of certain values that are stored in the database, such as job order statuses, units of measure, reason categories, and reason codes. This functionality is separate from the localization table support provided by ThingWorx. Such values that are delivered with the DPM solution are already localized. For more information, including the full list of the localized database strings, see Localization of Database Strings Using Database Tables.
Infrastructure support is present for customer-provided translations of reason code names and descriptions. Customers can work with PTC Implementation Services to supply translations for their own reason codes. For more information, see Providing Translations for Customer-Created Reason Code Names and Descriptions.
Building Block Enhancements
The following new building blocks have been added in DPM 1.2:
Custom Mashups
When creating or updating custom mashups, ensure that you are using secure expressions. For more information, see Using Secure Expressions in Custom Mashups.
Data Automation Enhancements
The PTC.OperationKPI.AutomationEventProcessor_TI timer is now enabled by default. For more information, see Setting Up Data Automation.
Database Schema Updates
For more information on updates to the database schema for the building blocks, see Database Schema Changes in this topic.
Known Issues and Limitations
The following known issues and limitations are present in the DPM 1.2.0 release:
Known Issue
Users should not directly modify the database.
Changes to the database schema must be performed through the supported services provided by the PTC.DBConnection.Database_TS Thing Shape and the PTC.DBConnection.Manager_TS Thing Shape. For more information, see Database Connection Building Block.
Changes to stored procedures and functions that are provided by PTC are not supported. Stored procedures and functions can be overridden on upgrade, so any changes would be lost.
After updating the ideal cycle time for a material, existing job orders for the material are not updated with the new ideal cycle time.
Workaround: If you want job orders that have not yet started production (in the Pending or Dispatched states) to use the updated ideal cycle time, cancel the existing job orders and create new ones. The new job orders will reflect the updated ideal cycle time for the material.
Job orders that have already completed or are in production (in the Running or Held states) correctly use the previous ideal cycle time.
Very small scrap values (less than 0.1) appear as a blank in the Edit Loss Event window. The values appear as expected in the Event Log.
This issue will be addressed in a future release.
The Equipment List intermittently does not display if Administration is selected from the navigation menu more than once in a row.
Workaround: To view the Equipment List, select another item from the menu, or another page within Administration, then select Administration or Equipment List again.
If a user is entering a value in the Enter Quantity field on the Time Loss Accounting window, and an automated event is received before that quantity is saved, the quantity is cleared.
This issue will be addressed in a future release.
When data automation is configured, if the ThingWorx server time is behind the time on the server where Kepware is installed, automated events coming from Kepware are ignored.
This issue will be addressed in a future release.
Some error messages in Administration are not fully externalized. Portions of these messages display in English even when the user interface is viewed in another language.
This issue will be addressed in a future release.
When you sort two or more columns available in Reason Trees, Job Orders, Materials, Metrics, Shifts and Calendars, and Scorecard, multi-level sorting behaves differently on different tables.
This issue will be addressed in a future release.
After upgrading to DPM 1.2, some customized administration mashups that are opened in Google Chrome and Microsoft Edge browsers are showing unnecessary scrollbars.
Workaround: To view scrollbar-free customized mashups in Google Chrome and Microsoft Edge browsers, update your customized mashups to align with the updated mashups that are provided by PTC.
Automated events can be logged against an incorrect job order when the Kepware clock and the ThingWorx server clock are not synchronized.
Workaround: Ensure that the system clocks (the "Date & time settings" on Windows OS) on the Kepware server and the ThingWorx server are synchronized within 5 seconds and that this synchronization is maintained over time.
Disabled reason codes are displayed in the Select Loss Reason pane of the Edit Loss Event window which can lead to erroneous entries. A loss event can be logged for a disabled reason code belonging to an incorrect reason category.
This issue will be addressed in a future release.
Scheduler, timer, or other pacemaker data processing is not occurring. For example, shift instances are not being created, or automated events are not being processed. A possible cause is the lock property being set to true on a related entity.
Workaround: Reset the lock property on the related entity to false.
The following table lists the entities with lock properties and their property names:
Any model (equipment)that implements or inherits PTC.TimeLoss.ModelLogic_TS
Any model (equipment) that implements or inherits PTC.OperationKPI.AutomationEventsModelLogic_TS
Any model (equipment) that implements or inherits PTC.MfgModel.AnalysisModelLogic_TS
When appending data to a data set for time loss analytics, the first production block in the appended data for a given work center does not include values for time losses from the previous production block as expected. Instead, the following columns are empty in the appended data for those production blocks:
This issue will be addressed in a future release.
When new work centers, materials, or shifts are added to an area, the existing time loss analytics data set for the area needs to be deleted and a new data set should be created. You can delete and recreate a data set from Area Settings > Pipeline Scheduling Tab > Create Manual Push > Delete and Recreate Data Set.
This issue will be addressed in a future release.
Resolved Support Cases
The following support cases are resolved in DPM 1.2.0:
Case Number
Issue has been addressed where the DPM timer became disabled when the host machine restarted.
Issue has been addressed where scrap counts and production counts received through data automation were not being processed correctly.
Issue has been addressed where ideal cycle times of less than 1 second were being recorded as 0.
Issue has been addressed where the actual cycle time and ideal cycle time shown on the Production Dashboard and Administration screens were limited to 1 decimal place instead of 4 decimal places.
Issue has been addressed where drill-down arrows were shown in reason trees for reason codes that did not have any enabled children.
Issue has been addressed where an error resulted when executing the RemoveUserFromRole service on the PTC.UserManagement.Manager Thing.
Issue has been addressed where an error was logged each time an automated event was inserted into the database.
Database Schema Changes
The following database schema changes have been made in DPM 1.2.0:
Data Shape
New Data Shape added.
New Data Shape added.
New Data Shape added.
New field added: name_token.
New fields added: abbreviation_token and description_token.
New fields added: displayname_token and description_token.
New fields added: name_token and description_token.
New field added: displayname_token.
New Data Shape added.
New Data Shape added.
New Data Shape added.
New Data Shape added.
New Data Shape added.
Field deprecated: siteUid.
New Data Shape added.
New Data Shape added.
New Data Shape added.
New Data Shape added.
New Data Shape added.
New Data Shape added.
New Data Shape added.
New Data Shape added.
A new back-end database table, AggreggatedJobOrder, has been added. This table does not have a Data Shape in ThingWorx.
Refactored Services
The following services have been moved from PTC.AdminConfiguration.Management_TS to PTC.Administration.Management_TS. Any customizations that use or reference these services need to be updated.
End-of-Support Information
For information on content that has been deprecated in DPM 1.2.0, see Deprecated Entities, Services, and Other Content.
Was this helpful?