Re: [ubl-dev] UBL in real life shipping web services integration

[Tim McGrath <tmcgrath@portcomm.com.au>]

Your questions highlight the fact the UBL 1.0 scenario does not encompass
the documents that flow to and from the Carrier of the goods.  Its scope
is entirely between Buyer and Seller parties.
 
 What you are doing is applying UBL to an extended use case - that involves 
document exchanges with the Carrier of the goods.  Most of the following responses
relate to this situation.  

Whilst you will find  UBL currently addresses a significant number of these
it will not satisfy all.  Therefore it would be helpful if you could formalize
this into a submission to UBL and we can discuss how they may be accommodated
into the UBL 1.1 library.
    
Konstantin vassilev wrote:
> Hi Tim,
>
> This was very useful info. I will submit proposal to the UBL but firstly I
> want to be sure I understand well all elements already defined.
>
> We have to add XML elements for:
> 1) International export - commodity codes, shipment export declarations,
> etc.
check out the Item.CommodityClassification.CommodityCode, etc al.
> 2) The case when the shipper address can be different from the address where
> we ship from.
the ship from address is not related the the shipper.  UBL 1.0 considers
the shipper is the SellerParty.
> 3) The case when the pickup address can be different from the address where
> we ship from.
Obviously at some point the goods move from the ship from to the pickup address.
UBL 1.0 considers this  as a separate ShipmentStage, where each may have
different CarrierParties each with their own Addresses.  
> 4) We need shipper contact info, pickup contact info(name, phone), consignee
> contact info
UBL 1.0 considers the shipper is the SellerParty. But depending on the TransportContract
what you term the shipper may be the FreightForwarderParty.
> 5) We need an element for email address for delivery notification
this would be Party.Contact.ElectronicMail for the relevant party, perhaps
the BuyerParty.
> 6) We need an element for Carrier Account Number for shipment, Billing, Duty
> payment. They can be different.
UBL 1.0 does not deal with payment for carrier services i,e the Bill of Lading
charges.  Its scope is only the payments between Buyer and Seller.  This
would be a new requirement for UBL 1.1.
> 7) We need an elements for Payment with credit card.
UBL PaymentMeans has CardAccount.
> I am trying to understand the meaning of the following XPath statements in
> the light of parcel shipping and wonder if they are relevant for this case: 
>
> ShipmentStage - the name is not very informative.
I suggest you refer to the schemas or the Assembly Models (in spreadsheet
form) within the /mod subdirectory of the UBL package for more details...

For example ShipmentStage is defined as "information directly relating to
a shipment stage. Goods may be shipped in stages, factory to wharf, port
to port, wharf to customers, etc."
> ActualShipment/cac:Delivery - when this is used?
Actual Shipment associates the despatch advice with actual shipment detail.
(Note that this relationship comes into play when the transaction has moved
from the order state to the delivery state.).
Delivery associates the shipment with details of a delivery. This is the
Consignor's view of the shipment  not the carriers.
> DespatchLine/cac:Delivery - when this is used?

When individual lines on an Despatch Advice have different Delivery requirements.
> DespatchLine - I suppose we can have many DespatchLine items.
> In this case this declaration has to be 
> DespatchLines/DespatchLine - instance1
> DespatchLines/DespatchLine - instance2
there is no "DespatchLines" only multiple DespatchLine types.
> DespatchLine/Item - I suppose we can have many Items.
No, each DespatchLine has one and only one Item.  That is what makes it a
separate DespatchLine - the need to identify different Items.
> Then we have to have 
> Items/Item1 - instance1
> Items/Item2 - instance2
There is no "Items" type.
> Can you give me some real world examples?
> /Request/UBLDespatchAdviceAll/ActualShipment/cac:ShipmentStage/cac:Transport
> ModeCode
"Sea","Air" (perhaps UN/EDIFACT data element  8067)
> Can you give me some real world examples?
> /Request/UBLDespatchAdviceAll/ActualShipment/cac:ShipmentStage/cac:Transport
> MeansTypeCode
"Barge","Train","Trailer","Ship", "Pipeline" (perhaps UN/EDIFACT  data element
8179)
> This element has to be used for DHL, UPS, FedEx, Etc:
> /Request/UBLDespatchAdviceAll/ActualShipment/cac:ShipmentStage/cac:CarrierPa
> rty/cac:PartyName
or perhaps the DespatchAdvice.FreightForwarderParty - depends on the Transport
Contract.
> When these elements are used:
> /Request/UBLDespatchAdviceAll/ActualShipment/cac:Delivery/cac:DeliveryAddres
> s
> and
> /Request/UBLDespatchAdviceAll/ActualShipment/cac:Delivery/cac:DespatchAddres
> s
Both DeliveryAddress and DespatchAddress may be places such as a Warehouse
or Distribution Center Dock.  The places between which goods are deemd to
be in transit.
> Package - Express Envelope, etc. - can I place this text here:
> DespatchAdvice.DespatchLine.TransportHandlingUnit.ActualPackage.ID
> I suppose ID has to be a number actually.
Sorry, you are correct.  What you neeed is a PackageType - we don't have
this (the nearest would be TransportHandlingUnit.UnitTypeCode but this is
for aggregations used for handling the packages, such as containers or sacks).
 This could be a new requirement for UBL 1.1
