Provisioning Bandwidth & Logical Circuits
with Fiber Manager
Jonathan Hager | Tri-State G&T
Skye Perry | SSP Innovations
Dennise Ramirez | SSP Innovations
3
Jonathan Hager | Tri-State G&T
 Fiber Project Coordinator
 Responsible for All New Capital Fiber Projects
 Been with Tri-State for 6 years
 Extensive experience in private telecom arena
(Level 3, Century Link)
Skye Perry | SSP Innovations
 Principal Consultant
 Esri & Schneider Electric Technical Architect
 Led the technical design @ Tri-State
 Certified Fiber Manager Implementer
Dennise Ramirez | SSP Innovations
 Principal Consultant
 Esri & Schneider Electric Technical Architect
 Leading the implementation @ Tri-State with a
team of 4 developers
 Significant experience extending SE products
Introductions
4
 Introduction
 Project Update
 The Current System & Telecom Assets
 Business Drivers
 Custom Requirements
 Demonstration
Agenda
5
 Great example of an extension to Fiber Manager
 Shows the value of customer collaboration
 An eye towards the future
 SONET/SDH
 Ethernet
Introduction
6
7
 On one 400 mile fiber route, approx. 4800 fiber records
 On one OC-48 segment, approx. 355,000 T1 circuit records
 Adding 100 to 200 miles of fiber
per year
 Adding 150+ circuit requests
per year
High Volume of Telecom Asset Records
8
 Originally Access Database with VBA Front End (~1996)
 Converted to Oracle 9i Forms in 2004
 Tracked logical infrastructure
of circuits including SONET
timeslots/channel designation
 Excel for fiber records
Current System - CSMGMT
9
 Create a GIS database and web-based interface to:
 Identify, review, analyze, and update key attributes of Tri-State’s telecom
network
 Include collocation buildings, equipment locations,
fiber optic routes, microwave radio systems,
MAS radio systems, USAT, and UHF radio systems
 Provide ability to track logical provisioning with
similar capabilities as current home grown system
to the DS0 level
Business Drivers
10
 Install new GIS telecom OTS software
 Include a new Circuit Mgmt Solution
 Add customized software interface for Circuit Mgmt
 Migrate Telecom database and fiber data
to new GIS telecom software
(with new customization)
 Tie telecom circuits to GIS software
 Focus on expanding fiber routes
Requirements
11
 Reviewed numerous software providers
 Interview / demo 4 leading OTS software vendors
 Selected ESRI/Schneider and Fiber Manager
Final Solution
12
Fiber Manager – It’s Physical
● Connection Manager allows you to connect fiber, microwave, etc. to a physical
port on a device on each end
● No internal connectivity between device ports within a device
● Circuit Manager allows you to create a named physical path from device to device
● Does a good job in tracking physical assets and connectivity
13
●Track master/header circuits that traverse through devices
●Custom Trace Linking Multiple Fiber Manager Physical Circuits
●Defines connectivity between internal device ports
●Establish bandwidth between end points (up to an OC-192)
Systems / Master Circuits
14
The Data Model
F_Circuit F_Circuit F_Circuit F_Circuit F_Circuit
F_System #1 A:C F_System #2 C:F
Custom
15
B
A C
16
B
A C
System A: OC-48
System B: E-3
System C: OC-12
1
2
17
B
A C
System A: OC-48
System B: E-3
System C: OC-12
Physical Circuits
1
2
18
Demonstration – Dennise Ramirez
●Creating Master Circuits
19
●Define a bandwidth hierarchy for each master circuit up to
an OC-192 (10 Gb/s)
●Allocate logical trunk circuits
(reserved bandwidth, ex. a full STS-1 or DS1)
●Provision logical tributary circuits
(committed bandwidth) down to a DS0
●Custom Two Point Trace Through Master Circuits
Bandwidth Hierarchy
20
● Allocate circuits within the master circuit hierarchy
● 24 DS0s = 1 DS1
● Tributary Circuit
● Ex Hierarchy:
● Consuming the 1st Vir. Tributary
● Within the 13th OC-1 (trunk)
● Within an OC-3 (trunk)
● Within an OC-12 (trunk)
● Within an OC-24 (trunk)
● Within an OC-48 (master)
● Defines the Timeslot of the circuit
Bandwidth Hierarchy
21
The Data Model
F_Circuit F_Circuit F_Circuit F_Circuit F_Circuit
F_System #1 A:C F_System #2 C:F
F_LogicalCircuit B:E
F_LogicalCircuit A:D
Custom
22
B
A C
System A: OC-48
System B: E-3
System C: OC-12
Physical Circuits
1
2
23
B
A C
System A: OC-48
System B: E-3
System C: OC-12
Trunk Circuit: DS-1
1
2
24
B
A C
System A: OC-48
DS0
System B: E-3
DS0
System C: OC-12
DS0
Tributary Circuit
1
2
25
Demonstration – Dennise Ramirez
●Creating a Trunk
●Creating a Tributary
26
What can we do with this level of detailed data?
●Recommend circuit provisioning based on available timeslots
●Track allocated bandwidth vs. capacity at all points on network
●Create a GIS heat map showing bottlenecks
●Drive capital planning for network expansion
●Poke the network at any point to see:
●Hierarchy of the master circuit(s)
●Which logical circuits are present
●The use of each logical circuit (down to the DS0)
●Result is a scalable system
27
Demonstration – Dennise Ramirez
●Illustrate allocated bandwidth vs. capacity
28
Questions?
SkyePerry
PrincipalConsultant
SSPInnovations
skye.perry@sspinnovations.com
JonathanHager
Fiber Project Coordinator
Tri-StateG&T
jhager@tristategt.org
Dennise Ramirez
PrincipalConsultant
SSPInnovations
dennise.ramirez@sspinnovations.com
register experience engage
https://infrastructurecommunity.schneider-electric.com
Surveys
• Session Feedback
• View the session in the Link
2015 app
• Click the Surveys button and
choose session feedback
• Conference Feedback
• Click the surveys link on the app
nav bar
• Then choose General Survey
Link2015 Tri-State Provisioning Bandwidth & Logical Circuits with Fiber Manager

