Skip Headers
Oracle® Communications Order and Service Management Developer's Guide
Release 7.2.2

E35419-02
Go to Documentation Home
Home
Go to Table of Contents
Contents
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

11 Process Example

This chapter describes an example of a competitive local exchange carrier (CLEC) using Oracle Communications Order and Service Management (OSM) to provision a POTS customer using unbundled local loop.

About the Process Example

Figure 11-1 depicts a sample OSM process. An independent local exchange carrier (ILEC) customer wants to replace an ILEC service with a CLEC POTS service. These are typically residential or small office, a home office (SOHO) customer with a small number of phone lines, (a larger business customer would generally have equipment installed at the customer premise to support a large number of connections and use higher bandwidth connections from the CLEC central office (CLEC CO) to customer site). The CLEC CO contains the switch to be used for connection to the customer. This example assumes that the CLEC also has existing presence and capacity at the ILEC CO that currently serves the customer.

The CLEC uses the ILEC local loop that connects the ILEC CO to the customer. The CLEC uses Digital Loop Carrier (DLC) technology that uses a higher bandwidth connection (typically 1 or more DS-1 connections, DS-3, and so on) from the CLEC switch to the DLC equipment (at the ILEC CO) that provides individual DS-0 ports for connection to the copper loop to the customer.

Figure 11-1 Overview of OSM Process

Illustrates an overview of OSM processes, as described in surrounding text.

The following diagrams show a graphical representation of the OSM process flow described in this document. The symbols used are described in the legend. The tasks are arranged to identify which group is performing the task, Customer Care or OSM. The task numbers correspond to the section that describes the task.

Figure 11-2 OSM Process Flow

Shows a graphical representation of the OSM process flow described in this document.

Process Flow Diagram

Figure 11-3 OSM Flow

Shows a graphical representation of the OSM process flow described in this document

Figure 11-4 OSM Flow (continued)

Shows a graphical representation of the OSM process flow described in this document

Figure 11-5 OSM Flow (continued)

Shows a graphical representation of the OSM process flow described in this document

About the Tasks Defined in the Process Example

The following sections describe the tasks that make up the process of providing a new CLEC customer with a POTS service.

Before starting the process, information must be gathered from the customer. This is typically done by a Customer Service Representative (CSR) or Sales person. The information is generally entered into an order entry system by the CSR.

The Order Entry System also assigns an order number for the customer order that must be used to reference the activities taking place in the Integrated Suite components. The customer may order more than one service that requires separate processing. These must be identified and service processes started as necessary to implement the required services. In this case assume that the only service requested is POTS, and that only a single line is contained within each order initiated in the suite (OSM).

In this example, each task that is described, contains the following sections:

The data format is described as A/N (Alpha/Numeric), or N (Numeric) with the number of characters, fixed format types such as Date or Phone, or Lookup, where a lookup table is used to set the value.

The source of data is the task that generated the data, or, within the generating task description.

Initiate Order

To begin activities, an order must be entered into OSM or there must be an interface between the Order Entry System (OES) and OSM that allows the information to be automatically passed into OSM.

Activities

Enter the data into OSM and initiate the process. Otherwise, the data is entered automatically into OSM, from OES, and the process is initiated.

Input Data

None.

Output Data

Table 11-1 Output Data for Initiate Order

OSM Business Name Description Format Source

OSM Order ID

OSM assigned order number

9 A/N

OSM

Customer Order Number

The order number assigned by the order entry system

12 A/N

OES


Table 11-2 Output Data: Customer Details Group

OSM Business Name Description Format Source

Customer Name

Customer name

30 A/N

OES - Customer

Customer ID Number

Assigned by OE system

12 A/N

OES


Table 11-3 Output Data: Service Address Group

OSM Business Name Description Format Source

Street address

Street address number

40 A/N

OES - Customer

City

City name

25 A/N

OES - Customer

State or Prov Code

