You have chosen to sponsor your bid up to a maximum amount of .
I have a RFP for network design Plan ( about 6 pages ). I need to write Analyzing Business Goals and Constraints( about one page ) & Characterizing the Existing Internetwork( about two pages) for this RFP.
Analyzing Business Goals and Constraints
How to write it :
Chapter 14: Documenting Your Network Design
￼￼￼￼￼￼￼￼￼￼￼￼￼￼￼￼￼￼￼￼￼￼￼￼￼￼￼￼￼￼￼￼￼￼￼￼￼￼￼￼from the book: Top-Down Network Design
----- Business Goals and Constraints - information how to write it from -------
Business goals explain the role the network design will play in helping an organization provide better products and services to its customers. Executives who read the design document will be more likely to accept the network design if they recognize from the Business Goals section that the network designer understands the organization’s busi- ness mission.
Many network designers have a hard time writing the Business Goals section because they are more interested in technical goals. However, it is critical that you focus your net- work design document on the ability of your design to help a customer solve real-world business problems.
As discussed in Chapter 1, most businesses embark on a network design project to help them increase revenue, reduce operational costs and inefficiencies, and improve corporate communications. Other typical goals include building partnerships with other companies and expanding into worldwide markets. At this point in the network design process, you should have a comprehensive understanding of your customer’s business goals and be able to list them in the design document in priority order.
Characterizing the Existing Internetwork - information how to write it from -------
This section briefly describes the structure and performance of the existing network. It should include a high-level network map that identifies the location of major internet- working devices, data processing and storage systems, and network segments. The high- level map should document the names and addresses of major devices and segments and indicate the types and lengths of principal network segments. For large internetworks, two or three high-level maps might be necessary. Detailed maps, however, should be placed in the Appendix rather than in this section.
The network maps should include logical and physical components (for example, the location and reach of any virtual private networks [VPN], virtual LANs [VLAN], firewall segments, server clusters, and so on). The maps should also characterize the logical topol- ogy of the internetwork and the networks that make up the internetwork. Network draw- ings, or text associated with drawings, should indicate whether networks are hierarchical or flat, structured or unstructured, layered or not, and so on. They should also indicate network geometry (for example, star, ring, bus, hub and spoke, or mesh). The documenta- tion of the current state of the network also briefly describes any strategies or standards your customer uses for network addressing and device naming. If the customer uses address-summarization techniques, for example, this should be indicated in the design document.
A portion of the Current State of the Network section of the network design document should be dedicated to an analysis of the health and performance of the present network. See Chapter 3, “Characterizing the Existing Internetwork,” for more information on the documentation you should gather about the existing network.
Detailed health and performance reports can be placed in the Appendix of the design document to avoid overwhelming the reader with too much information at this stage. It is important that the reader be able to quickly reach the Logical Design and Physical Design sections of the document, because those sections contain the essence of your design proposal.