I started with filters, but really liked OG's better for a couple of reasons:
1. Each computer can only exist once. I was finding that we were having servers in multiple patching filters. I know that's more of a tracking issue, but its one easily resolved with OGs.
2. Heirarchy. It's extremely easy for me to click on Week 2 and see everything listed beneath it. While that can also be setup with filters, its completely manual. With OGs, as soon as I add another group with more servers under Week 2, it is instantly reflected in the Week 2 count.
That said, I was able to work out a query that shows me the two lowest groups that a computer belongs to, which works perfectly for the way we have it setup. Well, technically I wasn't, because a coworker and I were somewhat racing to see who could do it first. He beat me. Here is the query we used:
SELECT( nri.[Name] +'\'+(
SELECT
nri2.[Name]
FROM
FolderBaseFolder fbf2
INNER JOIN
vNonResourceItem nri2 ON fbf2.[ParentFolderGuid] = nri2.[Guid]
WHERE
fbf2.depth = 0
AND fbf.FolderGuid=fbf2.ParentFolderGuid
)) As BaseLevel,c.[Name]
FROM
FolderBaseFolder fbf
INNER JOIN
vNonResourceItem nri ON fbf.[ParentFolderGuid] = nri.[Guid]
INNER JOIN
ScopeMembership sm ON fbf.[FolderGuid] = sm.[ScopeCollectionGuid]
INNER JOIN
vComputer c ON sm.[ResourceGuid] = c.[Guid]
WHERE
nri.Name LIKE 'W1%'
AND c.[IsManaged] = 1
AND nri.Attributes = 512
AND fbf.FolderGuid <> '25134AE7-5259-4139-8686-F7E76F9EA1D3'
AND fbf.FolderGuid <> '328CD0C5-50CC-4F5C-B65B-F640E30ED7BB'
AND fbf.FolderGuid <> '523A368F-9487-4CBE-9281-11AC638D9E5A'
AND fbf.FolderGuid <> 'DC0A2FC0-8BCB-4BC0-8D7B-DBF4CF81D4EF'
AND fbf.depth = 1
AND (nri.[ClassGuid] IN (
SELECT
cbc.[ClassGuid]
FROM
ClassBaseClass cbc
WHERE
cbc.[BaseClassGuid] ='A1BBB63E-7194-4282-AB92-64E27FA2C18D'
) )
ORDER BY
BaseLevel, c.[Name]
And I have attached screenshots of how our org groups are setup (company info excluded to protect the innocent). Hopefully this helps someone.