ATP System Issues
1. Report for Process Exception currently requires the Demand interface Concurrent Manager ID to be
used (due to bug)
2. Table read by Demand Interface is never purged or cleaned up. As a result, records of failure will not
be purged after success has occurred. Need to clear the Demand Interface table prior to each run
somehow.
3. Process Exception Report will need to sort by Order Request Date
4. Modifications to default promise date from the schedule date after Demand Interface has occurred
once. Future changes to schedule date should not affect request Date.
ATP Process Issues
1. Who will own the decision to use product from another demand class? Under what guidelines?
2. Who will determine which orders will slip out in order to add an order to an ATP date? Under what
guidelines?
3. How can we guarantee that when Master Scheduling increases an ATP, that the order that required that
date receives it? (Hand-off issues)
4. How will DOA orders work so that they are shipped ASAP?
5. Should Customer Services be allowed to use the Buffer (DO NOT USE) demand class for any
reservations?
6. What are exact definitions of promise date, schedule date and request date? How will they be
populated?
7. How to control the use of Master Scheduling? Do Not Use/Buffer Demand Class?
Commentary: Process Issue Number 1
Responsibility for this lies entirely within Customer Service Organization for demand classes that service
customer segments. CS not allowed to move available quantity from Non-Revenue demand class without an
approval from Master Scheduling (to avoid impacting the revenue plan) or from the Buffer Demand Class.
Commentary: Process Issue Number 2
Open Issue: CS to own resolution on this
Commentary: Process Issue Number 3
Master Scheduling will change the demand class on the order and on line interface of the order if the product is available to avoid confusing communication issues (To be tested in Conference Room pilot)
Commentary: Process Issue Number 5
Elizabeth and Kevin will work on this with Master Scheduling to determine best way to handle.
Commentary: Process Issue Number 6
No
Commentary: Process Issue Number 7
Request date is customer’s requested ship from Cisco date. Promise date is the date that Cisco has committed to ship the order to the customer. Schedule Date is the date used by Manufacturing to assign ATP and to notify CS of changes to the production date once an order has been missed.