292729

DHL C-TMS

Enable Communication with Smartphone

FUNCTIONAL SPECIFICATION - 10.7

03/11/11 - 1.0
Reference: 292729 BS-8MCHDK

Client Requirement

Openfield are planning to roll out Smartphone technology to all subcontractors however before a final decision is taken on the feasibility of this concept for the business, we need to pilot the concept with our own fleet and a few owner drivers (subcontractors), It is planned the pilot should commence on the 29th November to coincide with the delivery of the Phase2 development from mubaloo. To enable this we require the following:-

1. Upgrade of Industrial Openfield instance of CTMS to send the already developed smartphone message outbound at both Carrier and Driver level when a trip is set to 'ACCEPTED' from within the OPENFIELD specific 'Carrier Trip Planning' screen
2. The Inbound POD/POC message from the smartphone requires additional tags of "Gross_Weight" "Tare_Weight" "Net_Weight" and "Weighbridge_Ticket" adding into the schema and importing into CTMS
3. The Weighbridge_Ticket will need to be mapped into the same field as the Tokairo debrief Weighbridge ticket 'ADD REF 99" the "Net_Weight" will be mapped into the "Actual Weight" field, Vehicle Reg (Tractor) and Trailer Number will need to be applied and delivery and collection times all are required to be inserted into the Openfield Order Debrief screen and order status updated to 'delivered' and trip "Completed" if all orders on the trip have been delivered and all info has validated.
4. Two new field's will need adding to CTMS to hold the "Gross Weight" and "Tare Weight" from the POD/POC, these weights are to be used for calculating overweight vehicles in the future, the prefered location of these weights would be on the order screen in the general tab near the actual delivered weight.
5. Due to how Openfield operate vehicles at a 'Carrier' level we need to put a rule into CTMS which denotes that if the number of haulage units is 1 in the resource screen for a Carrier ID that CTMS will automatically set the Tractor Unit, Trailer ID and Driver which is associated to that Carrier ID enabling the CTMS Trip xml to be sent with this detail. The planner should be prompted if they attempt to brief/set a trip to 'ACCEPTED' to a carrier with smartphone enabled and there is no vehicle level detail available.
6. Upgrade CTMS and apply all relevant parameters to ensure the smartphone functionality works including update of statuses throught the trips lifecycle.

Solution

Implementation OBS will implement an instance of the Smartphone EDI interface, configuring the necessary server, system and database setup in the Industrial test (INPF – INDTST) and production (INLV – INDPRD) environments to enable both inbound and outbound XML message processing.

Automatic Trip Resource

A new trigger point will be added to the trip creation/update process which will automatically set the Trip header resources (Tractor ID, Driver ID) and the Trip Stop resources (Trailer ID) when a Carrier ID is assigned to the trip. This will remove/update the data if a carrier is removed or changed.

The values will be set based on the master data settings in the C-TMS Resource screen:

• The Tractor ID will only be set where a single Tractor ID is setup against the particular chosen Carrier ID. If multiple Tractor IDs are linked to the carrier or no Tractor IDs are linked to the carrier then the Tractor ID will remain blank.
• The Driver ID will only be set where a single Driver ID is setup against the particular chosen Carrier ID. If multiple Driver IDs are linked to the carrier or no Driver IDs are linked to the carrier then the Driver ID will remain blank.
• The Trailer ID will only be set where a single Trailer ID is setup against the particular chosen Tractor ID populated on the rules above. If multiple Trailer IDs are linked to the Tractor ID or no Trailer IDs are linked to the Tractor ID then the Trailer ID will remain blank.

The activation of this dynamic data population will be controlled by a new C-TMS system parameter at Cost Centre level: TMS_AUTO_DEFAULT_RESOURCE.