1999 AGN JAN 19 I24 - Laserfiche WebLink

Browse Search

Year 2000 Issues for the Electric Utility Industry 5 Transfer - Systems exchange dates with other. systems, frequently without standard date formats between systems. This forces the need to review each and every system. Often, date-stamped data is collected by an intermediate system or device and the use of that information must be traced. Some examples of date transfer include: ■ Batch processing ■ Statistical Process Control (SPC) ■ Process information management ■ Time synchronization of PLC's, systems (PIMs) networks, network applications, ■ Dates embedded in bar codes communications ■ PLC programming ■ Electronic transactions (commerce, notifications, inquiries, status, etc.) ■ Keyboard entry ■ Production planning Output - These situations are not critical if the end-user can properly interpret the date format. In some cases, however, the output can affect a later use in the "information chain." Some examples of date -oriented sensitive output include: ■ Shift reports ■ Printed schedules ■ Shipping documents ■ Orders ■ Operator interface screens ■ Compliance documents ■ Notifications ■ Change management documents ■ Billings/Invoices Calculations - Functions specific to calendar date, day of the week, and other calendar - based periods could have Y2k-related issues. The difference between two dates can be very sensitive, especially if the result is used in a denominator. Some general calculation -related areas include: ■ Specific operations by day, or other ■ Expiration dates calendar -based period including ■ Comparisons startup and shutdown routines, report generation and scheduling ■ Custom programs ■ Counters that span the year 2000 ■ Dates as code rollover ■ Access control ■ Energy management systems ■ Supervisory control and sequencing Copyright 1998, TAVA/R. W. BeckLLc AU rights reserved. �TAIA R\WRECK