implementation of otm 6.4.1

75

Upload: prasad-chandane

Post on 20-Mar-2017

124 views

Category:

Technology


8 download

TRANSCRIPT

Page 1: Implementation of OTM 6.4.1
Page 2: Implementation of OTM 6.4.1

Implementation of OTM 6.4.1

Page 3: Implementation of OTM 6.4.1

3

Page 4: Implementation of OTM 6.4.1

4

Page 5: Implementation of OTM 6.4.1

5

Page 6: Implementation of OTM 6.4.1

Mutual Materials manufactures and distributesbrick, block, pavers and related building products

throughout the northwestern US and Canada

Page 7: Implementation of OTM 6.4.1

7

Page 8: Implementation of OTM 6.4.1

Mutual Materials• 12 Plants, 16 branches• Private Fleet plus Common Carriers

– We also do “will call” orders• Diverse customer set

– Contractors, dealers, consumers,builders

• Over 1500 “stocking” items– Manufactured and purchased– Internal orders, many are LTL

Page 9: Implementation of OTM 6.4.1

Oracle Footprint• EBS Version 12.2.5

– Financials, Supply Chain, Sales,Manufacturing, EDI

• Custom Cash / POS solution• Customized reporting• OTM• Oracle Sale Cloud

Page 10: Implementation of OTM 6.4.1

Things to consider for 6.4.1• Need of external access to an instance of

OTM for mobile app access.• Who will be using the mobile app and

understanding the setup.• How to utilize events entered in the app.

10

Page 11: Implementation of OTM 6.4.1

External OTM Site• Our friends at Hitachi Consulting have been hosting our

EBS/OTM servers for about two years now, and quicklysetup a reverse proxy connection to allow us access to OTMfrom an outside connection.

• Another option would be to have a VPN setup on the smartdevice using the mobile app and on the OTM server.

• If you can’t access your OTM instance from outside yournetwork then you won’t be able to connect a smart phone ortablet to the instance from the mobile app.

11

Page 12: Implementation of OTM 6.4.1

Intended Mobile App Users

12

The Mutual Materials Fleet

Page 13: Implementation of OTM 6.4.1

Setups in the OTM User-InterfaceThe User Role

13

Page 14: Implementation of OTM 6.4.1

Setups in the OTM User-Interface

• Access Control Lists– Mobile Application REST– Mobile Application REST Shipment

These lists can be added to specific Users,other lists, and in this case a User Role.

14

Page 15: Implementation of OTM 6.4.1

Setups in the OTM User-InterfaceThe User

15

Page 16: Implementation of OTM 6.4.1

Setups in the OTM User-InterfaceShipment Visibility

16

• Shipment must have a driver assigned

• Shipment must not have an Enroute Status of ‘ENROUTE_COMPLETED’

• Shipment must have an open or accepted tender.

Page 17: Implementation of OTM 6.4.1

Setups in the OTM User-InterfaceMobile Events

• Need to decide what kind of events adriver will be entering during his day

• Set each event to change Shipmentstatus’s accordingly

17

Page 18: Implementation of OTM 6.4.1

Setups in the OTM User-InterfaceMobile Events

18

Page 19: Implementation of OTM 6.4.1

Setups in the OTM User-InterfaceMobile Events

19

Page 20: Implementation of OTM 6.4.1

Setups in the OTM User-InterfaceMobile Events

20

Page 21: Implementation of OTM 6.4.1

Setups in the OTM User-InterfaceMobile Events

21

Custom Domain‘MM’

Public Domain

Page 22: Implementation of OTM 6.4.1

Setups in the OTM User-InterfaceMobile Events

22

Based on the ‘Departed’ event’s status and reason

codes, the corresponding shipment’s status will be

changed. The Enroute Status will be changed to

‘ENROUTE_ENROUTE’ from ‘ENROUTE_NOT STARTED’.

Page 23: Implementation of OTM 6.4.1

Setups in the OTM User-InterfaceVPD – Mobile App Visibility

Apps can be difficult to use and understand. The

VPD can help make the app more user-friendly by

limiting what’s visible to the user.

23

Page 24: Implementation of OTM 6.4.1

Setups in the OTM User-InterfaceVPD – Mobile App Visibility

24

Page 25: Implementation of OTM 6.4.1

Setups in the OTM User-InterfaceVPD – Mobile App Visibility

25

Driver’s Name is like the logged in User’s name, the Shipment Start Time is greater than orequal to today, and show less than or equal to 50 shipments.

ExternalPredicate inSQL

The SQLexplained

Page 26: Implementation of OTM 6.4.1

26

Page 27: Implementation of OTM 6.4.1

Using the Mobile App Data

• Used an agent to interact with the datafrom the Mobile App

• Used the data to change the way we planour shipments

27

Page 28: Implementation of OTM 6.4.1

Using the Mobile App DataThe Agent

Our customer’s deliveries are very important.We take advantage of any opportunity toimprove their overall experience. The newmobile app adds a new competitive edge forMutual Materials by giving us the opportunityto send real-time delivery notifications via textand email.

28

Page 29: Implementation of OTM 6.4.1

Using the Mobile App DataThe Agent - Notification

29

Page 30: Implementation of OTM 6.4.1

Using the Mobile App DataThe Agent - Notification

• Use a Tracking Agent to react to the MobileApp Events

• Based on the event entered on the mobile app,the Shipment, the Stop, the Customerassociated with the Order we send a messageto our customer’s regarding their Order.

30

Page 31: Implementation of OTM 6.4.1

Using the Mobile App DataThe Agent - Notification

• Rounds the estimated delivery time to thenearest 15 minutes.

• Includes a Project or Site/Location in themessage.

