ACE

AUTO-
CONFIG
ENGINE
 ACE TX DROP-I
PROVISIONING GUIDELINES (BPM & NETP)
Index-

1. Summary-Drop-1 activation.
2. Crammer relations
3. BPM Activation steps –New Order
4. Topology Diagram checking on NetP GUI.
5. BPM Activation steps –MACD Orders
6. Precautions while creating the order through BPM-
a. Don’t do: Wrong MACD selection ( like instead of Upgrade, downgrade selection)
b. Don’t do: Success EOR re-fire ( already Success EOR re-fired for Execution)
7. BPM Activation steps –Termination
8. BPM Activation steps –IOR- HOT
9. BPM Activation steps –IOR-MSB and EOR
10. Error handling
11. Circuit Status check and Damage Circuit correction.
12. NW Devices Upload to NetP and Verify.
13. Manual Verify operation and Post NCCM Sync up tool.
14. Current Ongoing issues of ACE-
a. Activation on ECI Serial- NBI License.
b. Early Message by NetP on Node visibility and CLR issues.
c. Manual Server trail creation between 2 UMEs for VBL NW.
d. VBL NW EOS circuit activation issues.
e. VBL NW whole upload while changes happened in some nodes.
f. Making Fibcom and Tejas nodes Un-managed through NetP.
g. TCL ECI Cross connection grouping
h. Fibcom EMAP4s, ETEX and Tejas ELAN card modeling.
i. TCL ECI intermediate optical points trace validation.
15. Post Go Live IT support and NC support.
16. Daily Circuit Activation through ACE- MIS Template
17. Daily Activation Reports and Analysis.
SUMMARY DROP-1 ACTIVATIONS:

WHAT IS DROP-1?

It is a Phase of ACE Project which covers mentioned four devices for New Order
Activation/Upgrade/Downgrade/Terminate.

a. Ciena
b. Fibcom
c. ECI
d. Tejas

WHY DO WE HAVE DROPS (PHASES) IN ACE PROJECT?

The above mentioned four devices covers nearly 90% of New Order/MACD Order, hence it is a strategic
approach to cover the maximum scenario for SDNOC.

WHAT IS NOT COVERED IN DROP-1?

 Devices like Alcatel, NEC, and Marconi.

 NCCM Orders (Shifting, Migration, etc.)
 International devices

HOW TO PROCEED THROUGH ACE IF NON-DROP-1 SCENARIOS PRESENT IN A CLR?

Need to complete those non-drop-1 devices first and then proceed through ACE

WHAT IS THE EXPECTED TIMELINES FOR GO-LIVE OF DROP-1

October 17th -2012

CRAMER RELATIONS:--

1. Issued
2. Active
3. Marked For Delete(MFD)

1. Issued: For New order, CLR relation must be in Issued State

2. Active: Once CLR is activated in network, the state changes from
Issued to Active via SET_CLR command in BPM.
3. MFD: CLR status must be in MFD before Termination. This also
happens via SET_CLR command.
Cramer provisioning status-

1. Planned in Progress(PIP)
2. Ready in Service (RIS)

1. PIP: The entire underlying layer must be in PIP for a new order
provisioning.
2. RIS: Once the order becomes active in Network, the provisioning
status changes to RIS.
NEW ORDER PROVISIONING THROUGH BPM
STEPS INVOLVED IN NEW ORDER PROVISIONING THROUGH ACE BPM:
S.NO Process Description of the Process Expected Output Probable Errors Root Cause

SERVICE Name Not Ciruit ID/Service ID

Found In Cramer is wrong
No CLR or assoicted Cramer State not
This Step checks the
object with the given Proper--
1 CHECK_CLR existence of a CLR in SUCCESS
input Issued/Active/MFD
CBOSS(Cramer)
This request can not be Underlying circuit
processed through ACE not proper- PIP/RIS
Unable to write in a BPM error- Try
Queue again
This step fetches details Need to be taken
2 GET_CLR from CBOSS SUCCESS Any Exception with CBOSS Team
Once Details are fetched
INITIATE_Create_Or from CBOSS, we Initiate
3 der order Creation
BPM will list all those
devices where manul
config is required. These
devices will be Non drop-1
devices and may be
CLAIM_Manual_Co Generic device/Cisco
4 nfiguration Router,etc.

User need to check all the

devices which implies that
COMPLETE_Manual required ccx has been
5 _Configuration done at manual devices
User need to claim this
CLAIM_Activity_Go step in order to proceed
6 Ahead for Auto-Config
This step triggers our
command to NetP for
COMPLETE_Activity actual configuration in
7 _GoAhead Network
CONFIG_Auto_Conf This step returns Config
8 iguration result SUCCESS TBD* TBD*
This step return
9 POST_VALIDATION Trace/Switching result SUCCESS TBD* TBD*

This Step changes CLR Webservice invocation Need to contact

