1

Leveraging Milestone Monitors for Visibility at Cisco

By

Kevin Franklin

Anuj Garg

Sree Guru

2

Agenda

• Milestone Templates

• Milestone Monitors

• Cisco Business Process related to Milestone

• Implementation of Milestone Monitors at Cisco

3

Milestone Template

Milestone Template Role

• Controls the creation of milestone monitors and the types of business objects

that are assigned to the monitors

• These milestones control how the system monitors specific events and

performs actions for a business object

Milestone Template Contains

• Assignment criteria determines which Milestone template gets

assigned to the Business object (Order / Shipment) and also in what

event it gets assigned.

• Milestones that determine the events to monitor, actions to take in

response, and various other processing attributes

4

Usefulness of Milestones

When are Milestones useful?

• Business configurable Inter-event dependencies are to be considered,

e.g. sequencing and time expiration

• Specification of mandatory events

• Specification of the completion of a chain of events to enable

handling of missing mandatory events

• Notification escalations

5

Milestone Template – An example

6

Milestone Monitors

What are Milestone monitors?

• A milestone monitor is a copy of a milestone template that attaches to a

business object and then monitors it.

For example, a milestone template may be defined to monitor sequence of events

occurring at the Order Release and monitor the time elapsed before an event occurs

at the Order Release level.

When a new order release is approved, by approving the shipments assigned to the

order release, the system creates a copy of that milestone template and attaches the

copy to the approved order release. The copy is called a milestone monitor. The

milestone monitor is what monitors the events taking place at the order release level.

One milestone template can assign milestone monitors to several order releases

depending on the assignment criteria. A milestone template can be used again and

again.

7

Assignment Criteria of Milestone Template

8

Assignment Criteria of Milestone Template – Saved Condition

9

Cisco Business Process

• Different Contract Manufacturers (CM) called Orgs serve Cisco’s end customers

• Each Org is responsible for transporting goods depending on a specific route.

• Different route codes are possible. These are listed below:

a) A -> CM to Origin SLC* to End Customer

b) B -> CM to End Customer

c) C-> CM to Destination SLC to End Customer

d) D-> CM to Origin SLC to Destination SLC to End Customer

• Order Release received into OTM and is routed based on the route code.

• Order Release after routing is sent again into OTM in the form of a Delivery that

needs to be tracked from the SLC (Origin or Destination) to the End Customer or

from CM to End Customer.

• This Delivery on approval in OTM is assigned to the Milestone Template to form a

Milestone Monitor * SLC is a Distribution Center for Cisco

10

Cisco Business Process

SLC/CM Destination

Gateway Customer

Wheels Up

1 4

Customs Clearance

Delivered to Customer

Shipment 1 Shipment 2

3

2 Wheels Down

• Ensure that sequence of milestone is validated

• Ensure that the time based SLA between

milestones are met

36 hrs. 36 hrs.

5 hrs. 4 hrs.

Sent by Carrier 1

Sent by Carrier 1 or Carrier 2

11

Cisco Business Process

Cisco Terms RNET

Code RNET Description

WHEELSUP - when the plane has taken off with the

shipment from the origin airport (where customs was

cleared) and is in flight to the destination airport;

DDP Departed/Aircraft departure.

WHEELS DOWN - Aircraft has landed in the destination

airport AAV Arrival / Aircraft Arrival

CLEARED IMPORT CUSTOMS - when the shipment has

cleared Customs of the destination CRF Customs/Released from customs.

DELIVERED TO CUSTOMER - when the carrier has

handed the shipment over to the customer including

delivered to customers broker/carrier

DAS Delivered/Receiver acknowledges receipt.

12

Cisco Business Process

OTM EBS

Partner

Systems

3B3 / 3B2 Status

message

OTM

Sequence Validation &

Time based monitoring

3B3 Milestone Details Post shipment

event management

for downstream application

Applying milestone templates based on lanes

Listen to the events and perform out of sequence

validation

Milestone monitors to listen and validate if the service

level agreement (SLA) meets or not

Sends notification to carrier for non compliance

Sends information to EBS on milestone events

TIBCO

TIBCO

EBS

13

Implementation of Milestones Milestone Template assignment

Plan Order Release Approve Shipments Assign Monitor

Template on Order Release

Agent to check if Monitor Template has been applied

on the Order, and send e-mail if

required.

3B3/3B2 status messages from

EBS

Event creation & trigger milestone based on status

code

Sequence Validation

followed by time based SLA for the

subsequent milestone is

validated

Send valid message /

sequence & SLA validation error

notification

Processing of Milestone event

14

Implementation of Milestones

When Order gets created in OTM, order release refnum is populated

with lane and Biz entity

15

Implementation of Milestones On Order status changed to approved, Milestone template is assigned

Saved condition in Assignment Criteria of the Milestone template refers the same Order

Release Refnum to constrain the template being attached to the Order Release.

16

Implementation of Milestones Milestone Template

17

Implementation of Milestones

Milestone event for

ship confirm

Set Ups – Sequence Validation

Next Milestone – Wheels up

18

Implementation of Milestones Set Ups – Sequence Validation

19

Implementation of Milestones Set Ups – SLA validation

20

Implementation of Milestones Sample Order Release with Events

THANK YOU

For Further details please reach out to the following:

Kevin Franklin: Kevinfra@cisco.com

Anuj Garg : Anuj_Garg05@infosys.com

Sree Guru: Sree_Sankaran@infosys.com