State abbreviation

2 A

OES - Customer

Zip or Postal Code

Postal code

10 A/N

OES - Customer

Additional Description

Additional address description

50 A/N

OES - Customer


Table 11-4 Output Data: Contact Details Group

OSM Business Name Description Format Source

Contact Name

A contact in case a problem is encountered

30 A/N

OES - Customer

Contact Phone Number

Contact phone number

Phone number

OES - Customer

Contact Cell Phone

Contact cell phone

Phone number

OES - Customer


Table 11-5 Output Data: Service Details Group

OSM Business Name Description Format Source

Existing phone number

Existing phone number

Phone number

OES - Customer

Port Existing Number?

Port existing number

Lookup[Y - Yes N - No]

OES - Customer

New Number

If required, blank otherwise

Phone number

OES - Number Assignment System

Current Access Provider

Current provider of local phone service [name or code number]

20 A/N

OES - Customer

Current Account number

Customer account number with ILEC

C20 A/N

OES - Customer

ILEC CO CLLI

Location code of ILEC CO where local loop terminates (blank if not known)

11 A/N

OES

LD Provider

Long distance provider (to set PIC in switch) [code number]

6 A/N

OES - Customer

Service Type

Business/Residential POTS [service code]

Lookup[B - Business R - Residential]

OES - Customer

Priority

Expedite/Normal

Lookup[E - Expedite N - Normal]

OES - Customer

Due Date

Required in service date

Date

OES - Customer


Table 11-6 Output Data: Service Feature Group

OSM Business Name Description Format Source

Service Feature 1.12

Features required (as detailed below)

12 entries, each consisting of: Feature identifier: LookupFeature parameter 1:12 A/NFeature Parameter 2:12 A/N

OES - Customer


Table 11-7 Feature List

Feature Name Description Lookup Code Feature Parameter 1 Feature Parameter 2

Three way calling

Allows a customer to add a third party to and existing conversation without operator assistance

3WC

Not Used

Not Used

Call Waiting

Informs a busy station user by a burst of tone that another call is waiting. The busy station may answer the new call by placing the original call on hold and flashing the switch hook or going on hook.

CW

Not Used

Not Used

Call Forwarding -Variable

Calls to the line are forwarded to another network address when this feature is subscribed to and the customer has activated it. An access code and the forwarding number is dialed to activate the feature.

CFV

Call Forward DN The number to which the call is forwarded

Call Forward Rings Interval (Number of seconds of ringing before call is forwarded)

Call Forwarding - Busy

When the subscriber line is busy, the call is forwarded to a designated line.

CFB

Call Forward DN The number to which the call is forwarded

Call Forward Rings Interval (Number of seconds of ringing before call is forwarded)

Call Forwarding - Don't Answer

When the subscriber does not answer, calls are forwarded to designated number.

CFD

Call Forward DN The number to which the call is forwarded

Call Forward Rings Interval (Number of seconds of ringing before call is forwarded)

Remote activation of call forwarding

Allows a subscriber with CFV to activate/deactivate the feature from a line other than their own.

CFR

Remote Activation Pin (Pin to access this feature from a remote location)

Not Used

Customer Changeable Speed Calling - 1 Digit

Allows the customer to maintain the list, short

SC1

List Size

Not Used

Customer Changeable Speed Calling - 2 Digit

Allows the customer to maintain the list, long

SC2

List Size

Not Used

Caller ID - Number

Shows calling numbers on display.

CNU

Not Used

Not Used

Caller ID - Name

Gives the Caller Id feature with Name

CNA

Not Used

Not Used

Caller ID - Blocking (Call Blocking)

Blocks outgoing call information

CBL

Not Used

Not Used


Additional data may be gathered in the OES concerning the customer that is not required in the suite unless OSM is performing some order entry functions. This information may include information such as customer billing address, additional contacts and phone numbers, pricing information, and so on.

Completion

