A "strength of schedule" measurement that includes games not yet played necessarily must be based upon some ordinal ranking. Simply averaging opponents' power ranking is not very useful, because the list of opponents' ranks does not typically have a normal distribution. It's also true that the difference between two teams is not linearly rated to the difference in ranks - there's usually a greater difference between say, rank 1 and rank 10 than between rank 51 and rank 60.
The SOS measurement used here takes those factors into account by relating the median opponent's strength to the median of the field weighted by how "top-heavy" or "bottom-heavy" the schedule is. There are two parts to the straightforward calculation:
Opp Rank | Rank - Median |
---|---|
25 | -35 |
83 | 23 |
110 | 50 |
120 | 60 |
57 | -3 |
37 | -23 |
5 | -55 |
73 | 13 |
94 | 34 |
7 | -53 |
39 | -21 |
-0.9 + 57 = 56.1 |
An example using pre-season composite computer rankings as the teams' strength rating is here.
Note that unlike a simple average, this measurement can fall outside of the range of the ordinal rankings used as input. A very top-heavy schedule (North Carolina has 10 of 11 opponents from the top half of the field) can be negative, and ten teams here have such a bottom-heavy schedule that the measurement falls "below" the worst rank in the field (119th).
The same formula can be applied in any case where an average doesn't properly characterize an aggregate of ordinal ranks. For example, it could be used as an alternative to Jeff Sagarin's "central mean" to aggregate rankings of teams by conference affiliation.