SI
SI
discoversearch

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor.  We ask that you disable ad blocking while on Silicon Investor in the best interests of our community.  If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.
Microcap & Penny Stocks : ALYA Cost cutting system via software as well as security -- Ignore unavailable to you. Want to Upgrade?


To: Glen Abbey who wrote (1255)7/14/1998 3:45:00 PM
From: Essam Hamza  Respond to of 2534
 
[CyberTimes]
[toolbar]
[IBM E-business solutions]

November 12, 1997

Real Estate: For Building Operators, a Taste Of The
Year 2000 In '99?

By JOHN HOLUSHA

EW YORK -- Office workers heading back to their
buildings after all the celebrations accompanying
the advent of the year 2000 may be in for a surprise.
They may find that the building's security system does
not recognize their magnetically coded card. They may
also find all the elevators stubbornly insistent on
staying on the ground floor.

Engineers and property managers say building operations
are no less susceptible to what is known as the "year
2000 problem" or the "millennium bug" than their
counterparts in banking, insurance and accounting.
Because computer programmers opted to use only the last
two digits of years in dates to conserve memory in the
1970s and 1980s, many control systems may misinterpret
the 00 that replaces the 99 of 1999.

It is impossible to predict what some systems will do
unless the clock is artificially advanced to see what
goes wrong, which is difficult to do in an operating
building. The security system, designed to restrict
admission on weekends, may shift to a default mode and
keep everybody out. The elevator controller may decide
that no maintenance has been done in 100 years and
lower all the cars to the ground floor as it would in a
fire.

"The real old stuff is not a problem because it is
electromechanical, and in the newer equipment, the
manufacturers have anticipated the 2000 problem," said
Kenneth Silver, an associate principal with Flack &
Kurtz Consulting Engineers. "But a lot was built in the
1970s and 1980s that have chips embedded in their
control units that did not anticipate 2000."

He said most 2000 errors would result in nuisances,
like elevators that have to be operated with an
override key until the fix is made. But in complicated,
multibuilding operations, like a hospital complex or a
college campus operating as a custom network, the
consequences could be severe.

The problem may not wait for the ball to fall in Times
Square on Dec. 31, 1999. Difficulties may start to pop
up on Sept. 9, 1999, because of another programming
trick, Silver said. "The highest number in a
four-number sequence is 9999," he said. "It was often
used as an error code." As a result, systems like fire
alarms could start generating false signals when that
date is reached.

Many property managers say they are surveying their
buildings to see what types and models of equipment
they have. They are then contacting the manufacturers
either to get assurances that the devices are "2000
compliant," or to find out what sorts of repairs or
replacements are needed.

"We started in on Feb. 11 of this year by giving our
on-site property managers a plan to survey the
buildings and identify problems," said Anthony
Lifrieri, managing director of operations for the
Insignia/Edward S. Gordon Co., which manages 50
buildings in the New York metropolitan area.

He said equipment suppliers had been asked to warrant
in writing that their devices will not crash as the 00
replaces the 99. "Some of the letters were a little too
generic, so we are doing a second round asking if the
model we have in our building has a compliant
processor," he said.

Lifrieri said some discreet testing had been done at
some of the buildings that his company manages. "In
some locations, we simulated 2000 and found that things
worked," he said.

Gwen Jolley, vice president for information technology
for Compass Management & Leasing, said much of the
equipment in a typical building, such as heating and
cooling, is on a 24-hour time system, which would not
be affected by a date change. "Our
preventive-maintenance system is date-driven," he said,
"but it is only four years old and is equipped to
handle 2000."

John Santora, a senior managing director of Cushman &
Wakefield, another property manager, said the company
has set a date of June 1998 for manufacturers to say
whether their equipment is 2000 compliant. After that,
he said, economics will take control.

"We are going to have to decide, if a system is not in
compliance, whether to try to repair or replace it,"
Santora said.

In most cases, he said, it would be too difficult to
repair equipment that has older chips with obsolete
programming languages.

"The first microprocessor-controlled elevators were
installed in 1978 and 1979," he said. "Making changes
to the existing controller probably will not be
cost-effective, so we will just replace the head," he
said, referring to the control unit.

He said research has not turned up any problem that
will be prohibitively costly to fix. He said replacing
the controller unit would cost about $15,000, while a
thorough elevator renovation, which a controller
replacement would be likely to trigger, is about
$100,000 per car.

He said many tenants were aware of the 2000 problem.
"Our clients are putting the onus on us," he said.
"They say: 'You are the property manager. What are your
going to do about it?' "

millennia-bcs.com



To: Glen Abbey who wrote (1255)7/14/1998 3:48:00 PM
From: Essam Hamza  Read Replies (1) | Respond to of 2534
 
Beyond IT Systems:
The Year 2000 Problem
Touches Everything

12 March 1997

Management Edge: Year 2000

An excerpt from "The Year 2000 Crisis: An Enormous Challenge that Must be
Addressed"

Strategic Analysis Report from the Gartner Group

