[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: FW: UBL / e-procurement-review
This describes the proposal for egov-tc to review UBL.
Marion A. Royal
202.208.4643 (Office)
202.302.4634 (Mobile)
----- Forwarded by Marion A. Royal/MEB/CO/GSA/GOV on 05/13/2003 10:56 AM
-----
"Tim Benson" To: marion.royal@gsa.gov
<tb@abies.co.u cc:
k> Subject: FW: UBL / e-procurement-review
05/13/2003
02:26 AM
Marion - I am sorry you were left off the original circulation list for
this.
Tim
Tim Benson
Abies Ltd, 7 White Court, Platts Lane, London NW3 7PL
+44 (0)20 7431 6428, 078 55 68 20 37 (mob), 020 7794 2078 (fax)
tim.benson@abies.co.uk http://www.abies.co.uk
** Consultancy - Master Classes **
-----Original Message-----
From: Tim Benson [mailto:tb@abies.co.uk]
Sent: 9 May 2003 8:27
To: Jouko Salonen; david.layton@gsa.gov; arthur.brunson@gsa.gov;
tim.benson@abies.co.uk; Palle Aagaard; Michael Bang Kjeldgaard; René
Løhde; mhb@schemaworks.com; jon.bosak@sun.com; juhani.koivunen@vm.fi;
john.borras@e-envoy.gsi.gov.uk
Cc: Sue Probert; Tim McGrath; Michael Adcock; Martin Leverington; Mark
Leitch; Paul Spencer; Amabel Grant
Subject: RE: UBL / e-procurement-review
Jouko, it was good to hear you at the eGov TC meeting yesterday. I am
looking forward to working with you all on this.
Could we add one one further dimension to the admirable list you have
provided (the review team, timeline, modus operandi, meeting schedule,
workload, technical assistance, proceedings). This additional dimension is
the decomposition of the work into bite-sized pieces. My suggestion is to
use three axes: (1) dynamic behaviour (use cases), (2) static structure
(packages) and (3) complexity and context (flavours).
Each axis need sto be further subdivided and I provide some straw-man
suggestions below. For example, we could choose to work with four use
cases
(source, order, fulfillment and accounting), five packages (document,
party,
line, item, financial) and two flavours (vanilla and tutti-frutti).
Decomposition along these lines effectively divides the work into 10
compartments, which should be a lot more digestable than trying to keep it
all in one's head at the same time.
* Use Cases *
Each use case relates to a small group of document types. The four
proposed
use cases are:
(1) Source - covering catalogue information about items and prices, request
for quotation, quotation and punchout to supplier website prior to placing
a
formal order.
(2) Order - covering purchase order (new and cancel) and seller's order
response.
(3) Fulfillment - covering notification of goods despatch, delivery or
completion of service, buyer's notification of receipt and seller's
rectification advice.
(4) Accounting - covering invoices, credit and debit notes, statements and
remittance advice.
* Packages *
Each package has generic information common to all instances we are
considering with specialisations for each type of document, party etc. The
five proposed packages are:
(1) Document - general information about all documents, such as document ID
and header iniformation, as well as specialisations for each type of
document (purchase order, invoice etc).
(2) Party - common information for each party (name, address, telephone,
identifier(s)) and specialisations for each party role (order point, sales
point, invoice to etc).
(3) Line - the structure of each document line with specialisations for
different types of line used on different documents.
(4) Item - information concerning items, products, goods and services.
(5) Financial - financial and tax information, which is used at both line
and document level.
* Flavours *
The term flavour is used to avoid over-used terms such as "type" or implied
hierarchies such as "level".
(1) The vanilla flavour is the minimum neccessary to achieve the
financially
important objectives of the government as buyer (such as enabling
automation
of the three-way match of order, receipt and invoice to trigger payment),
based on the 80:20 pareto principle.
(2) Tutti-frutti (all fruits) is everything!
I hope that this helps. If we adopt a structure along these lines it will
make our (UK government) contributions easier to prepare, manage and
organise, as this is the way that we have structured our present work. It
maps quite easily to the present UBL deliverables, so we can comment on
those using this sort of framework.
Best wishes
Tim
Tim Benson
Abies Ltd, 7 White Court, Platts Lane, London NW3 7PL
+44 (0)20 7431 6428, 078 55 68 20 37 (mob), 020 7794 2078 (fax)
tim.benson@abies.co.uk http://www.abies.co.uk
> -----Original Message-----
> From: Jouko Salonen [mailto:jouko.salonen@republica.fi]
> Sent: 8 May 2003 11:59
> To: Jouko Salonen; david.layton@gsa.gov; arthur.brunson@gsa.gov;
> tim.benson@abies.co.uk; Palle Aagaard; Michael Bang Kjeldgaard; René
> Løhde; mhb@schemaworks.com; jon.bosak@sun.com; juhani.koivunen@vm.fi;
> john.borras@e-envoy.gsi.gov.uk
> Subject: UBL / e-procurement-review
>
>
>
> UBL e-procurement review team
>
> Our mission is within 6 weeks in June/july to provide a review of
> UBL libraries from the government e-procurement point of view.
>
> The review team
> The review team will consist of procurement business domain
> experts. At the moment we have identified the following individuals:
> - UK, Tim Benson - tb@abies.co.uk - mobile +44 (0) 7855682037
> - USA Arthur Brunson (GSA) (arthur.brunson@gsa.gov)
> - FINLAND One person from the Ministry of Finance in Finland
> and an other from Hansel.
> - DENMARK Mr. Mikkel Hippe Brun mhb@schemaworks.com
> - GERMANY Mr. - , ( Has contacted already John Borras, we get
> the name 8.4.2003)
> I will do the follow-up with individual participants and send the
> final name-list as soon as I have got the confirmations.
> My contact details are: Jouko Salonen,
> jouko.salonen@republica.fi, mobile +358-40-3011106.
>
> Timeline
> The UBL-library-review version is out June 2nd and the
> review-period is ending July 14th.
>
> Modus operandi
> - The review version will be distributed to the review team
> as a library of excel spreadsheets
> - The team will work in close contact to the UBL-team who is
> simultaneously during the review period finalising the UBL 1.0
> publishing. This sets an important requirement for the review
> team: We must start very intensively right from the beginning of
> the review period. If we fail to contribute right from the
> beginning, the UBL team will be overloaded in July, when they
> should do the last preparations for the final package.
>
> Meeting schedules
> - I guess the domain experts in each country would like to
> spend first a day or two with the material and use e-mail to
> discuss the best possible approach. That means, that the first
> teleconference might take place at June 4th. During this
> teleconference we could agree on the further meeting schedules.
>
> - Meeting schedule. We should be prepared for almost daily
> teleconferences. This actually doesn't look bad (assuming that
> all the meetings are by phone) because the time zones aren't that
> far apart; a meeting held 08h00-10h00 Washington time on 4th of
> June will take place 13h00-15h00 in London and 1400-1600 in
> Berlin and Copenhagen, 15h00-17h00 in Helsinki. This is quite
> decent as international collaborative efforts go.
>
> - Work load. The work of arriving at a consensus
> recommendation on points where the three governments do things
> differently will be substantial. This implies that the joint
> team will probably have to meet several times a week, perhaps
> daily, during the time allotted for the review. If we figure
> that each member will spend two hours a day on the phone and
> another two hours offline, then we are looking at a resource
> allocation of 0.5 FTE per participant for the 6-8 weeks of the project.
>
> Technical assistance:
> - I will try to work as a facilitator and provide some help
> if needed in technical/resource matters. I am familiar with the
> earlier version of the UBL-libraries and I also have a team of
> 6-7 developers who have been actively working with these issues
> several months now so they might be able to assist us in
> technical matters.
>
> Proceedings:
> - Finally we will collect a review-document. Here as well I
> will be the facilitator resource and compile a review-document
> out of the contributions made by the domain-specialists.
>
> Does this make sense? Please let me hear your opinion about the
> working model and timelines, so that we can express our
> commitment as a team.
>
> --Jouko Salonen
> CEO, Republica.fi
> www.x-fetch.com
> www.republica.fi
> GSM: +358-403011106
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]