Table of Contents
Module 3 - Build a Prototype or Pilot for the Network Structure
Section 1 - Build a Prototype or Pilot
Section Objectives
Upon completion of this section, you will be able to:
-
Determine how much of the network structure must be built to prove that
the network design meets the customer's needs.
-
List the tasks required to build a prototype or pilot that demonstrates
the functionality of the network design.
Time Required to Complete This Section
Approximately 1 hour
Completing This Section
Follow these steps to complete this section:
1. Study the reading assignment.
2. Click on any links that you see in the reading assignment and review
the information that appears.
3. Review any tables and job aids that appear in the reading assignment.
4. Review the case studies at the end of this section.
5. Complete the questions in each case study.
6. Review the answers provided by our internetworking experts.
Resources Required to Complete this Section
To complete this section, you will need:
-
Access to the World Wide Web and Cisco's Web site
-
A downloaded, printed copy of this section
-
Paper and pencil
Reading Assignment
Prototype versus Pilot
In order to prove your design works, you can either build a prototype as
described below or build a pilot, depending on your customer's requirements.
The decision will probably be made by your customer based on cost versus
need.
-
For larger configurations, a prototype is generally more feasible.
-
For smaller configurations a pilot might be more practical.
Steps to Build a Prototype
You can follow these steps to build a prototype network structure to prove
to a customer that your design works:
1. Review the work you did in Section
2 of Module 1, "Extract New Customer Requirements."
-
Synthesize the customer's requirements for performance, security, capacity,
and scalability into a short list of the customer's major goals.
-
List ideas for demonstrations you can conduct that will please the customer.
-
List any pitfalls or outcomes to avoid because they could cause a negative
reaction.
2. Determine how much of the network structure
must be built to prove that the design meets the
customer's major
goals.
-
Investigate services and tools you can use to simplify the task of purchasing,
installing, and configuring equipment for a prototype, for example, testing
services and network simulation tools.
3. Gain an understanding of what your competition
plans to propose.
-
If possible, work with your account manager to find out the exact design
and products competitors plan to propose.
-
If it is not possible to get details, make some assumptions based on the
types of products that will meet the customer's requirements.
4. Develop a test plan.
-
Draw a topology map of the test environment.
-
Include in the map major configuration parameters.
-
List simulation tools, Cisco hardware and software, and non-Cisco hardware
and software you will need for the prototype.
-
Include cables, modems, null modems, WAN connections, Internet access,
workstations, servers, design simulation tools, telephone-equipment simulators,
and so on.
-
List and plan for any other resources you will need.
-
Schedule time in a lab either at Cisco or the customer's site.
-
Help from coworkers or customer staff.
-
Develop a list of the tests and demonstrations you will run.
-
Explain how each test will prove that the design meets the customer's needs.
-
Explain how each test will showcase Cisco's strengths.
-
If possible, explain how each test will cause a competitor's product or
design to fail.
-
Write a script for each test or demonstration.
-
List the steps to prove the design.
-
Describe how to avoid pitfalls.
5. Purchase (if necessary) and configure equipment.
-
Network simulation tools.
-
Cisco hardware and software.
-
Non-Cisco hardware and software.
6. Practice demonstrations (before doing them
in front of the customer).
7. Conduct final tests and demonstrations.
Refer to Section 2 of Module 3, "Test the
Prototype,"
for more information.
Steps to Build a Pilot
For small businesses, a pilot might be more practical. A pilot is simply
a scaled-down prototype used to demonstrate basic functionality.
If applicable, here are some minium recommendations for a pilot of your
design.
1. Test the design.
-
Make sure you can meet the customer's stated response-time requirement.
For example, users should see their screens within one tenth of a second.
2. Investigate what competitors will be proposing.
3. Write a script for a demonstration of
the test results.
-
Make sure the tests will prove that the design meets the customer's
needs.
-
Make sure the tests will showcase Cisco's strengths.
-
If possible, make sure the tests will showcase competitors' weaknesses.
4. Practice the demonstration.
5. Schedule time with the customer and present
the demonstration.
The case studies in this section provide some practical examples of
how to design and build a pilot based on customer requirements.
Products and Services to Prove Concept
The following products and services can help you prove the concept to the
customer without installing and configuring the whole internetwork.
Industry Tests
Sometimes it is not necessary to build a test yourself. Instead, you can
take advantage of tests already done in the industry or by Cisco personnel.
For example, if you are proposing Catalyst 5000 switches and the competition
is proposing Cabletron MMAC-Plus switches, download the results of the
Strategic Networks Consulting, Inc. (SNCI) switch tests from the SNCI's
Web site.
Network General Corporation's Sniffer Network Analyzer
You can use the Sniffer network analyzer to generate traffic and hence
simulate new network designs. It is not a true network simulator, but if
you are knowledgeable about the amount of network traffic caused by new
applications you plan to install on a network, you can use the Sniffer
to gain an understanding of the effect new applications will have on your
network. For more detail, see Network
Associate's web pages.
Case Studies
In this section, you will build a prototype or recommend a pilot of the
network.
Read each case study and complete the questions that follow. Keep in
mind that there are potentially several correct answers to each question.
When you complete each question, you can refer to the solutions provided
by our internetworking experts. The case studies and solutions will help
prepare you for the Sylvan exam following the course.
In this section, you will review the following case studies:
1. CareTaker Publications, a publishing company
2. PH Network Services Corporation, a health care company
3. Pretty Paper Ltd., a European wall covering company
4. Jones, Jones, & Jones, an international law firm
Case Study:
CareTaker Publications
To review the CareTaker Publications case study, click
here.
Write a high-level "to-do" list (five to ten statements) of the tasks
required to create a pilot. The pilot must be realistic enough so that
you can use it to prove to the customer that your design works and meets
the requirements for performance.
Although testing the prototype should be on your list, you need not
include any details about the test. (The next section of this class focuses
on testing a prototype.)
Mr. Smith of CareTaker Publications has accepted your recommendations
but has made it clear that both the parent corporation’s and CareTaker’s
management have repeatedly expressed the requirement that everything will
work before the move takes place.
Describe how you will "pilot" the system prior to the move. You need
not worry about the mainframe and the SNA traffic; that will be the parent
corporation’s Network Operations personnel’s responsibility.
Now that you have completed the exercise, click here
to view the solutions provided by our internetworking design experts.
Case Study:
PH Network Services Corporation
To review the PH Network Services Corporation case study, click
here.
Although testing the prototype should be on your list, you need not
include any details regarding testing the prototype. (The next section
of this class focuses on testing a prototype.)
The general manager of PH wants to make sure that the system can be
installed in a manner that will allow all offices to "come on line" in
a phased-in approach. Describe your method of installing the system.
Now that you have completed the exercise, click here
to view the solutions provided by our internetworking design experts.
Case Study:
Pretty Paper Ltd.
To review the Pretty Paper case study, click
here.
Write a high-level "to-do" list (five to ten statements) of the tasks
required to create a pilot. The pilot must be realistic enough so that
you can use it to prove to the customer that your design works and meets
the requirements for performance.
Before spending all the effort and money needed to do this conversion,
Pretty Paper management would like assurance that this solution will work.
However, it does not have the time or money to do a prototype or proof-of-concept.
How would you propose to pilot the system so that most of the effort for
the pilot is moving toward the final system while demonstrating the functionality
of the final system?
Now that you have completed the exercise, click here
to view a solution provided by our internetwork design experts.
Case Study:
Jones, Jones, & Jones
To review the Jones, Jones, & Jones case study, click
here.
The firm has decided to implement one U.S. office and the Europe office
as a prototype network. Describe a project plan (at a high level) that
will pilot the system to prove the concept for a full implementation.
Now that you have completed the exercise, click here
to view the solutions provided by our internetworking design experts.
Click here to advance to Section 2.
Copyright Cisco Systems, Inc. -- Version 2.0 7/98