For some time I looked at the 7 OSI layers and thought some things are missing. especially when you need to define a model for the CMDB.

Here is what I have been sorting for the past year.
Maybe people are willing to provide some comments.
I already had positive reactions
from Novell, IBM and a few BPM software compagnies

00 Physical (Passive Components: Facilities, Infrastructure, Material)
00 Physical (Active Components: Sensory, Assets, Personnel, Time)

01 Datalink layer (MAC and LLC Protocols)
02 Virtualisation (Operating Systems and Networks)
03 Networks (Logical addressing)
04 Transport (End to End connections and reliability)
05 Sessions (Inter host communication)
06 Presentation (Application Functionality and encryption)
07 Application

08 Users (Personnel)
09 Groups (Personnel Job functions)
10 Administration
11 Planning (Physical and Logical)
12 Security
13 Regulation
14 Management
15 Finance
16 Policy
17 Business

Why not go for 34 layers!

In my job, I use the phrase "It must be a layer 8 problem" at least once a day. This is response to "It must be the network"

Now I have a model where I can say "It must be a layer 14 problem" <grin!>

Thanks... I'll use it

Your Layer 8 sounds like a wetware problem. ( As in brain matter not some weird fetish )

I'm going to have to come up with a much more elaborate acrostic to memorize all that.

Here we might have a layer 8 problems wich is violating layer 16. Damn we should improve layer 15 to resolve some level 17 issues were having ..

Nah it was fun where we had only layer 8 problems , besides non technical people already have problems understanding this kind of jokes to add more stuff... at some point you can even say men my layer 17 15 is having problems? HUH???

heck of an acrostic you might have to put up with