10 SET_CLR status from Issued to SUCCESS failed CBOSS Team
Active Need to contact
JAVA Exception CBOSS Team
11 COMPLETE Order is Complete
BUCKETS IN BPM:-
DETAILED STEPS FOR NEW ORDER PROVISIONING THROUGH ACE BPM
STEP 1: CHECK_CLR

Once Order Source is selected as Metasolv, COPF ID Field becomes Mandatory and if the Order Source is
selected as Viznet , Schedule ID Field becomes Mandatory.

Rest of the options is not mandatory.

STEP 2: GET_CLR

Once Verify option is done, we get Service details (Like customer name, Customer Type and service
Type) automatically from CBOSS. We need to press SUBMIT button to complete the operation of
GET_CLR.
After selecting Submit option, search window appears, enter the circuit ID and press Search.

A list of all operations performed on that order appears with their status.
User need to select the transaction which they are working upon.

The First transaction listed above will be the latest transaction. We need to click on the link to get
details.
STEP_3: INITIATE_Create_Order and STEP4: CLAIM_Manual_Configuration

The next page which appears has Auto-refresh feature which results in GET_CLR success and INITIATE
CREATE ORDER.

This is followed by claiming the task. In The same page, all manual configurable devices will be listed out.
STEP 5: COMPLETE_Manual_Configuration
LET us see other options at this Page

STEP 6: CLAIM_Activity_GoAhead
STEP7: COMPLETE_Activity_GoAhead

STEP 8: CONFIG_Auto_Configuration & STEP 9: POST_VALIDATION

A) CONFIG SUCCESS & POST VALIDATION SUCCESS and ORDER COMPLETE

B) CONFIG SUCCESS & BUT POST VALIDATION FAILURE

Option-1 Complete manual Validation

1. Click this point

2. Complete manual post validation.

Option2: Ignore Post validation

1. Click Ignore post Validation. This will automatically check update Cramer.
2. Select the cancellation reason or select others and write the appropriate reason
3. Clicks cancel post validation.

Order will proceed to completion after above Step.

TO CHECK THE TOPOLOGY DIAGRAM THROUGH NETP GUI:

1) Go to Resource Application
2) Go to Elements and select link type as-
a) SonetSDH Circuit – both End optical
b) PDH Circuit—at least one end drop on E1/E3/DS3 drop
c) VCAT Member—at least one end Ethernet drop
3) List All
4) Select your circuit
5) Click on Topology.

We can use Advance Search option to search by Service ID.

TOPOLOGY VIEW

Topology view looks like below. This can be saved in picture format.
MACD ORDER (UG, DG) PROVISIONING THROUGH
BPM

SUCCESSFUL UPGRADE ORDER FOR HOT-UPGRADE

STEP-1 : FILL THE REQUIRED DETAILS AND SELECT THE OPERATION-UG/DG
 i) Go to MACD Request TX
ii) Enter relevant details.
iii) Select Hot upgrade/Downgrade

STEP-2:

It follows the process of—

a) SET_CLR--- Change the existing Active state in Cramer to MFD.

b) GET_CLR—Fetch the Issued CLR status from Cramer.
c) Manual Config—Claim and complete
d) Activity Go Ahead—For Auto Config
e) Post Validation—Trace / Manual Switch

ONCE ABOVE STEPS ARE COMPLETED, A USER HAS TWO OPTION TO MOVE FORWARD—

A) CONFIRM CLR DELETE –Deletes MFD CLR from Cramer (old path)
B) CANCEL CLR DELETE—Changes the Cramer state from MFD to Issued (Used for roll-back).
This will delete CLR which was in MFD state. So, old CLR will be deleted and new CLR will become Active
in Cramer.

This will not delete old CLR from Cramer. It will just change CLR status from MFD to Issued. This can be
used for roll-back operation.

COOLING-OFF PERIOD:
COOLING-OFF period is a time duration which auto-deletes CLR from Cramer after a certain time when
there is no response from user regarding Confirm CLR deletion/Cancel CLR deletion.

This value can be customized.

PRECAUTIONS: IMPORTANT DO’s AND DON’T’s

1) DO NOT Select wrong MACD option (Like Hot upgrade instead of
hot-downgrade & Vice-versa)
2) DO NOT Select wrong EOR operation(Like Insert node instead of
add node)
3) DO Make sure before performing operations like confirm CLR
delete or cancel CLR delete after Termination
4) DO Make sure before performing operation like cancel OLD CLR
delete or confirm OLD CLR delete after MACD operation.
(Upgrade/downgrade)
5) Select proper option like Ignore post validation or complete post
validation.
6) DO NOT claim a task and leave as such. Make sure to either
complete your operation or release the task.
7) Select proper option for MSB/Non-MSB
8) DO NOT Re-fire same EOR which has already been executed.
TERMINATION
IOR MSB AND HOT

1. Go to IOR RequestNew Request Tx

