Enhancement Theme: Trunking Marked-up Based on User Group Working Session Sal Rodriguez Senior Application Developer

<Insert Picture Here>

Enhancement Theme: TrunkingMarked-up Based on User Group Working Session

Sal RodriguezSenior Application Developer

The following is intended to outline our general product direction. It is intended for information purposes only, and may not be incorporated into any contract. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions.The development, release, and timing of any features or functionality described for Oracle’s products remains at the sole discretion of Oracle.


Agenda

• Issues Resolved• Open issues• Tomorrow• Q & A

Trunk-related Issues Resolved

Issue Release Description

CR00245573 6.0.10Trunk Group User Data on Trunk Group Information window does not display the same as trunk group product history

CR00248719 6.0.10TCO option disabled when processing design for a facility order with trunks

CR00248254 6.0.10Cannot disconnect Special Trunk Group, error In Service Children not on the Order

CR00231592 6.0.10ASR Trunking confirmation - FACDESIG and FACTYPE not saving

CR00244612 6.0.10 ASR NewFrom not copying FDT column

Trunk-related Issues Resolved(Cont’d)


CR00264725 6.0.10Error when group assigning trunks on a special circuit with equipment assignment

CR00198896 6.0.10ASR disconnect trunk contact information not showing up on design

CR00255027 6.0.11Application terminates when expanding treeview of a Dedicated Access Trunk Group on a new PSR order

CR00256991 6.0.11Specifying more than one row of trunks to disconnect causes application to crash

CR00262968 6.0.12Change icon should not be enabled on ASR Trunk Disconnect orders



CR00254244 6.0.12Removing In Progress trunk members from EWO cancels the trunks

CR00255765 6.0.12 Wrong TGN reuse error on Loc A TGN

CR00242678 6.0.12Unable to delete ASR with partially entered

Questionnaire Trunking Section

CR00242935 6.0.12TCO Printing with large number of circuits locks application

CR00250772 6.0.12CABS Billing does not validate when the ASR TTT field is blank on disconnecting trunks



CR00263285 6.0.12Unable to create more than 1,000 trunk members in a trunk group at once

CR00131901 6.0.13 Trunk Group Info Two Six Code enabled for editing

CR00180971 6.0.13Updating the CKR through ASR change order not updating the trunk circuit design details appropriately

CR00187428 6.0.13 Information is missing on Tech Translations Sheet

CR00259542 6.0.13Double TCIC rows created on change of Point Code between same Network Locations



CR00260517 6.0.13TCIC re-use Problem on ISR Record Activity after changing the SS7 Signaling code

CR00263232 6.0.13Rate code does not change back to previous value after supplement correct on an ISR Trunk order

CR00265446 6.0.13Item Validation on Import message when selecting values for the mandatory drop-down fields under the Trunk Info tab.

CR00267188 6.0.13When removing trunk connections on EWO with In Progress and Pending statuses, application terminates

Trunk-related Enhancement—Group Assign Across Facilities

• Added the ability to sequentially assign available channels from multiple available facilities using the ‘Assign All’ button found on the Group Assignment window.

• Benefit: Increased productivity

• Delivered in 6.0.10

Trunk-related Enhancement—Auto-create New Design Issue

• Added the ability to create new design issues for change activities that do not require actual design changes

• Benefit: Increased productivity due to automated design issue creation


Trunk-related Enhancement—Re-use TCICs on Pending Disconnects

• Added the ability to re-use TCICs that were assigned to a trunk members with a pending disconnect status

• Benefit: Faster re-use, no waiting until due date completion



Agenda


Priority Legend

• High (11 Issues)

• The issue results in a material negative impact on the business process, cost, or outcome

• There is no viable work-around

• Medium (9 Issues)

• The issue has a material negative impact on the business process, cost, or outcome

• There is a viable work-around

• Low (13 Issues)

• The issue has a less-than-material negative impact on the business process, cost, or outcome

Known Trunking Issues

1. Two Six Code Auto-numbering & Formatting

2. Two Six Code Validation

3. Two Six Code Reuse on Pending Disconnect

4. Duplicating PSR Trunks

5. Trunk Types Required

6. Special Trunk Group Relationships to TNs

7. TCO Report for Special Trunks

8. Point Code Table Updates

9. TGN Inventory

10.Disconnect Facility

Known Trunking Issues (Cont’d)

11.Free Format Identification Support12.Tech Translation Sheet for Special Trunks13.Navigation to the Order from Trunk Group14.Live Update of Trunk Group Information15.Number of Available Channels Displayed16.Trunk Group Search Capability17.Other TCIC18.Ability to Enter TGNs on PSR19.“New” not on Trunk Group Search window20.“New From” not on Trunk Group Search results

