UBL Transportation SC

sorry i could not make the call yesterday.  I have reviewed the TSD model and think it works fine.  I note the GII has comments that  reflect the decision but not all associations have been implemented yet.  is that right? On 18/01/2011 4:07 AM, Audun Vennesland wrote: Dear Andy and Tim,   Enclosed you’ll find the latest models of the GII and TSD for discussion in tomorrow’s telecon. I have simplified the GII in order to make it more in line with how the e-Freight GII profile will look like as well as included the comments from our telecon last Friday.   Regards, Audun ------------------------------------------------------------- Audun Vennesland SINTEF ICT Software Engineering, Safety and Security 7465 Trondheim   Office: +47 73 59 29 37 Cell:     +47 92 89 44 18 Visiting address: S.P. Andersens v 15B --------------------------------------------------------------     From: Andrew Schoka [ mailto:AMSchoka@comcast.net ] Sent: 17. januar 2011 15:16 To: 'Andrew Schoka'; ubl-tsc@lists.oasis-open.org ; Audun Vennesland; 'Jan Tore Pedersen'; 'Onder, Michael (FHWA)'; dvankemmel@wanadoo.fr ; 'Henk van Maaren'; 'Kenneth Vaughn'; 'Alan Veile'; roberto@javest.com Cc: 'Tim McGrath' Subject: UBL TSC Telecon 18 Jan 2011, Tues, 0700 EST (WashDC), 1300 CET (Europe), 2000 (Perth)   AGENDA FOR UBL Transport SubCommittee Telecon   18 Jan 2011 (Tues, 1300 CET (Europe), 0700 EST (Wash DC), 2000 (Perth)   http://www.timeanddate.com/worldclock/fixedtime.html?month=01&day=18&year=2011&hour=12&min=0&sec=0  #############################################   ****** CON CALL NUMBER! ****** If possible, please use Skype     Skype: +9900827043982678      US/Canada toll-free: 1-888-350-0075     International: 201-793-9022      Conference Room Number : 3982678 then #         (applies only if calling one of the phone numbers) For screen sharing: https://www2.gotomeeting.com/join/440146818   AGENDA ITEM 1: REVIEW OF UBL 2.1 PRD02 submission Goods Item Itinerary (GII) revised (Audun can you send to this list?) Transport Service Description (TSD) revised (Audun can you send to this list?) AGENDA ITEM 2: UBL 2.1 PRD01 Issue Resolution (Attached) (see Issue spreadsheet, TSC subset) Refinement of  Transport Execution Status Refinement of Transport Operation Status Transport Library refinement (Audun) Transport Library refinement (Roberto) AGENDA ITEM 3: Other Items Regards, Andy Schoka       begin:vcard fn:Tim McGrath n:McGrath;Tim org:Document Engineering Services Ltd. email;internet:tim.mcgrath@documentengineeringservices.com title:Managing Director tel;work:+45 36 95 33 58 tel;cell:+61 438 352228 url:www.documentengineeringservices.com version:2.1 end:vcard

Tim, We discussed the GII model and Audun is working to complete the past decisions. We still need to have a comprehensive call on the TSC issues raised by Roberto and Audun. I am very tied up on other matters next week but would like to get an idea what day/time slots on the following week you could be available.. . .     From: Tim McGrath [mailto:tim.mcgrath@documentengineeringservices.com] Sent: Tuesday, January 18, 2011 10:49 PM To: Audun Vennesland Cc: Andrew Schoka; 'Jan Tore Pedersen'; 'Onder, Michael (FHWA)'; dvankemmel@wanadoo.fr; 'Henk van Maaren'; ubl-tsc@lists.oasis-open.org; 'Kenneth Vaughn'; 'Alan Veile'; roberto@javest.com ; Marianne Hagaseth Subject: Re: UBL TSC Telecon 18 Jan 2011, Tues, 0700 EST (WashDC), 1300 CET (Europe), 2000 ( Perth )   sorry i could not make the call yesterday.  I have reviewed the TSD model and think it works fine.  I note the GII has comments that  reflect the decision but not all associations have been implemented yet.  is that right? On 18/01/2011 4:07 AM, Audun Vennesland wrote: Dear Andy and Tim,   Enclosed you’ll find the latest models of the GII and TSD for discussion in tomorrow’s telecon. I have simplified the GII in order to make it more in line with how the e-Freight GII profile will look like as well as included the comments from our telecon last Friday.   Regards, Audun ------------------------------------------------------------- Audun Vennesland SINTEF ICT Software Engineering, Safety and Security 7465 Trondheim   Office: +47 73 59 29 37 Cell:     +47 92 89 44 18 Visiting address: S.P. Andersens v 15B --------------------------------------------------------------     From: Andrew Schoka [ mailto:AMSchoka@comcast.net ] Sent: 17. januar 2011 15:16 To: 'Andrew Schoka'; ubl-tsc@lists.oasis-open.org ; Audun Vennesland; 'Jan Tore Pedersen'; 'Onder, Michael (FHWA)'; dvankemmel@wanadoo.fr ; 'Henk van Maaren'; 'Kenneth Vaughn'; 'Alan Veile'; roberto@javest.com Cc: ' Tim McGrath ' Subject: UBL TSC Telecon 18 Jan 2011, Tues, 0700 EST (WashDC), 1300 CET (Europe), 2000 ( Perth )   AGENDA FOR UBL Transport SubCommittee Telecon   18 Jan 2011 (Tues, 1300 CET (Europe), 0700 EST ( Wash DC), 2000 ( Perth )   http://www.timeanddate.com/worldclock/fixedtime.html?month=01&day=18&year=2011&hour=12&min=0&sec=0  #############################################   ****** CON CALL NUMBER! ****** If possible, please use Skype     Skype: +9900827043982678      US/Canada toll-free: 1-888-350-0075     International: 201-793-9022      "Conference Room Number": 3982678 then #         (applies only if calling one of the phone numbers) For screen sharing: https://www2.gotomeeting.com/join/440146818   AGENDA ITEM 1: REVIEW OF UBL 2.1 PRD02 submission Goods Item Itinerary (GII) revised (Audun can you send to this list?) Transport Service Description (TSD) revised (Audun can you send to this list?) AGENDA ITEM 2: UBL 2.1 PRD01 Issue Resolution (Attached) (see Issue spreadsheet, TSC subset) Refinement of  Transport Execution Status Refinement of Transport Operation Status Transport Library refinement (Audun) Transport Library refinement (Roberto) AGENDA ITEM 3: Other Items Regards, Andy Schoka      

Hello TSC, I am currently working on Freight invoicing and I noted some important issues that should be solved on the Freight Invoice document. Firstly I provide some initial requirements: - A Shipment is identified by a Bill of Lading or a WayBill (for instance) - A Shipment is also associated to a Booking. - There could be more than one B/L in a single Booking. - A Freight Invoice could be: + per single B/L + a whole Booking + per Voyage Freight Invoice Issues: 1) There is just a single cac:Shipment which means we can provide a single B/L. I propose to change the cardinality of cac:Shipment from (1) to (1..n) 2) The Booking ID has not a good location yet. The FreightInvoice sample in UBL 2.1 uses the cac:InvoiceLine/cbc:AccountingCost which is not so bad but I would suggest to provide a more precise location like we have in the BillOfLading document. I propose to add in the header: cbc:CarrierAssignedID ---> Booking 3) We miss a location for the following date/time information to be associated to a ShipmentStage for a vessel carrier ATA - Actual Time Arrival ETA - Estimated Time Arrival ATD - Actual Time Departure ETD - Estimated Time Departure Actually we have just a TransitPeriod but it is not sufficient for vessel journeys. 4) Under ShipmentStage we miss a "FinalDestinationPortLocation" that is commonly used together other port codes: POL, POD, FDE *** OTHER SHIPPING RELATED ISSUES *** 5) Maritime Transport Sometimes the VesselID is not sufficient or not available. It could be useful to add the RadioCallSignCode available from ITU. 6) Road Transport Along with the LicencePlateID it could be usefult to add a "DriverName". This is a requirement on some ports. Hope this helps, Roberto -- * JAVEST by Roberto Cisternino * * Document Engineering Services Ltd. - Alliance Member * UBL Italian Localization SubCommittee (ITLSC), co-Chair * UBL Online Community editorial board member (ubl.xml.org) * Italian UBL Advisor Roberto Cisternino mobile: +39 328 2148123 skype: roberto.cisternino.ubl-itlsc [UBL Technical Committee] http://www.oasis-open.org/committees/ubl [UBL Online Community] http://ubl.xml.org [UBL International Conferences] http://www.ublconference.org [UBL Italian Localization Subcommittee] http://www.oasis-open.org/committees/ubl-itlsc [Iniziativa divulgativa UBL Italia] http://www.ubl-italia.org