31

Page 32: Implementation of OTM 6.4.1

Using the Mobile App DataThe Agent

• The agent also re-drives all the Estimated andActual Shipment Stop Times.

• Allows the Driver to enter an event to pull theShipment off of the Driver’s view within the MobileApp, and places the Shipment into the view of aDispatcher to schedule again.

• Calculates the time early or late based on theactual against the estimated stop times.

32

Page 33: Implementation of OTM 6.4.1

Using the Mobile App DataMore Efficient Planning

• Every time a driver enters an event againsta shipment stop the action re-drives theActual Arrival/Departure times as part ofthe Tracking Agent.

• The data can be used to adjust PlanningParameters

33

Page 34: Implementation of OTM 6.4.1

Using the Mobile App DataMore Efficient Planning

34

Page 35: Implementation of OTM 6.4.1

Using the Mobile App DataMore Efficient Planning

35

Created custom actions that are linked to their own Agentsthat automatically make a shipment visible on the mobileapp and vice-versa.

Page 36: Implementation of OTM 6.4.1

Using the Mobile App DataMore Efficient Planning

Using the knowledge we’ve gained fromthe mobile app we can make changes to

the way we calculate service times in morespecific regions.

36

Page 37: Implementation of OTM 6.4.1

Tips for the Mobile AppIf using a customDomain, be sure tolog into the MobileApp using yourdomain followed byyour username, andseparated by aperiod.

37

Domain: MM Username: DSOLIS

Page 38: Implementation of OTM 6.4.1

Tips for the Mobile AppCan change an entry in the glog.properties file inthe file system to change the email address thatthe customer receives the texts/emails from.

38

Page 39: Implementation of OTM 6.4.1

39

Page 40: Implementation of OTM 6.4.1

Contact Information

Derek Solis | Business AnalystMutual Materials [email protected]

Guy DeFlorio | CTOMutual Materials [email protected]

Page 41: Implementation of OTM 6.4.1

Technical DetailsThe Agent – Agent Header

41

Page 42: Implementation of OTM 6.4.1

Technical DetailsThe Agent – Agent Header – Saved Condition

42

Page 43: Implementation of OTM 6.4.1

Technical DetailsThe Agent - Actions

43

Page 44: Implementation of OTM 6.4.1

Technical DetailsAssign Variable $DRIVER_GID

Page 45: Implementation of OTM 6.4.1

Technical DetailsAssign Variable $POWER_UNIT_GID

Page 46: Implementation of OTM 6.4.1

Technical DetailsAssign Variable $STOP_NUM

Page 47: Implementation of OTM 6.4.1

Technical DetailsAssign Variable $SHIPMENT_GID

Page 48: Implementation of OTM 6.4.1

Technical DetailsDirect SQL Update

Page 49: Implementation of OTM 6.4.1

Technical DetailsDirect SQL Update

Page 50: Implementation of OTM 6.4.1

Technical DetailsThe Agent – Actions – Saved Condition

Page 51: Implementation of OTM 6.4.1

Technical DetailsAssign Variable $LOCATION

Page 52: Implementation of OTM 6.4.1

Technical DetailsAssign Variable $ESTIMATED_ARRIVAL

52

Page 53: Implementation of OTM 6.4.1

Technical DetailsDirect SQL Update

Page 54: Implementation of OTM 6.4.1

Technical DetailsThe Agent – Actions – Saved Condition

Page 55: Implementation of OTM 6.4.1

Technical DetailsAssign Variable $BSA_NAME

Page 56: Implementation of OTM 6.4.1

Technical DetailsDirect SQL Update

Page 57: Implementation of OTM 6.4.1

Technical DetailsThe Agent – Actions – Saved Condition

Page 58: Implementation of OTM 6.4.1

Technical DetailsAssign Variable $LOCATION_DESCRIPTION

Page 59: Implementation of OTM 6.4.1

Technical DetailsDirect SQL Update

Page 60: Implementation of OTM 6.4.1

Technical DetailsThe Agent – Actions – Saved Condition

Page 61: Implementation of OTM 6.4.1

Technical DetailsThe Agent – Actions – Saved Condition

Page 62: Implementation of OTM 6.4.1

Technical DetailsAssign Variable $FUTURE_STOP_CONTACTS

Page 63: Implementation of OTM 6.4.1

Technical DetailsThe Agent – Actions – Saved Condition

Page 64: Implementation of OTM 6.4.1

Technical DetailsAssign Variable

$FUTURE_STOP_MOBILE_CONTACTS

Page 65: Implementation of OTM 6.4.1

Technical DetailsAssign Variable $DEPARTURE_TIME_DIFFERENCE

Page 66: Implementation of OTM 6.4.1

Technical DetailsDirect SQL Update

Page 67: Implementation of OTM 6.4.1

Technical DetailsDirect SQL Update

Page 68: Implementation of OTM 6.4.1

Technical DetailsThe Agent – Actions – Saved Condition

Page 69: Implementation of OTM 6.4.1

Technical DetailsAssign Variable $ARRIVAL_TIME_DIFFERENCE

Page 70: Implementation of OTM 6.4.1

Technical DetailsDirect SQL Update

Page 71: Implementation of OTM 6.4.1

Technical DetailsDirect SQL Update

Page 72: Implementation of OTM 6.4.1

Technical DetailsThe Agent – Actions – Saved Condition

Page 73: Implementation of OTM 6.4.1

Technical DetailsDirect SQL Update

Page 74: Implementation of OTM 6.4.1

Technical DetailsThe Agent – Actions – Saved Condition

Page 75: Implementation of OTM 6.4.1

Technical DetailsDirect SQL Update