OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

ubl message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: Re: [ubl] Proposal for UBL 2.0 Extended Procurement Process Model

Dear Tim McGrath,
Thank you very much for your sending extended procurement process model.
I have read your document.
The followings are my comments.

1. My overall impressions to your proposal
- The party definitions (Section 2.1) defines Business function, Role,
Description, Example, Synonyms , Sends, and Receives. This table is arranged
well, and very understandable for readers.
- These additional business process and business documents will be necessary
for the procurement business process.

2. Comments regarding the miner mistakes (maybe), and editing issues.
(1) About the contents in the table (Page 7)
- In the line (Business function: Supplier, Role: Despatch), there is no
contents in the 'Receives' row. I think that 'Receipt Advice' should be
added in this cell.

(2) The characters of the diagram 'Fulfillment' in Page 12 are too small for
readers to read. Please make the characters more bigger.

(3) About the End Notes
The End Notes says "1 Where a customer knows-----". This note is difficult
for readers to understand where this note referring.
This note will be changed to "self billed invoice 1: Where a customer
knows-----", this would be more understandable for readers.

(4) About the Document overview (Section 3.6)
If the information of 'Submitter' and 'Receiver' will be added as a column
in this table, it would be more understandable for readers.
For example:
Document : Catalogue
Submitter: Seller Party
Receiver: Catalogue Managing Party

3. Comments regarding the next document assembly stage.
More 10 business documents will be added to the current 8 UBL business
documents. Finally, the number of UBL business documents will be 18.
Furthermore, many common reusable BIEs will be designed.
If the additional common reusable BIEs will be added to the current Reusable
BIEs (V1.0), I am afraid that the extended reusable library would become
much bigger and difficult for users to manage and reuse.
Even though these extended business processes and business documents are in
the procurement process, the common reusable BIEs would be better to be
modular to get better handling.
For example: The procurement common reusable BIEs will be categorized and
divided to the following 3 modules (spreadsheets), it would be much better
to handle.
- Sourcing common BIEs
- Ordering (and Fulfillment) common BIEs (almost same to the current
Reusable BIEs)
- Billing and Payment common BIEs

Best Regards,
Yukinori Saito
Yukinori Saito
Fuji Electric Information Service Co., Ltd. (FIS)
e-mail: saito-yukinori@fujielectric.co.jp
Tel: +81-3-5435-7333     Fax: +81-3-5435-7513

----- Original Message ----- 
From: "Tim McGrath" <tmcgrath@portcomm.com.au>
To: <ubl@lists.oasis-open.org>
Sent: Tuesday, July 05, 2005 6:53 PM
Subject: [ubl] Proposal for UBL 2.0 Extended Procurement Process Model

Please find attached the final draft of the proposed extended
procurement process model document.  This has been prepared by the UBL
European Collaboration team, comprising of participants from several
European Governments as well as the European Commission itself.  It
incorporates the updates requested after an earlier draft was presented
in April 2005.

The document describes the overall process model proposed for UBL 2.0
procurement as well as the principle of modeling Parties and their roles
in this process.

Please review this document this week as we would like to sign off its
content, add it to the UBL 2.0 Issues List and move into the design and
document assembly stage next week.

We will discuss this on this week's European/Asia working session
(Wednesday 0800 UTC) and/or you may wish to send comments directly to
the list.

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


To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail.  You may a link to this group and all your TCs in OASIS

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]