I cameo revision gd version2

27
PROS/CAMEO International Design Document PTT ID: 52252.AA Revision Prepared By: Thomas Clay V806-4397 (703)886-4397 [email protected] VerizonBusiness, Inc. Confidential & Proprietary This documentation is extremely sensitive; please limit distribution. No part of this document may be photocopied, disclosed, or otherwise provided to third parties. 5/25/2022 1

Transcript of I cameo revision gd version2

Page 1: I cameo revision gd version2

PROS/CAMEOInternationalDesign Document

PTT ID: 52252.AA RevisionPrepared By:Thomas Clay V806-4397(703)886-4397 [email protected]

VerizonBusiness, Inc. Confidential & ProprietaryThis documentation is extremely sensitive; please limit distribution. No part of this document may be

photocopied, disclosed, or otherwise provided to third parties.

4/13/2023 1

Page 2: I cameo revision gd version2

TABLE OF CONTENTS

1 REVISION HISTORY.....................................................................................................................................................................3

2 INTRODUCTION............................................................................................................................................................................3

3 ASSUMPTIONS, AND DEPENDENCIES....................................................................................................................................3

3.1 CONSTRAINTS..............................................................................................................................................................................33.2 ASSUMPTIONS.............................................................................................................................................................................43.3 OPEN ISSUES................................................................................................................................................................................43.4 DEPENDENCIES............................................................................................................................................................................53.5 CONTINGENCIES..........................................................................................................................................................................5

4 SCOPE...............................................................................................................................................................................................5

5 CHANGE SUMMARY....................................................................................................................................................................5

6 PROCESS FLOW............................................................................................................................................................................6

7 DESIGN DETAIL............................................................................................................................................................................7

7.1 AO REQUEST...............................................................................................................................................................................87.2 IDENTIFYING TYPE OF ACCESS....................................................................................................................................................87.3 ACCESS PATH SELECTION ON/NEAR-NET...................................................................................................................................9

7.3.4 Identifying the On/Near-Net A site...................................................................................................................................97.3.5 Validating On/Near-Net A site.........................................................................................................................................97.3.6 Creating the access path..................................................................................................................................................9

7.4 ACCESS PATH SELECTION OFF-NET............................................................................................................................................97.4.4 Map NUP code to ABB-ISS-COM....................................................................................................................................97.4.5 Create the access path – Off-Net location id not supplied by eCost.............................................................................107.4.6 Create the access paths – Off-Net location id supplied by eCost.................................................................................10

7.5 PLATFORM HOMING..................................................................................................................................................................117.5.4 On/Near-Net...................................................................................................................................................................117.5.5 Off-Net............................................................................................................................................................................11

7.6 AO RESPONSE....................................................................................................................ERROR! BOOKMARK NOT DEFINED.7.7 DATA PROCESSES AND PRE-PROCESSES....................................................................................................................................11

7.7.4 Circuit options................................................................................................................................................................117.7.5 Foreign circuit ids and owners......................................................................................................................................137.7.6 Circuit load bandwidth mapping....................................................................................................................................13

7.8 CFA VALIDATION.....................................................................................................................................................................137.8.4 CFA issue potential solution..........................................................................................................................................13

8 APPENDIX.....................................................................................................................................................................................14

8.1 SERVICE PLATFORM VALUES.....................................................................................................................................................148.2 VZB ISS COM VALUES.............................................................................................................................................................148.3 ACCESS CIRCUITS......................................................................................................................................................................15

8.3.4 Sample shared access circuits........................................................................................................................................158.3.5 Asia Pac circuit slotting (March 2009)..........................................................................................................................15

8.4 SPEED – BANDWIDTH MAPPING ISSUE STATISTICS....................................................................................................................168.5 SPEED MAPPINGS.......................................................................................................................................................................178.6 INTERNATIONAL CFA VALIDATION..........................................................................................................................................178.7 F&E PRODUCT – SPEED MAPPING TABLE..................................................................................................................................188.8 CAMEO ICD..............................................................................................................................................................................188.9 ECOST ICD................................................................................................................................................................................198.10 CLOSED ISSUES.......................................................................................................................................................................19

