I wanted to get opinions on our newest mock draft... Here are my thoughts..  

1st rnd--E. Britton (OT)-- -- (They met him and worked him out privately, looks like a perfect fit at RT that could develop into a LT as well in a year)

2nd rnd----J. Inglesia--(WR Feature)  (Oklahoma guy-- you know they like this college)

3rd rnd--M. King-- (DE-- I am not too high on him, but it is what it is)

Late 3rd--R. Barden--(WRP) -- Possession receiver..

4th -- Z. Follet-- (OLB) They have actually met with this guy twice I believe..

5th--J. Davis-- (RB Feature) -- supposedly they are interested in this guy as well

6th--T. Nolan-- (FS) -- Competition and insurance for when one of the safeties we picked up get cut or hurt

7th--R. Brewster (OT)-- We are thin here, we need this guy to pan out for Depth-- JA still needs to pick up a veteran at tackly for depth

2nd 7th Round--T. Nighton (DT)-- need to strike lightening in a bottle-- Dusty in contract year, Idonje moving to DE.. good for competition and depth..

 
I think this hits every position of need.. only ones I am unsure is if we will actual pickup a second WR high enough.. and a RB in the fifth after signing K. Jones..
Still unsure whether they will go for a guard at any point..I feel with the signing of F. Omaye we are good at this position..  

Your Thoughts?  www.drafttek.com

I thought it would be interesting to put a couple notes on potential draft picks for the Chicago Bears that play in bowl games–

QB– Graham Harrel (Texas Tech)

– Constant pressure all game for about 90% of the time and I felt he handled it well.

– Questionable decision making ie- safety allowed and not kneeling in time for a field goal at the end of the half

Overall Feeling– still would be a good developmental QB in the 3-4 rounds or later, has the height and the arm to possibly make it.

QB–

John Paker Wilson– (Alabama)

– Was not able to will his team to a win in the biggest one of his career

– Height is listed at 6′1”– all Chicago fans remember the rollercoaster with Rex and do not want a repeat of this.

– At times made good deep throws that his recievers did get pass intereference calls on

Overall Feeling– I will be steering clear of this guy, may consider blocking from a potential pick for the Bears.

OG– Brandon Carter (Texas Tech)

– Thought he did a nice of blocking Peria Jerry the whole night– not once do I think he lost a battle against the all american Def. Tackle

– Extremely wide guard with a fiery attitude despite the losing effort of his team

Overall Feeling– would love to see this guy in a Bears uniform seems to be a warrior that would fit right in, still a junior so not sure if he would come out for the draft.

Peria Jerry- Defensive Tackle (Ole Miss)

– Seemed to get locked up at times against Brandon Carter

– Had success when switched off of Brandon Carter and made penetration

Overall Feeling– Seemed to be average to above average, though if he struggles with OG’s in college how will he translate on the next level

John Jerry– Offensive Guard (Ole Miss)

– Played right tackle all night and I am not sure if this was his natural position as he listed as an OG. If this is the case, I felt he handled himself well.

– If not, he did get beat off the ball on numerous occasions.

– At times did set the edge well for run plays.

Overall Feeling– Large lineman with not the greatest footwork– not a bad pick in the latter rounds. Still a Junior so not sure if he will come out. Should probably stay in college and perfect his technique.

Greg Hardy- DE (Ole Miss)

– Nonexistant all game, going against a non-draft pick OT

Overall Feeling– I would stay away from this guy, got swallowed on numerous plays last night– it doesn’t get easier in the NFL.

Micah Johson– Kentucky (ILB)

– played well at times seemed to be around the ball most of the game as you would like to see with your linebackers

– Fairly athletic was able to run down the field with WR’s– something you like to see if you run the cover 2 scheme as the bears do.

Overall Feeling– could be a nice pick in the middle rounds–seem to be pretty rangey at 250 lbs. Still a Junior, the telecaster did make a comment that he may test the waters of the NFL.

Van Eskridge East Carolina (FS)

– Don’t remember too much but seem to have good speed and tackling seemed to be average to above average.

Overall Feeling– did not see enough highlights on him to make a certain discussion will keep an eye on in the combine, still a junior.

Doug Palmer– East Carolina (OG)