window

Known Trunking Issues (Cont’d)

21.Need to expand scope of query criteria

22.Limited support for trunk group “CLLI”

23.Trunk Group User Data limited and cumbersome

24.Trunk-level renumbering is cumbersome

25.Comprehensive trunk detail view not available

26.Need to view and maintain trunk groups from a facilities orientation

27.Trunk group maintenance is cumbersome and unintuitive

Trunking Issues (New Stuff)

28.Navigation from Order to the Trunk Group

29.PSR Valid Value Labels mismatch

30.Support for IP transport Trunk Group Modeling

31.Modeling NextGen MPLS (L3)

32.Trunk Group InterRelationships and Mapping

33.Trunk Group Data Execution Points

1. Two Six Code Generation

• Problem: No ability to generate & format two six codes• Impact: Requires users to enter TSCs manually• Initial User Group Priority: HighPSR special trunk order

PSR message trunk order

Trunk Group Info window

2. Two Six Code Format Validation

• Problem: No format validation on save of two six code• Impact: Allows inaccurate data• Initial User Group Priority: High

PSR special trunk order

PSR message trunk order


3. Two Six Code Reuse on Pending Disconnect

• Problem: Two Six Code cannot be reused when the trunk group is in pending disconnect status

• Impact: Increased ordering time due to having to wait until the trunk group has been due date completed to reuse or requires the completion of the disconnect order prematurely

• Initial User Group Priority: High

4. Duplicating PSR Trunks

• Problem: There is no ability to duplicate a previous created trunk • Impact: Time consuming entering data when multiple trunk groups

are on an order• Initial User Group Priority: Low

5. Trunk Types Required

• Problem: Non-editable, required field limited to three values

• Impact: Inadequate, restrictive, inaccurate reporting• Initial User Group Priority: Medium

Trunk Group Info window PSR window

6. Special Trunk Group Relationships to TNs

• Problem: Not a consistent and clean way to map telephone numbers and blocks of numbers to trunks and groups of trunks

• Impact: Very time consuming, must open multiple PSR windows to determine relationships

• Initial User Group priority: High

7. TCO Report for Special Trunks

• Problem: No report for special trunk groups

• Impact: • Lack of consolidated view of

data,

• requires multiple CLR printouts

• Wasteful and Cumbersome Output

• Initial User Group Priority: Medium

Message trunk TCO example

8. STP Point Code Maintenance

• Problem: Point codes on STP entry are not maintained in sync with Network Location Point Codes

• Impact: Redundant data entry; must navigate to Infrastructure and re-enter the code

• Initial User Group Priority: MediumPSR window


9. TGN Inventory

• Problem: Difficult to determine what the next TGN is for a given switch

• Impact: It’s a guessing game….• Initial User Group Priority: High

10. Disconnect Facility with Trunks

• Problem: No mechanized way to include the supporting T1 facility when trunk riders are being disconnected

• Impact• Manual process to determine, query and include• Left-In Facilities Cause

• Data Integrity Issues • Stranded Capacity• Billing Errors


11. Trunk Group Identification Flexibility

• Problem: Limited identification format support for special trunks (currently defaulted with TSC or Billing Number plus sequence number)

• Impact: Inadequate naming flexibility• Initial User Group Priority: Low

12. Tech Translation Sheet for Special Trunks

• Problem: No implementation-oriented view for special trunks• Impact: Lack of consolidated view of data• Initial User Group Priority: Low

13. Navigation from Trunk Group to the Order

• Problem: Cannot navigate to orders from Trunk Group Information window

• Impact: “Brutily” Time Consuming and Productivity Hinderance• Initial User Group Priority: High

14. Update of Trunk Group Information

• Problem: Need the appropriate level of flexible and control on how trunk group data is maintained

• Impact: Some people can’t do what they need to do when they need to do it

• Initial User Group Priority: Low

15. Number of Available Channels Displayed

• Problem: Cannot determine the number of available channels when selecting a facility on Group Assign window

• Impact: Tedious process to determine channels


16. Trunk Group Search Capability

• Problem: The Trunk Group Search window does not use the same ‘OR’ searching for network locations as the Connection Design window

• Impact: Cumbersome having to execute query twice• Initial User Group Priority: High

Trunk Group Connection Design

17. Other TCIC

• Problem: No mechanism to keep track of other TCICs for trunk members for intra-switch trunks (“Loopies”)

• Impact: Requires external inventory• Initial User Group Priority: Low

18. Ability to Enter TGNs on PSR

• Problem: Limited ability to enter TGNs on the PSR trunk order