Hello TSC, please remove the issue (4) as I noted that the FinalDestinationPortLocation can be already expressed with: cac:Shipment/cac:LastExitPortLocation All the other issues are existing. Cheers, Roberto > Hello TSC, > I am currently working on Freight invoicing and I noted some important > issues that should be solved on the Freight Invoice document. > > Firstly I provide some initial requirements: > > - A Shipment is identified by a Bill of Lading or a WayBill (for instance) > - A Shipment is also associated to a Booking. > - There could be more than one B/L in a single Booking. > > - A Freight Invoice could be: > + per single B/L > + a whole Booking > + per Voyage > > Freight Invoice Issues: > > 1) There is just a single cac:Shipment which means we can provide a single > B/L. > I propose to change the cardinality of cac:Shipment from (1) to (1..n) > > 2) The Booking ID has not a good location yet. The FreightInvoice sample > in UBL 2.1 uses the cac:InvoiceLine/cbc:AccountingCost which is not so bad > but I would suggest to provide a more precise location like we have in the > BillOfLading document. > > I propose to add in the header: > cbc:CarrierAssignedID ---> Booking > > 3) We miss a location for the following date/time information to be > associated to a ShipmentStage for a vessel carrier > > ATA - Actual Time Arrival > ETA - Estimated Time Arrival > ATD - Actual Time Departure > ETD - Estimated Time Departure > > Actually we have just a TransitPeriod but it is not sufficient for vessel > journeys. > > 4) Under ShipmentStage we miss a "FinalDestinationPortLocation" that is > commonly used together other port codes: > POL, POD, FDE > > > *** OTHER SHIPPING RELATED ISSUES *** > > 5) Maritime Transport > > Sometimes the VesselID is not sufficient or not available. > It could be useful to add the RadioCallSignCode available from ITU. > > 6) Road Transport > > Along with the LicencePlateID it could be usefult to add a > "DriverName". This is a requirement on some ports. > > Hope this helps, > > Roberto > > -- > * JAVEST by Roberto Cisternino > * > * Document Engineering Services Ltd. - Alliance Member > * UBL Italian Localization SubCommittee (ITLSC), co-Chair > * UBL Online Community editorial board member (ubl.xml.org) > * Italian UBL Advisor > > Roberto Cisternino > > mobile: +39 328 2148123 > skype: roberto.cisternino.ubl-itlsc > > [UBL Technical Committee] > http://www.oasis-open.org/committees/ubl > > [UBL Online Community] > http://ubl.xml.org > > [UBL International Conferences] > http://www.ublconference.org > > [UBL Italian Localization Subcommittee] > http://www.oasis-open.org/committees/ubl-itlsc > > [Iniziativa divulgativa UBL Italia] > http://www.ubl-italia.org > > -- * JAVEST by Roberto Cisternino * * Document Engineering Services Ltd. - Alliance Member * UBL Italian Localization SubCommittee (ITLSC), co-Chair * UBL Online Community editorial board member (ubl.xml.org) * Italian UBL Advisor Roberto Cisternino mobile: +39 328 2148123 skype: roberto.cisternino.ubl-itlsc [UBL Technical Committee] http://www.oasis-open.org/committees/ubl [UBL Online Community] http://ubl.xml.org [UBL International Conferences] http://www.ublconference.org [UBL Italian Localization Subcommittee] http://www.oasis-open.org/committees/ubl-itlsc [Iniziativa divulgativa UBL Italia] http://www.ubl-italia.org