The "ILEC CO CLLI Identified? (Rule Task)" task runs.

ILEC CO CLLI Identified? (Rule Task)

The following sections describe ILEC CO CLLI Identifiers.

Task Activities

Check the ILEC CO CLLI data element. If it has an entry, complete the task with the status True. Otherwise, complete the task with the status False.

Input Data

Service Details Group

Output Data

None

Completion

True: The"Assign Port" task runs.

False: The"Identify ILEC CO" task runs.

Identify ILEC CO

The ILEC CO, which is connected to the customer, is generally determined using the NPA-NXX portion of the customer's telephone number or by the Postal or Zip code. The purpose of this task is to identify the ILEC CO if it was not provided in the order information.

Task Activities

  1. Perform a lookup into a database that matches phone numbers or postal codes to the ILEC CO (or switch) CLLI.

  2. Enter the CLLI into the data element ILEC CO CLLI.

  3. Complete the task.

Input Data

  • Customer Order Number

  • Customer Details Group

  • Contact Details Group

  • Service Details Group

Output Data

Service Details Group

Table 11-8 Output Data for Identify ILEC CO Task

OSM Business Name Description Format

ILEC CO CLLI

Location code of ILEC CO where local loop terminates

11 A/N


Completion

The "ILEC CO CLLI Identified? (Rule Task)" task runs.

Assign Port

This task interacts with UIM to perform the necessary functions to locate and assign a port for the required service.

Task Activities

  1. Find the location with a common language location identifier (CLLI) attribute equal to the value of ILEC CO CLLI.

  2. If it is not found, this indicates no presence at CO, or perhaps an error in the CLLI. Set the data element No Presence to True.

  3. Complete the task with a Problem status. Otherwise, based on the Service Type, determine the required signal type, type of port, and the equipment to use for the search.

  4. Find the port of the required type in the appropriate equipment whose Status attribute is Available.

  5. If no port is found, set the data element No Capacity to True.

  6. Complete the task with a Problem status. Otherwise, set the port Status attribute to Assigned.

  7. Store the Customer ID Number in the port attribute Customer ID.

  8. Store the Customer Order Number in the port attribute Order ID.

  9. Store the OSM Order Number in the port attribute OSM Order ID.

  10. Store the New, if entered, or existing phone number in the port attribute Phone No.

  11. Determine the termination point of the port on the IDF (site, rack, panel, port identifiers) and store it in the data element Termination Point.

  12. Obtain the LEN/OE for the port and store in the data element Port OE or LEN.

  13. Obtain the identifier (CLLI) for the switch controlling the port and store in the data element Switch ID.

  14. Obtain the Location Routing Number (LRN) for the switch controlling the port and store in the data element Switch LRN.

  15. Complete the task with the status Success.

Input Data

  • OSM Order ID

  • Customer Order ID

  • Customer Details Group

Output Data

Assignment Details

Table 11-9 Output Data for Assign Port Task

OSM Business Name Description Format

No Presence

No presence at ILEC CO

Lookup[1 - True 0 - False]

No Capacity

No ports available

Lookup[1 - True 0 - False]

Port OE or LEN

ID of port assigned

40 A/N

Termination Point

Identifier of IDF port where port is terminated

40 A/N

Switch ID

Identifier of the switch controlling the port

11 A/N

Switch LRN

LRN of the switch for LNP

Phone number


Completion

Success: The"Send LSR to ILEC" task runs.

Problem: The"Notify Customer of Delay" task runs.

Notify Customer of Delay

This task deals with notifying a customer of an order delay.

Task Activities

  1. Determine the cause of the problem and the impact on customer delivery.

  2. Alert Network Engineering to the problem.

  3. Contact the customer for a decision to continue with the order.

  4. If the customer cannot wait, complete the task with the status Cancel.

  5. If the customer can wait, enter the Updated Due Date.

  6. Complete the task with the status Wait.