Link2015 Tri-State Provisioning Bandwidth & Logical Circuits with Fiber Manager

  • 2.
    Provisioning Bandwidth &Logical Circuits with Fiber Manager Jonathan Hager | Tri-State G&T Skye Perry | SSP Innovations Dennise Ramirez | SSP Innovations
  • 3.
    3 Jonathan Hager |Tri-State G&T  Fiber Project Coordinator  Responsible for All New Capital Fiber Projects  Been with Tri-State for 6 years  Extensive experience in private telecom arena (Level 3, Century Link) Skye Perry | SSP Innovations  Principal Consultant  Esri & Schneider Electric Technical Architect  Led the technical design @ Tri-State  Certified Fiber Manager Implementer Dennise Ramirez | SSP Innovations  Principal Consultant  Esri & Schneider Electric Technical Architect  Leading the implementation @ Tri-State with a team of 4 developers  Significant experience extending SE products Introductions
  • 4.
    4  Introduction  ProjectUpdate  The Current System & Telecom Assets  Business Drivers  Custom Requirements  Demonstration Agenda
  • 5.
    5  Great exampleof an extension to Fiber Manager  Shows the value of customer collaboration  An eye towards the future  SONET/SDH  Ethernet Introduction
  • 6.
  • 7.
    7  On one400 mile fiber route, approx. 4800 fiber records  On one OC-48 segment, approx. 355,000 T1 circuit records  Adding 100 to 200 miles of fiber per year  Adding 150+ circuit requests per year High Volume of Telecom Asset Records
  • 8.
    8  Originally AccessDatabase with VBA Front End (~1996)  Converted to Oracle 9i Forms in 2004  Tracked logical infrastructure of circuits including SONET timeslots/channel designation  Excel for fiber records Current System - CSMGMT
  • 9.
    9  Create aGIS database and web-based interface to:  Identify, review, analyze, and update key attributes of Tri-State’s telecom network  Include collocation buildings, equipment locations, fiber optic routes, microwave radio systems, MAS radio systems, USAT, and UHF radio systems  Provide ability to track logical provisioning with similar capabilities as current home grown system to the DS0 level Business Drivers
  • 10.
    10  Install newGIS telecom OTS software  Include a new Circuit Mgmt Solution  Add customized software interface for Circuit Mgmt  Migrate Telecom database and fiber data to new GIS telecom software (with new customization)  Tie telecom circuits to GIS software  Focus on expanding fiber routes Requirements
  • 11.
    11  Reviewed numeroussoftware providers  Interview / demo 4 leading OTS software vendors  Selected ESRI/Schneider and Fiber Manager Final Solution
  • 12.
    12 Fiber Manager –It’s Physical ● Connection Manager allows you to connect fiber, microwave, etc. to a physical port on a device on each end ● No internal connectivity between device ports within a device ● Circuit Manager allows you to create a named physical path from device to device ● Does a good job in tracking physical assets and connectivity
  • 13.
    13 ●Track master/header circuitsthat traverse through devices ●Custom Trace Linking Multiple Fiber Manager Physical Circuits ●Defines connectivity between internal device ports ●Establish bandwidth between end points (up to an OC-192) Systems / Master Circuits
  • 14.
    14 The Data Model F_CircuitF_Circuit F_Circuit F_Circuit F_Circuit F_System #1 A:C F_System #2 C:F Custom
  • 15.
  • 16.
    16 B A C System A:OC-48 System B: E-3 System C: OC-12 1 2
  • 17.
    17 B A C System A:OC-48 System B: E-3 System C: OC-12 Physical Circuits 1 2
  • 18.
    18 Demonstration – DenniseRamirez ●Creating Master Circuits
  • 19.
    19 ●Define a bandwidthhierarchy for each master circuit up to an OC-192 (10 Gb/s) ●Allocate logical trunk circuits (reserved bandwidth, ex. a full STS-1 or DS1) ●Provision logical tributary circuits (committed bandwidth) down to a DS0 ●Custom Two Point Trace Through Master Circuits Bandwidth Hierarchy
  • 20.
    20 ● Allocate circuitswithin the master circuit hierarchy ● 24 DS0s = 1 DS1 ● Tributary Circuit ● Ex Hierarchy: ● Consuming the 1st Vir. Tributary ● Within the 13th OC-1 (trunk) ● Within an OC-3 (trunk) ● Within an OC-12 (trunk) ● Within an OC-24 (trunk) ● Within an OC-48 (master) ● Defines the Timeslot of the circuit Bandwidth Hierarchy
  • 21.
    21 The Data Model F_CircuitF_Circuit F_Circuit F_Circuit F_Circuit F_System #1 A:C F_System #2 C:F F_LogicalCircuit B:E F_LogicalCircuit A:D Custom
  • 22.
    22 B A C System A:OC-48 System B: E-3 System C: OC-12 Physical Circuits 1 2
  • 23.
    23 B A C System A:OC-48 System B: E-3 System C: OC-12 Trunk Circuit: DS-1 1 2
  • 24.
    24 B A C System A:OC-48 DS0 System B: E-3 DS0 System C: OC-12 DS0 Tributary Circuit 1 2
  • 25.
    25 Demonstration – DenniseRamirez ●Creating a Trunk ●Creating a Tributary
  • 26.
    26 What can wedo with this level of detailed data? ●Recommend circuit provisioning based on available timeslots ●Track allocated bandwidth vs. capacity at all points on network ●Create a GIS heat map showing bottlenecks ●Drive capital planning for network expansion ●Poke the network at any point to see: ●Hierarchy of the master circuit(s) ●Which logical circuits are present ●The use of each logical circuit (down to the DS0) ●Result is a scalable system
  • 27.
    27 Demonstration – DenniseRamirez ●Illustrate allocated bandwidth vs. capacity
  • 28.
  • 29.
  • 30.
    Surveys • Session Feedback •View the session in the Link 2015 app • Click the Surveys button and choose session feedback • Conference Feedback • Click the surveys link on the app nav bar • Then choose General Survey

