Customization
The Customization KPI provides an assessment of the readiness of your Windchill environment based on the extent of customization done on the environment. The readiness score is calculated using the number of issues identified for Windchill+ Guidelines, Security, Portability, Upgrade Status, and OOTB Modified Files.
The summary of the customization score is provided to help you understand the high level efforts required to mitigate the impact.
For Windchill+ Guidelines, see Windchill+ Help Center.
Each customized file is assessed for the impact categories mentioned below and issues are identified from the artifacts. The impact status is defined for each category. Each category lists the issue types suffixed with number of occurrences for that particular issue type.
The impact categories are as below:
• Allowed in SaaS
• Upgrade Status
• OOTB Files Modified
The Overall Status is calculated based on the impact of each category.
Allowed in SaaS
The Allowed in Saas category consists of three impacts:
• Windchill+ Guidelines Issues — Issues that are caused due to non-compliance with Windchill+ guidelines. The types of issues under this category are as below:
◦ Use of unauthorized third-party libraries
◦ Unauthorized hard modelling (use of not allowed annotations)
◦ Use of unauthorized Windchill class implementation
◦ Use of main method
◦ Use of unauthorized Java API
◦ Use of unauthorized JSP tags or Angular JS
• Security Issues — Issues where unsecure code is identified.
• Portability Issues — Issues caused due to:
◦ Use of internal classes and methods
◦ Use of non-extendable Windchill class
◦ Use of deprecated classes and methods
◦ Use of deprecated API
The status definition for Allowed in Saas is:
• Excellent if there are no issues
• Moderate if there are issues from Windchill+ guidelines or portability
• Critical if there is at least one security issue
Upgrade Status
If the customized file causes an impact to the execution of the Upgrade Manager, it is displayed under the Upgrade Status category. Only files that cause database schema changes are included in this category.
The types of issues under Upgrade Status are as below:
• Index deleted
• New index added
• Column data type changed
• Primary key deleted
• Column resized
• Index modified
• New column(s) added
• New tables added
The status definition for Upgrade Status is:
• Excellent if there are no issues.
• Moderate if there are column resize, custom index, and constraint changes as per the Windchill+ Guidelines.
• Critical if there are new tables created or OOTB tables modified for the changes which are not allowed or key modified.
OOTB Files Modified
The type of issue under Upgrade Status is — OOTB Binary Files Modified
The status definition for OOTB files modified is:
• Excellent if there are no issues.
• Critical if there is at least one OOTB file modified which is not in the allowed list.
Artifacts Status
Artifacts Status pie chart displays the distribution of total number of artefacts/files modified in your environment based on the issues identified in the artifacts. Artifacts statuses are — Windchill+ Ready, Not Windchill+ Ready, or Mitigation Effort Required.
The artifacts with issues that are not allowed in Windchill+ that are marked as Not Windchill+ Ready.
The artifacts with issues that can be mitigated like use of internal classes and methods, use of deprecated classes and methods are marked as Mitigation Effort Required.
The artifacts with no issues identified are marked as Windchill+ Ready.
 |
There is a possibility that the same file may have multiple impacts. For example, a file may not be allowed in Windchill + as per the Windchill+ guidelines, and may use a deprecated API (portability impact), and the code may be unsecured (security impact). In this case, this file is listed under all the impact categories.
|
For additional information about the details of each customized file, see the Customization Analysis page. To navigate to the Customization Analysis page, click either the Customization Analysis Dashboard link at the bottom right corner of the Customization Analysis page, or the Customization Analysis gadget on the main dashboard.
Calculation of Customization Score
The calculation of customization score is explained here with an example.
As per the definition, the Red score (not ready for SaaS) value is 1 to 4.
So the Red Range is 4 — 1 = 3
Suppose you have 100 OOTB files and total 200 binary files.
The per parameter weightage is calculated as Red Range divided by Total number of binary files.
So in this example, the per parameter weightage is 3/200 = 0.015
The customization score is calculated as Per parameter weightage * No of OOTB files.
So in this example, the customization score is 0.015 * 100 = 1.5
|
|
When OOTB files or Red category parameters are present, the Green and Yellow score are not calculated.
|