1. GM Check-Mate Development Framework Status and Future
Shirish More
Solutions Architect – Global General Motors Account
Siemens PLM Software 1

2. ABSTRACT
This presentation will address the challenge of developing, integrating and deploying Check-Mate checkers/profiles into GM Math Data Validation processes.

3. General Motors Validation Facts
Check-Mate as globally agreed upon CAD validation tool
Successfully implemented Check-Mate at all GM Global Sites
Enforced 53 Check-Mate Checkers as part of GM workflow
Check-Mate used as CAD Data Assessment Tool
More than 200,000 NX parts assessed weekly using check-mate batch mode
Significant improvement in Math data quality

4. GM Quick Validation Roadmap To Achieve CAD Data Quality
Phase1
Phase2
Phase3
Phase4
Phase5
Design
Function
Checks (RDDV)
Value (Time\Cost\Quality)
Fabrication
Process
Checks
Modeling
Best
Practice
Checks
Geometry
Integrity
Checks
File Organization
Checks
CURRENT STATE
FUTURE STATE
Scope

5. Simple GM Validation Workflow
Designer
Design in NX
Create Item Revision in Teamcenter
Execute Check-Mate in NX
Release in Tc

6. Validation Technology
GMNA – DCS File Checker
(Mostly File Organization Checks)
GME – SQS/DQS
(Mostly Structure / Data Checks)
Retiring different GM custom validation tools at different regional sites
Accepted Solution
Check-Mate as globally agreed upon CAD validation tool
Challenge
Advantages
Validation framework that is supported, enhanced and maintained by Siemens
Better error reporting
(tree structure, failed objects, external log files)
Performs Validation on Assemblies/Folders
(Native and Teamcenter)
Check-Mate execution from command line

7. Business Processes Checks Vs. Workflow
Different checks required at different sites for releasing data
Accepted Solution
“Global Quality Seal” Profile consisting 53 globally agreed upon checkers (File Organization and Data Structure Checkers to begin with )
Challenge
Advantages
CAD Data validated to globally agreed upon GM data creation standards
Smooth data sharing between global sites
Global regions now speak same validation
language

8. Integration with Teamcenter
Enforcement
Saving Checking Results
(Teamcenter/NX ?)
Teamcenter Groups and Checking Results?
Importing Native CAD Data and Validation Results?
Challenge
Accepted Solution and Advantages
Check-Mate results are saved in NX part file and in Teamcenter
Different groups can execute different Profiles and still can be enforced using Tc XML rule file
With Tc validation can be performed from Tc product structure editor
NX 5 now will create validation objects when native data is imported to Tc

9. Tc Validation Results Summary Example
Status
Result
NX Dataset
Checker/Profile Class Name

10. Generic Validation Rule Set Content Example
Tc Group
Owning Group of the Item Revision
“All, All-Except, None, None-Except” logic
Dataset Type
Dataset type to Validate
Profiles to validate/acceptable results
Profile Name: Passed/Run

11. Teamcenter Rule File Items Example
Baseline Rule File Item:
AKP62495
All WIP Item Revisions validated to same checks
Hard Release Rule File Item:
AKP86750
WIP Item Revisions can be validated to different checks based upon Owning Group of Item Revision and Dataset Type
Replicated to the following sites:
GMTG_Production, GMPT_Production, GMSA, ISUZU_Production, GMM_Production, GM_Suzuki, Holden_Prod, JCI_Warren, IMC , Torrance, GMB-S.CAETANO, GMCL-REC_Production, FCA_HF_Production, SaabTDC1, GMPTE, GMDAT, EDAG_GME, Manuf_Production, GM-Strasbourg, GMIDEL_Production (Master in SCG001)

12. Check-Mate Performance
Checking Time + Result Display Time
Check-Mate checking time is on higher side as compared to our legacy NX/Open validation tools
Challenge
Accepted Solution (Functional and Core Architecture)
Set environment variables that limits display of failed objects in check-mate results window
UGCHECKMATE_MAX_DISPLAY_ENTITIES
UGCHECKMATE_MAX_LOG_ENTITIES
Skip “read-only/released” NX part from checking
Skip part files having check-mate flag PASS and Up-To-Date
Set environment variable that will not bring-up results window when checking is complete
UGII_CHECKMATE_AUTO_SHOW_RESULTS

13. GM Check-Mate Coding Framework - Current
NX 3.0.5
Enforced Profiles
Adhoc Profiles/Checkers
GM Check-Mate Profiles
Core and GM Specific Check-Mate Checkers
Core and GM Specific Check-Mate Routines
NX/Open + KF
NX Core

14. GM Check-Mate Coding Framework - Future
NX 5+
Enforced Profiles
Adhoc Profiles/Checkers
GM Check-Mate Profiles/Checkers
GM Specific Check-Mate Routines KF
API
.NET
API
C++
API
Open C
API
Common API
NX Core

15. GM Check-Mate Profile/Checker Hierarchy – Conceptual Plan
Group
Specific
Checking
NX Check-Mate Rule Set
NX Roles and Math Maturity
Top
Level GM
Check-Mate
Profile PT
IDENTIFIER
RULE
Interior
Exterior
Chassis
AVDC
HVAC
Styling 1 2 3 4 5 6 7

16. GM Validation Future Development Plans
Implement Check-Mate override capability in GM workflow
Enforce RDDV checks
Job Scheduler and Check-Mate batch-mode checking

17. GM Check-Mate
DEMO

18. Questions 18