2. Enter the IOR no.
3. Select MSB(for MSB IOR) or Non-MSB(for HOT)
4. Click Verify

EOR REQUEST:
1. ADD NODE --- Nodes are added in a network (in Linear Topology)
2. DELETE NODE—Nodes are deleted from a network (Linear Topology)
3. INSERT NODE -- Nodes are inserted in the ring. (2 MSB Required)
4. REMOVE NODE—Nodes are removed from the ring (1 MSB Required)
5. INSERT CARD—Insert card in the Node
6. DELETE CARD--- delete Card from the NODE.
1. Go to EOR Request EOR Configuration Tx.
2. Write the EOR No.
3. Select the appropriate operation.
INSERT NODE:

Consider we have an operation for Node Insertion in a ring.

STEP-1: Select order Type as Insert Node

1. Select Insert Node

2. Select the EMS under which that node is to be inserted.

This Node is inserted in a ring. So we need to fill two MSB’s for this..

So in BPM Screen, MSB1 and MSB2 become mandatory.

1. Enter the MSB1 and MSB2 details.
2. Click verify.
3. Once Verify is done, if the entered data is correct, then MSB1 list and MSB2 List will show drop
down option of the same bearer.
STEP-2: Select both the bearers and click Submit

Now The request goes to NetP for Node Insertion.

 ERROR HANDLING DURING AUTO CONFIG

ERROR
HANDLING.xlsx
CIRCUIT STATUS CHECK AND DAMAGED CORRECTION.

1. Select the resource(SonetSDH/PDH/VCAT Member/VCAT Group).

2. This is Provisioning State—It can be Active/warning/damaged
3. Select the link to be verified.
4. Go to Verify option.
5. A Different window appears.
6. Click Apply
NETWORK DEVICES UPLOAD IN NETP DB:

1. Go to Equipment module
2. Select the node Type
3. Go to Elements Node
4. List all the nodes
5. Select the node to be uploaded.
6. Go to Upload and select the required option
A) Node_Fabric: Uploads Cards , Ports and Protection Group (MSP,BLSR)
B) Node_Fabric_Service: uploads Cards, Ports, Protection Group and CCX.
NCCM—CBOSS STEPS: TO UPLOAD CBOSS DATA TO NETP DB

http://10.209.19.174:8580/intranetV1/login.jsp?errMsg=

Follow below steps—

REPORTSIMS TASKSNODENODEWISE DUMP FOR ACE

NOW Enter those node names here which underwent changes in the
NCCM process.

Let us consider one NCCM scenario—

Existing: ABCD

Proposed: ABYZ

So the nodes involved in the change process are B,Y,Z

 Enter the node names here and click report.

Then a POP-UP Window appears which is—Validate Success nodelist dump.

Verify the results and click on GO.

AFTER THE GO COMMAND, THE CHANGES ARE IN PROCESS—

CLICK OK TO COMPLETE THE PROCESS
TYPES OF REPORTS IN BPM:
1) CONFIGURATION REPORT:
It contains fields such as-
a) Activation ID
b) Order Category (Service, IOR)
c) Order Type (New, Terminate, MACD)
d) Service/EOR/IOR ID
e) Config status (SUCCESS/FAILURE)
f) Post-validation Status (SUCCESS/FAILURE)
g) Order Initiation Date
h) Order Completion Date
i) Jeopardy Config Reason
j) Jeopardy Post-validation Reason

2) ORDER PROCESSING REPORT

It contains fields such a
a) Activation ID
b) Order Category (Service, IOR)
c) Order Type (New, Terminate, MACD)
d) Service/EOR/IOR ID
e) Manual Config Involved (Y/N)
f) Order Status (COMPLETE/IN PROGRESS/CANCELLED)
g) Config Status (SUCCESS/FAILURE)
h) Post-validation Status (SUCCESS/FAILURE)
i) Order Initiation Date
j) Order Completion Date
k) No. of Config Retries
l) No. of Post Validation Retries

3) PERFORMANCE REPORT
It contains fields such as-
a) Activation ID
 b) Order Category (Service, IOR)
c) Order Type (New, Terminate, MACD)
d) Order Initiation Date
e) Order Completion Date
f) Order Processing Time
g) Config Response Time
h) Post Validation Response Time.

4) PRODUCTIVITY REPORT
It contains fields such as-
a) Activation ID
b) Service/EOR/IOR ID
c) Order Category (Service, IOR)
d) Order Type (New, Terminate, MACD)
e) Config Status (SUCCESS/FAILURE)
f) Post-validation Status (SUCCESS/FAILURE)
g) Order Status (COMPLETE/IN PROGRESS/CANCELLED)
h) Order Initiation Date
i) Order Completion Date
j) Originator name
k) Originator group

DAILY ACTIVATION REPORT AND ANALYSIS:

ACE Go Live SD Daily ACE Order

NOC- plan of action for
Execution
smooth transition.pptx
by SDNOC- Tracker.xlsx