I'd guess that Corey's getting hit by his poor .735 OPS campaign in 2005. Toss in that he was 32 that season and the .788 OPS projection fits right in. I wouldn't knock the credibility all the way down to zero. Rather, I'd say "know thy projection system" and go from there. These things are tools and tools must be used properly. Keep in mind that by necessity, a computer must use a 'one size fits all' approach. If it didn't, it'd stop being objective. If I'm a GM, I'd want to use these systems to keep my feet on the ground, so to speak, when trying to do my own more subjective projections. Counting stats, such as home runs, will be affected by projected ABs. Prince's 2005 AB total amounted to less than that of a full-time player. While league effects should be accounted for, Prince only hit 23 homers in 2004 at Huntsville. In short, younger players are often projected to have a goofy number of ABs and counting stats are affected accordingly. Even the rate stats (averages) need to be handled with care. If you know a guy's likely to get 250 ABs and he's projected for 450, you'll have to give the numbers some breathing room. Slumps or hot streaks are much more likely to stick out. You might want to take a look at the Projection systems thread Ennder started a few days ago; it contains a couple of links that might be helpful. (I can't attest to how helpful they might be; I haven't read them yet. http://forum.brewerfan.net/images/smilies/wink.gif)