View Single Post
Old
08-28-2012, 06:42 PM
  #148
seventieslord
Moderator
 
seventieslord's Avatar
 
Join Date: Mar 2006
Location: Regina, SK
Country: Canada
Posts: 24,101
vCash: 500
Quote:
Originally Posted by Canadiens1958 View Post
The basic point is that TOI or ETOI(estimated) has to reflect how the game was played/coached.

There are two situations O6/post 1967 expansion that I will use to illustrate.

O6 basically saw teams play with 4 defensemen with the 5th playing a swing role, rotating thru based on circumstances.

Rank the dmen 1,2,3,4, in terms of the team hierarchy. The coach would want his best two defensemen on the ice as much as possible. As a pairing they could not play 60 minutes but in the following pairing format:

#1 and #4, #2 and #3 it was possible to approach sixty minutes for the first two. This could produce situations where the first pairing #'s 1 and 4 would play app 31 minutes each, while the second pairing could play app 29 minutes each. This would not mean that the #4 was suddenly the #2 defenseman.

Post expansion produced interesting defensive pairings. Most of the defensmen available to the expansion teams were old, experienced whose time had to be managed. A Team with three old defencemen could break-in two young defensemen using the following rotation:

Old #'s 1,2,3, New #'s 4,5.

Basic rotation: 1/4,2/5/3/4,1/5,2/4,35, dropping down to 1/2, or 2/3 0r 1.3 at times. Point is that #'s 4 and 5 would see more TOI but that did not make them the #1 and #2.
those situations are actually very rare in the modern game. Look at Don Sweeney as an example. He played with Bourque and you'd think that his TOI would come out 2nd on the team even though he was a #3-4 defenseman. But no, his TOI was actually 3rd-4th just like it belonged in the team hierarchy. The fact is, the superior player will always get more special teams time, and extra ES shifts with other partners (last minute, for example). Dallas Smith, as another example, was not near Orr's ice time despite being his partner.

seventieslord is offline