Property Management
Pages: [1] 2
How REALTORS Can Outsmart the Y2K Bug
What is the Year 2000 bug (or, Y2K as we call it in Geek Land) and how does it affect the real estate industry? Is the sky really falling, or is Chicken Little simply pumping up the hype? Should you delay your flight home or take all of your money out of the bank? Will everything come to a stop - or worse - on January 1, 2000? The answer depends upon how prepared you, or more accurately, your computers are for the changeover to the new millennium. If you are not sure that either of you are prepared, then read on and discover what you need to do today to outsmart this long-dormant computing bug. What exactly is the Y2K bug? In a nutshell, it is a 30-year old time-bomb that we thought we would have defused ten years ago but haven"t and only have two years before it goes off! It goes something like this: In the early days of computing, when computers had less memory than most of today"s wristwatches, software programmers had to cut corners to conserve memory for really important tasks. So they decided to leave the first two digits of the year off when recording the date. So "1970" was recorded in the computer as simply "70" and two digits worth of space was conserved. Now that might not seem like a lot of space, but consider that a date can appear again and again in millions of lines of code - say, in a program which tracks credit card transactions or weekly social security contributions. Conserving two digits each time - for trillions of transactions - really added up! As computing power expanded over the last 30 years, more features and calculations were added to the programs but nobody changed the convention of storing years in two-digit formats. In fact, because programming was so "personal," each programmer could make unique little changes as well, so large software files often became entangled with various methods of calculation - kind of like 20 different people working on the same quilt over 20 years - and the mess grew. However, nobody was concerned about the problem because everybody thought that somebody would come up with a silver bullet long before the end of the century. The flaw in this thinking, though, was that nobody did! In fact, there is no such "single solution" to the problem because there are thousands of different programs - with different programming styles inside - and there is not simply a "search and replace" feature that can update them in one single command! To further complicate the problem, the 50-something-year-olds who were programming these products thirty years ago are, well, thirty years older. Even those that are still around do not remember how they did it - or have any idea how to fix what has become a patch-work of coding since then! So the problem has become something like an archaeologist trying to decipher an ancient riddle in time to prevent a nuclear disaster in less than two years (well, not quite so dramatic, but something like that)! Okay, so there"s the problem - or part of it. Actually, the problem is not only with computers. As it turns out, computers are the easiest things to fix in this mess, if anything is going to be easy at all. Most laptops and desktops can be updated somewhat easily with software fixes downloaded from the Internet. Most word processors and spreadsheet programs are already Year 2000 "compliant." And when Windows 98 comes out, the millions of Windows 95 users will become Year 2000 compliant simply by upgrading. Yet the problem is not just inside your computer. It"s inside everything! Think about this: Almost every electronic product in our lives has "embedded chips" (sometimes thousands of chips) that control how it operates. Many of these chips are programmed to do only one thing: If this happens, then do this. For example, a simple chip in your home"s thermostat works on a simple logic that says "If the temperature drops below 65, then turn on the heating unit to raise it to 70." Sounds simple, right? Well, what if your thermostat has a chip that says "If the date is Thursday, (or Thursday, the 20th of March), at 3:30 p.m., and the temperature is below 65, then turn on the heater and raise the temperature to 70 degrees." If this is the case, your thermostat has an embedded chip that works not only conditions of the temperature but of the date and time as well! And it"s not just your thermostat that works this way. It"s your coffee pot, VCR, home alarm system, even your alarm clock that does what it does as a function of the date and time! What devices might be affected? Well, everything from your office"s sprinkler system to your car"s airbag to your heart"s pacemaker can be affected by the change to a "00" date. It"s almost impossible to list everything that might malfunction or stop altogether when the clock ticks double-zero on that fateful day. And to make matters worse - yes, they can be worse - it all might happen before the end of 1999! Not only might the millions of computers and embedded chip products go crazy on the new year, they actually might start practicing their mayhem three months ahead of schedule. How might this happen? Well, consider this little-known function of many embedded chips: If you set their date to September 9, 1999 - or 9/9/99 - they enter their "diagnostic mode" which is usually how they are tested when they are installed or during yearly checkups. Hotels set their alarm, elevator and sprinkler systems to 9/9/99 each year to make sure they work and stay in compliance with the fire code. Auto makers set air bags to 9/9/99 to test their deployment in laboratories. Even some appliance manufacturers use that date to test their systems like washing machine timers and microwave magnetrons just before they are shipped to the consumer. So come September 9, 1999, things may go up, on, and in but may never come down, off or out! And they"ll simply think it’s all a test! Keep in mind that products with embedded chips usually cannot be "upgraded" easily because their chips are programmed once and soldered into the other components. This means that many of your systems may have to be replaced and you need to plan a budget for the new items, service and down-time now! Companies are already feeling the pressure of thousands of advance orders on replacement products and parts. Some companies have already estimated that they cannot manufacture enough chips to replace their current customers" products before the year 2000 - so you may have to find an alternative product or vendor to keep your systems running. How can you find out what might happen to you and your electronics? How can you fix or upgrade them in time? And how much is all of this going to cost? There are some steps you can take away to outsmart this problem ahead of time: Take a Personal Inventory. Sit down and make three lists. First, list all of the items in your house you think might be affected by the Y2K bug. Start by listing obvious items that work with a clock or date feature, like your VCR and programmable sprinkler systems. Then list secondary items like appliances last. Each item will can checked by calling the manufacturer"s service line and asking if there are any known or anticipated problems with the product as the millennium approaches. This is going to take a lot of time, so start early! Take a Business Inventory. Make a similar list for your office paying special attention to items you take for granted every day. List items like computers (which need BIOS upgrades from the manufacturer), copy machines (they have dates that set off maintenance alert features), fax machines (it prints the date and time on each page of a fax), alarm systems (will the diagnostic mode go off on 9/9/99?) and other items. Call each manufacturer or your service representative and make sure each is compliant. If not, you are going to have to plan a budget to upgrade or replace the item. Remember, many manufacturers do not plan to take responsibility for the repairs or replacements and insurance may not cover these items either! Get online! Surf the web to each company"s homepage. Most manufacturers have a Year 2000 section on their page where you can search a database of their products and see their level of compliance. Good places to start for computers are http://www.boma.org/year2000/, http://www.microsoft.com/ithome/topics/year2k/default.htm, and http://globe.lmi.org/lmi_pbs/y2kproducts/search.htm but be sure to check the websites of each product you use - even auto makers and television companies. Remember, wherever you least expect it, there is probably a Y2K bug lurking inside your device! Plan a timeline to completion. Most companies, governments and individuals are still waiting, hoping that someone is going to come up with a silver bullet that will make all of this go away. The truth is that no such solution will ever come, so stop denying that a problem exists and start planning to outsmart the bug! Sit down with your employees and family and dive up the tasks. Plan to meet regularly to update your progress. Most importantly, make your deadline January, 1999, not December, 1999; you need to be ready to implement contingencies if possible with plenty of lead time! Plan a budget. Outsmarting the Y2K bug is going to cost money. When you identify problems, you are going to either fix or replace the items affected which will take time and money. If you do not have a budget in place, then you may not be ready to fix problems even when you find them! And set aside some contingency money as well, because you may not find all of the bugs until they strike, so you will need some quick cash to replace or repair them at the last minute! When it"s all said and done, outsmarting the Y2K problem can be less painless if you plan ahead and take steps now before you are under the stress of many systems failures. Our lives have become incredibly integrated - almost "embedded" you might say - in the chips that run the devices that make life fun, safe andPages: [1] 2