[interdoc-y2k 315] Re: Year 2000 Virus

["Michael C. Richardson" <mcr@sandelman.ottawa.on.ca>]

>>>>> "Bob" == Bob Olsen <bobolsen@tao.ca> writes:
    Bob> Can someone explain how a system, or a computer, that is Y2K
    Bob> compliant can become Y2K corrupted by data from another computer or
    Bob> system?

  If you run a just-in-time auto-parts company and your buyer, GM, is
not y2K compliant, they might send you an order that says: send 47 red
Saturn doors by April 3, 1900. Penalty for being late is $Xk per door.

  So, you, having a nice MRP (Materials Requirements Planning) system
upon receiving the order, realizing that the order is late, drop
everything (since your other orders only have a late fee of $100/day)
and work on the GM order... Only, you could have easily met all your
orders if you'd looked more carefully at the date.

  What does this prove? 
1. your MRP system was compliant, but not resilient.
2. just-in-time manufacturing sucks
3. GIGO.

   :!mcr!:            |  Network and security consulting/contract programming
   Michael Richardson | IPsec, VPN, Firewalls, PKI, network design, Unix admin
 Personal: http://www.sandelman.ottawa.on.ca/People/Michael_Richardson/Bio.html
 Corporate: http://www.sandelman.ottawa.on.ca/SSW/
	ON HUMILITY: To err is human, to moo bovine.