My Network Admin Data Tips

Network Proposal Executive Summary



Important notes about the Executive Summary:
• The Executive Summary is presented first because it provides the reader with an overview of the complete proposal. The proposal will be read by people with different roles and requirements. These may include managers; network engineers and technicians; marketing and sales consultants; and finance and accounting personnel. By reviewing the Executive Summary first, readers can then decide whether to read through the complete document or read only those sections that apply to their role.
• Although presented first, the Executive Summary cannot be written until the rest of the proposal document has been compiled. This section is therefore the final section to be written.

An executive summary is a report, proposal, or portfolio, etc in miniature (usually one page or shorter). That is, the executive summary contains enough information for the readers to become acquainted with the full document without reading it. Usually, it contains a statement of the problem, some background information, a description of any alternatives, and the major conclusions. Someone reading an executive summary should get a good idea of main points of the document without becoming bogged down with details.
 An executive summary differs from an abstract in that an abstract is usually only about six to eight lines long. Its purpose is to inform the reader of the points to be covered in the report without any attempt to tell what is said about them. Covering no more than a page in length, the executive summary is longer and is a highly condensed version of the most important information the full document contains. Both the executive summary and the abstract are independent elements rather than a part of the body of the document. Both are placed at the beginning of the document.

 With the possible exception of the conclusion and recommendation, the executive summary is the most important part of a report. As such, it should be the best-written and most polished piece of the document. This is because many readers may only look at the executive summary when deciding whether or not to read the entire document. In some companies, the executive summaries are distributed so that employees are informed as to what information is available, and interested readers may request the entire document. In short, you may expect that an executive summary will be read more frequently and by more people than will your entire document.

When writing your executive summary, ask yourself if those who read the summary will be those who will read the entire report. If you are dealing with two different groups of people, you will have to decide how much technical detail to include in the summary. If it is likely that some who read only the executive summary will not have the technical background of the writer or final reader, keep the technical information and vocabulary to a minimum. You might have three types of readers: those who want a full picture but won't check the details (they might read the executive summary, some of the body, the conclusions, and the recommendations), those who read everything (they read the appendices, all the data, the calculations, etc.), and those who are in executive positions, wish to be kept informed on what is going on in the company, and will say "yes" or "no" to a project (they will read the executive summary, the conclusions, and the recommendations). Your executive summary must address all three types of readers.

Since the executive summary is a condensation, when creating it, you omit any preliminaries, details, and illustrative examples. You do include the main ideas, the facts, the necessary background to understand the problem, the alternatives, and the major conclusions. Brevity and conciseness are the keys to a well-written summary. Do not take a few sentences from key sections of the document and string them together. Rather, go over the entire document and make notes of the elements you consider important. From your notes, create a rough draft of the summary. Then, polish what you have written until it is smooth and seamless without unnecessary wordiness. Do not include any introductory or transitional material. Finally, ensure that your executive summary is accurate and representative of your full document. It should not be misleading, but it should give readers the same impression as if they had read the entire report. 


Read More Add your Comment 0 comments


Layout of the Network Architecture Proposal



The proposal layout should be highly readable and aid the reader in locating information. Graphics enhance the readability of a proposal and convey information as well. Text should be legible, typically a serif typeface such as Times Roman, at 10-point to 12-point type. Page margins should be at least 0.5 inches, and page numbers should be included at the top or bottom of each page.



Section
Description
Executive Summary
Discusses the project goals and project scope at a high level. This section demonstrates that the network vendor understands the extent of the project and the role of the network in meeting the business goals. The goal of the summary is to convince the decision-makers of the business benefits of the design. This section is typically one to two pages long.
Network Requirements
Reviews the business goals and network requirements, including users and applications that need to be supported. This section often lists the business goals, in order of priority, with critical goals marked. This section includes the topologies; protocols, hardware, software, and training that are required to meet the business goals.
Current Network Environment
Documents the state of the existing network. This section includes physical and logical diagrams and the IP addressing scheme. The section summarizes the results of the network characterization, including strengths and weaknesses of the existing network. It also documents the user community and applications currently in use, based on the network characterization.
Proposed Physical Design
Describes the physical layout of the proposed design. This section documents trade-offs made to accommodate business goals and technical requirements. The section describes the features and recommended uses for the technologies and devices proposed for the new network design. This section documents the new WAN service and new network equipment. The section also includes proposed network diagrams.
Proposed Logical Design
Describes the logical topology of the proposed network. This section documents any proposed addressing and naming conventions. It describes the routing and switching protocols recommended for the planned network. This section includes recommended security mechanisms and products that support the security policy of the business. The section may include information on recommended network management procedures and applications.
Implementation Plan
Provides a detailed list of the tasks that must be performed to install and implement the new network. This section includes tasks, steps, time required, and proposed schedules.
Cost Proposal
Provides cost proposal for equipment, software, installation, and ongoing support.


Read More Add your Comment 0 comments


Guideline in Network Administration



Cisco Lifecycle Services
Cisco Lifecycle Services is designed to support evolving networks. Cisco Lifecycle Services is a six-phase approach to deploying and operating Cisco technologies.

The six phases of the Cisco Lifecycle Services are:
• The Preparation Phase
• The Plan Phase
• The Design Phase
• The Implement Phase
• The Operate Phase -maintenance
• The Optimize Phase -maintenance


  • In the Prepare phase, the business goals of the project are identified and a business case is created to justify the installation of the network upgrade.
  • During the Plan phase, the network designer performs a comprehensive site and operations assessment of the current network. A project plan is created that includes the tasks, time-lines, risks, responsibilities and the resources required to complete the network design project.
  • In the Design Phase, the designer creates a flexible design that can integrate new technologies into the current operations and existing network infrastructure.
  • During the Implement phase, the network is built according to the approved designs and specifications and tested to ensure it meets the business goals and requirements.
  • The Operate and Optimize phases of the network lifecycle are ongoing and represent the day-to-day operations of the network. Optimizing a network is a continuous process that identifies and resolves potential weaknesses before they become problems for network operations.

The proposal typically contains the following sections:

A. Executive Summary
B. Network Requirements (planning stage)
C. Current Network Environment (planning stage)
D. Proposed Physical Design
E. Proposed Logical Design
F. Implementation Plan
G. Cost Estimate


Read More Add your Comment 0 comments


 

© 2011 My Network Admin Data Tips All Rights Reserved