Conference acadmy::tpas_notes

70.0. "Implementation approach" by SNOFS1::CHEUNGW (Wilson Cheung from down under DTN: 730-5106) Thu Feb 16 1995 01:35

Hi there,

Attached is am EM I sent to Eamonn about SPT TPAS II implementation 
strategy issues.  Any comments to the questions I posted are most 
welcome.

Regards,


Wilson
SPT IM&T Finance Development

                  I N T E R O F F I C E   M E M O R A N D U M

 Digital Equipment Corporation          Date:     16-Feb-1995 12:00pm AED
 (Australia) Pty. Limited               From:     Wilson Cheung
 A.C.N. 000 446 800                               CHEUNG WILSON
                                        Dept:     
                                        Tel No:   DTN 730-5106 / (02) 561-5106

TO:  Eamonn Fahy @MSO                     ( FAHY.EAMONN AT A1 at POWDML at PKO )

CC:  award::magni @vaxmail
CC:  Barbara Wilfand                      ( WILFAND.BARBARA AT A1 at POWDML at PKO )
CC:  Tracy Walker @MSO                    ( WALKER.TRACY AT A1 at POWDML at PKO )
CC:  Jeff Helman @MSO                     ( HELMAN.JEFF AT A1 at POWDML at PKO )

Subject: RE: A: TPAS changeover plan

Hi Eamonn,

Thank you for your quick reply.  I am looking forward to the table set-up 
in your test system.

Regarding to our implementation approach, we are still working on a way 
to avoid an end of month load.  It simple takes too long to run.  We 
estimate it will take around 57 hours to load all our parts and it has to 
be run during the busy month end schedule.

On the other hand, we concern about a few things if we access MTP 
on-line.

1. What is the contingent arrangement if the network is down, or TPAS is 
not available due to other system problem?  We may need the data during a 
tight closing schedule.

2. Is the system/network performance acceptable to our transaction 
processing systems?  We are now in the process of arranging the 
installation for trial.

3. We have at least three reasons of accessing MTP history.  They are (1) 
for invoice and receipt matching (12 months), (2) stock revaluation (2 
months) and (3) to answer query from local tax office (18-36 months).

I've been talking to Canada.  They can manage to get the appropriate 
information for (1) and (2) from their "CDNIW PRODT table and COPPS" 
(local systems?)  We are yet to explore our local data warehouse (SPRDW) 
further.  I am not sure how is other site handle (3) above.

Our plan is to have all the above questions answered by end of next week.  
I'll appreciate if you can give us a hand on these.

In order to learn more from other site, I am posting this EM to the TPAS 
notes conference too.  Please comment.

Regards,


Wilson

Wilson,


>> 1. What is the contingent arrangement if the network is down, or TPAS is 
>>   not available due to other system problem?  We may need the data during a 
>>    tight closing schedule.

>> 2. Is the system/network performance acceptable to our transaction 
>>    processing systems?  We are now in the process of arranging the 
>>  installation for trial.


The TPAS Logic allows you to use both PPCS and/or the Local AMPs data file.
The PPCS Software is the Part and Product Client Server, which does depend on
the network to access the APPIX Database in Salem, NH, USA. The AMPs data file
is a local RMS data file of the APPIX Database. This data file is fed 5 days
a week with parts that have been updated on the APPIX Database. The feed does 
rely on the network. If the feed is late due to the network, TPAS will not be 
effected, although the Corp Std and Corp MLP may have been changed/added for 
the few parts that are in the daily feed.

So inotherwords, unless you are planning to use PPCS soley, as a source for
Corp MLP, Corp Std Cost and TPAS Prodt Type, AND your Ship To locations require
the parts be on APPIX, then you may have a problem if the network is down.
To avoid  this, I suggest using AMPs instead of or as a backup to PPCS.

regards,
Lois