– Seem to hold his own, wide lineman and I don’t remember him getting test to much.

Overall Feeling– not enough tape for me to make a certain decision. Still a Junior, will keep an eye on him if he did come out.

Sean Smith– Utah (CB)

– I though he had a solid game since he wasn’t brought very much at all. Usually a good sign your corner isn’t getting burned.

– Seemed Bama was going elsewhere to throw and they did have some success against the other corners.

Overall Feeling– Seems to be a decent prospect will need to watch more tape and will keep an eye on him at the combine should he come out (Jr).

Zane Beadles– Utah (OT)

– Seemed to hold his own as well, don’t remember him getting burned at all.

Overall Feeling– probably a decent prospect in the late rounds. Still a junior and I bet he would stay in a year longer to up his status.

Javier Arenas– Alabama (CB)

– Thought he had good speed and strength on the punt return.

– Don’t remember any plays against him in a negative fashion.

Overall Feeling– Felt he was quite athletic and would probably do OK on the next level– still a junior so not sure he will come out.

Rashod Johnson– Alabama (FS)

– Seemed to be around the ball most of the time, seem to be a sure tackler though he did have his moments during the game.

Overall Feeling– Need to do more research on him– he is a senior and will keep an eye on him in the combine.

Justin Woodal– Alabama (SS)

– Layed the wood down at times though I felt he was not quite the ball hawk that Rashad Johnson was.

– Seemed a little light for a strong safety.

Overall Feeling– Still a junior, will keep an eye on him if he comes out.

Antoine Caldwell– Alabama (OC)

– Seemed to hold his own especially with two of the other starting lineman out.

Overall Feeling– Draftscout.com has an arrow pointing down on him– not sure if this was from the game. Very well could be– again I thought he did ok but I think his footwork could be improved.

Glen Coffee– Alabama (RB)

– Was having a nice game till he got injured.

Overall Feeling– still a junior lets see if he comes out. Not the bruising back that I would be looking for as a compliment to Matt Forte.

Interesting NFL network excerpt on their thoughts on what the bears will be doing this year with the drafting of the quarterbacks... The analyst that came on there said that Angelo is targeting only 4 QB's Flacco, Henne, Brennan, and Paul Smith from Tulsa...

Does anyone have any info. to confirm this?

What do you think of these what if scenarios and priority changes?

QB- If Grossman signed-- move QB down to a P5 or P6-- not that we solved the problem but the likelihood goes down of us picking higher and especially if Griese is not moved.  

WR-- if we lose berrian-- keep the P2-- just cause JA is very unlikely to pick a WR in the first.  I would move the priority to M2 meaning we will pick twice in the higher rounds.  This would obviously change until a move is made in FA.

OLB- If Briggs is kept keep at P4 strictly as a value pick for depth.  If Briggs and ayanbadejo are gone still keep it at a P5 making sure we do get one pick in for depth as we do have starters still at the position.

OG- If Left Guard is bought-- then move the priority down to P5 strictly for depth here as well .  For now was going to move it up to a P2 as R. Brown is not coming back and they did talk to the top guard in the draft the other day.

Any input would be great as I decide to make these changes.

Here's detail on how the code works for the Drafttek.com site:

Team Needs
Code Descriptions
1 (or P1) - This is the absolutely highest priority team positional need.  If a player position (PP) is assigned a P1 code, the program will reach to fill the need.  For example if a team is selecting 15th, the program will search to the 25th player (as an example) to fill the P1 need.  A team can have only one P1 need.  However it is acceptable to have no P1 needs.
2 (or P2) -  PP's designated with P2 indicate that the that the team is in great need of starting calliber talent and will reach to fill the need.  The reach isn't quite as great as P1.  There can be multiple P2's identified per team.
Regarding Reach, the reach limit changes as the selection number increases.
3 (P3) - PP's (Player Positions) designated with P3 indicate that the team is in need of starting caliber talent, but will not reach for it.  Some teams use a "best available player" draft discipline, this fits the P3 code well.  
Two notes on P3:
a) even though we say "will not reach", there is a little bit of reach.  Selection #25 could reach to the #30 rated player to fill a P3 need.
b) If the program cycles through all the P1, P2, P3 and P4 needs without finding a player, the program will add more reach to the P3 PP's and seach again for a P3 player.
4 (P4) - PP's tagged with a P4 code are depth needs.  P4 is purely a value oriented selection, so there is no reach.
5 (P5) - The P5 code is used to identify positional needs that the team absolutely wants to fill (within reason), but does not want to invest a high draft pick.  P5 PP's start the simulation as an equivalent to P4 (depth needs), but in the 4th round all P5 PP's are promoted to P3.  Thus the chances of the PP's getting a player fill increase dramatically in the 4th round.
6(P6) - The P6 code is used to  identify late round fill needs - like a kicker, fullback, or backup QB.  
P6's have very low priority in rounds 1-5 and will only fill a player under the most unlucky of circumstances for the team.
In the 5th round, a conversion takes place and all P6 PP's convert to P4.
P7 and P8 do not exist.  They did once but were replicative and never seemed to fill.
9 (P9) - PP's tagged with a P9 code will not be filled under any circumstances.  The program simply bypasses them