Hello TSC, while testing our Freight Invoice I found further requirements. I was happy to see that the new cac:TradeFinancing under cac:PaymentMeans was perfect to describe the Letter of Credit (LC) which is exactly a trade financing instrument, anyway I noted we miss two important information to complete this precious information aggregate: cbc:IssueDate cbc:ExpireDate together they solve the minimal information requirements for an LC: LC Number --> cbc:ID LC Issuing Date --> cbc:IssueDate LC Expiry Date --> cbc:ExpireDate I propose to add both cbc:IssueDate and cbc:ExpireDate below the cbc:ID. > Hello TSC, > please remove the issue (4) as I noted that the > FinalDestinationPortLocation can be already expressed with: > > cac:Shipment/cac:LastExitPortLocation > > All the other issues are existing. > > Cheers, > Roberto > >> Hello TSC, >> I am currently working on Freight invoicing and I noted some important >> issues that should be solved on the Freight Invoice document. >> >> Firstly I provide some initial requirements: >> >> - A Shipment is identified by a Bill of Lading or a WayBill (for >> instance) >> - A Shipment is also associated to a Booking. >> - There could be more than one B/L in a single Booking. >> >> - A Freight Invoice could be: >> + per single B/L >> + a whole Booking >> + per Voyage >> >> Freight Invoice Issues: >> >> 1) There is just a single cac:Shipment which means we can provide a >> single >> B/L. >> I propose to change the cardinality of cac:Shipment from (1) to >> (1..n) >> >> 2) The Booking ID has not a good location yet. The FreightInvoice sample >> in UBL 2.1 uses the cac:InvoiceLine/cbc:AccountingCost which is not so >> bad >> but I would suggest to provide a more precise location like we have in >> the >> BillOfLading document. >> >> I propose to add in the header: >> cbc:CarrierAssignedID ---> Booking >> >> 3) We miss a location for the following date/time information to be >> associated to a ShipmentStage for a vessel carrier >> >> ATA - Actual Time Arrival >> ETA - Estimated Time Arrival >> ATD - Actual Time Departure >> ETD - Estimated Time Departure >> >> Actually we have just a TransitPeriod but it is not sufficient for >> vessel >> journeys. >> >> 4) Under ShipmentStage we miss a "FinalDestinationPortLocation" that is >> commonly used together other port codes: >> POL, POD, FDE >> >> >> *** OTHER SHIPPING RELATED ISSUES *** >> >> 5) Maritime Transport >> >> Sometimes the VesselID is not sufficient or not available. >> It could be useful to add the RadioCallSignCode available from ITU. >> >> 6) Road Transport >> >> Along with the LicencePlateID it could be usefult to add a >> "DriverName". This is a requirement on some ports. >> >> Hope this helps, >> >> Roberto >> >> -- >> * JAVEST by Roberto Cisternino >> * >> * Document Engineering Services Ltd. - Alliance Member >> * UBL Italian Localization SubCommittee (ITLSC), co-Chair >> * UBL Online Community editorial board member (ubl.xml.org) >> * Italian UBL Advisor >> >> Roberto Cisternino >> >> mobile: +39 328 2148123 >> skype: roberto.cisternino.ubl-itlsc >> >> [UBL Technical Committee] >> http://www.oasis-open.org/committees/ubl >> >> [UBL Online Community] >> http://ubl.xml.org >> >> [UBL International Conferences] >> http://www.ublconference.org >> >> [UBL Italian Localization Subcommittee] >> http://www.oasis-open.org/committees/ubl-itlsc >> >> [Iniziativa divulgativa UBL Italia] >> http://www.ubl-italia.org >> >> > > > -- > * JAVEST by Roberto Cisternino > * > * Document Engineering Services Ltd. - Alliance Member > * UBL Italian Localization SubCommittee (ITLSC), co-Chair > * UBL Online Community editorial board member (ubl.xml.org) > * Italian UBL Advisor > > Roberto Cisternino > > mobile: +39 328 2148123 > skype: roberto.cisternino.ubl-itlsc > > [UBL Technical Committee] > http://www.oasis-open.org/committees/ubl > > [UBL Online Community] > http://ubl.xml.org > > [UBL International Conferences] > http://www.ublconference.org > > [UBL Italian Localization Subcommittee] > http://www.oasis-open.org/committees/ubl-itlsc > > [Iniziativa divulgativa UBL Italia] > http://www.ubl-italia.org > > > > --------------------------------------------------------------------- > To unsubscribe from this mail list, you must leave the OASIS TC that > generates this mail. Follow this link to all your TCs in OASIS at: > https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php > > -- * JAVEST by Roberto Cisternino * * Document Engineering Services Ltd. - Alliance Member * UBL Italian Localization SubCommittee (ITLSC), co-Chair * UBL Online Community editorial board member (ubl.xml.org) * Italian UBL Advisor Roberto Cisternino mobile: +39 328 2148123 skype: roberto.cisternino.ubl-itlsc [UBL Technical Committee] http://www.oasis-open.org/committees/ubl [UBL Online Community] http://ubl.xml.org [UBL International Conferences] http://www.ublconference.org [UBL Italian Localization Subcommittee] http://www.oasis-open.org/committees/ubl-itlsc [Iniziativa divulgativa UBL Italia] http://www.ubl-italia.org

