Hi Deborah,
This is a good question.
The naming conventions for Configuration Items (CI) varies between organizations. It will be really helpful if you could talk to the clients and other team members to decide a naming convention.
I see a couple of scenarios:
1. If your organization has already established naming conventions for CI's other than the documentation like software or hardware assets, it will be useful to utilize those conventions for naming your documents. For instance, if some software has a short name like SF and if you're maintaining the documentation for configuring this software, then you might consider naming it something like: D.C.SF.v where D means documentation, C means Configuration, SF means software and v is the version of the software. So, if someone is trying to access the documentation for configuring the software, they can easily identify it by searching for D.C.SF.v in Sharepoint.
2. If your organization doesn't have any established naming conventions for any CI's, it would be helpful to identify naming conventions that are unique and easily identifiable. Since documentation can be just one CI among a whole bunch of assets, it will be useful to follow conventions like:
<Superset>.<subset>.<type of documentation>.<CI>.<v>
Here <Superset> can be a D for Documentation, <subset> can be multiple versions of documents, <type of documentation> can be the type such as Installing(I)/configuring(C) etc., ,<CI> is the actual CI whose documentation we're addressing like say M for Microsoft, O for Office etc., and <v> is the version of the software like Office 98/professional/2000 etc.,
Hope this helps!
Regards,
Pradeep
Cell: (+91) 9535279950
E-mail: [email protected]