I havent used 7000 since 1999 but I would use a similar method to John but their could now be an even quicker way of doing this. You should be able to export your data. If you cant do this straight to P3 or MSP then the last method is Excel.
MSP provides an excel template to import into mSP. then cut and paste your export file from A7 to this template. Import this into MSP and then finally export and import into P3. There are plenty of dicussion threads on this latter method.
Member for
20 years 9 months
Member for20 years10 months
Submitted by John Frantzen on Wed, 2007-01-24 21:52
Artemis 7000?! I used 7000 back in the early 1990s (and 6000 throughout the the 1980s). Those were the good ol days.
How big is your network? If your network is large, then it is worth trying to migrate things electronically. If it is small, a manual key-job might be more efficient time-wise (really!).
If your A7000 system has a relatively flexible back-end (like the traditional Artemis systems) then it should not be too much of a problem. The relationship table will be the most difficult (as usual). You need to get your data out to a flat file and then use Excel or text editors and do some horsing around.
Strategy-wise, it might be even be easier to first get the 7000 data into MS Project brute force (copy/paste) since Project is typically "happier" accepting external data than Primavera/SureTrak. Then save the MPP as an MPX, open in SureTrak, save to Concentric, and then open w/P3 (Im talking "old" P3/ST). Seems like there would likely be more difficulty jamming your data into P5 (Contractor) than going the flat file and cut/paste route. But again, the relationships are tricky. Tough nut to crack.
Flat file wise... you could use PRMBATCH. With maybe 3 or 4 export files, you should be able to get the A7000 data into something semi-usable that you can start tweaking for PRMBATCH. With PRMBATCH youll need a good text editor since PRMBATCH is column-oriented, but at least youll be able to load the logic straight away (assuming A7000 can export relationships in some rational manner). The old P3 manuals (and the CD, I believe) have the batch file definition laid-out. It will take some tinkering. Again, data volume must be considered. Boy, this is really old fashioned. Just like we used to do it in the stone ages.
IMO it would be easier to do your data XFER on the "old side" of P3 since I am an old dog (just now getting into v5.0 and not overly thrilled with what Im seeing) and also Im not sure how restrictive the v5.0 SQL back end might be. If you attempt to go the "direct" route (DB to DB, youd need to be a super good DB jock to take the A7000 data into v5.0 via the back door (again, I dont know how tight they bolt the doors). And of course the s/w has all sorts of sanity checks during data entry that you would be bypassing. Youd need the v5.0 DB def.
Member for
19 years 5 monthsRE: Artemis 7000 to P3 conversion
I havent used 7000 since 1999 but I would use a similar method to John but their could now be an even quicker way of doing this. You should be able to export your data. If you cant do this straight to P3 or MSP then the last method is Excel.
MSP provides an excel template to import into mSP. then cut and paste your export file from A7 to this template. Import this into MSP and then finally export and import into P3. There are plenty of dicussion threads on this latter method.
Member for
20 years 9 monthsRE: Artemis 7000 to P3 conversion
Neil...
Artemis 7000?! I used 7000 back in the early 1990s (and 6000 throughout the the 1980s). Those were the good ol days.
How big is your network? If your network is large, then it is worth trying to migrate things electronically. If it is small, a manual key-job might be more efficient time-wise (really!).
If your A7000 system has a relatively flexible back-end (like the traditional Artemis systems) then it should not be too much of a problem. The relationship table will be the most difficult (as usual). You need to get your data out to a flat file and then use Excel or text editors and do some horsing around.
Strategy-wise, it might be even be easier to first get the 7000 data into MS Project brute force (copy/paste) since Project is typically "happier" accepting external data than Primavera/SureTrak. Then save the MPP as an MPX, open in SureTrak, save to Concentric, and then open w/P3 (Im talking "old" P3/ST). Seems like there would likely be more difficulty jamming your data into P5 (Contractor) than going the flat file and cut/paste route. But again, the relationships are tricky. Tough nut to crack.
Flat file wise... you could use PRMBATCH. With maybe 3 or 4 export files, you should be able to get the A7000 data into something semi-usable that you can start tweaking for PRMBATCH. With PRMBATCH youll need a good text editor since PRMBATCH is column-oriented, but at least youll be able to load the logic straight away (assuming A7000 can export relationships in some rational manner). The old P3 manuals (and the CD, I believe) have the batch file definition laid-out. It will take some tinkering. Again, data volume must be considered. Boy, this is really old fashioned. Just like we used to do it in the stone ages.
IMO it would be easier to do your data XFER on the "old side" of P3 since I am an old dog (just now getting into v5.0 and not overly thrilled with what Im seeing) and also Im not sure how restrictive the v5.0 SQL back end might be. If you attempt to go the "direct" route (DB to DB, youd need to be a super good DB jock to take the A7000 data into v5.0 via the back door (again, I dont know how tight they bolt the doors). And of course the s/w has all sorts of sanity checks during data entry that you would be bypassing. Youd need the v5.0 DB def.
JF