• Impact: Time consuming navigating to other windows


Message Trunk

Special Trunk

19. “New” on Trunk Group Search Window

• Problem: Cannot create a new trunk group using menu option on Trunk Group query window

• Impact: Increased keystrokes to enter trunk group


20. “New From” Not on Trunk Group Search Results Window

• Problem: Cannot copy attributes of existing trunk group using menu option on Trunk Group results window

• Impact: Increased keystrokes to enter trunk group• Initial User Group Priority: Low

21. Need to Expand Scope of Query Criteria

• Problem: More search options are needed when querying for trunk groups, (Customer’s Identification (CKR), Facility Circuit ID)

• Impact: Time consuming• Initial User Group

Priority: Medium

22. Trunk Group “CLLI”

• Problem: Inconvenient method to inventory Switch Trunk Group “CLLI” except for User Data

• Impact• Time consuming, large number of User Data fields causes

confusion• Work-Arounds: user data or description


23. Trunk Group User Data Limited and Cumbersome

• Problem: User Data does not support filtered information for specific types of trunk groups, displays all fields for all trunk groups, no data value dependency

• Impact: Unruly, causes confusion, inflexible• Initial User Group Priority: Medium

24. Trunk-level Renumbering is Cumbersome

• Problem: Renumbering of Trunk Numbers, Members, TCICs is not intuitive

• Impact: ‘Brutilly” Time consuming - Windows are confusing

• Initial User Group Priority: HighTGN TCIC

25. Comprehensive Trunk Detail View Not Available

• Problem: Does not display switch-specific information conveniently for trunk members

• Impact: Causes confusion


26. Need to View and Maintain Trunk Groups From a Facilities Orientation

• Problem: Trunk Groups are maintained only from a Trunk Group perspective and not from a Facility orientation

• Impact: Hampers productivity• Initial User Group Priority

27. Trunk Group Maintenance is Cumbersome and Unintuitive

• Problem: The entire Trunk Group maintenance process has limited capabilities, navigation and views

• Impact: Confusing, hampers productivity


28. Navigation from Order to the Trunk Group

• Problem: Cannot navigate from orders to Appropriate Trunk Group Maintenance window

• Impact: Time Consuming and significant Training Issue


29. Valid Value labels and Trunk Group Info Tab labels mis-match

• Problem: Mismatch between • PSR (MetaSolv Defined Labels) Valid Value Labels • Related PSR Special Trunk Group Info Tab attribute labels

• Impact: Usability Confusing - Training Issue• Initial User Group Priority: Low

30. Support for IP transport Trunk group Modeling

• Problem: Require support IP transport trunks (Virtual Trunk Groups)• Ethernet connection Originating and terminating points

• Virtual ‘Trunks’ over TDM

• Reference TEKELEC T6000 / T7000 Softswitch Technology

• TEKELEC – PSTN Trunking

• Impact: Unclear how to support this technology in the product• Initial User Group Priority: Medium

31. Modeling NextGen MPLS (L3) Trunk Oriented Service Arrangements

• Problem: Modeling NextGen MPLS

• All Virtual Trunking• Template-Based Trunking• Extranet Support

• Issue• This issue is unclear based on the interactions during the

working session• We believe this is more about modeling packet based

backbone and service technologies more than trunking


32. Trunk Group InterRelationships and Mapping

• Problem: Trunk Group Inter Relationships• PRI/B – PRI/D Mapping

• Primary - Overflow Mappings

• Support for Trunk Group Bundles

• (possible overlap with Trunk Group User data issue number 23)

• Impact: TBD• Initial Priority: Low

33. Trunk Group Data Execution Points

• Problem: Soft & TDM Switches serving same EUL• Events in trunk group process

• Research still needs to be done on this issue before officially entering into this list

• Impact: TBD• Initial Priority: Low


Agenda


Tomorrow

• What’s Missing?• Detailed Issue Review/Discussion

• Is each issue well understood and defined• User Group ‘Take-Away’ Actions

• Business Impact + Value = Priority

Next Steps

• Oracle: Supply updated Issue Slides (04/27/07))

• User Group Validation and Valuation (Target 06/06/07)

• Final List of Issues• Confirmed Consensus Priorities (H/M/L)• Quantified Business Cases with Impacts/Value

• User Group Use Cases (07/18/07)

• Detailed Business use cases• Illustrate and clarify each issue

• Oracle Confirmation (09/12/07)

• Review of Issues and Understanding• Potential Approaches and Alternatives where Available

AQ&

Documents

Enhancement Theme: Trunking Marked-up Based on User Group Working Session Sal Rodriguez Senior Application Developer