Documentation folders

[Dieselboy]

In my old network role back in UK we had a central location for literally everything including documentation. The was the intranet (sharepoint). I remember we had a folder structure, templated. So when a brand new customer came onboard either greenfield or brownfield, the intranet would immediately be updated (manually) with an empty folder structure.

I'm trying to remember this folder structure so I can do something similar at my place. I can't remember at all.

What's typically important for customers documentation? Here's what I can remember. Can anyone suggest anything further?


Customer name
1.       Projects
a.       In-progress
b.      Completed
2.       Documentation
a.       Server
b.      Network
3.       HR
4.       Something-else

[deanwebb]

High level design document/diagram
Low level design documents / diagrams
Work instructions
Standard Operating Procedures

Bill of Materials
Purchase orders
Statements of work

[Otanx]

Points of Contacts - technical (server and network), after hours contact procedures. Escalation procedures for when you can't get ahold of POC. This should be phone, email, mailing, and physical addresses.

-Otanx

[Dieselboy]

Thanks guys! Plenty that I forgot there! Site contacts ->> one of the most important ones!

[SimonV]

If you have a standardized hostname system, you can have one folder per device with a physical diagram, pictures, inventory details, etc.
For sites, the IP Plan, WAN documentation, license files, original design documents...

[deanwebb]

If you have a standardized hostname system, you can have one folder per device with a physical diagram, pictures, inventory details, etc.
For sites, the IP Plan, WAN documentation, license files, original design documents...

That reminds me... add the "Device Naming Convention" document to my list, above.