suggestion or comment,
feel free to send
Microsoft's MSNBC Technology
miningco.com Orlando, FL.
The Miami Herald
The Dallas Morning News
Peter deJager's Year 2000
Massachusetts Institute of Technology
Robert Hilliard's Website of the World has been featured in the following publications:
Web Guide Monthly, (Sept. 1998 Issue)
Rochester Engineer, Rochester Engineering Society, (Oct. 1998)
IFMA Notes, International Facility Management Association, (Sept. 1998)
This website is best experienced with Microsoft Explorer 4.0 (or higher) or Netscape Communicator 4.04 (or higher) at 800X600 display size. Some pages are formatted in frames.
To view an article written by Robert Hilliard as seen on www.year2000.com and www.developer.com, entitled: "The Year 2000: are you a time traveler?"
A hard fast look at the Year 2000 situation is coming to light at every organization in the world. After all, 1999 is not just around the corner...IT'S HERE! Organizations are increasingly becoming aware of the Year 2000 date crisis and what they face in fixing their particular problems. The following is a list of Y2K tips that would be excellent for any organization to look at and try to incorporate in their Year 2000 remediation plans:
Contingency Plans - There is a national push in the Y2K community for completing contingency plans. These are plans outlining what will be done if failures occur on January 1, 2000. If a company cannot use their computers, what manual procedures will have to be implemented to complete everyday tasks and stay in business? Contingency plans must be thought out and documented thoroughly. Decide what time period the contingency plan will cover. Will it be from January 1, 2000 until January 14th? Maybe it will cover December 1999 through January 2000. Who will the plan cover? Employees? Vendors? What procedure will your company follow if a manual process were inacted? Will you need additional employees? Will you need additional desks, typewriters, etc.? What about utilities? Will you need a backup generator for power or an additional water source? What will you do if your business relationship partners (vendors) can't deliver the products you need to operate? A detailed plan must be created outlining every procedure your company will perform in the event of a business disruption.
Create a safety net for incoming products - It's great that you have put in motion plans to check what you already have, but what about items that are puchased and delivered that are Y2K sensitive? Are you putting up a "safety net" so to speak, to check anything that may be purchased and delivered to your door? There is talk that there are companies that are discounting products to buyers because they know they are Y2K sensitive and are not Y2K compatible. There are even companies that feel that to make their products Y2K compatible, it would cost far more than it's worth. Rumors have it that these companies plan to go out of business, then re-emerge after the year 2000 under another name. Anyone within an organization that is responsible for purchasing or receiving purchased goods must be aware of this potential problem.
Check out and replace critical equipment - The next step is to identify and check out/test any or all organization critical equipment. Run tests on any type of equipment that stores a date. Check out all of your hardware and software. Check your mainframe, your PC's, and check all miscellaneous equipment that you may not suspect could even be involved. Rule of thumb: check out equipment that is vital to the operation and cash flow of your business!
Create and distribute an organization-wide newsletter - Let's face it, the more people in your organization you get involved, the quicker you'll get things done. Let everyone be your eyes and ears. Write and distribute a company Y2K newsletter that explains what the Y2K effort is. You can list vital Y2K information including people to report Y2K concerns to. You can also list internet addresses (URL's) that a person might look up on the internet to help them better understand the Year 2000 effort.
Y2K "Trigger Dates"
Thanks to Jack Voltz of Pirate Pete's Page for the Trigger Date Counter
Other Dates To Consider...
February 6, 2040 - Early Macintosh date-and-time utility fails.
January 18, 2034 - UNIX time calendar fails.
January 1, 2046 - The system clocks on Amiga computers overflow.
January 1, 2108 - 128 years from 1980. MS-DOS calendar fails.
January 1, 10000 - Y10K problem, 4-digit year counters overflow.
January 1, 29602 - Windows NT file system fails due to date representation problems.
January 1, 29940 - Present-day Macintoshes cannot recognize date after this point.
January 1, 292271023 - Java clocks fail.