YOU Also need Standard Operating Procedure (SOP)
i am not sure about " as-built " diagrams , but they are used in my
comp..to refer to physical fiber links
On Tue, Sep 24, 2013 at 9:28 PM, olugbenga lasisi <logpoet_at_gmail.com> wrote:
> Hi Experts,
>
> This is completely OT, but please indulge me.
>
> I am currently helping out a large enterprise client with an overall
> infrastructure design and architecture work. As this client will be working
> with third parties to deliver is future IT services, I want to ensure that
> the names of the design and architecture documents are standardized across
> industries and technology vendors.
>
> Some of the document names being considered are:
>
> - Detailed design
> - High level design
> - Low level design
> - Site level design
>
> These documents will include Compute/Server designs, Storage (SAN/NAS)
> designs, and Network (LAN/WAN/WLAN/Firewall/Load Balancing) designs. Thus I
> want to ensure that the document names and tables of contents are not
> specific to a single technology domain but go across all. Any feedback on
> the above including alternatives or sample tables of contents would be
> helpful.
>
>
>
>
>
> Regards
> --
> Olugbenga Lasisi
> CCIE(R&S)# 27036
>
>
> Blogs and organic groups at http://www.ccie.net
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
Blogs and organic groups at http://www.ccie.net
Received on Tue Sep 24 2013 - 23:41:31 ART
This archive was generated by hypermail 2.2.0 : Tue Oct 01 2013 - 06:36:35 ART