Hello TSC, This is a summary with all recent issues I catched while working on freight invoicing. The UBL release I worked on was: UBL-2.1-PRD2-20110810 I discussed all of these with Andy Shoka and I am available for any further clarification and evaluation. Best regards, Roberto -- * JAVEST by Roberto Cisternino * * Document Engineering Services Ltd. - Alliance Member * UBL Italian Localization SubCommittee (ITLSC), co-Chair * UBL Online Community editorial board member (ubl.xml.org) * Italian UBL Advisor Roberto Cisternino mobile: +39 328 2148123 skype: roberto.cisternino.ubl-itlsc [UBL Technical Committee] http://www.oasis-open.org/committees/ubl [UBL Online Community] http://ubl.xml.org [UBL International Conferences] http://www.ublconference.org [UBL Italian Localization Subcommittee] http://www.oasis-open.org/committees/ubl-itlsc [Iniziativa divulgativa UBL Italia] http://www.ubl-italia.org -- * JAVEST by Roberto Cisternino * * Document Engineering Services Ltd. - Alliance Member * UBL Italian Localization SubCommittee (ITLSC), co-Chair * UBL Online Community editorial board member (ubl.xml.org) * Italian UBL Advisor Roberto Cisternino mobile: +39 328 2148123 skype: roberto.cisternino.ubl-itlsc [UBL Technical Committee] http://www.oasis-open.org/committees/ubl [UBL Online Community] http://ubl.xml.org [UBL International Conferences] http://www.ublconference.org [UBL Italian Localization Subcommittee] http://www.oasis-open.org/committees/ubl-itlsc [Iniziativa divulgativa UBL Italia] http://www.ubl-italia.org UBL-2 1-TSC-Issues-2011-09-01.xls