Re: [ebxml-bp] Groups - IVI_Min-Max_Future_State_of_Execution2nd_draft_v5-Kulvantunyou-120103.doc uploaded

["Boonserm \(Serm\) Kulvatunyou" <serm@nist.gov>]

I think the major saving they are looking at is when each supplier can use
only a single IV tool to interact with all customers. Lower training cost
and personnel cost to handle with multiple IV tool is one. Others are
lowering errors and headache to remember multiple sign on and how things
work and are presented on each IV tool.

The business process looks simple but can be quite complicated when
capturing into a model. As far as I understand to this point, there are two
big biz cases - namely cumulative and discrete shipment/replenishment.
Basically, the bp involves 3 messages SyncQuantityOnHand, AdvanceShipNotice
(i.e., shipment), and ReceivedAdvice (i.e., somewhat delivery ack).
Customers update their inventory levles and Min/Max levels to suppliers
using SyncQOH. Once suppliers ship, they send the ASN. Once the customers
receive, they send the ReceivedAdvice. Customers keep update in the QOH
every certain time interval. In the cumulative case, suppliers replenish
continuously (with multiple shipment) typically based on a blanket PO (cap
by period or quantity) to maintain customer inventory b/w the Min/Max. In
the discrete case, supplier ships single shipment to replenish.

There are other business process issues regarding who and how to handle the
IV tool usage payment. Some tools charge by transaction some by monthly fee
and how to handle the sign-on.

Hope this answer some of your question,
- serm


----- Original Message ----- 
From: "David RR Webber" <david@drrw.info>
To: <ebxml-bp@lists.oasis-open.org>; <monica.martin@sun.com>
Sent: Monday, January 26, 2004 10:08 PM
Subject: Re: [ebxml-bp] Groups -
IVI_Min-Max_Future_State_of_Execution2nd_draft_v5-Kulvantunyou-120103.doc
uploaded


> Monica,
>
> I'm not sure this document is currently ready for primetime
> vis BPSS.  It raises a lot of questions as to the actual
> business solution being sought and the business
> orchestration and real collaborations IMHO.
>
> Perhaps some IV experts may be able to provide
> some insights for us here as to what might be
> significant ROI that can be garnered by improving
> the IV interoperablity across collaborating
> enterprise partners?  Information for information
> sakes is less interesting for most CFOs!
>
> The use cases show isolated events with message
> exchanges.  What is needed is to know the drivers
> and business outputs that those exchanges enable,
> so that you can create CPA and BPSS sets that
> deliver those - and then context control and
> parameters - to drive the information exchanges.
>
> I do believe we will have a better sense of this in a
> week or two following further deliberation by the
> IVI team.
>
> Anyway - right now it at least shows some parts of
> the puzzle.
>
> Thanks, DW
>
> ----- Original Message ----- 
> From: <monica.martin@sun.com>
> To: <ebxml-bp@lists.oasis-open.org>
> Sent: Monday, January 26, 2004 9:12 PM
> Subject: [ebxml-bp] Groups -
> IVI_Min-Max_Future_State_of_Execution2nd_draft_v5-Kulvantunyou-120103.doc
> uploaded
>
>
> > The document
> IVI_Min-Max_Future_State_of_Execution2nd_draft_v5-Kulvantunyou-120103.doc
> has been submitted by Monica Martin (monica.martin@sun.com) to the OASIS
> ebXML Business Process TC document repository.
> >
> > Document Description:
> > IV&I working Min/Max Replenishment document
> >
> > Scenario and use cases provided by Serm Kulvantunyou, NIST.
> >
> > Note, interesting scenarios related to late binding.
> >
> > Thanks.
> >
> >
> > Download Document:
> >
>
http://www.oasis-open.org/apps/org/workgroup/ebxml-bp/download.php/5172/IVI_Min-Max_Future_State_of_Execution2nd_draft_v5-Kulvantunyou-120103.doc
> >
> > View Document Details:
> >
>
http://www.oasis-open.org/apps/org/workgroup/ebxml-bp/document.php?document_id=5172
> >
> >
> > PLEASE NOTE:  If the above links do not work for you, your email
> application
> > may be breaking the link into two pieces.  You may be able to copy and
> paste
> > the entire link address into the address field of your web browser.
> >
> >
> >
>
>
>
>
>