|
Michael: My answer to your question is that date field expansion is just as quick to implement and does not cost more than +/- 28. I understand that your situation is temporary. We have many clients who bought Focus/2000 even while they were implementing version 6.X. The reasons they did this were many and varied: 1. Their version 6.X implementation projects were taking much longer then they had expected - they discovered that they would not get "up" in time on V6 2. They began to realize that the custom portions of their systems (those not handled by BPCS) would have to be remediated for Y2K anyway - some of those custom apps would actually be retained for a number of years 3. They learned from Nexgen's references that Focus/2000 and date expansion is very quick to implement and also very thorough 4. They learned that they had the option to outsource the entire Y2K project to Nexgen or one of its distributors (including distributors in Europe) so that the client could focus its resources on the version 6.X project 5. In some cases, they learned that Nexgen's services organization could also help them get on track with their version 6.X project 6. They needed a contingency plan In fact Michael, your situation is not that uncommon -- only that you are really starting to run out of time to act. If you do not think that your version 6.1 project will complete in time you must: 1. Remediate your existing code and data with the most robust approach that can be completed in the time that is available. 2. Choose a solution and partner that is willing and able to put their arms around your entire BPCS system including modifications and custom enhancements. 3. Realize that the solution you implement must accomodate dates within interfaces outside of BPCS including EDI, CIM, queries, spreadsheets and other non-BPCS applications -- you will also have to assess Y2K readiness of those external systems 4. Don't trust anyone who says testing is not important after remediation Thanks for your question. As difficult as it may be to believe, with only three months left, there are many companies who have not yet started their Y2K remediation. Fortunately, with technology like Focus/2000, there is a reasonable chance that you and they can implement the better Y2K solution in the time remaining. |--------+-----------------------> | | "MKL" | | | <MKLBOURDIN@w| | | anadoo.fr> | | | | | | 09/16/99 | | | 11:44 AM | | | Please | | | respond to | | | BPCS-L | | | | |--------+-----------------------> >----------------------------------------------------------------------------| | | | To: BPCS-L@midrange.com | | cc: (bcc: Dan Mitchell/Nexgen) | | Subject: RE: Y2K tools for BPCS 5.1 | >----------------------------------------------------------------------------| Mitchell, I agree, the screen speaks for itself. BUT, this Y2K statment (-28 yrs) will be a TEMPORARY statment, while we are setting up a BPCS V6.1 release. So, it's a questions of few weeks, not for ever !! So, my questions were for only a temporary solution. Pls give me your ideas on this solution based on that hypothesis. Thanks, Michael. -----Original Message----- From: owner-bpcs-l@midrange.com [mailto:owner-bpcs-l@midrange.com]On Behalf Of mitchell@nexgensoftware.com Sent: mercredi 15 septembre 1999 21:23 To: BPCS-L@midrange.com Subject: Re: Y2K tools for BPCS 5.1 Michael: Since your question about +/- 28 has evolved into a discussion about the merits of that method, I feel it is only fair to present some cautions as well a very strong alternative. We at Nexgen are certainly biased toward date expansion (converting 6 digit YYMMDD to 8 digit CCYYMMDD and 2 digit YY fields to CCYY) because that is the approach we have been using for the past 3 years. With over 300 customers and conversion projects now taking as little as 3 weeks (including testing), we are confident that field expansion is both superior and as quick or quicker to implement compared to +/- 28. Refer also to an article of mine that appeared in the November 9, 1998 issue of Midrange Systems magazine regarding the drawbacks of encapsulation. http://www.nexgeninfo.com/debunk.htm A Tale of Caution: Recently, Nexgen contracted with a new services customer to "Finish their Y2K testing" that another firm had started. The other firm had been contracted to implement +/- 28 solution and also to do the testing on a "time and materials basis". Our customer finally kicked the other firm out because the testing was turning up date-related bug after bug and costing our customer thousands. Once Nexgen started the testing project, it only took a couple of days before we saw some of the horrifying results. I have XXXX'ed out proprietary information (to protect the innocent) but the following is an true screen capture that speaks for itself: ---------------------------------------------------------------------------- ----------------------------------------------------------------- ORD500-02 ##*!* XXXXXXX 3.0 Y2K LIVE SYSTEM *!*## QPADEV0006 9/01/71 Notice the system date! Revise Customer Order Entry XXXXXXXX 10:16:28 Order/Customer . XXXXX / 100316 Ship-To 1 * Store Name . . . . . . XXXXXM PRECISION XXXXXNG XXXXXM PRECISION XXXXXXXNG, INC Attention. . . . Address 1. . . . 11 XXXXX ROAD 11 XXXXX ROAD Address 2. . . . Address 3. . . . XXXXXX XXXXXXX Ste/Post/Country XX XXXX0 USA XX XXXXX0 USA Salesperson/CC . 36 * XXXN XXXXXXXX Split . . . . . * Co. / P/C . . . 20 * 100 * Default Whse . . XX XXXXXXE MASTER WAREHOUSE Customer PO . . 66869 PIC Revised date 9/01/71 Cert. . . . . . Notice Revised and Orig Dates! PIC Orig Date. . 9/01/71 Terms . . . . . 30 * Print .......... T Terms Desc. . . NET 30 Cust Tax Code . G/L Reason Code * Condition/Sale Corporate Cust . XXXXXX XXXXXX PRECISIO Credit. . . . . Order Status . . H * Credit hold Bank. . . . . . * Payment . . . . C * F1=Help F4=Prompt F5=Refresh F12=Cancel F14=Add Info F15=Ship-to Maint F16=Customer Notes F17=Order Notes F18=Ship-to Inquiry F21=Delete Order ---------------------------------------------------------------------------- ----------------------------------------------------------------- It has been an uphill struggle the entire way through this testing project. We probably won't take on another testing project where the client used +/- 28. Be warned. |--------+-----------------------> | | "Michael | | | BOURDIN" | | | <MKLBOURDIN@w| | | anadoo.fr> | | | | | | 09/13/99 | | | 01:30 PM | | | Please | | | respond to | | | BPCS-L | | | | |--------+-----------------------> >--------------------------------------------------------------------------- -| | | | To: bpcs <BPCS-L@midrange.com> | | cc: (bcc: Dan Mitchell/Nexgen) | | Subject: Y2K tools for BPCS 5.1 | >--------------------------------------------------------------------------- -| Just few questions about some Y2K tools on BPCS V5.1 1) Is there any tools that convert the Date (-28 yrs) automatically in the database ? 2) Is there some people who has already install them (and successfully test them) ? 3) How many time to setup ? Pls Answer me about this (because the Due Date of the Y2K is not discutable!). Regards. Michael. +--- | This is the BPCS Users Mailing List! | To submit a new message, send your mail to BPCS-L@midrange.com. | To subscribe to this list send email to BPCS-L-SUB@midrange.com. | To unsubscribe from this list send email to BPCS-L-UNSUB@midrange.com. | Questions should be directed to the list owner: dasmussen@aol.com +--- +--- | This is the BPCS Users Mailing List! | To submit a new message, send your mail to BPCS-L@midrange.com. | To subscribe to this list send email to BPCS-L-SUB@midrange.com. | To unsubscribe from this list send email to BPCS-L-UNSUB@midrange.com. | Questions should be directed to the list owner: dasmussen@aol.com +--- +--- | This is the BPCS Users Mailing List! | To submit a new message, send your mail to BPCS-L@midrange.com. | To subscribe to this list send email to BPCS-L-SUB@midrange.com. | To unsubscribe from this list send email to BPCS-L-UNSUB@midrange.com. | Questions should be directed to the list owner: dasmussen@aol.com +--- +--- | This is the BPCS Users Mailing List! | To submit a new message, send your mail to BPCS-L@midrange.com. | To subscribe to this list send email to BPCS-L-SUB@midrange.com. | To unsubscribe from this list send email to BPCS-L-UNSUB@midrange.com. | Questions should be directed to the list owner: dasmussen@aol.com +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
