Professional Documents
Culture Documents
Cost Integration
Alpesh Purohit – KSAP Technologies
Agenda
• Background
• OTMNow Tolls Cost Solution
• Solution Approach
• Integration Process Flow
• Sample Shipment with Tolls
• HERE Maps Tolls Cost API Options
• Q&A
3
Background
• OTM out of the box does not provide Tolls cost
integration
• Tolls could be a significant portion of the overall
shipment costs
• Accuracy of Match and Pay
• Auto Creation of Invoice for Voucher to Pay
4
OTMNow Tolls Cost Solution
• What Is OTMNow Tolls Cost Web Service?
– Custom Java Web Service based on KSAP OTMNow Framework
5
Solution Approach Considerations
• Business Triggers to Invoke the Tolls Cost API
• Key Business Factors that affect Tolls Cost
• Business Process / Workflow to persist Tolls Cost
• Integration Flow
• Error Handling
6
Solution Approach Considerations
• Business Triggers to Invoke the Tolls Cost API
– Tolls Cost Applicable?
– Before Tender
– After Tender Accept
– After Actuals Received
– After Delivered
7
Solution Approach Considerations
• Key Business Factors that affect Tolls Cost
– Weight / Volume
– Truck Size / Trailer Count
– Number of Axels
– Trailer Length / Width / Height
8
Solution Approach Considerations
• Business Process / Workflow to persist Tolls Cost
– Custom Status Workflow
• TOLLS_COST_REQUEST_NOT_STARTED
• TOLLS_COST_ REQUEST _IN_PROCESS
• TOLLS_COST_ REQUEST _PROCESSED
• TOLLS_COST_ REQUEST _NOT_APPLICABLE
• TOLLS_COST_ REQUEST _ERROR
– Persist Tolls Cost
• Refnums (with review / approval process to persist as Shipment Costs)
• Shipment Accessorial Costs
• Shipment Informational Costs
9
Integration Flow
• OTM à OTMNow Tolls Cost WS (Async)
– Invoke OTMNow Tolls Cost WebService
– Shipment Status à TOLLS_COST_REQUEST_IN_PROCESS
• OTMNow Tolls Cost WS à HERE Tolls Cost REST WS call (Sync)
– Receive the OTM XML and persist for tracking
– Parse OTM XML to populate HERE API Request parameters
– Invoke HERE Tolls Cost REST API
– Receive the HERE JSON Response
• OTMNow Tolls Cost WS à OTM (Async)
– Transform HERE JSON Response to OTM XML
– Post XML to OTM
– Shipment Status à TOLLS_COST_REQUEST_PROCESSED
*- WS - WebService
10
Error Handling
• OTM à OTMNow Tolls Cost WS (Async)
– Retry Mechanism
– Error Notification / Status
*- WS - WebService
11
Sample – LATAM Shipment
12
Sample – LATAM Shipment
13
Sample – LATAM Shipment
14
Sample – NA Shipment
15
Sample – NA Shipment
16
Sample – EU Shipment
17
Sample – EU Shipment
18
19
HERE Tolls Cost API
• HERE Maps Tolls Cost API Options
– A Toll Cost Extension API supports the resources outlined in the table below
Resource name Description
calculateroute.json Retrieves a cost-optimized route
Retrieves the toll cost of a route depending on the specified
tollcost.json
parameters
20
HERE Cost-Optimized Route API
• Example to find Cost-Optimized Route
– To find a cost-optimized route for a car using the fastest route, send the following
GET request
21
HERE Cost-Optimized Route API
The response to the route request includes the following high level
elements:
• Metadata about the request
• Information about the route
• Information about the toll cost calculation assumptions and results
22
HERE Cost-Optimized Route API
23
HERE Cost-Optimized Route API
Below are other important parameters supported by Cost-optimized
route API
• driver_cost • vehicleWeight
• vehicle_cost • limitedWeight
• currency • passengersCount
• tollVehicleType • tiresCount
• trailerType • commercial
• trailersCount • metricsystem
• vehicleNumberAxles • maneuverattributes
• trailerNumberAxles • routeattributes
• emissionType • combinechange
• Height • cost_optimize
• trailerHeight • detail
24
Questions?
25
Exhibit Floor Map – Booth #24
26