Input Data

  • Customer Order Number

  • Customer Details Group

  • Contact Details Group

  • Service Details Group

  • Assignment Details Group

Output Data

Updated value

Service Details Group

Table 11-10 Output Data for Notify Customer of Delay Task

OSM Business Name Description Format

Updated Due Date

Revision Required in service date

Date


Completion

Cancel: The "Cancel Order" task runs.

Wait: The"Wait for Engineering" task runs.

Cancel Order

This task deals with cancelling orders.

Task Activities

  1. Enter the data element Reason for Cancellation.

  2. Enter the data element Cancellation Date.

  3. Complete the task.

Input Data

  • Customer Order Number

  • Customer Details Group

  • Contact Details Group

  • Service Details Group

  • Assignment Details Group

Output Data

Cancellation Details Group

Table 11-11 Output Data for Cancel Order Task

OSM Business Name Description Format

Cancellation Date

Cancellation date

Date

Reason for Cancellation

Reason for cancellation

160 A/N


Completion

Terminate order.

Wait for Engineering

The following sections describe the parameters which require engineering intervention.

Task Activities

  1. Wait for an update from engineering indicating that the presence/capacity is available.

  2. When available, enter the date into the data element Engineering Complete Date.

  3. Complete task.

Input Data

  • Customer Order Number

  • Customer Details Group

  • Contact Details Group

  • Service Details Group

  • Assignment Details Group

Output Data

Assignment Details Group

Table 11-12 Output Data for Wait for Engineering Task

OSM Business Name Description Format

Engineering Complete Date

Engineering completion date

Date


Completion

The "Assign Port" task runs.

Send LSR to ILEC

To acquire the use of the local loop, local service request (LSR) forms must be sent to the ILEC. There are a number of possible forms that may be used depending on the type of request. For an unbundled loop request, three forms must be sent to the ILEC, the LSR, EU, and LS as described below. Some of the data required to fill the forms is available from OSM and some data is provided by the person filling the forms.

Task Activities

  1. Enter data into three Local Service Request (LSR) forms:

    • Loop Service Request Form (LSR)

    • End User Information Form (EU)

    • Loop Service Form (LS)

  2. Transmit the forms to the ILEC.

  3. Complete the task.

Input Data

  • Customer Order Number

  • Customer Details Group

  • Contact Details Group

  • Service Details Group

  • Assignment Details Group

Output Data

LSR Details Group

Table 11-13 Output Data for Send LSR to ILEC Task

OSM Business Name Description Format

LSR Sent Date

Date that LSR was sent to ILEC

Date


Completion

The "Receive LSR Confirmation" task runs.

Receive LSR Confirmation

A response to the LSR request and the LSR Confirmation (LSC), is returned by the ILEC.

Task Activities

  1. Wait for LSR response from ILEC.

  2. Receive the response and handle any problems that can be resolved. For example, schedules.

  3. If there are any problems, complete with status of the LSR with Problem. Otherwise, enter the data from the LSC.

  4. Complete with the status of Success.

Input Data

  • Customer Order Number

  • Customer Details Group

  • Contact Details Group

  • Service Details Group

  • Assignment Details Group

  • LSR Details Group

Output Data

LSR Details Group

Table 11-14 Output Data for Receive LSR Confirmation Task

OSM Business Name Description Format Source

LSR Number

Local Service Request Number (provider)

18 A/N

LSC Field # 6

Provider Order Number

Order Number (provider)

20 A/N

LSC Field # 7

Confirmation Date

Confirmation Date Sent

Date

LSC Field # 11

Provider Rep

Provider Contact Representative

15 A/N

LSC Field # 12

Provider Rep. Phone

