Enhanced Tender Collaboration through Conditional Booking (6.3.7) Presenter: Sai Mahabhashyam Development Manager Oracle Product Development

Size: px
Start display at page:

Download "Enhanced Tender Collaboration through Conditional Booking (6.3.7) Presenter: Sai Mahabhashyam Development Manager Oracle Product Development"

Transcription

1

2 Enhanced Tender Collaboration through Conditional Booking (6.3.7) Presenter: Sai Mahabhashyam Development Manager Oracle Product Development

3 Agenda Conditional Booking (CB) Definition and Process Flow Conditional Booking Profile enhancements Online Booking/Tendering Screen enhancements Updated and New Shipment Actions Public agent Business Case Example 3

4 Conditional Booking Process Flow Conditional booking allows negotiation between the shipper and the carrier. Carrier can reply that they can accept the load with certain conditions Conditional Booking is targeted primarily at ocean bookings. It is a common practice for the service provider to send back modified information as part of the booking acceptance. 4

5 Configuring Conditional Booking OTM allows service providers to accept a tender with certain conditions. The CB Profile allows the user to determine the list of elements or fields to be shared with the carrier. 5

6 CB profile - New CB fields CFS = Container Freight Station SI = Shipping Instruction NEW New elements were added to support the ocean business segment. The generated fields allow you to specify information for conditional booking that will appear for each stop. Since there could be multiple pickup stops, the concept of generated fields was used so the user could specify pickup stop arrival and an element for pickup stop arrival stop time would be generated for all pickup stops. 6

7 CB Profile Example for Ocean Stop Times Specification

8 Online Tendering Screen - Equipment Check Digit Validation only works when check digit is entered and initial and number are in proper form Added License Plate UI Warning ISO 6346 is an international standard covering the coding, identification and marking of intermodal (shipping) containers used within containerized intermodal freight transport. Check Digit helps in determining the correctness of the container number.

9 Online Tendering Screen Shipment Fields Approved 9

10 Concept: Auto-Approval vs. Planner Approval Auto-approval Exactly same value returned by service provider Service provider value can be null treated as the same value COND_BOOK_ACCEPT_SPV_WHEN_PV_IS_NULL: Workflow parameter (existing) determines what to do with the CB fields that have null planner values Conditional Acceptance by Service provider Date fields are within the threshold set by planner No threshold for GIDs Planner will not have to review if it passes the threshold. Shipment will be updated if all CB fields pass threshold State of tender and shipment will be changed confirmed/accepted. Planner will have to review if even one case is not approved not an exact match or if values fail to meet the threshold.

11 Online tendering Screen Informational fields for Inbound data OTM does not speak EDI or EDIFACT, only XML. The translation is done in the middleware. OTM needs to provide the elements (data content) to be able to communicate shared date elements between OTM and industry partners that adopt the EDIFACT standards. Location Long Name Location Qualifier POL, Pickup, etc Transport Stage Pre-carriage, main carriage, on-carriage Time Qualifier - Arrival and Departure indicator The same EDIFACT elements are used to populate the OTM header and stop information. This is done OUTSIDE of OTM in the configuration of the MIDDLEWARE.

12 Online tendering Screen Informational fields for Inbound data These can help the planner identify the correct location for records provided by a carrier that do not match a record that should have been updated. Location Qualifier Based on EDIFACT element 3227 Time Qualifier Based on EDIFACT element 2005 Transport Stage Navigation is SHIPMENT MANAGEMENT>POWER Based on EDIFACT element DATA>QUALIFIERS>LOCATION 8051 QUALIFIER

13 Online Tendering Screen Location Alias Ocean carriers can have different names for the same location. The user has to configure the location once and enter in all of the known alias names for a location. OTM can use the alias field provided on the XML from the carrier response to determine a matching location. This is also important because carriers may not send the STOP NUMBER to match the stop related CB records

14 Location Alias Implementation This parameter can be used to help find the location ID, if the location ID is not provided by the service provider. The query will look at the location reference number for a value that matches the text string in the location alias field of the CB response.

15 Online Tendering Screen Planner s view Seq 1- Invalid stop number Seq 2- Invalid location alias Seq 3-Location ID, Stop and Alias Null Seq 4-Invalid Location ID

16 New Table: Tender_Collab Inbound_Error Planner validates record Record is removed from grid Qualifiers helpful for resolution of mismatch. Tender_Collab Inbound_Error table is updated

17 Shipment Actions - Change Schedule Action (Updated) Select Find Schedules New Re-drive section

18 Shipment Actions Re-rate and Re-drive Action (New) Re-Drive configuration allows specification of Upstream or Downstream direction based on source or destination location of current shipment.