M Codes Descriptions
Originally  the "M" degnation stood for "Multiple" indicating that a team was looking to find more than one player at a given Player Position (PP).  
Most player positions do not have the M designation, in these cases, if a PP is filled, the PP will be reset ro P9 so that there will be no further players selected at that position.
But if the PP has an M code next to it, the reset will be based upon the M code.
M2  - PP's (Player Positions) appended with M2  are for teams with multiple starter level needs at a certain position.  
Assume that the WR position is coded as a "1" with an M2 next to it.    After the first WR is selected, probably in the 1st, maybe 2nd round, the priority code is reset to P2 (internally) and the M code is reset to a blank.  Likely  a second WR will be selected within the next couple selections given the P2 designation.  Then after the second WR selection, the priority code will be setto P9 so that no more WRs are picked.
M3 - PP's appended with an M3 code will get the PP code reset to P3 following the first selection at the PP.  This also indicates a desire to add a second helping early on.
M4  - PPs appended with M4 will have the PP codes converted to P4 following the initial selection at the PP.  This implies that the team has a starter level need, then a 2nd depth need at some position.
M5  - PPs appended with M5 will have the PP codes converted to P5 following the initial selection at the PP.  This implies that the team has a starter level need, then a 2nd depth need to be filled in the mid-rounds.
M6  - PPs appended with M6 will have the PP codes converted to P6 following the initial selection at the PP.

I would like to give a big THANK YOU for all of those who gave me feedback on the needs for draft tek.com team matrix needs.  I have implemented quite a few of them-- like putting CB and TE at a P9-- no chances of bears drafting this position.  Moving SS to a higher priority and putting in multiple needs for the WR and OT position especially with the cuts happening today.  

I may make some more moves but I wanted to show what the current standing is for team needs and how it all works please read below:

As it sits right now I have the priorities like such:

Offense:

QB- P3
RB- P3
WR P2-- but with a M6-- Meaning that it will try to pick up a second value guy late
OT- P1-- but with a M6-- Meaning that it will try to pick up a second value guy late
OG- P3
TE- P9
OC- P9
FB- P9

Defense:

DT-P4
DE- P9
ILB- P9
OLB- P4
SS- P3
FS- P4
CB- P9
PK- P9

Here is detail on how the codes work:

Team Needs
Code Descriptions
1 (or P1) - This is the absolutely highest priority team positional need.  If a player position (PP) is assigned a P1 code, the program will reach to fill the need.  For example if a team is selecting 15th, the program will search to the 25th player (as an example) to fill the P1 need.  A team can have only one P1 need.  However it is acceptable to have no P1 needs.
2 (or P2) -  PP's designated with P2 indicate that the that the team is in great need of starting calliber talent and will reach to fill the need.  The reach isn't quite as great as P1.  There can be multiple P2's identified per team.
Regarding Reach, the reach limit changes as the selection number increases.
3 (P3) - PP's (Player Positions) designated with P3 indicate that the team is in need of starting caliber talent, but will not reach for it.  Some teams use a "best available player" draft discipline, this fits the P3 code well.  
Two notes on P3:
a) even though we say "will not reach", there is a little bit of reach.  Selection #25 could reach to the #30 rated player to fill a P3 need.
b) If the program cycles through all the P1, P2, P3 and P4 needs without finding a player, the program will add more reach to the P3 PP's and seach again for a P3 player.
4 (P4) - PP's tagged with a P4 code are depth needs.  P4 is purely a value oriented selection, so there is no reach.
5 (P5) - The P5 code is used to identify positional needs that the team absolutely wants to fill (within reason), but does not want to invest a high draft pick.  P5 PP's start the simulation as an equivalent to P4 (depth needs), but in the 4th round all P5 PP's are promoted to P3.  Thus the chances of the PP's getting a player fill increase dramatically in the 4th round.
6(P6) - The P6 code is used to  identify late round fill needs - like a kicker, fullback, or backup QB.  
P6's have very low priority in rounds 1-5 and will only fill a player under the most unlucky of circumstances for the team.
In the 5th round, a conversion takes place and all P6 PP's convert to P4.
P7 and P8 do not exist.  They did once but were replicative and never seemed to fill.
9 (P9) - PP's tagged with a P9 code will not be filled under any circumstances.  The program simply bypasses them

M Codes Descriptions
Originally  the "M" degnation stood for "Multiple" indicating that a team was looking to find more than one player at a given Player Position (PP).  
Most player positions do not have the M designation, in these cases, if a PP is filled, the PP will be reset ro P9 so that there will be no further players selected at that position.
But if the PP has an M code next to it, the reset will be based upon the M code.
M2  - PP's (Player Positions) appended with M2  are for teams with multiple starter level needs at a certain position.  
Assume that the WR position is coded as a "1" with an M2 next to it.    After the first WR is selected, probably in the 1st, maybe 2nd round, the priority code is reset to P2 (internally) and the M code is reset to a blank.  Likely  a second WR will be selected within the next couple selections given the P2 designation.  Then after the second WR selection, the priority code will be setto P9 so that no more WRs are picked.
M3 - PP's appended with an M3 code will get the PP code reset to P3 following the first selection at the PP.  This also indicates a desire to add a second helping early on.
M4  - PPs appended with M4 will have the PP codes converted to P4 following the initial selection at the PP.  This implies that the team has a starter level need, then a 2nd depth need at some position.
M5  - PPs appended with M5 will have the PP codes converted to P5 following the initial selection at the PP.  This implies that the team has a starter level need, then a 2nd depth need to be filled in the mid-rounds.
M6  - PPs appended with M6 will have the PP codes converted to P6 following the initial selection at the PP.

THE NEXT UPDATE IS 02/19/08-- Feel free to check it out, I really I think I have hit on the head so far.. I am waiting to see what happens on 03/02/08 when free agency opens to start making more moves!

This topic has been created to discuss team needs for the Draft Tek
computer simulated draft. I'm so-and-so and am a correspondent for that
Web Site.
I am responsible for determining the Priority Codes for each position
for the Bears. This is what I currently have for their offensive and
defensive positions:

  NFL Draft 2008 Simulation Team Needs
Offense:
QB- 3, RB-3, WR-2, OT-1, OG-3, TE-6, OC-6, FB-6

Defense:
DT-4, DE-9, ILB-9, OLB-4, SS-4, FS-3, CB-6, PK-9

The biggest changes I am considering making are switching the priorities on SS and FS-- where it is higher for us to get a SS over FS, it was just so evident all year how poor we were against the run..

also moving CB and TE to a 9 as I think we are solid in both of these areas..

possibly moving DT priority up and even ILB with Urlachers recent news..

Generally speaking-- the priority runs higher at 1 and lowest at 9-- but please read below to see how exactly it works.  Once you get the hang you will be addicted and making the correct moves as I am.. Hope to get some great insight from all you die hard Bears fans..

Those who are familiar with this site and their methodology/code system
are welcome to provide input on this thread. The codes determine how
the program prioritizes and selects. As with all computer simulationss,
it has its flaws, but the logic has been steadily improving since
inception and there are quite a few additional improvements planned.
The simulation is updated every few days, and I have no problem changing
codes if justified.

The codes and their meanings are here at the site at the very bottom of the page-- it is quite intricate but I think quite useful when trying to determine the right priority for each need..

Unfortunately I am unable to post this into this blog or else I would to save you a trip.  

http://www.drafttek.com/teamneeds2008.html