9 CONTACTS (PARTICIPANTS OF THIS DOCUMENT..........................................................................................................23

10 Organizational Approvals for this Document................................................................................................................................23

4/13/2023 2

Page 3: I cameo revision gd version2

1 Revision History

DocumentVersion # Date Author Reason for Change

1.0 10/4/2010 Thomas Clay Initial document – draft.

2.0 11/11/2010 Thomas Clay First draft

2.1 11/26/2010 Thomas Clay Final edit / re-write

2 Introduction

This document describes modifications to the path design functionality released in 52252.AA (Cameo International) that are required to support Off-Net access in cases where the provisioning access location is not available from eCost.

3 Assumptions, Dependencies, Constraints and Issues

3.1 Constraints

Constraint ID

Description

C1 CAMEO is constrained by the quality of data that is available in F&E. A valid address and mapped representation of the access provider are required to guarantee provisioning selection of the closest interconnect with the provider that was chosen by Global Link.

C2 Technology specific provisioning locations that are not locations with shared access circuits cannot be identified unless selection rules are provided. This applies to Ethernet, DSL and public IP where product specific locations may be required

C3 The information required to identify the service type using the VDDS – F&E approach is not included in the access order. It is part of the service order but the access speed and number of circuits can differ between access and service orders. Development to pass access and service information to Cameo in the AO call is out of scope for this release. The users will be required to select the service type using the F&E service selection feature as a step in the AO process.

4/13/2023 3

Page 4: I cameo revision gd version2

3.2 Assumptions

Assumption ID

Description

A1 eCost will return either a valid provisioning location in the form of an F&E ABBLOC or a NUP code representing the carrier..

A2 Cameo will select access paths starting at the provisioning location returned by eCost. If a provisioning location was not returned, Cameo will select access paths starting at the provisioning locations associated with the carrier identified using the NUP code.

A3 If provisioning locations are identified using the NUP, the closest provisioning location to the customer that can support the ordered speed and product will be selected as the A site of the access path.

A4 eCost will always return an F&E ABBLOC representing the provisioning location when the access selection is On-Net or Near-Net.

A5 In cases where On-Net facilities are customer specific, eCost will return the location identifying the customer interconnect.

A6 In cases where an entire building is lit eCost will return the provisioning location representing the building POP.

A7 Latitudes and longitudes will be identified for the current 3rd party interconnect locations and the information will be added to F&E.

A8 Addresses for new 3rd party interconnect locations will be geo-coded using the OneStop / Avalon user interface and the latitude and longitude will be added to the inventory systems before the access paths are made available for customer access.

A9 F&E will support use of the service platform for international

3.3 Open issues

Issue ID Description Resolution StatusI1 Some speeds greater than

DS3/E3 the Cameo bandwidth mapping is inaccurate

Use F&E circuit type to speed mapping table

Open

4/13/2023 4

Page 5: I cameo revision gd version2

3.4 Dependencies

Dependency ID

Description

D1 Latitudes and Longitudes for interconnect locations D2 NUP or ICSC codes will be returned by eCostD3 F&E support for the manual service platform selection

3.5 Contingencies

The dependencies in section 3.3 are baseline requirements. No contingencies can be substituted and if they are not met the functionality can not be implemented.

4 Scope

The scope of this release is the same scope that was delivered for Cameo International 9.3 52252 AA. TDM/SDH access technology is supported for all speeds and products except public IP (IDE/IDA). Ethernet, SDL and MVIC access technologies are not supported nor are any products requiring these technologies.

5 Change summary

Modifications to Cameo International 52252 AA release 9.3 are needed because the off-net access locations will not be returned by the upstream application. This was a dependency for the 9.3 approach and unless the changes described in this document are made the functionality cannot be delivered.The following lists the changes that will be made to support Cameo international for Asia-Pac.

– Use of NUP code to identify access paths– Optional use of location id to identify access paths– Inclusion of international circuit options– Upgraded process for identifying bandwidth of access circuits

4/13/2023 5

Page 6: I cameo revision gd version2

6 Process Flow

4/13/2023 6

Page 7: I cameo revision gd version2

7 Design Detail

. The following list defines the path design functionality being delivered by Cameo to support International orders. The code supporting this functionality has already been deployed but is being modified with the major change being providing the ability to determine the access entrance using the carrier. The following list summarizes changes and rules required to support access path automation for AsiaPac SDH/TDM excluding diversity orders:

Change Type of change DescriptionAccess path request Business process The AO request included circuit type,

service type and PIP indicator for switched products but this information will not be passed by F&E on the access order. The service platform will be used as a substitute

Identification of Off-Net interconnect

Code and logic change

Two methods are supported:

1. F&E location id returned by eCost in extSiteId element

2. No location id then the NUP code will be used to identify provider locations in the country.

Off-Net path selection Code and logic change

Paths that have the bandwidth to support the request and that start at the Off-net interconnects will be identified. The one nearest the customer will be selected as optimal

Capacity verification Code and logic change

Capacity on the circuits on the optimal path will be checked and if there is a capacity problem the user will be notified in the response

Platform homing

Data mapping The Cameo - F&E service platform functionality will be used to identify the service type/ product. The original design identified the service type/ product from the service type and circuit type.

Access circuit bandwidth mapping

Preprocess & load The F&E circuit type to speed mapping table will be added to the Cameo bandwidth mapping logic.

Access circuit attributes Preprocess Changes will be made to ensure International circuit options and PTT ECCKT information is selected from the F&E extracts and included in the Cameo database.

4/13/2023 7

Page 8: I cameo revision gd version2

7.1 AO request

The process that supports automated selection of the optimal access path & switch location is based on interfaces between the provisioning systems and Cameo. The same interface is used for Option1 domestic and International. The following table lists elements or structures that are impacted by the changes to the design or to ensure quality

Element Impact RemarksAddressRequestModel Cameo- This is a double check

/ reminderThe F&E address elements cannot support some international addresses and we were unable to have the F&E field lengths changed. The agreed upon solution was for eCost to ensure that the addresses are validated and for Cameo to use the eCost version. Cameo was required to allow the users to view the address and the eCost order detail. This data must be retained and visible at least until all steps in the order process are complete. (test, turn-up and billing)

linecoding Cameo- This is a double check / reminder

Line codes are used in international and were detailed in the 52252 AA design. The preprocess might need to be updated to included CSS, CRC4-OFF and CRC4-ON as valid line codes for international

serviceType F&E – Only make access call for Order/site (Not present in access order)

With no solution to the Option 1 two order scenario being implemented. These elements will not be used. Service platform will be used to identify the platform type.

circuitType F&E – Only make access call for Order/site (Not present in access order)

pipIndirect F&E – Only make access call for Order/site (Not present in access order)

servicePlatform F&E – Include in access call, ensure available for international

Replacing service type – service type

7.2 Identifying type of access

A flag identifying the A site type is returned by eCost. This information is the first step used to identify the A-site. The information is supplied in the OECircuit structure element siteClassifiaction.

4/13/2023 8

Page 9: I cameo revision gd version2

–o = On-Net–n = Near-Net–f = Off-Net

7.3 Access path selection On/Near-Net

On-Net and Near-Net solutions use VZB facilities to connect with the customer. In the case of On-Net, the facilities existed when the quote was provided. With Near-Net, no facilities exist but the projected ROI warrants extending VZB facilities to the customer premise.

For both solutions, eCost must supply the A-location to Cameo as a prerequisite to creating the access path.

7.3.4 Identifying the On/Near-Net A site

The A site is returned by eCost. This information is required for On-Net and Near-Net and can not be derived by Cameo. The detail is supplied by eCost in the following structures:

–OESite structure–extSite element

7.3.5 Validating On/Near-Net A site

A valid A site must be supplied by eCost. The following edits will be performed to ensure the information is accurate.

–A check will be performed to ensure the location returned by eCost is a valid F&E location

–The ABB-ISS-COM associated with the location will be validated to ensure it is a VZB location. The VZB ABB-ISS-COM values can be found in Appendix 8.2

7.3.6 Creating the access path

A virtual path will be created for On-Net and Near-Net. The location passed from eCost will be both the A and Z location.

7.4 Access path selection Off-Net

Off-Net and OLO/CLEC paths start at a location where VZB connects with a 3rd party access carrier who will be used to connect with the customer.

Cameo will support two methods for Off-Net. If a location id exists in the eCost response it will be used as the starting point of the access path. If no location is provided, the path start point will be identified based on the provider information supplied by eCost.

7.4.4 Map NUP code to ABB-ISS-COM

eCost will return the NUP code of the chosen access provider in the OECircuit structure, element NUPCode. The following are the steps to identify the optimal access path.

1. Map NUP code to ABB-ISS-COM

a. A look up will be performed in the I_provider table using the NUP code and if found the ABB_ISS_COM will be selected

b. If ABB_ISS_COM is not returned an exception is set and the response returned to the calling system.

4/13/2023 9

Page 10: I cameo revision gd version2

c. If ABB-ISS-COM is a VZB ABB_ISS_COM (Appendix 8.2) an exception is set and the response returned to the calling system.

7.4.5 Selection – Off-Net location id not supplied by eCost

If no location is provided, Cameo will identify the path start point using provider information supplied by eCost. The following steps document the approach Cameo will use to build the access path.

1. Select eligible paths

a. Paths in the country on the request b. Path bandwidth can support the requestc. Path A location is an interconnect with the provider indicated by the NUP-

ABB_ISS_COM match.

2. Identify path optimal path

a. Calculate the distance between the customer and the start location of the eligible paths

b. Select the path with the closest start location to the customer

3. Verify capacity is available

a. Invoke the Provisioning Controller CFA interface for circuits on the optimal pathb. Check that available channels exist – (Channel bandwidth was not incorporated

into the service so the check cannot guarantee capacity is available) c. If capacity is not available populate all elements except CFA and numberOfCFA

and set a 1008 response..

4. Populate access path response

a. The access path response will be populated and returned to the calling system.

7.4.6 Selection – Off-Net location id supplied by eCost

Support for cases where the location id is supplied by eCost for OFF-Net location types is included in the design. The following steps document the approach Cameo will use to build the access path.

1. Return A location from eCost interface

a. OESite structureb. extSite element

2. Validate location

a. Verify location id is a F&E location idb. Verify the ABB-ISS-COM associated with the location matches the ABB-ISS-COM

returned in the NUP-ISS com translation

5. Select eligible paths

a. Path bandwidth can support the request

6. Verify capacity is available

a. Invoke the Provisioning Controller CFA interface for circuits on the optimal pathb. Check that available channels exist – (Channel bandwidth was not incorporated

into the service so the check cannot guarantee capacity is available) c. If capacity is not available populate all elements except CFA and numberOfCFA

and set a 1008 response.

7. Populate access path response

4/13/2023 10

Page 11: I cameo revision gd version2

a.The access path response will be populated and returned to the calling system.

7.5 Platform homing

Switch location homing is supported for platform services that connect to VZB with TDM/SDH technology. The only exception as listed in the 52252 AA 9.3 release 9.3 is Public IP (IDA). This was because IDA used a product specific architecture that was undergoing modification at the time of the release.

The homing architecture uses homing plans that are stored in Cameo and administered by switch planning. The design links the access terminating location that is identified during optimal path selection to a switch location. The following summarizes the design:

1. Option1 user selects a service platform from an F&E screen. a. The current service platform values are listed in appendix 8.1

2. The service platform, speed and bandwidth are sent to Cameo in the Option1 AO request

3. The service platform is mapped to a homing name.4. The optimal access path is selected by Cameo.5. The following elements are used to search for the switch site in the homing plan

a. The VZB end of the path (Backhaul) b. Homing name (Mapped from service type)c. Bandwidth

6. The switch location is selected and populated in the switchSite element of the response

This design is currently supported so no development is required but the data mapping but be done prior to implementation.

7.5.4 On/Near-Net

The homing design is based on the VZB end of the shared access path (Backhaul) but shared access is not part of the On-Net design. On-Net paths will use the location supplied by eCost for both the customer and VZB ends of the path. This requires that a homing plan exist for each On-Net location, service platform and bandwidth.

Planning will need to provide the On-Net location to switch location relationship.

7.5.5 Off-Net

The Asia-Pac switches are collocated at the VZB end of the shared access path. The development team will create the initial homing plans using the VZB end for both the backhaul and switch location.

7.6 Data processes and pre-processes

The following requirements were part of the initial release but may not have been implemented. To ensure accuracy the following changes must be made.

7.6.4 Circuit options

Circuit options are used in international and some countries use the US circuit options but the pre process needs to be updated to included the following options:

4/13/2023 11

Page 12: I cameo revision gd version2

TCIR-OPT Values CCSCRC4-OFFCRC4-ON           

4/13/2023 12

Page 13: I cameo revision gd version2

7.6.5 Foreign circuit ids and owners

The foreign circuit id and circuit owner associated with the shared access circuit is required in many countries and is part of the F&E -Cameo circuit interfaces but some international information is not being selected from the extract. The preprocess script needs to be analyzed to see if changes are needed to include international ECCKTS.

See Appendix 8.3.1 aggregate circuits for some example that have the ECCKTS

7.6.6 Circuit load bandwidth mapping

The current bandwidth mapping for F&E circuits do not always reflect the size of the circuit. The impact for Asia-Pac is minimal but as we expand international, the risk will increase. The following describes the method provided by F&E to map to a Cameo bandwidth.

1. Read F&E extract that is used to map IDN-TYP-CIR to a speed (VAL-SPD)2. In the circuit load or preprocess map IDN-TYP-CIR associated with the circuit to IDN-

TYP-CIR in the mapping table3. Map speed to Cameo bandwidth

– F&E mapping table extract is WLT.UO.DB.EXTRACT.CIR304(0) – VAL-SPD to Bandwidth is documented in – 8.5 is the F&E speed mapping table

Appendix speed bandwidth issue statistics 8.4

7.7 CFA Validation

International and domestic capacity validation have the same general design but have different speeds and international planning uses fiber circuits as channelized carriers for electronic bandwidths. Support for international CFA validation was deployed in Cameo International 9.2 but a key element was not included.

– International bandwidths – Extension of the channel arrays to account for E-1 on STM4– Channel bandwidth was not included and unless a solution is identified will reduce

accuracy

7.7.4 CFA issue potential solution

F&E CFA information is stored in TCAR-CAR and Cameo currently uses some of the information in the circuit pre-process. A workaround to the missing channel bandwidth follows:

1. Create the following reference table

Element name

Type Comments Examples

Circuit id String F&E carrier circuit W0R50185

Channel String Channel number 3Speed (or BW) Int (or string Val speed (Can be mapped to andwidth)

2. Load TCAR-CAR values into table3. Combine with values from CFA response on circuit and channel

CFA rules are documented in appendix speed mappings 8.64/13/2023 13

Page 14: I cameo revision gd version2

8 Appendix

8.1 Service platform values

Service platform

Homing Name

ATM ATMDSL ATMFR FRLYFRAME FRLYHSFR FRLYINTERNET ATMNXDS1ATM ATMNXDS1ATMBR ATMNXDS1FR FRLYNXDS1FRBR FRLYPIPDEDATM PDIRPIPDEDFR PDIRPIPNDEDATM PATMPIPNDEDFR PFRYVOICE ISDN

8.2 VZB ISS Com values

ABB ISS COMWORLDCOMVZBMCIWCOMWLDINT'LWCOMASIAUUN-AUSWILTELUUNETWCASUUN-INDIUUN-JAD

4/13/2023 14

Page 15: I cameo revision gd version2

8.3 Sample shared access circuits

CircuitE1 E3 DS3 STM1

SpareIn

use SpareIn

use SpareIn

use SpareIn

useW0N60898 3 60 0   0 0 0 0W0N60899 11 10 0 1 0 1 0 0W0P99218 0 63 0   0 0 0 0W0R10637 4 59 0   0 0 0 0

Circuit Bandwidth VENDOR VENDOR Circuit IDW0R54212 STM-4 TELSTRA J PZTJ EXHX F001-F004W0S16435 STM-4 OPTUS J 33CB 03ML W101W0R34670 STM-1 TELSTRA J CHTX VRNB F001W0S16498 STM-1 OPTUS J O4MO O4WF VC4S106W0S31974 STM-1 TELSTRA J WAYC ZMCE F001

8.4 Asia Pac circuit slotting (March 2009)

Country Carriers Requests

Australia STM-1 and STM-4E-1 and DS-3

Australia E-1 E-0China STM-1 E-1China E-1 E-0

India STM-4E-1 and DS-3

India E-1 E-0

Hong Kong STM-1 and STM-4E-1 and DS-3

Hong Kong E-1 E-0

Japan OC-3T1 and Ds-3

Japan DS-3 T-1Japan DS-1 DS-0Singapore STM-1 & STm-4 E-1Singapore E-1 E-0Thailand E-1 E-0Vietnam E-1 E-0 Taiwan E-1 E-0Taiwan STM-1 E-1Philippines STM-1 and STM-4 E-1Philippines E-1 E-0New Zealand Stm-4 and STM-1 E-1New Zealand E-1 E-0Malaysia E-1 E-0 South Korea DS-1 DS-0 Indonesia E-1 E-0

4/13/2023 15

Page 16: I cameo revision gd version2

8.5 Speed – Bandwidth mapping issue statistics

Counts of F&E N5F circuits by Cameo bandwidth

Cameo Bandwidth

Frequency Percent Running Total

DS3 7788 25.93 7788DS5ABA 6012 20.02 13800DS1 3548 11.82 17348STM4 2434 8.11 19782DS5 2125 7.08 21907DS5TRA 2016 6.71 23923STM16 1898 6.32 25821OC48 1809 6.02 27630DS3COA 1092 3.64 28722OC3 747 2.49 29469OC12 238 0.79 29707OC192 195 0.65 29902Not Mapped

74 0.25 29976

E1 48 0.16 30024STM64 3 0.01 30027STM1 1 0.00 30028STS12 1 0.00 30029

Counts of N5F using F&E speed

F&E Bandwidth

Frequency Percent Running Total

DS3 13800 45.96 13800Non Standard

5221 17.39 19021

DS1 3548 11.82 22569STM4 2436 8.11 25005STM16 1898 6.32 26903OC48 1810 6.03 28713STM1 580 1.93 29293OC12 237 0.79 29530OC192 225 0.75 29755OC3 168 0.56 29923STM64 57 0.19 29980E1 48 0.16 30028

4/13/2023 16

Page 17: I cameo revision gd version2

8.6 Speed mappings

Speed Value

Bandwidth Description

Possible Slot Levels

00000064000 DS-0 / E-0 N/A00001544000 DS-1 DS000044736000 DS-3 DS100002048000 E-1 E000034386000 E-3 E1

00155000000 STM-1E1-E3-DS3

00155520000 OC-3 DS1-DS3

00622000000 STM-4

E1-E3-DS3-STM1-OC3

00622080000 OC-12DS1-DS3-OC3

02488320000 OC-48 S02488000000 STM16 S09952000000 STM64 S09953280000 OC192 S

Bandwidth Mbps F&E speed values

DS1 1.5Mpbs 0001544000

E1 2Mbps 0002048000

E3 34Mbps 0034386000

DS3 44Mbps 0044736000

STM1 155Mpps 0155500000

OC3 155.52Mbps 0155520000

OC12 622Mbps 0622080000

STM4 622Mbps 0622000000

OC48 2.45Gbps 2488320000

STM16 2.45Gbps 2488000000

STM64 9.6Gbps 9952000000

OC192 9.6Gbp2 9953280000

4/13/2023 17

Page 18: I cameo revision gd version2

8.7 International CFA validation

The following is a summary of the CFA validation structures -

– Optical circuits can be subdivided into varying numbers of subordinate channels. The maximums are dependent on the bandwidth of the optical carrier and the size of the subordinate channel.

The following table illustrates the maximum channels by circuit bandwidth and subordinate bandwidth. Please note that International uses both US and International conventions.

AccessCircuit Bandwidth VENDOR Channel

Channel bandwidt

h Status VENDOR Circuit IDW0S16434 STM-4 TELSTRA 146 E1 WRK J KSTX VRB3 F001 – F004W0S16434 STM-4 OPTUS 147 E1 WRK J KSTX VRB3 F001 – F004W0S16434 STM-1 OPTUS 190 DS3 AVL J KSTX VRB3 F001 – F004W0S16434 STM-1 TELSTRA 211 DS3 AVL J KSTX VRB3 F001 – F004W0S16434 STM-1 TELSTRA 146 E3 AVL J KSTX VRB3 F001 – F004W0S16434 STM-1 TELSTRA 147 E1 AVL J KSTX VRB3 F001 – F004W0S16434 STM-4 OPTUS 190 E1 WRK J KSTX VRB3 F001 – F004

Maximum subordinate channel mappings

Carrier Bandwidth Subordinate Bandwidth

Max Subordinate Channels

OC3 DS3 3STM1 E1 63STM1 E3 4STM1 DS3 3STM4 E1 252STM4 E3 14OC12 DS3 12OC12 OC3 4OC48 DS3 48OC48 OC3 16OC48 OC12 4OC192 DS3 192OC192 OC3 64OC192 OC12 16OC192 OC48 4

8.8 F&E Product – speed mapping table

WLT.UO.DB.EXTRACT.SPD330 (0) contains all the speeds used by F&E and has descriptions of when they are used.

4/13/2023 18