| To: C.K. Houston who wrote (960) | 1/24/1998 12:26:00 AM |
| From: Josef Svejk | of 9818 |
| |
Humbly report, All, "Where the rubber meets the road":
_____________________
From: "Pittelkau, Harlan" <HarlanP@DIS.WA.GOV>
To: "'Y2K Esofta'" <y2k@esofta.com>
Subject: Where the rubber meets the road
Date: Fri, 23 Jan 1998 14:23:07 -0800
The basic issue with remediation of Year 2000 problems in general but
especially in the Non-IT or embedded microprocessor/controller
environment is to mobilize the right group of people to identify and fix
specific problems. Debate about theoretical issues doesn't matter a
whit to the operating engineer or repairperson involved in maintaining
plant infrastructure or transmission system(s). Every one of them needs
to know which component to replace to remain operational.
Understanding that automation, inclusive of all computerized devices in
the plant is often unique to the operating environment, is the first
step in the realization that the person who is involved with every
component in the process must be a participant in the remediation
process. Anyone working outside the process is going to have to spend a
tremendous amount of time in learning what the repairman already knows
before they can even begin to inventory the devices performing date
functions. The more distributed the systems components are, the more
people there are who are involved in its maintenance.
Since automation exists in virtually every academic discipline and has
become necessary as tools for production of work, anyone involved in
tool usage is involved in Year 2000 issues in some manner. There exists
a major shortcoming in communicating information about year 2000 issues
in assembly line produced consumer type systems as well as in the common
devices used for control of unique processes. Manufacturers often send
technical bulletins to select lists of customers indicating problem
issues with components of end products. Because of the management and
budget structure built around Y2K remediation efforts, product
compliancy information must be made public in terms of do nothing,
revise, replace, test, and methodology.
Lets hear it for all of the ants building the hill one grain at a time!
Harlan Pittelkau, Computer Information Consultant
Washington State, Year 2000 Program Office
harlanp@dis.wa.gov, (360) 902-3204, FAX: (360) 586-8992
_____________________
Posted with permission from author,
Svejk
(GL-15 applies: http://digiserve.com/fbngraphics/gl-des1.htm ;-) |
