I've been at Edwards a little over 3 months now. Lots going on - major initiatives to "raise the bar" in many areas, including CAD quality and becoming more model-based.
We're actively establishing / updating standards in various areas, and attempting to automate checking and reporting against those as much as possible. For this reason, I've been immersed in ModelCheck recently and have things configured pretty well. Over the years there have been many PTC/User presentations / discussions about ModelCheck and I've gone thru them all. I created some additional "cheat sheets" and a diagram - happy to provide to anyone interested.
This week, I took a close look at the ModelCheck Metrics tool and just had an extensive session w/tech support on it. Very disappointed that the metrics tool has not been kept up to date and essentially can no longer be used. It has to run using very old Java, Apache and Tomcat versions. Sad to see that it lagged so far behind. Whoever is not the PTC product manager for ModelCheck, I'd love to have a discussion w/you.
In any case, we have the metrics files being output by users to a common location. These can be "mined" fairly easily for some info by just opening in Excel and doing some manipulation using pivot tables. note: We also have the four MC parameters mapped to Windchill attributes and intend to use these in workflows to prevent release for production if any errors exist. Just takes a little code on a workflow conditional robot to accomplish.
Sorry for all the before the question... 
Question: Does anyone have anything in use that they are willing to share for monitoring use of / summarizing results of ModelCheck other that the (essentially obsolete) PTC metrics tool?
thanks in advance
///
Starting next week - I need to get to a similar point using SolidWorks Design Check.
All folks on this thread -
I have setup a fairly extensive MC configuration for my company, and went through the PAIN of poor documentation, poor PTC support, lots of trial and error, to get it working.
The MC Metrics is really a POS, but it does offer a few useful items. The AccessDB it uses/creates is actually pretty useful. What I do is export the data out to Excel and work with it there to create pivot tables, etc.
NOTE: Keep in mind that the AccessDB is a compilation of all MC runs by engineers. For instance, it a user has a model that has 1 error, and he runs MC 50 times, the AccessDB will count all 50 errors. The reverse is true if you have a clean model (lots of OK's in the AccessDB) What this means to me is that the data gathered needs to be filtered down to individual runs (by last date) to get data that means more than a trend. Something else to keep in mind is that there isn't a good way to tell which models actually got checked in, and if the errors/warning were fixed before check-in.
This is where Creo Distributed Batch comes into play - I have been playing with the tool for about a week now, and the best caveat of the tool is the ability to run MC on "checked-in" models! You can batch check against a workspace, or a context (could be brutal if many objects exist).
BTW - I COMPLETELY agree with Mike Lockwood that ALL data should be allowed to check-in, to keep the data secure. However, if using Gatekeeper, much easier said than done. Mike's way of controlling the quality through the Change process is an interesting one.
If anyone on this thread would like to have an open teleconference to discuss MC more, I'd love to see that.
Perhaps we can even get Rosemary on the call