Editor's Notes

  • #3 Last year we presented on an exciting Tri-State project to add a bandwidth and circuit provisioning extension to Fiber Manager. A year later, we are ready to demonstrate the tools and provide an update to the community! We will cover the new application which allows for provisioning a TDM network ranging from an OC-192 to a DS0. We will demo provisioning master trunks, logical tributaries, and our hierarchical circuit management tools along with a map showing reserved bandwidth vs. capacity!
  • #15 Skye… Talk about the custom data model. The F_Circuit is the product physical circuit. The other objects are custom objects that traverse into the logical provisioning world. This is best captured via an example. Take the case where we have 6 patch locations (or sites) labeled A thru F. In Fiber Manager we establish physical circuits between each of these patch locations – device to device (A to B, B to C, etc.). Next we create master circuits which can also be called systems. System #1 will be from A to C and System #2 will be from C to F. Each system shares the same bandwidth and the same designator/timeslot hierarchy. Now we want to create a logical circuit from B to E which crosses the two systems. (Reference the model.) This logical circuit traverses multiple systems and within each system it is assigned a specific timeslot. That reservation with the system may only use a subset of the physical circuits. In system #1 is only uses B to C and in System #2 it only uses C to D and D to E. It does NOT use A to B or E to F. To demonstrate the opposite direction we can show a second logical circuit. And now we can easily see that any given physical circuit such as B to C can be part of different timeslots which are being used by differing logical circuits. So in summary, one physcial circuit can host many different logical circuits AND one logical circuit can traverse many different physical circuits.
  • #22 Skye… Talk about the custom data model. The F_Circuit is the product physical circuit. The other objects are custom objects that traverse into the logical provisioning world. This is best captured via an example. Take the case where we have 6 patch locations (or sites) labeled A thru F. In Fiber Manager we establish physical circuits between each of these patch locations – device to device (A to B, B to C, etc.). Next we create master circuits which can also be called systems. System #1 will be from A to C and System #2 will be from C to F. Each system shares the same bandwidth and the same designator/timeslot hierarchy. Now we want to create a logical circuit from B to E which crosses the two systems. (Reference the model.) This logical circuit traverses multiple systems and within each system it is assigned a specific timeslot. That reservation with the system may only use a subset of the physical circuits. In system #1 is only uses B to C and in System #2 it only uses C to D and D to E. It does NOT use A to B or E to F. To demonstrate the opposite direction we can show a second logical circuit. And now we can easily see that any given physical circuit such as B to C can be part of different timeslots which are being used by differing logical circuits. So in summary, one physcial circuit can host many different logical circuits AND one logical circuit can traverse many different physical circuits.
  • #30 Join us and your colleagues in exchange, your online collaborative community for all things utilities and communications!