D. Brown, W. Close, B. Conway, C. Germann, C. Goodhue, B. Hall, M. Hotle, C. Jones, N.
Jones, H. Kline, M. Light, S. Nelson, J. Pucciarelli, B. Reilly, J. Seay, P. Sondergaard, B. Stanco,
R. Terdiman, E. Andren

Back to the Year 2000 resources page.

The number of non-IT computers in the world far exceeds those in IT. Some are date-aware and
embedded in mission-critical systems, and therefore must be checked for year 2000 compliance.
Many enterprises own non-IT equipment, such as process control or monitoring systems, that is
both mission-critical and date-aware, and that may contain year 2000 errors. Although the risk of
failure is low, the consequences of failure may be very serious. Hence, these must be investigated
as part of the overall year 2000 project.

Strategic Planning Assumption: More than 50 million embedded-system devices worldwide
will exhibit year 2000 date anomalies in 1999 (0.6 probability).

The challenge that these devices pose is not restricted to IS organizations or IT applications. Most
of the computers in the world are performing non-IT functions. In 1995, Dataquest, a Gartner
Group company, estimated worldwide shipments of reduced instruction set computer (RISC) and
x86 microprocessors at more than 200 million units -- over half of which were in embedded
systems.

The number of microprocessors is tiny when compared to the more than three billion
microcontroller chips shipped in the same period. These are small, programmable units with word
lengths ranging from 4 to 32 bits embedded in consumer and industrial devices. The average car
contains 14 microcontrollers, and some include more than 45. Other uses include video recorders,
microwave ovens, factory machinery and air-conditioning systems. The following examples
illustrate a selection of commercial, date-aware embedded systems:

Environmental-control units
Factory printing and packaging machinery
Process control and monitoring equipment
Video recorders
Security and access control systems
Telephone exchanges
Traffic lights
Civilian and military avionics

Year 2000 faults in many of these units would be annoying rather than catastrophic; however,
enterprises cannot afford to ignore the small percentage that have direct business impact. Failures in
the following embedded systems, for example, would be unacceptable:

Factory printing and packaging machinery. The law requires expiration dates to be
printed on food products in many countries.
Traffic lights. Failure could cause accidents.
Military systems. Weaponry might not operate correctly.
Monitoring equipment. Enterprises such as nuclear power stations may be legally required
to log measurements.

Issues for Non-IT Systems

Although many enterprises are aware of this issue, in 2H96, less than 5 percent investigated it in
sufficient detail to provide a quantitative assessment of its impact (0.7 probability). Issues to
consider include:

Microcontroller equipment may be connected to corporate IT systems (e.g., printing bar
codes, batch numbers and expiration dates on manufactured goods). The year 2000 date
problem can be exported or imported via such links.
Many enterprises own non-IT equipment (e.g., in process control or monitoring systems)
that is both mission-critical and date-aware, and that may contain year 2000 errors.
Identifying and correcting year 2000 errors in embedded systems is expensive (generally
requiring significant manual effort). Much factory equipment cannot be shut down or tested
trivially. Embedded controllers and microprocessors may be in units that are no longer
manufactured, or suppliers may not be able to offer updates. Even when correction is
possible, a physical hardware update (such as a new ROM chip) may be required.
Companies that have manufactured consumer or industrial equipment that is not
year-2000-compliant must be prepared for conversion, support and legal costs. The laws
that may relate to year 2000 conformance and consumer products vary substantially among
different countries, and generally have not yet been tested in court. In some European
countries, general consumer legislation (such as the U.K. requirement that goods be "of
merchantable quality and fit for their purpose") will force suppliers to deliver conformant
products, although the date when this becomes legally necessary is still undefined. A further
complication is that, in some countries, the law applying to consumers differs from the law
that applies when two parties, such as business enterprises, enter into a mutually negotiated
contract. In the latter case, the responsibility for year 2000 conformance may be more
explicitly assigned.
It is generally difficult and expensive to identify and audit embedded systems. The process
cannot be automated and is likely to require physical inspection of hardware distributed
widely throughout the enterprise.

A Plan for Embedded Systems

A high-level project plan to investigate year 2000 conformance in embedded systems might consist
of six stages:

Responsibility. Appoint a project coordinator reporting to the year 2000 project office.
Education and Awareness. Investigating the year 2000 impact of embedded systems
cannot be carried out centrally; it will require effort from every business location in the
enterprise. Embedded systems are less obvious than IT programs; an education and
awareness program is essential to ensure that staff understand the risks and the many forms
embedded systems can take.
Inventory. Create an inventory of date-aware embedded systems in all business locations.
Prioritizing and Planning. Investigation may be expensive and the impact of embedded
system date errors may vary from trivial to catastrophic. Effort should be concentrated
initially on those systems posing the greatest business risk.
Investigation. Determine if date-aware equipment is year-2000-compliant. This may
involve testing or contacting suppliers. As initial results arrive, statistical techniques can be
used to obtain early estimates of overall cost to be fed back to the year 2000 project office.
Correction. Correct or replace equipment and interfaces as necessary.

wsj.com