EcoNets. User’s Guide. 1. The basic design methodology 2. Description of input files (use the Textbook or Help Menu for additional details) 3. General Description of output files (use the Textbook or Help Menu for more details) 4. General Description of File Menu. EcoNets.
1. The basic design methodology
2. Description of input files (use the Textbook or Help Menu for additional details)
3. General Description of output files (use the Textbook or Help Menu for more details)
4. General Description of File Menu
A tool that models new network topologies.
It can also model any given topology.
A network design tool based on interactive
and iterative techniques.
A tool that provides cost and performance
A tool that provides a capability to store
and view detailed outputs and topologies.
A Mac/PC with 16 Mbytes of RAM for a
trial version (< 60 nodes) or 32 Mbytes (<
250 nodes) or 64 Mbytes (< 500 nodes).
System 6.05/7.0x(MAC) & Windows.
MS PPT or HTML Browser for slides.
The PC must be a 486DX/Pentium type
- Design Approach
Considering the facts that (1) network
topology determines total monthly costs
and performance, (2) there are almost
infinite topologies possible & (3) 70-80%
of the monthly costs are determined by
access lines and trunks, one must then
Vary design parameters to obtain a
subset of useful network topologies,
study their costs and performance
obtain the optimum topology.
- About Inputs
A maximum of 17 input files may
be required to design a network
Each input file is a sequential or a
“flat” text file
A negative number defines an end
-of-file (EOF) for each input file
The structure of data within each
input file is derived by
- Inputs & Outputs
:Required Input Files
1. VHD - Defines V&H coordinates of
each node and its BHR traffic value
2. LINK - Defines ALink types that connect
network nodes (e.g. CPEs)
3. MAP - Defines the map boundary
4. NLT - Defines each link type, C,
MF, applicable tariff number &
5. TARIFF-Defines each tariff listed in NLT
6. SDF - Defines < 60 design parameters
7. NAME - Defines < 6-character codes
for each network-node name
8. FTD - Defines detailed from-to traffic
flows for each nodal pair
9. LATA - Defines a LATA number for
each network node
10. FILES - Names all input files used
for each model
. Input Files(
11. CSABDS - Defines customer service area
bands for ACD networking
12. UTBL - Defines Virtual 800-Service tariff
13. WUTBL -WATS-Service tariff
14. MUTBL -MegaCom800-
15. RSTBL - Rate-Step-Table for
16. DTP - defines daily traffic profile
- defines #
and SW IDs
Input Files are defined by their 2-letter prefixes of
their assigned numbers. Any input file names
without the following 2-letter prefixes will be
ignored - a FATAL Error.
1. VH 2. LI 3.MA 4. NL 5. TA
6. SD 7. NA 8. FT 9. LA 10. FI
11. CS 12. UT 13. WU 14. MU 15. RS
16. DT 17. SW
- File Operations
Create a new input file
View/Update an input file
Save/Duplicate file under another name
Merge 2 VHD/Map/FTD files
Multiply VHD traffic values by fixed
File (text or graphics)
- The VHD File
The 1st element of each vector defines the
assigned node number for a CPE
The 2nd element defines
Coordinate for the node CPE
The 3rd element defines the Horizontal (H)-
Coordinate for the node CPE
The 4th element defines the node’s Time
. (TCA) of busy hour(BHR)
traffic intensity (
for voice, bits
per second for data). A FTD file must be
used to represent actual traffic flows.
- the LINK File
A LINK file defines voice/data AL types
• A LINK file is used only when Flk=1
It has a single column of numbers,
each defining the access link (AL) type
for each nodal CPE when Flk=1.
Range of AL types=1, 2, 3, 4, ..per NLT
If a LINK file is not read (i.e. Flk=0),
each CPE is assigned ALT type in SDF.
- Tariff file
1st element of a 16-element vector defines
the average total cost of 2 local channels
) of each leased AL or TK,
Next 5 elements define the upper values
of mileage bands (=< 5),
Next 5 elements define the associated
fixed monthly costs,
Next 5 elements define the associated per-
- SDF file structure
60 design parameters can be
defined to either create a network
topology or affect its performance
These 60 parameters can be
divided into 4 distinct sets:
1. Common 2. Voice-related
3. Data-related 4. ACD-related
TGF (traffic growth factor)
file read factors
(print or not to print factor for nodal#s)
ADM, DPM (actual/days/
NDEC, DECT (
Note: See TEXT for complete definitions
. Call Duration in
. for design
. of exceeding DREQ)
(cost of labor in $/Hr.)
(rate setting factor for discounts)
(ACD type to be modeled)
Note: See TEXT for complete definitions
- FTD file structure
Each vector has 3 elements:
1. From-Node (e.g. 1,2,3,....)
2. To-Node (e.g. 2, 3, 1,.......)
3. TCA of BHR traffic intensity (
The LATA input file consists of a single column with as many rows as there are CPE nodes in the network. Each element is a 3-digit Local Access & Transport Area (LATA) code. LATA file is also used for ACD/VPN network design where each element is a 2-digit geographical code (varying from 01 to 60) used by common carriers. See pages 265-267 of Text for a table relating these codes to CSABDS (varying from 1 to 6). An example for a 5-node network is as follows:
CSABDS file structure
The CSABDS has 60 vectors, each
with 62 elements. Each vector
represents a region. Each element
represents the customer service
band# for a given pair of source &
destination regions. See Chapter 8
of Textbook “Network Design Using
” for further study.
Hourly Usage Cost($) Vs.CSABD
2 12 11 9
4 14 13 11
5 15 14 12
6 16 15 13
-1. Note:CSABD may = mileage band value
RSTBL file structure
A RSTBL consists of 60 vectors, each
consisting of 6 elements.
There is one vector for each calling
Each of the six elements represents a
rate step, one for each CSABD.
See Chapter 8 of Text for more help.
1. VoiceNets, ACDNets, and DataNets have unique output file structures
2. Textbook is the best source of good examples of output files for all networks
3. The Help Menu is a also a good source of hints for reading output file data
4. Output files for VoiceNets describe details of each AL bundle (star topology)
5. Output files for ACDNet describe details of each virtual AL bundle (star topology) and agent force required for each hour for which calls are answered.
6. Output files for StarDataNets describe each AL Bundle for a Star Topology
7. Output files for MDNets, DLNets & MSTNets describe details of each netlink (e.g. sites sharing a netlink plus delays)
8. Output files also list response times.
9. Output files are saved under following names automatically: ALFSDi, ALFMDi, ALFDLi, ALFMST, ALFVN, ACDF and TKF where “i” represents the ith level of AL bundle and TKF represents an output file for a fully connected mesh backbone trunking network. To prevent overwrites, one must open it and use “Save as..”.
Understanding of input and output files
is only one aspect of the network design
and the task of
finding optimum locations
locations are also useful for under-
standing the network design process.
-r’s InterUseface (GUI)
for making the network design process a
one. One such interface
popularly known as the graphics user
interface (GUI) is now available for all
. Such a GUI employs
windows, menus, dialog buttons and edit
fields to enable the user to handle all file and
networking operations in an effortless
A user friendly interface is an utmost necessity
(2) input files-contents/structures,
(3) output files -how to read them,
(4) networking tasks and results.
(5) analysis tasks. This menu can
help reduce references to textbook.
A GUI for
4. HELP MENU: It enables the user to
interpret useful data related to:
1. Study SDF design parameters and divide them into 2 groups: dynamic (those affecting performance and static (those that influence presentation of results).
2. Attempt some network topologies for a given VHD17 input file ( only voice & data)
3. Study output files, ALFSD1, ALFMD1, TKF with help of Textbook and print them.
4. For each network modeled, study the DBF and print it. Study it for the listing of all important design parameters. Note: A structured DBF is automatically created for each network modeled.
5. Study the TKF for a 2-SW network model with the help of Chapt. 2, Eq. 2.28