Going to bed now...
Jun. 17th, 2006 11:45 pmWhich takes me to the second step of my SODM. sigh
A policy describes the legalize about various practices within my department. Standards describe a specific implementation of the policy so every standard needs to be (a) written and (b) linked back to its relevant parent policy document. Operating guidelines list considerations for a given UNIX platform in support of the standard. Procedures are precise, line-by-line instructions on how a task is conducted such that a trained chimp an intern could do it successfully.
The hierarchy looks something like this:
policy -> standard -> operating guideline -> procedures
Some policies were already 99% assembled but they needed links to policies. I've finished that small task tonight, as well as updated my spreadsheet tracking all of these little pieces. I can sleep now.
Tomorrow, I have to revise my tracking spreadsheet further, ensuring that I have a to-do list of standards which must yet be written to comply with my freshly minted policies. Whee. And on Monday, I get to start writing those missing standards.
I don't even want to think about the procedures and operating guidelines documentation yet.
no subject
Date: 2006-06-18 04:07 am (UTC)Makes for a boring as shit read if you ask me.
no subject
Date: 2006-06-18 11:59 am (UTC)I refer to these as "write-only" documents: no real human being will ever read these pieces again. The sole reason they exist and are designed in this fashion is to please auditors. The folks who actually do things with our servers require much shorter & concise documents, and fewer of them so that we can find the key information quickly. When a server is down, I don't care who authorized the document or why they wrote it: I just want enough info to get the server back up asap.
no subject
Date: 2006-06-18 02:19 pm (UTC)Exactly.