> But there is a carrier specific stuff such as DHL Account Number for example
> - where to place this number to?
Both  the BuyerParty and the SellerParty can have a additional PartyIdentification.ID
that denotes their account number with the carrier.
> Also some carriers need to send with the request the Shipper address, beside
> ShipTo and ShipFrom Address. Not that ShipFrom address can be different than
> the Shipper address. Where to place the Shipper Address?
> Additionally we have the following: COD (collect On Delivery), Insured Value
>
> For Billing we can have the following cases:
> Billing the shipper party - need an element for Carrier Account Number
> Billing the receiver party - need an element for Carrier Account Number
> Direct Billing to credit card - need an element for Credit Card Number
> Duty Payment for international shipments - need an element for Carrier
> Account Number
>
> Where to place the following info:
> Multiple Pieces
> Shipment Contents
> Shipment is Dutiable or not
> /Pickup/PickupDate
> /Pickup/ReadyByTime
> /Pickup/CloseTime
> /Pickup/AfterHoursClosingTime
> /Pickup/AfterHoursLocation
> PickupType/code
> PickupPlace - can be different from ShipFrom Address
> PickupContact - this can be different than Shipper Party contact
> Shipper Contact - shipper can be different than Seller Party contact
> Commodity Code - important for export
> Commodity Name- important for export
>
> Dutiable info - Declared Value, SheduleB, Export License, Terms of trade,
> etc.
> Export Declaration - Export Reason, SED number, etc.
>
> Constantine
> ExpediteBiz
> ExpediteShip.com
>
>
> -----Original Message-----
> From: Tim McGrath [mailto:tmcgrath@portcomm.com.au] 
> Sent: Monday, April 11, 2005 5:37 PM
> To: constantine@expeditebiz.com
> Cc: ubl-dev@lists.oasis-open.org
> Subject: Re: [ubl-dev] UBL in real life shipping web services integration
>
> constantine@expeditebiz.com wrote:
>
> > In this regard I am wondering if there is a document where I can see
> > the following information:
> >
> > Carrier - DHL, UPS, FedEx, USPS, etc.
> >
> >   
> DespatchAdvice.ActualShipment.ShipmentStage.CarrierParty
>
> > Services - 2Day, GROUND, etc.
> >
> >   
> For service levels this would be:
>
> DespatchAdvice.ActualShipment.PriorityLevelCode
>
> - identifies the priority or level of service required for a shipment.
>
> For scope of reponsibility (eg.  CIF, FOB, or EXW from the INCOTERMS 
> Terms of Deliver) this would be:
>
> DespatchAdvice.DespatchLine.DeliveryTerms.SpecialTerms
>
> > Package - Express Envelope, etc.
> >
> >   
> DespatchAdvice.DespatchLine.TransportHandlingUnit.ActualPackage.ID
>
> > Weight - value
> >
> >   
> the Shipment describes the Gross and Nett weights of goods shipped
>
> > Dimensions - value
> >
> >   
> the Shipment describes the Gross and Nett volume of goods shipped
>
> > DropoffType/Pickup - residence, business, etc.
> >
> >   
> DespatchAdvice.Delivery.DespatchAddress is the pickup point
> DespatchAdvice.Delivery.DeliveryAddress is the dropoff point
>
> > Payment - billing shipper, billing recipient, etc.
> >
> >   
> Shipment.TransportContract simply identifies the contract.  this would 
> determine who pays what.  For more details we would need to define the 
> payment terms for shipment.  Perhaps this is a UBL 1.1 requirement?
>
> > Declared Value - value
> >  
> >
> >   
> This has already been identified as a requirement for UBL 1.1
>
> > These are the missing tags. If you have them in the standard we can build
> >   
> our 
> > product from here.
> >
> > The tags and vocabularies are the most important part and have to be chosen
> >   
> very carefully. 
> > Our customers build interface
> > changing tags at a later phase is very expensive.
> >
> >
> >  
> >
> >   

-- 
regards
tim mcgrath
phone: +618 93352228  
postal: po box 1289   fremantle    western australia 6160

DOCUMENT ENGINEERING: Analyzing and Designing Documents for Business Informatics and Web Services
(coming soon from MIT Press)
http://mitpress.mit.edu/catalog/item/default.asp?sid=632C40AB-4E94-4930-A94E-22FF8CA5641F&ttype=2&tid=10476