Tender Notification Cutoff time

[raj73]

Hello - Can we model tender cutoff times in OTM, based on parameters like transport mode, lane and carrier. For example, FTL & LTL transport bookings (over a particular lane) need to be sent over to the carrier 2 & 1 days in advance (prior to goods pickup) respectively. Any tips would be of great help. Thanks.

[joecallan]

Re: Tender Notification Cutoff time

Look into Workflow Parameters (Business Process Automation>Power Data>Event Management>Workflow Parameters) and Milestone Templates (Business Process Automation>Agents and Milestones>Milestone Template). Using Milestone-related functionality, I believe you can setup Mandatory Time Based Constraints around Tendering based on a Shipment's Planned Departure Time.

[raj73]

Re: Tender Notification Cutoff time

Hi Joe,
I am aware of handling this using milestone templates but not very clear on the relevance of workflow paramaters here. It would be helpful if you could you please throw some light on this.
Thanks,
Raj

[joecallan]

Re: Tender Notification Cutoff time

Using Workflow Parameters, you can define how certain transport mode affect shipment execution.

Generally, in the US:

TL Shipments must be tendered to carriers (the carrier then accepts or declines the freight) and so you would use the Tender_Modes Parameter which forces the shipments to go through the tendering process

VESSEL Shipments require space on a vessel to be reserved and so you would use the Booking_Modes Parameter which forces shipments to go through the booking process

LTL Shipments only require a pickup notification to be sent to the carrier (LTL carriers never decline freight) so you would use the Auto_Modes Parameter which tells OTM to skip the tendering process

I am not sure if this functionality is revelevant to you...just wanted to make you aware of it.

[raj73]

Re: Tender Notification Cutoff time

Hi Joe,

I was trying to define a milestone template that has a monitor getting assigned upon shipment creation with a time-based milestone that expires 5 minutes before planned arrival on 1st stop and sets indicator to green.

I have used only 1 execution milestone which listens on a time based event with Based-On dates & time offsets defined there-in. I have 'Monitor event' and 'Perform action' checks in place on both assignment and execution milestones.

In theory, this appears to be quite simple and straight-forward but it doesnt work in our instance 5.5CU3.
Do you think this could be related to the instance or am I missing any configuration for setting up Time-Based monitoring.

I have attached an excerpt from the log below. Any tips would be of immense help.

.....Starting Profile.... [SCEM - 1]
MonitorProfile=CUST1.00055 [SCEM - 1]
MXA=CUST1.00055_EXECUTION_AGENT [SCEM - 1]
EventTopic=MonitoredShipmentTimeBasedEvent: shipment=CUST1.01310, monitorAgent=CUST1.00076 [SCEM - 1]
isProfileEvent =false [SCEM - 1]
Unsubscribing <CUST1.EXECUTE_GREEN58/context=/agent=CUST1.EXECUTE_GREEN58/event=(class=glog.server.workflow.lifetime.monitor .shipment.MonitoredShipmentTimeBasedEvent/param=LifeTimedomain=CUST1)/queue=CUST1.SET_TIMEBASED_INDICATORS: CUST1.01310 | 2)/monitorAgent=CUST1.00076> from <(class=glog.server.workflow.lifetime.monitor.ship ment.MonitoredShipmentTimeBasedEvent/param=LifeTimedomain=CUST1)/queue=CUST1.SET_TIMEBASED_INDICATORS: CUST1.01310 | 2)> [SCEM - 1]

Thanks,
Raj