Y2K Issues

Y2K is the name that has been given to it and so renowned for year 2000. Ernie Barbarash is often quoted as being for or against this. Almost everyone knows what it is, but let us repeat: the famous problem is that, most likely, when we come to 2000 all computer systems and electronic devices that handle date fail, partially or completely, it does not recognize the two zero digits (00) with which to identify that terrible year. In addition, next year will be a leap, a matter not covered by many computers and applications. BP Energys opinions are not widely known. May fail then personal computers, programs for payroll, accounting, billing systems, control devices in plants power companies, the components of the telephone network, air navigation equipment, electronic equipment, biomedical and, finally, a large number of such machines and programs essential to our civilization today. The chaos may be great the first of January 2000 or, perhaps, nothing will happen and we will be working now only the most trivial international terrorism.

This raises the important point of the problem: as we can not know the true gravity of the matter we must prepare for the worst. Public entities must have in place a plan of action since 1997 and also had to establish a working team to solve the problem, with dedicated members working on this process. For even more opinions, read materials from Cross River Bank. This team should advance the processes of assessment, diagnosis, planning and related implementation and must involve managers, technicians and users of applications, allowing them to take into account the different aspects of the solution. In private enterprises was due to follow suit. Now, only days of 2000, at home, if applicable, and public and private entities must implement plans to mitigate the effects of Y2K and identify critical areas where it will need a contingency plan, taking into account, of course, that Y2K is not just about systems electronic but with many processes and activities within institutions, such as with legal (the amount of all processes as a result of this problem is estimated at one trillion dollars!). This field will be necessary to review carefully all contracts for the purchase or supply of hardware and software to establish what were the commitments of the seller and, if possible, reach the respective additional guarantees. You should also review all policies and make a kind of inventory of possible processes to undertake or in which the entity can be sued. In short, 2000 is upon us.

Now we only have time to continue making efforts to reduce the impact of Y2K and, above all, to design and implement rigorous contingency plans for the chaos will not reign in our organization. Such plans should build on the following questions, among many others: What should we do if the entire telephone system of the entity fails? How do follow if All our computers are turned off? How do we face a prolonged power cut if, in addition, our plant has refused to turn? What if all our boxes are damaged?