19 Automation Public Agent and Agent Action Ocean Carriers are likely to either specify a voyage or the critical stop times but not both. OTM considers the specification of a Voyage GID as the need to either validate the planned Voyage or to change a voyage. The change voyage action is a planning action and will change the stop times. If the carrier provides stop times it is because there is no voyage Static data in OTM. OTM will simply change the stop times and not re-drive the current shipment.

20 Business Case - Ocean Scenario Case details: Freight being produced in a Dayton, OH factory is being purchased by a company in Frankfurt Germany. The transportation is being arranged with OOCL. The OTM Conditional Booking solution does not need to understand the INCO terms nor if the shipper, consignee, or broker is arranging the transportation. In this solution, OOCL offers a door to door rate where the charges for the inland freight are separate from the ocean freight. The industry refers to these inland charges as arbitrary charges as they are not the main business of the carrier. The shipment is tendered to OOCL via integration.

21 Business Case - Carrier Response 1 Ocean carrier sends in an xml with the proposed changes: -Change POL to USORF (Norfolk, VA) and the POD to NLRTM (Rotterdam, NL) -Update the Container Initial, Number, and Check Digit as well as other conditional booking fields: CONTAINER_PICKUP_LOC_GID PORT_OF_LOAD_LOCATION_GID SAIL_CUTOFF_DATE PORT_OF_DIS_LOCATION_GID PLACE_DELIVER_LOCATION_GID PICKUP_STOP_ESTIMATED_DEPARTURE POL_STOP_ESTIMATED_DEPARTURE POD_STOP_ESTIMATED_DEPARTURE PLACE_RECEIPT_LOCATION_GID SI_CUTOFF_DATE SAIL_DATE PORT_DISCHARGE_ETA CONTAINER_DELIVERY_LOC_GID POL_STOP_ESTIMATED_ARRIVAL POD_STOP_ESTIMATED_ARRIVAL DELIVERY_STOP_ESTIMATED_ARRIVAL

22 Business case - XML Snippet

23 XML is Uploaded COND_BOOK_ACCEPT_SPV_WHEN_PV_IS_NULL = true Date Threshold = 2 days The planner reviews the data on Online Booking /Tendering screen.

24

25 Correcting Errors Planner corrects a typo in the drop location name. Planner fixes the ETA at the POD and Accepts the changes.

26 CB and Shipment Status are Updated

27 Shipment Header is Updated by CB

28 Equipment and Stops are Updated

29 Rate Record and Cost are Updated (By Re-rate and Re-drive Action)

30 Carrier Response 2 The next day, ocean carrier sends in a new xml updating the Shipment Refnum with the Vessel Name.

31 CB and Shipment are Updated CB and Shipment status remain the same and modification is accepted automatically.

32 Carrier Response 3 One week after sailing, ocean carrier sends in an updated Arrival ETA at the POD as a stop time change and as a header change. ENABLE_CB_UPDATE_AFT ER_SHIPMENT_ACCEPTED: If true, OTM will evaluate the tender based on the threshold. If not within the threshold, the status will change to conditionally accepted and will need to be manually approved. Keep UI and XML in synch same behavior.

33 Planner Reviews the Changes Status changes to conditionally accepted and planner has to review the data to re-set the status.

34 34 Summary Enhanced the CB profile New shipment fields, new shipment stop fields grid Enhanced online tendering page EDI related informational fields Location Alias concept Error table for Self-help Shipment actions Change Schedule (updated), Re-rate and Re-drive (New) New public agent New workflow parameters for consistency

35 Q & A

36 Location Alias Logic Shipment ID is fetched from the itransaction number Planning parameter used while planning the shipment is found Based on location alias provided by the service provider through integration, the query will be executed For Shipment Header fields, the first record found will be considered as the Location ID and update the CB record For Stop fields, all the corresponding stop records (example: pick stop) will be validated and if a match is found that CB Stop record will be updated with the service provider value When an inbound record from the carrier that has already been translated by the middleware still does not match a record for update, the record is put into the error table. The user can make notes and check off the record. This form of self-help allows the planner to solve the problem without calling IT.

37 Threshold Definition Navigation is Business Process Automation > Agents and Milestones > Threshold Date thresholds are expressed as the number of seconds representing the day/minute/hour duration.

38 Properties These properties define when you can update the Online Booking/Tendering screen. glog.tender.avoidpickupdatecheck: This indicates if updates can be made to a tender after the tender is confirmed/accepted. Sometimes there is a need to update enroute shipments (mostly delivery date) via the conditional booking process. glog.tender.checktenderupdateableusingshipment: If updates are allowed after a tender is confirmed/accepted, this determines if the update will be based on the shipment start time instead of the tender pickup time. For this property to be used, glog.tender.avoidpickupdatecheck must be set to 'false'. If it is true, the Update button when you edit the Online Tender/Booking screen always displays. If it is false, there are two options for when updates are allowed based on the tender or the shipment and that depends on this property.

39 Agent Gates These impact whether changes can be made after a tender is confirmed.