RE: [ubl-dev] Applicability of 'Forwarding instructions' in the absence of an ordering context

["David RR Webber \(XML\)" <david@drrw.info>]

Jan,
 
Your use case below looks like a classic ship notice / delivery / receipt confirmation interaction - so those are all supported by UBL (as you'd expect of part of supply chain automation).
 
DW

"I love deadlines. I like the whooshing sound they make as they fly by". (Douglas Noel Adams 1952 - 2001, author Hitch-Hiker's Guide to the Galaxy)



-------- Original Message --------
Subject: [ubl-dev] Applicability of 'Forwarding instructions' in the
absence of an ordering context
From: Jan Algermissen <algermissen1971@mac.com>
Date: Sun, February 17, 2008 11:15 am
To: ubl-dev@lists.oasis-open.org

Hi,

(thanks so far for the thoughful responses, I'll reply to those later)

I have a use case from the car leasing domain and have a question 
regarding the applicability of UBL.

The use case is taken from the car remarketing part of the leasing 
domain: when a leasing contract ends, it is (at least in Germany) 
comman practice for the leasing customer to drop of the car at some 
location (e.g. her home address) and inform the leasing company that 
the car can be picked up.
The leasing company will then issue a request to some third party 
transport service supplier to pick up the car and deliver it to the 
company's used car parking lot.

For the collaboration between the leasing company and the transport 
service provider I would like to apply UBL processes and documents 
but I am not sure

- whether UBL's processes are applicable at all
- whether the request to the transport service supplier is an offer 
or a forwarding request
- how to best go about extending the appropriate document to provide 
the transport parameters to the
service provider (location, vehicle plate number, time of pick up 
etc.) - this seems like a general
issue when ordering services, ...yes?

There are about half a dozen other processes in the remarketing 
domain (many of them service requests)....should I generally try to 
extend the UBL or is the use case domain so different that I should 
make up my own processes and documents (maybe reusing UBL components)?

What about other areas of logistsics (coordination of service 
providers) - is UBL intended to fit or has this never been considered?

Thanks for help,

Jan




---------------------------------------------------------------------
To unsubscribe, e-mail: ubl-dev-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: ubl-dev-help@lists.oasis-open.org