[tm-rg] Distributed ATP use case

[Haugen Robert]

This is unfinished;  I hit "send" when I meant to save a draft.
But feel free to comment anyway...

> -----Original Message-----
> From: Haugen Robert 
> Sent: Wednesday, April 13, 2005 11:05 AM
> To: tm-rg at ggf.org
> Subject: [tm-rg] Distributed ATP use case
> 
> 
> "Available To Promise" is a function or query in an order 
> processing system that determines whether the quantity of an 
> item ordered will be available at the required time.
> 
> Early versions of ATP considered only finished goods 
> inventory in one location.  Supply chain or distributed 
> versions consider also work-in-process (in manufacturing), 
> goods-in-transit, and inventory (whether finished or in 
> previous stages, that is, "in the pipeline") in many 
> locations and often controlled by many companies.
> 
> Two versions of ATP:
> 1) All available "in the pipeline" for a particular product 
> or product family, often for a defined timespan;
> 2) Sufficient to satisfy a particular demand.
> 
> ATP to satisfy a particular demand usually means "to fill a 
> customer order".  Such an ATP aggregation might want to be 
> transactional, that is, provide assurance that the 
> aggregation succeeded (completely), or that it failed 
> (completely or according to a reported pattern). "Failing 
> according to a reported pattern" in this case might mean that 
> business rules would be applied to the reported failures:  
> for example, if one supplier did not respond, but the demand 
> was satisfied anyway, it doesn't matter; if the demand was 
> not satisfied, the interaction with the supplier might be 
> retried, or tried in some other way.
> 
>