[ubl-tsc] Minutes of Transport Subcommittee Teleconference Call 7 November 2005

MHonArc v2.5.0b2 -->
















ubl-tsc message






[Date Prev]
 | [Thread Prev]
 | [Thread Next]
 | [Date Next]

--

[Date Index]
 | [Thread Index]
 | [List Home]








Subject: [ubl-tsc] Minutes of Transport Subcommittee Teleconference Call 7 November 2005




From: "Kama, Kamarudin Bin Tambi" <>
To: <>
Date: Mon, 7 Nov 2005 18:21:17 +0800














MINUTES
OF UBL-TRANSPORT SUBCOMMITTEE MEETING

0930
- 1100 (Singapore time) Monday 07 NOVEMBER
 2005

Teleconference

 

ATTENDANCE IN SINGAPORE:

   
Kama (UBL-TSC Chairperson, CrimsonLogic)

Tim McGrath (UBL Vice-Chair)

Andrew Schoka
(Information Systems Engineer (US))

Mike Onder - Team Leader Freight
Technology & Operations (USDOT-Federal Highway Administration)

Ng Chi Yuen (CECID) 

Jern-Kuan, Leong (CrimsonLogic)

 

ISSUES DISCUSSED:


 Reviewed
     Tim’s comment from 5th Nov. 
 
  Similar
      issues can be found in Bill of Lading and WayBill. 
  Insurance
      arrangement to be confirm on whether it will be required in FI. 
  Tim
      commented that abbreviation and acronyms must be spelt out in full unless
      it is in the approved list. 
  Conjunctions,
      prepositions, etc. must not be used unless it is a legitimate business
      term for example in FI, “To Order Indicator”. “To
      Order” is a business term thus the use of “To” is
      valid. 
  Shipment
      Order ID is like a number similar to the concept of PO number,
      however it is not the same as consignment identifier/UCR. 
  All
      other comments accepted and clarified. 
  CY
      will make necessary changes to the 3 documents sent.
 
 UCR,
     unique consignment reference or any other alternative business terms can
     be represented by the Identifier attribute in the consignment model. 
 Commodity
     Classification of an item can be found in the Item class. 
 Consignment
     model has not been used in the 3 documents, FI, BL and WB. Changes to
     spreadsheet of the three documents required to include Consignment. 
 
  In
      the spreadsheet file, only new components that have not been defined will
      be defined in the spreadsheet, for all other defined components, there
      would be no need to redefine them again in the spreadsheet. Document
      assembly. 
  For
      classes not used by FI, BL, WB it will be represented in the data model
      that it is not used. 
  Tim
      commented that the Denmark
      group has made use of Schematron to further verify and validate the
      validity of the XML. As the XML schema would contain the full
      Consignment, in some scenario where the Consignment model is not taken
      wholly, Schematron helped them to validate and verify the XML 
  Tim
      reiterate that consignment is not the equivalent of shipment
 
 Exchange
     rate should not be placed in allowance charges; instead it should be
     placed at a document level, if it is so required. It is often that we are
     interested in a specific instance of Exchange Rate and to be used
     throughout.
 Item
     within Shipment
 
  Jern
      Kuan mentioned that for Packing List, there is a need to include Item
      within the Shipment class.
  Tim
      commented that this is the reverse for the current common transport data
      model, where the Consignment contains the Goods Item, which in turn
      contains the Shipment component.
  Tim
      asked CrimsonLogic to propose a model to cater to the Packing List
      requirement.
 


 

ACTION ITEMS:


 CY
     to contact Ralph to gather missing definition of DTTN models. 
 CY
     to update data model based on Tim’s comment in email, and to include
     consignment into the model. CY will try to sent the updated spreadsheet to
     the list by Tuesday evening. 
 CY
     to clarify with Ralph on whether insurance will be required in FI. 
 CrimsonLogic
     to work on additional three documents based on the input gathered so far
     and to propose a model wherein the Item is contained within the Shipment
     component. 
 CrimsonLogic
     to complete/fine-tune COML data model and spreadsheet and review the need
     for the Shipment class. 
 Look
     through excel file for any other issues sent by CY for discussion on 10th
     Nov.


 

Next Meeting Schedule : 

10 NOVEMBER 2005 SGT
1000

Telephone         
: +65 67844333 

Conference
Code :  800324

 

Best Regards

Kamarudin Bin Tambi

UBL TSC Chair

 

DID: 65 – 6887 7516

Fax: 65 – 6778 5277

 

CrimsonLogic Pte Ltd 

(Regn No: 198800784N)

formerly
known as  Network Services

,
The Crimson, Singapore
117611

Main Tel: 65 - 6887 7888  

Main Fax: 65 - 6778 5277

Visit us at www.crimsonlogic.com

Makes better sense 

 

NOTICE

This eMail and any attachments are intended
solely for the named addressee(s) only. It contains confidential and/or
privileged information which should not be copied or disclosed without the
consent of the CrimsonLogic
group.  If you are not the intended recipient or if you have received this
eMail in error, you must not copy, distribute, disclose or take any action in
reliance on it (or any part of its contents).  In such case, you should
inform the CrimsonLogic group
immediately by eMail or telephone +65 68877888 (reverse charges if necessary)
and delete this eMail and any attachments from your system.

 

The integrity and security
of Internet communications and in particular this eMail and any attachments
cannot be guaranteed.  The CrimsonLogic
group accepts no liability whatsoever in
connection therewith.  You are strongly advised to carry out all necessary
virus checks and that you open this eMail and any attachments at your own risk.



 



 


















[Date Prev]
 | [Thread Prev]
 | [Thread Next]
 | [Date Next]

--

[Date Index]
 | [Thread Index]
 | [List Home]