Year 2000 (Y2K) Embedded Systems & Infrastructure Problem Message Board

STOCKTALK

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor. We ask that you disable ad blocking while on Silicon Investor in the best interests of our community. If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.

Technology Stocks : Year 2000 (Y2K) Embedded Systems & Infrastructure Problem

Public Reply Prvt Reply Mark as Last Read File

Previous 10 Next 10 Previous Next

To: John Mansfield who wrote (71)	2/4/1998 1:36:00 PM
From: John Mansfield	of 618

Peter de Jager's site: Implementing a Site Review Program - also on embedded software year2000.com 'Implementing a Site Review Program to Prepare Your Organization for Y2K and Other Risks By Kathleen Tudor - ktudor@kpmg.com, 415 951-7569 ------------------------------------------------------------------------ Abstract The process of identifying threats and the risks they pose within your organization is a cost-effective way to eliminate the risk, or reduce its impact and frequency. For these reasons, the importance of performing this type of critical analysis cannot be overstated. In fact, the application of this activity should be elevated so that non-traditional threats and the risks they pose within your business operation are also identified and addressed before they adversely affect business as usual. <snip> Year 2000 Much has already been written about the implications of the upcoming millennium and the importance of ensuring that hardware and software will accommodate this important milestone. As a result, the focus for this topic is directed toward a somewhat more obscure area worth considering when engaged in Year 2000 planning. The key benefit of thinking the unthinkable is that angles not previously considered are brought into scrutiny so that ample time is available to plan for risks not previously known. One such example involves individuals addressing Year 2000 computer changes for a large financial institution. They wondered whether embedded chips would also be affected by the millennium's approach. Good thing they stopped to consider other non-traditional implications of the Year 2000. They discovered that the locking mechanism situated inside their primary safe would not allow access on January 1, 2000. Had they failed to evaluate other effects of the Year 2000 date change, they would have needed to break into their own safe. ' <snip>

Report TOU Violation

Share This Post

Public Reply Prvt Reply Mark as Last Read File

Previous 10 Next 10 Previous Next