Telephone Number (of provider's rep)

Phone number

LSC Field # 15

Provider Due Date

Due Date

Date

LSC Field # 19

Provider Estimated Date

Estimated Due Date

Date

LSC Field # 28

Cut over time

Frame Due Time (cutover time)

10 A/N

LSC Field # 18

Provider Bill Date

Effective Bill Date

Date

LSC Field # 20

LSR Problem Identifier

Reason Code

2 A/N

LSC Field # 26

LSR Problem Detail

Reason Code Jeopardy Detail

60 A/N

LSC Field # 27

Provider Designer

Network Service Provider (NSP) Design/Engineering Contact

15 A/N

LSC Field # 31

Provider Designer Phone

Telephone Number

Phone number

LSC Field # 32

Provider Circuit ID (ECCKT)

Exchange Company Circuit ID

41 A/N

LSC Field # 48

Provider Loop Order Number

Loop Order Number

20 A/N

LSC Field # 56


Completion

LSR Problem: The "Handle LSR Problem" task runs.

Success: The "Send LNP Porting Request" task runs.

Handle LSR Problem

The following sections describe handling LSR problems.

Task Activities

  1. Handle any problems with the LSR.

  2. Update any LSR data fields as required.

  3. Complete the task.

Input Data

  • Customer Order Number

  • Customer Details Group

  • Contact Details Group

  • Service Details Group

  • Assignment Details Group

  • LSR Details Group

Output Data

Updated fields as required.

Completion

The "LNP Required? (Rule Task)" runs.

LNP Required? (Rule Task)

The following sections describe the rule task that determines whether LNP is required.

Task Activities

If the Port Existing Number is Y, complete the task with a True status. Otherwise, complete the task with a False status.

Input Data

Table 11-15 Output Data for LNP Required Task

OSM Business Name Description Format Source

Port existing number?

Port existing phone number

Lookup[Y - Yes N - No]

Initiate order


Output Data

None

Completion

True: The "Send LNP Porting Request" task runs.

False: The "Activate Port and Services on CLEC Switch" runs.

Send LNP Porting Request

If the LNP is available and required, a porting request is generated and sent to the NPAC (Number Portability Accounting Center).

Task Activities

  1. Generate a porting request to the Number Portability Accounting Center (NPAC) using the data provided and manually generated data.

  2. Transmit the request to NPAC.

  3. Complete the task.

Input Data

  • Customer Order Number

  • Customer Details Group

  • Contact Details Group

  • Service Details Group

Output Data

LNP Details Group

Table 11-16 Output Data for Send LNP Porting Request Task

OSM Business Name Description Format

LNP Sent Date

Date that LNP request was sent to NPAC

Date


Completion

The "Receive LNP Confirmation" task runs.

Receive LNP Confirmation

A response to the LNP request is returned by the NPAC.

Task Activities

  1. Wait for the LNP response from NPAC.

  2. Receive the response.

  3. If there are any problems, complete with a status of LNP Problem. Otherwise, enter the data from the NPAC response.

  4. Complete with a status of Success.

Input Data

  • Customer Order Number

  • Customer Details Group

  • Contact Details Group

  • Service Details Group

  • Assignment Details Group

  • LNP Details Group

Output Data

LNP Details Group

Table 11-17 Output Data for Receive LNP Confirmation Task

OSM Business Name Description Format

LNP Reference Number

LNP request reference number from NPAC

18 A/N

LNP Confirmation Date

Confirmation date Received

Date


Completion

LNP Problem: The "Handle LNP Problem" task runs.

Success: The "Activate Port and Services on CLEC Switch" task runs.

Handle LNP Problem

The following sections describe handling LNP problems.

Task Activities

  1. Handle any problems with the LNP request.

  2. Update any data fields as required.

  3. Complete the task.

Input Data

Same as previous for reference purposes.

  • Customer Order Number

  • Customer Details Group

  • Contact Details Group

  • Service Details Group

  • LNP Details Group

Output Data

Updated fields as required.

Activate Port and Services on CLEC Switch

The required switch activations are performed.

Task Activities

  1. Get required activation information.

  2. Activate switch.

  3. If activation is successful, store the date in the data element Activation Date.

  4. Complete the task with a status Success.

  5. If activation unsuccessful, store the error information in the data element Activation Error Info.

  6. Complete the task with a status Activation Failed.

Input Data

  • Customer Order Number

  • Service Details Group

  • Assignment Details Group

Output Data

Activation Details Group

Table 11-18 Output Data for Activate Port and Services on CLEC Switch Task

OSM Business Name Description Format

Activation Date

Date activation was completed

Date

Activation Error Info

Activation error returned from ASAP or IP Service Activator

60 A/N


Completion

Success: The "Check for Loop Availability" task runs.

Activation Failed: The "Handle Activation Problem" task runs.

Handle Activation Problem

The following sections describe handling activation problems.

Task Activities

  1. Work with the activation system to determine a reason for the activation failure.

  2. Correct the problem.

  3. Complete the task.

Input Data

  • Customer Order Number

  • Service Details Group

  • Assignment Details Group

  • Activation Details Group

Output Data

Updated data fields as required.

Check for Loop Availability

When the loop is due to be switched over to the ILEC, it may be done within a time span of many hours. In order to minimize interruption to the customer and ensure that the changeover is successfully completed, the line is checked for connection beginning at the earliest time the changeover is expected.

Task Activities

  1. Setup the test equipment as necessary to check for loop completion.

  2. If it is not detected in a specific time following the expected date, contact the ILEC to investigate the problem.

  3. When the loop is available, complete the task.

Input Data

  • Customer Order Number

  • Customer Details Group

  • Contact Details Group

  • Service Details Group

  • Assignment Details Group

  • LSR Details Group

  • Activation Details Group

Output Data

Completion Details Group

Table 11-19 Output Data for Check for Loop Availability Task

OSM Business Name Description Format

Loop Available Date

Date the loop was found to be available

Date


Completion

The "Update UIM" task runs.

Update UIM

The following sections describe updating UIM.

Task Activities

  1. Access the assigned port attributes, update the attribute Status to Active, and store the ECCKT in the port attribute Provider Circuit ID.

  2. Complete the task.

Input Data

  • Customer Order Number

  • Service Details Group

  • Assignment Details Group

  • LSR Details Group

Output Data

None

Completion

The "Order Complete" task runs.

Send Activation Notice to NPAC

The following sections describe sending notices to NPAC.

Task Activities

  1. Send a message to the NPAC confirming that the LNP change was activated.

  2. Store the date of sending the activation notice in the data element LNP Activation Date.

  3. Complete task.

Input Data

  • Customer Order Number

  • Customer Details Group

  • Service Details Group

  • LNP Details Group

Output Data

LNP Details Group

Table 11-20 Output Data for Send Activation Notice to NPAC Task

OSM Business Name Description Format

LNP Activation Date

Date LNP activation sent

Date


Completion

The "Order Complete" task runs.

Update Other Systems

The following sections describe updating other systems.

Task Activities

  1. Notify external systems:

    • Telephone directory producer (may be the ILEC).

    • Directory assistance provider (may be the ILEC).

    • 911?

  2. Notify other interested CLEC systems that the service is active. These may include:

    • Billing - start billing customer

    • Accounting - receives charges for local loop

  3. When activities are finished, complete the task with a status Success.

Input Data

  • Customer Order Number

  • Customer Details Group

  • Contact Details Group

  • Service Details Group

  • Assignment Details Group

  • LSR Details Group

  • LNP Details Group

  • Activation Details Group

  • Completion Details Group

Output Data

Completion Details Group

Table 11-21 Output Data for Update Other Systems Task

OSM Business Name Description Format

System Update Completion Date

System update completion date

Date


Completion

The "Order Complete" task runs.

Order Complete

Notify Customer Service that the order is complete.

Task Activities

  1. Review data as desired.

  2. Enter the date into the data element Order Completion Date.

Input Data

  • Customer Order Number

  • Customer Details Group

  • Contact Details Group

  • Service Details Group

  • Assignment Details Group

  • LSR Details Group

  • LNP Details Group

  • Activation Details Group

  • Completion Details Group

Output Data

Completion Details Group

Table 11-22 Output Data for Order Complete Task

OSM Business Name Description Format

Order Completion Date

Order completion date

Date


Completion

Complete: The order is now completed.

About Port Configuration Data

The following sections describe the port configuration data.

Physical Port

  • Status

    • Available

    • Assigned

    • Reserved

    • Active

  • Customer ID

  • OSM Order ID

  • Order ID

  • Phone Number

  • Provider Circuit ID

Functional Switch

  • LRN

  • Switch ID

About OSM Data Summary, Grouping

The following is a summary of all OSM data elements organized by groups as used in OSM. If a group name is indented, the group is a subgroup of the previous group. The Process defined in OSM is Phone Line Activation and the order template is POTS/Order Entry. Views are defined to match the groups.

Table 11-23 OSM Data Summary

OSM Business Name Description Format Source Task

OSM Order ID

OSM assigned order number

9 A/N

OSM

Customer Order Number

The order number assigned by the order entry system

12 A/N

Initiate Order


Table 11-24 OSM Data Summary: Customer Details Group

OSM Business Name Description Format Source Task

Customer Name

Customer name

30 A/N

Initiate Order

Customer ID Number

Assigned by OE system

12 A/N

Initiate Order


Table 11-25 OSM Data Summary: Service Address Group

OSM Business Name Description Format Source Task

Service Address:Street address

Service Address:Street address

40 A/N

Initiate Order

City

City

25 A/N

Initiate Order

State or Prov Code

State or Prov Code

2 A

Initiate Order

Zip or Postal Code

Zip or Postal Code

10 A/N

Initiate Order

Additional Description

Additional Description

50 A/N

Initiate Order


Table 11-26 OSM Data Summary: Contact Details Group

OSM Business Name Description Format Source Task

Contact Name

A contact in case a problem is encountered

30 A/N

Initiate Order

Contact Phone Number

Contact Phone Number

Phone

Initiate Order

Contact Cell Phone

Contact Cell Phone

Phone

Initiate Order


Table 11-27 OSM Data Summary: Service Details Group

OSM Business Name Description Format Source Task

Existing phone number

Existing phone number

Phone

Initiate Order

Port existing number?

Port existing number?

Lookup[Y - Yes N - No]

Initiate Order

New Number

New Number

12 A/N

Initiate Order

Current Access Provider

Current provider of local phone service [name or code number]

20 A/N

Initiate Order

Current Account number

Customer account number with ILEC

20 A/N

Initiate Order

ILEC CO CLLI

Location code of ILEC CO where local loop terminates

11 A/N

Initiate Order/Identify ILEC CO

LD Provider

Long distance provider (to set PIC in switch) [code number]

6 A/N

Initiate Order

Service Type

Business/Residential POTS [service code]

Lookup[B - Business R - Residential]

Initiate Order

Priority

Expedite/Normal

Lookup[E - Expedite N - Normal]

Initiate Order

Due date

Required in service date

Date

Initiate Order

Updated Due Date

Revised Required in service date

Date

Notify Customer of Delay


Table 11-28 OSM Data Summary: Service Features Group

OSM Business Name Description Format Source Task

Service Feature 1.12

Features required

Up to 12 entries, each consisting of: Feature identifier: Lookup [see definition below]Feature parameter 1:12 A/NFeature Parameter 2:12 A/N

Initiate Order


Table 11-29 OSM Data Summary: Assignment Details Group

OSM Business Name Description Format Source Task

No Presence

No presence at ILEC CO

Lookup [0 - False 1 - True]

Assign Port

No Capacity

Insufficient port capacity

Lookup [0 - False 1 - True]

Assign Port

Engineering Complete Date

Engineering Complete Date

Date

Wait for Engineering

Port OE or LEN

ID of port assigned

40 A/N

Assign Port

Termination Point

Identifier of IDF port where port is terminated

40 A/N

Assign Port

Switch ID

Identifier of the switch controlling the port

11 A/N

Assign Port

Switch LRN

LRN of the switch for LNP

Phone

Assign Port


Table 11-30 OSM Data Summary: LSR Details Group

OSM Business Name Description Format Source Task

LSR Sent Date

Date that LSR was sent to ILEC

Date

Send LSR

LSR Number

Local Service Request Number (provider)

18 A/N

Receive LSR Confirmation

Provider Order Number

Order Number (provider)

20 A/N

Receive LSR Confirmation

Confirmation Date

Confirmation Date Sent

Date

Receive LSR Confirmation

Provider Rep

Provider Contact Representative

15 A/N

Receive LSR Confirmation

Provider Rep. Phone

Telephone Number (of provider's rep)

Phone

Receive LSR Confirmation

Provider Due Date

Due Date

Date

Receive LSR Confirmation

Provider Estimated Date

Estimated Due Date

Date

Receive LSR Confirmation

Cutover time

Frame Due Time (cutover time)

10 A/N

Receive LSR Confirmation

Provider Bill Date

Effective Bill Date

Date

Receive LSR Confirmation

LSR Problem Identifier

Reason Code

2 A/N

Receive LSR Confirmation

LSR Problem Detail

Reason Code Jeopardy Detail

60 A/N

Receive LSR Confirmation

Provider Designer

Network Service Provider (NSP) Design/Engineering Contact

15 A/N

Receive LSR Confirmation

Provider Designer Phone

Telephone Number

Phone

Receive LSR Confirmation

Provider Circuit ID (ECCKT)

Exchange Company Circuit ID

41 A/N

Receive LSR Confirmation

Provider Loop Order Number

Loop Order Number

20 A/N

Receive LSR Confirmation


Table 11-31 OSM Data Summary: LNP Details Group

OSM Business Name Description Format Source Task

LNP Sent Date

Date that LNP request was sent to NPAC

Date

Send LNP

LNP Reference Number

LNP request reference number from NPAC

18 A/N

Receive LNP Confirmation

LNP Confirmation Date

Confirmation Received date

Date

Receive LNP Confirmation


Table 11-32 OSM Data Summary: Activation Details Group

OSM Business Name Description Format Source Task

Activation Date

Date activation was completed

Date

Activate Port.

Activation error info

Activation error returned from ASAP or IP Service Activator

60 A/N

Activate Port.


Table 11-33 OSM Data Summary: Completion Details Group

OSM Business Name Description Format Source Task

Loop Available Date

Date loop was found to be available

Date

Check for Loop Availability

LNP Activation Date

LNP activation sent date

Date

Send Activation Notice to NPAC

System Update Completion Date

System Update Completion Date

Date

Update Other Systems

Order Completion Date

Order Completion Date

Date

Order Complete


Table 11-34 OSM Data Summary: Cancellation Details Group

OSM Business Name Description Format Source Task

Cancellation Date

Cancellation Date

Date

Cancel Order

Reason for Cancellation

Reason for Cancellation

160 A/N

Cancel Order


Feature Identifier Lookup Definition

Table 11-35 lists the feature identifier lookup definitions.

Table 11-35 Feature Identifier Lookup Definition

Code Definition

3WC

Three way calling

CW

Call Waiting

CFV

Call Forward Variable

CFB

Call Forward Busy

CFD

Call Forward Don't Answer

CFR

Call Forward Remote

SC1

Speed Call 1 Digit

SC2

Speed Call 2 Digit

CNU

Caller ID Number

CNA

Caller ID Name

CBL

Caller ID Block